draft-ietf-ecrit-car-crash-08.txt   draft-ietf-ecrit-car-crash-09.txt 
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Consultant Internet-Draft Core Technology Consulting
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: January 7, 2017 NeuStar, Inc. Expires: February 2, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
July 6, 2016 August 1, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-08.txt draft-ietf-ecrit-car-crash-09.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 emergency calls placed mechanisms to support the next generation of emergency calls placed
by vehicles (automatically in the event of a crash or serious by vehicles (automatically in the event of a crash or serious
incident, or manually invoked by a vehicle occupant) and conveying incident, or manually invoked by a vehicle occupant) and conveying
vehicle, sensor, and location data related to the crash or incident. vehicle, sensor, and location data related to the crash or incident.
Such calls are often referred to as "Automatic Crash Notification" Such calls are often referred to as "Automatic Crash Notification"
(ACN), or "Advanced Automatic Crash Notification" (AACN), even in the (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the
case of manual trigger. The "Advanced" qualifier refers to the case of manual trigger. The "Advanced" qualifier refers to the
ability to carry a richer set of data. ability to carry a richer set of data.
This document also registers a MIME Content Type and an Emergency This document also registers a MIME Content Type and Emergency Call
Call Additional Data Block for the vehicle, sensor, and location data Additional Data Block for the vehicle, sensor, and location data
(often referred to as "crash data" even though there is not (often referred to as "crash data" even though there is not
necessarily a crash). An external specification for the data format, necessarily a crash). An external specification for the data format,
contents, and structure are referenced in this document. contents, and structure are referenced in this document.
This document reuses the technical aspects of next-generation pan- This document reuses the technical aspects of next-generation pan-
European eCall (a mandated and standardized system for emergency European eCall (a mandated and standardized system for emergency
calls by in-vehicle systems within Europe and other regions). calls by in-vehicle systems within Europe and other regions).
However, this document specifies a different set of vehicle (crash) However, this document specifies a different set of vehicle (crash)
data, specifically, the Vehicle Emergency Data Set (VEDS) rather than data, specifically, the Vehicle Emergency Data Set (VEDS) rather than
the eCall Minimum Set of Data (MSD). This document is an extension the eCall Minimum Set of Data (MSD). This document is an extension
of the eCall document, with the primary differences being that this of the eCall document, with the primary differences being that this
document makes the MSD data set optional and VEDS mandatory, and document makes the MSD data set optional and VEDS mandatory, and adds
extends the eCall metadata/control object to permit greater attribute values to the eCall metadata/control object to permit
functionality. This document also describes legacy (circuit- greater functionality. This document registers a new INFO package
(identical to that registered for eCall but with the addition of the
VEDS MIME type). This document also describes legacy (circuit-
switched) ACN systems and their migration to next-generation switched) ACN systems and their migration to next-generation
emergency calling, to provide background information and context. emergency calling, to provide background information and context.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 7, 2017. This Internet-Draft will expire on February 2, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 37 skipping to change at page 2, line 42
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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8
4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10
6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 13 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13
6.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 15 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 14
7. eCall Metadata/Control Extensions . . . . . . . . . . . . . . 16 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15
7.1. New values for the 'action' attribute' . . . . . . . . . 17 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 16
7.2. <ack> element extensions . . . . . . . . . . . . . . . . 17 9.1. New values for the 'action' attribute' . . . . . . . . . 17
7.3. The <capabilities> element . . . . . . . . . . . . . . . 19 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 18
7.4. <request> element extensions . . . . . . . . . . . . . . 21 9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 18
8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 23 9.4. The <capabilities> element . . . . . . . . . . . . . . . 19
9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 20
10. Security Considerations . . . . . . . . . . . . . . . . . . . 30 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 21
11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 30 11.1. INFO Package Requirements . . . . . . . . . . . . . . . 22
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
12.1. MIME Content-type Registration for 13. Security Considerations . . . . . . . . . . . . . . . . . . . 29
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 31 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 29
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
12.2. Registration of the 'VEDS' entry in the Emergency Call 15.1. MIME Content-type Registration for
Additional Data registry . . . . . . . . . . . . . . . . 32 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 30
12.3. Additions to the eCall Control Extension Registry . . . 32 15.2. Registration of the 'VEDS' entry in the Emergency Call
12.4. eCall Action Extensions . . . . . . . . . . . . . . . . 34 Additional Data registry . . . . . . . . . . . . . . . . 31
12.5. eCall Static Message Registry . . . . . . . . . . . . . 34 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 32
12.6. eCall Reason Registry . . . . . . . . . . . . . . . . . 35 15.4. Static Message Registry . . . . . . . . . . . . . . . . 32
12.7. eCall Lamp ID Registry . . . . . . . . . . . . . . . . . 36 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 33
12.8. eCall Camera ID Registry . . . . . . . . . . . . . . . . 37 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 34
13. eCall Control Block Schema . . . . . . . . . . . . . . . . . 38 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 41 17. Changes from Previous Versions . . . . . . . . . . . . . . . 35
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41 17.1. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 35
16. Changes from Previous Versions . . . . . . . . . . . . . . . 41 17.2. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 36
16.1. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41 17.3. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 36
16.2. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42 17.4. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 36
16.3. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42 17.5. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 36
16.4. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42 17.6. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 36
16.5. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42 17.7. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 36
16.6. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42 17.8. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 36
16.7. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42 17.9. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 37
16.8. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42 17.10. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 37
16.9. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 43 17.11. Changes from draft-gellens-01 to -02 . . . . . . . . . . 37
16.10. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43 17.12. Changes from draft-gellens-00 to -01 . . . . . . . . . . 37
16.11. Changes from draft-gellens-00 to -01 . . . . . . . . . . 43 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
17. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 18.1. Normative References . . . . . . . . . . . . . . . . . . 37
17.1. Normative References . . . . . . . . . . . . . . . . . . 43 18.2. Informative references . . . . . . . . . . . . . . . . . 39
17.2. Informative references . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
Additionally, we use the following abbreviations: Additionally, we use the following abbreviations:
skipping to change at page 4, line 43 skipping to change at page 4, line 43
by allowing emergency services to respond quickly and appropriately by allowing emergency services to respond quickly and appropriately
to the specifics of the incident, often with better location to the specifics of the incident, often with better location
accuracy. accuracy.
Drivers often have a poor location awareness, especially outside of Drivers often have a poor location awareness, especially outside of
major cities, at night and when away from home (especially abroad). major cities, at night and when away from home (especially abroad).
In the most crucial cases, the victim(s) might not be able to call In the most crucial cases, the victim(s) might not be able to call
because they have been injured or trapped. because they have been injured or trapped.
For more than two decades, some vehicles have been equipped with For more than two decades, some vehicles have been equipped with
telematics systems that, among other features, place an emergency telematics systems which, among other features, place an emergency
call automatically in the event of a crash or manually in response to call automatically in the event of a crash or manually in response to
an emergency call button. Such systems generally have on-board an emergency call button. Such systems generally have on-board
location determination systems that make use of satellite-based location determination systems that make use of satellite-based
positioning technology, inertial sensors, gyroscopes, etc., which can positioning technology, inertial sensors, gyroscopes, etc., which can
provide an accurate position for the vehicle. Such built-in systems provide an accurate position for the vehicle. Such built-in systems
can take advantage of the benefits of being integrated into a can take advantage of the benefits of being integrated into a
vehicle, such as more power capacity, ability to have larger or vehicle, such as more power capacity, ability to have larger or
specialized antenna, ability to be engineered to avoid or minimise specialized antenna, ability to be engineered to avoid or minimise
degradation by vehicle glass coatings, interference from other degradation by vehicle glass coatings, interference from other
vehicle systems, etc. Thus, the PSAP can be provided with a good vehicle systems, etc. Thus, the PSAP can be provided with a good
skipping to change at page 5, line 31 skipping to change at page 5, line 31
As of the date of this document, currently deployed in-vehicle As of the date of this document, currently deployed in-vehicle
telematics systems are circuit-switched and lack a standards-based telematics systems are circuit-switched and lack a standards-based
ability to convey crash data directly to the PSAP (generally relying ability to convey crash data directly to the PSAP (generally relying
on either a human advisor or an automated text-to-speech system to on either a human advisor or an automated text-to-speech system to
provide the PSAP call taker with some crash data orally, or in some provide the PSAP call taker with some crash data orally, or in some
cases via a proprietary mechanism). In most cases, the PSAP call cases via a proprietary mechanism). In most cases, the PSAP call
taker needs to first realize that the call is related to a vehicle taker needs to first realize that the call is related to a vehicle
incident, and then listen to the data and transcribe it. Circuit- incident, and then listen to the data and transcribe it. Circuit-
switched ACN systems are referred to here as CS-ACN. switched ACN systems are referred to here as CS-ACN.
The transition to next-generation calling in general, and emergency The transition to next-generation calling in general, and for
calling in particular, provides an opportunity to vastly improve the emergency calling in particular, provides an opportunity to vastly
scope, breadth, reliability and usefulness of crash data during an improve the scope, breadth, reliability and usefulness of crash data
emergency by allowing it to be transmitted during call set-up, and to during an emergency by allowing it to be transmitted during call set-
be automatically processed by the PSAP and made available to the call up, and to be automatically processed by the PSAP and made available
taker in an integrated, automated way, as well as provide the ability to the call taker in an integrated, automated way, as well as provide
for a PSAP call taker to request that a vehicle take certain actions, the ability for a PSAP call taker to request that a vehicle take
such as flashing lights or unlocking doors. In addition, vehicle certain actions, such as flashing lights or unlocking doors. In
manufacturers are provided an opportunity to take advantage of the addition, vehicle manufacturers are provided an opportunity to take
same standardized mechanisms for data transmission and request advantage of the same standardized mechanisms for data transmission
processing for internal use if they wish (such as telemetry between and request processing for internal use if they wish (such as
the vehicle and a service center for both emergency and non-emergency telemetry between the vehicle and a service center for both emergency
uses, including location-based services, multi-media entertainment and non-emergency uses, including location-based services, multi-
systems, remote door unlocking, and road-side assistance media entertainment systems, remote door unlocking, and road-side
applications). assistance applications).
Next-generation ACN provides an opportunity for such calls to be Next-generation ACN provides an opportunity for such calls to be
recognized and processed as such during call set-up, and routed to an recognized and processed as such during call set-up, and routed to an
equipped PSAP where the vehicle data is available to assist the call equipped PSAP where the vehicle data is available to assist the call
taker in assessing and responding to the situation. Next-generation taker in assessing and responding to the situation. Next-generation
(IP-based) ACN systems are referred to here as NG-ACN. (IP-based) ACN systems are referred to here as NG-ACN.
An ACN call can initiated by a vehicle occupant or automatically An ACN call can be initiated by a vehicle occupant or automatically
initiated by vehicle systems in the event of a serious incident. initiated by vehicle systems in the event of a serious incident.
(The "A" in "ACN" does stand for "Automatic," but the term is broadly (The "A" in "ACN" does stand for "Automatic," but the term is broadly
used to refer to the class of calls that are placed by an in-vehicle used to refer to the class of calls that are placed by an in-vehicle
system (IVS) or Telematics Service Providers (TSP) and that carry system (IVS) or Telematics Service Providers (TSP) and that carry
incident-related data as well as voice.) Automatically triggered incident-related data as well as voice.) Automatically triggered
calls indicate a car crash or some other serious incident (e.g., a calls indicate a car crash or some other serious incident (e.g., a
fire). Manually triggered calls are often reports of observed fire). Manually triggered calls are often reports of observed
crashes or serious hazards (such as impaired drivers or roadway crashes or serious hazards (such as impaired drivers or roadway
debris). Depending on the design, manually triggered calls might be debris). In some implementations, manually triggered calls might be
more likely to be accidental. more likely to be accidental.
This document describes how the IETF mechanisms for IP-based This document describes how the IETF mechanisms for IP-based
emergency calls, including [RFC6443] and emergency calls, including [RFC6443] and [RFC7852], are used to
[I-D.ietf-ecrit-additional-data], are used to provide the realization provide the realization of next-generation ACN.
of next-generation ACN.
This document reuses the technical aspects of next-generation pan- This document reuses the technical aspects of next-generation pan-
European eCall (a mandated and standardized system for emergency European eCall (a mandated and standardized system for emergency
calls by in-vehicle systems within Europe and other regions), as calls by in-vehicle systems within Europe and other regions), as
described in [I-D.ietf-ecrit-ecall]. However, this document described in [I-D.ietf-ecrit-ecall]. However, this document
specifies a different set of vehicle (crash) data, specifically, the specifies a different set of vehicle (crash) data, specifically, the
Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set
of Data (MSD). This document is an extension of of Data (MSD). This document is an extension of
[I-D.ietf-ecrit-ecall], with the differences being that this document [I-D.ietf-ecrit-ecall], with the differences being that this document
makes the MSD data set optional and VEDS mandatory, and adds makes the MSD data set optional and VEDS mandatory, and adds new
extension elements, attributes, and values to the eCall metadata/ attribute values to the eCall metadata/control object defined in that
control object defined in that document. document. This document also registers a new INFO package (identical
to that defined in [I-D.ietf-ecrit-ecall] with the addition of the
VEDS MIME type).
The Association of Public-Safety Communications Officials (APCO) and The Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) have jointly the National Emergency Number Association (NENA) have jointly
developed a standardized set of incident-related vehicle data for ACN developed a standardized set of incident-related vehicle data for ACN
use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data
is often referred to as crash data although it is applicable in is often referred to as crash data although it is applicable in
incidents other than crashes. incidents other than crashes.
VEDS provides a standard data set for the transmission, exchange, and VEDS provides a standard data set for the transmission, exchange, and
interpretation of vehicle-related data. A standard data format interpretation of vehicle-related data. A standard data format
skipping to change at page 7, line 14 skipping to change at page 7, line 15
injured patients [triage-2008] [triage-2011]. These guidelines are injured patients [triage-2008] [triage-2011]. These guidelines are
designed to help responders identify the potential existence of designed to help responders identify the potential existence of
severe internal injuries and to make critical decisions about how and severe internal injuries and to make critical decisions about how and
where a patient needs to be transported. where a patient needs to be transported.
This document registers the 'application/EmergencyCallData.VEDS+xml' This document registers the 'application/EmergencyCallData.VEDS+xml'
MIME content-type, and registers the 'VEDS' entry in the Emergency MIME content-type, and registers the 'VEDS' entry in the Emergency
Call Additional Data registry. Call Additional Data registry.
VEDS is an XML structure (see [VEDS]) transported in SIP using the VEDS is an XML structure (see [VEDS]) transported in SIP using the
'application/EmergencyCallData.VEDS+xml' MIME content-type. The 'application/EmergencyCallData.VEDS+xml' MIME content-type..
'VEDS' entry in the Emergency Call Additional Data registry is used
to construct a 'purpose' parameter value to indicate VEDS data in a
Call-Info header (as described in [I-D.ietf-ecrit-additional-data]).
VEDS is a versatile structure that can accomodate varied needs. VEDS is a versatile structure that can accomodate varied needs.
However, if additional sets of data are determined to be needed However, if additional sets of data are determined to be needed
(e.g., in the future or in different regions), the steps to enable (e.g., in the future or in different regions), the steps to enable
each data block are very briefly summarized below: each data block are very briefly summarized below:
o A standardized format and encoding (such as XML) is defined and o A standardized format and encoding (such as XML) is defined and
published by a Standards Development Organization (SDO) published by a Standards Development Organization (SDO)
o A MIME Content-Type is registered for it (typically under the o A MIME Content-Type is registered for it (typically under the
'Application' media type) with a sub-type starting with 'Application' media type) with a sub-type starting with
'EmergencyCallData.' 'EmergencyCallData.'
o An entry for the block is added to the Emergency Call Additional o An entry for the block is added to the Emergency Call Additional
Data Blocks sub-registry (established by Data Blocks sub-registry (established by [RFC7852]); the registry
[I-D.ietf-ecrit-additional-data]); the registry entry is the root entry is the root of the MIME sub-type (not including the
of the MIME sub-type (not including the 'EmergencyCallData' prefix 'EmergencyCallData' prefix and any suffix such as '+xml')
and any suffix such as '+xml')
A next-generation In-Vehicle System (IVS) or TSP transmits crash data o A new INFO package is registered that permits carrying the new
by encoding it in a standardized and registered format (such as VEDS) content type and the metadata/control object (defined in
and attaching it to a SIP message as a MIME body part. The body part [I-D.ietf-ecrit-ecall]) in INFO messages.
is identified by its MIME content-type (such as 'application/
EmergencyCallData.VEDS+xml') in the Content-Type header field of the Section 6 describes how VEDA data and metadata/control are
body part. The body part is assigned a unique identifier which is transported within NG-ACN calls. Section 7 describes how such calls
listed in a Content-ID header field in the body part. The SIP are places.
message is marked as containing the crash data by adding a Call-Info
header field at the top level of the message. This Call-Info header
field contains a CID URL referencing the body part's unique
identifier, and a 'purpose' parameter identifying the data as the
crash data per the registry entry. The 'purpose' parameter's value
is 'EmergencyCallData.' plus the value associated with the data type
in the registry; for VEDS data, "purpose=EmergencyCallData.VEDS".
These mechanisms are thus used to place emergency calls that are These mechanisms are thus used to place emergency calls that are
identifiable as ACN calls and that carry one or more standardized identifiable as ACN calls and that carry standardized crash data in
crash data objects in an interoperable way. an interoperable way.
Calls by in-vehicle systems are placed via cellular networks, which Calls by in-vehicle systems are placed via cellular networks, which
might ignore location sent by an originating device in an emergency might ignore location information sent by an originating device in an
call INVITE, instead attaching their own location (often determined emergency call INVITE, instead attaching their own location
in cooperation with the originating device). Standardized crash data information (often determined in cooperation with the originating
structures often include location as determined by the IVS. A device). Standardized crash data structures often include location
benefit of this is that it allows the PSAP to see both the location as determined by the IVS. A benefit of this is that it allows the
as determined by the cellular network (often in cooperation with the PSAP to see both the location as determined by the cellular network
originating device) and the location as determined by the IVS. (often in cooperation with the originating device) and the location
as determined by the IVS.
This specification inherits the ability to utilize test call This specification inherits the ability to utilize test call
functionality from Section 15 of [RFC6881]. functionality from Section 15 of [RFC6881].
3. Document Scope 3. Document Scope
This document is focused on how an ACN emergency call is setup and This document is focused on how an ACN emergency call is setup and
incident-related data (including vehicle, sensor, and location data) incident-related data (including vehicle, sensor, and location data)
is transmitted to the PSAP using IETF specifications. For the direct is transmitted to the PSAP using IETF specifications. For the direct
model, this is the end-to-end description (between the vehicle and model, this is the end-to-end description (between the vehicle and
skipping to change at page 8, line 38 skipping to change at page 8, line 28
the TSP and the PSAP, leaving the call leg between the vehicle and the TSP and the PSAP, leaving the call leg between the vehicle and
the TSP up to the entities involved (i.e., IVS and TSP vendors) who the TSP up to the entities involved (i.e., IVS and TSP vendors) who
are then free to use the same mechanism as for the right-hand side or are then free to use the same mechanism as for the right-hand side or
not. not.
Note that Europe has a mandated and standardized system for emergency Note that Europe has a mandated and standardized system for emergency
calls by in-vehicle systems. This pan-European system is known as calls by in-vehicle systems. This pan-European system is known as
"eCall" and is the subject of a separate document, "eCall" and is the subject of a separate document,
[I-D.ietf-ecrit-ecall], which this document builds on. Vehicles [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles
designed to operate in multiple regions might need to support eCall designed to operate in multiple regions might need to support eCall
as well as the ACN described here. In this case, a vehicle IVS might as well as NG-ACN as described here. A vehicle IVS might determine
determine whether to use eCall or ACN by first determining a region whether to use eCall or ACN by first determining the region or
or country in which it is located (e.g., from a GNSS location fix country in which it is located (e.g., from a GNSS location fix and/or
and/or identity of or information from an MNO). If other regions identity of or information from an MNO). If other regions adopt
adopt other data formats, a multi-region vehicle might need to other data formats, a multi-region vehicle might need to support
support those as well. This document adopts the call set-up and those as well. This document adopts the call set-up and other
other technical aspects of [I-D.ietf-ecrit-ecall], which uses technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852];
[I-D.ietf-ecrit-additional-data]; this makes it straightforward to this makes it straightforward to use a different data set while
use a different data set while keeping other technical aspects keeping other technical aspects unchanged. Hence, both NG-eCall and
unchanged. Hence, both NG-eCall and the NG-ACN mechanism described the NG-ACN mechanism described here are compatible, differing
here are compatible, differing primarily in the specific data block primarily in the specific data block that is sent (the eCall MSD in
that is sent (the eCall MSD in the case of NG-eCall, and the APCO/ the case of NG-eCall, and the APCO/NENA VEDS used in this document),
NENA VEDS used in this document), and some additions to the metadata/ and some additions to the metadata/control data block. If other
control data block. If other regions adopt their own vehicle data regions adopt their own vehicle data sets, this can be similarly
sets, this can be similarly accomodated without changing other accomodated without changing other technical aspects. Note that any
technical aspects. additional data blocks require a new INFO package to permit transport
within INFO messages.
4. Overview of Legacy Deployment Models 4. Overview of Legacy Deployment Models
Legacy (circuit-switched) systems for placing emergency calls by in- Legacy (circuit-switched) systems for placing emergency calls by in-
vehicle systems generally have some ability to convey at least vehicle systems generally have some ability to convey at least
location and in some cases telematics data to the PSAP. Most such location and in some cases telematics data to the PSAP. Most such
systems use one of three architectural models, which are described systems use one of three architectural models, which are described
here as: "Telematics Service Provider" (TSP), "direct", and "paired". here as: "Telematics Service Provider" (TSP), "direct", and "paired".
These three models are illustrated below. These three models are illustrated below.
skipping to change at page 10, line 37 skipping to change at page 10, line 30
5. Migration to Next-Generation 5. Migration to Next-Generation
Migration of emergency calls placed by in-vehicle systems to next- Migration of emergency calls placed by in-vehicle systems to next-
generation (all-IP) technology per this document provides a generation (all-IP) technology per this document provides a
standardized mechanism to identify such calls and to present crash standardized mechanism to identify such calls and to present crash
data with the call, as well as enabling additional communications data with the call, as well as enabling additional communications
modalities and enhanced functionality. This allows ACN calls and modalities and enhanced functionality. This allows ACN calls and
crash data to be automatically processed by the PSAP and made crash data to be automatically processed by the PSAP and made
available to the call taker in an integrated, automated way. Because available to the call taker in an integrated, automated way. Because
the crash data is carried in the initial SIP INVITE (per the crash data is carried in the initial SIP INVITE (per [RFC7852])
[I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call the PSAP can present it to the call taker simultaneously with the
taker simultaneously with the appearance of the call. The PSAP can appearance of the call. The PSAP can also process the data to take
also process the data to take other actions (e.g., if multiple calls other actions (e.g., if multiple calls from the same location arrive
from the same location arrive when the PSAP is busy and a subset of when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP
them are NG-ACN calls, a PSAP might choose to store the information might choose to store the information and reject the calls, since the
and reject the calls, since the IVS will receive confirmation that IVS will receive confirmation that the information has been
the information has been successfully received; a PSAP could also successfully received; a PSAP could also choose to include a message
choose to include a message stating that it is aware of the incident stating that it is aware of the incident and responders are on the
and responders are on the way; a PSAP could call the vehicle back way; a PSAP could call the vehicle back when a call taker is
when a call taker is available). available).
Origination devices and networks, PSAPs, emergency services networks, Origination devices and networks, PSAPs, emergency services networks,
and other telephony environments are migrating to next-generation. and other telephony environments are migrating to next-generation.
This provides opportunities for significant enhancement to This provides opportunities for significant enhancement to
interoperability and functionality, especially for emergency calls interoperability and functionality, especially for emergency calls
carrying additional data such as vehicle crash data. (In the U.S., a carrying additional data such as vehicle crash data. (In the U.S., a
network specifically for emergency responders is being developed. network specifically for emergency responders is being developed.
This network, FirstNet, will be next-generation from the start, This network, FirstNet, will be next-generation from the start,
enhancing the ability for data exchange between PSAPs and enhancing the ability for data exchange between PSAPs and
responders.) responders.)
Migration to next-generation (NG) provides an opportunity to Migration to next-generation (NG) provides an opportunity to
significantly improve the handling and response to vehicle-initiated significantly improve the handling and response to vehicle-initiated
emergency calls. Such calls can be recognized as originating from a emergency calls. Such calls can be recognized as originating from a
vehicle, routed to a PSAP equipped both technically and operationally vehicle, routed to a PSAP equipped both technically and operationally
to handle such calls, and the vehicle-determined location and crash to handle such calls, and the vehicle-determined location and crash
data can be made available to the call taker simultaneously with the data can be made available to the call taker simultaneously with the
call appearance. The PSAP can take advantage of enhanced call appearance. The PSAP can take advantage of enhanced
functionality, including the ability to request the vehicle to take functionality, including the ability to request the vehicle to take
an action, such as sending an updated set of data, converying a an action, such as sending an updated set of data, converying a
message to the occupants, flashing lights, unlocking doors, etc. message to the occupants, flashing lights, unlocking doors, etc.
skipping to change at page 13, line 25 skipping to change at page 13, line 20
Figure 6: Next-Generation Paired Model Figure 6: Next-Generation Paired Model
If the call is routed to a PSAP that is not capable of processing the If the call is routed to a PSAP that is not capable of processing the
vehicle data, the PSAP ignores (or does not receive) the vehicle vehicle data, the PSAP ignores (or does not receive) the vehicle
data. This is detectable by the IVS or TSP when the status response data. This is detectable by the IVS or TSP when the status response
to the INVITE (e.., 200 OK) lacks an eCall control structure to the INVITE (e.., 200 OK) lacks an eCall control structure
acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or
TSP then proceeds as it would for a CS-ACN call (e.g., verbal TSP then proceeds as it would for a CS-ACN call (e.g., verbal
conveyance of data) conveyance of data)
6. Call Setup 6. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of
data to a SIP emergency call. This mechanism permits certain
emergency call MIME types to be attached to SIP messages. This
document makes use of that mechanism.
An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS])
by attaching it to a SIP message as a MIME body part per [RFC7852].
The body part is identified by its MIME content-type ('application/
emergencyCallData.eCall.VEDS+xml') in the Content-Type header field
of the body part. The body part is assigned a unique identifier
which is listed in a Content-ID header field in the body part. The
SIP message is marked as containing the VEDS data by adding (or
appending to) a Call-Info header field at the top level of the SIP
message. This Call-Info header field contains a CID URL referencing
the body part's unique identifier, and a 'purpose' parameter
identifying the data as a VEDS data block per the Emergency Call
Additional Data Blocks registry entry; the 'purpose' parameter's
value is 'emergencyCallData.VEDS'.
A PSAP or IVS transmits a metadata/control object (see
[I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME
body part per [RFC7852]. The body part is identified by its MIME
content-type ('application/emergencyCallData.eCall.control+xml') in
the Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header
field in the body part. The SIP message is marked as containing the
metadata/control block by adding (or appending to) a Call-Info header
field at the top level of the SIP message. This Call-Info header
field contains a CID URL referencing the body part's unique
identifier, and a 'purpose' parameter identifying the data as a
metadata/control block per the Emergency Call Additional Data Blocks
registry entry; the 'purpose' parameter's value is
'emergencyCallData.eCall.control'.
An In-Vehicle System (IVS) initiating an NG-ACN call includes in the
initial INVITE a VEDS data block and a metadata/control object
informing the PSAP of its capabilities. The PSAP creates a metadata/
control object acknowledging receipt of the VEDS data and includes it
to the SIP response to the INVITE.
A PSAP can request the vehicle to send an updated VEDS data block
during a call. The PSAP creates a metadata/control object requesting
the VEDS data and attaches it to a SIP INFO message which it sends
within the dialog. The IVS then attaches an updated VEDS data to a
SIP INFO message and sends it within the dialog. The metadata/
control object and the VEDS are attached to an INFO message in the
same way they are attached to other messages (such as the INVITE and
the reply to the INVITE as discussed above). INFO messages are sent
using an appropriate INFO Package. See Section 11 for more
information.
When data is being carried in an INFO request message, the body part
also carries a Content-Disposition header field set to "Info-
Package".
7. Call Setup
A next-generation In-Vehicle System (IVS) initiates an NG-ACN call A next-generation In-Vehicle System (IVS) initiates an NG-ACN call
with a SIP INVITE using one of the SOS sub-services with a SIP INVITE using one of the SOS sub-services
"SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI,
standard sets of crash data and capabilities data encoded in standard sets of crash data and capabilities data encoded in
standardized and registered formats, attached as additional data standardized and registered formats, attached as additional data
blocks as specified in Section 4.1 of blocks as specified in Section 4.1 of [RFC7852]. As described in
[I-D.ietf-ecrit-additional-data]. As described in that document, that document, each data block is identified by its MIME content-
each data block is identified by its MIME content-type, and pointed type, and pointed to by a CID URL in a Call-Info header with a
to by a CID URL in a Call-Info header with a 'purpose' parameter 'purpose' parameter value corresponding to the data block.
value corresponding to the data block.
Should new data blocks be needed (e.g., in other regions or in the If new data blocks are needed (e.g., in other regions or in the
future), the steps required during standardization are: future), the steps required during standardization are briefly
summarized below:
o A set of data is standardized by an SDO or appropriate o A set of data is standardized by an SDO or appropriate
organization organization
o A MIME Content-Type for the crash data set is registered with IANA o A MIME Content-Type for the crash data set is registered with IANA
* If the data is specifically for use in emergency calling, the * If the data is specifically for use in emergency calling, the
MIME type is normally under the 'application' type with a MIME type is normally under the 'application' type with a
subtype starting with 'EmergencyCallData.' subtype starting with 'EmergencyCallData.'
* If the data format is XML, then by convention the name has a * If the data format is XML, then by convention the name has a
suffix of '+xml' suffix of '+xml'
o The item is registered in the Emergency Call Additional Data o The item is registered in the Emergency Call Additional Data
registry, as defined in Section 9.1.7 of registry, as defined in Section 9.1.7 of [RFC7852]
[I-D.ietf-ecrit-additional-data]
* For emergency-call-specific formats, the registered name is the * For emergency-call-specific formats, the registered name is the
root of the MIME Content-Type (not including the root of the MIME Content-Type (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') as 'EmergencyCallData' prefix and any suffix such as '+xml') as
described in Section 4.1 of [I-D.ietf-ecrit-additional-data]. described in Section 4.1 of [RFC7852].
When placing an emergency call:
o The crash data set is created and encoded per its specification
o IVS capability data is encoded per the specification in
[I-D.ietf-ecrit-ecall] as extended in this document
o The crash data set and capabilities data are attached to the
emergency call INVITE as specified in Section 4.1 of
[I-D.ietf-ecrit-additional-data], that is, as MIME body parts
identified by the MIME Content-Type in the body part's Content-
Type header field
o Each body part is assigned a unique identifier label in the
Content-ID header field of the body part
o Call-Info header fields at the top level of the INVITE are added
that reference the crash data and capabilities data and identify
each by its MIME root (as registered in the Emergency Call
Additional Data registry)
* The crash and capabilities data are referenced in Call-Info
header fields by CID URLs that contain the unique Content ID
assigned to the body part
* The crash and capabilities data are identified in the Call-Info
header fields by a 'purpose' parameter whose value is
'EmergencyCallData.' concatenated with the specific data
block's entry in the Emergency Call Additional Data registry
* A Call-Info header field can be either solely to reference one o A new INFO package is registered that permits carrying the the new
item of data (and hence have only the one URL) or can also content type, the metadata/control object (defined in
contain other URLs referencing other data [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS
objects, in INFO messages.
o Any additional data sets are included by following the same steps When placing an emergency call, the crash data set and IVS capability
data are transported as described in Section 6.
The Vehicle Emergency Data Set (VEDS) is an XML structure defined by The Vehicle Emergency Data Set (VEDS) is an XML structure defined by
the Association of Public-Safety Communications Officials (APCO) and the Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) [VEDS]. The the National Emergency Number Association (NENA) [VEDS]. It is
'application/EmergencyCallData.VEDS+xml' MIME content-type is used to carried in body part with MIME content-type 'application/
identify it. The 'VEDS' entry in the Emergency Call Additional Data EmergencyCallData.VEDS+xml'.
registry is used to construct a 'purpose' parameter value for
conveying VEDS data in a Call-Info header.
The VEDS data is attached as a body part with MIME content type
'application/EmergencyCallData.VEDS+xml' which is pointed at by a
Call-Info URL of type CID with a 'purpose' parameter of
'EmergencyCallData.VEDS'.
Entities along the path between the vehicle and the PSAP are able to Entities along the path between the vehicle and the PSAP are able to
identify the call as an ACN call and handle it appropriately. The identify the call as an ACN call and handle it appropriately. The
PSAP is able to identify the crash data as well as any other PSAP is able to identify the crash and capabilities data attached to
additional data attached to the INVITE by examining the Call-Info the INVITE by examining the Call-Info header fields for 'purpose'
header fields for 'purpose' parameters whose values start with parameters whose values start with 'EmergencyCallData.' The PSAP is
'EmergencyCallData.' The PSAP is able to access the data it is able to access the data it is capable of handling and is interested
capable of handling and is interested in by checking the 'purpose' in by checking the 'purpose' parameter values.
parameter values.
This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- This document extends [I-D.ietf-ecrit-ecall] by reusing the call set-
up and other normative requirements with the exception that in this up and other normative requirements with the exception that in this
document, support for the eCall MSD is OPTIONAL and support for VEDS document, support for the eCall MSD is OPTIONAL and support for VEDS
in REQUIRED. This document also extends the metadata/control object in REQUIRED. This document also adds new attribute values to the
defined in [I-D.ietf-ecrit-ecall] by adding new elements, attributes, metadata/control object defined in [I-D.ietf-ecrit-ecall].
and values.
6.1. Call Routing 8. Call Routing
An Emergency Services IP Network (ESInet) is a network operated by or An Emergency Services IP Network (ESInet) is a network operated by or
on behalf of emergency services authorities. It handles emergency on behalf of emergency services authorities. It handles emergency
call routing and processing before delivery to a PSAP. In the call routing and processing before delivery to a PSAP. In the
NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2
architecture adopted by EENA, each PSAP is connected to one or more architecture adopted by EENA, each PSAP is connected to one or more
ESInets. Each originating network is also connected to one or more ESInets. Each originating network is also connected to one or more
ESInets. The ESInets maintain policy-based routing rules which ESInets. The ESInets maintain policy-based routing rules which
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
skipping to change at page 16, line 13 skipping to change at page 16, line 24
calls requiring translation or relay services). calls requiring translation or relay services).
In an environment that uses ESInets, the originating network need In an environment that uses ESInets, the originating network need
only detect that the service URN of an emergency call is or starts only detect that the service URN of an emergency call is or starts
with "sos", passing all types of emergency calls to an ESInet. The with "sos", passing all types of emergency calls to an ESInet. The
ESInet is then responsible for routing such calls to an appropriate ESInet is then responsible for routing such calls to an appropriate
PSAP. In an environment without an ESInet, the emergency services PSAP. In an environment without an ESInet, the emergency services
authorities and the originating carriers determine how such calls are authorities and the originating carriers determine how such calls are
routed. routed.
7. eCall Metadata/Control Extensions 9. New Metadata/Control Values
This document extends the eCall metadata/control structure defined in This document adds new attribute values to the metadata/control
[I-D.ietf-ecrit-ecall] by adding new elements, attributes, and structure defined in [I-D.ietf-ecrit-ecall].
values.
The <ack> element is permitted in a control block sent by the IVS In addition to the base usage from the PSAP to the IVS to
to the PSAP, to acknowledge receipt of a request by the PSAP and acknowledge receipt of crash data, the <ack> element is also
indicate if the request was carried out, when that request would contained in a metadata/control block sent by the IVS to the PSAP.
not otherwise be acknowledged (if the PSAP requests the vehicle to This is used by the IVS to acknowledge receipt of a request by the
send data and the vehicle does so, the data serves as a success PSAP and indicate if the request was carried out when that request
acknowledgement). 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).
A new <capabilities> element is added; used in a control block The <capabilities> element is used in a metadata/control block
sent from the IVS to the PSAP (e.g., in the initial INVITE) to sent from the IVS to the PSAP (e.g., in the initial INVITE) to
inform the PSAP of the vehicle capabilities. Child elements inform the PSAP of the vehicle capabilities. Child elements
contain all actions and data types supported by the vehicle and contain all actions and data types supported by the vehicle and
all available lamps (lights) and cameras. all available lamps (lights) and cameras.
New request values are added to the <request> element to enable New request values are added to the <request> element to enable
the PSAP to request the vehicle to perform actions. the PSAP to request the vehicle to perform actions.
Mandatory Actions (the IVS and the PSAP MUST support): Mandatory Actions (the IVS and the PSAP MUST support):
skipping to change at page 16, line 49 skipping to change at page 17, line 14
Optional Actions (the IVS and the PSAP MAY support): Optional Actions (the IVS and the PSAP MAY support):
o Play and/or display static (pre-defined) message o Play and/or display static (pre-defined) message
o Speak/display dynamic text (text supplied in action) o Speak/display dynamic text (text supplied in action)
o Flash or turn on or off a lamp (light) o Flash or turn on or off a lamp (light)
o Honk horn o Honk horn
o Enable a camera o Enable a camera
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 metadata/control block containing <request>
elements), and reports success or failure.
The <capabilities> element has child <request> elements to indicate The <capabilities> element has child <request> elements indicating
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. attribute is mandatory and indicates the specific action.
[I-D.ietf-ecrit-ecall] established an IANA registry to contain the [I-D.ietf-ecrit-ecall] established an IANA registry to contain the
allowed values; this document adds new values to that registry in allowed values; this document adds new values to that registry in
Table 3. Table 2.
7.1. New values for the 'action' attribute' Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block
in response to the VEDS data sent by the IVS in SIP requests other
than INFO (e.g., the INVITE). This metadata/control block is sent in
the SIP response to the request (e.g., the INVITE response). When
the PSAP needs to send a control block that is not an immediate
response to a VEDS or other data sent by the IVS, the control block
is transmitted from the PSAP to the IVS in a SIP INFO request within
the established dialog. The IVS sends the requested data (e.g., the
VEDS) or an acknowledgment (for requests other than to send data) in
a new INFO request. This mechanism flexibly allows the PSAP to send
metadata/control data to the IVS and the IVS to respond. If control
data sent in a response message requests the IVS to send a new VEDS
or other data block, or to perform an action other than sending data,
the IVS sends the requested data or an acknowledgment regarding the
action in an INFO message within the dialog.
9.1. New values for the 'action' attribute'
The following new "action" values are defined: The following new "action" values are defined:
'msg-static' displays or plays a predefined message (translated as msg-static: displays or plays a predefined message (translated as
appropriate for the language of the vehicle's interface). A registry appropriate for the language of the vehicle's interface). A
is created in Section 12.5 for messages and their IDs. Vehicles registry is created in Section 15.4 for messages and their IDs.
include the highest registered message in their <capabilities> Vehicles include the highest registered message in their
element to indicate support for all messages up to and including the <capabilities> element to indicate support for all messages up to
indicated value. and including the indicated value.
'msg-dynamic' displays or speaks (via text-to-speech) a dynamic msg-dynamic displays or speaks (via text-to-speech) a dynamic
message included in the request. message included in the request.
'honk' sounds the horn. honk sounds the horn.
'lamp' turns a lamp (light) on, off, or flashes. lamp turns a lamp (light) on, off, or flashes.
'enable-camera' adds a one-way media stream (established via SIP re- enable-camera adds a one-way media stream (established via SIP re-
INVITE sent by the vehicle) to enable the PSAP call taker to view a INVITE sent by the vehicle) to enable the PSAP call taker to view
feed from a camera. a feed from a camera.
Note that there is no 'request' action to play dynamic media (such as Note that there is no 'request' action to play dynamic media (such as
an audio message). The PSAP can send a SIP re-INVITE to establish a an audio message). The PSAP can send a SIP re-INVITE to establish a
one-way media stream for this purpose. one-way media stream for this purpose.
7.2. <ack> element extensions 9.2. Request Example
The <ack> element is extended to be 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, indicates whether the
request was successfully performed, and if not, optionally includes
an explanation.
The <ack> element has the following new child elements:
7.2.1. New Child Element of the <ack> element
The <ack> element has the following new child element:
Name: actionResult
Usage: Optional
Description: An <actionResult> element indicates the result of an
action (other than a 'send-data' action). When an <ack> element
is in response to a control object with multiple <request>
elements (that are not 'send-data' actions), the <ack> element
contains an <actionResult> element for each.
The <actionResult> element has the following
attributes:
Name: action <?xml version="1.0" encoding="UTF-8"?>
Usage: Mandatory <EmergencyCallData.eCallControl
Type: token xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
Description: Contains the value of the 'action' attribute of the xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<request> element xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
Name: success <request action="send-data" datatype="VEDS"/>
Usage: Mandatory <request action="lamp" lamp-id="hazard"
Type: Boolean lamp-action="flash" persistance="PT1H"/>
Description: Indicates if the action was successfully <request action="msg-static" msgid="1"/>
accomplished <request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text>
</request>
Name: reason </EmergencyCallData.eCallControl>
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 12.6.
Name: details Figure 7: Request Example
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"/> 9.3. The <ack> element
Example: <actionResult action="lamp" success="false" reason="unable" In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the
details="The requested lamp is inoperable"/> PSAP to acknowledge the MSD. Here, the <ack> element is also
transmitted by the PSAP to acknowledge the VEDS data and by 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
request to display a message would be acknowledged, but a request to
transmit VEDS data 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
metadata/control object containing the request(s) and indicates
whether the request was successfully performed, and if not,
optionally includes an explanation.
7.2.2. Ack Examples 9.3.1. Ack Examples
<?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 ref="1234567890@atlanta.example.com"> <ack ref="1234567890@atlanta.example.com">
<actionResult action="msg-dynamic" success="true"/> <actionResult action="msg-dynamic" success="true"/>
<actionResult action="lamp" success="false" reason="unable" <actionResult action="lamp" success="false" reason="unable"
details="The requested lamp is inoperable"/> details="The requested lamp is inoperable"/>
</ack> </ack>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
Figure 7: Ack Example from IVS to PSAP Figure 8: Ack Example from IVS to PSAP
7.3. The <capabilities> element
The <capabilities> element is transmitted by the IVS to indicate to
the PSAP its capabilities. No attributes for this element are
currently defined. The following child elements are defined:
7.3.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> 9.4. The <capabilities> element
child element with a "send-data" 'action' attribute is also
REQUIRED. The 'supported-datatypes' attribute is REQUIRED in this
<request> element within a <capabilities> element, and MUST
contain at a minimum the 'VEDS' data block value; it SHOULD
contain all data blocks supported by the IVS.
All other actions are OPTIONAL. The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by
the IVS to indicate its capabilities to the PSAP.
If the "msg-static" action is supported, a <request> child element The <capabilities> element contains a <request> child element per
with a "msg-static" 'action' attribute is sent, with a 'msgid' action supported by the vehicle. The vehicle MUST support sending
attribute set to the highest supported static message supported by the VEDS data object and so includes at a minimum a <request> child
the vehicle. A registry is created in Section 12.5 to map 'msgid' element with the 'action' attribute set to "send-data" and the
values to static text messages. By sending the highest supported 'supported-values' attribute containing all data blocks supported by
static message number in its <capabilities> element, the vehicle the IV, which MUST include 'VEDS'. All other actions are OPTIONAL.
indicates its support for all static messages in the registry up
to and including that value.
If the "lamp" action is supported, a <request> child element with If the "msg-static" action is supported, a <request> child element
a "lamp" 'action' is sent, with a 'supported-lamps' attribute set with the 'action' attribute set to "msg-static" is included, with the
to all supported lamp IDs. 'msgid' attribute set to the highest supported static message
supported by the vehicle. A registry is created in Section 15.4 to
map 'msgid' values to static text messages. By sending the highest
supported static message number in its <capabilities> element, the
vehicle indicates its support for all static messages in the registry
up to and including that value.
If the "enable-camera" action is supported, a <request> child If the "lamp" action is supported, a <request> child element with the
element with an "enable-camera" 'action' is sent, with a 'action' attribute set to "lamp" is included, with the 'supported-
'supported-cameras' attribute set to all supported camera IDs. values' attribute set to all supported lamp IDs. A registry is
created in Section 15.5 to contain lamp ID values.
Examples: If the "enable-camera" action is supported, a <request> child element
<request action="send-data" supported-datatypes="VEDS"/> with the 'action' attribute set to "enable-camera" is included, with
<request action="send-data" supported-datatypes="VEDS; eCall.MSD" the 'supported-values' attribute set to all supported camera IDs. A
/> registry is created in Section 15.6 to contain camera ID values.
<request action="msg-dynamic"/>
<request action="msg.static" msgid="17" />
7.3.2. Capabilities Example 9.4.1. Capabilities Example
<?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="VEDS"/> <request action="send-data" supported-values="VEDS"/>
<request action="lamp" <request action="lamp"
supported-lamps="head;interior;fog-front;fog-rear;brake; supported-values="head;interior;fog-front;fog-rear;brake;
position-front;position-rear;turn-left;turn-right;hazard"/> position-front;position-rear;turn-left;turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" msgid="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" supported-cameras="backup; interior"/> <request action="enable-camera" supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
Figure 8: Capabilities Example Figure 9: Capabilities Example
7.4. <request> element extensions
This document extends the <request> element to be permitted one or
more times on its own or as a child elements of a <capabilities>
element. The following new attributes, values, and child elements
are defined for the <request> element:
7.4.1. New Attributes of the <request> element
The <request> element has the following new attributes:
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 establishes an IANA registry
for messages and their IDs, in Section 12.5
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 for the duration of the ACN call.
Example: persistance="PT1H"
Name: supported-datatypes
Usage: Conditional
Type: string
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
[I-D.ietf-ecrit-additional-data]. Multiple values are separated
with a semicolon.
Example: supported-datatypes="VEDS; eCall.MSD"
Name: lamp-action
Usage: Conditional
Type: token
Description: Used with a 'lamp' action, indicates if the lamp is to
be illuminated, turned off, or flashed. Permitted values are
'on', 'off', and 'flash'.
Example: lamp-action="flash"
Name: lamp-ID
Usage: Conditional
Type: token
Description: Used with a 'lamp' action, indicates which lamp the
action affects. Permitted values are contained in the registry of
lamp-ID tokens created in Section 12.7
Example: lamp-ID="hazard"
Name: supported-lamps
Usage: Conditional
Type: string
Description: Used with a 'lamp' action in a <request> element that
is a child of a <capability> element, this attribute lists all
supported lamps, using values in the registry of lamp-ID tokens
created in Section 12.7. Multiple values are separated with a
semicolon.
Example: supported-lamps="head; interior; fog-front; fog-rear;
brake; position-front; position-rear; turn-left; turn-right;
hazard"
Name: camera-ID
Usage: Conditional
Type: token
Description: Used with an 'enable-camera' action, indicates which
camera to enable. Permitted values are contained in the registry
of camera-ID tokens created in Section 12.8. When a vehicle
camera is enabled, the IVS sends a re-INVITE to negotiate a one-
way media stream for the camera.
Example: camera-ID="backup"
Name: supported-cameras
Usage: Conditional
Type: string
Description: Used with an 'enable-camera' action in a <request>
element that is a child of a <capability> element, this attribute
lists all cameras that the vehicle supports (can add as a video
feed in the current dialog), using the same identifiers as are
used in the 'camera-ID' attribute (contained in the camera ID
registry in Section 12.8). Multiple values are separated with a
semicolon.
Example: supported-cameras="backup; interior"
7.4.2. New Child Elements of the <request> element
The <request> element has the following new 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>
7.4.3. Request Example
<?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.eCallControl
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:
eCall:control">
<request action="send-data" datatype="VEDS"/>
<request action="lamp" lamp-id="hazard"
lamp-action="flash" persistance="PT1H"/>
<request action="msg-static" msgid="1"/>
<request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text>
</request>
</EmergencyCallData.eCallControl>
Figure 9: Request Example
8. Test Calls 10. Test Calls
An NG-ACN test call is a call that is recognized and treated to some An NG-ACN test call is a call that is recognized and treated to some
extent as an NG-ACN call but not given emergency call treatment and extent as an NG-ACN call but not given emergency call treatment and
not handled by a call taker. The specific handling of test NG-ACN not handled by a call taker. The specific handling of test NG-ACN
calls is not itself standardized; the test call facility is intended calls is not itself standardized; the test call facility is intended
to allow the IVS, user, or TSP to verify that an NG-ACN call can be to allow the IVS, user, or TSP to verify that an NG-ACN call can be
successfully established with voice and/or other media communication. successfully established with voice and/or other media communication.
The IVS might also be able to verify that the crash data was The IVS might also be able to verify that the crash data was
successfully received. successfully received.
This document builds on [I-D.ietf-ecrit-ecall], which inherits the This document builds on [I-D.ietf-ecrit-ecall], which inherits the
ability to utilize test call functionality from Section 15 of ability to utilize test call functionality from Section 15 of
[RFC6881]. A service URN starting with "test." indicates a test [RFC6881]. A service URN starting with "test." indicates a test
call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall"
for test calls. for test calls.
MNOs, emergency authorities, ESInets, and PSAPs determine how to MNOs, emergency authorities, ESInets, and PSAPs determine how to
skipping to change at page 24, line 29 skipping to change at page 21, line 32
successfully processed) in addition to supporting media loopback per successfully processed) in addition to supporting media loopback per
[RFC6881]). [RFC6881]).
Note that since test calls are placed using "test" as the parent Note that since test calls are placed using "test" as the parent
service URN and "sos" as a child, such calls are not treated as an service URN and "sos" as a child, such calls are not treated as an
emergency call and so some functionality might not apply (such as emergency call and so some functionality might not apply (such as
preemption or service availability for devices lacking service ("non- preemption or service availability for devices lacking service ("non-
service-initialized" or "NSI" devices) if those are available for service-initialized" or "NSI" devices) if those are available for
emergency calls). emergency calls).
9. Example 11. The emergencyCallData.eCall.VEDS INFO package
This document registers the 'emergencyCallData.eCall.VEDS' INFO
package.
Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.VEDS' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO messages carrying data
as described here.
Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates
the ability to receive the VEDS body part as specified in [TBD: THIS
DOCUMENT] and the metadata/control body part as specified in
[I-D.ietf-ecrit-ecall].
An INFO request message carrying data related to an emergency call as
described in [TBD: THIS DOCUMENT] has an Info-Package header field
set to 'emergencyCallData.eCall.VEDS' per [RFC6086].
11.1. INFO Package Requirements
The requirements of Section 10 of [RFC6086] are addressed in the
following sections.
11.1.1. Overall Description
This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.VEDS INFO
package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information.
11.1.2. Applicability
This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, per
Section 6, and is normally carried in the initial INVITE and its
response; the use of INFO only occurs when emergency-call-related
data needs to be sent mid-call. While MESSAGE could be used, it is
not tied to a SIP dialog as is INFO and thus might not be associated
with the dialog. SIP OPTIONS or re-INVITE could also be used, but is
seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into
service, but the semantics are not a good fit, e.g., the subscribe/
notify mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport.
11.1.3. Info Package Name
The info package name is emergencyCallData.eCall.VEDS
11.1.4. Info Package Parameters
None
11.1.5. SIP Option-Tags
None
11.1.6. INFO Message Body Parts
The 'application/emergencyCallData.eCall.VEDS+xml' and 'application/
emergencyCallData.eCall.control+xml' MIME types are associated with
this INFO package. See [TBD: THIS DOCUMENT] and
[I-D.ietf-ecrit-ecall] for more information.
11.1.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT].
11.1.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the
emergencyCallData.eCall.VEDS info package is normally quite low (most
dialogs are likely to contain zero INFO requests, while others can be
expected to carry an occasional request).
11.1.9. Info Package Security Considerations
The MIME content type registations for the data blocks that can be
carried using this IFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in vehicle-initiated emergency calls as described in
that document.
11.1.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details.
11.1.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples.
12. Example
Figure 10 shows an NG-ACN call routing. The mobile network operator Figure 10 shows an NG-ACN call routing. The mobile network operator
(MNO) routes the call to an Emergency services IP Network (ESInet), (MNO) routes the call to an Emergency services IP Network (ESInet),
as for any emergency call. The ESInet routes the call to an as for any emergency call. The ESInet routes the call to an
appropriate NG-ACN-capable PSAP (using location information and the appropriate NG-ACN-capable PSAP (using location information and the
fact that that it is an NG-ACN call). The call is processed by the fact that that it is an NG-ACN call). The call is processed by the
Emergency Services Routing Proxy (ESRP), as the entry point to the Emergency Services Routing Proxy (ESRP), as the entry point to the
ESInet. The ESRP routes the call to an appropriate NG-ACN-capable ESInet. The ESRP routes the call to an appropriate NG-ACN-capable
PSAP, where the call is received by a call taker. (In deployments PSAP, where the call is received by a call taker. (In deployments
where there is no ESInet, the MNO itself routes the call directly to where there is no ESInet, the MNO itself routes the call directly to
skipping to change at page 29, line 35 skipping to change at page 28, line 51
<?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="VEDS"/> <request action="send-data" supported-datatypes="VEDS"/>
<request action="lamp" <request action="lamp"
supported-lamps="head;interior;fog-front;fog-rear; supported-values="head;interior;fog-front;fog-rear;
brake;position-front;position-rear;turn-left; brake;position-front;position-rear;turn-left;
turn-right;hazard"/> turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" msgid="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" <request action="enable-camera"
supported-cameras="backup; interior"/> supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.eCallControl> </EmergencyCallData.eCallControl>
--boundary1-- --boundary1--
Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call
10. Security Considerations 13. Security Considerations
Since this document relies on [I-D.ietf-ecrit-ecall] and Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852],
[I-D.ietf-ecrit-additional-data], the security considerations the security considerations described there and in [RFC5069] apply
described there and in [RFC5069] apply here. Implementors are here. Implementors are cautioned to read and understand the
cautioned to read and understand the discussion in those documents. discussion in those documents.
As with emergency service systems where location data is supplied or As with emergency service systems where location data is supplied or
determined with the assistance of an end host, there is the determined with the assistance of an end host, there is the
possibility that that location is incorrect, either intentially possibility that that location is incorrect, either intentially
(e.g., in a denial of service attack against the emergency services (e.g., in a denial of service attack against the emergency services
infrastructure) or due to a malfunctioning device. The reader is infrastructure) or due to a malfunctioning device. The reader is
referred to [RFC7378] for a discussion of some of these referred to [RFC7378] for a discussion of some of these
vulnerabilities. vulnerabilities.
In addition to the security considerations discussion specific to the In addition to the security considerations discussion specific to the
metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles
MAY decline to carry out any requested action (e.g., if the vehicle MAY decline to carry out any requested action (e.g., if the vehicle
requires but is unable to verify the certificate used to sign the requires but is unable to verify the certificate used to sign the
request). The vehicle MAY use any value in the reason registry to request). The vehicle MAY use any value in the reason registry to
indicate why it did not take an action (e.g., the generic "unable" or indicate why it did not take an action (e.g., the generic "unable" or
the more specific "security-failure"). the more specific "security-failure").
11. Privacy Considerations 14. Privacy Considerations
Since this document builds on [I-D.ietf-ecrit-ecall], which itself Since this document builds on [I-D.ietf-ecrit-ecall], which itself
builds on [I-D.ietf-ecrit-additional-data], the data structures builds on [RFC7852], the data structures specified there, and the
specified there, and the corresponding privacy considerations corresponding privacy considerations discussed there, apply here as
discussed there, apply here as well. The VEDS data structure well. The VEDS data structure contains optional elements that can
contains optional elements that can carry identifying and personal carry identifying and personal information, both about the vehicle
information, both about the vehicle and about the owner, as well as and about the owner, as well as location information, and so needs to
location information, and so needs to be protected against be protected against unauthorized disclosure, as discussed in
unauthorized disclosure, as discussed in
[I-D.ietf-ecrit-additional-data]. Local regulations may impose
additional privacy protection requirements.
12. IANA Considerations [RFC7852]. 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 or to an emergency services
provider (e.g., by verifying that the request for camera access is
signed by a certificate issued by an emergency services registrar).
15. IANA Considerations
This document registers the 'application/EmergencyCall.VEDS+xml' MIME This document registers the 'application/EmergencyCall.VEDS+xml' MIME
content type, and adds "VEDS" to the Emergency Call Additional Data content type, and adds "VEDS" to the Emergency Call Additional Data
registry. This document adds to and creates new sub-registries in registry. This document adds to and creates sub-registries in the
the 'eCall Control Data' registry created in [I-D.ietf-ecrit-ecall]. 'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall].
This document registers a new INFO package.
12.1. MIME Content-type Registration for 'application/ 15.1. MIME Content-type Registration for 'application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME content
according to the procedures of RFC 4288 [RFC4288] and guidelines in type according to the procedures of RFC 4288 [RFC4288] and guidelines
RFC 3023 [RFC3023]. in RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
skipping to change at page 31, line 35 skipping to change at page 31, line 4
Security considerations: Security considerations:
This content type is designed to carry vehicle crash data This content type is designed to carry vehicle crash data
during an emergency call. during an emergency call.
This data can contain personal information including vehicle This data can contain personal information including vehicle
VIN, location, direction, etc. Appropriate precautions need to VIN, location, direction, etc. Appropriate precautions need to
be taken to limit unauthorized access, inappropriate disclosure be taken to limit unauthorized access, inappropriate disclosure
to third parties, and eavesdropping of this information. to third parties, and eavesdropping of this information.
Please refer to Section 7 and Section 8 of
[I-D.ietf-ecrit-additional-data] for more information. Please refer to Section 7 and Section 8 of [RFC7852] for more
information.
When this content type is contained in a signed or encrypted When this content type is contained in a signed or encrypted
body part, the enclosing multipart (e.g., multipart/signed or body part, the enclosing multipart (e.g., multipart/signed or
multipart/encrypted) has the same Content-ID as the data part. multipart/encrypted) has the same Content-ID as the data part.
This allows an entity to identify and access the data blocks it This allows an entity to identify and access the data blocks it
is interested in without having to dive deeply into the message is interested in without having to dive deeply into the message
structure or decrypt parts it is not interested in. (The structure or decrypt parts it is not interested in. (The
'purpose' parameter in a Call-Info header field identifies the 'purpose' parameter in a Call-Info header field identifies the
data, and the CID URL points to the data block in the body, data, and the CID URL points to the data block in the body,
which has a matching Content-ID body part header field). which has a matching Content-ID body part header field).
skipping to change at page 32, line 4 skipping to change at page 31, line 23
structure or decrypt parts it is not interested in. (The structure or decrypt parts it is not interested in. (The
'purpose' parameter in a Call-Info header field identifies the 'purpose' parameter in a Call-Info header field identifies the
data, and the CID URL points to the data block in the body, data, and the CID URL points to the data block in the body,
which has a matching Content-ID body part header field). which has a matching Content-ID body part header field).
Interoperability considerations: None Interoperability considerations: None
Published specification: [VEDS] Published specification: [VEDS]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
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'
Persons and email addresses for further information: Randall Persons and email addresses for further information: Randall
Gellensm rg+ietf (at) randy.pensive.org; Hannes Tschofenig, Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig,
Hannes.Tschofenig (at) gmx.net Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
12.2. Registration of the 'VEDS' entry in the Emergency Call Additional 15.2. Registration of the 'VEDS' entry in the Emergency Call Additional
Data registry Data registry
This specification requests IANA to add the 'VEDS' entry to the This specification requests IANA to add the 'VEDS' entry to the
Emergency Call Additional Data registry, with a reference to this Emergency Call Additional Data registry, with a reference to this
document. The Emergency Call Additional Data registry has been document. The Emergency Call Additional Data registry was
established by [I-D.ietf-ecrit-additional-data]. established by [RFC7852].
12.3. Additions to the eCall Control Extension Registry
This document uses the "eCall Control Extension Registry" to add new
elements, attributes, and values to the eCall metadata/control
object, as per [I-D.ietf-ecrit-ecall]:
+-----------+---------------------+---------------------------------+
| Type | Name | Description |
+-----------+---------------------+---------------------------------+
| Attribute | msgid | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | persistance | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | supported-datatypes | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | lamp-action | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | lamp-ID | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | supported-lamps | See Section 7.2 of this |
| | | document |
| | | |
| Attribute | camera-ID | See Section 7.2 of this |
| | | document |
| | | |
| Element | text | See Section 7.4.2 of this |
| | | document |
| | | |
| Element | actionResult | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | action | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | success | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | reason | See Section 7.2.1 of this |
| | | document |
| | | |
| Attribute | details | See Section 7.2.1 of this |
| | | document |
+-----------+---------------------+---------------------------------+
Table 2: eCall Control Extension Registry New Values
12.4. eCall Action Extensions 15.3. New Action Values
This document adds new values for the 'action' attribute of the This document adds new values for the 'action' attribute of the
<request> element in the "eCall Control Action Registry" registry <request> element in the "Action Registry" registry created by
created by [I-D.ietf-ecrit-ecall]. [I-D.ietf-ecrit-ecall].
+---------------+------------------------------+ +---------------+-------------------------------------+
| Name | Description | | Name | Description |
+---------------+------------------------------+ +---------------+-------------------------------------+
| msg-static | Section 7.1 of this document | | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| msg-dynamic | Section 7.1 of this document | | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| honk | Section 7.1 of this document | | honk | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| lamp | Section 7.1 of this document | | lamp | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| enable-camera | Section 7.1 of this document | | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] |
+---------------+------------------------------+ +---------------+-------------------------------------+
Table 3: eCall Control Action Registry New Values Table 2: Action Registry New Values
12.5. eCall Static Message Registry 15.4. Static Message Registry
This document creates a new sub-registry called "eCall Static Message This document creates a new sub-registry called "Static Message
Registry" in the "eCall Control Data" registry established by Registry" in the "Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected
to support all static messages translated into all languages to support all static messages translated into all languages
supported by the vehicle, it is important to limit the number of such supported by the vehicle, it is important to limit the number of such
messages. As defined in [RFC5226], this registry operates under messages. As defined in [RFC5226], this registry operates under
"Publication Required" rules, which require a stable, public document "Publication Required" rules, which require a stable, public document
and imply expert review of the publication. The expert should and implies expert review of the publication. The expert should
determine that the document has been published by an appropriate determine that the document has been published by an appropriate
emergency services organization (e.g., NENA, EENA, APCO) or by the emergency services organization (e.g., NENA, EENA, APCO) or by the
IETF with input from an emergency services organization, and that the IETF with input from an emergency services organization, and that the
proposed message is sufficiently distinguishable from other messages. proposed message is sufficiently distinguishable from other messages.
The content of this registry includes: The contents of this registry are:
ID: An integer identifier to be used in the 'msgid' attribute of an ID: An integer identifier to be used in the 'msgid' attribute of a
eCall control <request> element. metadata/control <request> element.
Message: The text of the message. Messages are listed in the Message: The text of the message. Messages are listed in the
registry in English; vehicles are expected to implement registry in English; vehicles are expected to implement
translations into languages supported by the vehicle. translations into languages supported by the vehicle.
When new messages are added to the registry, the message text is When new messages are added to the registry, the message text is
determined by the registrant; IANA assigns the IDs. Each message is determined by the registrant; IANA assigns the IDs. Each message is
assigned a consecutive integer value as its ID. This allows an IVS assigned a consecutive integer value as its ID. This allows an IVS
to indicate by a single integer value that it supports all messages to indicate by a single integer value that it supports all messages
with that value or lower. with that value or lower.
The initial set of values is listed in Table 4. The initial set of values is listed in Table 3.
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| 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 4: eCall Static Message Registry Table 3: Static Message Registry
12.6. eCall Reason Registry
This document creates a new sub-registry called "eCall Reason
Registry" in the "eCall Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry 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 5.
+------------------+------------------------------------------------+
| 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. |
| | |
| security-failure | The authenticity of the request or the |
| | authority of the requestor could not be |
| | verified. |
+------------------+------------------------------------------------+
Table 5: eCall Reason Registry
12.7. eCall Lamp ID Registry 15.5. Lamp ID Registry
This document creates a new sub-registry called "eCall Lamp ID This document creates a new sub-registry called "Lamp ID Registry" in
Registry" in the "eCall Control Data" registry established by the "Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies
of automotive lamps (lights). As defined in [RFC5226], this registry the names of automotive lamps (lights). As defined in [RFC5226],
operates under "Expert Review" rules. The expert should determine this registry operates under "Expert Review" rules. The expert
that the proposed lamp name is clearly understandable and is should determine that the proposed lamp name is clearly
sufficiently distinguishable from other lamp names. understandable and is sufficiently distinguishable from other lamp
names.
The content of this registry includes: The contents of this registry are:
Name: The identifier to be used in the 'lamp-ID' attribute of an Name: The identifier to be used in the 'lamp-ID' attribute of a
eCall control <request> element. metadata/control <request> element.
Description: A description of the lamp (light). Description: A description of the lamp (light).
The initial set of values is listed in Table 6. The initial set of values is listed in Table 4.
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| Name | Description | | Name | Description |
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| head | The main lamps used to light the road ahead | | head | The main lamps used to light the road ahead |
| | | | | |
| interior | Interior lamp, often at the top center | | interior | Interior lamp, often at the top center |
| | | | | |
| fog-front | Front fog lamps | | fog-front | Front fog lamps |
| | | | | |
| fog-rear | Rear fog lamps | | fog-rear | Rear fog lamps |
| | | | | |
| brake | Brake indicator lamps | | brake | Brake indicator lamps |
| | | | | |
| brake-center | Center High Mounted Stop Lamp |
| | |
| position-front | Front position/parking/standing lamps | | position-front | Front position/parking/standing lamps |
| | | | | |
| position-rear | Rear position/parking/standing lamps | | position-rear | Rear position/parking/standing lamps |
| | | | | |
| 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 6: eCall Lamp ID Registry Initial Values Table 4: Lamp ID Registry Initial Values
12.8. eCall Camera ID Registry 15.6. Camera ID Registry
This document creates a new sub-registry called "eCall Camera ID This document creates a new sub-registry called "Camera ID Registry"
Registry" in the "eCall Control Data" registry established by in the "Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies
of automotive camera. As defined in [RFC5226], this registry automotive cameras. As defined in [RFC5226], this registry operates
operates under "Expert Review" rules. The expert should determine under "Expert Review" rules. The expert should determine that the
that the proposed camera name is clearly understandable and is proposed camera name is clearly understandable and is sufficiently
sufficiently distinguishable from other camera names. distinguishable from other camera names.
The content of this registry includes: The contents of this registry are:
Name: The identifier to be used in the 'camera-ID' attribute of an Name: The identifier to be used in the 'camera-ID' attribute of an
eCall control <request> element. eCall control <request> element.
Description: A description of the camera. Description: A description of the camera.
The initial set of values is listed in Table 7. The initial set of values is listed in Table 5.
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| Name | Description | | Name | Description |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| backup | Shows what is behind the vehicle, e.g., often used | | backup | Shows what is behind the vehicle, e.g., often used |
| | for driver display when the vehicle is in reverse. | | | for driver display when the vehicle is in reverse. |
| | Also known as rearview, reverse, etc. | | | Also known as rearview, reverse, rear visibility, |
| | etc. |
| | | | | |
| left-rear | Shows view to the left and behind (e.g., left side | | left-rear | Shows view to the left and behind (e.g., left side |
| | rear-view mirror or blind spot view) | | | rear-view mirror or blind spot view) |
| | | | | |
| right-rear | Shows view to the right and behind (e.g., right | | right-rear | Shows view to the right and behind (e.g., right |
| | side rear-view mirror or blind spot view) | | | side rear-view mirror or blind spot view) |
| | | | | |
| forward | Shows what is in front of the vehicle | | forward | Shows what is in front of the vehicle |
| | | | | |
| rear-wide | Shows what is behind vehicle (e.g., used by rear- | | rear-wide | Shows what is behind vehicle (e.g., used by rear- |
skipping to change at page 38, line 33 skipping to change at page 35, line 34
| | | | | |
| lane | Used by systems to identify road lane and/or | | lane | Used by systems to identify road lane and/or |
| | monitor vehicle's position within lane | | | monitor vehicle's position within lane |
| | | | | |
| interior | Shows the interior (e.g., driver) | | interior | Shows the interior (e.g., driver) |
| | | | | |
| night-front | Night-vision view of what is in front of the | | night-front | Night-vision view of what is in front of the |
| | vehicle | | | vehicle |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
Table 7: eCall Camera ID Registry Initial Values Table 5: Camera ID Registry Initial Values
13. eCall Control Block Schema
This section presents an XML schema of the eCall control block after
applying the extensions defined in this document. Note that the text
is normative; this schema is informative.
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:eCall:control"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:eCall-control"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2009/01/xml.xsd"/>
<xs:element name="EmergencyCallData.eCallControl"
type="pi:eCallControlType"/>
<xs:complexType name="eCallControlType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:choice>
<xs:element name="capabilities"
type="pi:capabilitiesType"/>
<xs:element name="request" type="pi:requestType"/>
<xs:element name="ack" type="pi:ackType"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:choice>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="ackType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="actionResult" minOccurs="0"
maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="action"
type="xs:token"
use="required"/>
<xs:attribute name="success"
type="xs:boolean"
use="required"/>
<xs:attribute name="reason"
type="xs:token">
<xs:annotation>
<xs:documentation>conditionally
mandatory when @success='false"
to indicate reason code for a
failure </xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="details"
type="xs:string"/>
<xs:anyAttribute processContents="skip"/>
</xs:complexType>
</xs:element>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ref"
type="xs:anyURI"
use="required"/>
<xs:attribute name="received"
type="xs:boolean"/>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="capabilitiesType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence minOccurs="1" maxOccurs="unbounded">
<xs:element name="request"
type="pi:requestType"
minOccurs="1"
maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="requestType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:any namespace="##other" processContents="lax"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:choice>
<xs:attribute name="action" type="xs:token" use="required"/>
<xs:attribute name="msgid" type="xs:unsignedInt"/>
<xs:attribute name="persistence" type="xs:duration"/>
<xs:attribute name="datatype" type="xs:token"/>
<xs:attribute name="supported-datatypes" type="xs:string"/>
<xs:attribute name="lamp-id" type="xs:token"/>
<xs:attribute name="lamp-action">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=""/>
<xs:pattern value=""/>
<xs:enumeration value="on"/>
<xs:enumeration value="off"/>
<xs:enumeration value="flash"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="supported-lamps" type="xs:string"/>
<xs:attribute name="camera-id" type="xs:token"/>
<xs:attribute name="supported-cameras" type="xs:string"/>
<xs:anyAttribute/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:schema>
Figure 12: eCall Control Block Schema
14. Contributors 16. Acknowledgements
We would like to thank Ulrich Dietz for his help with earlier We would like to thank Christer Holmberg for his suggestions; Michael
versions of the original version of this document. Montag, Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom,
and Rex Buddenberg for their feedback; and Ulrich Dietz for his help
with earlier versions of the original version of this document.
15. Acknowledgements 17. Changes from Previous Versions
We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, 17.1. Changes from draft-ietf-08 to draft-ietf-09
Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback.
16. Changes from Previous Versions o Added INFO package registration for eCall.VEDS
o Moved <capabilities> element and other extension points back to
eCall document so that extension points are in base spec (and also
to get XML schema to compile)
o Text changes for clarification.
16.1. Changes from draft-ietf-07 to draft-ietf-08 17.2. Changes from draft-ietf-07 to draft-ietf-08
o Moved much of the metadata/control object from o Moved much of the metadata/control object from
[I-D.ietf-ecrit-ecall] to this document as extensions [I-D.ietf-ecrit-ecall] to this document as extensions
o Editorial clarifications and simplifications o Editorial clarifications and simplifications
o Moved "Call Routing" to be a subsection of "Call Setup" o Moved "Call Routing" to be a subsection of "Call Setup"
o Deleted "Profile" section and moved some of its text into o Deleted "Profile" section and moved some of its text into
"Introduction" "Introduction"
16.2. Changes from draft-ietf-06 to draft-ietf-07 17.3. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes o Minor editorial changes
16.3. Changes from draft-ietf-05 to draft-ietf-06 17.4. Changes from draft-ietf-05 to draft-ietf-06
o Added clarifying text regarding signed and encrypted data o Added clarifying text regarding signed and encrypted data
o Additional informative text in "Migration to Next-Generation" o Additional informative text in "Migration to Next-Generation"
section section
o Additional clarifying text regarding security and privacy. o Additional clarifying text regarding security and privacy.
16.4. Changes from draft-ietf-04 to draft-ietf-05 17.5. Changes from draft-ietf-04 to draft-ietf-05
o Reworded security text in main document and in MIME registration o Reworded security text in main document and in MIME registration
for the VEDS object for the VEDS object
16.5. Changes from draft-ietf-03 to draft-ietf-04 17.6. Changes from draft-ietf-03 to draft-ietf-04
o Added example VEDS object o Added example VEDS object
o Additional clarifications and corrections o Additional clarifications and corrections
o Removed references from Abstract o Removed references from Abstract
o Moved Document Scope section to follow Introduction o Moved Document Scope section to follow Introduction
16.6. Changes from draft-ietf-02 to draft-ietf-03 17.7. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
16.7. Changes from draft-ietf-01 to draft-ietf-02 17.8. Changes from draft-ietf-01 to draft-ietf-02
o This document now refers to [I-D.ietf-ecrit-ecall] for technical o This document now refers to [I-D.ietf-ecrit-ecall] for technical
aspects including the service URN; this document no longer aspects including the service URN; this document no longer
proposes a unique service URN for non-eCall NG-ACN calls; the same proposes a unique service URN for non-eCall NG-ACN calls; the same
service URN is now used for all NG-ACN calls including NG-eCall service URN is now used for all NG-ACN calls including NG-eCall
and non-eCall and non-eCall
o Added discussion of an NG-ACN call placed to a PSAP that doesn't o Added discussion of an NG-ACN call placed to a PSAP that doesn't
support it support it
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
16.8. Changes from draft-ietf-00 to draft-ietf-01 17.9. 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 such as eCall crash notification specifications such as eCall
o Minor wording improvements and clarifications o Minor wording improvements and clarifications
16.9. Changes from draft-gellens-02 to draft-ietf-00 17.10. Changes from draft-gellens-02 to draft-ietf-00
o Renamed from draft-gellens- to draft-ietf- o Renamed from draft-gellens- to draft-ietf-
o Added text to Introduction to clarify that during a CS ACN, the o Added text to Introduction to clarify that during a CS ACN, the
PSAP call taker usually needs to listen to the data and transcribe PSAP call taker usually needs to listen to the data and transcribe
it it
16.10. Changes from draft-gellens-01 to -02 17.11. Changes from draft-gellens-01 to -02
o Fixed case of 'EmergencyCallData', in accordance with changes to o Fixed case of 'EmergencyCallData', in accordance with changes to
[I-D.ietf-ecrit-additional-data] [RFC7852]
16.11. Changes from draft-gellens-00 to -01 17.12. 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 [RFC7852]
[I-D.ietf-ecrit-additional-data]
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
[I-D.ietf-ecrit-additional-data] 18.1. Normative References
Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency
Call", draft-ietf-ecrit-additional-data-38 (work in
progress), April 2016.
[I-D.ietf-ecrit-ecall] [I-D.ietf-ecrit-ecall]
Gellens, R. and H. Tschofenig, "Next-Generation Pan- Gellens, R. and H. Tschofenig, "Next-Generation Pan-
European eCall", draft-ietf-ecrit-ecall-07 (work in European eCall", draft-ietf-ecrit-ecall-10 (work in
progress), February 2016. progress), July 2016.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
<http://www.rfc-editor.org/info/rfc3023>. <http://www.rfc-editor.org/info/rfc3023>.
skipping to change at page 44, line 41 skipping to change at page 38, line 41
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, DOI 10.17487/RFC6443, December Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>. 2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>. <http://www.rfc-editor.org/info/rfc6881>.
[RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency
Call", RFC 7852, DOI 10.17487/RFC7852, July 2016,
<http://www.rfc-editor.org/info/rfc7852>.
[VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/
NENA Data Standardization Workgroup, , "Vehicular NENA Data Standardization Workgroup, , "Vehicular
Emergency Data Set (VEDS) version 3", July 2012, Emergency Data Set (VEDS) version 3", July 2012,
<https://www.apcointl.org/resources/telematics/aacn-and- <https://www.apcointl.org/resources/telematics/aacn-and-
veds.html>. veds.html>.
17.2. Informative references 18.2. Informative references
[RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, DOI 10.17487/RFC5012, January 2008, RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>. <http://www.rfc-editor.org/info/rfc5012>.
[RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, Emergency Call Marking and Mapping", RFC 5069,
DOI 10.17487/RFC5069, January 2008, DOI 10.17487/RFC5069, January 2008,
<http://www.rfc-editor.org/info/rfc5069>. <http://www.rfc-editor.org/info/rfc5069>.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
"Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378,
December 2014, <http://www.rfc-editor.org/info/rfc7378>. December 2014, <http://www.rfc-editor.org/info/rfc7378>.
[triage-2008] [triage-2008]
National Center for Injury Prevention and Control, and National Center for Injury Prevention and Control, and
Centers for Disease Control and Prevention, Centers for Disease Control and Prevention,
"Recommendations from the Expert Panel: Advanced Automatic "Recommendations from the Expert Panel: Advanced Automatic
Collision Notification and Triage of the Injured Patient", Collision Notification and Triage of the Injured Patient",
2008, <https://stacks.cdc.gov/view/cdc/5304/>. 2008, <https://stacks.cdc.gov/view/cdc/5304/>.
skipping to change at page 45, line 35 skipping to change at page 39, line 47
for field triage of injured patients: recommendations of for field triage of injured patients: recommendations of
the National Expert Panel on Field Triage", January 2012, the National Expert Panel on Field Triage", January 2012,
<https://www.researchgate.net/journal/1545-8601_MMWR_Recom <https://www.researchgate.net/journal/1545-8601_MMWR_Recom
mendations_and_reports_Morbidity_and_mortality_weekly_repo mendations_and_reports_Morbidity_and_mortality_weekly_repo
rt_Recommendations_and_reports_Centers_for_Disease_Control rt_Recommendations_and_reports_Centers_for_Disease_Control
>. >.
Authors' Addresses Authors' Addresses
Randall Gellens Randall Gellens
Consultant Core Technology Consulting
6755 Mira Mesa Blvd 123-151
San Diego 92121
US
Email: rg+ietf@randy.pensive.org Email: rg+ietf@randy.pensive.org
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US US
Email: br@brianrosen.net Email: br@brianrosen.net
Hannes Tschofenig Hannes Tschofenig
Individual 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. 137 change blocks. 
803 lines changed or deleted 576 lines changed or added

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