< draft-ietf-ecrit-ecall-17.txt   draft-ietf-ecrit-ecall-18.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 19, 2017 Individual Expires: April 20, 2017 Individual
October 16, 2016 October 17, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-17.txt draft-ietf-ecrit-ecall-18.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.
This document also registers MIME Content Types and an Emergency Call This document also registers MIME media types and an Emergency Call
Additional Data Block for the eCall vehicle data and metadata/control Additional Data Block for the eCall vehicle data and metadata/control
data, and an INFO package to enable carrying this data in INFO data, and an INFO package to enable carrying this data in INFO
requests. requests.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 19, 2017. This Internet-Draft will expire on April 20, 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 43 skipping to change at page 2, line 43
9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15 9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15
9.1.3. The <request> element . . . . . . . . . . . . . . . . 16 9.1.3. The <request> element . . . . . . . . . . . . . . . . 16
9.1.3.1. Attributes of the <request> element . . . . . . . 16 9.1.3.1. Attributes of the <request> element . . . . . . . 16
9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18
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 . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . 21 10.10. Implementation Details . . . . . . . . . . . . . . . . . 20
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 Content-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 Content-type Registration for 15.3. MIME Media 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-16 to draft-ietf-17 . . . . . . 38 18.1. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38
18.2. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38 18.2. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38
18.3. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 18.3. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38
18.4. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38 18.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38
18.5. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38 18.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 39
18.6. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39 18.6. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 39
18.7. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39 18.7. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39
18.8. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 18.8. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39
18.9. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 18.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39
18.10. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 18.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 40
18.11. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40 18.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40
18.12. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40 18.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40
18.13. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40 18.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40
18.14. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41 18.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 41
18.15. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41 18.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41
18.16. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41 18.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41
18.17. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41 18.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41
18.18. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42 18.18. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41
18.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42 18.19. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42
18.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42 18.20. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42
18.21. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . 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].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
skipping to change at page 6, line 39 skipping to change at page 6, line 39
A transition period will exist during which time the various entities A transition period will exist during which time the various entities
involved in initiating and handling an eCall might support next- involved in initiating and handling an eCall might support next-
generation eCall, legacy eCall, or both. The issues of migration and generation eCall, legacy eCall, or both. The issues of migration and
co-existence during the transition period are outside the scope of co-existence during the transition period are outside the scope of
this document. this document.
This document indicates how to use IP-based emergency services This document indicates how to use IP-based emergency services
mechanisms to support next-generation eCall. mechanisms to support next-generation eCall.
This document also registers MIME Content Types and an Emergency Call This document also registers MIME media types and an Emergency Call
Additional Data Block for the eCall vehicle data (MSD) and metadata/ Additional Data Block for the eCall vehicle data (MSD) and metadata/
control data, and an INFO package to enable carrying this data in control data, and an INFO package to enable carrying this data in
INFO requests. INFO requests.
The MSD is carried in the MIME type 'application/ The MSD is carried in the MIME type 'application/
emergencyCallData.eCall.MSD+per' and the metadata/control block is emergencyCallData.eCall.MSD+per' and the metadata/control block is
carried in the MIME type 'application/emergencyCallData.control+xml' carried in the MIME type 'application/emergencyCallData.control+xml'
(both of which are registered in Section 15) An INFO package is (both of which are registered in Section 15) An INFO package is
defined (in Section 10) to enable these MIME types to be carried in defined (in Section 10) to enable these MIME types to be carried in
SIP INFO requests, per [RFC6086]. SIP INFO requests, per [RFC6086].
4. eCall Requirements 4. eCall Requirements
eCall requirements are specified by CEN in [EN_16072] and by 3GPP in eCall requirements are specified by CEN in [EN_16072] and by 3GPP in
[TS22.101] clauses 10.7 and A.27. Requirements specific to vehicle [TS22.101] clauses 10.7 and A.27 and [TS24.229] section 4.7.6.
data are contained in EN 15722 [msd]. Requirements specific to vehicle data are contained in EN 15722
[msd].
5. Vehicle Data 5. Vehicle Data
Pan-European eCall provides a standardized and mandated set of Pan-European eCall provides a standardized and mandated set of
vehicle related data, known as the Minimum Set of Data (MSD). The vehicle related data, known as the Minimum Set of Data (MSD). The
European Committee for Standardization (CEN) has specified this data European Committee for Standardization (CEN) has specified this data
in EN 15722 [msd], along with both ASN.1 and XML encodings. Both in EN 15722 [msd], along with both ASN.1 and XML encodings. Both
circuit-switched eCall and this document use the ASN.1 PER encoding, circuit-switched eCall and this document use the ASN.1 PER encoding,
which is specified in Annex A of EN 15722 [msd] (the XML encoding which is specified in Annex A of EN 15722 [msd] (the XML encoding
specified in Annex C is not used in this document). specified in Annex C is not used in this document).
This document registers the 'application/ This document registers the 'application/
emergencyCallData.eCall.MSD+per' MIME Content-Type to enable the MSD emergencyCallData.eCall.MSD+per' MIME media type to enable the MSD to
to be carried in SIP. As an ASN.1 PER encoded object, the data is be carried in SIP. As an ASN.1 PER encoded object, the data is
binary and transported using binary content transfer encoding within binary and transported using binary content transfer encoding within
SIP messages. This document also adds the 'eCall.MSD' entry to the SIP messages. This document also adds the 'eCall.MSD' entry to the
Emergency Call Additional Data Blocks registry to enable the MSD to Emergency Call Additional Data Blocks registry to enable the MSD to
be recognized as such in a SIP-based eCall emergency call. (See be recognized as such in a SIP-based eCall emergency call. (See
[RFC7852] for more information about the registry and how it is [RFC7852] for more information about the registry and how it is
used.) used.)
See Section 6 for a discussion of how the MSD vehicle data is See Section 6 for a discussion of how the MSD vehicle data is
conveyed in an NG-eCall. conveyed in an NG-eCall.
skipping to change at page 7, line 52 skipping to change at page 8, line 4
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 an 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 media 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
the eCall MSD per the Emergency Call Additional Data Blocks registry the eCall MSD per the Emergency Call Additional Data Blocks registry
entry; the 'purpose' parameter's value is entry; the 'purpose' parameter's value is
'emergencyCallData.eCall.MSD'. Per [RFC6086], an MSD is carried in a 'emergencyCallData.eCall.MSD'. Per [RFC6086], an MSD is carried in a
SIP INFO request by using the INFO package defined in Section 10. SIP INFO request by using the INFO package defined in Section 10.
A PSAP or IVS transmits a metadata/control object (see Section 9) by A PSAP or IVS transmits a metadata/control object (see Section 9) by
encoding it per the description in this document and attaching it to encoding it per the description in this document and attaching it to
a SIP message as a MIME body part per [RFC7852]. The body part is a SIP message as a MIME body part per [RFC7852]. The body part is
identified by its MIME content-type ('application/ identified by its MIME media type ('application/
emergencyCallData.control+xml') in the Content-Type header field of emergencyCallData.control+xml') 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 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
skipping to change at page 11, line 49 skipping to change at page 11, line 49
to the IVS and the IVS to respond. INFO requests are sent using an to the IVS and the IVS to respond. INFO requests are sent using an
appropriate INFO Package. See Section 6 for more information on appropriate INFO Package. See Section 6 for more information on
attaching a metadata/control block to a SIP message. See Section 10 attaching a metadata/control block to a SIP message. See Section 10
for information about the use of INFO requests to carry data within for information about the use of INFO requests to carry data within
an eCall. an eCall.
When the IVS includes an unsolicited MSD in a SIP request (e.g., the When the IVS includes an unsolicited MSD in a SIP request (e.g., the
initial INVITE), the PSAP sends a metadata/control block indicating initial INVITE), the PSAP sends a metadata/control block indicating
successful/unsuccessful receipt of the MSD in the SIP response to the successful/unsuccessful receipt of the MSD in the SIP response to the
request. This also informs the IVS that an NG-eCall is in operation. request. This also informs the IVS that an NG-eCall is in operation.
If the IVS receives a SIP response without the metadata/control If the IVS receives a SIP final response without the metadata/control
block, it indicates that the SIP dialog is not an NG-eCall (e.g., block, it indicates that the SIP dialog is not an NG-eCall (e.g.,
some part of the call is being handled as a legacy call). When the some part of the call is being handled as a legacy call). When the
IVS sends a solicited MSD (e.g., in a SIP INFO request sent following IVS sends a solicited MSD (e.g., in a SIP INFO request sent following
receipt of a SIP INFO request containing a metadata/control block receipt of a SIP INFO request containing a metadata/control block
requesting an MSD), the PSAP does not send a metadata/control block requesting an MSD), the PSAP does not send a metadata/control block
indicating successful or unsuccessful receipt of the MSD. (Normal indicating successful or unsuccessful receipt of the MSD. (Normal
SIP retransmission handles non-receipt of requested data; note that, SIP retransmission handles non-receipt of requested data; note that,
per [RFC6086], a 200 OK response to an INFO request indicates only per [RFC6086], a 200 OK response to an INFO request indicates only
that the receiver has successfully received and accepted the INFO that the receiver has successfully received and accepted the INFO
request, it says nothing about the acceptability of the payload.) If request, it says nothing about the acceptability of the payload.) If
skipping to change at page 12, line 47 skipping to change at page 12, line 47
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 content 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 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.
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
skipping to change at page 15, line 10 skipping to change at page 15, line 10
Type: string Type: string
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=
"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>
Figure 3: Ack Example from PSAP to IVS Figure 3: Ack Example from PSAP to IVS
9.1.2. The <capabilities> element 9.1.2. The <capabilities> element
The <capabilities> element is transmitted by the IVS to indicate to The <capabilities> element is transmitted by the IVS to indicate to
skipping to change at page 16, line 4 skipping to change at page 16, line 4
Examples: Examples:
<request action="send-data" supported-values="eCall.MSD" /> <request action="send-data" supported-values="eCall.MSD" />
It is OPTIONAL for the IVS to support the <capabilities> element. If It is OPTIONAL for the IVS to support the <capabilities> element. If
the IVS does not send a <capabilities> element, this indicates that the IVS does not send a <capabilities> element, this indicates that
the only <request> action supported by the IVS is 'send-data' with the only <request> action supported by the IVS is 'send-data' with
'datatype' set to 'eCall.MSD'. 'datatype' set to 'eCall.MSD'.
9.1.2.2. Capabilities Example 9.1.2.2. Capabilities Example
<?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="urn:ietf:params:xml:ns:EmergencyCallData:control">
<capabilities> <capabilities>
<request action="send-data" supported-values="eCall.MSD"/> <request action="send-data" supported-values="eCall.MSD"/>
</capabilities> </capabilities>
</EmergencyCallData.Control> </EmergencyCallData.Control>
Figure 4: Capabilities Example Figure 4: Capabilities Example
9.1.3. The <request> element 9.1.3. The <request> element
A <request> element appears one or more times on its own or as a A <request> element appears one or more times on its own or as a
child of a <capabilities> element. It allows the PSAP to request child of a <capabilities> element. It allows the PSAP to request
that the IVS perform an action. The only action that MUST be that the IVS perform an action. The only action that MUST be
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:
skipping to change at page 18, line 10 skipping to change at page 18, line 10
Type: token Type: token
Direction: Sent from the PSAP to the IVS Direction: Sent from the PSAP to the IVS
Description: Defined for extension. Identifies the element to be Description: Defined for extension. Identifies the element to be
acted on. Permitted values depend on the request type. acted on. Permitted values depend on the request type.
9.1.3.2. Request Example 9.1.3.2. Request Example
<?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=
"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>
Figure 5: Request Example Figure 5: Request Example
10. The emergencyCallData.eCall.MSD INFO package 10. The emergencyCallData.eCall.MSD INFO package
This document registers the 'emergencyCallData.eCall.MSD' INFO This document registers the 'emergencyCallData.eCall.MSD' INFO
skipping to change at page 20, line 8 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 which MAY contain zero or one application/ multipart body containing zero or one application/
emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or
more application/emergencyCallData.control+xml (containing a more application/emergencyCallData.control+xml (containing a
metadata/control object) parts. metadata/control object) parts. At least one MSD or metadata/control
body part is expected; the behavior upon receiving 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 43 skipping to change at page 20, line 38
10.8. Rate of INFO Requests 10.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The rate of SIP INFO requests associated with the
emergencyCallData.eCall.MSD info package is normally quite low (most emergencyCallData.eCall.MSD info package is normally quite low (most
dialogs are likely to contain zero INFO requests, while others can be dialogs are likely to contain zero INFO requests, while others can be
expected to carry an occasional request). expected to carry an occasional request).
10.9. Info Package Security Considerations 10.9. Info Package Security Considerations
The MIME content 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.
10.10. Implementation Details 10.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
skipping to change at page 23, line 28 skipping to change at page 23, line 28
SUBSCRIBE, NOTIFY, UPDATE SUBSCRIBE, NOTIFY, UPDATE
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundary1 --boundary1
Content-Type: application/pidf+xml
Content-ID: <target123@example.com>
Content-Disposition: by-reference;handling=optional
...PIDF-LO goes in here
--boundary1
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundary1-- --boundary1--
Figure 8: SIP NG-eCall INVITE Figure 8: SIP NG-eCall INVITE
Continuing the example, Figure 9 illustrates a SIP 200 OK response to Continuing the example, Figure 9 illustrates a SIP 200 OK response to
the INVITE of Figure 8, containing a control block acknowledging the INVITE of Figure 8, containing a control block acknowledging
successful receipt of the eCall MSD. (For simplicity, the example successful receipt of the eCall MSD. (For simplicity, the example
does not show all SIP headers.) does not show all SIP headers.)
SIP/2.0 200 OK SIP/2.0 200 OK
To: <sip:+13145551111@example.com>;tag=9fxced76sl To: urn:service:sos.ecall.automatic;tag=8gydfe65t0
From: Exemplar PSAP <urn:service:sos.ecall.automatic> From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <cid:2345678901@atlanta.example.com>; Call-Info: <cid:2345678901@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: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall.MSD Recv-Info: 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
skipping to change at page 24, line 33 skipping to change at page 24, line 33
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundaryX --boundaryX
Content-Type: application/emergencyCallData.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <2345678901@atlanta.example.com> Content-ID: <2345678901@atlanta.example.com>
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=
"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 a SIP INFO request containing a 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>;tag=8gydfe65t0
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, CSeq: 41862 INFO
application/emergencyCallData.control+xml, Info-Package: emergencyCallData.eCall.MSD
application/emergencyCallData.eCall.MSD+per Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE,
CSeq: 41862 INFO SUBSCRIBE, NOTIFY, UPDATE
Info-Package: emergencyCallData.eCall.MSD Content-Type: multipart/mixed; boundary=boundaryZZZ
Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, Content-Dispositio: Info-Package
SUBSCRIBE, NOTIFY, UPDATE Content-Length: ...
Content-Type: multipart/mixed; boundary=boundaryZZZ
Content-Dispositio: Info-Package
Content-Length: ...
--boundaryZZZ --boundaryZZZ
Content-Disposition: by-reference 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=
"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-- --boundaryZZZ--
Figure 10: INFO requesting MSD Figure 10: INFO requesting MSD
Figure 11 illustrates a SIP INFO request containing 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;tag=8gydfe65t0
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,
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-Type: multipart/mixed; boundary=boundaryLine
Content-Disposition: Info-Package Content-Disposition: Info-Package
Content-Length: ... Content-Length: ...
--boundaryLine --boundaryLine
Content-Type: application/emergencyCallData.eCall.MSD+per Content-Type: application/emergencyCallData.eCall.MSD+per
skipping to change at page 28, line 22 skipping to change at page 28, line 22
<![CDATA[ <![CDATA[
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace">
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
<xs:element name="EmergencyCallData.control" <xs:element name="EmergencyCallData.control"
type="pi:controlType"/> type="pi:controlType"/>
<xs:complexType name="controlType"> <xs:complexType name="controlType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:choice> <xs:choice>
<xs:element name="capabilities" <xs:element name="capabilities"
type="pi:capabilitiesType"/> type="pi:capabilitiesType"/>
skipping to change at page 31, line 6 skipping to change at page 31, line 4
IANA is requested to register the URN 'urn:service:sos.ecall' under IANA is requested to register the URN 'urn:service:sos.ecall' under
the sub-services 'sos' registry defined in Section 4.2 of [RFC5031]. the sub-services 'sos' registry defined in Section 4.2 of [RFC5031].
This service requests resources associated with an emergency call This service requests resources associated with an emergency call
placed by an in-vehicle system, carrying a standardized set of data placed by an in-vehicle system, carrying a standardized set of data
related to the vehicle and incident. Two sub-services are registered related to the vehicle and incident. Two sub-services are registered
as well: as well:
urn:service:sos.ecall.manual urn:service:sos.ecall.manual
Used with an eCall invoked due to manual interaction by a vehicle Used with an eCall invoked due to manual interaction by a vehicle
occupant. occupant.
urn:service:sos.ecall.automatic urn:service:sos.ecall.automatic
Used with an eCall invoked automatically, for example, due to a Used with an eCall invoked automatically, for example, due to a
crash or other serious incident. crash or other serious incident.
IANA is also requested to register the URN IANA is also requested to register the URN
'urn:service:test.sos.ecall' under the sub-service 'test' registry 'urn:service:test.sos.ecall' under the sub-service 'test' registry
defined in Setcion 17.2 of [RFC6881]. defined in Setcion 17.2 of [RFC6881].
15.2. MIME Content-type Registration for 'application/ 15.2. MIME Media Type Registration for 'application/
emergencyCallData.eCall.MSD+per' emergencyCallData.eCall.MSD+per'
IANA is requested to add application/emergencyCallData.eCall.MSD+per IANA is requested to add application/emergencyCallData.eCall.MSD+per
as a MIME content type, with a reference to this document, in as a MIME media type, with a reference to this document, in
accordance to the procedures of RFC 6838 [RFC6838] and guidelines in accordance to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.MSD+per MIME subtype name: emergencyCallData.eCall.MSD+per
Mandatory parameters: none Mandatory parameters: none
Optional parameters: none Optional parameters: none
skipping to change at page 32, line 4 skipping to change at page 31, line 50
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.
Interoperability considerations: None Interoperability considerations: None
Published specification: Annex A of EN 15722 [msd]
Published specification: Annex A of EN 15722 [msd]
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: None File Extension: None
Macintosh file type code: 'BINA' Macintosh file type code: 'BINA'
skipping to change at page 32, line 29 skipping to change at page 32, line 27
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: The MSD specification was produced by the European Author: The MSD specification was produced by the European
Committee For Standardization (CEN). For contact information, Committee For Standardization (CEN). For contact information,
please see <http://www.cen.eu/cen/Pages/contactus.aspx>. please see <http://www.cen.eu/cen/Pages/contactus.aspx>.
Change controller: The European Committee For Standardization Change controller: The European Committee For Standardization
(CEN) (CEN)
15.3. MIME Content-type Registration for 'application/ 15.3. MIME Media Type Registration for 'application/
emergencyCallData.control+xml' emergencyCallData.control+xml'
IANA is requested to add application/emergencyCallData.control+xml as IANA is requested to add application/emergencyCallData.control+xml as
a MIME content type, with a reference to this document, in accordance a MIME media type, with a reference to this document, in accordance
to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303 to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303
[RFC7303]. [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.control+xml MIME subtype name: emergencyCallData.control+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
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-16 to draft-ietf-17 18.1. Changes from draft-ietf-17 to draft-ietf-18
o Added reference to 3GPP TS24.229
o Clarified that an INFO request is expected to have at least one
MSD or metadata/control body part
o Fixed minor errors in examples
o Corrected "content type" to "media type"
o Deleted "xsi:schemaLocation" from examples
18.2. 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.2. Changes from draft-ietf-15 to draft-ietf-16 18.3. 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.3. Changes from draft-ietf-14 to draft-ietf-15 18.4. 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.4. Changes from draft-ietf-13 to draft-ietf-14 18.5. 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.5. Changes from draft-ietf-12 to draft-ietf-13 18.6. 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.6. Changes from draft-ietf-11 to draft-ietf-12 18.7. 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.7. Changes from draft-ietf-09 to draft-ietf-11 18.8. 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.8. Changes from draft-ietf-08 to draft-ietf-09 18.9. 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 39, line 42 skipping to change at page 40, line 4
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.9. Changes from draft-ietf-07 to draft-ietf-08 18.10. 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]
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.10. Changes from draft-ietf-06 to draft-ietf-07 18.11. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.11. Changes from draft-ietf-05 to draft-ietf-06 18.12. 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.12. Changes from draft-ietf-04 to draft-ietf-05 18.13. 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.13. Changes from draft-ietf-03 to draft-ietf-04 18.14. 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.14. Changes from draft-ietf-02 to draft-ietf-03 18.15. 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.15. Changes from draft-ietf-01 to draft-ietf-02 18.16. 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.16. Changes from draft-ietf-00 to draft-ietf-01 18.17. 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 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.17. Changes from draft-gellens-03 to draft-ietf-00 18.18. 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.18. Changes from draft-gellens-02 to -03 18.19. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.19. Changes from draft-gellens-01 to -02 18.20. 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.20. Changes from draft-gellens-00 to -01 18.21. 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
skipping to change at page 43, line 47 skipping to change at page 43, line 52
principles". principles".
19.2. Informative references 19.2. Informative references
[CEN] "European Committee for Standardization", [CEN] "European Committee for Standardization",
<http://www.cen.eu>. <http://www.cen.eu>.
[I-D.ietf-ecrit-car-crash] [I-D.ietf-ecrit-car-crash]
Gellens, R., Rosen, B., and H. Tschofenig, "Next- Gellens, R., Rosen, B., and H. Tschofenig, "Next-
Generation Vehicle-Initiated Emergency Calls", draft-ietf- Generation Vehicle-Initiated Emergency Calls", draft-ietf-
ecrit-car-crash-12 (work in progress), September 2016. ecrit-car-crash-16 (work in progress), October 2016.
[MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for [MSG_TR] ETSI, , "ETSI Mobile Standards Group (MSG); eCall for
VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04), VoIP", ETSI Technical Report TR 103 140 V1.1.1 (2014-04),
April 2014. April 2014.
[RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, DOI 10.17487/RFC5012, January 2008, RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>. <http://www.rfc-editor.org/info/rfc5012>.
skipping to change at page 44, line 42 skipping to change at page 44, line 46
<http://www.3gpp.org/>. <http://www.3gpp.org/>.
[SDO-ETSI] [SDO-ETSI]
"European Telecommunications Standards Institute (ETSI)", "European Telecommunications Standards Institute (ETSI)",
<http://www.etsi.org>. <http://www.etsi.org>.
[TS23.167] [TS23.167]
3GPP, , "3GPP TS 23.167: IP Multimedia Subsystem (IMS) 3GPP, , "3GPP TS 23.167: IP Multimedia Subsystem (IMS)
emergency sessions". emergency sessions".
[TS24.229]
3GPP, , "3GPP TS 24.229: IP multimedia call control
protocol based on Session Initiation Protocol (SIP) and
Session Description Protocol (SDP); Stage 3".
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Core Technology Consulting Core Technology Consulting
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Hannes Tschofenig Hannes Tschofenig
Individual Individual
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
 End of changes. 71 change blocks. 
126 lines changed or deleted 136 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/