--- 1/draft-ietf-ecrit-car-crash-05.txt 2016-02-19 17:15:36.060443291 -0800 +++ 2/draft-ietf-ecrit-car-crash-06.txt 2016-02-19 17:15:36.116444707 -0800 @@ -1,21 +1,21 @@ ECRIT R. Gellens Internet-Draft Qualcomm Technologies, Inc Intended status: Informational B. Rosen -Expires: May 8, 2016 NeuStar, Inc. +Expires: August 22, 2016 NeuStar, Inc. H. Tschofenig (Individual) - November 5, 2015 + February 19, 2016 Next-Generation Vehicle-Initiated Emergency Calls - draft-ietf-ecrit-car-crash-05.txt + draft-ietf-ecrit-car-crash-06.txt Abstract This document describes how to use IP-based emergency services mechanisms to support the next generation of emergency calls placed by vehicles (automatically in the event of a crash or serious incident, or manually invoked by a vehicle occupant) and conveying vehicle, sensor, and location data related to the crash or incident. Such calls are often referred to as "Automatic Crash Notification" (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the @@ -47,25 +47,25 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on May 8, 2016. + This Internet-Draft will expire on August 22, 2016. Copyright Notice - Copyright (c) 2015 IETF Trust and the persons identified as the + Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -86,30 +86,31 @@ 11. Security Considerations . . . . . . . . . . . . . . . . . . . 21 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 13.1. MIME Content-type Registration for 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 22 13.2. Registration of the 'VEDS' entry in the Emergency Call Additional Data registry . . . . . . . . . . . . . . . . 23 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 16. Changes from Previous Versions . . . . . . . . . . . . . . . 23 - 16.1. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 23 - 16.2. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 23 - 16.3. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 23 - 16.4. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 24 - 16.5. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 24 - 16.6. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 24 - 16.7. Changes from draft-gellens-01 to -02 . . . . . . . . . . 24 - 16.8. Changes from draft-gellens-00 to -01 . . . . . . . . . . 24 - 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 24 - 17.1. Normative References . . . . . . . . . . . . . . . . . . 24 + 16.1. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 23 + 16.2. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 24 + 16.3. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 24 + 16.4. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 24 + 16.5. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 24 + 16.6. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 24 + 16.7. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 24 + 16.8. Changes from draft-gellens-01 to -02 . . . . . . . . . . 24 + 16.9. Changes from draft-gellens-00 to -01 . . . . . . . . . . 25 + 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 + 17.1. Normative References . . . . . . . . . . . . . . . . . . 25 17.2. Informative references . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. This document re-uses terminology defined in Section 3 of [RFC5012]. @@ -408,20 +409,29 @@ generation (all-IP) technology provides a standardized mechanism to identify such calls and to present crash data with the call, as well as enabling additional communications modalities and enhanced functionality. This allows ACN calls and crash data to be automatically processed by the PSAP and made available to the call taker in an integrated, automated way. Because the crash data is carried in the initial SIP INVITE (per [I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call taker simultaneously with the appearance of the call. + Origination networks, PSAPs, emergency services networks, and other + telephony environments are all migrating to next-generation. This + provides opportunities for significant enhancement to + interoperability, especially for emergency calls carrying additional + data such as vehicle crash data. Note that in the U.S., a network + specifically for emergency responders is being developed. This + network, FirstNet, will be next-generation from the start, enhancing + the ability for data exchange between PSAPs and responders. + Migration to next-generation (NG) thus provides an opportunity to significantly improve the handling and response to vehicle-initiated emergency calls. Such calls can be recognized as originating from a vehicle, routed to a PSAP equipped both technically and operationally to handle such calls, and the vehicle-determined location and crash data can be made available to the call taker simultaneously with the call appearance. Vehicle manufacturers using the TSP model can choose to take advantage of the same mechanism to carry telematics data between the @@ -1005,33 +1015,43 @@ This content type is designed to carry vehicle crash data during an emergency call. This data can contain personal information including vehicle VIN, location, direction, etc. Appropriate precautions need to be taken to limit unauthorized access, inappropriate disclosure to third parties, and eavesdropping of this information. Please refer to Section 7 and Section 8 of [I-D.ietf-ecrit-additional-data] for more information. + When this content type is contained in a signed or encrypted + body part, the enclosing multipart (e.g., multipart/signed or + multipart/encrypted) has the same Content-ID as the data part. + This allows an entity to identify and access the data blocks it + is interested in without having to dive deeply into the message + structure or decrypt parts it is not interested in. (The + 'purpose' parameter in a Call-Info header field identifies the + data, and the CID URL points to the data block in the body, + which has a matching Content-ID body part header field). + Interoperability considerations: None Published specification: [VEDS] Applications which use this media type: Emergency Services - Additional information: None Magic Number: None File Extension: .xml Macintosh file type code: 'TEXT' + Person and email address for further information: Hannes Tschofenig, Hannes.Tschofenig@gmx.net Intended usage: LIMITED USE Author: This specification is a work item of the IETF ECRIT working group, with mailing list address . Change controller: The IESG @@ -1048,68 +1068,75 @@ We would like to thank Ulrich Dietz for his help with earlier versions of the original version of this document. 15. Acknowledgements We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, Wes George, and Gunnar Hellstrom for their feedback. 16. Changes from Previous Versions -16.1. Changes from draft-ietf-04 to draft-ietf-05 +16.1. Changes from draft-ietf-05 to draft-ietf-06 + + o Added clarifying text regarding signed and encrypted data + o Additional informative text in "Migration to Next-Generation" + section + o Additional clarifying text regarding security and privacy. + +16.2. Changes from draft-ietf-04 to draft-ietf-05 o Reworded security text in main document and in MIME registration for the VEDS object -16.2. Changes from draft-ietf-03 to draft-ietf-04 +16.3. Changes from draft-ietf-03 to draft-ietf-04 o Added example VEDS object o Additional clarifications and corrections o Removed references from Abstract o Moved Document Scope section to follow Introduction -16.3. Changes from draft-ietf-02 to draft-ietf-03 +16.4. Changes from draft-ietf-02 to draft-ietf-03 o Additional clarifications and corrections -16.4. Changes from draft-ietf-01 to draft-ietf-02 +16.5. Changes from draft-ietf-01 to draft-ietf-02 o This document now refers to [I-D.ietf-ecrit-ecall] for technical aspects including the service URN; this document no longer 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 and non-eCall o Added discussion of an NG-ACN call placed to a PSAP that doesn't support it o Minor wording improvements and clarifications -16.5. Changes from draft-ietf-00 to draft-ietf-01 +16.6. Changes from draft-ietf-00 to draft-ietf-01 o Added further discussion of test calls o Added further clarification to the document scope o Mentioned that multi-region vehicles may need to support other crash notification specifications such as eCall o Minor wording improvements and clarifications -16.6. Changes from draft-gellens-02 to draft-ietf-00 +16.7. Changes from draft-gellens-02 to draft-ietf-00 o Renamed from draft-gellens- to draft-ietf- 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 it -16.7. Changes from draft-gellens-01 to -02 +16.8. Changes from draft-gellens-01 to -02 o Fixed case of 'EmergencyCallData', in accordance with changes to [I-D.ietf-ecrit-additional-data] -16.8. Changes from draft-gellens-00 to -01 +16.9. Changes from draft-gellens-00 to -01 o Now using 'EmergencyCallData' for purpose parameter values and MIME subtypes, in accordance with changes to [I-D.ietf-ecrit-additional-data] o Added reference to RFC 6443 o Fixed bug that caused Figure captions to not appear 17. References 17.1. Normative References