< draft-ietf-ecrit-ecall-03.txt   draft-ietf-ecrit-ecall-04.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, 2016 Expires: April 20, 2016 (Individual)
July 4, 2015 October 18, 2015
Next-Generation Pan-European eCall Next-Generation Pan-European eCall
draft-ietf-ecrit-ecall-03.txt draft-ietf-ecrit-ecall-04.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 in the very calls placed by vehicles. eCall deployment is required in the very
near future in European Union member states, and eCall (and eCall- near future in European Union member states, and eCall (and eCall-
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, 2016. This Internet-Draft will expire on April 20, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 51 skipping to change at page 2, line 51
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 . . . . . . . . . . . . . . 16 9.1.2.2. Capabilities Example . . . . . . . . . . . . . . 16
9.1.3. The <request> element . . . . . . . . . . . . . . . . 16 9.1.3. The <request> element . . . . . . . . . . . . . . . . 16
9.1.3.1. Attributes of the <request> element . . . . . . . 17 9.1.3.1. Attributes of the <request> element . . . . . . . 17
9.1.3.2. Child Elements of the <request> element . . . . . 19 9.1.3.2. Child Elements of the <request> element . . . . . 19
9.1.3.3. Request Example . . . . . . . . . . . . . . . . . 19 9.1.3.3. Request Example . . . . . . . . . . . . . . . . . 19
9.2. The emergencyCallData.eCall INFO package . . . . . . . . 20 9.2. The emergencyCallData.eCall INFO package . . . . . . . . 20
10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21 10. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Security Considerations . . . . . . . . . . . . . . . . . . . 25 11. Security Considerations . . . . . . . . . . . . . . . . . . . 25
12. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 26
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29 13. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 26
13.1. Service URN Registrations . . . . . . . . . . . . . . . 29 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
13.2. MIME Content-type Registration for 14.1. Service URN Registrations . . . . . . . . . . . . . . . 29
14.2. MIME Content-type Registration for
'application/emergencyCallData.eCall.MSD+xml' . . . . . 30 'application/emergencyCallData.eCall.MSD+xml' . . . . . 30
13.3. MIME Content-type Registration for 14.3. MIME Content-type Registration for
'application/emergencyCallData.eCall.control+xml' . . . 31 'application/emergencyCallData.eCall.control+xml' . . . 31
13.4. Registration of the 'eCall.MSD' entry in the Emergency 14.4. Registration of the 'eCall.MSD' entry in the Emergency
Call Additional Data Blocks registry . . . . . . . . . . 32 Call Additional Data Blocks registry . . . . . . . . . . 33
13.5. Registration of the 'eCall.control' entry in the 14.5. Registration of the 'eCall.control' entry in the
Emergency Call Additional Data Blocks registry . . . . . 33 Emergency Call Additional Data Blocks registry . . . . . 33
13.6. Registration of the emergencyCallData.eCall Info Package 33 14.6. Registration of the emergencyCallData.eCall Info Package 33
13.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 33 14.7. URN Sub-Namespace Registration . . . . . . . . . . . . . 33
13.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33 14.7.1. Registration for urn:ietf:params:xml:ns:eCall . . . 33
13.7.2. Registration for 14.7.2. Registration for
urn:ietf:params:xml:ns:eCall:control . . . . . . . . 34 urn:ietf:params:xml:ns:eCall:control . . . . . . . . 34
13.8. Registry creation . . . . . . . . . . . . . . . . . . . 34 14.8. Registry creation . . . . . . . . . . . . . . . . . . . 35
13.8.1. eCall Control Action Registry . . . . . . . . . . . 34 14.8.1. eCall Control Action Registry . . . . . . . . . . . 35
13.8.2. eCall Static Message Registry . . . . . . . . . . . 35 14.8.2. eCall Static Message Registry . . . . . . . . . . . 36
13.8.3. eCall Reason Registry . . . . . . . . . . . . . . . 36 14.8.3. eCall Reason Registry . . . . . . . . . . . . . . . 37
13.8.4. eCall Lamp ID Registry . . . . . . . . . . . . . . . 37 14.8.4. eCall Lamp ID Registry . . . . . . . . . . . . . . . 37
13.8.5. eCall Camera ID Registry . . . . . . . . . . . . . . 38 14.8.5. eCall Camera ID Registry . . . . . . . . . . . . . . 38
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39 15. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 39
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
16. Changes from Previous Versions . . . . . . . . . . . . . . . 39 17. Changes from Previous Versions . . . . . . . . . . . . . . . 39
16.1. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 17.1. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
16.2. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 17.2. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39
16.3. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40 17.3. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40
16.4. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 40 17.4. Changes from draft-gellens-03 to draft-ietf-00 . . . . . 40
16.5. Changes from draft-gellens-02 to -03 . . . . . . . . . . 40 17.5. Changes from draft-gellens-02 to -03 . . . . . . . . . . 40
16.6. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40 17.6. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40
16.7. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40 17.7. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
17.1. Normative References . . . . . . . . . . . . . . . . . . 41 18.1. Normative References . . . . . . . . . . . . . . . . . . 41
17.2. Informative references . . . . . . . . . . . . . . . . . 42 18.2. Informative references . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
skipping to change at page 4, line 35 skipping to change at page 4, line 35
[RFC6881]. eCall itself is specified by 3GPP and CEN and these [RFC6881]. eCall itself is specified by 3GPP and CEN and these
specifications include far greater scope than is covered here. 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).
The technical contents of this document may be suitable for use in The technical contents of this document can be suitable for use in
other vehicle-initiated emergency call systems, but this is out of other vehicle-initiated emergency call systems, but this is out of
scope for this document. scope for this document.
Vehicles designed for multiple regions may need to support eCall and Vehicles designed for multiple regions might need to support eCall
other Advanced Automatic Crash Notification systems, such as and other Advanced Automatic Crash Notification (AACN) systems, such
described in [draft-ietf-ecrit-car-crash]. That system is compatible as described in [draft-ietf-ecrit-car-crash]. That system is
with eCall, differing primarily in the specific data set that is compatible with eCall, differing primarily in the specific data set
sent. 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.
skipping to change at page 5, line 20 skipping to change at page 5, line 20
being adopted in other regions. being adopted in other regions.
The pan-European eCall system provides a standardized and mandated The pan-European eCall system provides a standardized and mandated
mechanism for emergency calls by vehicles. eCall establishes mechanism for emergency calls by vehicles. eCall establishes
procedures for such calls to be placed by in-vehicle systems, procedures for such calls to be placed by in-vehicle systems,
recognized and processed by the network, and routed to a specialized recognized and processed by the network, and routed to a specialized
PSAP where the vehicle data is available to assist the call taker in PSAP where the vehicle data is available to assist the call taker in
assessing and responding to the situation. eCall provides a standard assessing and responding to the situation. eCall provides a standard
set of vehicle, sensor (e.g., crash related), and location data. set of vehicle, sensor (e.g., crash related), and location data.
An eCall may be either user-initiated or automatically triggered. An eCall can be either user-initiated or automatically triggered.
Automatically triggered eCalls indicate a car crash or some other Automatically triggered eCalls indicate a car crash or some other
serious incident and carry a greater presumption of risk of injury. serious incident and carry a greater presumption of risk of injury.
Manually triggered eCalls may be reports of serious hazards and are Manually triggered eCalls might be reports of serious hazards and are
likely to require a different response than an automatically likely to require a different response than an automatically
triggered eCall. Manually triggered eCalls are also more likely to triggered eCall. Manually triggered eCalls are also more likely to
be false (e.g., accidental) calls and may thus be subject to be false (e.g., accidental) calls and so might be subject to
different handling by the PSAP. different operational 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). Flags in as a 3GPP circuit-switched call over GSM (2G) or UMTS (3G). Flags in
the call setup mark the call as an eCall, and further indicate if the the call setup mark the call as an eCall, and further indicate if the
call was automatically or manually triggered. The call is routed to call was automatically or manually triggered. The call is routed to
an eCall-capable PSAP, a voice channel is established between the an eCall-capable PSAP, a voice channel is established between the
vehicle and the PSAP, and an eCall in-band modem is used to carry a vehicle and the PSAP, and an eCall in-band modem is used to carry a
defined set of vehicle, sensor (e.g., crash related), and location defined set of vehicle, sensor (e.g., crash related), and location
data (the Minimum Set of Data or MSD) within the voice channel. The data (the Minimum Set of Data or MSD) within the voice channel. The
same in-band mechanism is used for the PSAP to acknowledge successful same in-band mechanism is used for the PSAP to acknowledge successful
skipping to change at page 6, line 43 skipping to change at page 6, line 43
o The call setup indicates if the call was manually or automatically o The call setup indicates if the call was manually or automatically
triggered triggered
o A voice channel between the vehicle and the PSAP o A voice channel between the vehicle and the PSAP
o Carrying the MSD intrinsically with the call (the MSD needs to be o Carrying the MSD intrinsically with the call (the MSD needs to be
available to the same call-taker as the voice) available to the same call-taker as the voice)
o The ability for the PSAP to acknowledge receipt of the MSD o The ability for the PSAP to acknowledge receipt of the MSD
o The ability for the PSAP to request that the vehicle generate and o The ability for the PSAP to request that the vehicle generate and
transmit a new MSD transmit a new MSD
o The ability of the PSAP to be able to re-contact the occupants of o The ability of the PSAP to be able to re-contact the occupants of
vehicle after the initial eCall is concluded vehicle after the initial eCall is concluded
o The ability to perform a test call (which may be routed to a PSAP o The ability to perform a test call (which can be routed to a PSAP
but is not treated as an emergency call and not handled by a call but is not treated as an emergency call and not handled by a call
taker) taker)
It is recognized that NG-eCall offers many potential enhancements, It is recognized that NG-eCall offers many potential enhancements,
although these are not required by current EU regulations. For although these are not required by current EU regulations. For
convenience, the enhancements most applicable to the limited scope of convenience, the enhancements most applicable to the limited scope of
this document are summarized very briefly below. this document are summarized very briefly below.
NG-eCall is expected to offer: NG-eCall is expected to offer:
skipping to change at page 8, line 46 skipping to change at page 8, line 46
///----\\\ 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 can 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
7. Call Routing 7. Call Routing
The routing rules for eCalls are likely to differ from those of other The routing rules for eCalls are likely to differ from those of other
emergency calls because eCalls are special types of emergency calls emergency calls because eCalls are special types of emergency calls
(with implications for the types of response required) and need to be (with implications for the types of response required) and need to be
handled by specially designated PSAPs. In an environment that uses handled by specially designated PSAPs. In an environment that uses
ESInets, the originating network passes all types of emergency calls ESInets, the originating network passes all types of emergency calls
skipping to change at page 9, line 39 skipping to change at page 9, line 39
control the routing and processing of emergency calls. The control the routing and processing of emergency calls. The
centralization of such rules within ESInets provides for a cleaner centralization of such rules within ESInets provides for a cleaner
separation between the responsibilities of the originating network separation between the responsibilities of the originating network
and that of the emergency services network, and provides greater and that of the emergency services network, and provides greater
flexibility and control over processing of emergency calls by the flexibility and control over processing of emergency calls by the
emergency services authorities. This makes it easier to react emergency services authorities. This makes it easier to react
quickly to unusual situations that require changes in how emergency quickly to unusual situations that require changes in how emergency
calls are routed or handled (e.g., a natural disaster closes a PSAP), calls are routed or handled (e.g., a natural disaster closes a PSAP),
as well as ease in making long-term changes that affect such routing as well as ease in making long-term changes that affect such routing
(e.g., cooperative agreements to specially handle calls requiring (e.g., cooperative agreements to specially handle calls requiring
translation or relay services). ESInets may support the ability to translation or relay services). ESInets might support the ability to
interwork NG-eCall to legacy eCall to handle eCall-capable PSAPs that interwork NG-eCall to legacy eCall to handle eCall-capable PSAPs that
are not IP PSAPs (similarly to the ability to interwork IP emergency are not IP PSAPs (similarly to the ability to interwork IP emergency
calls to legacy non-IP PSAPs). Note that in order to support legacy calls to legacy non-IP PSAPs). Note that in order to support legacy
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 might need the ability to route an
itself (e.g., to an interworking facility with interconnection to a eCall itself (e.g., to an interworking facility with interconnection
suitable legacy eCall capable PSAP) based on the eCall and manual or to a suitable legacy eCall capable PSAP) based on the eCall and
automatic indications. The ETSI TR "Mobile Standards Group (MSG); manual or automatic indications. The ETSI TR "Mobile Standards Group
eCall for VoIP" [MSG_TR] discusses transition issues in Clause 7. (MSG); 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 to some extent as eCalls but are not given are recognized and treated to some extent as eCalls but are not given
emergency call treatment and are not handled by call takers. The 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 test call facility allows the IVS or user to verify that an eCall can
be successfully established with voice communication. The IVS can be successfully established with voice communication. The IVS can
also verify that the MSD was successfully received. 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.
the current eCall test call facility is a non-emergency number so 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 does not get treated as an emergency call. MNOs can treat a vehicle
call in the "test" service URN in a way that tests as much call in the "test" service URN in a way that tests as much
functionality as desired, but this is outside the scope of this functionality as desired, but this is outside the scope of this
document. document.
PSAPs that have the ability to process NG-eCalls SHOULD accept test PSAPs that have the ability to process NG-eCalls SHOULD accept test
calls and send an acknowledgment if the MSD was successfully calls and send an acknowledgment if the MSD was successfully
received, per this document. Such PSAPs MAY also play an audio clip received, per this document. Such PSAPs MAY also play an audio clip
(for example, saying that the call reached a PSAP) in addition to (for example, saying that the call reached a PSAP) in addition to
supporting media loopback per [RFC6881]. supporting media loopback per [RFC6881].
9. eCall-Specific Control/Metadata 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 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 may 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 the vehicle's state or location has changed). a new MSD to see if the vehicle's state or location has changed).
Future enhancements are desired to enable the PSAP to send other Future enhancements are desired to enable the PSAP to send other
requests to the vehicle, such as locking or unlocking doors, sounding requests to the vehicle, such as locking or unlocking doors, sounding
the horn, flashing the lights, starting a video stream from on-board the horn, flashing the lights, starting a video stream from on-board
cameras (such as rear focus or blind-spot), etc. cameras (such as rear focus or blind-spot), etc.
The mechanism established in [additional-data-draft], used in The mechanism established in [additional-data-draft], used in
Section 5 of this document to carry the MSD from the IVS to the PSAP, Section 5 of this document to carry the MSD from the IVS to the PSAP,
is also used to carry a block of control data 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 (sometimes referred to as eCall IVS. This eCall control block (sometimes referred to as eCall
skipping to change at page 12, line 30 skipping to change at page 12, line 30
The <ack> element indicates the object being acknowledged (i.e., a The <ack> element indicates the object being acknowledged (i.e., a
data object or a <request> element), and reports success or failure. data object or a <request> element), and reports success or failure.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements to indicate
the actions supported by the IVS. the actions supported by the IVS.
The <request> element contains attributes to indicate the request and The <request> element contains attributes to indicate the request and
to supply any needed information, and MAY contain a <text> child to supply any needed information, and MAY contain a <text> child
element to contain the text for a dynamic message. The 'action' element to contain the text for a dynamic message. The 'action'
attribute is mandatory and indicates the specific action. An IANA attribute is mandatory and indicates the specific action. An IANA
registry is created in Section 13.8.1 to contain the allowed values. registry is created in Section 14.8.1 to contain the allowed values.
Extensibility: New elements, child elements, and attributes can be Extensibility: New elements, child elements, and attributes can be
defined in new namespaces. IANA registries are used to specify the defined in new namespaces. IANA registries are used to specify the
permitted values of several elements and attributes. These permitted values of several elements and attributes. These
mechanisms allow for extension. mechanisms allow for extension.
The control block does not contain a 'request' action to play dynamic There is no 'request' action to play dynamic media (such as a pre-
media (such as a pre-recorded audio message). The SIP re-INVITE recorded audio message). The SIP re-INVITE mechanism can be used to
mechanism can be used to establish a one-way media stream for this establish a one-way media stream for this purpose.
purpose.
9.1.1. The <ack> element 9.1.1. The <ack> element
The <ack> element is transmitted by the PSAP to acknowledge receipt The <ack> element is transmitted by the PSAP to acknowledge receipt
of an eCall data object. An <ack> element sent by a PSAP references 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 the unique ID of the data object that was sent by the IVS, and
further indicates if the PSAP considers the receipt successful or further indicates if the PSAP considers the receipt successful or
not. The <ack> element is also transmitted by the IVS to the PSAP to 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 acknowledge receipt of a <request> element that requested the IVS to
perform an action other than transmitting a data object (e.g., a perform an action other than transmitting a data object (e.g., a
skipping to change at page 14, line 12 skipping to change at page 14, line 12
Usage: Mandatory Usage: Mandatory
Type: Boolean Type: Boolean
Description: Indicates if the action was successfully Description: Indicates if the action was successfully
accomplished accomplished
Name: reason Name: reason
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used when 'success' is "False", this attribute Description: Used when 'success' is "False", this attribute
contains a reason code for a failure. A registry for reason contains a reason code for a failure. A registry for reason
codes is defined in Section 13.8.3. codes is defined in Section 14.8.3.
Name: details Name: details
Usage: optional Usage: optional
Type: string Type: string
Description: Contains further explanation of the circumstances of Description: Contains further explanation of the circumstances of
a success or failure. The contents are implementation-specific a success or failure. The contents are implementation-specific
and human-readable. and human-readable.
Example: <actionResult action="msg-dynamic" success="true"/> Example: <actionResult action="msg-dynamic" success="true"/>
skipping to change at page 16, line 48 skipping to change at page 16, line 48
</capabilities> </capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
Figure 5: Capabilities Example Figure 5: Capabilities Example
9.1.3. The <request> element 9.1.3. The <request> element
A <request> element appears one or more times on its own or as a A <request> element appears one or more times on its own or as a
child of a <capabilities> element. The following attributes and child of a <capabilities> element. The following attributes and
child elements may be used: child elements are defined:
9.1.3.1. Attributes of the <request> element 9.1.3.1. Attributes of the <request> element
The <request> element has the following attributes: The <request> element has the following attributes:
Name: action Name: action
Usage: Mandatory Usage: Mandatory
Type: token Type: token
Description: Identifies the action that the vehicle is requested to Description: Identifies the action that the vehicle is requested to
perform. An IANA registry is established in Section 13.8.1 to perform. An IANA registry is established in Section 14.8.1 to
contain the allowed values. contain the allowed values.
Example: action="send-data" Example: action="send-data"
Name: msgid Name: msgid
Usage: Conditional Usage: Conditional
Type: int Type: int
Description: Mandatory with a "msg-static" action. Indicates the Description: Mandatory with a "msg-static" action. Indicates the
identifier of the static message to be displayed and/or spoken for identifier of the static message to be displayed and/or spoken for
the vehicle occupants. This document established an IANA registry the vehicle occupants. This document established an IANA registry
for messages and their IDs, in Section 13.8.2 for messages and their IDs, in Section 14.8.2
Example: msgid="3" Example: msgid="3"
Name: persistance Name: persistance
Usage: Optional Usage: Optional
Type: duration Type: duration
Description: Specifies how long to carry on the specified action, Description: Specifies how long to carry on the specified action,
for example, how long to continue honking or flashing. If absent, for example, how long to continue honking or flashing. If absent,
the default is indefinitely. the default is indefinitely.
Example: persistance="PT1H" Example: persistance="PT1H"
skipping to change at page 18, line 12 skipping to change at page 18, line 12
identifier as in the 'purpose' attribute in a Call-Info header identifier as in the 'purpose' attribute in a Call-Info header
field to point to the data block. Permitted values are contained field to point to the data block. Permitted values are contained
in the 'Emergency Call Data Types' IANA registry established in in the 'Emergency Call Data Types' IANA registry established in
[additional-data-draft]. Multiple values are separated with a [additional-data-draft]. Multiple values are separated with a
semicolon. semicolon.
Example: supported-datatypes="eCall.MSD; VEDS; eCall.foo" Example: supported-datatypes="eCall.MSD; VEDS; eCall.foo"
Name: lamp-action Name: lamp-action
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used with a 'lamp' action, indicates if the lamp should Description: Used with a 'lamp' action, indicates if the lamp is to
be illuminated, turned off, or flashed. Permitted values are be illuminated, turned off, or flashed. Permitted values are
'on', 'off', and 'flash'. 'on', 'off', and 'flash'.
Example: lamp-action="flash" Example: lamp-action="flash"
Name: lamp-ID Name: lamp-ID
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used with a 'lamp' action, indicates which lamp the Description: Used with a 'lamp' action, indicates which lamp the
action affects. Permitted values are contained in the registry of action affects. Permitted values are contained in the registry of
lamp-ID tokens created in Section 13.8.4 lamp-ID tokens created in Section 14.8.4
Example: lamp-ID="hazard" Example: lamp-ID="hazard"
Name: supported-lamps Name: supported-lamps
Usage: Conditional Usage: Conditional
Type: string Type: string
Description: Used with a 'lamp' action in a <request> element that Description: Used with a 'lamp' action in a <request> element that
is a child of a <capability> element, this attribute lists all is a child of a <capability> element, this attribute lists all
supported lamps, using values in the registry of lamp-ID tokens supported lamps, using values in the registry of lamp-ID tokens
created in Section 13.8.4. Multiple values are separated with a created in Section 14.8.4. Multiple values are separated with a
semicolon. semicolon.
Example: supported-lamps="head; interior; fog-front; fog-rear; Example: supported-lamps="head; interior; fog-front; fog-rear;
brake; position-front; position-rear; turn-left; turn-right; brake; position-front; position-rear; turn-left; turn-right;
hazard" hazard"
Name: camera-ID Name: camera-ID
Usage: Conditional Usage: Conditional
Type: token Type: token
Description: Used with an 'enable-camera' action, indicates which Description: Used with an 'enable-camera' action, indicates which
camera to enable. Permitted values are contained in the registry camera to enable. Permitted values are contained in the registry
of camera-ID tokens created in Section 13.8.5. When a vehicle of camera-ID tokens created in Section 14.8.5. When a vehicle
camera is enabled, the IVS sends a re-INVITE to negotiate a one- camera is enabled, the IVS sends a re-INVITE to negotiate a one-
way media stream for the camera. way media stream for the camera.
Example: camera-ID="backup" Example: camera-ID="backup"
Name: supported-cameras Name: supported-cameras
Usage: Conditional Usage: Conditional
Type: string Type: string
Description: Used with an 'enable-camera' action in a <request> Description: Used with an 'enable-camera' action in a <request>
element that is a child of a <capability> element, this attribute element that is a child of a <capability> element, this attribute
lists all cameras that the vehicle supports (can add as a video lists all cameras that the vehicle supports (can add as a video
feed in the current session), using the same identifiers as are feed in the current session), using the same identifiers as are
used in the 'camera-ID' attribute (contained in the camera ID used in the 'camera-ID' attribute (contained in the camera ID
registry in Section 13.8.5). Multiple values are separated with a registry in Section 14.8.5). Multiple values are separated with a
semicolon. semicolon.
Example: supported-cameras="backup; interior" Example: supported-cameras="backup; interior"
9.1.3.2. Child Elements of the <request> element 9.1.3.2. Child Elements of the <request> element
The <request> element has the following child elements: The <request> element has the following child elements:
Name: text Name: text
Usage: Conditional Usage: Conditional
Type: string Type: string
skipping to change at page 20, line 48 skipping to change at page 20, line 48
an Info-Package header field set to 'emergencyCallData.eCall' per an Info-Package header field set to 'emergencyCallData.eCall' per
[RFC6086]. The INFO request message is marked as containing the [RFC6086]. The INFO request message is marked as containing the
eCall data or control block by a Call-Info header field containing a eCall data or control block by a Call-Info header field containing a
CID URL referencing the unique identifier of the body part containing CID URL referencing the unique identifier of the body part containing
the eCall data or control, and a 'purpose' parameter identifying the the eCall data or control, and a 'purpose' parameter identifying the
block. Because the eCall data or control block is being carried in block. Because the eCall data or control block is being carried in
an INFO request message, the body part also carries a Content- an INFO request message, the body part also carries a Content-
Disposition header field set to "Info-Package". Disposition header field set to "Info-Package".
Per [additional-data-draft], emergency call related additional data Per [additional-data-draft], emergency call related additional data
MAY be included in any SIP request or response message that may MAY be included in any SIP request or response message that can
contain a body. Hence, notwithstanding Section 4.3.2. of [RFC6086], contain a body. Hence, notwithstanding Section 4.3.2. of [RFC6086],
INFO response messages MAY contain eCall data or control blocks, INFO response messages MAY contain eCall data or control blocks,
provided they are included as described in this document (with a provided they are included as described in this document (with a
Call-Info header field containing a CID URL referencing the unique Call-Info header field containing a CID URL referencing the unique
identifier of the body part, and a 'purpose' parameter identifying identifier of the body part, and a 'purpose' parameter identifying
the block). When eCall data or control blocks are included in an the block). When eCall data or control blocks are included in an
INFO response message, this is done per [additional-data-draft] and INFO response message, this is done per [additional-data-draft] and
this document, and not under [RFC6086]; that is, they are included as this document, and not under [RFC6086]; that is, they are included as
emergency call additional data, not as an INFO package associated emergency call additional data, not as an INFO package associated
data. data.
skipping to change at page 22, line 21 skipping to change at page 22, line 21
cid:2345678901@atlanta.example.com; cid:2345678901@atlanta.example.com;
purpose=emergencyCallData.eCall.control; purpose=emergencyCallData.eCall.control;
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control application/emergencyCallData.eCall.control
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall 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
Content-Type: application/emergencyCallData.eCall.MSD+xml Content-Type: application/emergencyCallData.eCall.MSD+xml
Content-ID: 1234567890@atlanta.example.com Content-ID: 1234567890@atlanta.example.com
Content-Disposition: by-reference;handling=optional
<ECallMessage> <ECallMessage>
<id>1</id> <id>1</id>
<msd> <msd>
<msdStructure> <msdStructure>
<messageIdentifier>1</messageIdentifier> <messageIdentifier>1</messageIdentifier>
<control> <control>
skipping to change at page 23, line 40 skipping to change at page 23, line 40
</msdStructure> </msdStructure>
<optionalAdditionalData> <optionalAdditionalData>
<oid>1.2.125</oid> <oid>1.2.125</oid>
<data>30304646</data> <data>30304646</data>
</optionalAdditionalData> </optionalAdditionalData>
</msd> </msd>
</ECallMessage> </ECallMessage>
--boundary1 --boundary1
Content-Type: application/emergencyCallData.eCall.control+xml Content-Type: application/emergencyCallData.eCall.control+xml
Content-ID: 2345678901@atlanta.example.com Content-ID: 2345678901@atlanta.example.com
Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall-control"> eCall-control">
<capabilities> <capabilities>
<request action="send-data" supported-datatypes="eCall.MSD"/> <request action="send-data" supported-datatypes="eCall.MSD"/>
skipping to change at page 25, line 19 skipping to change at page 25, line 19
purpose=emergencyCallData.eCall.control; purpose=emergencyCallData.eCall.control;
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallData.eCall.control, application/emergencyCallData.eCall.control,
application/emergencyCallData.eCall.MSD application/emergencyCallData.eCall.MSD
CSeq: 31862 INVITE CSeq: 31862 INVITE
Recv-Info: emergencyCallData.eCall Recv-Info: emergencyCallData.eCall
Content-Type: multipart/mixed; boundary=boundaryX Content-Type: multipart/mixed; boundary=boundaryX
Content-Length: ... Content-Length: ...
--boundaryX --boundaryX
Content-Type: application/sdp Content-Type: application/sdp
...Session Description Protocol (SDP) goes here... ...Session Description Protocol (SDP) goes here...
--boundaryX --boundaryX
Content-Type: application/EmergencyCallData:eCall-control+xml
Content-ID: 2345678901@atlanta.example.com
Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl <EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall-control"> eCall-control">
<ack received="true" ref="1234567890@atlanta.example.com"/> <ack received="true" ref="1234567890@atlanta.example.com"/>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
--boundaryX --boundaryX--
Figure 9: 200 OK response to INVITE Figure 9: 200 OK response to INVITE
11. Security Considerations 11. Security Considerations
The security considerations described in [RFC5069] apply here. The security considerations described in [RFC5069] apply here.
An eCall will carry two forms of location data: the network-provided In addition to any network-provided location that is inherently
location that is inherently part of IMS emergency calls (which might permitted for IMS emergency calls (which might be determined solely
be determined solely by the network, or in cooperation with or by the network, or in cooperation with or possibly entirely by the
possibly entirely by the originating device), and the IVS-supplied originating device), an eCall carries an IVS-supplied location within
location within the MSD. This is likely to be useful to the PSAP, the MSD. This is likely to be useful to the PSAP, especially when
especially when the two locations are independently determined. Even the two locations are independently determined. Even in situations
in situations where the network-supplied location is limited to the where the network-supplied location is limited to the cell site, this
cell site, this can be useful as a sanity check on the device- can be useful as a sanity check on the device-supplied location
supplied location contained in the MSD. contained in the MSD.
The document [I-D.ietf-ecrit-trustworthy-location] discusses trust The document [RFC7378] discusses trust issues regarding location
issues regarding location provided by or determined in cooperation provided by or determined in cooperation with end devices.
with end devices.
The mechanism by which the PSAP sends acknowledgments and requests to The mechanism by which the PSAP sends acknowledgments and requests to
the vehicle requires authenticity considerations; when the PSAP the vehicle requires authenticity considerations; when the PSAP
request is received within a session initiated by the vehicle as an request is received within a session initiated by the vehicle as an
eCall emergency call placed over a cellular network, there is a eCall emergency call placed over a cellular network, there is a
higher degree of trust that the source is indeed a PSAP. If the PSAP higher degree of trust that the source is indeed a PSAP. If the PSAP
request is received in other situations, such as a call-back, the request is received in other situations, such as a call-back, the
trust issues in verifying that a call-back is indeed from a PSAP are trust issues in verifying that a call-back is indeed from a PSAP are
more complex (see the PSAP Callback document [RFC7090]). A further more complex (see the PSAP Callback document [RFC7090]). A further
safeguard (applicable regardless of which end initiated the call and safeguard (applicable regardless of which end initiated the call and
the means of the call) is for the PSAP or emergency service provider 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 to sign the body part using a certificate issued by a known emergency
services certificate authority and for which the IVS can verify the services certificate authority and for which the IVS can verify the
root certificate. root certificate.
12. XML Schema 12. Privacy Considerations
Since this document builds on [additional-data-draft], the data
structures specified there, and the corresponding privacy
considerations discussed there, apply here as well. The MSD carries
some additional identifying and personal information (mostly about
the vehicle and less about the owner), as well as location
information, and so needs to be protected against unauthorized
disclosure. Local regulations may impose additional privacy
protection requirements. The additional functionality enabled by
this document, such as access to vehicle camera streams, carries a
burden of protection and so implementations need to be careful that
access is only provided within the context of an emergency call and
to an emergency services provider, for example, within a vehicle-
initiated emergency call or by verifying that the request for camera
access is signed by a certificate issued by an emergency services
registrar.
13. XML Schema
This section defines the XML schema of the eCall control block. (The This section defines the XML schema of the eCall control block. (The
schema for the MSD can be found in EN 15722 [msd].) schema for the MSD can be found in EN 15722 [msd].)
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
skipping to change at page 29, line 4 skipping to change at page 29, line 23
<xs:attribute name="lamp-id" type="xs:token"/> <xs:attribute name="lamp-id" type="xs:token"/>
<xs:attribute name="lamp-action"> <xs:attribute name="lamp-action">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value=""/> <xs:pattern value=""/>
<xs:pattern value=""/> <xs:pattern value=""/>
<xs:enumeration value="on"/> <xs:enumeration value="on"/>
<xs:enumeration value="off"/> <xs:enumeration value="off"/>
<xs:enumeration value="flash"/> <xs:enumeration value="flash"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
<xs:attribute name="supported-lamps" type="xs:string"/> <xs:attribute name="supported-lamps" type="xs:string"/>
<xs:attribute name="camera-id" type="xs:token"/> <xs:attribute name="camera-id" type="xs:token"/>
<xs:attribute name="supported-cameras" type="xs:string"/> <xs:attribute name="supported-cameras" type="xs:string"/>
<xs:anyAttribute/> <xs:anyAttribute/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 10: eCall Control Block Schema Figure 10: eCall Control Block Schema
13. IANA Considerations 14. IANA Considerations
13.1. Service URN Registrations 14.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 a 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
skipping to change at page 29, line 32 skipping to change at page 30, line 4
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 a 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].
13.2. MIME Content-type Registration for 'application/ 14.2. MIME Content-type Registration for 'application/
emergencyCallData.eCall.MSD+xml' emergencyCallData.eCall.MSD+xml'
IANA is requested to add application/emergencyCallData.eCall.MSD+xml IANA is requested to add application/emergencyCallData.eCall.MSD+xml
as a MIME content type, with a reference to this document, in as a MIME content type, with a reference to this document, in
accordance to the procedures of RFC 6838 [RFC6838] and guidelines in accordance to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.MSD+xml MIME subtype name: emergencyCallData.eCall.MSD+xml
skipping to change at page 31, line 4 skipping to change at page 31, line 19
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
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)
13.3. MIME Content-type Registration for 'application/ 14.3. MIME Content-type Registration for 'application/
emergencyCallData.eCall.control+xml' emergencyCallData.eCall.control+xml'
IANA is requested to add application/ IANA is requested to add application/
emergencyCallData.eCall.control+xml as a MIME content type, with a emergencyCallData.eCall.control+xml as a MIME content type, with a
reference to this document, in accordance to the procedures of RFC reference to this document, in accordance to the procedures of RFC
6838 [RFC6838] and guidelines in RFC 7303 [RFC7303]. 6838 [RFC6838] and guidelines in RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.eCall.control+xml MIME subtype name: emergencyCallData.eCall.control+xml
skipping to change at page 31, line 48 skipping to change at page 32, line 15
Security considerations: This content type carries metadata and Security considerations: This content type carries metadata and
control information and requests, primarily from a Public Safety control information and requests, primarily from a Public Safety
Answering Point (PSAP) to an In-Vehicle System (IVS) during an Answering Point (PSAP) to an In-Vehicle System (IVS) during an
emergency call, and also capabilities from the IVS to the PSAP. emergency call, and also capabilities from the IVS to the PSAP.
Metadata (such as an acknowledgment that data sent by the IVS to Metadata (such as an acknowledgment that data sent by the IVS to
the PSAP was successfully received) has limited privacy and the PSAP was successfully received) has limited privacy and
security implications. Control information (such as requests from security implications. Control information (such as requests from
the PSAP that the vehicle perform an action) has some privacy and the PSAP that the vehicle perform an action) has some privacy and
important security implications. The privacy concern arises from important security implications. The privacy concern arises from
the ability to request the vehicle to transmit a data set, which the ability to request the vehicle to transmit a data set, which
as described in Section 13.2, may contain personal information. as described in Section 14.2, can contain personal information.
The security implication is the ability to request the vehicle to The security implication is the ability to request the vehicle to
perform an action. It is important that control information perform an action. It is important that control information
originate only from a PSAP or other emergency services provider, originate only from a PSAP or other emergency services provider,
and not from an impostor. The first safeguard for this is the and not from an impostor. The first safeguard for this is the
security of the cellular network over which the emergency call was security of the cellular network over which the emergency call was
placed. In particular, when the IVS initiates an eCall over a placed. In particular, when the IVS initiates an eCall over a
cellular network, the MNO routes the call to a PSAP. (Calls cellular network, the MNO routes the call to a PSAP. (Calls
placed using other means, such as Wi-Fi or over-the-top services, 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 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 IVS, such as a call-back from a PSAP, also do not carry the same
skipping to change at page 32, line 36 skipping to change at page 33, line 4
Applications which use this media type: Pan-European eCall Applications which use this media type: Pan-European eCall
compliant systems compliant systems
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Randall Gellens, Person and email address for further information: Randall Gellens,
rg+ietf@qti.qualcomm.com rg+ietf@qti.qualcomm.com
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: The IETF ECRIT WG. Author: The IETF ECRIT WG.
Change controller: The IETF ECRIT WG. Change controller: The IETF ECRIT WG.
13.4. Registration of the 'eCall.MSD' entry in the Emergency Call 14.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.5. Registration of the 'eCall.control' entry in the Emergency Call 14.5. Registration of the 'eCall.control' entry in the Emergency Call
Additional Data Blocks registry Additional Data Blocks registry
This specification requests IANA to add the 'eCall.control' entry to This specification requests IANA to add the 'eCall.control' entry to
the Emergency Call Additional Data Blocks registry (established by the 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.6. Registration of the emergencyCallData.eCall Info Package 14.6. Registration of the emergencyCallData.eCall Info Package
IANA is requested to add emergencyCallData.eCall to the Info Packages IANA is requested to add emergencyCallData.eCall to the Info Packages
Registry under "Session Initiation Protocol (SIP) Parameters", with a Registry under "Session Initiation Protocol (SIP) Parameters", with a
reference to this document. reference to this document.
13.7. URN Sub-Namespace Registration 14.7. URN Sub-Namespace Registration
13.7.1. Registration for urn:ietf:params:xml:ns:eCall 14.7.1. Registration for urn:ietf:params:xml:ns:eCall
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall URI: urn:ietf:params:xml:ns:eCall
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 34, line 5 skipping to change at page 34, line 22
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for eCall Data</title> <title>Namespace for eCall Data</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
13.7.2. Registration for urn:ietf:params:xml:ns:eCall:control 14.7.2. Registration for urn:ietf:params:xml:ns:eCall:control
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:eCall:control URI: urn:ietf:params:xml:ns:eCall:control
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 34, line 36 skipping to change at page 35, line 24
Control Block</title> Control Block</title>
</head> </head>
<body> <body>
<h1>Namespace for eCall Data</h1> <h1>Namespace for eCall Data</h1>
<h2>Control Block</h2> <h2>Control Block</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
13.8. Registry creation 14.8. Registry creation
This document creates a new registry called 'eCall Control Data'. This document creates a new registry called 'eCall Control Data'.
The following sub-registries are created for this registry. The following sub-registries are created for this registry.
13.8.1. eCall Control Action Registry 14.8.1. eCall Control Action Registry
This document creates a new sub-registry called "eCall Control Action This document creates a new sub-registry called "eCall Control Action
Registry". As defined in [RFC5226], this registry operates under Registry". As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the proposed "Expert Review" rules. The expert should determine that the proposed
action is within the purview of a vehicle, is sufficiently action is within the purview of a vehicle, is sufficiently
distinguishable from other actions, and the actions is clearly and distinguishable from other actions, and the actions is clearly and
fully described. In most cases, a published and stable document is fully described. In most cases, a published and stable document is
referenced for the description of the action. referenced for the description of the action.
The content of this registry includes: The content of this registry includes:
skipping to change at page 35, line 36 skipping to change at page 36, line 23
| | | | | |
| honk | Section xxx of this document | | honk | Section xxx of this document |
| | | | | |
| lamp | Section xxx of this document | | lamp | Section xxx of this document |
| | | | | |
| enable-camera | Section xxx of this document | | enable-camera | Section xxx of this document |
+---------------+------------------------------+ +---------------+------------------------------+
Table 2: eCall Control Action Registry Initial Values Table 2: eCall Control Action Registry Initial Values
13.8.2. eCall Static Message Registry 14.8.2. eCall Static Message Registry
This document creates a new sub-registry called "eCall Static Message This document creates a new sub-registry called "eCall Static Message
Registry". Because all compliant vehicles are expected to support Registry". Because all compliant vehicles are expected to support
all static messages translated into all languages supported by the all static messages translated into all languages supported by the
vehicle, it is important to limit the number of such messages. As vehicle, it is important to limit the number of such messages. As
defined in [RFC5226], this registry operates under "Publication defined in [RFC5226], this registry operates under "Publication
Required" rules, which require a stable, public document and imply Required" rules, which require a stable, public document and imply
expert review of the publication. The expert should determine that expert review of the publication. The expert should determine that
the document has been published by an appropriate emergency services the document has been published by an appropriate emergency services
organization (e.g., NENA, EENA, APCO) and that the proposed message organization (e.g., NENA, EENA, APCO) and that the proposed message
skipping to change at page 36, line 27 skipping to change at page 37, line 15
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| ID | Message | | ID | Message |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| 1 | Emergency authorities are aware of your incident and | | 1 | Emergency authorities are aware of your incident and |
| | location, but are unable to speak with you right now. We | | | location, but are unable to speak with you right now. We |
| | will help you as soon as possible. | | | will help you as soon as possible. |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
Table 3: eCall Static Message Registry Table 3: eCall Static Message Registry
13.8.3. eCall Reason Registry 14.8.3. eCall Reason Registry
This document creates a new sub-registry called "eCall Reason This document creates a new sub-registry called "eCall Reason
Registry" which contains values for the 'reason' attribute of the Registry" which contains values for the 'reason' attribute of the
<actionResult> element. As defined in [RFC5226], this registry <actionResult> element. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine operates under "Expert Review" rules. The expert should determine
that the proposed reason is sufficiently distinguishable from other that the proposed reason is sufficiently distinguishable from other
reasons and that the proposed description is understandable and reasons and that the proposed description is understandable and
correctly worded. correctly worded.
The content of this registry includes: The content of this registry includes:
skipping to change at page 37, line 18 skipping to change at page 37, line 47
| unsupported | The 'action' is not supported. | | unsupported | The 'action' is not supported. |
| | | | | |
| unable | The 'action' could not be accomplished. | | unable | The 'action' could not be accomplished. |
| | | | | |
| data-unsupported | The data item referenced in a 'send-data' | | data-unsupported | The data item referenced in a 'send-data' |
| | request is not supported. | | | request is not supported. |
+------------------+------------------------------------------------+ +------------------+------------------------------------------------+
Table 4: eCall Reason Registry Table 4: eCall Reason Registry
13.8.4. eCall Lamp ID Registry 14.8.4. eCall Lamp ID Registry
This document creates a new sub-registry called "eCall Lamp ID This document creates a new sub-registry called "eCall Lamp ID
Registry" to standardize the names of automotive lamps (lights). As Registry" to standardize the names of automotive lamps (lights). As
defined in [RFC5226], this registry operates under "Expert Review" defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the proposed lamp name is rules. The expert should determine that the proposed lamp name is
clearly understandable and is sufficiently distinguishable from other clearly understandable and is sufficiently distinguishable from other
lamp names. lamp names.
The content of this registry includes: The content of this registry includes:
skipping to change at page 38, line 31 skipping to change at page 38, line 42
| | | | | |
| turn-left | Left turn/directional lamps | | turn-left | Left turn/directional lamps |
| | | | | |
| turn-right | Right turn/directional lamps | | turn-right | Right turn/directional lamps |
| | | | | |
| hazard | Hazard/four-way lamps | | hazard | Hazard/four-way lamps |
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
Table 5: eCall Lamp ID Registry Initial Values Table 5: eCall Lamp ID Registry Initial Values
13.8.5. eCall Camera ID Registry 14.8.5. eCall Camera ID Registry
This document creates a new sub-registry called "eCall Camera ID This document creates a new sub-registry called "eCall Camera ID
Registry" to standardize the names of automotive camera. As defined Registry" to standardize the names of automotive camera. As defined
in [RFC5226], this registry operates under "Expert Review" rules. in [RFC5226], this registry operates under "Expert Review" rules.
The expert should determine that the proposed camera name is clearly The expert should determine that the proposed camera name is clearly
understandable and is sufficiently distinguishable from other camera understandable and is sufficiently distinguishable from other camera
names. names.
The content of this registry includes: The content of this registry includes:
skipping to change at page 39, line 16 skipping to change at page 39, line 23
| Name | Description | | Name | Description |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
| backup | Shows what is behind the vehicle. Also known as | | backup | Shows what is behind the vehicle. Also known as |
| | rearview, reverse, etc. | | | rearview, reverse, etc. |
| | | | | |
| interior | Shows the interior (driver) | | interior | Shows the interior (driver) |
+----------+--------------------------------------------------------+ +----------+--------------------------------------------------------+
Table 6: eCall Camera ID Registry Initial Values Table 6: eCall Camera ID Registry Initial Values
14. Contributors 15. Contributors
Brian Rosen was a co-author of the original document upon which this Brian Rosen was a co-author of the original document upon which this
document is based. document is based.
15. Acknowledgements 16. Acknowledgements
We would like to thank Bob Williams and Ban Al-Bakri for their We would like to thank Bob Williams and Ban Al-Bakri for their
feedback and suggestions, and Keith Drage for his review comments. feedback and suggestions, and Keith Drage for his review comments.
We would like to thank Michael Montag, Arnoud van Wijk, Gunnar We would like to thank Michael Montag, Arnoud van Wijk, Gunnar
Hellstrom, and Ulrich Dietz for their help with the original document Hellstrom, and Ulrich Dietz for their help with the original document
upon which this document is based. upon which this document is based.
16. Changes from Previous Versions 17. Changes from Previous Versions
16.1. Changes from draft-ietf-02 to draft-ietf-03 17.1. 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
16.2. Changes from draft-ietf-01 to draft-ietf-02 17.2. 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
16.3. Changes from draft-ietf-00 to draft-ietf-01 17.3. Changes from draft-ietf-00 to draft-ietf-01
o Added further discussion of test calls o Added further discussion of test calls
o Added further clarification to the document scope o Added further clarification to the document scope
o Mentioned that multi-region vehicles may need to support other o Mentioned that multi-region vehicles may need to support other
crash notification specifications in addition to eCall crash notification specifications in addition to eCall
o Added details of the eCall metadata and control functionality o Added details of the eCall metadata and control functionality
o Added IANA registration for the MIME content type for the eCall o Added IANA registration for the MIME content type for the eCall
control object control object
o Added IANA registries for protocol elements and tokens used in the o Added IANA registries for protocol elements and tokens used in the
eCall control object eCall control object
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
16.4. Changes from draft-gellens-03 to draft-ietf-00 17.4. 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
16.5. Changes from draft-gellens-02 to -03 17.5. Changes from draft-gellens-02 to -03
o Clarifications and editorial improvements. o Clarifications and editorial improvements.
16.6. Changes from draft-gellens-01 to -02 17.6. 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.
16.7. Changes from draft-gellens-00 to -01 17.7. 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
17. References 18. References
17.1. Normative References
18.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]
Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", draft-ietf-ecrit-additional-data-30 (work in Call", draft-ietf-ecrit-additional-data-37 (work in
progress), June 2015. progress), October 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031, Emergency and Other Well-Known Services", RFC 5031, DOI
January 2008. 10.17487/RFC5031, January 2008,
<http://www.rfc-editor.org/info/rfc5031>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[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, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013. 6838, DOI 10.17487/RFC6838, January 2013,
<http://www.rfc-editor.org/info/rfc6838>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013. BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
July 2014. DOI 10.17487/RFC7303, July 2014,
<http://www.rfc-editor.org/info/rfc7303>.
[TS22.101] [TS22.101]
3GPP, , "Technical Specification Group Services and System 3GPP, , "Technical Specification Group Services and 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.
17.2. Informative references 18.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-trustworthy-location]
Tschofenig, H., Schulzrinne, H., and B. Aboba,
"Trustworthy Location", draft-ietf-ecrit-trustworthy-
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.
[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, January 2008. RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>.
[RFC5069] Taylor, T., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, January Emergency Call Marking and Mapping", RFC 5069, DOI
2008. 10.17487/RFC5069, January 2008,
<http://www.rfc-editor.org/info/rfc5069>.
[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, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[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. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback", Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, April 2014. RFC 7090, DOI 10.17487/RFC7090, April 2014,
<http://www.rfc-editor.org/info/rfc7090>.
[RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
"Trustworthy Location", RFC 7378, DOI 10.17487/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>.
[draft-ietf-ecrit-car-crash] [draft-ietf-ecrit-car-crash]
skipping to change at page 43, line 26 skipping to change at page 43, line 35
ecrit-car-crash (work in progress), March 2015. ecrit-car-crash (work in progress), March 2015.
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@randy.pensive.org
Hannes Tschofenig Hannes Tschofenig
(Individual)
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
 End of changes. 94 change blocks. 
154 lines changed or deleted 177 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/