< draft-ietf-ecrit-ecall-21.txt   draft-ietf-ecrit-ecall-22.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: June 18, 2017 Individual Expires: July 15, 2017 Individual
December 15, 2016 January 11, 2017
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-21.txt draft-ietf-ecrit-ecall-22.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of the pan European in- mechanisms to support the next generation of the pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 June 18, 2017. This Internet-Draft will expire on July 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 37 skipping to change at page 2, line 37
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 10 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 11 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11 9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11
9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 13 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 . . . . . . . . . 14 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 Element of the <capabilities> element . . . 15
9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 16 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 . . . . . . . 17
9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 18
11. Security Considerations . . . . . . . . . . . . . . . . . . . 24 11. Security Considerations . . . . . . . . . . . . . . . . . . . 24
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 25 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 25
13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26 13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 28 14.1. The EmergencyCallData Media Subtree . . . . . . . . . . 28
14.2. Service URN Registrations . . . . . . . . . . . . . . . 29 14.2. Service URN Registrations . . . . . . . . . . . . . . . 29
14.3. MIME Media Type Registration for 14.3. MIME Media Type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 29 'application/emergencyCallData.eCall.MSD+per' . . . . . 29
14.4. MIME Media Type Registration for 14.4. MIME Media Type Registration for
'application/emergencyCallData.control+xml' . . . . . . 31 'application/emergencyCallData.control+xml' . . . . . . 31
14.5. Registration of the 'eCall.MSD' entry in the Emergency 14.5. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Types registry . . . . . . . . . . 32 Call Additional Data Types registry . . . . . . . . . . 32
14.6. Registration of the 'control' entry in the Emergency 14.6. Registration of the 'control' entry in the Emergency
Call Additional Data Types registry . . . . . . . . . . 32 Call Additional Data Types registry . . . . . . . . . . 32
14.7. Registration of the emergencyCallData.eCall Info Package 33 14.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 33
14.8. URN Sub-Namespace Registration . . . . . . . . . . . . . 33 14.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33
14.8.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33 14.7.2. Registration for urn:ietf:params:xml:ns:control . . 33
14.8.2. Registration for urn:ietf:params:xml:ns:control . . 33 14.8. Registry Creation . . . . . . . . . . . . . . . . . . . 34
14.9. Registry Creation . . . . . . . . . . . . . . . . . . . 34 14.8.1. Emergency Call Action Registry . . . . . . . . . . . 34
14.9.1. Emergency Call Action Registry . . . . . . . . . . . 34 14.8.2. Emergency Call Action Failure Reason Registry . . . 35
14.9.2. Emergency Call Action Failure Reason Registry . . . 35 14.9. The emergencyCallData.eCall.MSD INFO package . . . . . . 36
14.10. The emergencyCallData.eCall.MSD INFO package . . . . . . 36 14.9.1. Overall Description . . . . . . . . . . . . . . . . 36
14.10.1. Overall Description . . . . . . . . . . . . . . . . 36 14.9.2. Applicability . . . . . . . . . . . . . . . . . . . 36
14.10.2. Applicability . . . . . . . . . . . . . . . . . . . 37 14.9.3. Info Package Name . . . . . . . . . . . . . . . . . 37
14.10.3. Info Package Name . . . . . . . . . . . . . . . . . 37 14.9.4. Info Package Parameters . . . . . . . . . . . . . . 37
14.10.4. Info Package Parameters . . . . . . . . . . . . . . 37 14.9.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 37
14.10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . 38 14.9.6. INFO Request Body Parts . . . . . . . . . . . . . . 37
14.10.6. INFO Request Body Parts . . . . . . . . . . . . . . 38 14.9.7. Info Package Usage Restrictions . . . . . . . . . . 38
14.10.7. Info Package Usage Restrictions . . . . . . . . . . 38 14.9.8. Rate of INFO Requests . . . . . . . . . . . . . . . 38
14.10.8. Rate of INFO Requests . . . . . . . . . . . . . . . 38 14.9.9. Info Package Security Considerations . . . . . . . . 38
14.10.9. Info Package Security Considerations . . . . . . . 39 14.9.10. Implementation Details . . . . . . . . . . . . . . . 38
14.10.10. Implementation Details . . . . . . . . . . . . . . 39 14.9.11. Examples . . . . . . . . . . . . . . . . . . . . . . 38
14.10.11. Examples . . . . . . . . . . . . . . . . . . . . . 39 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38
15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
17. Changes from Previous Versions . . . . . . . . . . . . . . . 39 17. Changes from Previous Versions . . . . . . . . . . . . . . . 39
17.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 39 17.1. Changes from draft-ietf-19 to draft-ietf-20 . . . . . . 39
17.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 39 17.2. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 39
17.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 40 17.3. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 39
17.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 40 17.4. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 39
17.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 40 17.5. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 39
17.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 40 17.6. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 40
17.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 40 17.7. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 40
17.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 40 17.8. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 40
17.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 40 17.9. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 40
17.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 41 17.10. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 40
17.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 41 17.11. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 41
17.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41 17.12. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41
17.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42 17.13. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 41
17.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42 17.14. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42
17.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42 17.15. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42
17.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42 17.16. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42
17.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42 17.17. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42
17.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42 17.18. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42
17.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 43 17.19. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 43
17.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 43 17.20. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 43
17.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 43 17.21. Changes from draft-gellens-02 to -03 . . . . . . . . . . 43
17.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43 17.22. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43
17.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 44 17.23. Changes from draft-gellens-00 to -01 . . . . . . . . . . 43
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
18.1. Normative References . . . . . . . . . . . . . . . . . . 44 18.1. Normative References . . . . . . . . . . . . . . . . . . 44
18.2. Informative references . . . . . . . . . . . . . . . . . 45 18.2. Informative references . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 46 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].
skipping to change at page 5, line 40 skipping to change at page 5, line 40
with the vehicle occupants. This enables a quick and appropriate with the vehicle occupants. This enables a quick and appropriate
response. response.
The European Commission initiative of eCall was conceived in the late The European Commission initiative of eCall was conceived in the late
1990s, and has evolved to a European Parliament decision requiring 1990s, and has evolved to a European Parliament decision requiring
the implementation of a compliant in-vehicle system (IVS) in new the implementation of a compliant in-vehicle system (IVS) in new
vehicles and the deployment of eCall in the European Member States in vehicles and the deployment of eCall in the European Member States in
the very near future. Other regions are developing eCall-compatible the very near future. Other regions are developing eCall-compatible
systems. systems.
The pan-European eCall system provides a standardized and mandated The pan-European eCall system is a standardized and mandated
mechanism for emergency calls by vehicles. eCall establishes mechanism for emergency calls by vehicles, providing a voice channel
procedures for such calls to be placed by in-vehicle systems, and transmission of data. eCall establishes procedures for such
recognized and processed by the mobile network, and routed to a calls to be placed by in-vehicle systems, recognized and processed by
specialized PSAP where the vehicle data is available to assist the the mobile network, and routed to a specialized PSAP where the
call taker in assessing and responding to the situation. eCall vehicle data is available to assist the call taker in assessing and
provides a standard set of vehicle, sensor (e.g., crash related), and responding to the situation. eCall provides a standard set of
location data. vehicle, sensor (e.g., crash related), and location data.
An eCall can be either user-initiated or automatically triggered. An eCall can be either user-initiated or automatically triggered.
Automatically triggered eCalls indicate a car crash or some other Automatically triggered eCalls indicate a car crash or some other
serious incident. Manually triggered eCalls might be reports of serious incident. Manually triggered eCalls might be reports of
witnessed crashes or serious hazards. PSAPs might apply specific witnessed crashes or serious hazards. PSAPs might apply specific
operational handling to manual and automatic eCalls. operational handling to manual and automatic eCalls.
Legacy eCall is standardized (by 3GPP [SDO-3GPP] and CEN [CEN]) as a Legacy eCall is standardized (by 3GPP [SDO-3GPP] and CEN [CEN]) as a
3GPP circuit-switched call over GSM (2G) or UMTS (3G). Flags in the 3GPP circuit-switched call over GSM (2G) or UMTS (3G). Flags in the
call setup mark the call as an eCall, and further indicate if the call setup mark the call as an eCall, and further indicate if the
skipping to change at page 7, line 9 skipping to change at page 7, line 9
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 SIP 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 14). An INFO package is (both of which are registered in Section 14). An INFO package is
defined (in Section 14.10) to enable these MIME types to be carried defined (in Section 14.9) to enable these MIME types to be carried in
in SIP INFO requests, per [RFC6086]. SIP INFO requests, per [RFC6086].
4. eCall Requirements 4. eCall Requirements
eCall requirements are specified by CEN in [EN_16072] and by 3GPP in eCall requirements are specified by CEN in [EN_16072] and by 3GPP in
[TS22.101] clauses 10.7 and A.27 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
skipping to change at page 7, line 50 skipping to change at page 7, line 50
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 conveying blocks of [RFC7852] establishes a general mechanism for conveying blocks of
data within a SIP emergency call. This document makes use of that data within a SIP emergency call. This document makes use of that
mechanism to include vehicle data (the MSD, see Section 5) and/or mechanism to include vehicle data (the MSD, see Section 5) and/or
metadata/control information (see Section 9) within SIP messages. metadata/control information (see Section 9) within SIP messages.
This document also registers an INFO package (in Section 14.10) to This document also registers an INFO package (in Section 14.9) to
enable eCall related data blocks to be carried in SIP INFO requests enable eCall related data blocks to be carried in SIP INFO requests
(per [RFC6086], new INFO usages require the definition of an INFO (per [RFC6086], new INFO usages require the definition of an INFO
package). 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
skipping to change at page 8, line 26 skipping to change at page 8, line 26
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 Types 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 14.10. SIP INFO request by using the INFO package defined in Section 14.9.
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 including it encoding it per the description in this document, and including it
within a SIP message as a MIME body part per [RFC7852]. The body within a SIP message as a MIME body part per [RFC7852]. The body
part is 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 Types 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 14.10. by using the INFO package defined in Section 14.9.
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".
skipping to change at page 9, line 20 skipping to change at page 9, line 20
metadata/control object informing the PSAP of its capabilities as metadata/control object informing the PSAP of its capabilities as
another body part. The MSD body part (and metadata/control and PIDF- another body part. The MSD body part (and metadata/control and PIDF-
LO body parts if included) have a Content-Disposition header field LO body parts if included) have a Content-Disposition header field
with the value "By-Reference; handling=optional". Specifying with the value "By-Reference; handling=optional". Specifying
"handling=optional" prevents the SIP INVITE request from being "handling=optional" prevents the SIP INVITE request from being
rejected if it is processed by a legacy element (e.g., a gateway rejected if it is processed by a legacy element (e.g., a gateway
between SIP and circuit-switched environments) that does not between SIP and circuit-switched environments) that does not
understand the MSD (or metadata/control object or PIDF-LO). The PSAP understand the MSD (or metadata/control object or PIDF-LO). The PSAP
creates a metadata/control object acknowledging receipt of the MSD creates a metadata/control object acknowledging receipt of the MSD
and includes it as a body part within the SIP final response to the and includes it as a body part within the SIP final response to the
SIP INVITE request per [RFC7852]. A metadata/control object is sent SIP INVITE request per [RFC7852]. A metadata/control object is not
within a provisional (e.g., 180) responses. included in 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" within a final response using the MSD and containing "received=true" within a final response using
SIP response code 600 (Busy Everywhere), 486 (Busy Here), or 603 SIP response code 600 (Busy Everywhere), 486 (Busy Here), or 603
(Decline), per [RFC7852]. (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
skipping to change at page 9, line 47 skipping to change at page 9, line 47
(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 includes it within a metadata/control object requesting an MSD and includes it within a
SIP INFO request sent within the dialog. The IVS then includes an SIP INFO request sent within the dialog. The IVS then includes an
updated MSD within 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 14.10. In addition, to align with how an package defined in Section 14.9. 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 per INFO request to reference the MSD or metadata/control block per
[RFC7852]. See Section 14.10 for information about the use of SIP [RFC7852]. See Section 14.9 for information about the use of SIP
INFO requests to carry 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
skipping to change at page 10, line 30 skipping to change at page 10, line 30
///----\\\ 112 voice call with eCall flag +------+ ///----\\\ 112 voice call with eCall flag +------+
||| IVS |||---------------------------------------->+ PSAP | ||| IVS |||---------------------------------------->+ PSAP |
\\\----/// vehicle data via eCall in-band modem +------+ \\\----/// vehicle data via eCall in-band modem +------+
Figure 1: circuit-switched eCall Figure 1: circuit-switched eCall
For NG-eCall, the IVS establishes an emergency call using a Request- For NG-eCall, the IVS establishes an emergency call using a Request-
URI indicating a manual or automatic eCall; the MNO (or ESInet) URI indicating a manual or automatic eCall; the MNO (or ESInet)
recognizes the eCall URN and routes the call to an NG-eCall capable recognizes the eCall URN and routes the call to an NG-eCall capable
PSAP; the PSAP interpets the vehicle data sent with the call and PSAP; the PSAP interprets the vehicle data sent with the call and
makes it available to the call taker. makes it available to the call taker.
///----\\\ IMS emergency call with eCall URN +------+ ///----\\\ IMS emergency call with eCall URN +------+
IVS ----------------------------------------->+ PSAP | IVS ----------------------------------------->+ PSAP |
\\\----/// vehicle data included in call setup +------+ \\\----/// vehicle data included in call setup +------+
Figure 2: NG-eCall Figure 2: NG-eCall
See Section 6 for information on how the MSD is transported within an See Section 6 for information on how the MSD is transported within an
NG-eCall. NG-eCall.
skipping to change at page 12, line 9 skipping to change at page 12, line 9
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 SIP INFO request (per the requested data (the MSD) in a new SIP INFO request (per
[RFC6086]). This mechanism flexibly allows the PSAP to send eCall- [RFC6086]). This mechanism flexibly allows the PSAP to send eCall-
specific data to the IVS and the IVS to respond. SIP INFO requests specific data to the IVS and the IVS to respond. SIP INFO requests
are sent using an appropriate SIP INFO Package. See Section 6 for are sent using an appropriate SIP INFO Package. See Section 6 for
more information on sending a metadata/control block within a SIP more information on sending a metadata/control block within a SIP
message. See Section 14.10 for information about the use of SIP INFO message. See Section 14.9 for information about the use of SIP INFO
requests to carry data within an eCall. 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
skipping to change at page 13, line 9 skipping to change at page 13, line 9
towards the IVS before the error response from the PSAP is received, towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.) the response will be dropped, but these are unlikely to occur here.)
The metadata/control block is carried in the MIME type 'application/ The metadata/control block is carried in the MIME type 'application/
emergencyCallData.control+xml'. emergencyCallData.control+xml'.
The metadata/control block is designed for use with pan-European The metadata/control block is designed for use with pan-European
eCall and also eCall-like systems (i.e., in other regions), and has eCall and also eCall-like systems (i.e., in other regions), and has
extension points. Note that eCall-like systems might define their extension points. Note that eCall-like systems might define their
own vehicle data blocks, and so might need to register a new INFO own vehicle data blocks, and so might need to register a new INFO
package to accomodate the new data MIME media type and the metadata/ package to accommodate the new data MIME media type and the metadata/
control object. control object.
9.1. The Control Block 9.1. The Control Block
The control block is an XML data structure allowing for The control block is an XML data structure allowing for
acknowledgments, requests, and capabilities information. It is acknowledgments, requests, and capabilities information. It is
carried in a body part with a specific MIME media type. Three carried in a body part with a specific MIME media type. Three
elements are defined for use within a control block: elements are defined for use within a control block:
ack Acknowledges receipt of data or a request. ack Acknowledges receipt of data or a request.
skipping to change at page 13, line 38 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 14.9.1 to contain the allowed values. Section 14.8.1 to contain the allowed values.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element acknowledges receipt of an eCall data object or The <ack> element acknowledges receipt of an eCall data object or
request. An <ack> element references the 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 15, line 10 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 14.9.2. The initial values are: codes is defined in Section 14.8.2. The initial values are:
damaged (required components are damaged), data-unsupported damaged (required components are damaged), data-unsupported
(the data item referenced in a 'send-data' request is not (the data item referenced in a 'send-data' request is not
supported), security-failure (the authenticity of the request supported), security-failure (the authenticity of the request
or the authority of the requestor could not be verified), or the authority of the requestor could not be verified),
unable (a generic error for use when no other code is unable (a generic error for use when no other code is
appropriate), and unsupported (the 'action' value is not appropriate), and unsupported (the 'action' value is not
supported). supported).
Name: details Name: details
Usage: optional Usage: optional
skipping to change at page 15, line 45 skipping to change at page 15, line 45
</emergencyCallData.control> </emergencyCallData.control>
Figure 3: Ack Example from PSAP to IVS Figure 3: Ack Example from PSAP to IVS
9.1.2. The <capabilities> element 9.1.2. The <capabilities> element
The <capabilities> element is transmitted by the IVS to indicate to The <capabilities> element is transmitted by the IVS to indicate to
the PSAP its capabilities. No attributes for this element are the PSAP its capabilities. No attributes for this element are
currently defined. The following child elements are defined: currently defined. The following child elements are defined:
9.1.2.1. Child Elements of the <capabilities> element 9.1.2.1. Child Element of the <capabilities> element
The <capabilities> element has the following child elements: The <capabilities> element has the following child element:
Name: request Name: request
Usage: Mandatory Usage: Mandatory
Description: The <capabilities> element contains a <request> child Description: The <capabilities> element contains a <request> child
element per action supported by the vehicle. element per action supported by the vehicle.
Examples: Example:
<request action="send-data" supported-values="eCall.MSD" />
<capabilities>
<request action="send-data" supported-values="eCall.MSD" />
</capabilities>
It is OPTIONAL for the IVS to support the <capabilities> element. If It is OPTIONAL for the IVS to support the <capabilities> element. If
the IVS does not send a <capabilities> element, this indicates that the IVS does not send a <capabilities> element, this indicates that
the only <request> action supported by the IVS is 'send-data' with the only <request> action supported by the IVS is 'send-data' with
'datatype' set to 'eCall.MSD'. 'datatype' set to 'eCall.MSD'.
9.1.2.2. Capabilities Example 9.1.2.2. Capabilities Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.Control <EmergencyCallData.Control
skipping to change at page 17, line 4 skipping to change at page 17, line 16
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 14.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: int-id 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. Documents that make use of Description: Defined for extensibility. Documents that make use of
it are expected to explain when it is required and how it it used. it are expected to explain when it is required and how it is used.
Example: int-id="3" Example: int-id="3"
Name: persistence Name: persistence
Usage: Optional Usage: Optional
Type: duration Type: xs: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: persistence="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
skipping to change at page 17, line 49 skipping to change at page 18, line 11
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. Documents that make use of it are expected to explain semicolon. Documents that make use of it are expected to explain
when it is is required, the permitted values, and how it it used. when it is required, the permitted values, and how it is 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. Documents that make use of it are depend on the request type. Documents that make use of it are
expected to explain when it is is required, the permitted values, expected to explain when it is required, the permitted values, and
and how it it used. how it is 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. Documents acted on. Permitted values depend on the request type. Documents
that make use of it are expected to explain when it is is that make use of it are expected to explain when it is required,
required, the permitted values, and how it it used. the permitted values, and how it is 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"/>
skipping to change at page 24, line 32 skipping to change at page 24, line 32
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
11. Security Considerations 11. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] (on marking and
routing emergency calls) 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.
skipping to change at page 25, line 27 skipping to change at page 25, line 28
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 (including potentially, the data objects described here and elsewhere (including
the MSD and metadata/control objects) might be malformed, might the MSD and metadata/control objects) might be malformed, might
contain unexpected characters, excessively long attribute values, contain unexpected characters, excessively long attribute values,
elements, etc. 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, cipher 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
skipping to change at page 26, line 15 skipping to change at page 26, line 19
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 14.4. the "Security Considerations" block of Section 14.4.
13. 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>
<![CDATA[
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"/> <xs:import namespace="http://www.w3.org/XML/1998/namespace"/>
skipping to change at page 29, line 10 skipping to change at page 29, line 11
subtype tree, a new media subtree rooted at "application/ subtype tree, a new media subtree rooted at "application/
EmergencyCallData". This subtree is used only for content associated EmergencyCallData". This subtree is used only for content associated
with emergency communications. New subtypes in this subtree follow with emergency communications. New subtypes in this subtree follow
the rules specified in Section 3.1 of [RFC6838], with the additional the rules specified in Section 3.1 of [RFC6838], with the additional
restriction that the standards-related organization MUST be restriction that the standards-related organization MUST be
responsible for some aspect of emergency communications. responsible for some aspect of emergency communications.
This subtree initially contains the following subtypes (defined here This subtree initially contains the following subtypes (defined here
or in [RFC7852]): or in [RFC7852]):
emergencyCallData.control+xm emergencyCallData.control+xml
EmergencyCallData.Comment+xm EmergencyCallData.Comment+xml
EmergencyCallData.DeviceInfo+xml EmergencyCallData.DeviceInfo+xml
EmergencyCallData.MSD+per EmergencyCallData.MSD+per
EmergencyCallData.ProviderInfo+xml EmergencyCallData.ProviderInfo+xml
EmergencyCallData.ServiceInfo+xml EmergencyCallData.ServiceInfo+xml
EmergencyCallData.SubscriberInfo+xml EmergencyCallData.SubscriberInfo+xml
14.2. Service URN Registrations 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].
skipping to change at page 33, line 5 skipping to change at page 33, line 5
Emergency Call Additional Data Types registry, with a reference to Emergency Call Additional Data Types registry, with a reference to
this document; the 'Data About' value is 'The Call'. this document; the 'Data About' value is 'The Call'.
14.6. Registration of the 'control' entry in the Emergency Call 14.6. Registration of the 'control' entry in the Emergency Call
Additional Data Types 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 Types registry, with a reference to Emergency Call Additional Data Types registry, with a reference to
this document; the 'Data About' value is 'The Call'. this document; the 'Data About' value is 'The Call'.
14.7. Registration of the emergencyCallData.eCall Info Package 14.7. URN Sub-Namespace Registration
IANA is requested to add emergencyCallData.eCall to the Info Packages
Registry under "Session Initiation Protocol (SIP) Parameters", with a
reference to this document.
14.8. URN Sub-Namespace Registration
14.8.1. Registration for urn:ietf:params:xml:ns:eCall 14.7.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 33, line 42 skipping to change at page 33, line 36
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
14.8.2. Registration for urn:ietf:params:xml:ns:control 14.7.2. Registration for urn:ietf:params:xml:ns:control
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns: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 34, line 26 skipping to change at page 34, line 24
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
14.9. Registry Creation 14.8. 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.
14.9.1. Emergency Call Action Registry 14.8.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 35, line 17 skipping to change at page 35, line 13
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
14.9.2. Emergency Call Action Failure Reason Registry 14.8.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 36, line 26 skipping to change at page 36, line 5
| | | | | |
| unable | The action could not be accomplished (a | | unable | The action could not be accomplished (a |
| | generic error for use when no other code is | | | generic error for use when no other code is |
| | appropriate). | | | appropriate). |
| | | | | |
| unsupported | The 'action' value is not supported. | | 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
14.10. The emergencyCallData.eCall.MSD INFO package 14.9. The emergencyCallData.eCall.MSD INFO package
This document registers the 'emergencyCallData.eCall.MSD' INFO This document registers the 'emergencyCallData.eCall.MSD' INFO
package. package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.MSD' in a Recv-Info header field per 'emergencyCallData.eCall.MSD' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO requests carrying data [RFC6086] to indicate ability to receive INFO requests carrying data
as described here. as described here.
Support for the 'emergencyCallData.eCall.MSD' INFO package indicates Support for the 'emergencyCallData.eCall.MSD' INFO package indicates
the ability to receive eCall related body parts as specified in [TBD: the ability to receive eCall related body parts as specified in [TBD:
THIS DOCUMENT]. THIS DOCUMENT].
An INFO request message carrying body parts related to an emergency An INFO request message carrying body parts related to an emergency
call as described in [TBD: THIS DOCUMENT] has an Info-Package header call as described in [TBD: THIS DOCUMENT] has an Info-Package header
field set to 'emergencyCallData.eCall.MSD' per [RFC6086]. field set to 'emergencyCallData.eCall.MSD' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the The requirements of Section 10 of [RFC6086] are addressed in the
following sections. following sections.
14.10.1. Overall Description 14.9.1. Overall Description
This section describes "what type of information is carried in INFO This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package." applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.MSD INFO INFO requests associated with the emergencyCallData.eCall.MSD INFO
package carry data associated with emergency calls as defined in package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs. data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information. Refer to [TBD: THIS DOCUMENT] for more information.
14.10.2. Applicability 14.9.2. Applicability
This section describes "why the Info Package mechanism, rather than This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...." 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 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 requirements against the intent and effects of the INFO method versus
other approaches (which included the SIP MESSAGE method, the SIP other approaches (which included the SIP MESSAGE method, the SIP
OPTIONS method, the SIP re-INVITE method, media plane transport, and OPTIONS method, the SIP re-INVITE method, media plane transport, and
non-SIP protocols). In particular, the transport of emergency call non-SIP protocols). In particular, the transport of emergency call
data blocks occurs within a SIP emergency dialog, per Section 6, and data blocks occurs within a SIP emergency dialog, per Section 6, and
skipping to change at page 37, line 40 skipping to change at page 37, line 19
subscribe/notify mechanism provides one-way communication consisting subscribe/notify mechanism provides one-way communication consisting
of (often multiple) notifications from notifier to subscriber of (often multiple) notifications from notifier to subscriber
indicating that certain events in notifier have occurred, whereas indicating that certain events in notifier have occurred, whereas
what's needed here is two-way communication of data related to the what's needed here is two-way communication of data related to the
emergency dialog. Use of the media plane mechanisms was discounted emergency dialog. Use of the media plane mechanisms was discounted
because the number of messages needing to be exchanged in a dialog is 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 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 small. The overhead caused by user plane setup (e.g., to use MSRP as
transport) would be disproportionately large. transport) would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide Based on the analyses, the SIP INFO method was chosen to provide for
for mid-call data transport. mid-call data transport.
14.10.3. Info Package Name 14.9.3. Info Package Name
The info package name is emergencyCallData.eCall.MSD The info package name is emergencyCallData.eCall.MSD
14.10.4. Info Package Parameters 14.9.4. Info Package Parameters
None None
14.10.5. SIP Option-Tags 14.9.5. SIP Option-Tags
None None
14.10.6. INFO Request Body Parts 14.9.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a The body for an emergencyCallData.eCall.MSD info package is a
multipart (normally multipart/mixed) body containing zero or one multipart (normally multipart/mixed) body containing zero or one
application/emergencyCallData.eCall.MSD+per part (containing an MSD) application/emergencyCallData.eCall.MSD+per part (containing an MSD)
and zero or more application/emergencyCallData.control+xml and zero or more application/emergencyCallData.control+xml
(containing a metadata/control object) parts. At least one MSD or (containing a metadata/control object) parts. At least one MSD or
metadata/control body part is expected; the behavior upon receiving metadata/control body part is expected; the behavior upon receiving
an INFO request with neither is undefined. an INFO request with neither is undefined.
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
skipping to change at page 38, line 35 skipping to change at page 38, line 12
An MSD or metadata/control block is always enclosed in a multipart An MSD or metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the body part (even if it would otherwise be the only body part in the
SIP message), since as of the date of this document, the use of SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined 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 for use as a MIME header field). The innermost multipart that
contains only body parts associated with the INFO package has a contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package. Content-Disposition value of Info-Package.
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
14.10.7. Info Package Usage Restrictions 14.9.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
14.10.8. Rate of INFO Requests 14.9.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call 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 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 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 only on manual request of the PSAP call taker (who suspects some
aspect of the vehicle state has changed), the rate of SIP INFO aspect of the vehicle state has changed), the rate of SIP INFO
requests associated with the emergencyCallData.eCall.MSD info package requests associated with the emergencyCallData.eCall.MSD info package
is normally quite low (most dialogs are likely to contain zero INFO is normally quite low (most dialogs are likely to contain zero INFO
requests, while others might carry an occasional request). requests, while others might carry an occasional request).
14.10.9. Info Package Security Considerations 14.9.9. Info Package Security Considerations
The MIME media type registrations specified for use with this INFO The MIME media type registrations specified for use with this INFO
package (Section 14.3 and Section 14.4) contain a discussion of the package (Section 14.3 and Section 14.4) contain a discussion of the
security and/or privacy considerations specific to that data block. security and/or privacy considerations specific to that data block.
The "Security Considerations" and "Privacy Considerations" sections The "Security Considerations" and "Privacy Considerations" sections
of [TBD: THIS DOCUMENT] discuss security and privacy considerations of [TBD: THIS DOCUMENT] discuss security and privacy considerations
of the data carried in eCalls. of the data carried in eCalls.
14.10.10. Implementation Details 14.9.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
14.10.11. Examples 14.9.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See [TBD: THIS DOCUMENT] for protocol examples.
15. Contributors 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.
16. Acknowledgements 16. Acknowledgements
skipping to change at page 39, line 43 skipping to change at page 39, line 21
Robert Sparks and Paul Kyzivat for their help with the SIP Robert Sparks and Paul Kyzivat for their help with the SIP
mechanisms; Mark Baker and Ned Freed for their help with the media mechanisms; Mark Baker and Ned Freed for their help with the media
subtype registration issue. We would like to thank Michael Montag, subtype registration issue. We would like to thank Michael Montag,
Arnoud van Wijk, Gunnar Hellstrom, and Ulrich Dietz for their help Arnoud van Wijk, Gunnar Hellstrom, and Ulrich Dietz for their help
with the original document upon which this document is based. with the original document upon which this document is based.
Christer Holmberg deserves special mention for his many detailed Christer Holmberg deserves special mention for his many detailed
reviews. reviews.
17. Changes from Previous Versions 17. Changes from Previous Versions
RFC Editor: Please remove this section prior to publication.
17.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
17.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"
skipping to change at page 42, line 4 skipping to change at page 41, line 38
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 14.10 to be a main section instead of a o Moved new Section Section 14.9 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
17.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
17.14. Changes from draft-ietf-05 to draft-ietf-06 17.14. Changes from draft-ietf-05 to draft-ietf-06
skipping to change at page 45, line 32 skipping to change at page 45, line 23
Circuit Switched Networks, EN 16062", April 2015. Circuit Switched Networks, EN 16062", April 2015.
[EN_16072] [EN_16072]
CEN, , "Intelligent transport systems - eSafety - Pan- CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements, EN 16072", April European eCall operating requirements, EN 16072", April
2015. 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-19 (work in progress), November 2016. ecrit-car-crash-20 (work in progress), December 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>.
 End of changes. 61 change blocks. 
104 lines changed or deleted 103 lines changed or added

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