< draft-ietf-ecrit-ecall-15.txt   draft-ietf-ecrit-ecall-16.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: April 12, 2017 Individual Expires: April 15, 2017 Individual
October 9, 2016 October 12, 2016
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-15.txt draft-ietf-ecrit-ecall-16.txt
Abstract Abstract
This document describes how to use IP-based emergency services This document describes how to use IP-based emergency services
mechanisms to support the next generation of the Pan European in- mechanisms to support the next generation of the pan European in-
vehicle emergency call service defined under the eSafety initiative vehicle emergency call service defined under the eSafety initiative
of the European Commission (generally referred to as "eCall"). eCall of the European Commission (generally referred to as "eCall"). eCall
is a standardized and mandated system for a special form of emergency is a standardized and mandated system for a special form of emergency
calls placed by vehicles, providing real-time communications and an calls placed by vehicles, providing real-time communications and an
integrated set of related data. integrated set of related data.
This document also registers MIME Content Types and an Emergency Call This document also registers MIME Content Types and an Emergency Call
Additional Data Blocks for the eCall vehicle data and metadata/ Additional Data Block for the eCall vehicle data and metadata/control
control data. data, and an INFO package to enable carrying this data in INFO
requests.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 12, 2017. This Internet-Draft will expire on April 15, 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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 7
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 9
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 10
9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 10 9. The Metadata/Control Object . . . . . . . . . . . . . . . . . 11
9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 12 9.1. The Control Block . . . . . . . . . . . . . . . . . . . . 12
9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 13 9.1.1. The <ack> element . . . . . . . . . . . . . . . . . . 13
9.1.1.1. Attributes of the <ack> element . . . . . . . . . 13 9.1.1.1. Attributes of the <ack> element . . . . . . . . . 13
9.1.1.2. Child Element of the <ack> element . . . . . . . 13 9.1.1.2. Child Element of the <ack> element . . . . . . . 14
9.1.1.3. Ack Examples . . . . . . . . . . . . . . . . . . 14 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 . . . . . . . . . . . . . . 15
9.1.3. The <request> element . . . . . . . . . . . . . . . . 16 9.1.3. The <request> element . . . . . . . . . . . . . . . . 16
9.1.3.1. Attributes of the <request> element . . . . . . . 16 9.1.3.1. Attributes of the <request> element . . . . . . . 16
9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18 9.1.3.2. Request Example . . . . . . . . . . . . . . . . . 18
10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18 10. The emergencyCallData.eCall.MSD INFO package . . . . . . . . 18
10.1. Overall Description . . . . . . . . . . . . . . . . . . 18 10.1. Overall Description . . . . . . . . . . . . . . . . . . 18
10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19 10.2. Applicability . . . . . . . . . . . . . . . . . . . . . 19
10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19 10.3. Info Package Name . . . . . . . . . . . . . . . . . . . 19
10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19 10.4. Info Package Parameters . . . . . . . . . . . . . . . . 19
10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19 10.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 19
10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 20 10.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 20
10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20 10.7. Info Package Usage Restrictions . . . . . . . . . . . . 20
10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20 10.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 20
10.9. Info Package Security Considerations . . . . . . . . . . 20 10.9. Info Package Security Considerations . . . . . . . . . . 20
10.10. Implementation Details . . . . . . . . . . . . . . . . . 20 10.10. Implementation Details . . . . . . . . . . . . . . . . . 20
10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 20 10.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21 11. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21
12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 12. Security Considerations . . . . . . . . . . . . . . . . . . . 26
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 27
14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28 14. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 28
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
15.1. Service URN Registrations . . . . . . . . . . . . . . . 30 15.1. Service URN Registrations . . . . . . . . . . . . . . . 30
15.2. MIME Content-type Registration for 15.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+per' . . . . . 31 'application/emergencyCallData.eCall.MSD+per' . . . . . 31
15.3. MIME Content-type Registration for 15.3. MIME Content-type Registration for
'application/emergencyCallData.control+xml' . . . . . . 32 'application/emergencyCallData.control+xml' . . . . . . 32
skipping to change at page 3, line 22 skipping to change at page 3, line 24
15.6. Registration of the emergencyCallData.eCall Info Package 34 15.6. Registration of the emergencyCallData.eCall Info Package 34
15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34 15.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 34
15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34 15.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 34
15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35 15.7.2. Registration for urn:ietf:params:xml:ns:control . . 35
15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36 15.8. Registry creation . . . . . . . . . . . . . . . . . . . 36
15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36 15.8.1. Action Registry . . . . . . . . . . . . . . . . . . 36
15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37 15.8.2. Reason Registry . . . . . . . . . . . . . . . . . . 37
16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38 16. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 38
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 38
18. Changes from Previous Versions . . . . . . . . . . . . . . . 38 18. Changes from Previous Versions . . . . . . . . . . . . . . . 38
18.1. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 18.1. Changes from draft-ietf-15 to draft-ietf-16 . . . . . . 38
18.2. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38 18.2. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38
18.3. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38 18.3. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38
18.4. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 38 18.4. Changes from draft-ietf-12 to draft-ietf-13 . . . . . . 38
18.5. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39 18.5. Changes from draft-ietf-11 to draft-ietf-12 . . . . . . 39
18.6. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 18.6. Changes from draft-ietf-09 to draft-ietf-11 . . . . . . 39
18.7. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 18.7. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39
18.8. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40 18.8. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39
18.9. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40 18.9. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 40
18.10. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40 18.10. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 40
18.11. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40 18.11. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 40
18.12. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 40 18.12. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 40
18.13. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40 18.13. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 40
18.14. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41 18.14. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 41
18.15. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41 18.15. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 41
18.16. Changes from draft-gellens-02 to -03 . . . . . . . . . . 41 18.16. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 41
18.17. Changes from draft-gellens-01 to -02 . . . . . . . . . . 41 18.17. Changes from draft-gellens-02 to -03 . . . . . . . . . . 41
18.18. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42 18.18. Changes from draft-gellens-01 to -02 . . . . . . . . . . 42
18.19. Changes from draft-gellens-00 to -01 . . . . . . . . . . 42
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 42
19.1. Normative References . . . . . . . . . . . . . . . . . . 42 19.1. Normative References . . . . . . . . . . . . . . . . . . 42
19.2. Informative references . . . . . . . . . . . . . . . . . 43 19.2. Informative references . . . . . . . . . . . . . . . . . 43
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
skipping to change at page 4, line 35 skipping to change at page 4, line 43
| | | | | |
| PSAP | Public Safety Answering Point | | PSAP | Public Safety Answering Point |
+--------+----------------------------------------+ +--------+----------------------------------------+
2. Document Scope 2. Document Scope
This document is focused on the signaling, data exchange, and This document is focused on the signaling, data exchange, and
protocol needs of next-generation eCall (NG-eCall, also referred to protocol needs of next-generation eCall (NG-eCall, also referred to
as packet-switched eCall or all-IP eCall) within the SIP framework as packet-switched eCall or all-IP eCall) within the SIP framework
for emergency calls, as described in [RFC6443] and [RFC6881]. eCall for emergency calls, as described in [RFC6443] and [RFC6881]. eCall
itself is specified by 3GPP and CEN and these specifications include itself is specified by 3GPP (3rd Generation Partnership Project) and
far greater scope than is covered here. CEN (European Committee for Standardization) and these specifications
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]).
The technical contents of this document also provide a basis for The technical contents of this document also provide a basis for
reuse and extension for other vehicle-initiated emergency call reuse and extension for related emergency call systems (which is why
systems. there are extension points), but such reuse is a topic for other
documents.
Vehicles designed for multiple regions might need to support eCall Note that vehicles designed for multiple regions might need to
and other Advanced Automatic Crash Notification (AACN) systems, such support eCall and other Advanced Automatic Crash Notification (AACN)
as described in [I-D.ietf-ecrit-car-crash]. systems (such as described in [I-D.ietf-ecrit-car-crash]), but this
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
emergency services to be aware of the incident, the state of the emergency services to be aware of the incident, the state of the
vehicle, the location of the vehicle, and to have a voice channel vehicle, the location of the vehicle, and to have a voice channel
with the vehicle occupants. This enables a quick and appropriate with the vehicle occupants. This enables a quick and appropriate
response. response.
skipping to change at page 6, line 23 skipping to change at page 6, line 36
providing the ability to carry voice, text, and video. This providing the ability to carry voice, text, and video. This
capability is referred to within 3GPP as Multimedia Emergency capability is referred to within 3GPP as Multimedia Emergency
Services (MMES). Services (MMES).
A transition period will exist during which time the various entities A transition period will exist during which time the various entities
involved in initiating and handling an eCall might support next- involved in initiating and handling an eCall might support next-
generation eCall, legacy eCall, or both. The issues of migration and generation eCall, legacy eCall, or both. The issues of migration and
co-existence during the transition period are outside the scope of co-existence during the transition period are outside the scope of
this document. this document.
This document indicates how to use IP-based emergency services
mechanisms to support next-generation eCall.
This document also registers MIME Content Types and an Emergency Call
Additional Data Block for the eCall vehicle data (MSD) and metadata/
control data, and an INFO package to enable carrying this data in
INFO requests.
The MSD is carried in the MIME type 'application/ The MSD is carried in the MIME type 'application/
emergencyCallData.eCall.MSD+per' and the metadata/control block is emergencyCallData.eCall.MSD+per' and the metadata/control block is
carried in the MIME type 'application/emergencyCallData.control+xml' carried in the MIME type 'application/emergencyCallData.control+xml'
(both of which are registered in Section 15) An INFO package is (both of which are registered in Section 15) An INFO package is
defined (in Section 10) to enable these MIME types to be carried in defined (in Section 10) to enable these MIME types to be carried in
SIP INFO requests, per [RFC6086]. SIP INFO requests, per [RFC6086].
4. eCall Requirements 4. eCall Requirements
eCall requirements are specified by CEN in [EN_16072] and by 3GPP in eCall requirements are specified by CEN in [EN_16072] and by 3GPP in
skipping to change at page 8, line 12 skipping to change at page 8, line 35
SIP message. This Call-Info header field contains a CID URL SIP message. This Call-Info header field contains a CID URL
referencing the body part's unique identifier, and a 'purpose' referencing the body part's unique identifier, and a 'purpose'
parameter identifying the data as an eCall metadata/control block per parameter identifying the data as an eCall metadata/control block per
the Emergency Call Additional Data Blocks registry entry; the the Emergency Call Additional Data Blocks registry entry; the
'purpose' parameter's value is 'emergencyCallData.control'. Per 'purpose' parameter's value is 'emergencyCallData.control'. Per
[RFC6086], a metadata/control object is carried in a SIP INFO request [RFC6086], a metadata/control object is carried in a SIP INFO request
by using the INFO package defined in Section 10. by using the INFO package defined in Section 10.
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
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). Note that in some cases there might be intermediate SIP message), since as of the date of this document, the use of
multipart body parts between the top level multipart and the body Content-ID as a SIP header field is not defined (while it is defined
part containing the MSD or metadata/control object. 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 attaches an MSD to
the initial INVITE and optionally attaches a metadata/control object the initial INVITE and optionally attaches a metadata/control object
informing the PSAP of its capabilities. The MSD body part (and informing the PSAP of its capabilities. The MSD body part (and
metadata/control and PIDF-LO body parts if included) have a Content- metadata/control and PIDF-LO body parts if included) have a Content-
Disposition header field with the value "By-Reference; Disposition header field with the value "By-Reference;
handling=optional". Specifying "handling=optional" prevents the handling=optional". Specifying "handling=optional" prevents the
INVITE from being rejected if it is processed by a legacy element INVITE from being rejected if it is processed by a legacy element
(e.g., a gateway between SIP and circuit-switched environments) that (e.g., a gateway between SIP and circuit-switched environments) that
does not understand the MSD (or metadata/control object or PIDF-LO). does not understand the MSD (or metadata/control object or PIDF-LO).
The PSAP creates a metadata/control object acknowledging receipt of The PSAP creates a metadata/control object acknowledging receipt of
the MSD and attaches it to the SIP final response to the INVITE. A the MSD and attaches it to the SIP final response to the INVITE. A
metadata/control object is not attached to provisional (e.g., 180) metadata/control object is not attached to provisional (e.g., 180)
responses. responses.
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 MSD and containing "received=true" in a final response using SIP
response code 600 (Busy Everywhere), 486 (Busy Here), or 603
(Decline).
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 A PSAP can request that the vehicle send an updated MSD during a
call. To do so, the PSAP creates a metadata/control object call. To do so, the PSAP creates a metadata/control object
requesting an MSD and attaches it to a SIP INFO request and sends it requesting an MSD and attaches it to a SIP INFO request and sends it
skipping to change at page 10, line 46 skipping to change at page 11, line 27
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 vehicle- structure containing elements used for eCall and other related
initiated emergency call systems (i.e., in other regions) and emergency call systems and extension points. (This metadata/control
extension points. (This metadata/control block is in effect a high- block is in effect a high-level protocol between the PSAP and IVS.)
level protocol between the PSAP and IVS.) When the PSAP sends a When the PSAP sends a metadata/control block in response to data sent
metadata/control block in response to data sent by the IVS in a SIP by the IVS in a SIP request other than INFO (e.g., the MSD in the
request other than INFO (e.g., the MSD in the initial INVITE), the initial INVITE), the metadata/control block is sent in the SIP
metadata/control block is sent in the SIP response to that request response to that request (e.g., the response to the INVITE request).
(e.g., the response to the INVITE request). When the PSAP sends a When the PSAP sends a control block in other circumstances (e.g.,
control block in other circumstances (e.g., mid-call), the control mid-call), the control block is transmitted from the PSAP to the IVS
block is transmitted from the PSAP to the IVS in a SIP INFO request in a SIP INFO request within the established dialog. The IVS sends
within the established dialog. The IVS sends the requested data (the the requested data (the MSD) in a new INFO request (per [RFC6086]).
MSD) in a new INFO request (per [RFC6086]). This mechanism flexibly This mechanism flexibly allows the PSAP to send eCall-specific data
allows the PSAP to send eCall-specific data to the IVS and the IVS to to the IVS and the IVS to respond. INFO requests are sent using an
respond. INFO requests are sent using an appropriate INFO Package. appropriate INFO Package. See Section 6 for more information on
See Section 6 for more information on attaching a metadata/control attaching a metadata/control block to a SIP message. See Section 10
block to a SIP message. See Section 10 for information about the use for information about the use of INFO requests to carry data within
of INFO requests to carry data within an eCall. an eCall.
This mechanism requires
o An XML definition of the control object
o Extension points for use by eCall-like systems in other regions
o A MIME type registration for the control object (so it can be
carried in SIP messages and responses)
o An entry in the Emergency Call Additional Data Blocks registry so
that the control block can be recognized as emergency call
specific data within SIP messages
o An Info-Package registration per [RFC6086] permitting the
metadata/control block and the MSD within INFO requests
When the IVS includes an unsolicited MSD in a SIP request (e.g., the When the IVS includes an unsolicited MSD in a SIP request (e.g., the
initial INVITE), the PSAP sends a metadata/control block indicating initial INVITE), the PSAP sends a metadata/control block indicating
successful/unsuccessful receipt of the MSD in the SIP response to the successful/unsuccessful receipt of the MSD in the SIP response to the
request. This also informs the IVS that an NG-eCall is in operation. request. This also informs the IVS that an NG-eCall is in operation.
If the IVS receives a SIP response without the metadata/control If the IVS receives a SIP response without the metadata/control
block, it indicates that the SIP dialog is not an NG-eCall (e.g., block, it indicates that the SIP dialog is not an NG-eCall (e.g.,
some part of the call is being handled as a legacy call). When the some part of the call is being handled as a legacy call). When the
IVS sends a solicited MSD (e.g., in a SIP INFO request sent following IVS sends a solicited MSD (e.g., in a SIP INFO request sent following
receipt of a SIP INFO request containing a metadata/control block receipt of a SIP INFO request containing a metadata/control block
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; if the IVS SIP retransmission handles non-receipt of requested data; note that,
sends a requested MSD in an INFO request and does not receive a SIP per [RFC6086], a 200 OK response to an INFO request indicates only
status message for the INFO request, it resends it; if the PSAP that the receiver has successfully received and accepted the INFO
requests an MSD and does not receive a SIP status message for the request, it says nothing about the acceptability of the payload.) If
INFO request, it resends it.) If the IVS receives a request to send the IVS receives a request to send an MSD but it is unable to do so
an MSD but it is unable to do so for any reason, the IVS sends a for any reason, the IVS sends a metadata/control object acknowledging
metadata/control object acknowledging the request and containing the request and containing "success=false" and "reason" set to an
"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). The SIP response codes 600 not helpful to retry as a CS-eCall). (Note that there could be edge
(Busy Everywhere), 486 (Busy Here), and 603 (Decline) are used when cases where the PSAP response is not received by the IVS, e.g., if an
the PSAP wants to reject a call but inform the vehicle occupants that
it is aware of the situation. (Note that there could be edge cases
where the PSAP response is not received by the IVS, e.g., if an
intermediary sends a CANCEL, and an error response is forwarded intermediary sends a CANCEL, and an error response is forwarded
towards the IVS before the error response from the PSAP is received, towards the IVS before the error response from the PSAP is received,
the response will be dropped, but these are unlikely to occur here.) the response will be dropped, but these are unlikely to occur here.)
The metadata/control block is carried in the MIME type 'application/ The metadata/control block is carried in the MIME type 'application/
emergencyCallData.control+xml'. emergencyCallData.control+xml'.
The metadata/control block is designed for use with pan-European The metadata/control block is designed for use with pan-European
eCall and also eCall-like systems (i.e., in other regions), and has eCall and also eCall-like systems (i.e., in other regions), and has
extension points. Note that eCall-like systems might define their extension points. Note that eCall-like systems might define their
skipping to change at page 20, line 8 skipping to change at page 20, line 8
None None
10.5. SIP Option-Tags 10.5. SIP Option-Tags
None None
10.6. INFO Request Body Parts 10.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.MSD info package is a The body for an emergencyCallData.eCall.MSD info package is a
multipart body. Zero or one application/ multipart body which MAY contain zero or one application/
emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or emergencyCallData.eCall.MSD+per part (containing an MSD) and zero or
more application/emergencyCallData.control+xml (containing a more application/emergencyCallData.control+xml (containing a
metadata/control object) parts are permitted. Intermediate multipart metadata/control object) parts.
body parts MAY appear.
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in SIP messages other than INFO with how these body parts are sent in SIP messages other than INFO
requests, each associated body part is referenced by a Call-Info requests, each associated body part is referenced by a Call-Info
header field at the top level of the SIP message. The body part has header field at the top level of the SIP message. The body part has
a Content-Disposition header field set to "By-Reference". a Content-Disposition header field set to "By-Reference".
An MSD or metadata/control block is always enclosed in a multipart
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).
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
10.7. Info Package Usage Restrictions 10.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
10.8. Rate of INFO Requests 10.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The rate of SIP INFO requests associated with the
skipping to change at page 38, line 14 skipping to change at page 38, line 14
16. Contributors 16. 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 17. Acknowledgements
We would like to thank Bob Williams and Ban Al-Bakri for their We would like to thank Bob Williams and Ban Al-Bakri for their
feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith feedback and suggestion; Rex Buddenberg, Lena Chaponniere, Keith
Drage, Stephen Edge, Wes George, Christer Holmberg, Ivo Sedlacek, and Drage, Stephen Edge, Wes George, Ivo Sedlacek, and James Winterbottom
James Winterbottom for their review and comments; Robert Sparks and for their review and comments; Robert Sparks and Paul Kyzivat for
Paul Kyzivat for their help with the SIP mechanisms; Mark Baker and their help with the SIP mechanisms; Mark Baker and Ned Freed for
Ned Freed for their help with the media subtype registration issue. their help with the media subtype registration issue. We would like
We would like to thank Michael Montag, Arnoud van Wijk, Gunnar to thank Michael Montag, Arnoud van Wijk, Gunnar Hellstrom, and
Hellstrom, and Ulrich Dietz for their help with the original document Ulrich Dietz for their help with the original document upon which
upon which this document is based. this document is based. Christer Holmberg deserves special mention
for his many detailed reviews.
18. Changes from Previous Versions 18. Changes from Previous Versions
18.1. Changes from draft-ietf-14 to draft-ietf-15 18.1. Changes from draft-ietf-15 to draft-ietf-16
o Various clarifications and simplifications
o Added reference to 3GPP 23.167
18.2. 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.2. Changes from draft-ietf-13 to draft-ietf-14 18.3. 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.3. Changes from draft-ietf-12 to draft-ietf-13 18.4. 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.4. Changes from draft-ietf-11 to draft-ietf-12 18.5. 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.5. Changes from draft-ietf-09 to draft-ietf-11 18.6. 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.6. Changes from draft-ietf-08 to draft-ietf-09 18.7. 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.7. Changes from draft-ietf-07 to draft-ietf-08 18.8. Changes from draft-ietf-07 to draft-ietf-08
o eCall MSD now encoded as ASN.1 PER, using binary content transfer o eCall MSD now encoded as ASN.1 PER, using binary content transfer
encoding encoding
o Added text to point out aspects of call handling and metadata/ o Added text to point out aspects of call handling and metadata/
control usage, such as use in rejected calls, and solicited MSDs control usage, such as use in rejected calls, and solicited MSDs
o Revised use of INFO to require that when a request for an MSD is o Revised use of INFO to require that when a request for an MSD is
sent in INFO, the MSD sent in response is in its own INFO, not the sent in INFO, the MSD sent in response is in its own INFO, not the
response to the requesting INFO response to the requesting INFO
o Added material to INFO package registation to comply with o Added material to INFO package registation to comply with
Section 10 of [RFC6086] Section 10 of [RFC6086]
o Moved material not required by 3GPP into o Moved material not required by 3GPP into
[I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/ [I-D.ietf-ecrit-car-crash], e.g., some of the eCall metadata/
control elements, attributes, and values control elements, attributes, and values
o Revised test call wording to clarify that specific handling is out o Revised test call wording to clarify that specific handling is out
of scope of scope
o Revised wording throughout the document to simplify o Revised wording throughout the document to simplify
o Moved new Section 7.1 to be a subsection of 7 o Moved new Section 7.1 to be a subsection of 7
o Moved new Section Section 10 to be a main section instead of a o Moved new Section Section 10 to be a main section instead of a
subsection of Section 9 subsection of Section 9
o Revised SIP INFO usage and package registration per advice from o Revised SIP INFO usage and package registration per advice from
Robert Sparks and Paul Kyzivat Robert Sparks and Paul Kyzivat
18.8. Changes from draft-ietf-06 to draft-ietf-07 18.9. Changes from draft-ietf-06 to draft-ietf-07
o Fixed typo in Acknowledgements o Fixed typo in Acknowledgements
18.9. Changes from draft-ietf-05 to draft-ietf-06 18.10. 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.10. Changes from draft-ietf-04 to draft-ietf-05 18.11. 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.11. Changes from draft-ietf-03 to draft-ietf-04 18.12. 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.12. Changes from draft-ietf-02 to draft-ietf-03 18.13. 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.13. Changes from draft-ietf-01 to draft-ietf-02 18.14. 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.14. Changes from draft-ietf-00 to draft-ietf-01 18.15. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the control o Added IANA registration for the MIME content type for the control
object object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
control object control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
18.15. Changes from draft-gellens-03 to draft-ietf-00 18.16. 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.16. Changes from draft-gellens-02 to -03 18.17. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
18.17. Changes from draft-gellens-01 to -02 18.18. 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.18. Changes from draft-gellens-00 to -01 18.19. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
19. References 19. References
19.1. Normative References 19.1. Normative References
skipping to change at page 44, line 27 skipping to change at page 44, line 33
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>.
[TS23.167]
3GPP, , "3GPP TS 23.167: IP Multimedia Subsystem (IMS)
emergency sessions".
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Core Technology Consulting Core Technology Consulting
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Hannes Tschofenig Hannes Tschofenig
Individual Individual
 End of changes. 48 change blocks. 
116 lines changed or deleted 134 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/