draft-ietf-ecrit-car-crash-15.txt   draft-ietf-ecrit-car-crash-16.txt 
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Core Technology Consulting Internet-Draft Core Technology Consulting
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: April 15, 2017 NeuStar, Inc. Expires: April 19, 2017 NeuStar, Inc.
H. Tschofenig H. Tschofenig
Individual Individual
October 12, 2016 October 16, 2016
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-15.txt draft-ietf-ecrit-car-crash-16.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 April 15, 2017. This Internet-Draft will expire on April 19, 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 3, line 16 skipping to change at page 3, line 16
12. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23 12. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23
12.1. Overall Description . . . . . . . . . . . . . . . . . . 23 12.1. Overall Description . . . . . . . . . . . . . . . . . . 23
12.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24 12.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24
12.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24 12.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24
12.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 12.4. Info Package Parameters . . . . . . . . . . . . . . . . 24
12.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 12.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24
12.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24 12.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24
12.7. Info Package Usage Restrictions . . . . . . . . . . . . 25 12.7. Info Package Usage Restrictions . . . . . . . . . . . . 25
12.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 12.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25
12.9. Info Package Security Considerations . . . . . . . . . . 25 12.9. Info Package Security Considerations . . . . . . . . . . 25
12.10. Implementation Details . . . . . . . . . . . . . . . . . 25 12.10. Implementation Details . . . . . . . . . . . . . . . . . 26
12.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 26 12.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 26
13. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 13. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
14. Security Considerations . . . . . . . . . . . . . . . . . . . 31 14. Security Considerations . . . . . . . . . . . . . . . . . . . 31
15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31
16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 16. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32
16.1. MIME Content-type Registration for 16.1. MIME Content-type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32
16.2. Registration of the 'VEDS' entry in the Emergency Call 16.2. Registration of the 'VEDS' entry in the Emergency Call
Additional Data registry . . . . . . . . . . . . . . . . 33 Additional Data registry . . . . . . . . . . . . . . . . 33
16.3. New Action Values . . . . . . . . . . . . . . . . . . . 34 16.3. New Action Values . . . . . . . . . . . . . . . . . . . 34
skipping to change at page 25, line 17 skipping to change at page 25, line 17
The body parts are sent per [RFC6086], and in addition, to align with The body parts are sent per [RFC6086], and in addition, to align with
with how these body parts are sent in non-INFO messages, each with how these body parts are sent in non-INFO messages, each
associated body part is referenced by a Call-Info header field at the associated body part is referenced by a Call-Info header field at the
top level of the SIP message. The body part has a Content- top level of the SIP message. The body part has a Content-
Disposition header field set to "By-Reference". Disposition header field set to "By-Reference".
A VEDS or metadata/control block is always enclosed in a multipart 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 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 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 Content-ID as a SIP header field is not defined (while it is defined
for use as a MIME header field). 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 Service providers are not expected to attach [RFC7852] Additional
Data to an INFO request. Data to an INFO request.
See [TBD: THIS DOCUMENT] for more information. See [TBD: THIS DOCUMENT] for more information.
12.7. Info Package Usage Restrictions 12.7. Info Package Usage Restrictions
Usage is limited to vehicle-initiated emergency calls as defined in Usage is limited to vehicle-initiated emergency calls as defined in
[TBD: THIS DOCUMENT]. [TBD: THIS DOCUMENT].
 End of changes. 6 change blocks. 
6 lines changed or deleted 8 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/