< draft-ietf-ecrit-ecall-14.txt   draft-ietf-ecrit-ecall-15.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 6, 2017 Individual Expires: April 12, 2017 Individual
October 3, 2016 October 9, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-14.txt draft-ietf-ecrit-ecall-15.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 41 skipping to change at page 1, line 41
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 6, 2017. This Internet-Draft will expire on April 12, 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 44 skipping to change at page 2, line 44
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 . . . . . . . . . . . . . . . . 20 10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . 21 10.10. Implementation Details . . . . . . . . . . . . . . . . . 20
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 20
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 . . . . . . . . . . . . . . . . . . . . . . . . . 27 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 Content-type Registration for 15.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 'application/emergencyCallData.eCall.MSD+per' . . . . . 31
15.3. MIME Content-type Registration for 15.3. MIME Content-type Registration for
'application/emergencyCallData.control+xml' . . . . . . 32 'application/emergencyCallData.control+xml' . . . . . . 32
15.4. Registration of the 'eCall.MSD' entry in the Emergency 15.4. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 34 Call Additional Data Blocks registry . . . . . . . . . . 34
15.5. Registration of the 'control' entry in the Emergency 15.5. Registration of the 'control' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 34 Call Additional Data Blocks registry . . . . . . . . . . 34
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-13 to draft-ietf-14 . . . . . . 38 18.1. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38
18.2. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38 18.2. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38
18.3. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 38 18.3. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38
18.4. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 38 18.4. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 38
18.5. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 18.5. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39
18.6. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 18.6. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39
18.7. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 18.7. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39
18.8. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40 18.8. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40
18.9. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40 18.9. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40
18.10. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40 18.10. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40
18.11. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 40 18.11. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40
18.12. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40 18.12. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 40
18.13. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41 18.13. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40
18.14. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41 18.14. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41
18.15. Changes from draft-gellens-02 to -03 . . . . . . . . . . 41 18.15. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41
18.16. Changes from draft-gellens-01 to -02 . . . . . . . . . . 41 18.16. Changes from draft-gellens-02 to -03 . . . . . . . . . . 41
18.17. Changes from draft-gellens-00 to -01 . . . . . . . . . . 41 18.17. Changes from draft-gellens-01 to -02 . . . . . . . . . . 41
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 18.18. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
19.1. Normative References . . . . . . . . . . . . . . . . . . 42 19.1. Normative References . . . . . . . . . . . . . . . . . . 42
19.2. Informative references . . . . . . . . . . . . . . . . . 43 19.2. Informative references . . . . . . . . . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
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].
skipping to change at page 7, line 26 skipping to change at page 7, line 26
document makes use of that mechanism. This document also registers document makes use of that mechanism. This document also registers
an INFO package (in Section 10) to enable eCall related data blocks an INFO package (in Section 10) to enable eCall related data blocks
to be carried in SIP INFO requests (per [RFC6086], new INFO usages to be carried in SIP INFO requests (per [RFC6086], new INFO usages
require the definition of an INFO package). require the definition of an INFO package).
Note that if other data sets need to be transmitted in the future, Note that if other data sets need to be transmitted in the future,
the appropriate signalling mechanism for such data needs to be the appropriate signalling mechanism for such data needs to be
evaluated, including factors such as the size and frequency of such evaluated, including factors such as the size and frequency of such
data. data.
An In-Vehicle System (IVS) transmits the MSD (see Section 5) by An In-Vehicle System (IVS) transmits an MSD (see Section 5) by
encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP encoding it per Annex A of EN 15722 [msd] and attaching it to a SIP
message as a MIME body part per [RFC7852]. The body part is message as a MIME body part per [RFC7852]. The body part is
identified by its MIME content-type ('application/ identified by its MIME content-type ('application/
emergencyCallData.eCall.MSD+per') in the Content-Type header field of emergencyCallData.eCall.MSD+per') in the Content-Type header field of
the body part. The body part is assigned a unique identifier which the body part. The body part is assigned a unique identifier which
is listed in a Content-ID header field in the body part. The SIP is listed in a Content-ID header field in the body part. The SIP
message is marked as containing the MSD by adding (or appending to) a message is marked as containing the MSD by adding (or appending to) a
Call-Info header field at the top level of the SIP message. This Call-Info header field at the top level of the SIP message. This
Call-Info header field contains a CID URL referencing the body part's Call-Info header field contains a CID URL referencing the body part's
unique identifier, and a 'purpose' parameter identifying the data as unique identifier, and a 'purpose' parameter identifying the data as
skipping to change at page 8, line 10 skipping to change at page 8, line 10
message is marked as containing the metadata/control object by adding message is marked as containing the metadata/control object by adding
(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.
As is necessary with message bodies, if an MSD or a metadata/control An MSD or a metadata/control block is always enclosed in a multipart
block is sent in the same message with another body part, a body part (even if it would otherwise be the only body part in the
multipart/mixed body part encloses all body parts. In some cases, SIP message). Note that in some cases there might be intermediate
there are intermediate multipart body parts between the top level multipart body parts between the top level multipart and the body
multipart/mixed and the body part containing the MSD or metadata/ part containing the MSD or metadata/control object.
control object.
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".
unless it is the only body part in a SIP INFO request, in which case,
per [RFC6086], "INFO-Package" is used.
An In-Vehicle System (IVS) initiating an NG-eCall attaches the 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 INVITE handling=optional". Specifying "handling=optional" prevents the
from being rejected if it is processed by a legacy element (e.g., a INVITE from being rejected if it is processed by a legacy element
gateway between SIP and circuit-switched environments) that does not (e.g., a gateway between SIP and circuit-switched environments) that
understand the MSD (or metadata/control object or PIDF-LO). The PSAP does not understand the MSD (or metadata/control object or PIDF-LO).
creates a metadata/control object acknowledging receipt of the MSD The PSAP creates a metadata/control object acknowledging receipt of
and attaches it to the SIP final response to the INVITE. The the MSD and attaches it to the SIP final response to the INVITE. A
metadata/control object is not attached to provisional (e.g., 180) metadata/control object is not attached to provisional (e.g., 180)
responses. responses.
If the IVS receives an acknowledgment for an MSD with received=false, If the IVS receives an acknowledgment for an MSD containing
it indicates some fault with the transfer of the MSD, the MSD "received=false", this indicates that the PSAP was unable to properly
content, or the PSAP's ability to properly receive, decode and act on decode or process the MSD. The IVS action is not defined (e.g., it
the MSD. The IVS action is not defined (e.g., it might only log an might only log an error). Since the PSAP is able to request an
error). Since the PSAP is able to request an updated MSD during the updated MSD during the call, if an initial MSD is unsatisfactory in
call, if an initial MSD is unsatisfactory in any way, the PSAP can any way, the PSAP can choose to request another one.
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. To do so, the PSAP creates a metadata/control object call. To do so, the PSAP creates a metadata/control object
requesting an MSD and attaches it to a SIP INFO request and sends it requesting an MSD and attaches it to a SIP INFO request and sends it
within the dialog. The IVS then attaches an updated MSD to a SIP within the dialog. The IVS then attaches an updated MSD 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. If the IVS is unable to
send an MSD, it instead sends a metadata/control object acknowledging send an MSD, it instead sends a metadata/control object acknowledging
the request with the 'success' parameter set to 'false' and a the request with the 'success' parameter set to 'false' and a
'reason' parameter (and optionally a 'details' parameter) indicating 'reason' parameter (and optionally a 'details' parameter) indicating
why the request cannot be accomplished. Per [RFC6086], metadata/ why the request could not be accomplished. Per [RFC6086], metadata/
control objects and MSDs are sent using the INFO package defined in control objects and MSDs are sent using the INFO package defined in
Section 10 . In addition, to align with how an MSD or metadata/ Section 10 . In addition, to align with how an MSD or metadata/
control block is transmitted in a SIP message other than an INFO control block is transmitted in a SIP message other than an INFO
request, one or more Call-Info header fields are included in the SIP request, a Call-Info header field is included in the SIP INFO request
INFO request to reference the MSD or metadata/control block. See to reference the MSD or metadata/control block. See Section 10 for
Section 10 for information about the use of INFO requests to carry information about the use of INFO requests to carry data within an
data within an eCall. eCall.
The IVS is not expected to send an unsolicited MSD during the call. The IVS is not expected to send an unsolicited MSD after the initial
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
emergency call which carries an eCall flag (indicating that the call emergency call which carries an eCall flag (indicating that the call
is an eCall and also if the call was manually or automatically is an eCall and also if the call was manually or automatically
triggered); the mobile network operator (MNO) recognizes the eCall triggered); the mobile network operator (MNO) recognizes the eCall
skipping to change at page 12, line 27 skipping to change at page 12, line 24
where the PSAP response is not received by the IVS, e.g., if an where the PSAP response is not received by the IVS, e.g., if an
intermediary sends a CANCEL, and an error response is forwarded intermediary sends a CANCEL, and an error response is forwarded
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 to accomodate variances. Note that eCall-like extension points. Note that eCall-like systems might define their
systems might define their own vehicle data blocks, and so might need own vehicle data blocks, and so might need to register a new INFO
to register a new INFO package to accomodate the new data content package to accomodate the new data content type and the metadata/
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 content type. Three carried in a body part with a specific MIME content 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.
capabilities: Used in a control block sent from the IVS to the PSAP capabilities Used in a control block sent from the IVS to the PSAP
(e.g., in the initial INVITE) to inform the PSAP of the (e.g., in the initial INVITE) to inform the PSAP of the
vehicle capabilities. Child elements contain all vehicle capabilities. Child elements contain all
actions and data types supported by the vehicle. It is actions and data types supported by the vehicle. It is
OPTIONAL for the IVS to send this block. Omitting the OPTIONAL for the IVS to send this block. Omitting the
block indicates that the IVS supports only the block indicates that the IVS supports only the
mandatory functionality defined in this document. mandatory functionality defined in this document.
request Used in a control block sent by the PSAP to the IVS, to request Used in a control block sent by the PSAP to the IVS, to
request the vehicle to perform an action. request the vehicle to perform an action.
skipping to change at page 13, line 19 skipping to change at page 13, line 16
to supply related information. The 'action' attribute is mandatory to supply related information. The 'action' attribute is mandatory
and indicates the specific action. An IANA registry is created in and indicates the specific action. An IANA registry is created in
Section 15.8.1 to contain the allowed values. Section 15.8.1 to contain the allowed values.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element acknowledges receipt of an eCall data object or The <ack> element acknowledges receipt of an eCall data object or
request. An <ack> element references the unique ID of the data request. An <ack> element references the Content-ID of the object
object being acknowledged. The PSAP MUST send an <ack> element being acknowledged. The PSAP MUST send an <ack> element
acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in
the INVITE); this <ack> element indicates if the PSAP considers the the INVITE); this <ack> element indicates if the PSAP considers the
MSD successfully received or not. An <ack> element is not sent for a MSD successfully received or not. An <ack> element is not sent for a
<capabilities> element. <capabilities> element.
The <ack> element has the following attributes: The <ack> element has the following attributes:
9.1.1.1. Attributes of the <ack> element 9.1.1.1. Attributes of the <ack> element
The <ack> element has the following attributes: The <ack> element has the following attributes:
Name: ref Name: ref
Usage: Mandatory Usage: Mandatory
Type: anyURI Type: anyURI
Direction: In this document, sent from the PSAP to the IVS Direction: Sent in either direction
Description: References the Content-ID of the body part being Description: References the Content-ID of the body part being
acknowledged. acknowledged.
Example: <ack received="true" ref="1234567890@atlanta.example.com"/> Example: <ack received="true" ref="1234567890@atlanta.example.com"/>
Name: received Name: received
Usage: Conditional: mandatory in an >ack< element sent by a PSAP Usage: Conditional: mandatory in an <ack> element sent by a PSAP
Type: Boolean Type: Boolean
Direction: In this document, sent from the PSAP to the IVS Direction: In this document, sent from the PSAP to the IVS
Description: Indicates if the referenced object was considered Description: Indicates if the referenced object was considered
successfully received or not. successfully received or not.
Example: <ack received="true" ref="1234567890@atlanta.example.com"/> Example: <ack received="true" ref="1234567890@atlanta.example.com"/>
9.1.1.2. Child Element of the <ack> element 9.1.1.2. Child Element of the <ack> element
For extensibility, the <ack> element has the following child element: For extensibility, the <ack> element has the following child element:
Name: actionResult Name: actionResult
Usage: Optional Usage: Optional
Direction: Provided for extension, sent from the IVS to the PSAP Direction: Sent from the IVS to the PSAP
Description: An <actionResult> element indicates the result of an Description: An <actionResult> element indicates the result of an
action (other than a 'send-data' action). When an <ack> element action (other than a successfully executed 'send-data' action).
is in response to a control object with multiple <request> The <ack> element contains an <actionResult> element for each
elements, the <ack> element contains an <actionResult> element for <request> element that is not a successfully executed 'send-data'
each <request> element that is not a 'send-data' action. The action. The <actionResult> element has the following attributes:
<actionResult> element has the following attributes:
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Direction: In this document, sent from the PSAP to the IVS
Description: Contains the value of the 'action' attribute of the Description: Contains the value of the 'action' attribute of the
<request> element <request> element
Name: success Name: success
Usage: Mandatory Usage: Mandatory
Type: Boolean Type: Boolean
Direction: Sent from the IVS to the PSAP
Description: Indicates if the action was successfully Description: Indicates if the action was successfully
accomplished accomplished
Name: reason Name: reason
Usage: Conditional Usage: Conditional
Type: token Type: token
Direction: Sent from the IVS to the PSAP
Description: Used when 'success' is "false", this attribute Description: Used when 'success' is "false", this attribute
contains a reason code for a failure. A registry for reason contains a reason code for a failure. A registry for reason
codes is defined in Section 15.8.2. codes is defined in Section 15.8.2.
Name: details Name: details
Usage: optional Usage: optional
Type: string Type: string
Direction: Sent from the IVS to the PSAP
Description: Contains further explanation of the circumstances of Description: Contains further explanation of the circumstances of
a success or failure. The contents are implementation-specific a success or failure. The contents are implementation-specific
and human-readable. and human-readable.
9.1.1.3. Ack Examples 9.1.1.3. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<emergencyCallData.control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
skipping to change at page 16, line 33 skipping to change at page 16, line 33
supported is to send an MSD. The following attributes and child supported is to send an MSD. The following attributes and child
elements are defined: elements are defined:
9.1.3.1. Attributes of the <request> element 9.1.3.1. Attributes of the <request> element
The <request> element has the following attributes: The <request> element has the following attributes:
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Direction: In this document, sent from the PSAP to the IVS; for Direction: Sent in either direction
extension, sent from the IVS to the PSAP
Description: Identifies the action that the vehicle is requested to Description: Identifies the action that the vehicle is requested to
perform. An IANA registry is established in Section 15.8.1 to perform (in a <request> element within a <capabilities> element,
contain the allowed values. indicates an action that the vehicle is capable of performing).
An IANA registry is established in Section 15.8.1 to contain the
allowed values.
Example: action="send-data" Example: action="send-data"
Name: msgid Name: msgid
Usage: Conditional Usage: Conditional
Type: int Type: int
Direction: Sent from the PSAP to the IVS Direction: Sent in either direction
Description: Defined for extensibility. Description: Defined for extensibility.
Example: msgid="3" Example: msgid="3"
Name: persistance Name: persistance
Usage: Optional Usage: Optional
Type: duration Type: duration
Direction: Sent from the PSAP to the IVS Direction: Sent in either direction
Description: Defined for extensibility. Specifies how long to carry Description: Defined for extensibility. Specifies how long to carry
on the specified action. If absent, the default is for the on the specified action. If absent, the default is for the
duration of the call. duration of the call.
Example: persistance="PT1H" Example: persistance="PT1H"
Name: datatype Name: datatype
Usage: Conditional Usage: Conditional
Type: token Type: token
Direction: In this document, sent from the PSAP to the IVS; as an Direction: Sent in either direction
extension, sent from the IVS to the PSAP
Description: Mandatory with a "send-data" action within a <request> Description: Mandatory with a "send-data" action within a <request>
element that is not within a <capabilities> element. Specifies element that is not within a <capabilities> element. Specifies
the data block that the IVS is requested to transmit, using the the data block that the IVS is requested to transmit, using the
same identifier as in the 'purpose' attribute set in a Call-Info same identifier as in the 'purpose' attribute set in a Call-Info
header field to point to the data block. Permitted values are header field to point to the data block. Permitted values are
contained in the 'Emergency Call Data Types' IANA registry contained in the 'Emergency Call Data Types' IANA registry
established in [RFC7852]. Only the "eCall.MSD" value is mandatory established in [RFC7852]. Only the "eCall.MSD" value is mandatory
to support. to support.
Example: datatype="eCall.MSD" Example: datatype="eCall.MSD"
skipping to change at page 20, line 7 skipping to change at page 20, line 7
10.4. Info Package Parameters 10.4. Info Package Parameters
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: The body for an emergencyCallData.eCall.MSD info package is a
multipart body. Zero or one application/
o an application/emergencyCallData.eCall.MSD+per (containing an emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or
MSD), or more application/emergencyCallData.control+xml (containing a
metadata/control object) parts are permitted. Intermediate multipart
o an application/emergencyCallData.control+xml (containing a body parts MAY appear.
metadata/control object), or
o a multipart body containing:
* zero or one application/emergencyCallData.eCall.MSD+per part
(containing an MSD),
* zero or more application/emergencyCallData.control+xml
(containing a metadata/control object),
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. If the body part header field at the top level of the SIP message. The body part has
is the only body part, it has a Content-Disposition header field a Content-Disposition header field set to "By-Reference".
value of "INFO-Package". If the body part is contained within a
multipart, it has a Content-Disposition header field value of "By-
Reference".
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
skipping to change at page 24, line 38 skipping to change at page 24, line 38
Content-Disposition: by-reference Content-Disposition: by-reference
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<emergencyCallData.control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:control"> "urn:ietf:params:xml:ns:EmergencyCallData:control">
<ack received="true" ref="1234567890@atlanta.example.com"/> <ack received="true" ref="1234567890@atlanta.example.com"/>
</emergencyCallData.control> </emergencyCallData.control>
--boundaryX-- --boundaryX--
Figure 9: 200 OK response to INVITE Figure 9: 200 OK response to INVITE
Figure 10 illustrates an INFO request containing an eCall metadata/ Figure 10 illustrates a SIP INFO request containing a metadata/
control block requesting an eCall MSD. (For simplicity, the example control block requesting an eCall MSD. (For simplicity, the example
does not show all SIP headers.) does not show all SIP headers.)
INFO sip:+13145551111@example.com SIP/2.0 INFO sip:+13145551111@example.com SIP/2.0
To: <sip:+13145551111@example.com>;tag=9fxced76sl To: <sip:+13145551111@example.com>;tag=9fxced76sl
From: Exemplar PSAP <urn:service:sos.ecall.automatic> From: Exemplar PSAP <urn:service:sos.ecall.automatic>
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <cid:3456789012@atlanta.example.com>; Call-Info: <cid:3456789012@atlanta.example.com>;
purpose=emergencyCallData.control purpose=emergencyCallData.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml, application/emergencyCallData.control+xml,
application/emergencyCallData.eCall.MSD+per application/emergencyCallData.eCall.MSD+per
CSeq: 41862 INFO CSeq: 41862 INFO
Info-Package: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Disposition: info-package Content-Type: multipart/mixed; boundary=boundaryZZZ
Content-Length: ...
--boundaryZZZ
Content-Disposition: by-reference
Content-Type: application/emergencyCallData.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <3456789012@atlanta.example.com> Content-ID: <3456789012@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<emergencyCallData.control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation= xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:control"> "urn:ietf:params:xml:ns:EmergencyCallData:control">
<request action="send-data" datatype="eCall.MSD"/> <request action="send-data" datatype="eCall.MSD"/>
</emergencyCallData.control> </emergencyCallData.control>
--boundaryZZZ--
Figure 10: INFO requesting MSD Figure 10: INFO requesting MSD
Figure 11 illustrates a SIP eCall INFO that contains an MSD. For Figure 11 illustrates a SIP INFO request containing an MSD. For
simplicity, the example does not show all SIP headers. Because the simplicity, the example does not show all SIP headers. Because the
MSD is encoded in ASN.1 PER, which is a binary encoding, its contents MSD is encoded in ASN.1 PER, which is a binary encoding, its contents
cannot be included in a text document. cannot be included in a text document.
INFO urn:service:sos.ecall.automatic SIP/2.0 INFO urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <cid:4567890123@atlanta.example.com>; Call-Info: <cid:4567890123@atlanta.example.com>;
purpose=emergencyCallData.eCall.MSD purpose=emergencyCallData.eCall.MSD
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.control+xml application/emergencyCallData.control+xml
CSeq: 51862 INFO CSeq: 51862 INFO
Info-Package: emergencyCallData.eCall.MSD Info-Package: emergencyCallData.eCall.MSD
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundaryLine
Content-Length: ...
--boundaryLine
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: <4567890123@atlanta.example.com> Content-ID: <4567890123@atlanta.example.com>
Content-Disposition: info-package Content-Disposition: by-reference
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundaryLine--
Figure 11: INFO containing MSD Figure 11: INFO containing MSD
12. Security Considerations 12. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] apply here.
In addition to any network-provided location (which might be In addition to any network-provided location (which might be
determined solely by the network, or in cooperation with or possibly determined solely by the network, or in cooperation with or possibly
entirely by the originating device), an eCall carries an IVS-supplied entirely by the originating device), an eCall carries an IVS-supplied
location within the MSD. This is likely to be useful to the PSAP, location within the MSD. This is likely to be useful to the PSAP,
skipping to change at page 38, line 16 skipping to change at page 38, line 16
Brian Rosen was a co-author of the original document upon which this Brian Rosen was a co-author of the original document upon which this
document is based. document is based.
17. Acknowledgements 17. Acknowledgements
We would like to thank Bob Williams and Ban Al-Bakri for their We would like to thank Bob Williams and Ban Al-Bakri for their
feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith
Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and
James Winterbottom for their review and comments; Robert Sparks and James Winterbottom for their review and comments; Robert Sparks and
Paul Kyzivat for their help with the SIP mechanisms. We would like Paul Kyzivat for their help with the SIP mechanisms; Mark Baker and
to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and Ned Freed for their help with the media subtype registration issue.
Ulrich Dietz for their help with the original document upon which We would like to thank Michael Montag, Arnoud van Wijk, Gunnar
this document is based. Hellstrom, and Ulrich Dietz for their help with the original document
upon which this document is based.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-13 to draft-ietf-14 18.1. Changes from draft-ietf-14 to draft-ietf-15
o eCall body parts now always sent enclosed in multipart (even if
only body part in SIP message) and hence always have a Content-
Disposition of By-Reference
o Fixed errors in attribute directionality text
o Fixed typos.
18.2. 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.2. Changes from draft-ietf-12 to draft-ietf-13 18.3. 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.3. Changes from draft-ietf-11 to draft-ietf-12 18.4. 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.4. Changes from draft-ietf-09 to draft-ietf-11 18.5. 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.5. Changes from draft-ietf-08 to draft-ietf-09 18.6. 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
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.6. Changes from draft-ietf-07 to draft-ietf-08 18.7. 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 39, line 44 skipping to change at page 40, line 4
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]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
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.7. Changes from draft-ietf-06 to draft-ietf-07 18.8. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.8. Changes from draft-ietf-05 to draft-ietf-06 18.9. 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.9. Changes from draft-ietf-04 to draft-ietf-05 18.10. 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.10. Changes from draft-ietf-03 to draft-ietf-04 18.11. 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.11. Changes from draft-ietf-02 to draft-ietf-03 18.12. 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.12. Changes from draft-ietf-01 to draft-ietf-02 18.13. 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.13. Changes from draft-ietf-00 to draft-ietf-01 18.14. 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 content type for the control o Added IANA registration for the MIME content 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.14. Changes from draft-gellens-03 to draft-ietf-00 18.15. 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.15. Changes from draft-gellens-02 to -03 18.16. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.16. Changes from draft-gellens-01 to -02 18.17. 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.17. Changes from draft-gellens-00 to -01 18.18. 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. 64 change blocks. 
129 lines changed or deleted 132 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/