< draft-ietf-ecrit-car-crash-14.txt   draft-ietf-ecrit-car-crash-15.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: April 12, 2017 NeuStar, Inc. Expires: April 15, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
October 9, 2016 October 12, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-14.txt draft-ietf-ecrit-car-crash-15.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 Emergency Call This document also registers a MIME Content Type and Emergency 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) and an INFO package to enable carrying this and
contents, and structure are referenced in this document. related data in INFO requests. An external specification for the
data format, 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 adds document makes the MSD data set optional and VEDS mandatory, and adds
attribute values to the eCall metadata/control object to permit attribute values to the metadata/control object to permit greater
greater functionality. This document registers a new INFO package functionality. This document registers a new INFO package (identical
(identical to that registered for eCall but with the addition of the to that registered for eCall but with the addition of the VEDS MIME
VEDS MIME type). This document also describes legacy (circuit- type). This document also describes legacy (circuit-switched) ACN
switched) ACN systems and their migration to next-generation systems and their migration to next-generation emergency calling, to
emergency calling, to provide background information and context. 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 April 12, 2017. This Internet-Draft will expire on April 15, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . 9
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13
8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 16
9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 9. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. New values for the 'action' attribute' . . . . . . . . . 19 10. New Metadata/Control Values . . . . . . . . . . . . . . . . . 18
9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19 10.1. New values for the 'action' attribute' . . . . . . . . . 19
9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 20 10.2. Request Example . . . . . . . . . . . . . . . . . . . . 20
9.4. The <capabilities> element . . . . . . . . . . . . . . . 21 10.3. The <ack> element . . . . . . . . . . . . . . . . . . . 20
10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 22 10.4. The <capabilities> element . . . . . . . . . . . . . . . 21
11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23
11.1. Overall Description . . . . . . . . . . . . . . . . . . 23 11. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 22
11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24 12. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23
11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24 12.1. Overall Description . . . . . . . . . . . . . . . . . . 23
11.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 12.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24
11.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 12.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24
11.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24 12.4. Info Package Parameters . . . . . . . . . . . . . . . . 24
11.7. Info Package Usage Restrictions . . . . . . . . . . . . 25 12.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24
11.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 12.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24
11.9. Info Package Security Considerations . . . . . . . . . . 25 12.7. Info Package Usage Restrictions . . . . . . . . . . . . 25
11.10. Implementation Details . . . . . . . . . . . . . . . . . 25 12.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25
11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 25 12.9. Info Package Security Considerations . . . . . . . . . . 25
12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 12.10. Implementation Details . . . . . . . . . . . . . . . . . 25
13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 12.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 26
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 13. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 14. Security Considerations . . . . . . . . . . . . . . . . . . . 31
15.1. MIME Content-type Registration for 15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
16.1. MIME Content-type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32
15.2. Registration of the 'VEDS' entry in the Emergency Call 16.2. Registration of the 'VEDS' entry in the Emergency Call
Additional Data registry . . . . . . . . . . . . . . . . 33 Additional Data registry . . . . . . . . . . . . . . . . 33
15.3. New Action Values . . . . . . . . . . . . . . . . . . . 33 16.3. New Action Values . . . . . . . . . . . . . . . . . . . 34
15.4. Static Message Registry . . . . . . . . . . . . . . . . 34 16.4. Static Message Registry . . . . . . . . . . . . . . . . 34
15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35 16.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35
15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36 16.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
17. Changes from Previous Versions . . . . . . . . . . . . . . . 37 18. Changes from Previous Versions . . . . . . . . . . . . . . . 37
17.1. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 37 18.1. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 37
17.2. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38 18.2. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38
17.3. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38 18.3. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38
17.4. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 18.4. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38
17.5. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 18.5. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38
17.6. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 18.6. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
17.7. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 18.7. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
17.8. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 18.8. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39
17.9. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39 18.9. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39
17.10. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 18.10. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
17.11. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 18.11. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
17.12. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 18.12. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
17.13. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 18.13. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39
17.14. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39 18.14. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39
17.15. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40 18.15. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 40
17.16. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40 18.16. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40
18. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 18.17. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
18.1. Normative References . . . . . . . . . . . . . . . . . . 40 19. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
18.2. Informative references . . . . . . . . . . . . . . . . . 41 19.1. Normative References . . . . . . . . . . . . . . . . . . 40
19.2. Informative references . . . . . . . . . . . . . . . . . 41
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
1. Terminology 1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
This document re-uses terminology defined in Section 3 of [RFC5012]. This document re-uses terminology defined in Section 3 of [RFC5012].
skipping to change at page 6, line 33 skipping to change at page 6, line 33
(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). In some implementations, 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
emergency calls, including [RFC6443] and [RFC7852], are used to
provide the realization of next-generation ACN.
This document reuses the technical aspects of next-generation pan-
European eCall (a mandated and standardized system for emergency
calls by in-vehicle systems within Europe and other regions), as
described in [I-D.ietf-ecrit-ecall]. However, this document
specifies a different set of vehicle (crash) data, specifically, the
Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set
of Data (MSD). This document is an extension of
[I-D.ietf-ecrit-ecall], with the differences being that this document
makes the MSD data set optional and VEDS mandatory, and adds new
attribute values to the eCall metadata/control object defined in that
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 This document describes how the IETF mechanisms for IP-based
interpretation of vehicle-related data. A standard data format emergency calls are used to provide the realization of next-
allows the data to be generated by an IVS or TSP and interpreted by generation ACN.
PSAPs, emergency responders, and medical facilities. It includes
incident-related information such as airbag deployment, location and
compass orientation of the vehicle, spatial orientation of the
vehicle (e.g., upright, on its side or top or a bumper), various
sensor data that can indicate the potential severity of the crash and
the likelihood of severe injuries to the vehicle occupants, etc.
This data better informs the PSAP and emergency responders as to the
type of response that might be needed. Some of this information has
been included in U.S. government guidelines for field triage of
injured patients [triage-2008] [triage-2011]. These guidelines are
designed to help responders identify the potential existence of
severe internal injuries and to make critical decisions about how and
where a patient needs to be transported.
This document registers the 'application/EmergencyCallData.VEDS+xml'
MIME content-type, and registers the 'VEDS' entry in the Emergency
Call Additional Data registry.
VEDS is an XML structure (see [VEDS]) transported in SIP using the
'application/EmergencyCallData.VEDS+xml' MIME content-type..
VEDS is a versatile structure that can accomodate varied needs.
However, if additional sets of data are determined to be needed
(e.g., in the future or in different regions), the steps to enable
each data block are very briefly summarized below:
o A standardized format and encoding (such as XML) is defined and
published by a Standards Development Organization (SDO)
o A MIME Content-Type is registered for it (typically under the
'Application' media type) with a sub-type starting with
'EmergencyCallData.'
o An entry for the block is added to the Emergency Call Additional This document reuses the technical aspects of next-generation pan-
Data Blocks sub-registry (established by [RFC7852]); the registry European eCall (a mandated and standardized system for emergency
entry is the root of the MIME sub-type (not including the calls by in-vehicle systems within Europe), as described in
'EmergencyCallData' prefix and any suffix such as '+xml') [I-D.ietf-ecrit-ecall]. However, this document specifies a different
set of vehicle (crash) data, specifically, the Vehicle Emergency Data
Set (VEDS) rather than the eCall Minimum Set of Data (MSD). This
document is an extension of [I-D.ietf-ecrit-ecall], with the
differences being that this document makes the MSD data set optional
and VEDS mandatory, and adds new attribute values to the metadata/
control object defined in that 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).
o A new INFO package is registered that permits carrying the new This document registers the 'application/EmergencyCallData.VEDS+xml'
content type and the metadata/control object (defined in MIME content-type, registers the 'VEDS' entry in the Emergency Call
[I-D.ietf-ecrit-ecall]) in INFO requests. Additional Data registry, and registers an INFO package to enable
carrying this and related data in INFO requests.
Section 6 describes how VEDS data and metadata/control are Section 6 introduces VEDS. Section 7 describes how VEDS data and
transported within NG-ACN calls. Section 7 describes how such calls metadata/control blocks are transported within NG-ACN calls.
are placed. Section 8 describes how such calls are placed.
These mechanisms are thus used to place emergency calls that are These mechanisms are used to place emergency calls that are
identifiable as ACN calls and that carry standardized crash data in identifiable as ACN calls and that carry standardized crash data in
an interoperable way. an interoperable way.
Calls by in-vehicle systems are placed using cellular networks, which Calls by in-vehicle systems are placed using cellular networks, which
might ignore location information sent by an originating device in an might ignore location information sent by an originating device in an
emergency call INVITE, instead attaching their own location emergency call INVITE, instead attaching their own location
information (often determined in cooperation with the originating information (often determined in cooperation with the originating
device). Standardized crash data structures often include location device). Standardized crash data structures often include location
as determined by the IVS. A benefit of this is that it allows the as determined by the IVS. A benefit of this is that it allows the
PSAP to see both the location as determined by the cellular network PSAP to see both the location as determined by the cellular network
skipping to change at page 8, line 49 skipping to change at page 8, line 6
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 NG-ACN as described here. A vehicle IVS might determine as well as NG-ACN as described here. A vehicle IVS might determine
whether to use eCall or ACN by first determining the region or whether to use eCall or ACN by first determining the region or
country in which it is located (e.g., from a GNSS location fix and/or country in which it is located (e.g., from a GNSS location estimate
identity of or information from an MNO). If other regions adopt and/or identity of or information from an MNO). If other regions
other data formats, a multi-region vehicle might need to support adopt other data formats, a multi-region vehicle might need to
those as well. This document adopts the call set-up and other support those as well. This document adopts the call set-up and
technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852]; other technical aspects of [I-D.ietf-ecrit-ecall], which uses
this makes it straightforward to use a different data set while [RFC7852]; this makes it straightforward to use a different data set
keeping other technical aspects unchanged. Hence, both NG-eCall and while keeping other technical aspects unchanged. Hence, both NG-
the NG-ACN mechanism described here are compatible, differing eCall and the NG-ACN mechanism described here are compatible,
primarily in the specific data block that is sent (the eCall MSD in differing primarily in the specific data block that is sent (the
the case of NG-eCall, and the APCO/NENA VEDS used in this document), eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in
and some additions to the metadata/control data block. If other this document), and some additions to the metadata/control data
regions adopt their own vehicle data sets, this can be similarly block. If other regions adopt their own vehicle data sets, this can
accomodated without changing other technical aspects. Note that any be similarly accomodated without changing other technical aspects.
additional data blocks require a new INFO package to permit transport Note that any additional data formats require a new INFO package to
within INFO requests. permit transport within INFO requests.
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 13, line 36 skipping to change at page 12, line 45
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 a control structure acknowledging to the INVITE (e.., 200 OK) lacks a control structure acknowledging
receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then 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 conveyance of proceeds as it would for a CS-ACN call (e.g., verbal conveyance of
data) data)
6. Data Transport 6. Vehicle Data
The Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) have jointly
developed a standardized set of incident-related vehicle data for ACN
use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data
is often referred to as crash data although it is applicable in
incidents other than crashes.
VEDS provides a standard data set for the transmission, exchange, and
interpretation of vehicle-related data. A standard data format
allows the data to be generated by an IVS or TSP and interpreted by
PSAPs, emergency responders, and medical facilities. It includes
incident-related information such as airbag deployment, location and
compass orientation of the vehicle, spatial orientation of the
vehicle (e.g., upright, on its side or roof or a bumper), various
sensor data that can indicate the potential severity of the crash and
the likelihood of severe injuries to the vehicle occupants, etc.
This data better informs the PSAP and emergency responders as to the
type of response that might be needed. Some of this information has
been included in U.S. government guidelines for field triage of
injured patients [triage-2008] [triage-2011]. These guidelines are
designed to help responders identify the potential existence of
severe internal injuries and to make critical decisions about how and
where a patient needs to be transported.
VEDS is an XML structure (see [VEDS]) transported in SIP using the
'application/EmergencyCallData.VEDS+xml' MIME content-type.
VEDS is a versatile structure that can accomodate varied needs.
However, if additional sets of data are needed (e.g., in the future
or in different regions), the steps to enable each data block are
very briefly summarized below:
o A standardized format and encoding (such as XML) is defined and
published by a Standards Development Organization (SDO)
o A MIME Content-Type is registered for it (typically under the
'Application' media type) with a sub-type in the
'EmergencyCallData.' tree
o An entry for the block is added to the Emergency Call Additional
Data Blocks sub-registry (established by [RFC7852]); the registry
entry is the root of the MIME sub-type (not including the
'EmergencyCallData.' prefix and any suffix such as '+xml')
o A new INFO package is registered that permits carrying the new
content type and the metadata/control object (defined in
[I-D.ietf-ecrit-ecall]) in INFO requests.
7. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of [RFC7852] establishes a general mechanism for attaching blocks of
data to a SIP emergency call. This mechanism permits certain data to a SIP emergency call. This mechanism permits certain
emergency call MIME types to be attached to SIP messages. This emergency call MIME types to be attached to SIP messages. This
document makes use of that mechanism. This document also registers document makes use of that mechanism. This document also registers
an INFO package (in Section 11) to enable NG-ACN related data blocks an INFO package (in Section 12) to enable NG-ACN related data blocks
to be carried in SIP INFO requests (per [RFC6086], new INFO usages to be carried in SIP INFO requests (per [RFC6086], new INFO usages
require the definition of an INFO package). require the definition of an INFO package).
An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 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]. 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/ The body part is identified by its MIME content-type ('application/
emergencyCallData.VEDS+xml') in the Content-Type header field of the emergencyCallData.VEDS+xml') in the Content-Type header field of the
body part. The body part is assigned a unique identifier which is 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 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 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. 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 This Call-Info header field contains a CID URL referencing the body
part's unique identifier, and a 'purpose' parameter identifying the part's unique identifier, and a 'purpose' parameter identifying the
data as a VEDS data block per the Emergency Call Additional Data data as a VEDS data block per the Emergency Call Additional Data
Blocks registry entry; the 'purpose' parameter's value is Blocks registry entry; the 'purpose' parameter's value is
'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO 'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO
request by using the INFO package defined in Section 11. request by using the INFO package defined in Section 12.
A PSAP or IVS transmits a metadata/control object (see 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 [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 body part per [RFC7852]. The body part is identified by its MIME
content-type ('application/emergencyCallData.control+xml') in the content-type ('application/emergencyCallData.control+xml') in the
Content-Type header field of the body part. The body part is Content-Type header field of the body part. The body part is
assigned a unique identifier which is listed in a Content-ID header assigned a unique identifier which is listed in a Content-ID header
field in the body part. The SIP message is marked as containing the 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 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 at the top level of the SIP message. This Call-Info header
field contains a CID URL referencing the body part's unique field contains a CID URL referencing the body part's unique
identifier, and a 'purpose' parameter identifying the data as a identifier, and a 'purpose' parameter identifying the data as a
metadata/control block per the Emergency Call Additional Data Blocks metadata/control block per the Emergency Call Additional Data Blocks
registry entry; the 'purpose' parameter's value is registry entry; the 'purpose' parameter's value is
'emergencyCallData.control'. A metadata/control object is carried in 'emergencyCallData.control'. A metadata/control object is carried in
a SIP INFO request by using the INFO package defined in Section 11. a SIP INFO request by using the INFO package defined in Section 12.
A body part containing a VEDS or metadata/control object has a A body part containing a VEDS or metadata/control object has a
Content-Disposition header field value containing "By-Reference" and Content-Disposition header field value containing "By-Reference" and
is always enclosed in a multipart body part. (In some cases, there is always enclosed in a multipart body part (even if it would
might be intermediate multipart body parts between the top level otherwise be the only body part in the SIP message), since as of the
multipart/mixed and the body part containing the VEDS or metadata/ date of this document, the use of Content-ID as a SIP header field is
control object.) not defined (while it is defined for use as a MIME header field).
An In-Vehicle System (IVS) initiating an NG-ACN call includes in the An In-Vehicle System (IVS) initiating an NG-ACN call includes in the
initial INVITE a VEDS data block and a metadata/control object initial INVITE a VEDS data block and a metadata/control object
informing the PSAP of its capabilities. The VEDS and metadata/ informing the PSAP of its capabilities. The VEDS and metadata/
control body parts (and PIDF-LO) have a Content-Disposition header control body parts (and PIDF-LO) have a Content-Disposition header
field with the value "By-Reference; handling=optional". Specifying field with the value "By-Reference; handling=optional". Specifying
handling=optional prevents the INVITE from being rejected if it is handling=optional prevents the INVITE from being rejected if it is
processed by a legacy element (e.g., a gateway between SIP and processed by a legacy element (e.g., a gateway between SIP and
circuit-switched environments) that does not understand the VEDS or circuit-switched environments) that does not understand the VEDS or
metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/
skipping to change at page 15, line 18 skipping to change at page 15, line 27
A PSAP can request that the vehicle send an updated VEDS data block A PSAP can request that the vehicle send an updated VEDS data block
during a call. To do so, the PSAP creates a metadata/control object during a call. To do so, the PSAP creates a metadata/control object
requesting VEDS data and attaches it to a SIP INFO request and sends requesting VEDS data and attaches it to a SIP INFO request and sends
it within the dialog. The IVS then attaches an updated VEDS data it within the dialog. The IVS then attaches an updated VEDS data
object to a SIP INFO request and sends it within the dialog. If the object to a SIP INFO request and sends it within the dialog. If the
IVS is unable to send the VEDS, it instead sends a metadata/control IVS is unable to send the VEDS, it instead sends a metadata/control
object acknowledging the request with the 'success' parameter set to object acknowledging the request with the 'success' parameter set to
'false' and a 'reason' parameter (and optionally a 'details' 'false' and a 'reason' parameter (and optionally a 'details'
parameter) indicating why the request cannot be accomplished. Per parameter) indicating why the request cannot be accomplished. Per
[RFC6086], metadata/control objects and VEDS data are sent using the [RFC6086], metadata/control objects and VEDS data are sent using the
INFO package defined in Section 11. In addition, to align with the INFO package defined in Section 12. In addition, to align with the
way a VEDS or metadata/control block is transmitted in a SIP message way a VEDS or metadata/control block is transmitted in a SIP message
other than an INFO request, one or more Call-Info header fields are other than an INFO request, one or more Call-Info header fields are
included in the SIP INFO request to reference the VEDS or metadata/ included in the SIP INFO request to reference the VEDS or metadata/
control block. See Section 11 for more information on the use of control block. See Section 12 for more information on the use of
INFO requests within NG-ACN calls. INFO requests within NG-ACN calls.
Any metadata/control object sent by a PSAP can request that the Any metadata/control object sent by a PSAP can request that the
vehicle perform an action (such as sending a data block, flashing vehicle perform an action (such as sending a data block, flashing
lights, providing a camera feed, etc.) The vehicle sends an lights, providing a camera feed, etc.) The vehicle sends an
acknowledgement for any request other than a successfully executed acknowledgement for any request other than a successfully executed
send-data action. Multiple requests with the same 'action' value send-data action. Multiple requests with the same 'action' value
MUST be sent in separate body parts (to avoid any ambiguity in the MUST be sent in separate body parts (to avoid any ambiguity in the
acknowledgement). acknowledgement).
If the IVS is aware that VEDS data it sent previously has changed, it If the IVS is aware that VEDS data it sent previously has changed, it
MAY send an unsolicited VEDS (in any convenient SIP message, MAY send an unsolicited VEDS in any convenient SIP message, including
including an INFO request) during the call. The PSAP sends an an INFO request during the call. The PSAP sends an acknowledgment
acknowledgment for an unsolicited VEDS object (if the IVS sent the for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS
unsolicited VEDS in an INFO request, the acknowledgment is sent in a in an INFO request, the acknowledgment is sent in a new INFO request,
new INFO request, otherwise it is sent in the response to the message otherwise it is sent in the response to the message containing the
containing the VEDS). VEDS).
7. Call Setup 8. 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 [RFC7852]. As described in blocks as specified in Section 4.1 of [RFC7852]. As described in
that document, each data block is identified by its MIME content- that document, each data block is identified by its MIME content-
type, and pointed to by a CID URL in a Call-Info header with a type, and pointed to by a CID URL in a Call-Info header with a
'purpose' parameter value corresponding to the data block. 'purpose' parameter value corresponding to the data block.
skipping to change at page 16, line 35 skipping to change at page 16, line 47
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 [RFC7852]. described in Section 4.1 of [RFC7852].
o A new INFO package is registered that permits carrying the the new o A new INFO package is registered that permits carrying the the new
content type, the metadata/control object (defined in content type, the metadata/control object (defined in
[I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS
objects, in INFO messages. objects, in INFO messages.
When placing an emergency call, the crash data set and IVS capability When placing an emergency call, the crash data set and IVS capability
data are transported as described in Section 6. data are transported as described in Section 7.
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]. It is the National Emergency Number Association (NENA) [VEDS]. It is
carried in body part with MIME content-type 'application/ carried in body part with MIME content-type 'application/
EmergencyCallData.VEDS+xml'. EmergencyCallData.VEDS+xml'.
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 and capabilities data attached to PSAP is able to identify the crash and capabilities data attached to
skipping to change at page 17, line 8 skipping to change at page 17, line 21
parameters whose values start with 'EmergencyCallData.' The PSAP is parameters whose values start with 'EmergencyCallData.' The PSAP is
able to access the data it is capable of handling and is interested able to access the data it is capable of handling and is interested
in by checking the 'purpose' parameter values. in by checking the 'purpose' 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 adds new attribute values to the in REQUIRED. This document also adds new attribute values to the
metadata/control object defined in [I-D.ietf-ecrit-ecall]. metadata/control object defined in [I-D.ietf-ecrit-ecall].
8. Call Routing 9. 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 that ESInets. The ESInets maintain policy-based routing rules that
control the routing and processing of emergency calls. The control the routing and processing of emergency calls. The
centralization of such rules within ESInets allows for a cleaner centralization of such rules within ESInets allows for a cleaner
skipping to change at page 17, line 36 skipping to change at page 18, line 5
(e.g., cooperative agreements to specially handle calls requiring (e.g., cooperative agreements to specially handle calls requiring
translation or relay services). translation or relay services).
In an environment that uses ESInets, the originating network might In an environment that uses ESInets, the originating network might
pass all types of emergency calls to an ESInet (all calls with a pass all types of emergency calls to an ESInet (all calls with a
service URN of or starting with "sos"). The ESInet then routs such service URN of or starting with "sos"). The ESInet then routs such
calls to an appropriate PSAP. In an environment without an ESInet, calls to an appropriate PSAP. In an environment without an ESInet,
the emergency services authorities and the originating carriers the emergency services authorities and the originating carriers
determine how such calls are routed. determine how such calls are routed.
9. New Metadata/Control Values 10. New Metadata/Control Values
This document adds new attribute values to the metadata/control This document adds new attribute values to the metadata/control
structure defined in [I-D.ietf-ecrit-ecall]. structure defined in [I-D.ietf-ecrit-ecall].
In addition to the base usage from the PSAP to the IVS to In addition to the base usage from the PSAP to the IVS to
acknowledge receipt of crash data, the <ack> element is also acknowledge receipt of crash data, the <ack> element is also
contained in a metadata/control block sent by the IVS to the PSAP. contained in a metadata/control block sent by the IVS to the PSAP.
This is used by the IVS to acknowledge receipt of a request by the This is used by the IVS to acknowledge receipt of a request by the
PSAP and indicate if the request was carried out when that request PSAP and indicate if the request was carried out when that request
would not otherwise be acknowledged (if the PSAP requests the would not otherwise be acknowledged (if the PSAP requests the
skipping to change at page 19, line 7 skipping to change at page 19, line 23
is transmitted from the PSAP to the IVS in a SIP INFO request within 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 the established dialog. The IVS sends the requested data (e.g., the
VEDS) or an acknowledgment (for requests other than to send data) in VEDS) or an acknowledgment (for requests other than to send data) in
a new INFO request. This mechanism flexibly allows the PSAP to send 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 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 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, or other data block, or to perform an action other than sending data,
the IVS sends the requested data or an acknowledgment regarding the the IVS sends the requested data or an acknowledgment regarding the
action in an INFO message within the dialog. action in an INFO message within the dialog.
9.1. New values for the 'action' attribute' 10.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 appropriate for the language of the vehicle's interface). A
registry is created in Section 15.4 for messages and their IDs. registry is created in Section 16.4 for messages and their IDs.
Vehicles include the highest registered message in their Vehicles include the highest registered message in their
<capabilities> element to indicate support for all messages up to <capabilities> element to indicate support for all messages up to
and including the 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 INVITE sent by the vehicle) to enable the PSAP call taker to view
a 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.
9.2. Request Example 10.2. Request Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<request action="send-data" datatype="VEDS"/> <request action="send-data" datatype="VEDS"/>
<request action="lamp" lamp-id="hazard" <request action="lamp" lamp-id="hazard"
lamp-action="flash" persistance="PT1H"/> lamp-action="flash" persistance="PT1H"/>
<request action="msg-static" msgid="1"/> <request action="msg-static" msgid="1"/>
<request action="msg-dynamic"> <request action="msg-dynamic">
<text>Remain calm. Help is on the way.</text> <text>Remain calm. Help is on the way.</text>
</request> </request>
</EmergencyCallData.control> </EmergencyCallData.control>
Figure 7: Request Example Figure 7: Request Example
9.3. The <ack> element 10.3. The <ack> element
In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the In [I-D.ietf-ecrit-ecall], the <ack> element is transmitted by the
PSAP to acknowledge the MSD. Here, the <ack> element is also PSAP to acknowledge the MSD. Here, the <ack> element is also
transmitted by the PSAP to acknowledge the VEDS data and by the IVS 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 acknowledge receipt of a <request> element that requested the IVS
to perform an action other than transmitting a data object (e.g., a 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 request to display a message would be acknowledged, but a request to
transmit VEDS data would not result in a separate <ack> element being transmit VEDS data would not result in a separate <ack> element being
sent, since the data object itself serves as acknowledgment.) An sent, since the data object itself serves as acknowledgment.) An
<ack> element sent by an IVS references the unique ID of the <ack> element sent by an IVS references the unique ID of the
metadata/control object containing the request(s) and indicates metadata/control object containing the request(s) and indicates
whether the request was successfully performed, and if not, whether the request was successfully performed, and if not,
optionally includes an explanation. optionally includes an explanation.
9.3.1. Ack Examples 10.3.1. Ack Examples
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData: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.control> </EmergencyCallData.control>
Figure 8: Ack Example from IVS to PSAP Figure 8: Ack Example from IVS to PSAP
9.4. The <capabilities> element 10.4. The <capabilities> element
The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by The <capabilities> element ([I-D.ietf-ecrit-ecall]) is transmitted by
the IVS to indicate its capabilities to the PSAP. the IVS to indicate its capabilities to the PSAP.
The <capabilities> element contains a <request> child element per The <capabilities> element contains a <request> child element per
action supported by the vehicle. The vehicle MUST support sending action supported by the vehicle. The vehicle MUST support sending
the VEDS data object and so includes at a minimum a <request> child the VEDS data object and so includes at a minimum a <request> child
element with the 'action' attribute set to "send-data" and the element with the 'action' attribute set to "send-data" and the
'supported-values' attribute containing all data blocks supported by 'supported-values' attribute containing all data blocks supported by
the IV, which MUST include 'VEDS'. All other actions are OPTIONAL. the IV, which MUST include 'VEDS'. All other actions are OPTIONAL.
If the "msg-static" action is supported, a <request> child element If the "msg-static" action is supported, a <request> child element
with the 'action' attribute set to "msg-static" is included, with the with the 'action' attribute set to "msg-static" is included, with the
'msgid' attribute set to the highest supported static message 'msgid' attribute set to the highest supported static message
supported by the vehicle. A registry is created in Section 15.4 to supported by the vehicle. A registry is created in Section 16.4 to
map 'msgid' values to static text messages. By sending the highest map 'msgid' values to static text messages. By sending the highest
supported static message number in its <capabilities> element, the supported static message number in its <capabilities> element, the
vehicle indicates its support for all static messages in the registry vehicle indicates its support for all static messages in the registry
up to and including that value. up to and including that value.
If the "lamp" action is supported, a <request> child element with the If the "lamp" action is supported, a <request> child element with the
'action' attribute set to "lamp" is included, with the 'supported- 'action' attribute set to "lamp" is included, with the 'supported-
values' attribute set to all supported lamp IDs. A registry is values' attribute set to all supported lamp IDs. A registry is
created in Section 15.5 to contain lamp ID values. created in Section 16.5 to contain lamp ID values.
If the "enable-camera" action is supported, a <request> child element If the "enable-camera" action is supported, a <request> child element
with the 'action' attribute set to "enable-camera" is included, with with the 'action' attribute set to "enable-camera" is included, with
the 'supported-values' attribute set to all supported camera IDs. A the 'supported-values' attribute set to all supported camera IDs. A
registry is created in Section 15.6 to contain camera ID values. registry is created in Section 16.6 to contain camera ID values.
9.4.1. Capabilities Example 10.4.1. Capabilities Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<EmergencyCallData.control <EmergencyCallData.control
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control" xmlns="urn:ietf:params:xml:ns:EmergencyCallData:control"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control"> xsi:schemaLocation="urn:ietf:params:xml:ns:EmergencyCallData:control">
<capabilities> <capabilities>
<request action="send-data" supported-values="VEDS"/> <request action="send-data" supported-values="VEDS"/>
<request action="lamp" <request action="lamp"
skipping to change at page 22, line 28 skipping to change at page 22, line 28
<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-values="backup; interior"/> <request action="enable-camera" supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.control> </EmergencyCallData.control>
Figure 9: Capabilities Example Figure 9: Capabilities Example
10. Test Calls 11. 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.
skipping to change at page 23, line 16 skipping to change at page 23, line 16
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).
11. The emergencyCallData.eCall.VEDS INFO package 12. The emergencyCallData.eCall.VEDS INFO package
This document registers the 'emergencyCallData.eCall.VEDS' INFO This document registers the 'emergencyCallData.eCall.VEDS' INFO
package. package.
Both endpoints (the IVS and the PSAP equipment) include Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO messages carrying data [RFC6086] to indicate ability to receive INFO messages carrying data
as described here. as described here.
Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates
the ability to receive NG-ACN related body parts as specified in the ability to receive NG-ACN related body parts as specified in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
An INFO request message carrying data related to an emergency call as An INFO request message carrying data related to an emergency call as
described in [TBD: THIS DOCUMENT] has an Info-Package header field described in [TBD: THIS DOCUMENT] has an Info-Package header field
set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. set to 'emergencyCallData.eCall.VEDS' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the The requirements of Section 10 of [RFC6086] are addressed in the
following sections. following sections.
11.1. Overall Description 12.1. Overall Description
This section describes "what type of information is carried in INFO This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package." applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.VEDS INFO INFO requests associated with the emergencyCallData.eCall.VEDS INFO
package carry data associated with emergency calls as defined in package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs. data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information. Refer to [TBD: THIS DOCUMENT] for more information.
11.2. Applicability 12.2. Applicability
This section describes "why the Info Package mechanism, rather than This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...." some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, per emergency call data blocks occurs within a SIP emergency dialog, per
Section 6, and is normally carried in the initial INVITE and its Section 7, and is normally carried in the initial INVITE and its
response; the use of INFO only occurs when emergency-call-related 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 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 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 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 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/ service, but the semantics are not a good fit, e.g., the subscribe/
notify mechanism provides one-way communication consisting of (often notify mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog. is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or 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 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) overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large. would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport. for mid-call data transport.
11.3. Info Package Name 12.3. Info Package Name
The info package name is emergencyCallData.eCall.VEDS The info package name is emergencyCallData.eCall.VEDS
11.4. Info Package Parameters 12.4. Info Package Parameters
None None
11.5. SIP Option-Tags 12.5. SIP Option-Tags
None None
11.6. INFO Request Body Parts 12.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.VEDS info package is a The body for an emergencyCallData.eCall.VEDS info package is a
multipart body. Zero or one application/ multipart body which MAY contain zero or one application/
emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part, emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part,
zero or more application/emergencyCallData.control+xml (containing a zero or more application/emergencyCallData.control+xml (containing a
metadata/control object) parts, and zero or one application/ metadata/control object) parts, and zero or one application/
emergencyCallData.eCall.MSD+per (containing an MSD) part are emergencyCallData.eCall.MSD+per (containing an MSD) part.
permitted. Intermediate multipart body parts MAY appear.
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in non-INFO messages, each with how these body parts are sent in non-INFO messages, each
associated body part is referenced by a Call-Info header field at the associated body part is referenced by a Call-Info header field at the
top level of the SIP message. The body part has a Content- top level of the SIP message. The body part has a Content-
Disposition header field set to "By-Reference". Disposition header field set to "By-Reference".
A VEDS or metadata/control block is always enclosed in a multipart
body part (even if it would otherwise be the only body part in the
SIP message), since as of the date of this document, the use of
Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field).
Service providers are not expected to attach [RFC7852] Additional Service providers are not expected to attach [RFC7852] Additional
Data to an INFO request. Data to an INFO request.
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
11.7. Info Package Usage Restrictions 12.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
11.8. Rate of INFO Requests 12.8. Rate of INFO Requests
The rate of SIP INFO requests associated with the The rate of SIP INFO requests associated with the
emergencyCallData.eCall.VEDS info package is normally quite low (most emergencyCallData.eCall.VEDS info package is normally quite low (most
dialogs are likely to contain zero INFO requests, while others can be dialogs are likely to contain zero INFO requests, while others can be
expected to carry an occasional request). expected to carry an occasional request).
11.9. Info Package Security Considerations 12.9. Info Package Security Considerations
The MIME content type registations for the data blocks that can be The MIME content type registations for the data blocks that can be
carried using this INFO package contains a discussion of the security carried using this INFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of "Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of [TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in vehicle-initiated emergency calls as described in the data carried in vehicle-initiated emergency calls as described in
that document. that document.
11.10. Implementation Details 12.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details. See [TBD: THIS DOCUMENT] for protocol details.
11.11. Examples 12.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples. See [TBD: THIS DOCUMENT] for protocol examples.
12. Example 13. 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 26, line 41 skipping to change at page 26, line 45
| | | |
| | | |
| | | |
| ESInet | | ESInet |
+---------------------------------------+ +---------------------------------------+
Figure 10: Example of Vehicle-Placed Emergency Call Message Flow Figure 10: Example of Vehicle-Placed Emergency Call Message Flow
The example, shown in Figure 11, illustrates a SIP emergency call The example, shown in Figure 11, illustrates a SIP emergency call
INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS
data block), and capabilities data (an eCall metadata/control block data block), and capabilities data (a metadata/control block with
with extensions defined in this document) attached to the SIP INVITE extensions defined in this document) attached to the SIP INVITE
message. The INVITE has a request URI containing the message. The INVITE has a request URI containing the
'urn:service:sos.ecall.automatic' service URN. 'urn:service:sos.ecall.automatic' service URN.
The example VEDS data structure shows information about about a The example VEDS data structure shows information about about a
crashed vehicle. The example communicates that the car is a model crashed vehicle. The example communicates that the car is a model
year 2015 Saab 9-5 (a car which does not exist). The front airbag year 2015 Saab 9-5 (a car which does not exist). The front airbag
deployed as a consequence of the crash. The deployed as a consequence of the crash. The
'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a
passenger car (the code is set to '101') and that it is not a passenger car (the code is set to '101') and that it is not a
convertible (the 'ConvertibleIndicator' value is set to 'false'). convertible (the 'ConvertibleIndicator' value is set to 'false').
skipping to change at page 31, line 15 skipping to change at page 31, line 20
<request action="enable-camera" <request action="enable-camera"
supported-values="backup; interior"/> supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.control> </EmergencyCallData.control>
--boundary1-- --boundary1--
Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call
13. Security Considerations 14. Security Considerations
Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852],
the security considerations described there and in [RFC5069] apply the security considerations described there and in [RFC5069] apply
here. Implementors are cautioned to read and understand the here. Implementors are 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
skipping to change at page 31, line 38 skipping to change at page 31, line 43
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").
14. Privacy Considerations 15. 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 [RFC7852], the data structures specified there, and the builds on [RFC7852], the data structures specified there, and the
corresponding privacy considerations discussed there, apply here as corresponding privacy considerations discussed there, apply here as
well. The VEDS data structure contains optional elements that can well. The VEDS data structure contains optional elements that can
carry identifying and personal information, both about the vehicle carry identifying and personal information, both about the vehicle
and about the owner, as well as location information, and so needs to and about the owner, as well as location information, and so needs to
be protected against unauthorized disclosure, as discussed in be protected against unauthorized disclosure, as discussed in
[RFC7852]. Local regulations may impose additional privacy [RFC7852]. Local regulations may impose additional privacy
protection requirements. protection requirements.
The additional functionality enabled by this document, such as access The additional functionality enabled by this document, such as access
to vehicle camera streams, carries a burden of protection and so to vehicle camera streams, carries a burden of protection and so
implementations need to be careful that access is only provided implementations need to be careful that access is only provided
within the context of an emergency call or to an emergency services within the context of an emergency call or to an emergency services
provider (e.g., by verifying that the request for camera access is provider (e.g., by verifying that the request for camera access is
signed by a certificate issued by an emergency services registrar). signed by a certificate issued by an emergency services registrar).
15. IANA Considerations 16. 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 sub-registries in the registry. This document adds to and creates sub-registries in the
'Metadata/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. This document registers a new INFO package.
15.1. MIME Content-type Registration for 'application/ 16.1. MIME Content-type Registration for 'application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml'
This specification requests the registration of a new MIME content This specification requests the registration of a new MIME content
type according to the procedures of RFC 4288 [RFC4288] and guidelines type according to the procedures of RFC 4288 [RFC4288] and guidelines
in 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
skipping to change at page 33, line 37 skipping to change at page 33, line 43
Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig,
Hannes.Tschofenig@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>
15.2. Registration of the 'VEDS' entry in the Emergency Call Additional 16.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 was document. The Emergency Call Additional Data registry was
established by [RFC7852]. established by [RFC7852].
15.3. New Action Values 16.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 "Action Registry" registry created by <request> element in the "Action Registry" registry created by
[I-D.ietf-ecrit-ecall]. [I-D.ietf-ecrit-ecall].
+---------------+-------------------------------------+ +---------------+--------------------------------------+
| Name | Description | | Name | Description |
+---------------+-------------------------------------+ +---------------+--------------------------------------+
| msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | | msg-static | Section 10.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | | msg-dynamic | Section 10.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| honk | Section 9.1 of [TBD: THIS DOCUMENT] | | honk | Section 10.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| lamp | Section 9.1 of [TBD: THIS DOCUMENT] | | lamp | Section 10.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | | enable-camera | Section 10.1 of [TBD: THIS DOCUMENT] |
+---------------+-------------------------------------+ +---------------+--------------------------------------+
Table 2: Action Registry New Values Table 2: Action Registry New Values
15.4. Static Message Registry 16.4. Static Message Registry
This document creates a new sub-registry called "Static Message This document creates a new sub-registry called "Static Message
Registry" in the "Metadata/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 implies 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
skipping to change at page 35, line 15 skipping to change at page 35, line 20
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| ID | Message | | ID | Message |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| 1 | Emergency authorities are aware of your incident and | | 1 | Emergency authorities are aware of your incident and |
| | location, but are unable to speak with you right now. We | | | location, but are unable to speak with you right now. We |
| | will help you as soon as possible. | | | will help you as soon as possible. |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
Table 3: Static Message Registry Table 3: Static Message Registry
15.5. Lamp ID Registry 16.5. Lamp ID Registry
This document creates a new sub-registry called "Lamp ID Registry" in This document creates a new sub-registry called "Lamp ID Registry" in
the "Metadata/Control Data" registry established by the "Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies
the names of automotive lamps (lights). As defined in [RFC5226], the names of automotive lamps (lights). As defined in [RFC5226],
this registry operates under "Expert Review" rules. The expert this registry operates under "Expert Review" rules. The expert
should determine that the proposed lamp name is clearly should determine that the proposed lamp name is clearly
understandable and is sufficiently distinguishable from other lamp understandable and is sufficiently distinguishable from other lamp
names. names.
skipping to change at page 36, line 33 skipping to change at page 36, line 33
| | | | | |
| 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 4: Lamp ID Registry Initial Values Table 4: Lamp ID Registry Initial Values
15.6. Camera ID Registry 16.6. Camera ID Registry
This document creates a new sub-registry called "Camera ID Registry" This document creates a new sub-registry called "Camera ID Registry"
in the "Metadata/Control Data" registry established by in the "Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies
automotive cameras. As defined in [RFC5226], this registry operates automotive cameras. As defined in [RFC5226], this registry operates
under "Expert Review" rules. The expert should determine that the under "Expert Review" rules. The expert should determine that the
proposed camera name is clearly understandable and is sufficiently proposed camera name is clearly understandable and is sufficiently
distinguishable from other camera names. distinguishable from other camera names.
The contents of this registry are: The contents of this registry are:
skipping to change at page 37, line 36 skipping to change at page 37, line 36
| | 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 5: Camera ID Registry Initial Values Table 5: Camera ID Registry Initial Values
16. Acknowledgements 17. Acknowledgements
We would like to thank Lena Chaponniere, Stephen Edge, and Christer We would like to thank Lena Chaponniere, Stephen Edge, and Christer
Holmberg for their review and suggestions; Robert Sparks and Paul Holmberg for their review and suggestions; Robert Sparks and Paul
Kyzivat for their help with the SIP mechanisms; Michael Montag, Kyzivat for their help with the SIP mechanisms; Michael Montag,
Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex
Buddenberg for their feedback; and Ulrich Dietz for his help with Buddenberg for their feedback; and Ulrich Dietz for his help with
earlier versions of the original version of this document. earlier versions of the original version of this document.
17. Changes from Previous Versions 18. Changes from Previous Versions
17.1. Changes from draft-ietf-13 to draft-ietf-14 18.1. Changes from draft-ietf-14 to draft-ietf-15
o Moved VEDS text from Introduction to new Vehicle Data section
o Various clarifications and simplifications
18.2. Changes from draft-ietf-13 to draft-ietf-14
o Body parts now always sent enclosed in multipart (even if only o Body parts now always sent enclosed in multipart (even if only
body part in SIP message) and hence always have a Content- body part in SIP message) and hence always have a Content-
Disposition of By-Reference Disposition of By-Reference
o Fixed typos. o Fixed typos.
17.2. Changes from draft-ietf-11 to draft-ietf-13 18.3. Changes from draft-ietf-11 to draft-ietf-13
o Fixed typos o Fixed typos
17.3. Changes from draft-ietf-10 to draft-ietf-11 18.4. Changes from draft-ietf-10 to draft-ietf-11
o Clarifications suggested by Christer o Clarifications suggested by Christer
o Corrections to Content-Disposition text and examples as suggested o Corrections to Content-Disposition text and examples as suggested
by Paul Kyzivat by Paul Kyzivat
o Clarifications to Content-Disposition text and examples to clarify o Clarifications to Content-Disposition text and examples to clarify
that handling=optional is only used in the initial INVITE that handling=optional is only used in the initial INVITE
17.4. Changes from draft-ietf-09 to draft-ietf-10 18.5. Changes from draft-ietf-09 to draft-ietf-10
o Fixed errors in examples found by Dale in eCall draft o Fixed errors in examples found by Dale in eCall draft
o Removed enclosing sub-section of INFO package registration section o Removed enclosing sub-section of INFO package registration section
o Added text per Christer and Dale's suggestions that the MSD and o Added text per Christer and Dale's suggestions that the MSD and
metadata/control blocks are sent in INFO with a Call-Info header metadata/control blocks are sent in INFO with a Call-Info header
field referencing them field referencing them
o Other text changes per comments received from Christer and Ivo o Other text changes per comments received from Christer and Ivo
against eCall draft. against eCall draft.
17.5. Changes from draft-ietf-08 to draft-ietf-09 18.6. Changes from draft-ietf-08 to draft-ietf-09
o Added INFO package registration for eCall.VEDS o Added INFO package registration for eCall.VEDS
o Moved <capabilities> element and other extension points back to o Moved <capabilities> element and other extension points back to
eCall document so that extension points are in base spec (and also eCall document so that extension points are in base spec (and also
to get XML schema to compile) to get XML schema to compile)
o Text changes for clarification. o Text changes for clarification.
17.6. Changes from draft-ietf-07 to draft-ietf-08 18.7. 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"
17.7. Changes from draft-ietf-06 to draft-ietf-07 18.8. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes o Minor editorial changes
17.8. Changes from draft-ietf-05 to draft-ietf-06 18.9. 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.
17.9. Changes from draft-ietf-04 to draft-ietf-05 18.10. 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
17.10. Changes from draft-ietf-03 to draft-ietf-04 18.11. 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
17.11. Changes from draft-ietf-02 to draft-ietf-03 18.12. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
17.12. Changes from draft-ietf-01 to draft-ietf-02 18.13. 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
17.13. Changes from draft-ietf-00 to draft-ietf-01 18.14. 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
17.14. Changes from draft-gellens-02 to draft-ietf-00 18.15. 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
17.15. Changes from draft-gellens-01 to -02 18.16. 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
[RFC7852] [RFC7852]
17.16. Changes from draft-gellens-00 to -01 18.17. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
18. References 19. References
18.1. Normative References 19.1. Normative References
[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-13 (work in European eCall", draft-ietf-ecrit-ecall-13 (work in
progress), September 2016. progress), September 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>.
skipping to change at page 41, line 38 skipping to change at page 41, line 48
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, Call", RFC 7852, DOI 10.17487/RFC7852, July 2016,
<http://www.rfc-editor.org/info/rfc7852>. <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>.
18.2. Informative references 19.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,
 End of changes. 90 change blocks. 
240 lines changed or deleted 264 lines changed or added

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