< draft-ietf-ecrit-ecall-12.txt   draft-ietf-ecrit-ecall-13.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: March 25, 2017 Individual Expires: March 26, 2017 Individual
September 21, 2016 September 22, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-12.txt draft-ietf-ecrit-ecall-13.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 March 25, 2017. This Internet-Draft will expire on March 26, 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 23 skipping to change at page 2, line 23
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 10 9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 10
9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 12 9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 12
9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 13 9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 13
9.1.1.1. Attributes of the <ack> element . . . . . . . . . 13 9.1.1.1. Attributes of the <ack> element . . . . . . . . . 13
9.1.1.2. Child Element of the <ack> element . . . . . . . 13 9.1.1.2. Child Element of the <ack> element . . . . . . . 13
9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 14 9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 14
9.1.2. The <capabilities> element . . . . . . . . . . . . . 15 9.1.2. The <capabilities> element . . . . . . . . . . . . . 15
9.1.2.1. Child Elements of the <capabilities> element . . 15 9.1.2.1. Child Elements of the <capabilities> element . . 15
9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15 9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 15
9.1.3. The <request> element . . . . . . . . . . . . . . . . 15 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 . . . . . . . . . . . . . . . . . 17 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18
10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 17 10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18
10.1. Overall Description . . . . . . . . . . . . . . . . . . 18 10.1. Overall Description . . . . . . . . . . . . . . . . . . 18
10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 18 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 Message Body Parts . . . . . . . . . . . . . . . . 19 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 . . . . . . . . . . . . . . . . . 20 10.10. Implementation Details . . . . . . . . . . . . . . . . . 21
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 20 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 20 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 . . . . . . . . . . . . . . . . . . . . . . . . . 27
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.eCall.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 . . . . . . . . . . 33 Call Additional Data Blocks registry . . . . . . . . . . 33
15.5. Registration of the 'eCall.control' entry in the 15.5. Registration of the 'control' entry in the Emergency
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 15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35
urn:ietf:params:xml:ns:eCall:control . . . . . . . . 35
15.8. Registry creation . . . . . . . . . . . . . . . . . . . 35 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 35
15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 35 15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 35
15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 36 15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 36
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 37
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
18. Changes from Previous Versions . . . . . . . . . . . . . . . 37 18. Changes from Previous Versions . . . . . . . . . . . . . . . 37
18.1. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 37 18.1. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 37
18.2. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 38 18.2. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 38
18.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 18.3. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 38
18.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 18.4. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
18.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39 18.5. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
18.6. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39 18.6. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39
18.7. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39 18.7. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39
18.8. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 18.8. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
18.9. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 18.9. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
18.10. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 18.10. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
18.11. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40 18.11. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40
18.12. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 40 18.12. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40
18.13. Changes from draft-gellens-02 to -03 . . . . . . . . . . 40 18.13. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 40
18.14. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40 18.14. Changes from draft-gellens-02 to -03 . . . . . . . . . . 40
18.15. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40 18.15. Changes from draft-gellens-01 to -02 . . . . . . . . . . 41
18.16. Changes from draft-gellens-00 to -01 . . . . . . . . . . 41
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
19.1. Normative References . . . . . . . . . . . . . . . . . . 41 19.1. Normative References . . . . . . . . . . . . . . . . . . 41
19.2. Informative references . . . . . . . . . . . . . . . . . 42 19.2. Informative references . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
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 6, line 25 skipping to change at page 6, line 25
Services (MMES). Services (MMES).
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.
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/ carried in the MIME type 'application/emergencyCallData.control+xml'
emergencyCallData.eCall.control+xml' (both of which are registered in (both of which are registered in Section 15) An INFO package is
Section 15) An INFO package is defined (in Section 10) to enable defined (in Section 10) to enable these MIME types to be carried in
these MIME types to be carried in INFO messages. 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. Requirements specific to vehicle
data are contained in EN 15722 [msd]. 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
skipping to change at page 7, line 18 skipping to change at page 7, line 18
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.
6. Data Transport 6. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of [RFC7852] establishes a general mechanism for attaching blocks of
data to a SIP emergency call. This mechanism permits certain data to a SIP emergency call. This mechanism permits certain
emergency call MIME types to be attached to SIP messages. This emergency call MIME types to be attached to SIP messages. This
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 INFO messages. to be carried in SIP INFO requests (per [RFC6086], new INFO usages
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 the 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
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'. The body part has a Content- 'emergencyCallData.eCall.MSD'. Per [RFC6086], an MSD is carried in a
Disposition header field value of "By-Reference; handling=optional". SIP INFO request by using the INFO package defined in Section 10.
An MSD is carried in an INFO message by using the INFO package
registration (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 content-type ('application/
emergencyCallData.eCall.control+xml') in the Content-Type header emergencyCallData.control+xml') in the Content-Type header field of
field of the body part. The body part is assigned a unique the body part. The body part is assigned a unique identifier which
identifier which is listed in a Content-ID header field in the body is listed in a Content-ID header field in the body part. The SIP
part. The SIP message is marked as containing the metadata/control message is marked as containing the metadata/control object by adding
object by adding (or appending to) a Call-Info header field at the (or appending to) a Call-Info header field at the top level of the
top level of the SIP message. This Call-Info header field contains a SIP message. This Call-Info header field contains a CID URL
CID URL referencing the body part's unique identifier, and a referencing the body part's unique identifier, and a 'purpose'
'purpose' parameter identifying the data as an eCall metadata/control parameter identifying the data as an eCall metadata/control block per
block per the Emergency Call Additional Data Blocks registry entry; the Emergency Call Additional Data Blocks registry entry; the
the 'purpose' parameter's value is 'emergencyCallData.eCall.control'. 'purpose' parameter's value is 'emergencyCallData.control'. Per
The body part has a Content-Disposition header field value of "By- [RFC6086], a metadata/control object is carried in a SIP INFO request
Reference; handling=optional". A metadata/control object is carried by using the INFO package defined in Section 10.
in an INFO message by using the INFO package registration (defined in
Section 10).
As is standard practice, if an MSD or a metadata/control block is As is necessary with message bodies, if an MSD or a metadata/control
sent in the same message with another body part, a multipart/mixed block is sent in the same message with another body part, a
body part encloses all body parts. multipart/mixed body part encloses all body parts. In some cases,
there are intermediate multipart body parts between the top level
multipart/mixed and the body part containing the MSD or metadata/
control object.
A body part containing an MSD or metadata/control object has a
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 the 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 PSAP creates a metadata/ informing the PSAP of its capabilities. The MSD body part (and
control object acknowledging receipt of the MSD and attaches it to metadata/control and PIDF-LO body parts if included) have a Content-
the SIP final response to the INVITE. The metadata/control object is Disposition header field with the value "By-Reference;
not attached to provisional (e.g., 180) responses. handling=optional". Specifying handling=optional prevents the INVITE
from being rejected if it is processed by a legacy element (e.g., a
gateway between SIP and circuit-switched environments) that does not
understand the MSD (or metadata/control object or PIDF-LO). The PSAP
creates a metadata/control object acknowledging receipt of the MSD
and attaches it to the SIP final response to the INVITE. The
metadata/control object is not attached to provisional (e.g., 180)
responses.
If the IVS receives an acknowledgment for an MSD with received=false, If the IVS receives an acknowledgment for an MSD with received=false,
it indicates some fault with the transfer of the MSD, the MSD it indicates some fault with the transfer of the MSD, the MSD
content, or the PSAP's ability to properly receive, decode and act on content, or the PSAP's ability to properly receive, decode and act on
the MSD. The IVS action is not defined (e.g., it might only log an the MSD. The IVS action is not defined (e.g., it might only log an
error). Since the PSAP is able to request an updated MSD during the error). Since the PSAP is able to request an updated MSD during the
call, if an initial MSD is unsatisfactory in any way, the PSAP can call, if an initial MSD is unsatisfactory in 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 message which it requesting an MSD and attaches it to a SIP INFO request and sends it
sends within the dialog. The IVS then attaches an updated MSD to a within the dialog. The IVS then attaches an updated MSD to a SIP
SIP INFO message and sends it within the dialog. The metadata/ INFO request and sends it within the dialog. If the IVS is unable to
control object and the MSD are both associated with the INFO package send an MSD, it instead sends a metadata/control object acknowledging
registered by this document, and hence sent with normal INFO the request with the 'success' parameter set to 'false' and a
semantics. In addition, for consistency with the way an MSD or 'reason' parameter (and optionally a 'details' parameter) indicating
metadata/control block is transmitted in a non-INFO message, one or why the request cannot be accomplished. Per [RFC6086], metadata/
more Call-Info header fields are included in the INFO message to control objects and MSDs are sent using the INFO package defined in
reference the MSD or metadata/control block. If the body part Section 10 . In addition, to align with how an MSD or metadata/
containing the MSD or metadata/control block is the only body part, control block is transmitted in a SIP message other than an INFO
it has a Content-Disposition header field value of "Info-Package; request, one or more Call-Info header fields are included in the SIP
handling=optional". If it is contained within a multipart body part, INFO request to reference the MSD or metadata/control block. See
it has a Content-Disposition header field value of "By-Reference; Section 10 for information about the use of INFO requests to carry
handling=optional". See Section 10 for information about the use of data within an eCall.
INFO messages to carry data within an eCall.
The IVS is not expected to send an unsolicited MSD during the call. The IVS is not expected to send an unsolicited MSD during the call.
Indicating "handling=optional" in the Content-Disposition header
field value protects the body part from being discarded by
intermediate entities that do not support it.
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
flag and routes the call to an eCall-capable PSAP; vehicle data is flag and routes the call to an eCall-capable PSAP; vehicle data is
skipping to change at page 10, line 49 skipping to change at page 11, line 8
This document defines a block of metadata/control data as an XML This document defines a block of metadata/control data as an XML
structure containing elements used for eCall and other vehicle- structure containing elements used for eCall and other vehicle-
initiated emergency call systems (i.e., in other regions) and initiated emergency call systems (i.e., in other regions) and
extension points. (This metadata/control block is in effect a high- extension points. (This metadata/control block is in effect a high-
level protocol between the PSAP and IVS.) When the PSAP sends an level protocol between the PSAP and IVS.) When the PSAP sends an
eCall metadata/control block in response to data sent by the IVS in a eCall metadata/control block in response to data sent by the IVS in a
SIP request other than INFO (e.g., the MSD in the initial INVITE), SIP request other than INFO (e.g., the MSD in the initial INVITE),
the metadata/control block is sent in the SIP response to that the metadata/control block is sent in the SIP response to that
request (e.g., the response to the INVITE request). When the PSAP request (e.g., the response to the INVITE request). When the PSAP
sends an eCall control block in other circumstances (e.g., mid-call), sends a control block in other circumstances (e.g., mid-call), the
the control block is transmitted from the PSAP to the IVS in a SIP control block is transmitted from the PSAP to the IVS in a SIP INFO
INFO request within the established dialog. The IVS sends the request within the established dialog. The IVS sends the requested
requested data (the MSD) in a new INFO request (per [RFC6086]). This data (the MSD) in a new INFO request (per [RFC6086]). This mechanism
mechanism flexibly allows the PSAP to send eCall-specific data to the flexibly allows the PSAP to send eCall-specific data to the IVS and
IVS and the IVS to respond. INFO messages are sent using an the IVS to respond. INFO requests are sent using an appropriate INFO
appropriate INFO Package. See Section 6 for more information on Package. See Section 6 for more information on attaching a metadata/
attaching a metadata/control block to a SIP message. See Section 10 control block to a SIP message. See Section 10 for information about
for information about the use of INFO messages to carry data within the use of INFO requests to carry data within an eCall.
an eCall.
This mechanism requires This mechanism requires
o An XML definition of the eCall control object o An XML definition of the control object
o Extension points for use by eCall-like systems in other regions o Extension points for use by eCall-like systems in other regions
o A MIME type registration for the control object (so it can be o A MIME type registration for the control object (so it can be
carried in SIP messages and responses) carried in SIP messages and responses)
o An entry in the Emergency Call Additional Data Blocks registry so o An entry in the Emergency Call Additional Data Blocks registry so
that the control block can be recognized as emergency call that the control block can be recognized as emergency call
specific data within SIP messages specific data within SIP messages
o An Info-Package registration per [RFC6086] permitting the o An Info-Package registration per [RFC6086] permitting the
metadata/control block and the MSD within INFO messages metadata/control block and the MSD within INFO requests
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 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
skipping to change at page 12, line 16 skipping to change at page 12, line 23
not helpful to retry as a CS-eCall). The SIP response codes 600 not helpful to retry as a CS-eCall). The SIP response codes 600
(Busy Everywhere), 486 (Busy Here), and 603 (Decline) are used when (Busy Everywhere), 486 (Busy Here), and 603 (Decline) are used when
the PSAP wants to reject a call but inform the vehicle occupants that the PSAP wants to reject a call but inform the vehicle occupants that
it is aware of the situation. (Note that there could be edge cases it is aware of the situation. (Note that there could be edge cases
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.eCall.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 to accomodate variances. Note that eCall-like
systems might define their own vehicle data blocks, and so might need systems might define their own vehicle data blocks, and so might need
to register a new INFO package to accomodate the new data content to register a new INFO package to accomodate the new data content
type and the metadata/control object. type and the metadata/control object.
9.1. The eCall Control Block 9.1. The Control Block
The eCall 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 SIP 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 an eCall 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.
skipping to change at page 14, line 36 skipping to change at page 15, line 4
Name: details Name: details
Usage: optional Usage: optional
Type: string Type: string
Direction: Sent from the IVS to the PSAP 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"?>
<emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:control">
<?xml version="1.0" encoding="UTF-8"?> <ack received="true" ref="1234567890@atlanta.example.com"/>
<EmergencyCallData.eCall.Control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"urn:ietf:params:xml:ns:EmergencyCallData:eCall:control">
<ack received="true" ref="1234567890@atlanta.example.com"/>
</EmergencyCallData.eCall.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
the PSAP its capabilities. No attributes for this element are the PSAP its capabilities. No attributes for this element are
currently defined. The following child elements are defined: currently defined. The following child elements are defined:
9.1.2.1. Child Elements of the <capabilities> element 9.1.2.1. Child Elements of the <capabilities> element
skipping to change at page 15, line 29 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"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<?xml version="1.0" encoding="UTF-8"?> <capabilities>
<EmergencyCallData.eCallControl <request action="send-data" supported-values="eCall.MSD"/>
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" </capabilities>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall-control">
<capabilities>
<request action="send-data" supported-values="eCall.MSD"/>
</capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
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 17, line 31 skipping to change at page 18, line 7
Name: element-ID Name: element-ID
Usage: Conditional Usage: Conditional
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.eCall.Control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall: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:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:control">
<request action="send-data" datatype="eCall.MSD"/> <request action="send-data" datatype="eCall.MSD"/>
</EmergencyCallData.eCall.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
package. package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per 'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO messages carrying data [RFC6086] to indicate ability to receive INFO requests carrying data
as described here. as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive eCall related body parts as specified in [TBD: the ability to receive eCall related body parts as specified in [TBD:
THIS DOCUMENT]. THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086]. field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
skipping to change at page 19, line 27 skipping to change at page 20, line 5
The info package name is emergencyCallData.eCall.MSD The info package name is emergencyCallData.eCall.MSD
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 Message 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:
o an application/emergencyCallData.eCall.MSD+per (containing an o an application/emergencyCallData.eCall.MSD+per (containing an
MSD), or MSD), or
o an application/emergencyCallData.eCall.control+xml (containing a o an application/emergencyCallData.control+xml (containing a
metadata/control object), or metadata/control object), or
o a multipart body containing: o a multipart body containing:
* zero or one application/emergencyCallData.eCall.MSD+per part * zero or one application/emergencyCallData.eCall.MSD+per part
(containing an MSD), (containing an MSD),
* zero or more application/emergencyCallData.eCall.control+xml * zero or more application/emergencyCallData.control+xml
(containing a metadata/control object), (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 non-INFO messages, each with how these body parts are sent in SIP messages other than INFO
associated body part is referenced by a Call-Info header field at the requests, each associated body part is referenced by a Call-Info
top level of the SIP message. If the body part is the only body header field at the top level of the SIP message. If the body part
part, it has a Content-Disposition header field value of "INFO- is the only body part, it has a Content-Disposition header field
Package; handling=optional". If the body part is contained within a value of "INFO-Package". If the body part is contained within a
multipart body part, it has a Content-Disposition header field value multipart, it has a Content-Disposition header field value of "By-
of "By-Reference; handling=optional" (the top-level multipart body Reference".
part has "INFO-Package" in its Content-Disposition value).
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 21, line 28 skipping to change at page 22, line 6
| Network | | ESInet | | Network | | ESInet |
+------------+ +---------------------------------------+ +------------+ +---------------------------------------+
Figure 6: Example of NG-eCall Message Flow Figure 6: Example of NG-eCall Message Flow
Figure 7 illustrates an eCall call flow with a mid-call PSAP request Figure 7 illustrates an eCall call flow with a mid-call PSAP request
for an updated MSD. The call flow shows the IVS initiating an for an updated MSD. The call flow shows the IVS initiating an
emergency call, including the MSD in the INVITE. The PSAP includes emergency call, including the MSD in the INVITE. The PSAP includes
in the 200 OK response a metadata/control object acknowledging in the 200 OK response a metadata/control object acknowledging
receipt of the MSD. During the call, the PSAP sends a request for an receipt of the MSD. During the call, the PSAP sends a request for an
MSD in an INFO message. The IVS sends the requested MSD in a new MSD in an INFO request. The IVS sends the requested MSD in a new
INFO message. INFO request.
IVS PSAP IVS PSAP
|(1) INVITE (eCall MSD) | |(1) INVITE (eCall MSD) |
|------------------------------------------->| |------------------------------------------->|
| | | |
|(2) 200 OK (eCall metadata [ack MSD]) | |(2) 200 OK (eCall metadata [ack MSD]) |
|<-------------------------------------------| |<-------------------------------------------|
| | | |
|(3) start media stream(s) | |(3) start media stream(s) |
|............................................| |............................................|
skipping to change at page 23, line 14 skipping to change at page 23, line 14
INVITE urn:service:sos.ecall.automatic SIP/2.0 INVITE 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
Geolocation: <cid:target123@example.com> Geolocation: <cid:target123@example.com>
Geolocation-Routing: no Geolocation-Routing: no
Call-Info: <cid:1234567890@atlanta.example.com>; Call-Info: <cid:1234567890@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.eCall.control+xml application/emergencyCallData.control+xml
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
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
skipping to change at page 23, line 39 skipping to change at page 23, line 39
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 an eCall control block the INVITE of Figure 8, containing a control block acknowledging
acknowledging successful receipt of the eCall MSD. (For simplicity, successful receipt of the eCall MSD. (For simplicity, the example
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: <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:2345678901@atlanta.example.com>; Call-Info: <cid:2345678901@atlanta.example.com>;
purpose=emergencyCallData.eCall.control purpose=emergencyCallData.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.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
Content-Type: multipart/mixed; boundary=boundaryX Content-Type: multipart/mixed; boundary=boundaryX
Content-Length: ... Content-Length: ...
--boundaryX --boundaryX
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundaryX --boundaryX
Content-Type: application/EmergencyCallData.eCall.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <2345678901@atlanta.example.com> Content-ID: <2345678901@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCall.Control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall: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:eCall: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.eCall.Control> </emergencyCallData.control>
--boundaryX-- --boundaryX--
Figure 9: 200 OK response to INVITE Figure 9: 200 OK response to INVITE
Figure 10 illustrates an INFO message containing an eCall metadata/ Figure 10 illustrates an INFO request containing an eCall 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.eCall.control purpose=emergencyCallData.control
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.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; handling=optional Content-Disposition: info-package
Content-Type: application/EmergencyCallData.eCall.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.eCall.Control <emergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall: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:eCall:control"> "urn:ietf:params:xml:ns:EmergencyCallData:control">
<request action="send-data" datatype="eCall.MSD"/> <request action="send-data" datatype="eCall.MSD"/>
</EmergencyCallData.eCall.Control> </emergencyCallData.control>
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 eCall INFO that contains 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.eCall.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: 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; handling=optional Content-Disposition: info-package
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
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
skipping to change at page 27, line 46 skipping to change at page 27, line 46
Privacy considerations specific to the data structure containing Privacy considerations specific to the data structure containing
vehicle information are discussed in the "Security Considerations" vehicle information are discussed in the "Security Considerations"
block of Section 15.2. block of Section 15.2.
Privacy considerations specific to the mechanism by which the PSAP Privacy considerations specific to the mechanism by which the PSAP
sends acknowledgments and requests to the vehicle are discussed in sends acknowledgments and requests to the vehicle are discussed in
the "Security Considerations" block of Section 15.3. the "Security Considerations" block of Section 15.3.
14. XML Schema 14. XML Schema
This section defines an XML schema for the eCall control block. The This section defines an XML schema for the control block. The text
text description of the eCall control block in Section 9.1 is description of the control block in Section 9.1 is normative and
normative and supersedes any conflicting aspect of this schema. supersedes any conflicting aspect of this schema.
<artwork> <artwork>
<![CDATA[ <![CDATA[
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall-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:eCall-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"/> schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
<xs:element name="EmergencyCallData.eCallControl" <xs:element name="EmergencyCallData.eCallControl"
type="pi:eCallControlType"/> type="pi:eCallControlType"/>
skipping to change at page 30, line 21 skipping to change at page 30, line 21
<xs:attribute name="supported-values" type="xs:string"/> <xs:attribute name="supported-values" type="xs:string"/>
<xs:attribute name="element-id" type="xs:token"/> <xs:attribute name="element-id" type="xs:token"/>
<xs:attribute name="requested-state" type="xs:token"/> <xs:attribute name="requested-state" type="xs:token"/>
<xs:anyAttribute/> <xs:anyAttribute/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 12: eCall Control Block Schema Figure 12: Control Block Schema
15. IANA Considerations 15. IANA Considerations
15.1. Service URN Registrations 15.1. Service URN Registrations
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
skipping to change at page 32, line 17 skipping to change at page 32, line 17
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 Content-type Registration for 'application/
emergencyCallData.eCall.control+xml' emergencyCallData.control+xml'
IANA is requested to add application/ IANA is requested to add application/emergencyCallData.control+xml as
emergencyCallData.eCall.control+xml as a MIME content type, with a a MIME content type, with a reference to this document, in accordance
reference to this document, in accordance to the procedures of RFC to the procedures of RFC 6838 [RFC6838] and guidelines in RFC 7303
6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.control+xml MIME subtype name: emergencyCallData.control+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of the XML content. Indicates the character encoding of the XML content.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 7303 [RFC7303]. Section 3.2 of RFC 7303 [RFC7303].
skipping to change at page 34, line 5 skipping to change at page 34, line 5
Change controller: The IETF ECRIT WG. Change controller: The IETF ECRIT WG.
15.4. Registration of the 'eCall.MSD' entry in the Emergency Call 15.4. Registration of the 'eCall.MSD' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.MSD' entry to the This specification requests IANA to add the 'eCall.MSD' entry to the
Emergency Call Additional Data Blocks registry, with a reference to Emergency Call Additional Data Blocks registry, with a reference to
this document. this document.
15.5. Registration of the 'eCall.control' entry in the Emergency Call 15.5. Registration of the 'control' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.control' entry to This specification requests IANA to add the 'control' entry to the
the Emergency Call Additional Data Blocks registry, with a reference Emergency Call Additional Data Blocks registry, with a reference to
to this document. this document.
15.6. Registration of the emergencyCallData.eCall Info Package 15.6. Registration of the emergencyCallData.eCall Info Package
IANA is requested to add emergencyCallData.eCall to the Info Packages IANA is requested to add emergencyCallData.eCall to the Info Packages
Registry under "Session Initiation Protocol (SIP) Parameters", with a Registry under "Session Initiation Protocol (SIP) Parameters", with a
reference to this document. reference to this document.
15.7. URN Sub-Namespace Registration 15.7. URN Sub-Namespace Registration
15.7.1. Registration for urn:ietf:params:xml:ns:eCall 15.7.1. Registration for urn:ietf:params:xml:ns:eCall
skipping to change at page 35, line 5 skipping to change at page 35, line 5
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for eCall Data</title> <title>Namespace for eCall Data</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
15.7.2. Registration for urn:ietf:params:xml:ns:eCall:control 15.7.2. Registration for urn:ietf:params:xml:ns:control
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall:control URI: urn:ietf:params:xml:ns:control
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 36, line 7 skipping to change at page 36, line 7
This document creates a new sub-registry called "Action Registry". This document creates a new sub-registry called "Action Registry".
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the proposed action is rules. The expert should determine that the proposed action is
within the purview of a vehicle, is sufficiently distinguishable from within the purview of a vehicle, is sufficiently distinguishable from
other actions, and the action is clearly and fully described. In other actions, and the action is clearly and fully described. In
most cases, a published and stable document is referenced for the most cases, a published and stable document is referenced for the
description of the action. description of the action.
The content of this registry includes: The content of this registry includes:
Name: The identifier to be used in the 'action' attribute of an Name: The identifier to be used in the 'action' attribute of a
eCall control <request> element. control <request> element.
Description: A description of the action. In most cases this will Description: A description of the action. In most cases this will
be a reference to a published and stable document. The be a reference to a published and stable document. The
description MUST specify if any attributes or child elements are description MUST specify if any attributes or child elements are
optional or mandatory, and describe the action to be taken by the optional or mandatory, and describe the action to be taken by the
vehicle. vehicle.
The initial set of values is listed in Table 2. The initial set of values is listed in Table 2.
+-----------+--------------------------------------+ +-----------+--------------------------------------+
skipping to change at page 37, line 10 skipping to change at page 37, line 10
Description: A description of the reason. Description: A description of the reason.
The initial set of values is listed in Table 3. The initial set of values is listed in Table 3.
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
| ID | Description | | ID | Description |
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
| unsupported | The 'action' value is not supported. | | unsupported | The 'action' value is not supported. |
| | | | | |
| unable | The action could not be accomplished. | | damaged | Required components are damaged. |
| | |
| unable | The action could not be accomplished (a |
| | generic error for use when no other code is |
| | appropriate). |
| | | | | |
| data-unsupported | The data item referenced in a 'send-data' | | data-unsupported | The data item referenced in a 'send-data' |
| | request is not supported. | | | request is not supported. |
| | | | | |
| security-failure | The authenticity of the request or the | | security-failure | The authenticity of the request or the |
| | authority of the requestor could not be | | | authority of the requestor could not be |
| | verified. | | | verified. |
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
Table 3: Reason Registry Table 3: Reason Registry
skipping to change at page 37, line 40 skipping to change at page 37, line 44
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. 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. this document is based.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-11 to draft-ietf-12 18.1. Changes from draft-ietf-12 to draft-ietf-13
o Clarifications suggested by Christer
o Corrections to Content-Disposition text and examples as suggested
by Paul Kyzivat
o Clarifications to Content-Disposition text and examples to clarify
that handling=optional is only used in the initial INVITE
18.2. 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.2. Changes from draft-ietf-09 to draft-ietf-11 18.3. 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.3. Changes from draft-ietf-08 to draft-ietf-09 18.4. 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.4. Changes from draft-ietf-07 to draft-ietf-08 18.5. 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
skipping to change at page 39, line 4 skipping to change at page 39, line 16
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.5. Changes from draft-ietf-06 to draft-ietf-07 18.6. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.6. Changes from draft-ietf-05 to draft-ietf-06 18.7. 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.7. Changes from draft-ietf-04 to draft-ietf-05 18.8. 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.8. Changes from draft-ietf-03 to draft-ietf-04 18.9. 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.9. Changes from draft-ietf-02 to draft-ietf-03 18.10. 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.10. Changes from draft-ietf-01 to draft-ietf-02 18.11. 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.11. Changes from draft-ietf-00 to draft-ietf-01 18.12. 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 eCall o Added IANA registration for the MIME content type for the control
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
eCall control object control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.12. Changes from draft-gellens-03 to draft-ietf-00 18.13. 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.13. Changes from draft-gellens-02 to -03 18.14. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.14. Changes from draft-gellens-01 to -02 18.15. 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.15. Changes from draft-gellens-00 to -01 18.16. 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
 End of changes. 94 change blocks. 
205 lines changed or deleted 218 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/