< draft-ietf-ecrit-ecall-18.txt   draft-ietf-ecrit-ecall-19.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: April 20, 2017 Individual Expires: April 21, 2017 Individual
October 17, 2016 October 18, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-18.txt draft-ietf-ecrit-ecall-19.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of the pan European in- mechanisms to support the next generation of the pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 20, 2017. This Internet-Draft will expire on April 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 47 skipping to change at page 2, line 47
10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18 10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18
10.1. Overall Description . . . . . . . . . . . . . . . . . . 18 10.1. Overall Description . . . . . . . . . . . . . . . . . . 18
10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19 10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19
10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19 10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19
10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19 10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19
10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19 10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19
10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 19 10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 19
10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20 10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20
10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20 10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20
10.9. Info Package Security Considerations . . . . . . . . . . 20 10.9. Info Package Security Considerations . . . . . . . . . . 20
10.10. Implementation Details . . . . . . . . . . . . . . . . . 20 10.10. Implementation Details . . . . . . . . . . . . . . . . . 21
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21
12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 12. Security Considerations . . . . . . . . . . . . . . . . . . . 26
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28 14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
15.1. Service URN Registrations . . . . . . . . . . . . . . . 30 15.1. Service URN Registrations . . . . . . . . . . . . . . . 30
15.2. MIME Media Type Registration for 15.2. MIME Media Type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 'application/emergencyCallData.eCall.MSD+per' . . . . . 31
15.3. MIME Media Type Registration for 15.3. MIME Media Type Registration for
skipping to change at page 3, line 24 skipping to change at page 3, line 24
15.6. Registration of the emergencyCallData.eCall Info Package 34 15.6. Registration of the emergencyCallData.eCall Info Package 34
15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34 15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34
15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34 15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34
15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35 15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35
15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36
15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36 15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36
15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37 15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38
18. Changes from Previous Versions . . . . . . . . . . . . . . . 38 18. Changes from Previous Versions . . . . . . . . . . . . . . . 38
18.1. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38 18.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 38
18.2. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38 18.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38
18.3. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38 18.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38
18.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 18.4. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38
18.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 39 18.5. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 39
18.6. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 39 18.6. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 39
18.7. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39 18.7. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 39
18.8. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39 18.8. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39
18.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 18.9. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39
18.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 40 18.10. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 40
18.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 18.11. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 40
18.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40 18.12. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40
18.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40 18.13. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 41
18.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 41 18.14. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 41
18.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41 18.15. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 41
18.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41 18.16. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41
18.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41 18.17. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41
18.18. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41 18.18. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42
18.19. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42 18.19. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 42
18.20. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42 18.20. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42
18.21. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42 18.21. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42
18.22. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
19.1. Normative References . . . . . . . . . . . . . . . . . . 42 19.1. Normative References . . . . . . . . . . . . . . . . . . 43
19.2. Informative references . . . . . . . . . . . . . . . . . 43 19.2. Informative references . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
skipping to change at page 8, line 35 skipping to change at page 8, line 35
(or appending to) a Call-Info header field at the top level of the (or appending to) a Call-Info header field at the top level of the
SIP message. This Call-Info header field contains a CID URL SIP message. This Call-Info header field contains a CID URL
referencing the body part's unique identifier, and a 'purpose' referencing the body part's unique identifier, and a 'purpose'
parameter identifying the data as an eCall metadata/control block per parameter identifying the data as an eCall metadata/control block per
the Emergency Call Additional Data Blocks registry entry; the the Emergency Call Additional Data Blocks registry entry; the
'purpose' parameter's value is 'emergencyCallData.control'. Per 'purpose' parameter's value is 'emergencyCallData.control'. Per
[RFC6086], a metadata/control object is carried in a SIP INFO request [RFC6086], a metadata/control object is carried in a SIP INFO request
by using the INFO package defined in Section 10. by using the INFO package defined in Section 10.
An MSD or a metadata/control block is always enclosed in a multipart An MSD or a metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the (normally multipart/mixed) body part (even if it would otherwise be
SIP message), since as of the date of this document, the use of the only body part in the SIP message), since as of the date of this
Content-ID as a SIP header field is not defined (while it is defined document, the use of Content-ID as a SIP header field is not defined
for use as a MIME header field). (while it is defined for use as a MIME header field).
A body part containing an MSD or metadata/control object has a A body part containing an MSD or metadata/control object has a
Content-Disposition header field value containing "By-Reference". Content-Disposition header field value containing "By-Reference".
An In-Vehicle System (IVS) initiating an NG-eCall attaches an MSD to An In-Vehicle System (IVS) initiating an NG-eCall attaches an MSD to
the initial INVITE and optionally attaches a metadata/control object the initial INVITE and optionally attaches a metadata/control object
informing the PSAP of its capabilities. The MSD body part (and informing the PSAP of its capabilities. The MSD body part (and
metadata/control and PIDF-LO body parts if included) have a Content- metadata/control and PIDF-LO body parts if included) have a Content-
Disposition header field with the value "By-Reference; Disposition header field with the value "By-Reference;
handling=optional". Specifying "handling=optional" prevents the handling=optional". Specifying "handling=optional" prevents the
skipping to change at page 9, line 23 skipping to change at page 9, line 23
response code 600 (Busy Everywhere), 486 (Busy Here), or 603 response code 600 (Busy Everywhere), 486 (Busy Here), or 603
(Decline). (Decline).
If the IVS receives an acknowledgment for an MSD containing If the IVS receives an acknowledgment for an MSD containing
"received=false", this indicates that the PSAP was unable to properly "received=false", this indicates that the PSAP was unable to properly
decode or process the MSD. The IVS action is not defined (e.g., it decode or process the MSD. The IVS action is not defined (e.g., it
might only log an error). Since the PSAP is able to request an might only log an error). Since the PSAP is able to request an
updated MSD during the call, if an initial MSD is unsatisfactory in updated MSD during the call, if an initial MSD is unsatisfactory in
any way, the PSAP can choose to request another one. any way, the PSAP can choose to request another one.
A PSAP can request that the vehicle send an updated MSD during a A PSAP can request that the vehicle send an updated MSD during a call
call. To do so, the PSAP creates a metadata/control object (e.g., upon manual request of the PSAP call taker who suspects
requesting an MSD and attaches it to a SIP INFO request and sends it vehicle state may have changed.) To do so, the PSAP creates a
within the dialog. The IVS then attaches an updated MSD to a SIP metadata/control object requesting an MSD and attaches it to a SIP
INFO request and sends it within the dialog. If the IVS is unable to INFO request and sends it within the dialog. The IVS then attaches
send an MSD, it instead sends a metadata/control object acknowledging an updated MSD to a SIP INFO request and sends it within the dialog.
the request with the 'success' parameter set to 'false' and a If the IVS is unable to send an MSD, it instead sends a metadata/
'reason' parameter (and optionally a 'details' parameter) indicating control object acknowledging the request with the 'success' parameter
why the request could not be accomplished. Per [RFC6086], metadata/ set to 'false' and a 'reason' parameter (and optionally a 'details'
control objects and MSDs are sent using the INFO package defined in parameter) indicating why the request could not be accomplished. Per
Section 10 . In addition, to align with how an MSD or metadata/ [RFC6086], metadata/control objects and MSDs are sent using the INFO
control block is transmitted in a SIP message other than an INFO package defined in Section 10 . In addition, to align with how an
request, a Call-Info header field is included in the SIP INFO request MSD or metadata/control block is transmitted in a SIP message other
to reference the MSD or metadata/control block. See Section 10 for than an INFO request, a Call-Info header field is included in the SIP
information about the use of INFO requests to carry data within an INFO request to reference the MSD or metadata/control block. See
eCall. Section 10 for information about the use of INFO requests to carry
data within an eCall.
The IVS is not expected to send an unsolicited MSD after the initial The IVS is not expected to send an unsolicited MSD after the initial
INVITE. INVITE.
Support for the data blocks defined in [RFC7852] is NOT REQUIRED for Support for the data blocks defined in [RFC7852] is NOT REQUIRED for
conformance with this document. conformance with this document.
7. Call Setup 7. Call Setup
In circuit-switched eCall, the IVS places a special form of a 112 In circuit-switched eCall, the IVS places a special form of a 112
skipping to change at page 12, line 40 skipping to change at page 12, line 43
towards the IVS before the error response from the PSAP is received, towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.) the response will be dropped, but these are unlikely to occur here.)
The metadata/control block is carried in the MIME type 'application/ The metadata/control block is carried in the MIME type 'application/
emergencyCallData.control+xml'. emergencyCallData.control+xml'.
The metadata/control block is designed for use with pan-European The metadata/control block is designed for use with pan-European
eCall and also eCall-like systems (i.e., in other regions), and has eCall and also eCall-like systems (i.e., in other regions), and has
extension points. Note that eCall-like systems might define their extension points. Note that eCall-like systems might define their
own vehicle data blocks, and so might need to register a new INFO own vehicle data blocks, and so might need to register a new INFO
package to accomodate the new data content type and the metadata/ package to accomodate the new data MIME media type and the metadata/
control object. control object.
9.1. The Control Block 9.1. The Control Block
The control block is an XML data structure allowing for The control block is an XML data structure allowing for
acknowledgments, requests, and capabilities information. It is acknowledgments, requests, and capabilities information. It is
carried in a body part with a specific MIME media type. Three carried in a body part with a specific MIME media type. Three
elements are defined for use within a control block: elements are defined for use within a control block:
ack Acknowledges receipt of data or a request. ack Acknowledges receipt of data or a request.
skipping to change at page 19, line 50 skipping to change at page 19, line 50
None None
10.5. SIP Option-Tags 10.5. SIP Option-Tags
None None
10.6. INFO Request Body Parts 10.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a The body for an emergencyCallData.eCall.MSD info package is a
multipart body containing zero or one application/ multipart (normally multipart/mixed) body containing zero or one
emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or application/emergencyCallData.eCall.MSD+per part (containing an MSD)
more application/emergencyCallData.control+xml (containing a and zero or more application/emergencyCallData.control+xml
metadata/control object) parts. At least one MSD or metadata/control (containing a metadata/control object) parts. At least one MSD or
body part is expected; the behavior upon receiving an INFO request metadata/control body part is expected; the behavior upon receiving
with neither is undefined. an INFO request with neither is undefined.
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in SIP messages other than INFO with how these body parts are sent in SIP messages other than INFO
requests, each associated body part is referenced by a Call-Info requests, each associated body part is referenced by a Call-Info
header field at the top level of the SIP message. The body part has header field at the top level of the SIP message. The body part has
a Content-Disposition header field set to "By-Reference". a Content-Disposition header field set to "By-Reference".
An MSD or metadata/control block is always enclosed in a multipart An MSD or metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the body part (even if it would otherwise be the only body part in the
SIP message), since as of the date of this document, the use of SIP message), since as of the date of this document, the use of
skipping to change at page 20, line 31 skipping to change at page 20, line 31
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
10.7. Info Package Usage Restrictions 10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
10.8. Rate of INFO Requests 10.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The SIP INFO request is used within an established emergency call
emergencyCallData.eCall.MSD info package is normally quite low (most dialog for the PSAP to request the IVS to send an updated MSD, and
dialogs are likely to contain zero INFO requests, while others can be for the IVS to send a requested MSD. Because this is normally done
expected to carry an occasional request). only on manual request of the PSAP call taker (who suspects some
aspect of the vehicle state has changed), the rate of SIP INFO
requests associated with the emergencyCallData.eCall.MSD info package
is normally quite low (most dialogs are likely to contain zero INFO
requests, while others might carry an occasional request).
10.9. Info Package Security Considerations 10.9. Info Package Security Considerations
The MIME media type registations for the data blocks that can be The MIME media type registations for the data blocks that can be
carried using this INFO package contains a discussion of the security carried using this INFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of "Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of [TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in eCalls. the data carried in eCalls.
skipping to change at page 26, line 49 skipping to change at page 26, line 49
two locations are independently determined. Even in situations where two locations are independently determined. Even in situations where
the network-supplied location is limited to the cell site, this can the network-supplied location is limited to the cell site, this can
be useful as a sanity check on the device-supplied location contained be useful as a sanity check on the device-supplied location contained
in the MSD. in the MSD.
The document [RFC7378] discusses trust issues regarding location The document [RFC7378] discusses trust issues regarding location
provided by or determined in cooperation with end devices. provided by or determined in cooperation with end devices.
Security considerations specific to the mechanism by which the PSAP Security considerations specific to the mechanism by which the PSAP
sends acknowledgments and requests to the vehicle are discussed in sends acknowledgments and requests to the vehicle are discussed in
the "Security Considerations" block of Section 15.3. the "Security Considerations" block of Section 15.3. Note that an
attacker that has access to and is capable of generating a response
to the initial INVITE request could generate a 600 (Busy Everywhere),
486 (Busy Here), or 603 (Decline) response that includes a metadata/
control object containing a reference to the MSD in the initial
INVITE and a "received=true" field, which could result in the IVS
perceiving the PSAP to be overloaded and hence not attempting to
reinitiate the call. The risk can be mitigated as discussed in the
"Security Considerations" block of Section 15.3.
Data received from external sources inherently carries implementation Data received from external sources inherently carries implementation
risks. For example, depending on the platform, buffer overflows can risks. For example, depending on the platform, buffer overflows can
introduce remote code execution vulnerabilities, null characters can introduce remote code execution vulnerabilities, null characters can
corrupt strings, numeric values used for internal calculations can corrupt strings, numeric values used for internal calculations can
result in underflow/overflow errors, malformed XML objects can expose result in underflow/overflow errors, malformed XML objects can expose
parsing bugs, etc. Implementations need to be cognizant of the parsing bugs, etc. Implementations need to be cognizant of the
potential risks, observe best practices (which might include potential risks, observe best practices (which might include
sufficiently capable static code analysis, fuzz testing, component sufficiently capable static code analysis, fuzz testing, component
isolation, avoiding use of unsafe coding techniques, third-party isolation, avoiding use of unsafe coding techniques, third-party
skipping to change at page 31, line 38 skipping to change at page 31, line 43
Mandatory parameters: none Mandatory parameters: none
Optional parameters: none Optional parameters: none
Encoding scheme: binary Encoding scheme: binary
Encoding considerations: Uses ASN.1 PER, which is a binary Encoding considerations: Uses ASN.1 PER, which is a binary
encoding; when transported in SIP, binary content transfer encoding; when transported in SIP, binary content transfer
encoding is used. encoding is used.
Security considerations: This content type is designed to carry Security considerations: This media type is designed to carry
vehicle and incident-related data during an emergency call. This vehicle and incident-related data during an emergency call. This
data contains personal information including vehicle VIN, data contains personal information including vehicle VIN,
location, direction, etc. Appropriate precautions need to be location, direction, etc. Appropriate precautions need to be
taken to limit unauthorized access, inappropriate disclosure to taken to limit unauthorized access, inappropriate disclosure to
third parties, and eavesdropping of this information. In general, third parties, and eavesdropping of this information. In general,
it is acceptable for the data to be unprotected while briefly in it is acceptable for the data to be unprotected while briefly in
transit within the Mobile Network Operator (MNO); the MNO is transit within the Mobile Network Operator (MNO); the MNO is
trusted to not permit the data to be accessed by third parties. trusted to not permit the data to be accessed by third parties.
Sections 7 and Section 8 of [RFC7852] contain more discussion. Sections 7 and Section 8 of [RFC7852] contain more discussion.
skipping to change at page 33, line 5 skipping to change at page 33, line 11
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of the XML content. Indicates the character encoding of the XML content.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 7303 [RFC7303]. Section 3.2 of RFC 7303 [RFC7303].
Security considerations: Security considerations:
This content type carries metadata and control information and This media type carries metadata and control information and
requests, such as from a Public Safety Answering Point (PSAP) requests, such as from a Public Safety Answering Point (PSAP)
to an In-Vehicle System (IVS) during an emergency call. to an In-Vehicle System (IVS) during an emergency call.
Metadata (such as an acknowledgment that data sent by the IVS Metadata (such as an acknowledgment that data sent by the IVS
to the PSAP was successfully received) has limited privacy and to the PSAP was successfully received) has limited privacy and
security implications. Control information (such as requests security implications. Control information (such as requests
from the PSAP that the vehicle perform an action) has some from the PSAP that the vehicle perform an action) has some
privacy and security implications. The privacy concern arises privacy and security implications. The privacy concern arises
from the ability to request the vehicle to transmit a data set, from the ability to request the vehicle to transmit a data set,
which as described in Section 15.2, can contain personal which as described in Section 15.2, can contain personal
skipping to change at page 38, line 25 skipping to change at page 38, line 25
for their review and comments; Robert Sparks and Paul Kyzivat for for their review and comments; Robert Sparks and Paul Kyzivat for
their help with the SIP mechanisms; Mark Baker and Ned Freed for their help with the SIP mechanisms; Mark Baker and Ned Freed for
their help with the media subtype registration issue. We would like their help with the media subtype registration issue. We would like
to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and
Ulrich Dietz for their help with the original document upon which Ulrich Dietz for their help with the original document upon which
this document is based. Christer Holmberg deserves special mention this document is based. Christer Holmberg deserves special mention
for his many detailed reviews. for his many detailed reviews.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-17 to draft-ietf-18 18.1. Changes from draft-ietf-18 to draft-ietf-19
o Added additional text to "Rate of Info Requests"
o Added additional text to "Security Considerations"
o Further corrected "content type" to "media type"
18.2. Changes from draft-ietf-17 to draft-ietf-18
o Added reference to 3GPP TS24.229 o Added reference to 3GPP TS24.229
o Clarified that an INFO request is expected to have at least one o Clarified that an INFO request is expected to have at least one
MSD or metadata/control body part MSD or metadata/control body part
o Fixed minor errors in examples o Fixed minor errors in examples
o Corrected "content type" to "media type" o Corrected "content type" to "media type"
o Deleted "xsi:schemaLocation" from examples o Deleted "xsi:schemaLocation" from examples
18.2. Changes from draft-ietf-16 to draft-ietf-17 18.3. Changes from draft-ietf-16 to draft-ietf-17
o Clarify Content-Disposition value in INFO requests o Clarify Content-Disposition value in INFO requests
18.3. Changes from draft-ietf-15 to draft-ietf-16 18.4. Changes from draft-ietf-15 to draft-ietf-16
o Various clarifications and simplifications o Various clarifications and simplifications
o Added reference to 3GPP 23.167 o Added reference to 3GPP 23.167
18.4. Changes from draft-ietf-14 to draft-ietf-15 18.5. Changes from draft-ietf-14 to draft-ietf-15
o eCall body parts now always sent enclosed in multipart (even if o eCall body parts now always sent enclosed in multipart (even if
only body part in SIP message) and hence always have a Content- only body part in SIP message) and hence always have a Content-
Disposition of By-Reference Disposition of By-Reference
o Fixed errors in attribute directionality text o Fixed errors in attribute directionality text
o Fixed typos. o Fixed typos.
18.5. Changes from draft-ietf-13 to draft-ietf-14 18.6. Changes from draft-ietf-13 to draft-ietf-14
o Added text to the IANA Considerations to formalize the o Added text to the IANA Considerations to formalize the
EmergencyCallData media subtree EmergencyCallData media subtree
o Fixed some typos o Fixed some typos
18.6. Changes from draft-ietf-12 to draft-ietf-13 18.7. Changes from draft-ietf-12 to draft-ietf-13
o Clarifications suggested by Christer o Clarifications suggested by Christer
o Corrections to Content-Disposition text and examples as suggested o Corrections to Content-Disposition text and examples as suggested
by Paul Kyzivat by Paul Kyzivat
o Clarifications to Content-Disposition text and examples to clarify o Clarifications to Content-Disposition text and examples to clarify
that handling=optional is only used in the initial INVITE that handling=optional is only used in the initial INVITE
18.7. Changes from draft-ietf-11 to draft-ietf-12 18.8. Changes from draft-ietf-11 to draft-ietf-12
o Fixed errors in examples found by Dale o Fixed errors in examples found by Dale
o Removed enclosing sub-section of INFO package registration section o Removed enclosing sub-section of INFO package registration section
o Added text per Christer and Dale's suggestions that the MSD and o Added text per Christer and Dale's suggestions that the MSD and
metadata/control blocks are sent in INFO with a Call-Info header metadata/control blocks are sent in INFO with a Call-Info header
field referencing them field referencing them
o Deleted Call Routing section (7.1) in favor of a statement that o Deleted Call Routing section (7.1) in favor of a statement that
call routing is outside the scope of the document call routing is outside the scope of the document
o Other text changes per comments received from Christer and Ivo. o Other text changes per comments received from Christer and Ivo.
18.8. Changes from draft-ietf-09 to draft-ietf-11 18.9. Changes from draft-ietf-09 to draft-ietf-11
o Renamed INFO package to emergencyCallData.eCall.MSD o Renamed INFO package to emergencyCallData.eCall.MSD
o Changed INFO package to only permit MSD and metadata/control MIME o Changed INFO package to only permit MSD and metadata/control MIME
types types
o Moved <capabilities> element back from car-crash but made it o Moved <capabilities> element back from car-crash but made it
OPTIONAL OPTIONAL
o Moved other extension points back from car-crash so that extension o Moved other extension points back from car-crash so that extension
points are in base spec (and also to get XML schema to compile) points are in base spec (and also to get XML schema to compile)
o Text changes for clarification. o Text changes for clarification.
18.9. Changes from draft-ietf-08 to draft-ietf-09 18.10. Changes from draft-ietf-08 to draft-ietf-09
o Created a new "Data Transport" section that describes how the MSD o Created a new "Data Transport" section that describes how the MSD
and metadata/control blocks are attached, and then referred to and metadata/control blocks are attached, and then referred to
that section rather than repeat the information about the CID and that section rather than repeat the information about the CID and
Call-Info and so forth, which means most references to the Call-Info and so forth, which means most references to the
additional-data draft have now been deleted additional-data draft have now been deleted
o Mentioned edge cases where a PSAP response to INVITE isn't o Mentioned edge cases where a PSAP response to INVITE isn't
received by the IVS received by the IVS
o Reworded description of which status codes are used when a PSAP o Reworded description of which status codes are used when a PSAP
wishes to reject a call but inform the vehicle occupants that it wishes to reject a call but inform the vehicle occupants that it
skipping to change at page 40, line 4 skipping to change at page 40, line 17
o Created a new "Data Transport" section that describes how the MSD o Created a new "Data Transport" section that describes how the MSD
and metadata/control blocks are attached, and then referred to and metadata/control blocks are attached, and then referred to
that section rather than repeat the information about the CID and that section rather than repeat the information about the CID and
Call-Info and so forth, which means most references to the Call-Info and so forth, which means most references to the
additional-data draft have now been deleted additional-data draft have now been deleted
o Mentioned edge cases where a PSAP response to INVITE isn't o Mentioned edge cases where a PSAP response to INVITE isn't
received by the IVS received by the IVS
o Reworded description of which status codes are used when a PSAP o Reworded description of which status codes are used when a PSAP
wishes to reject a call but inform the vehicle occupants that it wishes to reject a call but inform the vehicle occupants that it
is aware of the situation to be more definite is aware of the situation to be more definite
o Added examples showing INFO o Added examples showing INFO
o Added references for eCall test call requirement o Added references for eCall test call requirement
o Described meaning of eCall URNs in Section 8 as well as in IANA o Described meaning of eCall URNs in Section 8 as well as in IANA
registration registration
18.10. Changes from draft-ietf-07 to draft-ietf-08 18.11. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, and solicited MSDs control usage, such as use in rejected calls, and solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
skipping to change at page 40, line 33 skipping to change at page 40, line 45
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section 7.1 to be a subsection of 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 10 to be a main section instead of a o Moved new Section Section 10 to be a main section instead of a
subsection of Section 9 subsection of Section 9
o Revised SIP INFO usage and package registration per advice from o Revised SIP INFO usage and package registration per advice from
Robert Sparks and Paul Kyzivat Robert Sparks and Paul Kyzivat
18.11. Changes from draft-ietf-06 to draft-ietf-07 18.12. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.12. Changes from draft-ietf-05 to draft-ietf-06 18.13. Changes from draft-ietf-05 to draft-ietf-06
o Added additional security and privacy clarifications regarding o Added additional security and privacy clarifications regarding
signed and encrypted data signed and encrypted data
o Additional security and privacy text o Additional security and privacy text
o Deleted informative section on ESINets as unnecessary. o Deleted informative section on ESINets as unnecessary.
18.13. Changes from draft-ietf-04 to draft-ietf-05 18.14. Changes from draft-ietf-04 to draft-ietf-05
o Reworked the security and privacy considerations material in the o Reworked the security and privacy considerations material in the
document as a whole and in the MIME registation sections of the document as a whole and in the MIME registation sections of the
MSD and control objects MSD and control objects
o Clarified that the <actionResult> element can appear multiple o Clarified that the <actionResult> element can appear multiple
times within an <ack> element times within an <ack> element
o Fixed IMS definition o Fixed IMS definition
o Added clarifying text for the 'msgid' attribute o Added clarifying text for the 'msgid' attribute
18.14. Changes from draft-ietf-03 to draft-ietf-04 18.15. Changes from draft-ietf-03 to draft-ietf-04
o Added Privacy Considerations section o Added Privacy Considerations section
o Reworded most uses of non-normative "may", "should", "must", and o Reworded most uses of non-normative "may", "should", "must", and
"recommended." "recommended."
o Fixed nits in examples o Fixed nits in examples
18.15. Changes from draft-ietf-02 to draft-ietf-03 18.16. Changes from draft-ietf-02 to draft-ietf-03
o Added request to enable cameras o Added request to enable cameras
o Improved examples and XML schema o Improved examples and XML schema
o Clarifications and wording improvements o Clarifications and wording improvements
18.16. Changes from draft-ietf-01 to draft-ietf-02 18.17. Changes from draft-ietf-01 to draft-ietf-02
o Added clarifying text reinforcing that the data exchange is for o Added clarifying text reinforcing that the data exchange is for
small blocks of data infrequently transmitted small blocks of data infrequently transmitted
o Clarified that dynamic media is conveyed using SIP re-INVITE to o Clarified that dynamic media is conveyed using SIP re-INVITE to
establish a one-way media stream establish a one-way media stream
o Clarified that the scope is the needs of eCall within the SIP o Clarified that the scope is the needs of eCall within the SIP
emergency call environment emergency call environment
o Added informative statement that the document may be suitable for o Added informative statement that the document may be suitable for
reuse by other ACN systems reuse by other ACN systems
o Clarified that normative language for the control block applies to o Clarified that normative language for the control block applies to
both IVS and PSAP both IVS and PSAP
o Removed 'ref', 'supported-mime', and <media> elements o Removed 'ref', 'supported-mime', and <media> elements
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.17. Changes from draft-ietf-00 to draft-ietf-01 18.18. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME media type for the control o Added IANA registration for the MIME media type for the control
object object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
control object control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.18. Changes from draft-gellens-03 to draft-ietf-00 18.19. Changes from draft-gellens-03 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf-. o Renamed from draft-gellens- to draft-ietf-.
o Added mention of and reference to ETSI TR "Mobile Standards Group o Added mention of and reference to ETSI TR "Mobile Standards Group
(MSG); eCall for VoIP" (MSG); eCall for VoIP"
o Added text to Introduction regarding migration/co-existence being o Added text to Introduction regarding migration/co-existence being
out of scope out of scope
o Added mention in Security Considerations that even if the network- o Added mention in Security Considerations that even if the network-
supplied location is just the cell site, this can be useful as a supplied location is just the cell site, this can be useful as a
sanity check on the IVS-supplied location sanity check on the IVS-supplied location
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.19. Changes from draft-gellens-02 to -03 18.20. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.20. Changes from draft-gellens-01 to -02 18.21. Changes from draft-gellens-01 to -02
o Minor wording improvements o Minor wording improvements
o Removed ".automatic" and ".manual" from o Removed ".automatic" and ".manual" from
"urn:service:test.sos.ecall" registration and discussion text. "urn:service:test.sos.ecall" registration and discussion text.
18.21. Changes from draft-gellens-00 to -01 18.22. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
19. References 19. References
19.1. Normative References 19.1. Normative References
[EN_16062] [EN_16062]
CEN, , "Intelligent transport systems - eSafety - eCall CEN, , "Intelligent transport systems - eSafety - eCall
High Level Application Requirements (HLAP) Using GSM/UMTS High Level Application Requirements (HLAP) Using GSM/UMTS
Circuit Switched Networks, EN 16062", April 2015. Circuit Switched Networks, EN 16062", April 2015.
[EN_16072] [EN_16072]
CEN, , "Intelligent transport systems - eSafety - Pan- CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April European eCall operating requirements, EN 16072", April
 End of changes. 38 change blocks. 
86 lines changed or deleted 103 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/