draft-ietf-ecrit-car-crash-11.txt   draft-ietf-ecrit-car-crash-12.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: March 26, 2017 NeuStar, Inc. Expires: March 29, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
September 22, 2016 September 25, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-11.txt draft-ietf-ecrit-car-crash-12.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
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 March 26, 2017. This Internet-Draft will expire on March 29, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 46 skipping to change at page 2, line 46
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8
4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10
6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15
8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 17
9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17
9.1. New values for the 'action' attribute' . . . . . . . . . 18 9.1. New values for the 'action' attribute' . . . . . . . . . 19
9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19
9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 19 9.3. The <ack> element . . . . . . . . . . . . . . . . . . . . 20
9.4. The <capabilities> element . . . . . . . . . . . . . . . 20 9.4. The <capabilities> element . . . . . . . . . . . . . . . 21
10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 22 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23
11.1. Overall Description . . . . . . . . . . . . . . . . . . 23 11.1. Overall Description . . . . . . . . . . . . . . . . . . 23
11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 23 11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24
11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 23 11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24
11.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 11.4. Info Package Parameters . . . . . . . . . . . . . . . . 24
11.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 11.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24
11.6. INFO Message Body Parts . . . . . . . . . . . . . . . . 24 11.6. INFO Message Body Parts . . . . . . . . . . . . . . . . 24
11.7. Info Package Usage Restrictions . . . . . . . . . . . . 25 11.7. Info Package Usage Restrictions . . . . . . . . . . . . 25
11.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 11.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25
11.9. Info Package Security Considerations . . . . . . . . . . 25 11.9. Info Package Security Considerations . . . . . . . . . . 25
11.10. Implementation Details . . . . . . . . . . . . . . . . . 25 11.10. Implementation Details . . . . . . . . . . . . . . . . . 26
11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 25 11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 26
12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 32
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
15.1. MIME Content-type Registration for 15.1. MIME Content-type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32
15.2. Registration of the 'VEDS' entry in the Emergency Call 15.2. Registration of the 'VEDS' entry in the Emergency Call
Additional Data registry . . . . . . . . . . . . . . . . 33 Additional Data registry . . . . . . . . . . . . . . . . 34
15.3. New Action Values . . . . . . . . . . . . . . . . . . . 33 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 34
15.4. Static Message Registry . . . . . . . . . . . . . . . . 34 15.4. Static Message Registry . . . . . . . . . . . . . . . . 34
15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35
15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36
16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
17. Changes from Previous Versions . . . . . . . . . . . . . . . 37 17. Changes from Previous Versions . . . . . . . . . . . . . . . 37
17.1. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37 17.1. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37
17.2. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 17.2. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38
17.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 17.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38
17.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 17.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38
17.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 17.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38
skipping to change at page 4, line 38 skipping to change at page 4, line 38
| 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 |
| 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,
to avoid receptively writing "IVS or TSP", the term "IVS" is used to
represent either an IVS or TSP when discussing signaling behavior
(e.g., attaching VEDS data, sending an INVITE request, receiving an
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.
Drivers often have a poor location awareness, especially outside of Drivers often have a poor location awareness, especially outside of
 End of changes. 12 change blocks. 
19 lines changed or deleted 25 lines changed or added

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