< draft-ietf-ecrit-ecall-20.txt   draft-ietf-ecrit-ecall-21.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: May 18, 2017 Individual Expires: June 18, 2017 Individual
November 14, 2016 December 15, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-20.txt draft-ietf-ecrit-ecall-21.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 media 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 SIP INFO
requests. requests.
Although this specification is designed to meet the requirements of
European next-generation eCall, it is specified generically such that
the technology can be re-used or extended to suit requirements across
jurisdictions.
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 May 18, 2017. This Internet-Draft will expire on June 18, 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 28
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 7 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 7
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11 9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11
9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 12 9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 13
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 . . . . . . . . . 14
9.1.1.2. Child Element of the <ack> element . . . . . . . 14 9.1.1.2. Child Element of the <ack> element . . . . . . . 14
9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 15 9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 15
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 . . . . . . . . . . . . . . 16
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. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Overall Description . . . . . . . . . . . . . . . . . . 18 11. Security Considerations . . . . . . . . . . . . . . . . . . . 24
10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 25
10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19 13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26
10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19 14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 28
10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 19 14.2. Service URN Registrations . . . . . . . . . . . . . . . 29
10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20 14.3. MIME Media Type Registration for
10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20 'application/emergencyCallData.eCall.MSD+per' . . . . . 29
10.9. Info Package Security Considerations . . . . . . . . . . 20 14.4. MIME Media Type Registration for
10.10. Implementation Details . . . . . . . . . . . . . . . . . 21 'application/emergencyCallData.control+xml' . . . . . . 31
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21 14.5. Registration of the 'eCall.MSD' entry in the Emergency
12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 Call Additional Data Types registry . . . . . . . . . . 32
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 14.6. Registration of the 'control' entry in the Emergency
14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28 Call Additional Data Types registry . . . . . . . . . . 32
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 14.7. Registration of the emergencyCallData.eCall Info Package 33
15.1. Service URN Registrations . . . . . . . . . . . . . . . 31 14.8. URN Sub-Namespace Registration . . . . . . . . . . . . . 33
15.2. MIME Media Type Registration for 14.8.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 14.8.2. Registration for urn:ietf:params:xml:ns:control . . 33
15.3. MIME Media Type Registration for 14.9. Registry Creation . . . . . . . . . . . . . . . . . . . 34
'application/emergencyCallData.control+xml' . . . . . . 32 14.9.1. Emergency Call Action Registry . . . . . . . . . . . 34
15.4. Registration of the 'eCall.MSD' entry in the Emergency 14.9.2. Emergency Call Action Failure Reason Registry . . . 35
Call Additional Data Blocks registry . . . . . . . . . . 34 14.10. The emergencyCallData.eCall.MSD INFO package . . . . . . 36
15.5. Registration of the 'control' entry in the Emergency 14.10.1. Overall Description . . . . . . . . . . . . . . . . 36
Call Additional Data Blocks registry . . . . . . . . . . 34 14.10.2. Applicability . . . . . . . . . . . . . . . . . . . 37
15.6. Registration of the emergencyCallData.eCall Info Package 34 14.10.3. Info Package Name . . . . . . . . . . . . . . . . . 37
15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34 14.10.4. Info Package Parameters . . . . . . . . . . . . . . 37
15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34 14.10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 38
15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35 14.10.6. INFO Request Body Parts . . . . . . . . . . . . . . 38
15.8. Registry Creation . . . . . . . . . . . . . . . . . . . 36 14.10.7. Info Package Usage Restrictions . . . . . . . . . . 38
15.8.1. Emergency Call Action Registry . . . . . . . . . . . 36 14.10.8. Rate of INFO Requests . . . . . . . . . . . . . . . 38
15.8.2. Emergency Call Action Failure Reason Registry . . . 37 14.10.9. Info Package Security Considerations . . . . . . . 39
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38 14.10.10. Implementation Details . . . . . . . . . . . . . . 39
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 14.10.11. Examples . . . . . . . . . . . . . . . . . . . . . 39
18. Changes from Previous Versions . . . . . . . . . . . . . . . 38 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39
18.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 38 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
18.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 38 17. Changes from Previous Versions . . . . . . . . . . . . . . . 39
18.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38 17.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 39
18.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38 17.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 39
18.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38 17.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 40
18.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 39 17.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 40
18.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 39 17.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 40
18.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 39 17.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 40
18.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39 17.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 40
18.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39 17.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 40
18.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 40 17.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 40
18.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 40 17.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 41
18.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 17.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 41
18.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 41 17.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41
18.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 41 17.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42
18.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 41 17.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42
18.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 41 17.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42
18.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41 17.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42
18.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42 17.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42
18.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 42 17.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42
18.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 42 17.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 43
18.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42 17.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 43
18.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42 17.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 43
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 17.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43
19.1. Normative References . . . . . . . . . . . . . . . . . . 43 17.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 44
19.2. Informative references . . . . . . . . . . . . . . . . . 44 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 18.1. Normative References . . . . . . . . . . . . . . . . . . 44
18.2. Informative references . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46
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 5, line 7 skipping to change at page 5, line 13
include far greater scope than is covered here. include far greater scope than is covered here.
The eCall service operates over cellular wireless communication, but The eCall service operates over cellular wireless communication, but
this document does not address cellular-specific details, nor client this document does not address cellular-specific details, nor client
domain selection (e.g., circuit-switched versus packet-switched). domain selection (e.g., circuit-switched versus packet-switched).
All such aspects are the purview of their respective standards All such aspects are the purview of their respective standards
bodies. The scope of this document is limited to eCall operating bodies. The scope of this document is limited to eCall operating
within a SIP-based environment (e.g., 3GPP IMS Emergency Calling within a SIP-based environment (e.g., 3GPP IMS Emergency Calling
[TS23.167]). [TS23.167]).
The technical contents of this document also provide a basis for Although this specification is designed to meet the requirements of
reuse and extension for related emergency call systems (which is why pan-European next-generation eCall, it is specified generically such
there are extension points), but such reuse is a topic for other that the technology can be re-used or extended to suit requirements
documents. across jurisdictions (see, e.g., [I-D.ietf-ecrit-car-crash]), and
extension points are provided to facilitate this.
Note that vehicles designed for multiple regions might need to Note that vehicles designed for multiple regions might need to
support eCall and other Advanced Automatic Crash Notification (AACN) support eCall and other Advanced Automatic Crash Notification (AACN)
systems (such as described in [I-D.ietf-ecrit-car-crash]), but this systems (such as described in [I-D.ietf-ecrit-car-crash]), but this
is out of scope of this document. is out of scope of this document.
3. Introduction 3. Introduction
Emergency calls made from vehicles (e.g., in the event of a crash) Emergency calls made from vehicles (e.g., in the event of a crash)
assist in significantly reducing road deaths and injuries by allowing assist in significantly reducing road deaths and injuries by allowing
skipping to change at page 6, line 41 skipping to change at page 6, line 48
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 media 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 SIP
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 14). An INFO package is
defined (in Section 10) to enable these MIME types to be carried in defined (in Section 14.10) to enable these MIME types to be carried
SIP INFO requests, per [RFC6086]. in 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 and [TS24.229] section 4.7.6. [TS22.101] clauses 10.7 and A.27 and [TS24.229] section 4.7.6.
Requirements specific to vehicle data are contained in EN 15722 Requirements specific to vehicle data are contained in EN 15722
[msd]. [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 (including VIN, vehicle type, propulsion type,
European Committee for Standardization (CEN) has specified this data current and optionally previous location coordinates, and number of
in EN 15722 [msd], along with both ASN.1 and XML encodings. Both occupants), known as the Minimum Set of Data (MSD). The European
circuit-switched eCall and this document use the ASN.1 PER encoding, Committee for Standardization (CEN) has specified this data in EN
which is specified in Annex A of EN 15722 [msd] (the XML encoding 15722 [msd], along with both ASN.1 and XML encodings. Both circuit-
specified in Annex C is not used in this document). switched eCall and this document use the ASN.1 PER encoding, which is
specified in Annex A of EN 15722 [msd] (the XML encoding specified in
Annex C is not used in this document, per 3GPP [SDO-3GPP]).
This document registers the 'application/ This document registers the 'application/
emergencyCallData.eCall.MSD+per' MIME media type to enable the MSD to emergencyCallData.eCall.MSD+per' MIME media type to enable the MSD 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 Types registry to enable the MSD to be
be recognized as such in a SIP-based eCall emergency call. (See 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.
6. Data Transport 6. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of [RFC7852] establishes a general mechanism for conveying blocks of
data to a SIP emergency call. This mechanism permits certain data within a SIP emergency call. This document makes use of that
emergency call MIME types to be attached to SIP messages. This mechanism to include vehicle data (the MSD, see Section 5) and/or
document makes use of that mechanism. This document also registers metadata/control information (see Section 9) within SIP messages.
an INFO package (in Section 10) to enable eCall related data blocks This document also registers an INFO package (in Section 14.10) to
to be carried in SIP INFO requests (per [RFC6086], new INFO usages enable eCall related data blocks to be carried in SIP INFO requests
require the definition of an INFO package). (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 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 including it as a MIME
message as a MIME body part per [RFC7852]. The body part is body part within a SIP message per [RFC7852]. The body part is
identified by its MIME media 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 Types 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 14.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 including it
a SIP message as a MIME body part per [RFC7852]. The body part is within a SIP message as a MIME body part per [RFC7852]. The body
identified by its MIME media type ('application/ part is 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 Types registry entry; the
'purpose' parameter's value is 'emergencyCallData.control'. Per 'purpose' parameter's value is 'emergencyCallData.control'. Per
[RFC6086], a metadata/control object is carried in a SIP INFO request [RFC6086], a metadata/control object is carried in a SIP INFO request
by using the INFO package defined in Section 10. by using the INFO package defined in Section 14.10.
An MSD or a metadata/control block is always enclosed in a multipart An MSD or a metadata/control block is always enclosed in a multipart
(normally multipart/mixed) body part (even if it would otherwise be (normally multipart/mixed) body part (even if it would otherwise be
the only body part in the SIP message), since as of the date of this the only body part in the SIP message), since as of the date of this
document, the use of Content-ID as a SIP header field is not defined document, the use of Content-ID as a SIP header field is not defined
(while it is defined for use as a MIME header field). (while it is defined for use as a MIME header field).
A body part containing an MSD or metadata/control object has a A body part containing an MSD or metadata/control object has a
Content-Disposition header field value containing "By-Reference". Content-Disposition header field value containing "By-Reference".
An In-Vehicle System (IVS) initiating an NG-eCall attaches an MSD to An In-Vehicle System (IVS) initiating an NG-eCall includes an MSD as
the initial INVITE and optionally attaches a metadata/control object a body part within the initial INVITE, and optionally also includes a
informing the PSAP of its capabilities. The MSD body part (and metadata/control object informing the PSAP of its capabilities as
metadata/control and PIDF-LO body parts if included) have a Content- another body part. The MSD body part (and metadata/control and PIDF-
Disposition header field with the value "By-Reference; LO body parts if included) have a Content-Disposition header field
handling=optional". Specifying "handling=optional" prevents the with the value "By-Reference; handling=optional". Specifying
INVITE from being rejected if it is processed by a legacy element "handling=optional" prevents the SIP INVITE request from being
(e.g., a gateway between SIP and circuit-switched environments) that rejected if it is processed by a legacy element (e.g., a gateway
does not understand the MSD (or metadata/control object or PIDF-LO). between SIP and circuit-switched environments) that does not
understand the MSD (or metadata/control object or PIDF-LO). The PSAP
The PSAP creates a metadata/control object acknowledging receipt of creates a metadata/control object acknowledging receipt of the MSD
the MSD and attaches it to the SIP final response to the INVITE. A and includes it as a body part within the SIP final response to the
metadata/control object is not attached to provisional (e.g., 180) SIP INVITE request per [RFC7852]. A metadata/control object is sent
responses. within a provisional (e.g., 180) responses.
A PSAP is able to reject a call while indicating that it is aware of A PSAP is able to reject a call while indicating that it is aware of
the situation by including a metadata/control object acknowledging the situation by including a metadata/control object acknowledging
the MSD and containing "received=true" in a final response using SIP the MSD and containing "received=true" within a final response using
response code 600 (Busy Everywhere), 486 (Busy Here), or 603 SIP response code 600 (Busy Everywhere), 486 (Busy Here), or 603
(Decline). (Decline), per [RFC7852].
If the IVS receives an acknowledgment for an MSD containing If the IVS receives an acknowledgment for an MSD containing
"received=false", this indicates that the PSAP was unable to properly "received=false", this indicates that the PSAP was unable to properly
decode or process the MSD. The IVS action is not defined (e.g., it decode or process the MSD. The IVS action is not defined (e.g., it
might only log an error). Since the PSAP is able to request an might only log an error). Since the PSAP is able to request an
updated MSD during the call, if an initial MSD is unsatisfactory in updated MSD during the call, if an initial MSD is unsatisfactory in
any way, the PSAP can choose to request another one. any way, the PSAP can choose to request another one.
A PSAP can request that the vehicle send an updated MSD during a call A PSAP can request that the vehicle send an updated MSD during a call
(e.g., upon manual request of the PSAP call taker who suspects (e.g., upon manual request of the PSAP call taker who suspects
vehicle state may have changed.) To do so, the PSAP creates a vehicle state may have changed.) To do so, the PSAP creates a
metadata/control object requesting an MSD and attaches it to a SIP metadata/control object requesting an MSD and includes it within a
INFO request and sends it within the dialog. The IVS then attaches SIP INFO request sent within the dialog. The IVS then includes an
an updated MSD to a SIP INFO request and sends it within the dialog. updated MSD within a SIP INFO request and sends it within the dialog.
If the IVS is unable to send an MSD, it instead sends a metadata/ If the IVS is unable to send an MSD, it instead sends a metadata/
control object acknowledging the request with the 'success' parameter control object acknowledging the request with the 'success' parameter
set to 'false' and a 'reason' parameter (and optionally a 'details' set to 'false' and a 'reason' parameter (and optionally a 'details'
parameter) indicating why the request could not be accomplished. Per parameter) indicating why the request could not be accomplished. Per
[RFC6086], metadata/control objects and MSDs are sent using the INFO [RFC6086], metadata/control objects and MSDs are sent using the INFO
package defined in Section 10 . In addition, to align with how an package defined in Section 14.10. In addition, to align with how an
MSD or metadata/control block is transmitted in a SIP message other MSD or metadata/control block is transmitted in a SIP message other
than an INFO request, a Call-Info header field is included in the SIP than an INFO request, a Call-Info header field is included in the SIP
INFO request to reference the MSD or metadata/control block. See INFO request to reference the MSD or metadata/control block per
Section 10 for information about the use of INFO requests to carry [RFC7852]. See Section 14.10 for information about the use of SIP
data within an eCall. INFO requests to carry data within an eCall.
The IVS is not expected to send an unsolicited MSD after the initial The IVS is not expected to send an unsolicited MSD after the initial
INVITE. INVITE.
This document does not mandate support for the data blocks defined in This document does not mandate support for the data blocks defined in
[RFC7852]. [RFC7852].
7. Call Setup 7. Call Setup
In circuit-switched eCall, the IVS places a special form of a 112 In circuit-switched eCall, the IVS places a special form of a 112
skipping to change at page 11, line 14 skipping to change at page 11, line 26
communication. The IVS might also be able to verify that the MSD was communication. The IVS might also be able to verify that the MSD was
successfully received. successfully received.
A service URN starting with "test." indicates a test call. For A service URN starting with "test." indicates a test call. For
eCall, "urn:service:test.sos.ecall" indicates such a test feature. eCall, "urn:service:test.sos.ecall" indicates such a test feature.
This functionality is defined in [RFC6881]. This functionality is defined in [RFC6881].
This document registers "urn:service:test.sos.ecall" for eCall test This document registers "urn:service:test.sos.ecall" for eCall test
calls. calls.
The CS-eCall test call facility is a non-emergency number so does not The circuit switched eCall test call facility is a non-emergency
get treated as an emergency call. For NG-eCall, MNOs, emergency number so does not get treated as an emergency call. For NG-eCall,
authorities, and PSAPs can determine how to treat a vehicle call MNOs, emergency authorities, and PSAPs can determine how to treat a
requesting the "test" service URN so that the desired functionality vehicle call requesting the "test" service URN so that the desired
is tested, but this is outside the scope of this document. functionality is tested, but this is outside the scope of this
document.
9. The Metadata/Control Object 9. The Metadata/Control Object
eCall requires the ability for the PSAP to acknowledge successful eCall requires the ability for the PSAP to acknowledge successful
receipt of an MSD sent by the IVS, and for the PSAP to request that receipt of an MSD sent by the IVS, and for the PSAP to request that
the IVS send an MSD (e.g., the call taker can initiate a request for the IVS send an MSD (e.g., the call taker can initiate a request for
a new MSD to see if there have been changes in the vehicle's state, a new MSD to see if there have been changes in the vehicle's state,
e.g., location, direction, number of fastened seatbelts). e.g., location, direction, number of fastened seatbelts).
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 related structure containing elements used for eCall and other related
emergency call systems and extension points. (This metadata/control emergency call systems and extension points. (This metadata/control
block is in effect a high-level protocol between the PSAP and IVS.) block is in effect a high-level protocol between the PSAP and IVS.)
When the PSAP sends a metadata/control block in response to data sent When the PSAP sends a metadata/control block in response to data sent
by the IVS in a SIP request other than INFO (e.g., the MSD in the by the IVS in a SIP request other than INFO (e.g., the MSD in the
initial INVITE), the metadata/control block is sent in the SIP initial INVITE), the metadata/control block is sent in the SIP
response to that request (e.g., the response to the INVITE request). response to that request (e.g., the response to the INVITE request).
When the PSAP sends a control block in other circumstances (e.g., When the PSAP sends a control block in other circumstances (e.g.,
mid-call), the control block is transmitted from the PSAP to the IVS mid-call), the control block is transmitted from the PSAP to the IVS
in a SIP INFO request within the established dialog. The IVS sends in a SIP INFO request within the established dialog. The IVS sends
the requested data (the MSD) in a new INFO request (per [RFC6086]). the requested data (the MSD) in a new SIP INFO request (per
This mechanism flexibly allows the PSAP to send eCall-specific data
to the IVS and the IVS to respond. INFO requests are sent using an [RFC6086]). This mechanism flexibly allows the PSAP to send eCall-
appropriate INFO Package. See Section 6 for more information on specific data to the IVS and the IVS to respond. SIP INFO requests
attaching a metadata/control block to a SIP message. See Section 10 are sent using an appropriate SIP INFO Package. See Section 6 for
for information about the use of INFO requests to carry data within more information on sending a metadata/control block within a SIP
an eCall. message. See Section 14.10 for information about the use of SIP INFO
requests to carry data within 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 final 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 a SIP INFO request indicates only
that the receiver has successfully received and accepted the INFO that the receiver has successfully received and accepted the SIP INFO
request, it says nothing about the acceptability of the payload.) If request, it says nothing about the acceptability of the payload.) If
the IVS receives a request to send an MSD but it is unable to do so the IVS receives a request to send an MSD but it is unable to do so
for any reason, the IVS sends a metadata/control object acknowledging for any reason, the IVS sends a metadata/control object acknowledging
the request and containing "success=false" and "reason" set to an the request and containing "success=false" and "reason" set to an
appropriate code. appropriate code.
This provides flexibility to handle various circumstances. For This provides flexibility to handle various circumstances. For
example, if a PSAP is unable to accept an eCall (e.g., due to example, if a PSAP is unable to accept an eCall (e.g., due to
overload or too many calls from the same location), it can reject the overload or too many calls from the same location), it can reject the
INVITE. Since a metadata/control object is also included in the SIP INVITE. Since a metadata/control object is also included in the SIP
response that rejects the call, the IVS knows if the PSAP received response that rejects the call, the IVS knows if the PSAP received
the MSD, and can inform the vehicle occupants that the PSAP the MSD, and can inform the vehicle occupants that the PSAP
successfully received the vehicle location and information but can't successfully received the vehicle location and information but can't
talk to the occupants at that time. Especially for SIP response talk to the occupants at that time. Especially for SIP response
codes that indicate an inability to conduct a call (as opposed to a codes that indicate an inability to conduct a call (as opposed to a
technical inability to process the request), the IVS can also technical inability to process the request), the IVS can also
determine that the call was successful on a technical level (e.g., determine that the call was successful on a technical level (e.g.,
not helpful to retry as a CS-eCall). (Note that there could be edge not helpful to retry as circuit-switched). (Note that there could be
cases where the PSAP response is not received by the IVS, e.g., if an edge cases where the PSAP response is not received by the IVS, e.g.,
intermediary sends a CANCEL, and an error response is forwarded if an intermediary sends a CANCEL, and an error response is forwarded
towards the IVS before the error response from the PSAP is received, towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.) the response will be dropped, but these are unlikely to occur here.)
The metadata/control block is carried in the MIME type 'application/ The metadata/control block is carried in the MIME type 'application/
emergencyCallData.control+xml'. emergencyCallData.control+xml'.
The metadata/control block is designed for use with pan-European The metadata/control block is designed for use with pan-European
eCall and also eCall-like systems (i.e., in other regions), and has eCall and also eCall-like systems (i.e., in other regions), and has
extension points. 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
skipping to change at page 13, line 24 skipping to change at page 13, line 38
request Used in a control block sent by the PSAP to the IVS, to request Used in a control block sent by the PSAP to the IVS, to
request the vehicle to perform an action. request the vehicle to perform an action.
The <ack> element indicates the object being acknowledged and reports The <ack> element indicates the object being acknowledged and reports
success or failure. success or failure.
The <request> element contains attributes to indicate the request and The <request> element contains attributes to indicate the request and
to supply related information. The 'action' attribute is mandatory to supply related information. The 'action' attribute is mandatory
and indicates the specific action. An IANA registry is created in and indicates the specific action. An IANA registry is created in
Section 15.8.1 to contain the allowed values. Section 14.9.1 to contain the allowed values.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element acknowledges receipt of an eCall data object or The <ack> element acknowledges receipt of an eCall data object or
request. An <ack> element references the Content-ID of the object request. An <ack> element references the Content-ID of the object
being acknowledged. The PSAP MUST send an <ack> element being acknowledged. The PSAP MUST send an <ack> element
acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in acknowledging receipt of an unsolicited MSD (e.g., sent by the IVS in
skipping to change at page 14, line 42 skipping to change at page 15, line 10
Usage: Mandatory Usage: Mandatory
Type: Boolean Type: Boolean
Description: Indicates if the action was successfully Description: Indicates if the action was successfully
accomplished accomplished
Name: reason Name: reason
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used when 'success' is "false", this attribute Description: Used when 'success' is "false", this attribute
contains a reason code for a failure. A registry for reason contains a reason code for a failure. A registry for reason
codes is defined in Section 15.8.2. codes is defined in Section 14.9.2. The initial values are:
damaged (required components are damaged), data-unsupported
(the data item referenced in a 'send-data' request is not
supported), security-failure (the authenticity of the request
or the authority of the requestor could not be verified),
unable (a generic error for use when no other code is
appropriate), and unsupported (the 'action' value is not
supported).
Name: details Name: details
Usage: optional Usage: optional
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
skipping to change at page 16, line 36 skipping to change at page 17, line 4
The <request> element has the following attributes: The <request> element has the following attributes:
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Direction: Sent in either direction Direction: Sent in either direction
Description: Identifies the action that the vehicle is requested to Description: Identifies the action that the vehicle is requested to
perform (in a <request> element within a <capabilities> element, perform (in a <request> element within a <capabilities> element,
indicates an action that the vehicle is capable of performing). indicates an action that the vehicle is capable of performing).
An IANA registry is established in Section 15.8.1 to contain the
An IANA registry is established in Section 14.9.1 to contain the
allowed values. allowed values.
Example: action="send-data" Example: action="send-data"
Name: msgid Name: int-id
Usage: Conditional Usage: Conditional
Type: int Type: int
Direction: Sent in either direction Direction: Sent in either direction
Description: Defined for extensibility. Description: Defined for extensibility. Documents that make use of
Example: msgid="3" it are expected to explain when it is required and how it it used.
Example: int-id="3"
Name: persistance Name: persistence
Usage: Optional Usage: Optional
Type: duration Type: duration
Direction: Sent in either direction Direction: Sent in either direction
Description: Defined for extensibility. Specifies how long to carry Description: Defined for extensibility. Specifies how long to carry
on the specified action. If absent, the default is for the on the specified action. If absent, the default is for the
duration of the call. duration of the call.
Example: persistance="PT1H" Example: persistence="PT1H"
Name: datatype Name: datatype
Usage: Conditional Usage: Conditional
Type: token Type: token
Direction: Sent in either direction Direction: Sent in either direction
Description: Mandatory with a "send-data" action within a <request> Description: Mandatory with a "send-data" action within a <request>
element that is not within a <capabilities> element. Specifies element that is not within a <capabilities> element. Specifies
the data block that the IVS is requested to transmit, using the the data block that the IVS is requested to transmit, using the
same identifier as in the 'purpose' attribute set in a Call-Info same identifier as in the 'purpose' attribute set in a Call-Info
header field to point to the data block. Permitted values are header field to point to the data block. Permitted values are
skipping to change at page 17, line 31 skipping to change at page 17, line 48
Example: datatype="eCall.MSD" Example: datatype="eCall.MSD"
Name: supported-values Name: supported-values
Usage: Conditional Usage: Conditional
Type: string Type: string
Direction: Sent from the IVS to the PSAP Direction: Sent from the IVS to the PSAP
Description: Defined for extensibility. Used in a <request> element Description: Defined for extensibility. Used in a <request> element
that is a child of a <capability> element, this attribute lists that is a child of a <capability> element, this attribute lists
all supported values of the action type. Permitted values depend all supported values of the action type. Permitted values depend
on the action value. Multiple values are separated with a on the action value. Multiple values are separated with a
semicolon. semicolon. Documents that make use of it are expected to explain
when it is is required, the permitted values, and how it it used.
Name: requested-state Name: requested-state
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. Indicates the requested state Description: Defined for extension. Indicates the requested state
of an element associated with the request type. Permitted values of an element associated with the request type. Permitted values
depend on the request type. depend on the request type. Documents that make use of it are
expected to explain when it is is required, the permitted values,
and how it it used.
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. Documents
that make use of it are expected to explain when it is is
required, the permitted values, and how it it used.
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">
<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. Examples
This document registers the 'emergencyCallData.eCall.MSD' INFO
package.
Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO requests carrying data
as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive eCall related body parts as specified in [TBD:
THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the
following sections.
10.1. Overall Description
This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.MSD INFO
package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information.
10.2. Applicability
This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, per
Section 6, and is normally carried in the initial INVITE and its
response; the use of INFO only occurs when emergency-call-related
data needs to be sent mid-call. While MESSAGE could be used, it is
not tied to a SIP dialog as is INFO and thus might not be associated
with the dialog. SIP OPTIONS or re-INVITE could also be used, but is
seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into
service, but the semantics are not a good fit, e.g., the subscribe/
notify mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport.
10.3. Info Package Name
The info package name is emergencyCallData.eCall.MSD
10.4. Info Package Parameters
None
10.5. SIP Option-Tags
None
10.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a
multipart (normally multipart/mixed) body containing zero or one
application/emergencyCallData.eCall.MSD+per part (containing an MSD)
and zero or more application/emergencyCallData.control+xml
(containing a 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
with how these body parts are sent in SIP messages other than 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
a Content-Disposition header field set to "By-Reference".
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
SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field). The innermost multipart that
contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package.
See [TBD: THIS DOCUMENT] for more information.
10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT].
10.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated MSD, and
for the IVS to send a requested MSD. Because this is normally done
only on manual request of the PSAP call taker (who suspects some
aspect of the vehicle state has changed), the rate of SIP INFO
requests associated with the emergencyCallData.eCall.MSD info package
is normally quite low (most dialogs are likely to contain zero INFO
requests, while others might carry an occasional request).
10.9. Info Package Security Considerations
The MIME media type registations for the data blocks that can be
carried using this INFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in eCalls.
10.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details.
10.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples.
11. Examples
Figure 6 illustrates an eCall. The call uses the request URI Figure 6 illustrates an eCall. The call uses the request URI
'urn:service:sos.ecall.automatic' service URN and is recognized as an 'urn:service:sos.ecall.automatic' service URN and is recognized as an
eCall, and further as one that was invoked automatically by the IVS eCall, and further as one that was invoked automatically by the IVS
due to a crash or other serious incident. In this example, the due to a crash or other serious incident. In this example, the
originating network routes the call to an ESInet which routes the originating network routes the call to an ESInet which routes the
call to the appropriate NG-eCall capable PSAP. The emergency call is call to the appropriate NG-eCall capable PSAP. The emergency call is
received by the ESInet's Emergency Services Routing Proxy (ESRP), as received by the ESInet's Emergency Services Routing Proxy (ESRP), as
the entry point into the ESInet. The ESRP routes the call to a PSAP, the entry point into the ESInet. The ESRP routes the call to a PSAP,
where it is received by a call taker. In deployments where there is where it is received by a call taker. In deployments where there is
skipping to change at page 22, line 40 skipping to change at page 20, line 38
|<-------------------------------------------| |<-------------------------------------------|
| | | |
|(9) end media streams | |(9) end media streams |
|............................................| |............................................|
| | | |
|(10) 200 OK | |(10) 200 OK |
|------------------------------------------->| |------------------------------------------->|
Figure 7: NG-eCall Call Flow Illustration Figure 7: NG-eCall Call Flow Illustration
The example, shown in Figure 8, illustrates a SIP eCall INVITE that The example, shown in Figure 8, illustrates a SIP eCall INVITE
contains an MSD. For simplicity, the example does not show all SIP request containing an MSD. For simplicity, the example does not show
headers, nor the SDP contents, nor does it show any additional data all SIP headers, nor the SDP contents, nor does it show any
blocks added by the IVS or the originating mobile network. Because additional data blocks added by the IVS or the originating mobile
the MSD is encoded in ASN.1 PER, which is a binary encoding, its network. Because the MSD is encoded in ASN.1 PER, which is a binary
contents cannot be included in a text document. encoding, its contents cannot be included in a text document.
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,
skipping to change at page 23, line 46 skipping to change at page 21, line 46
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 request of Figure 8, containing a control block
successful receipt of the eCall MSD. (For simplicity, the example acknowledging successful receipt of the eCall MSD. (For simplicity,
does not show all SIP headers.) the example does not show all SIP headers.)
SIP/2.0 200 OK SIP/2.0 200 OK
To: urn:service:sos.ecall.automatic;tag=8gydfe65t0 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: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
skipping to change at page 26, line 30 skipping to change at page 24, line 30
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: by-reference Content-Disposition: by-reference
...MSD in ASN.1 PER encoding goes here... ...MSD in ASN.1 PER encoding goes here...
--boundaryLine-- --boundaryLine--
Figure 11: INFO containing MSD Figure 11: INFO containing MSD
12. Security Considerations 11. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] apply here.
In addition to any network-provided location (which might be In addition to any network-provided location (which might be
determined solely by the network, or in cooperation with or possibly determined solely by the network, or in cooperation with or possibly
entirely by the originating device), an eCall carries an IVS-supplied entirely by the originating device), an eCall carries an IVS-supplied
location within the MSD. This is likely to be useful to the PSAP, location within the MSD. This is likely to be useful to the PSAP,
especially when no network-provided location is included, or when the especially when no network-provided location is included, or when the
two locations are independently determined. Even in situations where two locations are independently determined. Even in situations where
the network-supplied location is limited to the cell site, this can the network-supplied location is limited to the cell site, this can
be useful as a sanity check on the device-supplied location contained be useful as a sanity check on the device-supplied location contained
in the MSD. in the MSD.
The document [RFC7378] discusses trust issues regarding location The document [RFC7378] discusses trust issues regarding location
provided by or determined in cooperation with end devices. provided by or determined in cooperation with end devices.
Security considerations specific to the mechanism by which the PSAP Security considerations specific to the mechanism by which the PSAP
sends acknowledgments and requests to the vehicle are discussed in sends acknowledgments and requests to the vehicle are discussed in
the "Security Considerations" block of Section 15.3. Note that an the "Security Considerations" block of Section 14.4. Note that an
attacker that has access to and is capable of generating a response attacker that has access to and is capable of generating a response
to the initial INVITE request could generate a 600 (Busy Everywhere), to the initial INVITE request could generate a 600 (Busy Everywhere),
486 (Busy Here), or 603 (Decline) response that includes a metadata/ 486 (Busy Here), or 603 (Decline) response that includes a metadata/
control object containing a reference to the MSD in the initial control object containing a reference to the MSD in the initial
INVITE and a "received=true" field, which could result in the IVS INVITE and a "received=true" field, which could result in the IVS
perceiving the PSAP to be overloaded and hence not attempting to perceiving the PSAP to be overloaded and hence not attempting to
reinitiate the call. The risk can be mitigated as discussed in the reinitiate the call. The risk can be mitigated as discussed in the
"Security Considerations" block of Section 15.3. "Security Considerations" block of Section 14.4.
Data received from external sources inherently carries implementation Data received from external sources inherently carries implementation
risks. For example, depending on the platform, buffer overflows can risks. For example, depending on the platform, buffer overflows can
introduce remote code execution vulnerabilities, null characters can introduce remote code execution vulnerabilities, null characters can
corrupt strings, numeric values used for internal calculations can corrupt strings, numeric values used for internal calculations can
result in underflow/overflow errors, malformed XML objects can expose result in underflow/overflow errors, malformed XML objects can expose
parsing bugs, etc. Implementations need to be cognizant of the parsing bugs, etc. Implementations need to be cognizant of the
potential risks, observe best practices (which might include potential risks, observe best practices (which might include
sufficiently capable static code analysis, fuzz testing, component sufficiently capable static code analysis, fuzz testing, component
isolation, avoiding use of unsafe coding techniques, third-party isolation, avoiding use of unsafe coding techniques, third-party
attack tests, signed software, over-the-air updates, etc.), and have attack tests, signed software, over-the-air updates, etc.), and have
multiple levels of protection. Implementors need to be aware that, multiple levels of protection. Implementors need to be aware that,
potentially, the data objects described here and elsewhere might be potentially, the data objects described here and elsewhere (including
malformed, might contain unexpected characters, excessively long the MSD and metadata/control objects) might be malformed, might
attribute values, elements, etc. contain unexpected characters, excessively long attribute values,
elements, etc.
The security considerations discussed in [RFC7852] apply here (see The security considerations discussed in [RFC7852] apply here (see
especially the discussion of TLS, TLS versions, cypher suites, and especially the discussion of TLS, TLS versions, cypher suites, and
PKI). PKI).
When vehicle data or control/metadata is contained in a signed or When vehicle data or control/metadata is contained in a signed or
encrypted body part, the enclosing multipart (e.g., multipart/signed encrypted body part, the enclosing multipart (e.g., multipart/signed
or multipart/encrypted) has the same Content-ID as the enclosed data or multipart/encrypted) has the same Content-ID as the enclosed data
part. This allows an entity to identify and access the data blocks part. This allows an entity to identify and access the data blocks
it is interested in without having to dive deeply into the message it is interested in without having to dive deeply into the message
structure or decrypt parts it is not interested in. (The 'purpose' structure or decrypt parts it is not interested in. (The 'purpose'
parameter in a Call-Info header field identifies the data and parameter in a Call-Info header field identifies the data and
contains a CID URL pointing to the data block in the body, which has contains a CID URL pointing to the data block in the body, which has
a matching Content-ID body part header field). a matching Content-ID body part header field).
13. Privacy Considerations 12. Privacy Considerations
The privacy considerations discussed in [RFC7852] apply here. The The privacy considerations discussed in [RFC7852] apply here. The
MSD carries some identifying and personal information (mostly about MSD carries some identifying and personal information (mostly about
the vehicle and less about the owner), as well as location the vehicle and less about the owner), as well as location
information, and so needs to be protected against unauthorized information, and so needs to be protected against unauthorized
disclosure. Local regulations may impose additional privacy disclosure. Local regulations may impose additional privacy
protection requirements. protection requirements.
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 14.3.
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 14.4.
14. XML Schema 13. XML Schema
This section defines an XML schema for the control block. The text This section defines an XML schema for the control block. The text
description of the control block in Section 9.1 is normative and description of the control block in Section 9.1 is 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:control" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control"
skipping to change at page 29, line 18 skipping to change at page 27, line 18
type="xs:token" type="xs:token"
use="required"/> use="required"/>
<xs:attribute name="success" <xs:attribute name="success"
type="xs:boolean" type="xs:boolean"
use="required"/> use="required"/>
<xs:attribute name="reason" <xs:attribute name="reason"
type="xs:token"> type="xs:token">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
conditionally mandatory conditionally mandatory
when @success='false" when @success="false"
to indicate reason code to indicate reason code
for a failure for a failure
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:attribute> </xs:attribute>
<xs:attribute name="details" <xs:attribute name="details"
type="xs:string"/> type="xs:string"/>
<xs:anyAttribute <xs:anyAttribute
processContents="skip"/> processContents="skip"/>
</xs:complexType> </xs:complexType>
skipping to change at page 30, line 24 skipping to change at page 28, line 24
<xs:complexType name="requestType"> <xs:complexType name="requestType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:any namespace="##any" processContents="lax" <xs:any namespace="##any" processContents="lax"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:choice> </xs:choice>
<xs:attribute name="action" type="xs:token" <xs:attribute name="action" type="xs:token"
use="required"/> use="required"/>
<xs:attribute name="msgid" type="xs:unsignedInt"/> <xs:attribute name="int-id" type="xs:unsignedInt"/>
<xs:attribute name="persistence" <xs:attribute name="persistence"
type="xs:duration"/> type="xs:duration"/>
<xs:attribute name="datatype" type="xs:token"/> <xs:attribute name="datatype" type="xs:token"/>
<xs:attribute name="supported-values" <xs:attribute name="supported-values"
type="xs:string"/> type="xs:string"/>
<xs:attribute name="element-id" type="xs:token"/> <xs:attribute name="element-id" type="xs:token"/>
<xs:attribute name="requested-state" <xs:attribute name="requested-state"
type="xs:token"/> 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: Control Block Schema Figure 12: Control Block Schema
15. IANA Considerations 14. IANA Considerations
This document formalizes the "EmergencyCallData" media (MIME) subtype 14.1. The EmergencyCallData Media Subtree
tree. This tree is used only for content associated with emergency
communications. New subtypes in this tree can be registered by the
IETF or by other standards organizations working with emergency
communications, using the "Specification Required" rule, which
implies expert review. The designated expert is the ECRIT working
group.
15.1. Service URN Registrations This document establishes the "EmergencyCallData" media (MIME)
subtype tree, a new media subtree rooted at "application/
EmergencyCallData". This subtree is used only for content associated
with emergency communications. New subtypes in this subtree follow
the rules specified in Section 3.1 of [RFC6838], with the additional
restriction that the standards-related organization MUST be
responsible for some aspect of emergency communications.
This subtree initially contains the following subtypes (defined here
or in [RFC7852]):
emergencyCallData.control+xm
EmergencyCallData.Comment+xm
EmergencyCallData.DeviceInfo+xml
EmergencyCallData.MSD+per
EmergencyCallData.ProviderInfo+xml
EmergencyCallData.ServiceInfo+xml
EmergencyCallData.SubscriberInfo+xml
14.2. 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
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
skipping to change at page 31, line 27 skipping to change at page 29, line 40
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]. This service requests
resources associated with a test (non-emergency) call placed by an
in-vehicle system. See Section 8 for more information on the test
eCall request URN.
15.2. MIME Media Type Registration for 'application/ 14.3. 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 media 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
skipping to change at page 32, line 7 skipping to change at page 30, line 24
Encoding considerations: Uses ASN.1 PER, which is a binary Encoding considerations: Uses ASN.1 PER, which is a binary
encoding; when transported in SIP, binary content transfer encoding; when transported in SIP, binary content transfer
encoding is used. encoding is used.
Security considerations: This media type is designed to carry Security considerations: This media type is designed to carry
vehicle and incident-related data during an emergency call. This vehicle and incident-related data during an emergency call. This
data contains personal information including vehicle VIN, data contains personal information including vehicle VIN,
location, direction, etc. Appropriate precautions need to be location, direction, etc. Appropriate precautions need to be
taken to limit unauthorized access, inappropriate disclosure to taken to limit unauthorized access, inappropriate disclosure to
third parties, and eavesdropping of this information. In general, third parties, and eavesdropping of this information. Sections 9
it is acceptable for the data to be unprotected while briefly in and Section 10 of [RFC7852] contain more discussion.
transit within the Mobile Network Operator (MNO); the MNO is
trusted to not permit the data to be accessed by third parties.
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
skipping to change at page 32, line 40 skipping to change at page 31, line 5
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 Media Type Registration for 'application/ 14.4. 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 media 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
skipping to change at page 33, line 26 skipping to change at page 31, line 39
This media type carries metadata and control information and This media type carries metadata and control information and
requests, such as from a Public Safety Answering Point (PSAP) requests, such as from a Public Safety Answering Point (PSAP)
to an In-Vehicle System (IVS) during an emergency call. to an In-Vehicle System (IVS) during an emergency call.
Metadata (such as an acknowledgment that data sent by the IVS Metadata (such as an acknowledgment that data sent by the IVS
to the PSAP was successfully received) has limited privacy and to the PSAP was successfully received) has limited privacy and
security implications. Control information (such as requests security implications. Control information (such as requests
from the PSAP that the vehicle perform an action) has some from the PSAP that the vehicle perform an action) has some
privacy and security implications. The privacy concern arises privacy and security implications. The privacy concern arises
from the ability to request the vehicle to transmit a data set, from the ability to request the vehicle to transmit a data set,
which as described in Section 15.2, can contain personal which as described in Section 14.3, can contain personal
information. The security concern is the ability to request information. The security concern is the ability to request
the vehicle to perform an action. Control information needs to the vehicle to perform an action. Control information needs to
originate only from a PSAP or other emergency services originate only from a PSAP or other emergency services
provider, and not be modified en-route. The level of integrity provider, and not be modified en-route. The level of integrity
of the cellular network over which the emergency call is placed of the cellular network over which the emergency call is placed
is a consideration: when the IVS initiates an eCall over a is a consideration: when the IVS initiates an eCall over a
cellular network, in most cases it relies on the MNO to route cellular network, in most cases it relies on the MNO to route
the call to a PSAP. (Calls placed using other means, such as the call to a PSAP. (Calls placed using other means, such as
Wi-Fi or over-the-top services, generally incur somewhat higher Wi-Fi or over-the-top services, generally incur somewhat higher
levels of risk than calls placed "natively" using cellular levels of risk than calls placed "natively" using cellular
networks.) A call-back from a PSAP merits additional networks.) A call-back from a PSAP merits additional
consideration, since current mechanisms are not ideal for consideration, since current mechanisms are not ideal for
verifying that such a call is indeed a call-back from a PSAP in verifying that such a call is indeed a call-back from a PSAP in
response to an emergency call placed by the IVS. See the response to an emergency call placed by the IVS. See the
discussion in Section 12 and the PSAP Callback document discussion in Section 11 and the PSAP Callback document
[RFC7090]. [RFC7090].
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: This document Published specification: This document
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
skipping to change at page 34, line 4 skipping to change at page 32, line 16
[RFC7090]. [RFC7090].
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: This document Published specification: This document
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: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Randall Gellens, Person and email address for further information: Randall Gellens,
rg+ietf@randy.pensive.org rg+ietf@randy.pensive.org
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: The IETF ECRIT WG. Author: The IETF ECRIT WG.
Change controller: The IETF ECRIT WG. Change controller: The IETF ECRIT WG.
15.4. Registration of the 'eCall.MSD' entry in the Emergency Call 14.5. Registration of the 'eCall.MSD' entry in the Emergency Call
Additional Data Blocks registry Additional Data Types 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 Types registry, with a reference to
this document. this document; the 'Data About' value is 'The Call'.
15.5. Registration of the 'control' entry in the Emergency Call 14.6. Registration of the 'control' entry in the Emergency Call
Additional Data Blocks registry Additional Data Types registry
This specification requests IANA to add the 'control' entry to the This specification requests IANA to add the 'control' entry to the
Emergency Call Additional Data Blocks registry, with a reference to Emergency Call Additional Data Types registry, with a reference to
this document. this document; the 'Data About' value is 'The Call'.
15.6. Registration of the emergencyCallData.eCall Info Package 14.7. 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 14.8. URN Sub-Namespace Registration
15.7.1. Registration for urn:ietf:params:xml:ns:eCall 14.8.1. Registration for urn:ietf:params:xml:ns:eCall
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 URI: urn:ietf:params:xml:ns:eCall
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:
skipping to change at page 35, line 24 skipping to change at page 33, line 42
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:control 14.8.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: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:
skipping to change at page 36, line 24 skipping to change at page 34, line 26
Control Block</title> Control Block</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<h2>Control Block</h2> <h2>Control Block</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
15.8. Registry Creation 14.9. Registry Creation
This document creates a new registry called "Emergency Call Metadata/ This document creates a new registry called "Emergency Call Metadata/
Control Data". The following sub-registries are created for this Control Data". The following sub-registries are created for this
registry. registry.
15.8.1. Emergency Call Action Registry 14.9.1. Emergency Call Action Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Action". As defined in [RFC5226], this registry operates under Action". As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the proposed "Expert Review" rules. The expert should determine that the proposed
action is within the purview of a vehicle, is sufficiently action is within the purview of a vehicle, is sufficiently
distinguishable from other actions, and the action is clearly and distinguishable from other actions, and the action is clearly and
fully described. In most cases, a published and stable document is fully described. In most cases, a published and stable document is
referenced for the description of the action. referenced for the description of the action.
The content of this registry includes: The content of this registry includes:
skipping to change at page 37, line 13 skipping to change at page 35, line 17
The initial set of values is listed in Table 2. The initial set of values is listed in Table 2.
+-----------+--------------------------------------+ +-----------+--------------------------------------+
| Name | Description | | Name | Description |
+-----------+--------------------------------------+ +-----------+--------------------------------------+
| send-data | See Section 9.1.3.1 of this document | | send-data | See Section 9.1.3.1 of this document |
+-----------+--------------------------------------+ +-----------+--------------------------------------+
Table 2: Emergency Call Action Registry Initial Values Table 2: Emergency Call Action Registry Initial Values
15.8.2. Emergency Call Action Failure Reason Registry 14.9.2. Emergency Call Action Failure Reason Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Action Failure Reason" which contains values for the 'reason' Action Failure Reason" which contains values for the 'reason'
attribute of the <actionResult> element. As defined in [RFC5226], attribute of the <actionResult> element. As defined in [RFC5226],
this registry operates under "Expert Review" rules. The expert this registry operates under "Expert Review" rules. The expert
should determine that the proposed reason is sufficiently should determine that the proposed reason is sufficiently
distinguishable from other reasons and that the proposed description distinguishable from other reasons and that the proposed description
is understandable and correctly worded. is understandable and correctly worded.
The content of this registry includes: The content of this registry includes:
skipping to change at page 37, line 35 skipping to change at page 36, line 8
ID: A short string identifying the reason, for use in the 'reason' ID: A short string identifying the reason, for use in the 'reason'
attribute of an <actionResult> element. attribute of an <actionResult> element.
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. |
| | |
| damaged | Required components are damaged. | | 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. |
| | |
| unable | The action could not be accomplished (a |
| | generic error for use when no other code is |
| | appropriate). |
| | |
| unsupported | The 'action' value is not supported. |
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
Table 3: Emergency Call Action Failure Reason Registry Initial Values Table 3: Emergency Call Action Failure Reason Registry Initial Values
16. Contributors 14.10. The emergencyCallData.eCall.MSD INFO package
This document registers the 'emergencyCallData.eCall.MSD' INFO
package.
Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO requests carrying data
as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive eCall related body parts as specified in [TBD:
THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the
following sections.
14.10.1. Overall Description
This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.MSD INFO
package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information.
14.10.2. Applicability
This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...."
The use of the SIP INFO method is based on an analysis of the
requirements against the intent and effects of the INFO method versus
other approaches (which included the SIP MESSAGE method, the SIP
OPTIONS method, the SIP re-INVITE method, media plane transport, and
non-SIP protocols). In particular, the transport of emergency call
data blocks occurs within a SIP emergency dialog, per Section 6, and
is normally carried in the initial INVITE request and response; the
use of the SIP INFO method only occurs when emergency-call-related
data needs to be sent mid-call. While the SIP MESSAGE method could
be used, it is not tied to a SIP dialog as is the SIP INFO method and
thus might not be associated with the dialog. Either the SIP OPTIONS
or re-INVITE methods could also be used, but is seen as less clean
than the SIP INFO method. The SIP SUBSCRIBE/NOTIFY method could be
coerced into service, but the semantics are not a good fit, e.g., the
subscribe/notify mechanism provides one-way communication consisting
of (often multiple) notifications from notifier to subscriber
indicating that certain events in notifier have occurred, whereas
what's needed here is two-way communication of data related to the
emergency dialog. Use of the media plane mechanisms was discounted
because the number of messages needing to be exchanged in a dialog is
normally zero or very few, and the size of the data is likewise very
small. The overhead caused by user plane setup (e.g., to use MSRP as
transport) would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport.
14.10.3. Info Package Name
The info package name is emergencyCallData.eCall.MSD
14.10.4. Info Package Parameters
None
14.10.5. SIP Option-Tags
None
14.10.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a
multipart (normally multipart/mixed) body containing zero or one
application/emergencyCallData.eCall.MSD+per part (containing an MSD)
and zero or more application/emergencyCallData.control+xml
(containing a 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
with how these body parts are sent in SIP messages other than 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
a Content-Disposition header field set to "By-Reference".
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
SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field). The innermost multipart that
contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package.
See [TBD: THIS DOCUMENT] for more information.
14.10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT].
14.10.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated MSD, and
for the IVS to send a requested MSD. Because this is normally done
only on manual request of the PSAP call taker (who suspects some
aspect of the vehicle state has changed), the rate of SIP INFO
requests associated with the emergencyCallData.eCall.MSD info package
is normally quite low (most dialogs are likely to contain zero INFO
requests, while others might carry an occasional request).
14.10.9. Info Package Security Considerations
The MIME media type registrations specified for use with this INFO
package (Section 14.3 and Section 14.4) contain a discussion of the
security and/or privacy considerations specific to that data block.
The "Security Considerations" and "Privacy Considerations" sections
of [TBD: THIS DOCUMENT] discuss security and privacy considerations
of the data carried in eCalls.
14.10.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details.
14.10.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples.
15. Contributors
Brian Rosen was a co-author of the original document upon which this Brian Rosen was a co-author of the original document upon which this
document is based. document is based.
17. Acknowledgements 16. Acknowledgements
We would like to thank Bob Williams and Ban Al-Bakri for their We would like to thank Bob Williams and Ban Al-Bakri for their
feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Alissa
Drage, Stephen Edge, Wes George, Allison Mankin, Ivo Sedlacek, and Cooper, Keith Drage, Stephen Edge, Wes George, Allison Mankin, Ivo
James Winterbottom for their review and comments; Robert Sparks and Sedlacek, and James Winterbottom for their review and comments;
Paul Kyzivat for their help with the SIP mechanisms; Mark Baker and Robert Sparks and Paul Kyzivat for their help with the SIP
Ned Freed for their help with the media subtype registration issue. mechanisms; Mark Baker and Ned Freed for their help with the media
We would like to thank Michael Montag, Arnoud van Wijk, Gunnar subtype registration issue. We would like to thank Michael Montag,
Hellstrom, and Ulrich Dietz for their help with the original document Arnoud van Wijk, Gunnar Hellstrom, and Ulrich Dietz for their help
upon which this document is based. Christer Holmberg deserves with the original document upon which this document is based.
special mention for his many detailed reviews. Christer Holmberg deserves special mention for his many detailed
reviews.
18. Changes from Previous Versions 17. Changes from Previous Versions
18.1. Changes from draft-ietf-19 to draft-ietf-20 17.1. Changes from draft-ietf-19 to draft-ietf-20
o Fixed various nits o Fixed various nits
18.2. Changes from draft-ietf-18 to draft-ietf-19 17.2. Changes from draft-ietf-18 to draft-ietf-19
o Added additional text to "Rate of Info Requests" o Added additional text to "Rate of Info Requests"
o Added additional text to "Security Considerations" o Added additional text to "Security Considerations"
o Further corrected "content type" to "media type" o Further corrected "content type" to "media type"
18.3. Changes from draft-ietf-17 to draft-ietf-18 17.3. Changes from draft-ietf-17 to draft-ietf-18
o Added reference to 3GPP TS24.229 o Added reference to 3GPP TS24.229
o Clarified that an INFO request is expected to have at least one o Clarified that an INFO request is expected to have at least one
MSD or metadata/control body part MSD or metadata/control body part
o Fixed minor errors in examples o Fixed minor errors in examples
o Corrected "content type" to "media type" o Corrected "content type" to "media type"
o Deleted "xsi:schemaLocation" from examples o Deleted "xsi:schemaLocation" from examples
18.4. Changes from draft-ietf-16 to draft-ietf-17 17.4. 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.5. Changes from draft-ietf-15 to draft-ietf-16 17.5. 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.6. Changes from draft-ietf-14 to draft-ietf-15 17.6. 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.7. Changes from draft-ietf-13 to draft-ietf-14 17.7. 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.8. Changes from draft-ietf-12 to draft-ietf-13 17.8. 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.9. Changes from draft-ietf-11 to draft-ietf-12 17.9. 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.10. Changes from draft-ietf-09 to draft-ietf-11 17.10. 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.11. Changes from draft-ietf-08 to draft-ietf-09 17.11. 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.12. Changes from draft-ietf-07 to draft-ietf-08 17.12. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, and solicited MSDs control usage, such as use in rejected calls, and solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
skipping to change at page 40, line 38 skipping to change at page 42, line 4
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section 7.1 to be a subsection of 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 10 to be a main section instead of a o Moved new Section Section 14.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.13. Changes from draft-ietf-06 to draft-ietf-07 17.13. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.14. Changes from draft-ietf-05 to draft-ietf-06 17.14. 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.15. Changes from draft-ietf-04 to draft-ietf-05 17.15. 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.16. Changes from draft-ietf-03 to draft-ietf-04 17.16. 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.17. Changes from draft-ietf-02 to draft-ietf-03 17.17. 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.18. Changes from draft-ietf-01 to draft-ietf-02 17.18. 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.19. Changes from draft-ietf-00 to draft-ietf-01 17.19. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME media type for the control o Added IANA registration for the MIME media type for the control
object object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
control object control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.20. Changes from draft-gellens-03 to draft-ietf-00 17.20. 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.21. Changes from draft-gellens-02 to -03 17.21. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.22. Changes from draft-gellens-01 to -02 17.22. 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.23. Changes from draft-gellens-00 to -01 17.23. 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 18. References
19.1. Normative References
[EN_16062]
CEN, , "Intelligent transport systems - eSafety - eCall
High Level Application Requirements (HLAP) Using GSM/UMTS
Circuit Switched Networks, EN 16062", April 2015.
[EN_16072] 18.1. Normative References
CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April
2015.
[msd] CEN, , "Intelligent transport systems -- eSafety -- eCall [msd] CEN, , "Intelligent transport systems -- eSafety -- eCall
minimum set of data (MSD), EN 15722", April 2015. minimum set of data (MSD), EN 15722", April 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
skipping to change at page 43, line 38 skipping to change at page 44, line 38
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031, Emergency and Other Well-Known Services", RFC 5031,
DOI 10.17487/RFC5031, January 2008, DOI 10.17487/RFC5031, January 2008,
<http://www.rfc-editor.org/info/rfc5031>. <http://www.rfc-editor.org/info/rfc5031>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, DOI 10.17487/RFC6838, January 2013, RFC 6838, DOI 10.17487/RFC6838, January 2013,
<http://www.rfc-editor.org/info/rfc6838>. <http://www.rfc-editor.org/info/rfc6838>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>. <http://www.rfc-editor.org/info/rfc6881>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
DOI 10.17487/RFC7303, July 2014, DOI 10.17487/RFC7303, July 2014,
<http://www.rfc-editor.org/info/rfc7303>. <http://www.rfc-editor.org/info/rfc7303>.
[RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, Call", RFC 7852, DOI 10.17487/RFC7852, July 2016,
<http://www.rfc-editor.org/info/rfc7852>. <http://www.rfc-editor.org/info/rfc7852>.
[TS22.101] 18.2. Informative references
3GPP, , "3GPP TS 22.101: Technical Specification Group
Services and System Aspects; Service aspects; Service
principles".
19.2. Informative references
[CEN] "European Committee for Standardization", [CEN] "European Committee for Standardization",
<http://www.cen.eu>. <http://www.cen.eu>.
[EN_16062]
CEN, , "Intelligent transport systems - eSafety - eCall
High Level Application Requirements (HLAP) Using GSM/UMTS
Circuit Switched Networks, EN 16062", April 2015.
[EN_16072]
CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April
2015.
[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-18 (work in progress), October 2016. ecrit-car-crash-19 (work in progress), November 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>.
[RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, Emergency Call Marking and Mapping", RFC 5069,
DOI 10.17487/RFC5069, January 2008, DOI 10.17487/RFC5069, January 2008,
<http://www.rfc-editor.org/info/rfc5069>. <http://www.rfc-editor.org/info/rfc5069>.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, DOI 10.17487/RFC6443, December Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>. 2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback", Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, DOI 10.17487/RFC7090, April 2014, RFC 7090, DOI 10.17487/RFC7090, April 2014,
<http://www.rfc-editor.org/info/rfc7090>. <http://www.rfc-editor.org/info/rfc7090>.
skipping to change at page 45, line 22 skipping to change at page 46, line 22
December 2014, <http://www.rfc-editor.org/info/rfc7378>. December 2014, <http://www.rfc-editor.org/info/rfc7378>.
[SDO-3GPP] [SDO-3GPP]
"3d Generation Partnership Project", "3d Generation Partnership Project",
<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>.
[TS22.101]
3GPP, , "3GPP TS 22.101: Technical Specification Group
Services and System Aspects; Service aspects; Service
principles".
[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] [TS24.229]
3GPP, , "3GPP TS 24.229: IP multimedia call control 3GPP, , "3GPP TS 24.229: IP multimedia call control
protocol based on Session Initiation Protocol (SIP) and protocol based on Session Initiation Protocol (SIP) and
Session Description Protocol (SDP); Stage 3". Session Description Protocol (SDP); Stage 3".
Authors' Addresses Authors' Addresses
 End of changes. 118 change blocks. 
414 lines changed or deleted 462 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/