< draft-ietf-ecrit-ecall-00.txt   draft-ietf-ecrit-ecall-01.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Qualcomm Technologies, Inc. Internet-Draft Qualcomm Technologies, Inc.
Intended status: Informational H. Tschofenig Intended status: Informational H. Tschofenig
Expires: January 5, 2015 (no affiliation) Expires: April 29, 2015 (no affiliation)
July 04, 2014 October 26, 2014
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-00.txt draft-ietf-ecrit-ecall-01.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. eCall deployment is required by 2015 in calls placed by vehicles. eCall deployment is required by 2015 in
European Union member states, and eCall (and eCall-compatible European Union member states, and eCall (and eCall-compatible
skipping to change at page 2, line 7 skipping to change at page 2, line 7
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 January 5, 2015. This Internet-Draft will expire on April 29, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 3 2. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 4
3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 5 4. eCall Requirements . . . . . . . . . . . . . . . . . . . . . 6
5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 7
6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 6 6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. ESInets . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.1. ESInets . . . . . . . . . . . . . . . . . . . . . . . . . 8
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. eCall-Specific Data from PSAP to IVS . . . . . . . . . . . . 8 9. eCall-Specific Control/Metadata . . . . . . . . . . . . . . . 10
10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9.1. The eCall Control Block . . . . . . . . . . . . . . . . . 11
11. Security Considerations . . . . . . . . . . . . . . . . . . . 11 9.1.1. The 'ack' Element . . . . . . . . . . . . . . . . . . 12
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9.1.1.1. Attributes of the 'ack' Element . . . . . . . . . 12
12.1. Service URN Registration . . . . . . . . . . . . . . . . 12 9.1.1.2. Child Elements of the 'ack' Element . . . . . . . 13
12.2. MIME Content-type Registration for 9.1.2. The 'capabilities' Element . . . . . . . . . . . . . 13
'application/emergencyCallData.eCall.MSD+xml' . . . . . 12 9.1.2.1. Child Elements of the 'capabilities' Element . . 14
12.3. Registration of the 'eCall.MSD' entry in the Emergency 9.1.3. The 'request' Element . . . . . . . . . . . . . . . . 14
Call Additional Data Blocks registry . . . . . . . . . . 13 9.1.3.1. Attributes of the 'request' Element . . . . . . . 14
13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 14 9.1.3.2. Child Elements of the 'request' Element . . . . . 16
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 9.2. The emergencyCallData.eCall INFO package . . . . . . . . 17
15. Changes from Previous Versions . . . . . . . . . . . . . . . 14 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 19
15.1. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 14 11. Security Considerations . . . . . . . . . . . . . . . . . . . 20
15.2. Changes from draft-gellens-02 to -03 . . . . . . . . . . 14 12. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 21
15.3. Changes from draft-gellens-01 to -02 . . . . . . . . . . 14 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22
15.4. Changes from draft-gellens-00 to -01 . . . . . . . . . . 14 13.1. Service URN Registrations . . . . . . . . . . . . . . . 22
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 13.2. MIME Content-type Registration for
16.1. Normative References . . . . . . . . . . . . . . . . . . 15 'application/emergencyCallData.eCall.MSD+xml' . . . . . 22
16.2. Informative references . . . . . . . . . . . . . . . . . 16 13.3. MIME Content-type Registration for
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 'application/emergencyCallData.eCall.control+xml' . . . 24
13.4. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 25
13.5. Registration of the 'eCall.control' entry in the
Emergency Call Additional Data Blocks registry . . . . . 25
13.6. Registration of the emergencyCallData.eCall Info Package 26
13.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 26
13.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 26
13.7.2. Registration for
urn:ietf:params:xml:ns:eCall:control . . . . . . . . 26
13.8. Registry creation . . . . . . . . . . . . . . . . . . . 27
13.8.1. eCall Control Action Registry . . . . . . . . . . . 27
13.8.2. eCall Static Message Registry . . . . . . . . . . . 28
13.8.3. eCall Reason Registry . . . . . . . . . . . . . . . 29
13.8.4. eCall Lamp ID Registry . . . . . . . . . . . . . . . 30
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 31
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 31
16. Changes from Previous Versions . . . . . . . . . . . . . . . 31
16.1. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 31
16.2. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 32
16.3. Changes from draft-gellens-02 to -03 . . . . . . . . . . 32
16.4. Changes from draft-gellens-01 to -02 . . . . . . . . . . 32
16.5. Changes from draft-gellens-00 to -01 . . . . . . . . . . 32
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 33
17.1. Normative References . . . . . . . . . . . . . . . . . . 33
17.2. Informative references . . . . . . . . . . . . . . . . . 34
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 35
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
3GPP: 3rd Generation Partnership Project 3GPP: 3rd Generation Partnership Project
CEN: European Committee for Standardization CEN: European Committee for Standardization
EENA: European Emergency Number Association EENA: European Emergency Number Association
ESInet: Emergency Services IP network ESInet: Emergency Services IP network
IMS: Internet Multimedia Subsystem
IVS: In-Vehicle System IVS: In-Vehicle System
MNO: Mobile Network Operator MNO: Mobile Network Operator
MSD: Minimum Set of Data MSD: Minimum Set of Data
PSAP: Public Safety Answering Point PSAP: Public Safety Answering Point
2. Document Scope 2. Document Scope
This document is limited to the signaling, data exchange, and This document is limited to 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 (PS-eCall) and all-IP eCall). eCall itself as packet-switched eCall (PS-eCall) and all-IP eCall). eCall itself
is specified by 3GPP and CEN and these specifications include far is specified by 3GPP and CEN and these specifications include far
greater scope than is covered here. greater scope than is covered here.
The eCall service operates over cellular wireless communication, but
this document does not address cellular-specific details, nor client
domain selection (e.g., circuit-switched versus packet-switched).
All such aspects are the purview of their respective standards
bodies. The scope of this document is limited to eCall operating
within a SIP-based environment, such as 3GPP IMS Emergency Calling.
Vehicles designed for multiple regions may need to support eCall and
other Advanced Automatic Crash Notification systems, such as
described in [draft-ietf-ecrit-car-crash]. That system is compatible
with eCall in most respects, differing primarily in the Request-URI
and the specific data block that is sent.
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.
The European Commission initiative of eCall was conceived in the late The European Commission initiative of eCall was conceived in the late
skipping to change at page 4, line 23 skipping to change at page 5, line 15
An eCall may be either user-initiated or automatically triggered. An eCall may 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 (e.g., a fire) and carry a greater presumption of serious incident (e.g., a fire) and carry a greater presumption of
risk of injury. Manually triggered eCalls may be reports of serious risk of injury. Manually triggered eCalls may be reports of serious
hazards and are likely to require a different response than an hazards and are likely to require a different response than an
automatically triggered eCall. Manually triggered eCalls are also automatically triggered eCall. Manually triggered eCalls are also
more likely to be false (e.g., accidental) calls and may thus be more likely to be false (e.g., accidental) calls and may thus be
subject to different handling by the PSAP. subject to different handling by the PSAP.
Currently, eCall is standardized (by 3GPP [SDO-3GPP] and CEN [CEN]) Currently, eCall is standardized (by 3GPP [SDO-3GPP] and CEN [CEN])
as a 3GPP circuit-switched call over GSM (2G) or UMTS (3G). An eCall as a 3GPP circuit-switched call over GSM (2G) or UMTS (3G). Flags in
flag in the call setup marks the call as an eCall, and further the call setup mark the call as an eCall, and further indicate if the
indicates if the call was automatically or manually triggered. The call was automatically or manually triggered. The call is routed to
call is routed to an eCall-capable PSAP, a voice channel is an eCall-capable PSAP, a voice channel is established between the
established between the vehicle and the PSAP, and an eCall in-band vehicle and the PSAP, and an eCall in-band modem is used to carry a
modem is used to carry a defined set of vehicle, sensor (e.g., crash defined set of vehicle, sensor (e.g., crash related), and location
related), and location data (the Minimum Set of Data or MSD) within data (the Minimum Set of Data or MSD) within the voice channel. The
the voice channel. The same in-band mechanism is used for the PSAP same in-band mechanism is used for the PSAP to acknowledge successful
to acknowledge successful receipt of the MSD, and optionally to receipt of the MSD, and to request the vehicle to send a new MSD
request the vehicle to send a new MSD (e.g., to check if the state of (e.g., to check if the state of or location of the vehicle or its
or location of the vehicle or its occupants has changed). Work on occupants has changed). Work on next-generation eCall (NG-eCall,
next-generation eCall (NG-eCall, also referred to as packet-switched also referred to as packet-switched eCall or PS eCall) is now in
eCall or PS eCall) is now in process. As part of this work, the process. As part of this work, the European Telecommunications
European Telecommunications Standards Institute (ETSI) [SDO-ETSI] has Standards Institute (ETSI) [SDO-ETSI] has published a Technical
published a Technical Report titled "Mobile Standards Group (MSG); Report titled "Mobile Standards Group (MSG); eCall for VoIP" [MSG_TR]
eCall for VoIP" [MSG_TR] that presents findings and recommendations that presents findings and recommendations regarding support for
regarding support for eCall in an all-IP environment. NG-eCall moves eCall in an all-IP environment. NG-eCall moves from circuit switched
from circuit switched to all-IP, and carries the vehicle data and to all-IP, and carries the vehicle data and other eCall-specific data
other eCall-specific data as additional data associated with the as additional data associated with the call. This document describes
call. This document describes how IETF mechanisms for IP-based how IETF mechanisms for IP-based emergency calls, including [RFC6443]
emergency calls, including [RFC6443] and [additional-data-draft] are and [additional-data-draft] are used to provide the signaling and
used to provide the signaling and data exchange of the next data exchange of the next generation of pan-European eCall.
generation of pan-European eCall.
NG-eCall is a 3GPP IMS emergency call with additional elements
identifying the call as an eCall and as carrying eCall data and with
mechanisms for carrying the data. 3GPP IMS emergency services
support multimedia, providing the ability to carry voice, text, and
video. This capability is referred to within 3GPP as Multimedia
Emergency 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. This transition period generation eCall, legacy eCall, or both. This transition period
might last several years or longer. The issue of migration/co- might last several years or longer. The issue of migration/co-
existence during the transition period is very important but is existence during the transition period is very important but is
outside the scope of this document. The ETSI TR "Mobile Standards outside the scope of this document. The ETSI TR "Mobile Standards
Group (MSG); eCall for VoIP" [MSG_TR] discusses these issues in Group (MSG); eCall for VoIP" [MSG_TR] discusses these issues in
Clause 7. Clause 7.
skipping to change at page 6, line 11 skipping to change at page 7, line 11
(e.g., sound the horn, disable the ignition, lock/unlock doors) (e.g., sound the horn, disable the ignition, lock/unlock doors)
o The ability to avoid audio muting of the voice channel (because o The ability to avoid audio muting of the voice channel (because
the MSD is not transferred using an in-band modem) the MSD is not transferred using an in-band modem)
5. Vehicle Data 5. Vehicle Data
Pan-European eCall provides a standardized and mandated set of Pan-European eCall provides a standardized and mandated set of
vehicle related data, known as the Minimum Set of Data (MSD). The vehicle related data, known as the Minimum Set of Data (MSD). The
European Committee for Standardization (CEN) has specified this data European Committee for Standardization (CEN) has specified this data
in EN 15722 [msd], along with both ASN.1 and XML encodings for the in EN 15722 [msd], along with both ASN.1 and XML encodings for the
MSD [msd]. Circuit-switched eCall uses the ASN.1 encoding (due to MSD [msd]. Circuit-switched eCall uses the ASN.1 encoding. The XML
its more compact size). The XML encoding is better suited for use in encoding is better suited for use in SIP messages and is used in this
SIP messages and is used in this document. (The ASN.1 encoding is document. (The ASN.1 encoding is specified in Annex A of EN 15722
specified in Annex A of EN 15722 [msd], while the XML encoding is [msd], while the XML encoding is specified in Annex C.)
specified in Annex C.)
The "Additional Data related to an Emergency Call" document The "Additional Data related to an Emergency Call" document
[additional-data-draft] establishes a general mechanism for attaching [additional-data-draft] establishes a general mechanism for attaching
blocks of data to a SIP emergency call. This document makes use of blocks of data to a SIP emergency call. This document makes use of
that mechanism to carry the eCall MSD in a SIP emergency call. that mechanism to carry the eCall MSD in a SIP emergency call.
This document registers the 'application/ This document registers the 'application/
emergencyCallData.eCall.MSD+xml') MIME Content-Type to enable the MSD emergencyCallData.eCall.MSD+xml' MIME Content-Type to enable the MSD
to be carried in SIP. This document also adds the 'eCall.MSD' entry to be carried in SIP. This document also adds the 'eCall.MSD' entry
to the Emergency Call Additional Data Blocks registry (established by to the Emergency Call Additional Data Blocks registry (established by
[additional-data-draft]) to enable the MSD to be recognized as such [additional-data-draft]) to enable the MSD to be recognized as such
in a SIP-based eCall emergency call. in a SIP-based eCall emergency call.
6. Call Setup 6. Call Setup
In circuit-switched eCall, the IVS places a special form of a 112 In circuit-switched eCall, the IVS places a special form of a 112
emergency call which carries the eCall flag (indicating that the call emergency call which carries the eCall flag (indicating that the call
is an eCall and also if the call was manually or automatically is an eCall and also if the call was manually or automatically
skipping to change at page 6, line 49 skipping to change at page 7, line 48
///----\\\ 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
An In-Vehicle System (IVS) which supports NG-eCall transmits the MSD An In-Vehicle System (IVS) which supports NG-eCall transmits the MSD
in accordance with [additional-data-draft] by encoding it as in accordance with [additional-data-draft] by encoding it as
specified (per Appendix C of EN 15722 [msd]) and attaching it to an specified (per Appendix C of EN 15722 [msd]) and attaching it to an
INVITE as a MIME body part. The body part is identified by its MIME INVITE as a MIME body part. The body part is identified by its MIME
content-type 'application/emergencyCallData.eCall.MSD+xml') in the content-type ('application/emergencyCallData.eCall.MSD+xml') in the
Content-Type header field of the body part. The body part is Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header assigned a unique identifier which is listed in a Content-ID header
field in the body part. The INVITE is marked as containing the MSD field in the body part. The INVITE is marked as containing the MSD
by adding (or appending to) a Call-Info header field at the top level by adding (or appending to) a Call-Info header field at the top level
of the INVITE. This Call-Info header field contains a CID URL of the INVITE. 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 the eCall MSD per the registry parameter identifying the data as the eCall MSD per the registry
entry; the 'purpose' parameter's value is 'emergencyCallData.' and entry; the 'purpose' parameter's value is 'emergencyCallData.' and
the root of the MIME type (not including the 'emergencyCallData' the root of the MIME type (not including the 'emergencyCallData'
prefix and any suffix such as '+xml' (e.g., prefix and any suffix such as '+xml' (e.g.,
'purpose=emergencyCallData.eCall.MSD'). 'purpose=emergencyCallData.eCall.MSD').
For NG-eCall, the IVS establishes an emergency call using the 3GPP For NG-eCall, the IVS establishes an emergency call using the 3GPP
IMS solution with a Request-URI indicating an eCall type of emergency IMS solution with a Request-URI indicating an eCall type of emergency
call and with vehicle data attached; the MNO or ESInet recognizes the call and with vehicle data attached; the MNO or ESInet recognizes the
eCall URN and routes the call to a NG-eCall capable PSAP; the PSAP eCall URN and routes the call to a NG-eCall capable PSAP; the PSAP
interpets the vehicle data sent with the call and makes it available interpets the vehicle data sent with the call and makes it available
to the call taker. 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
This document registers new service URN children within the "sos" This document registers new service URN children within the "sos"
subservice. These URNs provide the mechanism by which an eCall is subservice. These URNs provide the mechanism by which an eCall is
identified, and differentiate between manually and automatically identified, and differentiate between manually and automatically
triggered eCalls (which may be subject to different treatment, triggered eCalls (which may be subject to different treatment,
depending on policy). The two service URNs are: depending on policy). The two service URNs are:
urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual
skipping to change at page 8, line 40 skipping to change at page 9, line 35
eCall-capable PSAPs that are not IP PSAPs and are not attached to an eCall-capable PSAPs that are not IP PSAPs and are not attached to an
ESInet, an originating network may need the ability to route an eCall ESInet, an originating network may need the ability to route an eCall
itself (e.g., to an interworking facility with interconnection to a itself (e.g., to an interworking facility with interconnection to a
suitable legacy eCall capable PSAP) based on the eCall and manual or suitable legacy eCall capable PSAP) based on the eCall and manual or
automatic indications. The ETSI TR "Mobile Standards Group (MSG); automatic indications. The ETSI TR "Mobile Standards Group (MSG);
eCall for VoIP" [MSG_TR] discusses transition issues in Clause 7. eCall for VoIP" [MSG_TR] discusses transition issues in Clause 7.
8. Test Calls 8. Test Calls
eCall requires the ability to place test calls. These are calls that eCall requires the ability to place test calls. These are calls that
are recognized and treated as eCalls but are not given emergency call are recognized and treated to some extent as eCalls but are not given
treatment and are not handled by call takers. emergency call treatment and are not handled by call takers. The
test call facility allows the IVS or user to verify that an eCall can
be successfully established with voice communication. The IVS can
also verify that the MSD was successfully received.
A service URN starting with "test." indicates a test call. For A service URN starting with "test." indicates a test call. For
eCall, "urn:service:test.sos.ecall" indicates such a test feature. eCall, "urn:service:test.sos.ecall" indicates such a test feature.
This functionality is defined in [RFC6881]. This functionality is defined in [RFC6881].
This document registers "urn:service:test.sos.ecall" for eCall test This document registers "urn:service:test.sos.ecall" for eCall test
calls. calls.
9. eCall-Specific Data from PSAP to IVS the current eCall test call facility is a non-emergency number so
does not get treated as an emergency call. MNOs may treat a vehicle
call in the "test" service URN in a way that tests as much
functionality as desired, but this is outside the scope of this
document.
PSAPs that have the ability to process NG-eCalls SHOULD accept test
calls and send an acknowledgment if the MSD was successfully
received, per this document. Such PSAPs MAY also play an audio clip
(for example, saying that the call reached a PSAP) in addition to
supporting media loopback per [RFC6881].
9. eCall-Specific Control/Metadata
eCall requires the ability for the PSAP to acknowledge successful eCall requires the ability for the PSAP to acknowledge successful
receipt of the MSD, and for the PSAP to optionally request that the receipt of an MSD sent by the IVS, and for the PSAP to request that
IVS send a new MSD (e.g., if the call taker wishes to see if the the IVS send an MSD (e.g., the call taker may initiate a request for
vehicle's state or location has changed). Future enhancements are a new MSD to see if the vehicle's state or location has changed).
desired, for example, to enable the PSAP to send other requests to Future enhancements are desired to enable the PSAP to send other
the vehicle, such as starting a video stream from on-board cameras requests to the vehicle, such as locking or unlocking doors, sounding
(such as rear focus or blind-spot), locking or unlocking doors, the horn, flashing the lights, starting a video stream from on-board
sounding the horn, flashing the lights, etc. cameras (such as rear focus or blind-spot), etc.
The same mechanism established in [additional-data-draft], used in The mechanism established in [additional-data-draft], used in
this document to carry the MSD from the IVS to the PSAP, can be Section 5 of this document to carry the MSD from the IVS to the PSAP,
additionally used to carry a control data block from the PSAP to the is also used to carry a block of control data from the PSAP to the
IVS. This eCall control block (also referred to as eCall metadata) IVS. This eCall control block (sometimes referred to as eCall
is an XML structure containing eCall-specific elements. When the metadata) is an XML structure containing eCall-specific elements.
PSAP needs to send an eCall control block that is in response to the When the PSAP needs to send an eCall control block that is in
MSD or other data sent by the IVS in a SIP request, the control block response to the MSD or other data sent by the IVS in a SIP request,
can be sent in the SIP response to the message that contained the MSD the control block can be sent in the SIP response to that request
or other data (e.g., the INVITE). When the PSAP needs to send an (e.g., the INVITE). When the PSAP needs to send an eCall control
eCall control block that is not an immediate response to an MSD or block that is not an immediate response to an MSD or other data sent
other data sent by the IVS, the control block can be transmitted from by the IVS, the control block can be transmitted from the PSAP to the
the PSAP to the IVS in a SIP INFO message within the established IVS in a SIP INFO message within the established session. The IVS
session. The IVS can then send any requested data (such as a new can then send any requested data (such as a new MSD) in the reply to
MSD) in the reply to the INFO message. This creates a framework the INFO message. This mechanism flexibly allows the PSAP to send
mechanism by which the PSAP can send eCall-specific data to the IVS eCall-specific data to the IVS and the IVS to respond. If control
and the IVS can respond with data if requested. If control data sent data sent in a response message requests the IVS to send a new MSD or
in a response message requests the IVS to send a new MSD or other other data block, the IVS can do so in an INFO message within the
data block, the IVS can do so in an INFO message within the session session (it could also use re-INVITE but that is unnecessary when no
(it could also use re-INVITE but that is unnecessary when no aspect aspect of the session or media is changing).
of the session or media is changing).
This mechanism requires This mechanism requires
o An XML definition of the eCall control object o An XML definition of the eCall control object
o An extension mechanism by which new elements can be added to the o An extension mechanism by which new elements can be added to the
control object definition (which may be as simple as permitting control object definition (e.g., permitting additional elements to
additional elements to be included by adding their namespace) be included by adding their namespace)
o A MIME type registration for the control object (so it can be o A MIME type registration for the control object (so it can be
carried in SIP messages and responses) carried in SIP messages and responses)
o An entry in the Emergency Call Additional Data Blocks sub-registry o An entry in the Emergency Call Additional Data Blocks sub-registry
(established by [additional-data-draft]) so that the control block (established by [additional-data-draft]) so that the control block
can be recognized as emergency call specific data within the SIP can be recognized as emergency call specific data within the SIP
messages messages
o An Info-Package registration per [RFC6086] permitting the control o An Info-Package registration per [RFC6086] permitting the control
block within Info messages block within Info messages
10. Example 9.1. The eCall Control Block
The eCall control block is an XML data structure allowing for
acknowledgments, requests, and capabilities information. It is
carried in a SIP body part with a specific MIME content type. Three
top-level elements are defined for use within an eCall control block:
ack Used in a control block sent by either side. The PSAP
uses this to acknowledge receipt of data set sent by
the IVS. The IVS uses this to acknowledge receipt of a
request by the PSAP when that request would not
otherwise be acknowledged (if the PSAP requests the
vehicle to send data and the vehicle does so, the data
serves as a success acknowledgement).
capabilities: Used in a control block sent from the IVS to the PSAP
(in the initial INVITE or subsequently if desired) to
inform the PSAP of the vehicle capabilities. Child
elements contain all actions and data types supported
by the vehicle .
request Used in a control block sent by the PSAP to the IVS, to
request the vehicle to perform an action.
Mandatory Actions (the IVS MUST support):
o Transmit data object
Optional Actions (the IVS MAY support):
o Play and/or display static (pre-defined) message
o Speak/display dynamic text (text supplied in action)
o Play dynamic audio (media supplied in SIP body part or in action)
o Flash lights, honk horn
The 'ack' element indicates the object being acknowledged, and
reports success or failure.
The 'capabilities' element has child 'request' elements to indicate
the actions supported by the IVS.
The 'request' element contains attributes to indicate the request and
to supply any needed information and MAY contain child elements
'text' and 'media' to contain the text or media for a dynamic
message. The 'action' attribute is mandatory and indicates the
specific action. An IANA registry is established by this document in
Section 13.8.1 to contain the allowed values.
New elements, child elements, and attributes can be defined with
their own sub-namespaces. IANA registries are used to specify the
permitted values of several elements and attributes. These
mechanisms allow for extension.
9.1.1. The 'ack' Element
The 'ack' element is transmitted by the PSAP to acknowledge receipt
of an eCall data object. An 'ack' element sent by a PSAP references
the unique ID of the data object that was sent by the IVS, and
further indicates if the PSAP considers the receipt successful or
not. The 'ack' element is also transmitted by the IVS to the PSAP to
acknowledge receipt of a 'request' element that requested the IVS to
perform an action other than transmitting a data object (e.g., a
request to display a message would be acknowledged, but a request to
transmit a data object would not result in a separate 'ack' element
being sent, since the data object itself serves as acknowledgment.)
An 'ack' element sent by an IVS references the unique ID of the
request being acknowledged, and further indicates whether the request
was successfully performed.
The 'ack' element has the following attributes and child elements:
9.1.1.1. Attributes of the 'ack' Element
The 'ack' element has the following attributes:
Name: ref
Usage: Mandatory
Type: anyURI
Description: References the Content-ID of the body part that
contained the data object or control object being acknowledged.
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/>
Name: rec
Usage: Mandatory
Type: Boolean
Description: Indicates if the referenced object was successfully
received or not.
Example: <ack received="yes" ref="1234567890@atlanta.example.com"/>
9.1.1.2. Child Elements of the 'ack' Element
The 'ack' element has the following child elements:
Name: ActionResult
Usage: Optional
Description: An 'ActionResult' element indicates the result of an
action (other than a 'send-data' action). It has the following
attributes:
Name: action
Usage: Mandatory
Type: token
Description: Contains the value of the 'action' attribute of the
'request' element
Name: success
Usage: Mandatory
Type: Boolean
Description: Indicates if the action was successfully
accomplished
Name: reason
Usage: Conditional
Type: token
Description: Used when 'success' is "False", this attribute
contains a reason code for a failure. A registry for reason
codes is defined in Section 13.8.3.
Name: details
Usage: optional
Type: string
Description: Contains further explanation of the circumstances of
a success or failure. The contents are implementation-specific
and human-readable.
Example: <ActionResult action="msg-dynamic" success="true"/>
Example: <ActionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/>
9.1.2. The 'capabilities' Element
The 'capabilities' element is transmitted by the IVS to indicate to
the PSAP its capabilities. No attributes are currently defined. The
following child elements may be used:
9.1.2.1. Child Elements of the 'capabilities' Element
The 'capabilities' element has the following child elements:
Name: request
Usage: Mandatory
Description: The 'capabilities' element contains a <request> child
element per action supported by the vehicle. Because support for
a 'send-data' action is REQUIRED, a <request> child element with a
"send-data" 'action' attribute is also REQUIRED. The 'supported-
datatype' attribute is REQUIRED in this <request> element and MUST
contain all eCall data blocks supported by the IVS. Currently,
only the 'eCall.MSD' datatype is defined. All other actions are
OPTIONAL. If the "play-audio" action is supported, a <request>
child element with a "play-audio" 'action' attribute is sent, with
a 'supported-mime' attribute set to all MIME content types
supported by the vehicle. If the "msg-static" action is
supported, a <request> child element with a "msg-static" 'action'
attribute is sent, with a 'msgid' attribute set to the highest
supported static message supported by the vehicle.
Examples: <request action="play-audio" supported-mime="audio/3gpp;
audio/3gpp2; audio/amr; audio/evrc"/>
<request action="send-data" supported-datatype="eCall.MSD" />
<request action="send-data" supported-datatype="eCall.MSD; VEDS;
eCall.type2" />
<request action="msg-dynamic"/>
<request action="msg.static" msgid="17" />
9.1.3. The 'request' Element
A 'request' element appears one or more times on its own or as a
child of a 'capabilities' element. The following attributes and
child elements may be used:
9.1.3.1. Attributes of the 'request' Element
The 'request' element has the following attributes:
Name: action
Usage: Mandatory
Type: token
Description: Identifies the action that the vehicle is requested to
perform. An IANA registry is established in Section 13.8.1 to
contain the allowed values.
Example: action="send-data"
Name: msgid
Usage: Conditional
Type: int
Description: Mandatory with a "msg-static" action. Indicates the
identifier of the static message to be displayed and/or spoken for
the vehicle occupants. This document established an IANA registry
for messages and their IDs, in Section 13.8.2
Example: msgid="3"
Name: persistance
Usage: Optional
Type: duration
Description: Specifies how long to carry on the specified action,
for example, how long to continue honking or flashing. If absent,
the default is indefinitely.
Example: persistance="PT1H"
Name: datatype
Usage: Conditional
Type: token
Description: Mandatory with a "send-data" action. Specifies the
data block that the IVS is requested to transmit, using the same
identifier as in the 'purpose' attribute set in a Call-Info header
field to point to the data block. Permitted values are contained
in the 'Emergency Call Data Types' IANA registry established in
[additional-data-draft].
Example: datatype="eCall.MSD"
Name: ref
Usage: Conditional
Type: URI
Description: Mandatory with a "play-audio" action. References the
audio media to be played. A CID is used to reference an audio
body part contained in the same SIP message. An external URL
(e.g., HTTP) is used to reference external content. Note that
external references might not be accessible by the vehicle due to
a variety of transient or permanent conditions.
Example: ref="cid:5432154321@example.gov"
Name: supported-mime
Usage: Conditional
Type: token
Description: Used with a 'play-audio' action in a 'request' element
that is a child of a 'capability' element, this attribute lists
all MIME content types/subtypes that the vehicle can render.
Multiple values are separated with a semicolon.
Example: supported-mime="audio/3gpp; audio/3gpp2; audio/amr; audio/
evrc"
Name: supported-datatype
Usage: Conditional
Type: token
Description: Used with a 'send-data' action in a 'request' element
that is a child of a 'capability' element, this attribute lists
all data blocks that the vehicle can transmit, using the same
identifier as in the 'purpose' attribute in a Call-Info header
field to point to the data block. Permitted values are contained
in the 'Emergency Call Data Types' IANA registry established in
[additional-data-draft]. Multiple values are separated with a
semicolon.
Example: supported-datatype="eCall.MSD; VEDS; eCall.foo"
Name: lamp-ID
Usage: Conditional
Type: token
Description: Used with a 'lamp' action, indicates which lamps the
action affects. This document creates a registry of lamp-ID
tokens, in Section 13.8.4
Example: lamp-ID="hazard"
Name: lamp-action
Usage: Conditional
Type: enumeration
Description: Used with a 'lamp' action, indicates if the lamp should
be illuminated, turned off, or flashed. Permitted values are
'on', 'off', and 'flash'.
Example: lamp-action="flash"
9.1.3.2. Child Elements of the 'request' Element
The 'request' element has the following child elements:
Name: text
Usage: Conditional
Type: string
Description: Used within a <request action="msg-dynamic"> element to
contain the text to be displayed and/or spoken (via text-to-
speech) for the vehicle occupants.
Example: <text>Emergency authorities are aware of your incident and
location. Due to a multi-vehicle incident in your area, no one is
able to speak with you right now. Please remain calm. We will
assist you soon.</text>
Name: media
Usage: Optional
Type: base64Binary
Attribute: xmime:contentType (mandatory; contains the MIME content
type of the media)
Description: MAY be used within a <request action="play-dynamic">
element to contain the media to be rendered for the vehicle
occupants. (The media may also be located in its own body part
and referenced by a CID URL, or may be external and referenced
with an external URL.)
Example: <media>Rk9STQAABeZBSUZGQ09NTQAAABIAAgAAAW4AEEANrEQAAAAAAABT
U05EAAAFwAAA
AAAAAAAAAAAAABHqEeoiISIhL1ovWjiPOI89Gz0bPK48rjdmN2YtxC3EIJ0gnRET
ERMAagBq7/3v/eEd4R3U7dTtzGTMZMghyCHIaMhozSPNI9XY1djh0uHS8ALwAv88
/zwOSQ5JG/Yb9icwJzAvFC8UMxkzGTLxMvEuuS65JtEm0RvtG+0O/g7+AQoBCvND
80PmtOa03F3cXdUL1QvRR9FH0VbRVtUa1RrcQ9xD5ifmJ/H48fj+uv66C10LXRbi
FuIgayBrJzAnMCq4KrgqwirCJ2MnYyDpIOkX5hfmDSENIQF4AXj15fXl60zrTOKG
4obcQ9xD2PPY89jV2NXb1dvV4bThtOno6ejzvPO8/mT+ZAj9CP0SuRK5Gs4aziCY
IJgjsyOzI+Uj5SE0ITQb4xvjFHMUcwt1C3UBugG6+AT4BO8Q7xDnoeeh4kXiRd9e
317fId8h4YbhhuZU5lTtGu0a9Un1Sf4y/jIHGwcbD08PTxYnFicbHxsfHdUd1R4a
Hhob+xv7F6EXoRF4EXgKAgoCAdgB2Pmz+bPyK/Ir697r3udG50bkvuS+5G3kbeZP
5k/qQepB79rv2vap9qn+Hv4eBZIFkgyADIASTxJPFowWjBjsGOwZQhlCF5IXkhQE
FAQO6g7qCLcItwHnAef7DvsO9Lf0t+9c71zrb+tv6TfpN+jd6N3qX+pf7ZPtk/I6
8jr34Pfg/h7+HgRgBGAKNAo0Dx0PHRK+Er4U0hTSFTIVMhPcE9wQ9RD1DL0MvQeT
B5MB4gHi/Cj8KPbL9svyRPJE7uju6Oz87Pzsl+yX7crtyvBn8Gf0P/Q/+PT49P4o
/igDZQNlCE0ITQx7DHsPlA+UEWQRZBHCEcIQuBC4DlgOWArfCt8GkwaTAc4Bzv0E
/QT4gfiB9Kj0qPHL8cvwIPAg77vvu/Cn8Kfyy/LL9fn1+fnh+eH+PP48AqICogbG
BsYKTQpNDPQM9A6BDoEO5Q7lDhIOEgwmDCYJRAlEBbEFsQG6Abr9r/2v+eb55vap
9qn0NfQ18rvyu/Jd8l3zFvMW9NX01fdx93H6tPq0/lX+VQIFAgUFfgV+CH8IfwrB
CsEMGwwbDHsMewvaC9oKQwpDB+MH4wTtBO0BnAGc/jz+PPsI+wj4SvhK9jX2NfTu
9O70lfSV9SH1IfaQ9pD4ufi5+237bf5z/nMBiAGIBHoEegcCBwII7gjuChsKGwp2
CnYJ+An4CK0IrQa7BrsEQgRCAX0Bff6r/qv7+vv6+aT5pPfg9+D2xvbG9m32bfba
9tr4BPgE+cz5zPwJ/An+kv6SASgBKAOhA6EFxQXFB2oHaghwCHAIwQjBCGEIYQdW
B1YFuwW7A6sDqwFfAV/+//7//L/8v/rD+sP5P/k/+E/4T/f59/n4T/hP+T/5P/q5
+rn8lvyW/rX+tQDeAN4C8gLyBMAEwAYkBiQHBwcHB1YHVgcMBwwGNAY0BN4E3gMt
Ay0BPAE8/0H/Qf1Z/Vn7tPu0+mn6afmV+ZX5SvlK+Yv5i/pK+kr7gfuB/Q79Dv7T
/tMAoQChAmACYAPoA+gFGwUbBd4F3gYkBiQF7QXtBT0FPQQkBCQCuwK7AR4BHv94
/3j93P3c/HP8c/tZ+1n6pfql+mT6ZPqR+pH7Mfsx/C38Lf14/Xj+8f7xAHQAdAHs
AewDNwM3BDgEOATjBOMFJQUlBP0E/QRwBHADgwODAlsCWwEBAQH/oP+g/kb+Rv0Y
/Rj8KPwo+4v7i/tK+0r7bftt+/D78PzE/MT90v3S/wn/CQBRAFEBjQGNAqcCpwOD
A4MEFQQVBEwETAQuBC4DugO6AwEDAQIFAgUA6ADo/7//v/6c/pz9m/2b/M78zvxL
/Ev8DvwO/Cj8KPyR/JH9O/07/iP+I/8n/ycAMgAyATwBPAIuAi4C6ALoA2UDZQOc
A5wDgwODAygDKAKNAo0BugG6AM4Azv/Y/9j+4v7i</media>
9.2. The emergencyCallData.eCall INFO package
This document registers the 'emergencyCallData.eCall' INFO package.
Both endpoints (the IVS and the PSAP equipment) set the Recv-Info
header field to 'emergencyCallData.eCall' per [RFC6086] to indicate
ability to receive INFO messages carrying eCall data or control
blocks.
Support for the 'emergencyCallData.eCall' INFO package indicates the
ability to receive eCall data and control blocks, which are carried
in a body part whose subtype starts with 'emergencyCallData.eCall.'.
At present there is only one defined eCall data block, which has the
'application/emergencyCallData.eCall.MSD+xml' MIME type, and one
eCall control block, which has the 'application/
emergencyCallData.eCall.control+xml' MIME type. The eCall control
block includes the ability for the IVS to indicate its capabilities,
so in the event additional eCall blocks are defined, the IVS can
indicate which it supports.
The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (such as SIP
MESSAGE, media plane, or non-SIP protocols). In particular, the
transport of eCall data and control blocks is done only during an
emergency session established with SIP, using the mechanism
established in [additional-data-draft], and is normally carried in
the initial INVITE and its response; the use of INFO only occurs when
a data block or request needs to be sent subsequently during the
call. While MESSAGE could be used, it is not tied to a SIP session
as is INFO. REINVITE could also be used, but is normally used to
modify the session. SUBSCRIBE/NOTIFY could be coerced into service,
but the semantics are not a clean fit. Hence, INFO is appropriate.
An INFO request message carrying an eCall data or control block has
an Info-Package header field set to 'emergencyCallData.eCall' per
[RFC6086]. The INFO request message is marked as containing the
eCall data or control block by a Call-Info header field containing a
CID URL referencing the unique identifier of the body part containing
the eCall data or control, and a 'purpose' parameter identifying the
block. Because the eCall data or control block is being carried in
an INFO request message, the body part also carries a Content-
Disposition header field set to "Info-Package".
Per [additional-data-draft], emergency call related additional data
MAY be included in any SIP message. Hence, notwithstanding
Section 4.3.2. of [RFC6086], INFO response messages MAY contain eCall
data or control blocks, provided they are included as described in
this document (with a Call-Info header field containing a CID URL
referencing the unique identifier of the body part, and a 'purpose'
parameter identifying the block). When eCall data or control blocks
are included in an INFO response message, this is done per
[additional-data-draft] and this document, and not under [RFC6086];
that is, they are included as emergency call additional data, not as
an INFO package associated data.
10. Examples
Figure 3 shows an eCall. The call uses the request URI Figure 3 shows an eCall. The call uses the request URI
'urn:service:sos.ecall.automatic' service URN and is recognized as an 'urn:service:sos.ecall.automatic' service URN and is recognized as an
eCall, and further as one that was invoked automatically by the IVS eCall, and further as one that was invoked automatically by the IVS
due to a crash or other serious incident. In this example, the due to a crash or other serious incident. In this example, the
originating network routes the call to an ESInet (as for any originating network routes the call to an ESInet (as for any
emergency call in an environment with an ESInet). The ESInet routes emergency call in an environment with an ESInet). The ESInet routes
the call to the appropriate NG-eCall capable PSAP. (In deployments the call to the appropriate NG-eCall capable PSAP. The emergency
where there is no ESInet, the originating network routes the call
directly to the appropriate NG-eCall capable PSAP.) The emergency
call is received by the ESInet's Emergency Services Routing Proxy call is received by the ESInet's Emergency Services Routing Proxy
(ESRP), as the entry point to the ESInet. The ESRP routes the call (ESRP), as the entry point into the ESInet. The ESRP routes the call
to a PSAP, where it is received by a call taker. to a PSAP, where it is received by a call taker. In deployments
where there is no ESInet, the originating network routes the call
directly to the appropriate NG-eCall capable PSAP.
+------------+ +-----------------------------------------+ +------------+ +---------------------------------------+
| | | | | | | +-------+ |
| | | +-------+ | | | | | PSAP2 | |
| | | | PSAP2 | | | | | +-------+ |
| | | +-------+ | | | | |
| | | | | | | +------+ +-------+ |
| | | +------+ +-------+ | Vehicle-->| |--+->| ESRP |---->| PSAP1 |--> Call-Taker |
Vehicle-->| |--+->| ESRP |---->| PSAP1 |---> Call-Taker | | | | +------+ +-------+ |
| | | +------+ +-------+ | | | | |
| | | | | | | +-------+ |
| | | +-------+ | | | | | PSAP3 | |
| | | | PSAP3 | | | Originating| | +-------+ |
| | | +-------+ | | Mobile | | |
| | | | | Network | | ESInet |
| Originating| | | +------------+ +---------------------------------------+
| Mobile | | |
| Network | | ESInet |
+------------+ +-----------------------------------------+
Figure 3: Example of NG-eCall Message Flow Figure 3: Example of NG-eCall Message Flow
The example, shown in Figure 4, illustrates a SIP eCall INVITE that The example, shown in Figure 4, illustrates a SIP eCall INVITE that
contains an MSD. contains an MSD.
INVITE urn:service:sos.ecall.automatic SIP/2.0 INVITE urn:service:sos.ecall.automatic SIP/2.0
To: urn:service:sos.ecall.automatic To: urn:service:sos.ecall.automatic
From: <sip:+13145551111@example.com>;tag=9fxced76sl From: <sip:+13145551111@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com Call-ID: 3848276298220188511@atlanta.example.com
Geolocation: <cid:target123@example.com> Geolocation: <cid:target123@example.com>
Geolocation-Routing: no Geolocation-Routing: no
Call-Info: cid:1234567890@atlanta.example.com; Call-Info: cid:1234567890@atlanta.example.com;
purpose=emergencyCallData.eCall.MSD purpose=emergencyCallData.eCall.MSD
Accept: application/sdp, application/pidf+xml Accept: application/sdp, application/pidf+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here ...Session Description Protocol (SDP) goes here
--boundary1 --boundary1
skipping to change at page 11, line 42 skipping to change at page 21, line 5
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 the two locations are independently determined. Even especially when the two locations are independently determined. Even
in situations where the network-supplied location is limited to the in situations where the network-supplied location is limited to the
cell site, this can be useful as a sanity check on the device- cell site, this can be useful as a sanity check on the device-
supplied location contained in the MSD. supplied location contained in the MSD.
The document [I-D.ietf-ecrit-trustworthy-location] discusses trust The document [I-D.ietf-ecrit-trustworthy-location] discusses trust
issues regarding location provided by or determined in cooperation issues regarding location provided by or determined in cooperation
with end devices. with end devices.
The mechanism by which the PSAP sends acknowledgment and optional The mechanism by which the PSAP sends acknowledgments and requests to
requests to the vehicle requires authenticity considerations; when the vehicle requires authenticity considerations; when the PSAP
the PSAP request is received within an established session initiated request is received within a session initiated by the vehicle as an
by the vehicle as an eCall emergency call, there is a higher degree eCall emergency call placed over a cellular network, there is a
of trust that the source is indeed a PSAP. If the PSAP request is higher degree of trust that the source is indeed a PSAP. If the PSAP
received in other situations, such as a call-back, the trust issues request is received in other situations, such as a call-back, the
in verifying that a call-back is indeed from a PSAP are more complex trust issues in verifying that a call-back is indeed from a PSAP are
(see the PSAP Callback document [I-D.ietf-ecrit-psap-callback]). more complex (see the PSAP Callback document [RFC7090]). A further
safeguard (applicable regardless of which end initiated the call and
the means of the call) is for the PSAP or emergency service provider
to sign the body part using a certificate issued by a known emergency
services certificate authority and for which the IVS can verify the
root certificate.
12. IANA Considerations 12. XML Schema
12.1. Service URN Registration This section defines the XML schema of the eCall control block.
<?xml version="1.0" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://example.com/ct-required"
xmlns:xmime="http://www.w3.org/2005/05/xmlmime"
targetNamespace="http://example.com/ct-required">
<xs:import namespace="http://www.w3.org/2005/05/xmlmime"
schemaLocation="http://www.w3.org/2005/05/xmlmime"/>
<!-- This element has binary content and requires the
xmime:contentType attribute which indicates the
content-type of the binary element -->
<xs:element name="media">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:base64Binary" >
<xs:attribute ref="xmime:contentType"
use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 5: eCall Control Block Schema
13. IANA Considerations
13.1. Service URN Registrations
IANA is requested to register the URN 'urn:service:sos.ecall' under IANA is requested to register the URN 'urn:service:sos.ecall' under
the sub-services 'sos' registry defined in Section 4.2 of [RFC5031]. the sub-services 'sos' registry defined in Section 4.2 of [RFC5031].
This service identifies a type of emergency call (placed by a This service identifies a type of emergency call (placed by a
specialized in-vehicle system and carrying standardized set of data specialized in-vehicle system and a carrying standardized set of data
related to the vehicle and crash or incident, and is needed to direct related to the vehicle and crash or incident, and is needed to direct
the call to a specialized public safety answering point (PSAP) with the call to a specialized public safety answering point (PSAP) with
technical and operational capabilities to handle such calls. Two technical and operational capabilities to handle such calls. Two
sub-services are registered as well, namely sub-services are registered as well, namely
urn:service:sos.ecall.manual urn:service:sos.ecall.manual
This service URN indicates that an eCall had been triggered based This service URN indicates that an eCall had been triggered based
on the manual interaction of the driver or a passenger. on the manual interaction of the driver or a passenger.
urn:service:sos.ecall.automatic urn:service:sos.ecall.automatic
This service URN indicates that an eCall had been triggered This service URN indicates that an eCall had been triggered
automatically, for example, due to a crash or other serious automatically, for example, due to a crash or other serious
incident (e.g., fire). incident (e.g., fire).
IANA is also requested to register the URN IANA is also requested to register the URN
'urn:service:test.sos.ecall' under the sub-service 'test' registry 'urn:service:test.sos.ecall' under the sub-service 'test' registry
defined in Setcion 17.2 of [RFC6881]. defined in Setcion 17.2 of [RFC6881].
12.2. MIME Content-type Registration for 'application/ 13.2. MIME Content-type Registration for 'application/
emergencyCallData.eCall.MSD+xml' emergencyCallData.eCall.MSD+xml'
This specification requests the registration of a new MIME type IANA is requested to add application/emergencyCallData.eCall.MSD+xml
according to the procedures of RFC 4288 [RFC4288] and guidelines in as a MIME content type, with a reference to this document, in
RFC 3023 [RFC3023]. accordance to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.MSD+xml MIME subtype name: emergencyCallData.eCall.MSD+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of the XML content. Indicates the character encoding of the XML content.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
vehicle and incident-related data during an emergency call. This vehicle and incident-related data during an emergency call. This
data contains personal information including vehicle VIN, data contains personal information including vehicle VIN,
location, direction, etc. Appropriate precautions need to be location, direction, etc. Appropriate precautions need to be
taken to limit unauthorized access, inappropriate disclosure to taken to limit unauthorized access, inappropriate disclosure to
third parties, and eavesdropping of this information. In general, third parties, and eavesdropping of this information. In general,
it is permissible for the data to be unprotected while briefly in it is permissible for the data to be unprotected while briefly in
transit within the Mobile Network Operator (MNO); the MNO is transit within the Mobile Network Operator (MNO); the MNO is
trusted to not permit the data to be accessed by third parties. trusted to not permit the data to be accessed by third parties.
skipping to change at page 13, line 48 skipping to change at page 24, line 5
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification was produced by the European Committee Author: This specification was produced by the European Committee
For Standardization (CEN). For contact information, please see For Standardization (CEN). For contact information, please see
<http://www.cen.eu/cen/Pages/contactus.aspx>. <http://www.cen.eu/cen/Pages/contactus.aspx>.
Change controller: The European Committee For Standardization Change controller: The European Committee For Standardization
(CEN) (CEN)
12.3. Registration of the 'eCall.MSD' entry in the Emergency Call 13.3. MIME Content-type Registration for 'application/
emergencyCallData.eCall.control+xml'
IANA is requested to add application/
emergencyCallData.eCall.control+xml as a MIME content type, with a
reference to this document, in accordance to the procedures of RFC
6838 [RFC6838] and guidelines in RFC 7303 [RFC7303].
MIME media type name: application
MIME subtype name: emergencyCallData.eCall.control+xml
Mandatory parameters: none
Optional parameters: charset
Indicates the character encoding of the XML content.
Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See
Section 3.2 of RFC 7303 [RFC7303].
Security considerations: This content type carries metadata and
control information and requests, primarily from a Public Safety
Answering Point (PSAP) to an In-Vehicle System (IVS) during an
emergency call, and also capabilities from the IVS to the PSAP.
Metadata (such as an acknowledgment that data sent by the IVS to
the PSAP was successfully received) has limited privacy and
security implications. Control information (such as requests from
the PSAP that the vehicle perform an action) has some privacy and
important security implications. The privacy concern arises from
the ability to request the vehicle to transmit a data set, which
as described in Section 13.2, may contain personal information.
The security implication is the ability to request the vehicle to
perform an action. It is important that control information
originate only from a PSAP or other emergency services provider,
and not from an impostor. The first safeguard for this is the
security of the cellular network over which the emergency call was
placed. In particular, when the IVS initiates an eCall over a
cellular network, the MNO routes the call to a PSAP. (Calls
placed using other means, such as Wi-Fi or over-the-top services,
do not carry the same degree of trust.) Calls received by the
IVS, such as a call-back from a PSAP, also do not carry the same
degree of trust, since the current mechanisms are not ideal for
verifying that such a call is indeed from a PSAP in response to an
emergency call placed by the IVS. See the discussion in
Section 11 and the PSAP Callback document [RFC7090]. A further
safeguard, and one applicable regardless of which end initiated
the call and the means of the call, is for the PSAP or emergency
service provider to sign the body part using a certificate issued
by a known emergency services certificate authority and for which
the IVS can verify the root certificate. Sections 7 and Section 8
of [I-D.ietf-ecrit-additional-data] contain more discussion.
Interoperability considerations: None
Published specification: Annex C of EN 15722 [msd]
Applications which use this media type: Pan-European eCall
compliant systems
Additional information: None
Magic Number: None
File Extension: .xml
Macintosh file type code: 'TEXT'
Person and email address for further information: Randall Gellens,
rg+ietf@qti.qualcomm.com
Intended usage: LIMITED USE
Author: The IETF ECRIT WG.
Change controller: The IETF ECRIT WG.
13.4. Registration of the 'eCall.MSD' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.MSD' entry to the This specification requests IANA to add the 'eCall.MSD' entry to the
Emergency Call Additional Data Blocks registry (established by Emergency Call Additional Data Blocks registry (established by
[additional-data-draft]), with a reference to this document. [additional-data-draft]), with a reference to this document.
13. Contributors 13.5. Registration of the 'eCall.control' entry in the Emergency Call
Additional Data Blocks registry
This specification requests IANA to add the 'eCall.control' entry to
the Emergency Call Additional Data Blocks registry (established by
[additional-data-draft]), with a reference to this document.
13.6. Registration of the emergencyCallData.eCall Info Package
IANA is requested to add emergencyCallData.eCall to the Info Packages
Registry under "Session Initiation Protocol (SIP) Parameters", with a
reference to this document.
13.7. URN Sub-Namespace Registration
13.7.1. Registration for urn:ietf:params:xml:ns:eCall
This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>.
XML:
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Namespace for eCall Data</title>
</head>
<body>
<h1>Namespace for eCall Data
</h1>
<p>See [TBD: This document].</p>
</body>
</html>
END
13.7.2. Registration for urn:ietf:params:xml:ns:eCall:control
This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall:control
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>.
XML:
BEGIN
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Namespace for eCall Data:
Control Block</title>
</head>
<body>
<h1>Namespace for eCall Data
</h1>
<h2>Control Block</h2>
<p>See [TBD: This document].</p>
</body>
</html>
END
13.8. Registry creation
This document creates a new registry called 'eCall Control Data'.
The following sub-registries are created for this registry.
13.8.1. eCall Control Action Registry
This document creates a new sub-registry called "eCall Control Action
Registry". As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the proposed
action is within the purview of a vehicle, is sufficiently
distinguishable from other actions, and the actions is clearly and
fully described. In most cases, a published and stable document is
referenced for the description of the action.
The content of this registry includes:
Name: The identifier to be used in the 'action' attribute of an
eCall control 'request' element.
Description: A description of the action. In most cases this will
be a reference to a published and stable document. The
description MUST specify if any attributes or child elements are
optional or mandatory, and describe the action to be taken by the
vehicle.
The initial set of values is listed in Table 1.
+-------------+------------------------------+
| Name | Description |
+-------------+------------------------------+
| send-data | Section xxx of this document |
| | |
| msg-static | Section xxx of this document |
| | |
| msg-dynamic | Section xxx of this document |
| | |
| play-audio | Section xxx of this document |
| | |
| honk | Section xxx of this document |
| | |
| lamp | Section xxx of this document |
+-------------+------------------------------+
Table 1: eCall Control Action Registry Initial Values
13.8.2. eCall Static Message Registry
This document creates a new sub-registry called "eCall Static Message
Registry". Because all compliant vehicles are expected to support
all static messages translated into all languages supported by the
vehicle, it is important to limit the number of such messages. As
defined in [RFC5226], this registry operates under "Publication
Required" rules, which require a stable, public document and imply
expert review of the publication. The expert should determine that
the document has been published by an appropriate emergency services
organization (e.g., NENA, EENA, APCO) and that the proposed message
is sufficiently distinguishable from other messages.
The content of this registry includes:
ID: An integer identifier to be used in the 'msgid' attribute of an
eCall control 'request' element.
Message: The text of the message. Messages are listed in the
registry in English; vehicles are expected to implement
translations into languages supported by the vehicle.
When new messages are added to the registry, the message text is
determined by the registrant; IANA assigns the IDs. Each message is
assigned a consecutive integer value as its ID. This allows an IVS
to indicate by a single integer value that it supports all messages
with that value or lower.
The initial set of values is listed in Table 2.
+----+--------------------------------------------------------------+
| ID | Message |
+----+--------------------------------------------------------------+
| 1 | Emergency authorities are aware of your incident and |
| | location. No one is free to speak with you right now. We |
| | will help you as soon as possible. |
+----+--------------------------------------------------------------+
Table 2: eCall Static Message Registry
13.8.3. eCall Reason Registry
This document creates a new sub-registry called "eCall Reason
Registry" which contains values for the 'reason' attribute of the
'ActionResult' element. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine
that the proposed reason is sufficiently distinguishable from other
reasons and that the proposed description is understandable and
correctly worded.
The content of this registry includes:
ID: A short string identifying the reason, for use in the 'reason'
attribute of an 'ActionResult' element.
Description: A description of the reason.
The initial set of values is listed in Table 3.
+------------------+------------------------------------------------+
| ID | Description |
+------------------+------------------------------------------------+
| unsupported | The 'action' is not supported. |
| | |
| unable | The 'action' could not be accomplished. |
| | |
| data-unsupported | The data item referenced in a 'send-data' |
| | request is not supported. |
+------------------+------------------------------------------------+
Table 3: eCall Reason Registry
13.8.4. eCall Lamp ID Registry
This document creates a new sub-registry called "eCall Lamp ID
Registry" to standardize the names of automotive lamps (lights). As
defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the proposed lamp name is
clearly understandable and is sufficiently distinguishable from other
lamp names.
The content of this registry includes:
Name: The identifier to be used in the 'lamp-ID' attribute of an
eCall control 'request' element.
Description: A description of the lamp (light).
The initial set of values is listed in Table 4.
+----------------+---------------------------------------------+
| Name | Description |
+----------------+---------------------------------------------+
| head | The main lamps used to light the road ahead |
| | |
| interior | Interior lamp, often at the top center |
| | |
| fog-front | Front fog lamps |
| | |
| fog-rear | Rear fog lamps |
| | |
| brake | Brake indicator lamps |
| | |
| position-front | Front position/parking/standing lamps |
| | |
| position-rear | Rear position/parking/standing lamps |
| | |
| turn-left | Left turn/directional lamps |
| | |
| turn-right | Right turn/directional lamps |
| | |
| hazard | Hazard/four-way lamps |
+----------------+---------------------------------------------+
Table 4: eCall Lamp ID Registry Initial Values
14. 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.
14. Acknowledgements 15. 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 suggestions. We would like to thank Michael Montag, feedback and suggestions, and Keith Drage for his review comments.
Arnoud van Wijk, Gunnar Hellstrom, and Ulrich Dietz for their help We would like to thank Michael Montag, Arnoud van Wijk, Gunnar
with the original document upon which this document is based. Hellstrom, and Ulrich Dietz for their help with the original document
upon which this document is based.
15. Changes from Previous Versions 16. Changes from Previous Versions
15.1. Changes from draft-gellens-03 to draft-ietf-00 16.1. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls
o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the eCall
control object
o Added IANA registries for protocol elements and tokens used in the
eCall control object
o Minor wording improvements and clarifications
16.2. 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
15.2. Changes from draft-gellens-02 to -03 16.3. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
15.3. Changes from draft-gellens-01 to -02 16.4. 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.
15.4. Changes from draft-gellens-00 to -01 16.5. 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 MIME subtypes, in accordance with changes to
[additional-data-draft] [additional-data-draft]
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
16. References 17. References
16.1. Normative References 17.1. Normative References
[EN_16072] [EN_16072]
CEN, ., "Intelligent transport systems - eSafety - Pan- CEN, , "Intelligent transport systems - eSafety - Pan-
European eCall operating requirements", December 2011. European eCall operating requirements", December 2011.
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Rosen, B., Tschofenig, H., Marshall, R., Randy, R., and J. Randy, R., Rosen, B., Tschofenig, H., Marshall, R., and J.
Winterbottom, "Additional Data related to an Emergency Winterbottom, "Additional Data related to an Emergency
Call", draft-ietf-ecrit-additional-data-15 (work in Call", draft-ietf-ecrit-additional-data-24 (work in
progress), November 2013. progress), October 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
Types", RFC 3023, January 2001. January 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", RFC 4288, December 2005.
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031, Emergency and Other Well-Known Services", RFC 5031,
January 2008. January 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Presence Information Data Format Location Object (PIDF-LO) IANA Considerations Section in RFCs", BCP 26, RFC 5226,
Usage Clarification, Considerations, and Recommendations", May 2008.
RFC 5491, March 2009.
[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.
Thomson, "Dynamic Extensions to the Presence Information
Data Format Location Object (PIDF-LO)", RFC 5962,
September 2010.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442, December
2011.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 2011. Multimedia", RFC 6443, December 2011.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013. BCP 181, RFC 6881, March 2013.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
July 2014.
[TS22.101] [TS22.101]
3GPP, ., "Technical Specification Group Services and 3GPP, , "Technical Specification Group Services and System
System Aspects; Service aspects; Service principles", . Aspects; Service aspects; Service principles", .
[additional-data-draft] [additional-data-draft]
Rosen, B., Tschofenig, H., Marshall, R., Gellens, R., and Rosen, B., Tschofenig, H., Marshall, R., Gellens, R., and
J. Winterbottom, "Additional Data related to an Emergency J. Winterbottom, "Additional Data related to an Emergency
Call", draft-ietf-ecrit-additional-data-11 (work in Call", draft-ietf-ecrit-additional-data-11 (work in
progress), July 2013. progress), July 2013.
[msd] CEN, ., "Intelligent transport systems - eSafety - eCall [msd] CEN, , "Intelligent transport systems -- eSafety -- eCall
minimum set of data (MSD), EN 15722", June 2011. minimum set of data (MSD), EN 15722", June 2011.
16.2. Informative references 17.2. Informative references
[CEN] , "European Committee for Standardization", [CEN] "European Committee for Standardization",
<http://www.cen.eu>. <http://www.cen.eu>.
[I-D.ietf-ecrit-psap-callback]
Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback",
draft-ietf-ecrit-psap-callback-13 (work in progress),
October 2013.
[I-D.ietf-ecrit-trustworthy-location] [I-D.ietf-ecrit-trustworthy-location]
Tschofenig, H., Schulzrinne, H., and B. Aboba, Tschofenig, H., Schulzrinne, H., and B. Aboba,
"Trustworthy Location", draft-ietf-ecrit-trustworthy- "Trustworthy Location", draft-ietf-ecrit-trustworthy-
location-07 (work in progress), July 2013. location-14 (work in progress), July 2014.
[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.
[RFC4481] Schulzrinne, H., "Timed Presence Extensions to the
Presence Information Data Format (PIDF) to Indicate Status
Information for Past and Future Time Intervals", RFC 4481,
July 2006.
[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, January 2008. RFC 5012, January 2008.
[RFC5069] Taylor, T., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, January Emergency Call Marking and Mapping", RFC 5069, January
2008. 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations",
RFC 5491, March 2009.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, January 2011. Framework", RFC 6086, January 2011.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442, December
2011.
[RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, April 2014.
[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 "European Telecommunications Standards Institute (ETSI)",
(ETSI)", <http://www.etsi.org>. <http://www.etsi.org>.
[draft-ietf-ecrit-car-crash]
Gellens, R., Rosen, B., and H. Tschofenig, "Next-
Generation Vehicle-Initiated Emergency Calls", draft-ietf-
ecrit-car-crash (work in progress), October 2014.
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
5775 Morehouse Drive 5775 Morehouse Drive
San Diego 92651 San Diego 92651
US US
Email: rg+ietf@qti.qualcomm.com Email: rg+ietf@qti.qualcomm.com
 End of changes. 60 change blocks. 
196 lines changed or deleted 999 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/