< draft-ietf-ecrit-car-crash-19.txt   draft-ietf-ecrit-car-crash-20.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: May 18, 2017 NeuStar, Inc. Expires: June 18, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
November 14, 2016 December 15, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-19.txt draft-ietf-ecrit-car-crash-20.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 media type and Emergency Call This document also registers a MIME media 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) and an INFO package to enable carrying this and necessarily a crash) and a SIP INFO package to enable carrying this
related data in INFO requests. An external specification for the and related data in SIP INFO requests. An external specification for
data format, contents, and structure are referenced in this document. 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 metadata/control object to permit greater attribute values to the metadata/control object to permit greater
functionality. This document registers a new INFO package (identical functionality. This document registers a new SIP INFO package
to that registered for eCall but with the addition of the VEDS MIME (identical to that registered for eCall but with the addition of the
type). This document also describes legacy (circuit-switched) ACN VEDS MIME type). This document also describes legacy (circuit-
systems and their migration to next-generation emergency calling, to switched) ACN systems and their migration to next-generation
provide background information and context. emergency calling, to provide background information and context.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 18, 2017. This Internet-Draft will expire on June 18, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7
4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9
6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 13 6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 14 7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13
8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 17 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 16
10. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 9.1. New values for the 'action' attribute' . . . . . . . . . 17
10.1. New values for the 'action' attribute' . . . . . . . . . 19 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 18
10.2. Request Example . . . . . . . . . . . . . . . . . . . . 19 9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 19
10.3. The <ack> element . . . . . . . . . . . . . . . . . . . 20 9.4. The <capabilities> element . . . . . . . . . . . . . . . 20
10.4. The <capabilities> element . . . . . . . . . . . . . . . 20 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21
11. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21 12. Security Considerations . . . . . . . . . . . . . . . . . . . 27
12. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 22 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 28
12.1. Overall Description . . . . . . . . . . . . . . . . . . 23 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28
12.2. Applicability . . . . . . . . . . . . . . . . . . . . . 23 14.1. MIME Media Type Registration for
12.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 28
12.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 14.2. Registration of the 'VEDS' entry in the Emergency Call
12.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 Data Types registry . . . . . . . . . . . . . . . . . . 30
12.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24 14.3. New Action Values . . . . . . . . . . . . . . . . . . . 30
12.7. Info Package Usage Restrictions . . . . . . . . . . . . 24 14.4. Emergency Call Static Message Registry . . . . . . . . . 30
12.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 14.5. Emergency Call Vehicle Lamp ID Registry . . . . . . . . 31
12.9. Info Package Security Considerations . . . . . . . . . . 25 14.6. Lamp State Registry . . . . . . . . . . . . . . . . . . 32
12.10. Implementation Details . . . . . . . . . . . . . . . . . 25 14.7. Emergency Call Vehicle Camera ID Registry . . . . . . . 33
12.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 25 14.8. The emergencyCallData.eCall.VEDS SIP INFO package . . . 34
13. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
14. Security Considerations . . . . . . . . . . . . . . . . . . . 31 16. Changes from Previous Versions . . . . . . . . . . . . . . . 37
15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 16.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 37
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 16.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38
16.1. MIME Media Type Registration for 16.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 16.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38
16.2. Registration of the 'VEDS' entry in the Emergency Call 16.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38
Additional Data registry . . . . . . . . . . . . . . . . 33 16.6. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38
16.3. New Action Values . . . . . . . . . . . . . . . . . . . 33 16.7. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38
16.4. Emergency Call Static Message Registry . . . . . . . . . 34 16.8. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38
16.5. Emergency Call Vehicle Lamp ID Registry . . . . . . . . 35 16.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39
16.6. Emergency Call Vehicle Camera ID Registry . . . . . . . 36 16.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39
17. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 16.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39
18. Changes from Previous Versions . . . . . . . . . . . . . . . 37 16.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39
18.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 37 16.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
18.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38 16.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
18.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38 16.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
18.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 16.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40
18.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38 16.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40
18.6. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38 16.18. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 40
18.7. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38 16.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40
18.8. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 16.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
18.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
18.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 17.1. Normative References . . . . . . . . . . . . . . . . . . 40
18.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39 17.2. Informative references . . . . . . . . . . . . . . . . . 41
18.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39
18.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39
18.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39
18.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39
18.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40
18.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40
18.18. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 40
18.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40
18.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40
19. References . . . . . . . . . . . . . . . . . . . . . . . . . 40
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 4, line 34 skipping to change at page 4, line 23
| APCO | Association of Public-Safety Communications Officials | | APCO | Association of Public-Safety Communications Officials |
| EENA | European Emergency Number Association | | EENA | European Emergency Number Association |
| ESInet | Emergency Services IP network | | ESInet | Emergency Services IP network |
| GNSS | Global Navigation Satellite System (which includes | | GNSS | Global Navigation Satellite System (which includes |
| | various systems such as the Global Positioning System or | | | various systems such as the Global Positioning System or |
| | GPS) | | | GPS) |
| IVS | In-Vehicle System | | IVS | In-Vehicle System |
| MNO | Mobile Network Operator | | MNO | Mobile Network Operator |
| MSD | eCall Minimum Set of Data | | MSD | eCall Minimum Set of Data |
| NENA | National Emergency Number Association | | NENA | National Emergency Number Association |
| NG | Next-Generation |
| POTS | Plain Old Telephone Service (normal, circuit-switched | | POTS | Plain Old Telephone Service (normal, circuit-switched |
| | voice calls) | | | voice calls) |
| PSAP | Public Safety Answering Point | | PSAP | Public Safety Answering Point |
| TSP | Telematics Service Provider | | TSP | Telematics Service Provider |
| VEDS | Vehicle Emergency Data Set | | VEDS | Vehicle Emergency Data Set |
+--------+----------------------------------------------------------+ +--------+----------------------------------------------------------+
Because the endpoints of an NG-ACN call are a PSAP and an IVS or TSP, Because the endpoints of a Next-Generation ACN call are a PSAP and an
to avoid receptively writing "IVS or TSP", the term "IVS" is used to IVS or TSP, to avoid receptively writing "IVS or TSP", the term "IVS"
represent either an IVS or TSP when discussing signaling behavior is used to represent either an IVS or TSP when discussing signaling
(e.g., attaching VEDS data, sending an INVITE request, receiving an behavior (e.g., sending VEDS data, sending a SIP INVITE request,
INFO request, etc.). receiving a SIP INFO request, etc.).
2. Introduction 2. Introduction
Emergency calls made by in-vehicle systems (e.g., automatically in Emergency calls made by in-vehicle systems (e.g., automatically in
the event of a crash or serious incident or manually by a vehicle the event of a crash or serious incident or manually by a vehicle
occupant) assist in significantly reducing road deaths and injuries occupant) assist in significantly reducing road deaths and injuries
by allowing emergency services to respond quickly and appropriately by allowing emergency services to respond quickly and appropriately
to the specifics of the incident, often with better location to the specifics of the incident, often with better location
accuracy. accuracy.
skipping to change at page 6, line 8 skipping to change at page 5, line 43
on either a human advisor or an automated text-to-speech system to on either a human advisor or an automated text-to-speech system to
provide the PSAP call taker with some crash data orally, or in some provide the PSAP call taker with some crash data orally, or in some
cases via a proprietary mechanism). In most cases, the PSAP call cases via a proprietary mechanism). In most cases, the PSAP call
taker needs to first realize that the call is related to a vehicle taker needs to first realize that the call is related to a vehicle
incident, and then listen to the data and transcribe it. Circuit- incident, and then listen to the data and transcribe it. Circuit-
switched ACN systems are referred to here as CS-ACN. switched ACN systems are referred to here as CS-ACN.
The transition to next-generation calling in general, and for The transition to next-generation calling in general, and for
emergency calling in particular, provides an opportunity to vastly emergency calling in particular, provides an opportunity to vastly
improve the scope, breadth, reliability and usefulness of crash data improve the scope, breadth, reliability and usefulness of crash data
during an emergency by allowing it to be transmitted during call set- during an emergency by allowing a standardized set to be transmitted
up, and to be automatically processed by the PSAP and made available during call set-up; to be automatically processed by the PSAP and
to the call taker in an integrated, automated way, as well as provide made available to the call taker in an integrated, automated way; as
the ability for a PSAP call taker to request that a vehicle take well as provide the ability for a PSAP call taker to request that a
certain actions, such as flashing lights or unlocking doors. In vehicle take certain actions, such as flashing lights or unlocking
addition, vehicle manufacturers are provided an opportunity to take doors. In addition, vehicle manufacturers are provided an
advantage of the same standardized mechanisms for data transmission opportunity to take advantage of the same standardized mechanisms for
and request processing for internal use if they wish (such as data transmission and request processing for internal use if they
telemetry between the vehicle and a service center for both emergency wish (such as telemetry between the vehicle and a service center for
and non-emergency uses, including location-based services, multi- both emergency and non-emergency uses, including location-based
media entertainment systems, remote door unlocking, and road-side services, multi-media entertainment systems, remote door unlocking,
assistance applications). remote diagnostics, and road-side assistance applications).
Next-generation ACN provides an opportunity for such calls to be Next-generation ACN provides an opportunity for such calls to be
recognized and processed as such during call set-up, and routed to an recognized and processed as such during call set-up, and routed to an
equipped PSAP where the vehicle data is available to assist the call equipped PSAP where the vehicle data is available to assist the call
taker in assessing and responding to the situation. Next-generation taker in assessing and responding to the situation. Next-generation
(IP-based) ACN systems are referred to here as NG-ACN. (IP-based) ACN systems are referred to here as NG-ACN.
An ACN call can be initiated by a vehicle occupant or automatically An ACN call can be initiated by a vehicle occupant or automatically
initiated by vehicle systems in the event of a serious incident. initiated by vehicle systems in the event of a serious incident.
(The "A" in "ACN" does stand for "Automatic," but the term is broadly (The "A" in "ACN" does stand for "Automatic," but the term is broadly
used to refer to the class of calls that are placed by an in-vehicle used to refer to the class of calls that are placed by an in-vehicle
system (IVS) or Telematics Service Providers (TSP) and that carry system (IVS) or Telematics Service Providers (TSP) and that carry
incident-related data as well as voice.) Automatically triggered incident-related data as well as voice.) Automatically triggered
calls indicate a car crash or some other serious incident (e.g., a calls indicate a car crash or some other serious incident (e.g., a
fire). Manually triggered calls are often reports of observed fire). Manually triggered calls include reports of observed crashes
crashes or serious hazards (such as impaired drivers or roadway or serious hazards (such as impaired drivers or roadway debris).
debris). In some implementations, manually triggered calls might be
more likely to be accidental.
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.
This document describes how the IETF mechanisms for IP-based This document describes how the IETF mechanisms for IP-based
emergency calls are used to provide the realization of next- emergency calls are used to provide the realization of next-
generation ACN. generation ACN. Although this specification is designed with the
requirements for North America ACN in mind (and both APCO and NENA
are based in the U.S.), it is specified generically such that the
technology can be re-used or extended to suit requirements in other
regions.
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), as described in calls by in-vehicle systems within Europe), as described in
[I-D.ietf-ecrit-ecall]. However, this document specifies a different [I-D.ietf-ecrit-ecall]. However, this document specifies a different
set of vehicle (crash) data, specifically, the Vehicle Emergency Data set of vehicle (crash) data, specifically, the Vehicle Emergency Data
Set (VEDS) rather than the eCall Minimum Set of Data (MSD). This Set (VEDS) rather than the eCall Minimum Set of Data (MSD). This
document is an extension of [I-D.ietf-ecrit-ecall], with the document is an extension of [I-D.ietf-ecrit-ecall], with the
differences being that this document makes the MSD data set optional differences being that this document makes the MSD data set optional
and VEDS mandatory, and adds new attribute values to the metadata/ and VEDS mandatory, and adds new attribute values to the metadata/
control object defined in that document. This document also control object defined in that document. This document also
registers a new INFO package (identical to that defined in registers a new SIP INFO package (identical to that defined in
[I-D.ietf-ecrit-ecall] with the addition of the VEDS MIME type). [I-D.ietf-ecrit-ecall] with the addition of the VEDS MIME type).
This document registers the 'application/EmergencyCallData.VEDS+xml' This document registers the 'application/EmergencyCallData.VEDS+xml'
MIME media type, registers the 'VEDS' entry in the Emergency Call MIME media type, registers the 'VEDS' entry in the Emergency Call
Additional Data registry, and registers an INFO package to enable Data Types registry, and registers a SIP INFO package to enable
carrying this and related data in INFO requests. carrying this and related data in SIP INFO requests.
Section 6 introduces VEDS. Section 7 describes how VEDS data and Section 6 introduces VEDS. Section 7 describes how VEDS data and
metadata/control blocks are transported within NG-ACN calls. metadata/control blocks are transported within NG-ACN calls.
Section 8 describes how such calls are placed. Section 8 describes how such calls are placed.
These mechanisms are 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 substituting 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
(often in cooperation with the originating device) and the location (often in cooperation with the originating device) and the location
as determined by the IVS. as determined by the IVS.
This specification inherits the ability to utilize test call This specification inherits the ability to utilize test call
functionality from Section 15 of [RFC6881]. functionality from Section 15 of [RFC6881].
3. Document Scope 3. Document Scope
This document is focused on how an ACN emergency call is setup and This document is focused on how an ACN emergency call is setup and
incident-related data (including vehicle, sensor, and location data) incident-related data (including vehicle, sensor, and location data)
is transmitted to the PSAP using IETF specifications. For the direct is transmitted to the PSAP using IETF specifications. For the direct
model, this is the end-to-end description (between the vehicle and model, this is the end-to-end description (between the vehicle and
the PSAP). For the TSP model, this describes the call leg between the PSAP). For the TSP model, this describes the call leg between
the TSP and the PSAP, leaving the call leg between the vehicle and the TSP and the PSAP, leaving the call leg between the vehicle and
the TSP up to the entities involved (i.e., IVS and TSP vendors) who the TSP up to the entities involved (i.e., IVS and TSP vendors) who
are then free to use the same mechanism as for the right-hand side or are then free to use the same mechanism as for the other leg 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 estimate country in which it is located (e.g., from a GNSS location estimate
and/or identity of or information from an MNO). If other regions and/or identity of or information from an MNO). If other regions
skipping to change at page 8, line 25 skipping to change at page 8, line 13
support those as well. This document adopts the call set-up and support those as well. This document adopts the call set-up and
other technical aspects of [I-D.ietf-ecrit-ecall], which uses other technical aspects of [I-D.ietf-ecrit-ecall], which uses
[RFC7852]; this makes it straightforward to use a different data set [RFC7852]; this makes it straightforward to use a different data set
while keeping other technical aspects unchanged. Hence, both NG- while keeping other technical aspects unchanged. Hence, both NG-
eCall and the NG-ACN mechanism described here are compatible, eCall and the NG-ACN mechanism described here are compatible,
differing primarily in the specific data block that is sent (the differing primarily in the specific data block that is sent (the
eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in
this document), and some additions to the metadata/control data this document), and some additions to the metadata/control data
block. If other regions adopt their own vehicle data sets, this can block. If other regions adopt their own vehicle data sets, this can
be similarly accomodated without changing other technical aspects. be similarly accomodated without changing other technical aspects.
Note that any additional data formats require a new INFO package to Note that any additional data formats require a new SIP INFO package
permit transport within INFO requests. to permit transport within SIP 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 10, line 9 skipping to change at page 9, line 40
///----\\\ 911/etc voice call via IVS +------+ ///----\\\ 911/etc voice call via IVS +------+
||| IVS |||---------------------------------------->+ PSAP | ||| IVS |||---------------------------------------->+ PSAP |
\\\----/// location via text-to-speech +------+ \\\----/// location via text-to-speech +------+
Figure 3: Legacy Direct Model Figure 3: Legacy Direct Model
5. Migration to Next-Generation 5. Migration to Next-Generation
Migration of emergency calls placed by in-vehicle systems to next- Migration of emergency calls placed by in-vehicle systems to next-
generation (all-IP) technology per this document provides a generation (all-IP) technology per this document provides a
standardized mechanism to identify such calls and to present crash standardized mechanism to identify such calls and to convey crash
data with the call, as well as enabling additional communications data with the call setup, as well as enabling additional
modalities and enhanced functionality. This allows ACN calls and communications modalities and enhanced functionality. This allows
crash data to be automatically processed by the PSAP and made ACN calls and crash data to be automatically processed by the PSAP
available to the call taker in an integrated, automated way. Because and made available to the call taker in an integrated, automated way.
the crash data is carried in the initial SIP INVITE (per [RFC7852]) Because the crash data is carried in the initial SIP INVITE (per
the PSAP can present it to the call taker simultaneously with the [RFC7852]) the PSAP can present it to the call taker simultaneously
appearance of the call. The PSAP can also process the data to take with the appearance of the call. The PSAP can also process the data
other actions (e.g., if multiple calls from the same location arrive to take other actions (e.g., if multiple calls from the same location
when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP arrive when the PSAP is busy and a subset of them are NG-ACN calls, a
might choose to store the information and reject the calls, since the PSAP might choose to store the information and reject the calls,
IVS will receive confirmation that the information has been since the IVS will receive confirmation that the information has been
successfully received; a PSAP could also choose to include a message successfully received; a PSAP could also choose to include a message
stating that it is aware of the incident and responders are on the stating that it is aware of the incident and responders are on the
way; a PSAP could call the vehicle back when a call taker is way; a PSAP could call the vehicle back when a call taker is
available). available).
Origination devices and networks, PSAPs, emergency services networks, The migration of origination devices and networks, PSAPs, emergency
and other telephony environments are migrating to next-generation. services networks, and other telephony environments to next-
This provides opportunities for significant enhancement to generation provides enhanced interoperability and functionality,
interoperability and functionality, especially for emergency calls especially for emergency calls carrying additional data such as
carrying additional data such as vehicle crash data. (In the U.S., a vehicle crash data. (In the U.S., a network specifically for
network specifically for emergency responders is being developed. emergency responders is being developed. This network, FirstNet,
This network, FirstNet, will be next-generation from the start, will be next-generation from the start, enhancing the ability for
enhancing the ability for data exchange between PSAPs and data exchange between PSAPs and responders.)
responders.)
Migration to next-generation (NG) provides an opportunity to NG-ACN calls can be recognized as originating from a vehicle, routed
significantly improve the handling and response to vehicle-initiated to a PSAP prepared both technically and operationally to handle such
emergency calls. Such calls can be recognized as originating from a calls, and the vehicle-determined location and crash data made
vehicle, routed to a PSAP equipped both technically and operationally available to the call taker simultaneously with the call appearance.
to handle such calls, and the vehicle-determined location and crash The PSAP can take advantage of enhanced functionality, including the
data can be made available to the call taker simultaneously with the ability to request the vehicle to take an action, such as sending an
call appearance. The PSAP can take advantage of enhanced updated set of data, converying a message to the occupants, flashing
functionality, including the ability to request the vehicle to take lights, unlocking doors, etc.
an action, such as sending an updated set of data, converying a
message to the occupants, flashing lights, unlocking doors, etc.
Vehicle manufacturers using the TSP model can choose to take Vehicle manufacturers using the TSP model can choose to take
advantage of the same mechanism to carry telematics data and requests advantage of the same mechanism to carry telematics data and requests
and responses between the vehicle and the TSP for both emergency and and responses between the vehicle and the TSP for both emergency and
non-emergency calls as are used for the interface with the PSAP. non-emergency calls as are used for the interface with the PSAP.
A next-generation IVS establishes an emergency call using the A next-generation IVS establishes a next-generation emergency call
emergency call solution as described in [RFC6443] and [RFC6881], with (see [RFC6443] and [RFC6881]), with an initial INVITE containing a
the difference that the Request-URI indicates an ACN type of Request-URI indicating an ACN type of emergency call and Call-Info
emergency call, the IVS typically does not perform routing or header fields indicating that both vehicle crash and capabilities
location queries but relies on the carrier for this, and uses Call- data are included; the IVS typically does not perform routing or
Info header fields to indicates that vehicle crash and capabilities location queries but relies on the carrier for this.
data is attached. When an ESInet is deployed, the MNO only needs to
recognize the call as an emergency call and route it to an ESInet.
The ESInet can recognize the call as an ACN with vehicle data and can
route the call to an NG-ACN capable PSAP. Such a PSAP can interpret
the vehicle data sent with the call and make it available to the call
taker.
[I-D.ietf-ecrit-ecall] registers new service URN children within the [I-D.ietf-ecrit-ecall] registers new service URN children within the
"sos" subservice. These URNs request NG-ACN resources, and "sos" subservice. These URNs request NG-ACN resources, and
differentiate between manually and automatically triggered NG-ACN differentiate between manually and automatically triggered NG-ACN
calls (which might be subject to different treatment depending on calls (which might be subject to different treatment depending on
policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] policy). The two service URNs registered in [I-D.ietf-ecrit-ecall]
are "urn:service:sos.ecall.automatic" and are "urn:service:sos.ecall.automatic" and
"urn:service:sos.ecall.manual". The same service URNs are used for "urn:service:sos.ecall.manual". The same service URNs are used for
ACN as for eCall since in any region only one of these is supported, ACN as for eCall since in any region only one of these is supported,
making a distinction unnecessary. (Further, PSAP equipment might making a distinction unnecessary. (Further, PSAP equipment might
skipping to change at page 11, line 29 skipping to change at page 11, line 4
"sos" subservice. These URNs request NG-ACN resources, and "sos" subservice. These URNs request NG-ACN resources, and
differentiate between manually and automatically triggered NG-ACN differentiate between manually and automatically triggered NG-ACN
calls (which might be subject to different treatment depending on calls (which might be subject to different treatment depending on
policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] policy). The two service URNs registered in [I-D.ietf-ecrit-ecall]
are "urn:service:sos.ecall.automatic" and are "urn:service:sos.ecall.automatic" and
"urn:service:sos.ecall.manual". The same service URNs are used for "urn:service:sos.ecall.manual". The same service URNs are used for
ACN as for eCall since in any region only one of these is supported, ACN as for eCall since in any region only one of these is supported,
making a distinction unnecessary. (Further, PSAP equipment might making a distinction unnecessary. (Further, PSAP equipment might
support multiple data formats, allowing a PSAP to handle a vehicle support multiple data formats, allowing a PSAP to handle a vehicle
that erroneously sent the wrong data object.) that erroneously sent the wrong data object.)
Note that in North America, routing queries performed by clients Note that in North America, routing queries performed by clients
outside of an ESInet typically treat all sub-services of "sos" outside of an ESInet typically treat all sub-services of "sos"
identically to "sos" with no sub-service. However, the Request-URI identically to "sos" with no sub-service. However, the Request-URI
header field retains the full sub-service; route and handling header field retains the full sub-service; route and handling
decisions within an ESInet or PSAP can take the sub-service into decisions within an ESInet or PSAP can take the sub-service into
account. For example, in a region with multiple cooperating PSAPs, account. For example, in a region with multiple cooperating PSAPs,
an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or
one that specializes in vehicle-related incidents. one that specializes in vehicle-related incidents.
Migration of the three architectural models to next-generation (all- Migration of the three architectural models to next-generation (all-
IP) is described below. IP) is described below.
In the TSP model, the IVS transmits crash and location data to the In the TSP model, the IVS transmits crash and location data to the
TSP either by re-using the mechanisms and data objects described TSP either by re-using the mechanisms and data objects described in
here, or using a proprietary mechanism. In an emergency, the TSP this document, or using a proprietary mechanism. In an emergency,
bridges in the PSAP and the TSP transmits crash and other data to the the TSP bridges in the PSAP and the TSP transmits crash and other
PSAP using the mechanisms and data objects described here. There is data to the PSAP using the mechanisms and data objects described in
a three-way call between the vehicle, the TSP, and the PSAP, allowing this document. There is a three-way call between the vehicle, the
communication between the PSAP call taker, the TSP call taker, and TSP, and the PSAP, allowing communication between the PSAP call
the vehicle occupants (who might be unconscious). The TSP relays taker, the TSP call taker, and the vehicle occupants (who might be
PSAP requests and vehicle responses. unconscious). The TSP relays PSAP requests and vehicle responses.
proprietary proprietary
///----\\\ or standard +------+ standard +------+ ///----\\\ or standard +------+ standard +------+
||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP |
\\\----/// crash + other data +------+ crash + other data +------+ \\\----/// crash + other data +------+ crash + other data +------+
Figure 4: Next-Generation TSP Model Figure 4: Next-Generation TSP Model
The vehicle manufacturer and the TSP can choose to use the same The vehicle manufacturer and the TSP can choose to use the same
mechanisms and data objects on the left call leg in Figure 4 as on mechanisms and data objects on the left call leg in Figure 4 as on
the right. (Note that the TSP model can be more difficult when the the right. (Note that the TSP model can be more difficult when the
vehicle is in a different country than the TSP (e.g., a US resident vehicle is in a different country than the TSP (e.g., a US resident
driving in Canada or Mexico) because of the additional complexity in driving in Canada) because of the additional complexity in choosing
choosing the correct PSAP based on vehicle location performed by a the correct PSAP based on vehicle location performed by a TSP in a
TSP in a different country.) different country.)
In the direct model, the IVS communicates crash data to the PSAP In the direct model, the IVS communicates crash data to the PSAP
directly using the mechanisms and data objects described here. directly using the mechanisms and data objects described in this
document.
///----\\\ NG emergency call +------+ ///----\\\ NG emergency call +------+
||| IVS |||----------------------------------------->+ PSAP | ||| IVS |||----------------------------------------->+ PSAP |
\\\----/// crash + other data +------+ \\\----/// crash + other data +------+
Figure 5: Next-Generation Direct Model Figure 5: Next-Generation Direct Model
In the paired model, the IVS uses a Bluetooth link to a previously- In the paired model, the IVS uses a Bluetooth link to a previously-
paired handset to establish an emergency call with the PSAP; it is paired handset to establish an emergency call with the PSAP; it is
undefined what facilities are or will be available for transmitting unclear what facilities are or will be available for transmitting
crash data through the Bluetooth link to the handset for inclusion in crash data through the Bluetooth link to the handset for inclusion in
an NG emergency call. Hence, manufacturers that use the paired model an NG emergency call. Hence, manufacturers that use the paired model
for legacy calls might choose to adopt either the direct or TSP for legacy calls might choose to adopt either the direct or TSP
models for next-generation calls. models for next-generation calls.
+---+ +---+
///----\\\ (undefined) | H | standard +------+ ///----\\\ (undefined) | H | standard +------+
||| IVS |||------------------>| S +------------------->+ PSAP | ||| IVS |||------------------>| S +------------------->+ PSAP |
\\\----/// (undefined) +---+ crash + other data +------+ \\\----/// (undefined) +---+ crash + other data +------+
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.g., 200 OK) lacks a metadata/control structure
receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or
proceeds as it would for a CS-ACN call (e.g., verbal conveyance of TSP then proceeds as it would for a CS-ACN call (e.g., verbal
data) conveyance of data)
6. Vehicle Data 6. Vehicle Data
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.
skipping to change at page 13, line 47 skipping to change at page 13, line 21
o A set of data is standardized by an SDO or appropriate o A set of data is standardized by an SDO or appropriate
organization organization
o A MIME media type for the crash data set is registered with IANA o A MIME media type for the crash data set is registered with IANA
* If the data is specifically for use in emergency calling, the * If the data is specifically for use in emergency calling, the
MIME media type is normally under the 'application' type with a MIME media type is normally under the 'application' type with a
subtype starting with 'EmergencyCallData.' subtype starting with 'EmergencyCallData.'
* If the data format is XML, then by convention the name has a * If the data format is XML, then by convention the name has a
suffix of '+xml' suffix of '+xml'
o The item is registered in the Emergency Call Additional Data o The item is registered in the Emergency Call Data Types registry,
registry, as defined in Section 9.1.7 of [RFC7852] as defined in Section 11.1.9 of [RFC7852]
* For emergency-call-specific formats, the registered name is the * For emergency-call-specific formats, the registered name is the
root of the MIME media type (not including the root of the MIME media 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 SIP INFO package is registered that permits carrying the the
media type, the metadata/control object (defined in new media 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 SIP INFO requests.
7. Data Transport 7. Data Transport
[RFC7852] establishes a general mechanism for attaching blocks of [RFC7852] establishes a general mechanism for including blocks of
data to a SIP emergency call. This mechanism permits certain data within a SIP emergency call. This document makes use of that
emergency call MIME types to be attached to SIP messages. This mechanism. This document also registers a SIP INFO package (in
document makes use of that mechanism. This document also registers Section 14.8) to enable NG-ACN related data blocks to be carried in
an INFO package (in Section 12) to enable NG-ACN related data blocks SIP INFO requests (per [RFC6086], new SIP INFO method usages require
to be carried in SIP INFO requests (per [RFC6086], new INFO usages the definition of a SIP INFO package).
require the definition of an INFO package).
The Vehicle Emergency Data Set (VEDS) is an XML structure defined by
the Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) [VEDS]. It is
carried in a body part with MIME media type 'application/
EmergencyCallData.VEDS+xml'.
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 including it as a body part of a SIP message per [RFC7852]. The
The body part is identified by its MIME media type ('application/ body part is identified by its MIME media 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 Types 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 12. request by using the SIP INFO package defined in Section 14.8.
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 including it in 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
media type ('application/emergencyCallData.control+xml') in the media 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 Types
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 12. a SIP INFO request by using the SIP INFO package defined in
Section 14.8.
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 (even if it would 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 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 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). 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/
control object acknowledging receipt of the VEDS data and includes it control object acknowledging receipt of the VEDS data and includes it
in the SIP final response to the INVITE. The metadata/control object in the SIP final response to the INVITE. The metadata/control object
is not attached to provisional (e.g., 180) responses. is not included in provisional (e.g., 180) responses.
If the IVS receives an acknowledgment for a VEDS data object with If the IVS receives an acknowledgment for a VEDS data object with
received=false, this indicates that the PSAP was unable to properly received=false, this indicates that the PSAP was unable to properly
decode or process the VEDS. The IVS action is not defined (e.g., it decode or process the VEDS. The IVS action is not defined (e.g., it
might only log an error). Since the PSAP is able to request an might only log an error). Since the PSAP is able to request an
updated VEDS during the call, if an initial VEDS is unsatisfactory in updated VEDS during the call, if an initial VEDS is unsatisfactory in
any way, the PSAP can choose to request another one. any way, the PSAP can choose to request another one.
A PSAP can request that the vehicle send an updated 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 includes it as a body part of a SIP INFO
it within the dialog. The IVS then attaches an updated VEDS data request sent within the dialog. The IVS then includes an updated
object to a SIP INFO request and sends it within the dialog. If the VEDS data object as a body part of a SIP INFO request and sends it
IVS is unable to send the VEDS, it instead sends a metadata/control within the dialog. If the IVS is unable to send the VEDS, it instead
object acknowledging the request with the 'success' parameter set to sends a metadata/control object acknowledging the request with the
'false' and a 'reason' parameter (and optionally a 'details' 'success' parameter set to 'false' and a 'reason' parameter (and
parameter) indicating why the request cannot be accomplished. Per optionally a 'details' parameter) indicating why the request cannot
[RFC6086], metadata/control objects and VEDS data are sent using the be accomplished. Per [RFC6086], metadata/control objects and VEDS
INFO package defined in Section 12. In addition, to align with the data are sent using the SIP INFO package defined in Section 14.8. In
way a VEDS or metadata/control block is transmitted in a SIP message addition, to align with the way a VEDS or metadata/control block is
other than an INFO request, one or more Call-Info header fields are transmitted in a SIP message other than a SIP INFO request, one or
included in the SIP INFO request to reference the VEDS or metadata/ more Call-Info header fields are included in the SIP INFO request
control block. See Section 12 for more information on the use of referencing the VEDS or metadata/control block. See Section 14.8 for
INFO requests within NG-ACN calls. more information on the use of SIP 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, including MAY send an unsolicited VEDS in any convenient SIP message, including
an INFO request during the call. The PSAP sends an acknowledgment a SIP INFO request during the call. The PSAP sends an acknowledgment
for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS
in an INFO request, the acknowledgment is sent in a new INFO request, in a SIP INFO request, the acknowledgment is sent in a new SP INFO
otherwise it is sent in the response to the message containing the request, otherwise it is sent in the reply to the SIP request
VEDS). containing the VEDS).
8. Call Setup 8. Call Setup
A next-generation In-Vehicle System (IVS) initiates an NG-ACN call A next-generation In-Vehicle System (IVS) initiating an NG-ACN call
with a SIP INVITE using one of the SOS sub-services sends a SIP INVITE request 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. This
standard sets of crash data and capabilities data encoded in SIP INVITE request includes standard sets of both crash and
standardized and registered formats, attached as additional data capabilities data as described in Section 7.
blocks as specified in Section 4.1 of [RFC7852]. As described in
that document, each data block is identified by its MIME media type,
and pointed to by a CID URL in a Call-Info header with a 'purpose'
parameter value corresponding to the data block.
When placing an emergency call, the crash data set and IVS capability
data are transported as described in Section 7.
The Vehicle Emergency Data Set (VEDS) is an XML structure defined by
the Association of Public-Safety Communications Officials (APCO) and
the National Emergency Number Association (NENA) [VEDS]. It is
carried in a body part with MIME media type 'application/
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 included in
the INVITE by examining the Call-Info header fields for 'purpose' the SIP INVITE request by examining the Call-Info header fields for
parameters whose values start with 'EmergencyCallData.' The PSAP is 'purpose' parameters whose values start with 'EmergencyCallData.'
able to access the data it is capable of handling and is interested The PSAP is able to access the data it is capable of handling and is
in by checking the 'purpose' parameter values. interested 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].
9. Call Routing 9. New Metadata/Control Values
An Emergency Services IP Network (ESInet) is a network operated by or
on behalf of emergency services authorities. It handles emergency
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
architecture adopted by EENA, each PSAP is 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
control the routing and processing of emergency calls. The
centralization of such rules within ESInets allows for a cleaner
separation between the responsibilities of the originating network
and that of the emergency services network, and provides greater
flexibility and control over processing of emergency calls by the
emergency services authorities and PSAPs. This can make it easier to
react quickly to situations that require changes in how emergency
calls are routed or handled (e.g., a natural disaster closes a PSAP),
as well as ease in making long-term changes that affect such routing
(e.g., cooperative agreements to specially handle calls requiring
translation or relay services).
In an environment that uses ESInets, the originating network might
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
calls to an appropriate PSAP. In an environment without an ESInet,
the emergency services authorities and the originating carriers
determine how such calls are routed.
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 18, line 17 skipping to change at page 17, line 4
o Transmit data object (VEDS MUST be supported; MSD MAY be o Transmit data object (VEDS MUST be supported; MSD MAY be
supported) supported)
Optional Actions (the IVS and the PSAP MAY support): Optional Actions (the IVS and the PSAP MAY support):
o Play and/or display static (pre-defined) message o Play and/or display static (pre-defined) message
o Speak/display dynamic text (text supplied in action) o Speak/display dynamic text (text supplied in action)
o Flash or turn on or off a lamp (light) o Flash or turn on or off a lamp (light)
o Honk horn o Honk horn
o Enable a camera o Enable a camera
The <ack> element indicates the object being acknowledged (i.e., a The <ack> element indicates the object being acknowledged (i.e., a
data object or a metadata/control block containing <request> data object or a metadata/control block containing <request>
elements), and reports success or failure. elements), and reports success or failure.
The <capabilities> element has child <request> elements indicating The <capabilities> element has child <request> elements indicating
the actions supported by the IVS. the actions supported by the IVS.
The <request> element contains attributes to indicate the request and The <request> element contains attributes to indicate the request and
to supply any needed information, and MAY contain a <text> child to supply any needed information, and MAY contain a <text> child
element to contain the text for a dynamic message. The 'action' element to contain the text for a dynamic message. The 'action'
attribute is mandatory and indicates the specific action. attribute is mandatory and indicates the specific action.
[I-D.ietf-ecrit-ecall] established an IANA registry to contain the [I-D.ietf-ecrit-ecall] established an IANA registry to contain the
allowed values; this document adds new values to that registry in allowed values; this document adds new values to that registry in
Table 2. Table 2.
Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block Per [I-D.ietf-ecrit-ecall], the PSAP sends a metadata/control block
in response to the VEDS data sent by the IVS in SIP requests other in response to the VEDS data sent by the IVS in SIP requests other
than INFO (e.g., the INVITE). This metadata/control block is sent in than INFO (e.g., the INVITE). This metadata/control block is sent in
the SIP response to the request (e.g., the INVITE response). When the SIP response to the request (e.g., the INVITE response). When
the PSAP needs to send a control block that is not an immediate the PSAP needs to send a control block that is not an immediate
response to a VEDS or other data sent by the IVS, the control block response to a VEDS or other data sent by the IVS, the metadata/
is transmitted from the PSAP to the IVS in a SIP INFO request within control block is transmitted from the PSAP to the IVS in a SIP INFO
the established dialog. The IVS sends the requested data (e.g., the request within the established dialog. The IVS sends the requested
VEDS) or an acknowledgment (for requests other than to send data) in data (e.g., the VEDS) or an acknowledgment (for requests other than
a new INFO request. This mechanism flexibly allows the PSAP to send to send data or to indicate an inability to send the requested data)
metadata/control data to the IVS and the IVS to respond. If control in a new SIP INFO request. This mechanism flexibly allows the PSAP
data sent in a response message requests the IVS to send a new VEDS to send metadata/control data to the IVS and the IVS to respond. If
or other data block, or to perform an action other than sending data, a metadata/control block sent in a SIP response message requests the
the IVS sends the requested data or an acknowledgment regarding the IVS to send a new VEDS or other data block, or to perform an action
action in an INFO message within the dialog. other than sending data, the IVS sends the requested data or an
acknowledgment regarding the action in a SIP INFO request within the
dialog.
10.1. New values for the 'action' attribute' 9.1. New values for the 'action' attribute'
The following new "action" values are defined: The following new "action" values are defined:
msg-static displays or plays a predefined message (translated as msg-static displays or plays a predefined message (translated as
appropriate for the language of the vehicle's interface). A appropriate for the language of the vehicle's interface). A
registry is created in Section 16.4 for messages and their IDs. registry is created in Section 14.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. A registry of message
identification values is defined in Section 14.4. There is only
one static message initially defined (listed in Table 3). Because
all compliant vehicles are expected to support all static messages
translated into all languages supported by the vehicle, it is
important to limit the number of such messages. Therefore, this
registry operates under "Specification Required" rules as defined
in [RFC5226], which require a stable, public document and implies
expert review of the publication.
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 contained in a child <text> element within 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. The lamp is
identified by a lamp ID token contained in an "element-id"
attribute of the request. The desired state of the lamp is
indicated by a lamp state token contained in a "requested-state"
attribute. The duration of the lamp's requested state is
specified in a "persistence" attribute. A registry of lamp
identification values is defined in Section 14.5. The initial
values (listed in Table 4) are head, interior, fog-front, fog-
rear, brake, brake-center, position-front, position-rear, turn-
left, turn-right, and hazard. A registry of lamp states is
defined in Section 14.6. The initial values (listed in Table 5)
are "on", "off", and "flash".
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. A registry of camera identification values
is defined in Section 14.7. The initial values (listed in
Table 6) are backup, left-rear, right-rear, forward, rear-wide,
lane, interior, and night-front.
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.
10.2. Request Example 9.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">
<request action="send-data" datatype="VEDS"/> <request action="send-data" datatype="VEDS"/>
<request action="lamp" lamp-id="hazard" <request action="lamp" element-id="hazard"
lamp-action="flash" persistance="PT1H"/> requested-state="flash" persistence="PT1H"/>
<request action="msg-static" msgid="1"/> <request action="msg-static" int-id="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
10.3. The <ack> element 9.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.
10.3.1. Ack Examples 9.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">
<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
10.4. The <capabilities> element 9.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 IVS, 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 'int-id' attribute set to the highest supported static message
supported by the vehicle. A registry is created in Section 16.4 to supported by the vehicle. A registry is created in Section 14.4 to
map 'msgid' values to static text messages. By sending the highest map 'int-id' 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 16.5 to contain lamp ID values. created in Section 14.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 16.6 to contain camera ID values. registry is created in Section 14.7 to contain camera ID values.
10.4.1. Capabilities Example 9.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">
<capabilities> <capabilities>
<request action="send-data" supported-values="VEDS"/> <request action="send-data" supported-values="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front; supported-values="head;interior;fog-front;
fog-rear;brake;position-front;position-rear; fog-rear;brake;position-front;position-rear;
turn-left;turn-right;hazard"/> turn-left;turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" int-id="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<request action="enable-camera" <request action="enable-camera"
supported-values="backup; interior"/> supported-values="backup; interior"/>
</capabilities> </capabilities>
</EmergencyCallData.control> </EmergencyCallData.control>
Figure 9: Capabilities Example Figure 9: Capabilities Example
11. Test Calls 10. Test Calls
An NG-ACN test call is a call that is recognized and treated to some An NG-ACN test call is a call that is recognized and treated to some
extent as an NG-ACN call but not given emergency call treatment and extent as an NG-ACN call but not given emergency call treatment and
not handled by a call taker. The specific handling of test NG-ACN not handled by a call taker. The specific handling of test NG-ACN
calls is not itself standardized; the test call facility is intended calls is not itself standardized; the test call facility is intended
to allow the IVS, user, or TSP to verify that an NG-ACN call can be to allow the IVS, user, or TSP to verify that an NG-ACN call can be
successfully established with voice and/or other media communication. successfully established with voice and/or other media communication.
The IVS might also be able to verify that the crash data was The IVS might also be able to verify that the crash data was
successfully received. successfully received.
skipping to change at page 22, line 34 skipping to change at page 22, line 17
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).
12. The emergencyCallData.eCall.VEDS INFO package 11. Example
This document registers the 'emergencyCallData.eCall.VEDS' INFO
package.
Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.VEDS' in a Recv-Info header field per
[RFC6086] to indicate ability to receive INFO messages carrying data
as described here.
Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates
the ability to receive NG-ACN related body parts as specified in
[TBD: THIS DOCUMENT].
An INFO request message carrying data related to an emergency call as
described in [TBD: THIS DOCUMENT] has an Info-Package header field
set to 'emergencyCallData.eCall.VEDS' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the
following sections.
12.1. Overall Description
This section describes "what type of information is carried in INFO
requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package."
INFO requests associated with the emergencyCallData.eCall.VEDS INFO
package carry data associated with emergency calls as defined in
[TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency
calls established using SIP. The functionality is to carry vehicle
data and metadata/control information between vehicles and PSAPs.
Refer to [TBD: THIS DOCUMENT] for more information.
12.2. Applicability
This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...."
The use of INFO is based on an analysis of the requirements against
the intent and effects of INFO versus other approaches (which
included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane
transport, and non-SIP protocols). In particular, the transport of
emergency call data blocks occurs within a SIP emergency dialog, per
Section 7, and is normally carried in the initial INVITE and its
response; the use of INFO only occurs when emergency-call-related
data needs to be sent mid-call. While MESSAGE could be used, it is
not tied to a SIP dialog as is INFO and thus might not be associated
with the dialog. SIP OPTIONS or re-INVITE could also be used, but is
seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into
service, but the semantics are not a good fit, e.g., the subscribe/
notify mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport.
12.3. Info Package Name
The info package name is emergencyCallData.eCall.VEDS
12.4. Info Package Parameters
None
12.5. SIP Option-Tags
None
12.6. INFO Request Body Parts
The body for an emergencyCallData.eCall.VEDS info package is a
multipart body which MAY contain zero or one application/
emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part,
zero or more application/emergencyCallData.control+xml (containing a
metadata/control object) parts, and zero or one application/
emergencyCallData.eCall.MSD+per (containing an MSD) part. At least
one VEDS, MSD, or metadata/control body part is expected; the
behavior upon receiving an INFO request with none is undefined.
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
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-
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). The innermost multipart that
contains only body parts associated with the INFO package has a
Content-Disposition value of Info-Package.
Service providers are not expected to attach [RFC7852] Additional
Data to an INFO request.
See [TBD: THIS DOCUMENT] for more information.
12.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT].
12.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated data set,
and for the IVS to send the requested data set. Because this is
normally done only on manual request of the PSAP call taker (who
suspects some aspect of the vehicle state has changed), the rate of
SIP INFO requests associated with the emergencyCallData.eCall.VEDS
info package is normally quite low (most dialogs are likely to
contain zero INFO requests, while others can be expected to carry an
occasional request).
12.9. Info Package Security Considerations
The MIME media type registations for the data blocks that can be
carried using this INFO package contains a discussion of the security
and/or privacy considerations specific to that data block. The
"Security Considerations" and "Privacy Considerations" sections of
[TBD: THIS DOCUMENT] discuss security and privacy considerations of
the data carried in vehicle-initiated emergency calls as described in
that document.
12.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details.
12.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples.
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 26 skipping to change at page 23, line 6
| +-------+ | | +-------+ |
| | | |
| | | |
| | | |
| 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 request with location information (a PIDF-LO), VEDS crash data
data block), and capabilities data (a metadata/control block with (a VEDS data block), and capabilities data (a metadata/control block
extensions defined in this document) attached to the SIP INVITE with extensions defined in this document) included in the SIP INVITE
message. The INVITE has a request URI containing the request 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 a crashed
crashed vehicle. The example communicates that the car is a model vehicle. The example communicates that the car is a model year 2015
year 2015 Saab 9-5 (a car which does not exist). The front airbag Saab 9-5 (a car which does not exist). The front airbag deployed as
deployed as a consequence of the crash. The a consequence of the crash. The 'VehicleBodyCategoryCode' indicates
'VehicleBodyCategoryCode' indicates that the crashed vehicle is a that the crashed vehicle is a passenger car (the code is set to
passenger car (the code is set to '101') and that it is not a '101') and that it is not a convertible (the 'ConvertibleIndicator'
convertible (the 'ConvertibleIndicator' value is set to 'false'). value is set to 'false').
The 'VehicleCrashPulse' element provides further information about The 'VehicleCrashPulse' element provides further information about
the crash, namely that the force of impact based on the change in the crash, namely that the force of impact based on the change in
velocity over the duration of the crash pulse was 100 MPH. The velocity over the duration of the crash pulse was 100 MPH. The
principal direction of the force of the impact is set to '12' (which principal direction of the force of the impact is set to '12' (which
refers to 12 O'Clock, corresponding to a frontal collision). This refers to 12 O'Clock, corresponding to a frontal collision). This
value is described in the 'CrashPulsePrincipalDirectionOfForceValue' value is described in the 'CrashPulsePrincipalDirectionOfForceValue'
element. element.
The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of
skipping to change at page 30, line 25 skipping to change at page 27, line 4
<VehicleFinalRestOrientationCategoryCode>Driver <VehicleFinalRestOrientationCategoryCode>Driver
</VehicleFinalRestOrientationCategoryCode> </VehicleFinalRestOrientationCategoryCode>
<VehicleFireIndicator>false</VehicleFireIndicator> <VehicleFireIndicator>false</VehicleFireIndicator>
</Crash> </Crash>
</AutomatedCrashNotification> </AutomatedCrashNotification>
--boundary1 --boundary1
Content-Type: application/emergencyCallData.control+xml Content-Type: application/emergencyCallData.control+xml
Content-ID: <1234567892@atlanta.example.com> Content-ID: <1234567892@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?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">
<capabilities> <capabilities>
<request action="send-data" supported-datatypes="VEDS"/> <request action="send-data" supported-datatypes="VEDS"/>
<request action="lamp" <request action="lamp"
supported-values="head;interior;fog-front;fog-rear; supported-values="head;interior;fog-front;fog-rear;
brake;position-front;position-rear;turn-left; brake;position-front;position-rear;turn-left;
turn-right;hazard"/> turn-right;hazard"/>
<request action="msg-static" msgid="3"/> <request action="msg-static" int-id="3"/>
<request action="msg-dynamic"/> <request action="msg-dynamic"/>
<request action="honk"/> <request action="honk"/>
<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
14. Security Considerations 12. 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 28 skipping to change at page 28, line 5
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").
15. Privacy Considerations 13. 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).
16. IANA Considerations 14. IANA Considerations
This document registers the 'application/EmergencyCall.VEDS+xml' MIME This document registers the 'application/EmergencyCall.VEDS+xml' MIME
media type, and adds "VEDS" to the Emergency Call Additional Data media type, and adds "VEDS" to the Emergency Call Data Types
registry. This document adds to and creates sub-registries in the registry. This document adds to and creates sub-registries in the
"Emergency Call Metadata/Control Data" registry created in "Emergency Call Metadata/Control Data" registry created in
[I-D.ietf-ecrit-ecall]. This document registers a new INFO package. [I-D.ietf-ecrit-ecall]. This document registers a new SIP INFO
package.
16.1. MIME Media Type Registration for 'application/ 14.1. MIME Media Type Registration for 'application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml'
This specification requests the registration of a new MIME media type This specification requests the registration of a new MIME media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
skipping to change at page 32, line 37 skipping to change at page 29, line 14
Security considerations: Security considerations:
This media type is designed to carry vehicle crash data during This media type is designed to carry vehicle crash data during
an emergency call. an emergency call.
This data can contain personal information including vehicle This data can contain personal information including vehicle
VIN, location, direction, etc. Appropriate precautions need to VIN, location, direction, etc. Appropriate precautions need to
be taken to limit unauthorized access, inappropriate disclosure be taken to limit unauthorized access, inappropriate disclosure
to third parties, and eavesdropping of this information. to third parties, and eavesdropping of this information.
Please refer to Section 7 and Section 8 of [RFC7852] for more Please refer to Section 9 and Section 10 of [RFC7852] for more
information. information.
When this media type is contained in a signed or encrypted body When this media type is contained in a signed or encrypted body
part, the enclosing multipart (e.g., multipart/signed or part, the enclosing multipart (e.g., multipart/signed or
multipart/encrypted) has the same Content-ID as the data part. multipart/encrypted) has the same Content-ID as the data part.
This allows an entity to identify and access the data blocks it This allows an entity to identify and access the data blocks it
is interested in without having to dive deeply into the message is interested in without having to dive deeply into the message
structure or decrypt parts it is not interested in. (The structure or decrypt parts it is not interested in. (The
'purpose' parameter in a Call-Info header field identifies the 'purpose' parameter in a Call-Info header field identifies the
data, and the CID URL points to the data block in the body, data, and the CID URL points to the data block in the body,
skipping to change at page 33, line 4 skipping to change at page 29, line 28
part, the enclosing multipart (e.g., multipart/signed or part, the enclosing multipart (e.g., multipart/signed or
multipart/encrypted) has the same Content-ID as the data part. multipart/encrypted) has the same Content-ID as the data part.
This allows an entity to identify and access the data blocks it This allows an entity to identify and access the data blocks it
is interested in without having to dive deeply into the message is interested in without having to dive deeply into the message
structure or decrypt parts it is not interested in. (The structure or decrypt parts it is not interested in. (The
'purpose' parameter in a Call-Info header field identifies the 'purpose' parameter in a Call-Info header field identifies the
data, and the CID URL points to the data block in the body, data, and the CID URL points to the data block in the body,
which has a matching Content-ID body part header field). which has a matching Content-ID body part header field).
Interoperability considerations: None Interoperability considerations: None
Published specification: [VEDS] Published specification: [VEDS]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: None Additional information: None
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Persons and email addresses for further information: Randall Persons and email addresses for further information: Randall
Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, Gellens 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>
16.2. Registration of the 'VEDS' entry in the Emergency Call Additional 14.2. Registration of the 'VEDS' entry in the Emergency Call Data Types
Data registry 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 Data Types registry, with a reference to this
document. The Emergency Call Additional Data registry was document; the 'Data About' value is 'The Call'. The Emergency Call
established by [RFC7852]. Data types registry was established by [RFC7852].
16.3. New Action Values 14.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 "Emergency Call Action" registry created by <request> element in the "Emergency Call Action" registry created by
[I-D.ietf-ecrit-ecall]. [I-D.ietf-ecrit-ecall].
+---------------+--------------------------------------+ +---------------+-------------------------------------+
| Name | Description | | Name | Description |
+---------------+--------------------------------------+ +---------------+-------------------------------------+
| msg-static | Section 10.1 of [TBD: THIS DOCUMENT] | | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| msg-dynamic | Section 10.1 of [TBD: THIS DOCUMENT] | | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| honk | Section 10.1 of [TBD: THIS DOCUMENT] | | honk | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| lamp | Section 10.1 of [TBD: THIS DOCUMENT] | | lamp | Section 9.1 of [TBD: THIS DOCUMENT] |
| | | | | |
| enable-camera | Section 10.1 of [TBD: THIS DOCUMENT] | | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] |
+---------------+--------------------------------------+ +---------------+-------------------------------------+
Table 2: Emergency Call Action Registry New Values Table 2: Emergency Call Action Registry New Values
16.4. Emergency Call Static Message Registry 14.4. Emergency Call Static Message Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Static Message" in the "Emergency Call Metadata/Control Data" Static Message" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. Because all registry established by [I-D.ietf-ecrit-ecall]. Because all
compliant vehicles are expected to support all static messages compliant vehicles are expected to support all static messages
translated into all languages supported by the vehicle, it is translated into all languages supported by the vehicle, it is
important to limit the number of such messages. As defined in important to limit the number of such messages. As defined in
[RFC5226], this registry operates under "Publication Required" rules, [RFC5226], this registry operates under "Specification Required"
which require a stable, public document and implies expert review of rules, which require a stable, public document and implies expert
the publication. The expert should determine that the document has review of the publication. The expert should determine that the
been published by an appropriate emergency services organization document has been published by an appropriate emergency services
(e.g., NENA, EENA, APCO) or by the IETF with input from an emergency organization (e.g., NENA, EENA, APCO) or by the IETF with input from
services organization, and that the proposed message is sufficiently an emergency services organization, and that the proposed message is
distinguishable from other messages. sufficiently distinguishable from other messages.
The contents of this registry are: The contents of this registry are:
ID: An integer identifier to be used in the 'msgid' attribute of a ID: An integer identifier to be used in the 'int-id' attribute of a
metadata/control <request> element. metadata/control <request> element.
Message: The text of the message. Messages are listed in the Message: The text of the message. Messages are listed in the
registry in English; vehicles are expected to implement registry in English; vehicles are expected to implement
translations into languages supported by the vehicle. translations into languages supported by the vehicle.
When new messages are added to the registry, the message text is When new messages are added to the registry, the message text is
determined by the registrant; IANA assigns the IDs. Each message is determined by the registrant; IANA assigns the IDs. Each message is
assigned a consecutive integer value as its ID. This allows an IVS assigned a consecutive integer value as its ID. This allows an IVS
to indicate by a single integer value that it supports all messages to indicate by a single integer value that it supports all messages
skipping to change at page 35, line 15 skipping to change at page 31, line 30
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| ID | Message | | ID | Message |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
| 1 | Emergency services has noted your information and location, | | 1 | Emergency services has noted your information and location, |
| | but cannot speak with you right now. We will help you as | | | but cannot speak with you right now. We will help you as |
| | soon as possible. | | | soon as possible. |
+----+--------------------------------------------------------------+ +----+--------------------------------------------------------------+
Table 3: Emergency Call Static Message Registry Initial Values Table 3: Emergency Call Static Message Registry Initial Values
16.5. Emergency Call Vehicle Lamp ID Registry 14.5. Emergency Call Vehicle Lamp ID Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Vehicle Lamp ID" in the "Emergency Call Metadata/Control Data" Vehicle Lamp ID" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. This new sub- registry established by [I-D.ietf-ecrit-ecall]. This new sub-
registry uniquely identifies the names of automotive lamps (lights). registry uniquely identifies the names of automotive lamps (lights).
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the proposed lamp name is rules. The expert should determine that the proposed lamp name is
clearly understandable and is sufficiently distinguishable from other clearly understandable and is sufficiently distinguishable from other
lamp names. lamp names.
The contents of this registry are: The contents of this registry are:
Name: The identifier to be used in the 'lamp-ID' attribute of a Name: The identifier to be used in the 'element-id' attribute of a
metadata/control <request> element. metadata/control <request> element.
Description: A description of the lamp (light). Description: A description of the lamp (light).
The initial set of values is listed in Table 4. The initial set of values is listed in Table 4.
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| Name | Description | | Name | Description |
+----------------+---------------------------------------------+ +----------------+---------------------------------------------+
| head | The main lamps used to light the road ahead | | head | The main lamps used to light the road ahead |
skipping to change at page 36, line 33 skipping to change at page 32, 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: Emergency Call Lamp ID Registry Initial Values Table 4: Emergency Call Lamp ID Registry Initial Values
16.6. Emergency Call Vehicle Camera ID Registry 14.6. Lamp State Registry
This document creates a new sub-registry called "Lamp State" in the
"Emergency Call Metadata/Control Data" registry established by
[I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies
the states that lamps (lights) can be placed into. As defined in
[RFC5226], this registry operates under "Expert Review" rules. The
expert should determine that the proposed lamp state is clearly
understandable and is sufficiently distinguishable from other lamp
states.
The contents of this registry are:
Name: The identifier to be used in the 'requested-state' attribute
of a metadata/control <request> element.
Description: A description of state of a lamp (light).
The initial set of values is listed in Table 5.
+-------+----------------------------------------+
| Name | Description |
+-------+----------------------------------------+
| on | The lamp is on (illuminated) |
| | |
| off | The lamp is off (extinguished) |
| | |
| flash | The lamp alternates between on and off |
+-------+----------------------------------------+
Table 5: Lamp State Registry Initial Values
14.7. Emergency Call Vehicle Camera ID Registry
This document creates a new sub-registry called "Emergency Call This document creates a new sub-registry called "Emergency Call
Vehicle Camera ID" in the "Emergency Call Metadata/Control Data" Vehicle Camera ID" in the "Emergency Call Metadata/Control Data"
registry established by [I-D.ietf-ecrit-ecall]. This new sub- registry established by [I-D.ietf-ecrit-ecall]. This new sub-
registry uniquely identifies automotive cameras. As defined in registry uniquely identifies automotive cameras. As defined in
[RFC5226], this registry operates under "Expert Review" rules. The [RFC5226], this registry operates under "Expert Review" rules. The
expert should determine that the proposed camera name is clearly expert should determine that the proposed camera name is clearly
understandable and is sufficiently distinguishable from other camera understandable and is sufficiently distinguishable from other camera
names. names.
The contents of this registry are: The contents of this registry are:
Name: The identifier to be used in the 'camera-ID' attribute of a Name: The identifier to be used in the 'element-id' attribute of a
control <request> element. control <request> element.
Description: A description of the camera. Description: A description of the camera.
The initial set of values is listed in Table 5. The initial set of values is listed in Table 6.
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| Name | Description | | Name | Description |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
| backup | Shows what is behind the vehicle, e.g., often used | | backup | Shows what is behind the vehicle, e.g., often used |
| | for driver display when the vehicle is in reverse. | | | for driver display when the vehicle is in reverse. |
| | Also known as rearview, reverse, rear visibility, | | | Also known as rearview, reverse, rear visibility, |
| | etc. | | | etc. |
| | | | | |
| left-rear | Shows view to the left and behind (e.g., left side | | left-rear | Shows view to the left and behind (e.g., left side |
skipping to change at page 37, line 34 skipping to change at page 34, line 34
| | | | | |
| lane | Used by systems to identify road lane and/or | | lane | Used by systems to identify road lane and/or |
| | monitor vehicle's position within lane | | | monitor vehicle's position within lane |
| | | | | |
| interior | Shows the interior (e.g., driver) | | interior | Shows the interior (e.g., driver) |
| | | | | |
| night-front | Night-vision view of what is in front of the | | night-front | Night-vision view of what is in front of the |
| | vehicle | | | vehicle |
+-------------+-----------------------------------------------------+ +-------------+-----------------------------------------------------+
Table 5: Emergency Call Vehicle Camera ID Registry Initial Values Table 6: Emergency Call Vehicle Camera ID Registry Initial Values
17. Acknowledgements 14.8. The emergencyCallData.eCall.VEDS SIP INFO package
We would like to thank Lena Chaponniere, Stephen Edge, Christer This document registers the 'emergencyCallData.eCall.VEDS' SIP INFO
Holmberg, and Allison Mankin for their review and suggestions; Robert package.
Sparks and Paul Kyzivat for their help with the SIP mechanisms;
Michael Montag, Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar
Hellstrom, and Rex Buddenberg for their feedback; and Ulrich Dietz
for his help with earlier versions of the original version of this
document.
18. Changes from Previous Versions Both endpoints (the IVS and the PSAP equipment) include
'emergencyCallData.eCall.VEDS' in a Recv-Info header field per
[RFC6086] to indicate ability to receive SIP INFO messages carrying
data as described here.
18.1. Changes from draft-ietf-18 to draft-ietf-19 Support for the 'emergencyCallData.eCall.VEDS' SIP INFO package
indicates the ability to receive NG-ACN related body parts as
specified in [TBD: THIS DOCUMENT].
A SIP INFO request message carrying data related to an emergency call
as described in [TBD: THIS DOCUMENT] has an Info-Package header field
set to 'emergencyCallData.eCall.VEDS' per [RFC6086].
The requirements of Section 10 of [RFC6086] are addressed in the
following sections.
14.8.1. Overall Description
This section describes "what type of information is carried in Info
requests associated with the Info Package, and for what types of
applications and functionalities UAs can use the Info Package."
SIP INFO requests associated with the emergencyCallData.eCall.VEDS
SIP INFO package carry data associated with emergency calls as
defined in [TBD: THIS DOCUMENT]. The application is vehicle-
initiated emergency calls established using SIP. The functionality
is to carry vehicle data and metadata/control information between
vehicles and PSAPs. Refer to [TBD: THIS DOCUMENT] for more
information.
14.8.2. Applicability
This section describes "why the Info Package mechanism, rather than
some other mechanism, has been chosen for the specific use-case...."
The use of the SIP INFO method is based on an analysis of the
requirements against the intent and effects of the INFO method versus
other approaches (which included the SIP MESSAGE method, SIP OPTIONS
method, SIP re-INVITE method, media plane transport, and non-SIP
protocols). In particular, the transport of emergency call data
blocks occurs within a SIP emergency dialog, per Section 7, and is
normally carried in the initial INVITE request and its response; the
use of the INFO method only occurs when emergency-call-related data
needs to be sent mid-call. While the SIP MESSAGE method could be
used, it is not tied to a SIP dialog as is the INFO method and thus
might not be associated with the dialog. Both the SIP OPTIONS or re-
INVITE methods could also be used, but is seen as less clean than the
INFO method. The SIP SUBSCRIBE/NOTIFY method could be coerced into
service, but the semantics are not a good fit, e.g., the subscribe/
notify mechanism provides one-way communication consisting of (often
multiple) notifications from notifier to subscriber indicating that
certain events in notifier have occurred, whereas what's needed here
is two-way communication of data related to the emergency dialog.
Use of the media plane mechanisms was discounted because the number
of messages needing to be exchanged in a dialog is normally zero or
very few, and the size of the data is likewise very small. The
overhead caused by user plane setup (e.g., to use MSRP as transport)
would be disproportionately large.
Based on the the analyses, the SIP INFO method was chosen to provide
for mid-call data transport.
14.8.3. Info Package Name
The SIP INFO package name is emergencyCallData.eCall.VEDS
14.8.4. Info Package Parameters
None
14.8.5. SIP Option-Tags
None
14.8.6. INFO Request Body Parts
The body of an emergencyCallData.eCall.VEDS SIP INFO package is a
multipart body which MAY contain zero or one application/
emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part,
zero or more application/emergencyCallData.control+xml (containing a
metadata/control object) parts, and zero or one application/
emergencyCallData.eCall.MSD+per (containing an MSD) part. At least
one VEDS, MSD, or metadata/control body part is expected; the
behavior upon receiving a SIP INFO request with none is undefined.
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
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-
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). The innermost multipart that
contains only body parts associated with the SIP INFO package has a
Content-Disposition value of Info-Package.
Service providers are not expected to add [RFC7852] Additional Data
to SIP INFO requests.
See [TBD: THIS DOCUMENT] for more information.
14.8.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT].
14.8.8. Rate of INFO Requests
The SIP INFO request is used within an established emergency call
dialog for the PSAP to request the IVS to send an updated data set,
and for the IVS to send the requested data set. Because this is
normally done only on manual request of the PSAP call taker (who
suspects some aspect of the vehicle state has changed), the rate of
SIP INFO requests associated with the emergencyCallData.eCall.VEDS
SIP INFO package is normally quite low (most dialogs are likely to
contain zero SIP INFO requests, while others can be expected to carry
an occasional request).
14.8.9. Info Package Security Considerations
The MIME media type registations for the data blocks that can be
carried using this SIP INFO package contains a discussion of the
security and/or privacy considerations specific to that data block.
The "Security Considerations" and "Privacy Considerations" sections
of [TBD: THIS DOCUMENT] discuss security and privacy considerations
of the data carried in vehicle-initiated emergency calls as described
in that document.
14.8.10. Implementation Details
See [TBD: THIS DOCUMENT] for protocol details.
14.8.11. Examples
See [TBD: THIS DOCUMENT] for protocol examples.
15. Acknowledgements
We would like to thank Lena Chaponniere, Alissa Cooper, Stephen Edge,
Christer Holmberg, and Allison Mankin for their review and
suggestions; Robert Sparks and Paul Kyzivat for their help with the
SIP mechanisms; Michael Montag, Arnoud van Wijk, Ban Al-Bakri, Wes
George, Gunnar Hellstrom, and Rex Buddenberg for their feedback; and
Ulrich Dietz for his help with earlier versions of the original
version of this document.
16. Changes from Previous Versions
16.1. Changes from draft-ietf-18 to draft-ietf-19
o Fixed various nits o Fixed various nits
18.2. Changes from draft-ietf-17 to draft-ietf-18 16.2. Changes from draft-ietf-17 to draft-ietf-18
o Added additional text to "Rate of Info Requests" o Added additional text to "Rate of Info Requests"
o Further corrected "content type" to "media type" o Further corrected "content type" to "media type"
18.3. Changes from draft-ietf-16 to draft-ietf-17 16.3. Changes from draft-ietf-16 to draft-ietf-17
o Clarified that an INFO request is expected to have at least one o Clarified that an INFO request is expected to have at least one
VEDS, MSD or metadata/control body part VEDS, MSD or metadata/control body part
o Corrected "content type" to "media type" o Corrected "content type" to "media type"
18.4. Changes from draft-ietf-14 to draft-ietf-15 16.4. Changes from draft-ietf-14 to draft-ietf-15
o Moved VEDS text from Introduction to new Vehicle Data section o Moved VEDS text from Introduction to new Vehicle Data section
o Various clarifications and simplifications o Various clarifications and simplifications
18.5. Changes from draft-ietf-13 to draft-ietf-14 16.5. 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.
18.6. Changes from draft-ietf-11 to draft-ietf-13 16.6. Changes from draft-ietf-11 to draft-ietf-13
o Fixed typos o Fixed typos
18.7. Changes from draft-ietf-10 to draft-ietf-11 16.7. 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
18.8. Changes from draft-ietf-09 to draft-ietf-10 16.8. 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.
18.9. Changes from draft-ietf-08 to draft-ietf-09 16.9. 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.
18.10. Changes from draft-ietf-07 to draft-ietf-08 16.10. 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"
18.11. Changes from draft-ietf-06 to draft-ietf-07 16.11. Changes from draft-ietf-06 to draft-ietf-07
o Minor editorial changes o Minor editorial changes
18.12. Changes from draft-ietf-05 to draft-ietf-06 16.12. 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.
18.13. Changes from draft-ietf-04 to draft-ietf-05 16.13. 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
18.14. Changes from draft-ietf-03 to draft-ietf-04 16.14. 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
18.15. Changes from draft-ietf-02 to draft-ietf-03 16.15. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
18.16. Changes from draft-ietf-01 to draft-ietf-02 16.16. 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
18.17. Changes from draft-ietf-00 to draft-ietf-01 16.17. 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
18.18. Changes from draft-gellens-02 to draft-ietf-00 16.18. 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
18.19. Changes from draft-gellens-01 to -02 16.19. 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]
18.20. Changes from draft-gellens-00 to -01 16.20. Changes from draft-gellens-00 to -01
o Now using 'EmergencyCallData' for purpose parameter values and o Now using 'EmergencyCallData' for purpose parameter values and
MIME subtypes, in accordance with changes to [RFC7852] MIME subtypes, in accordance with changes to [RFC7852]
o Added reference to RFC 6443 o Added reference to RFC 6443
o Fixed bug that caused Figure captions to not appear o Fixed bug that caused Figure captions to not appear
19. References 17. References
19.1. Normative References 17.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-19 (work in European eCall", draft-ietf-ecrit-ecall-20 (work in
progress), October 2016. progress), November 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>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
DOI 10.17487/RFC5226, May 2008, DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>. <http://www.rfc-editor.org/info/rfc5226>.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, Specifications and Registration Procedures", BCP 13,
RFC 6838, DOI 10.17487/RFC6838, January 2013, RFC 6838, DOI 10.17487/RFC6838, January 2013,
<http://www.rfc-editor.org/info/rfc6838>. <http://www.rfc-editor.org/info/rfc6838>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>. <http://www.rfc-editor.org/info/rfc6881>.
skipping to change at page 41, line 40 skipping to change at page 41, line 45
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>.
19.2. Informative references 17.2. Informative references
[RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, DOI 10.17487/RFC5012, January 2008, RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>. <http://www.rfc-editor.org/info/rfc5012>.
[RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M.
Shanmugam, "Security Threats and Requirements for Shanmugam, "Security Threats and Requirements for
Emergency Call Marking and Mapping", RFC 5069, Emergency Call Marking and Mapping", RFC 5069,
DOI 10.17487/RFC5069, January 2008, DOI 10.17487/RFC5069, January 2008,
<http://www.rfc-editor.org/info/rfc5069>. <http://www.rfc-editor.org/info/rfc5069>.
[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
Initiation Protocol (SIP) INFO Method and Package
Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011,
<http://www.rfc-editor.org/info/rfc6086>.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, DOI 10.17487/RFC6443, December Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>. 2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
"Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378,
December 2014, <http://www.rfc-editor.org/info/rfc7378>. December 2014, <http://www.rfc-editor.org/info/rfc7378>.
[triage-2008] [triage-2008]
 End of changes. 123 change blocks. 
528 lines changed or deleted 531 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/