< draft-ietf-ecrit-car-crash-04.txt   draft-ietf-ecrit-car-crash-05.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Qualcomm Technologies, Inc Internet-Draft Qualcomm Technologies, Inc
Intended status: Informational B. Rosen Intended status: Informational B. Rosen
Expires: April 20, 2016 NeuStar, Inc. Expires: May 8, 2016 NeuStar, Inc.
H. Tschofenig H. Tschofenig
(Individual) (Individual)
October 18, 2015 November 5, 2015
Next-Generation Vehicle-Initiated Emergency Calls Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-04.txt draft-ietf-ecrit-car-crash-05.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 12 skipping to change at page 2, line 12
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 20, 2016. This Internet-Draft will expire on May 8, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 45 skipping to change at page 2, line 45
5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9
6. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 6. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 12 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 12
8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15
9. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 16
10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
11. Security Considerations . . . . . . . . . . . . . . . . . . . 21 11. Security Considerations . . . . . . . . . . . . . . . . . . . 21
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
13.1. MIME Content-type Registration for 13.1. MIME Content-type Registration for
'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 21 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 22
13.2. Registration of the 'VEDS' entry in the Emergency Call 13.2. Registration of the 'VEDS' entry in the Emergency Call
Additional Data registry . . . . . . . . . . . . . . . . 22 Additional Data registry . . . . . . . . . . . . . . . . 23
14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23
15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23
16. Changes from Previous Versions . . . . . . . . . . . . . . . 23 16. Changes from Previous Versions . . . . . . . . . . . . . . . 23
16.1. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 23 16.1. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 23
16.2. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 23 16.2. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 23
16.3. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 23 16.3. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 23
16.4. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 23 16.4. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 24
16.5. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 23 16.5. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 24
16.6. Changes from draft-gellens-01 to -02 . . . . . . . . . . 24 16.6. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 24
16.7. Changes from draft-gellens-00 to -01 . . . . . . . . . . 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 24
17.1. Normative References . . . . . . . . . . . . . . . . . . 24 17.1. Normative References . . . . . . . . . . . . . . . . . . 24
17.2. Informative references . . . . . . . . . . . . . . . . . 25 17.2. Informative references . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
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 21, line 17 skipping to change at page 21, line 17
<VehicleFireIndicator>false</VehicleFireIndicator> <VehicleFireIndicator>false</VehicleFireIndicator>
</Crash> </Crash>
</AutomatedCrashNotification> </AutomatedCrashNotification>
--boundary1-- --boundary1--
Figure 8: SIP INVITE indicating a Vehicule-Initated Emergency Call Figure 8: SIP INVITE indicating a Vehicule-Initated Emergency Call
11. Security Considerations 11. Security Considerations
This document does not raise security considerations beyond those Since this document relies on [I-D.ietf-ecrit-ecall] and
described in [RFC5069]. As with emergency service systems with end [I-D.ietf-ecrit-additional-data], the security considerations
host provided location information there is the possibility that that described there and in [RFC5069] apply here. Implementors are
location is incorrect, either intentially (in case of an a denial of strongly cautioned to read and understand the discussion in those
service attack against the emergency services infrastructure) or due documents.
to a malfunctioning device. The reader is referred to [RFC7378] for
a discussion of some of these vulnerabilities. As with emergency service systems where location data is supplied or
determined with the assistance of an end host, there is the
possibility that that location is incorrect, either intentially (in
case of an a denial of service attack against the emergency services
infrastructure) or due to a malfunctioning device. The reader is
referred to [RFC7378] for a discussion of some of these
vulnerabilities.
12. Privacy Considerations 12. 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 [I-D.ietf-ecrit-additional-data], the data structures builds on [I-D.ietf-ecrit-additional-data], the data structures
specified there, and the corresponding privacy considerations specified there, and the corresponding privacy considerations
discussed there, apply here as well. The VEDS data structure discussed there, apply here as well. The VEDS data structure
contains optional elements that can carry identifying and personal contains optional elements that can carry identifying and personal
information, both about the vehicle and about the owner, as well as information, both about the vehicle and about the owner, as well as
location information, and so needs to be protected against location information, and so needs to be protected against
unauthorized disclosure. Local regulations may impose additional unauthorized disclosure, as discussed in
privacy protection requirements. [I-D.ietf-ecrit-additional-data]. Local regulations may impose
additional privacy protection requirements.
13. IANA Considerations 13. IANA Considerations
13.1. MIME Content-type Registration for 'application/ 13.1. MIME Content-type Registration for 'application/
EmergencyCall.VEDS+xml' EmergencyCall.VEDS+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
skipping to change at page 22, line 4 skipping to change at page 22, line 16
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.VEDS+xml MIME subtype name: EmergencyCallData.VEDS+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
Security considerations: This content type is designed to carry Security considerations:
vehicle crash data during an emergency call. This data can
contain personal information including vehicle VIN, location, This content type is designed to carry vehicle crash data
direction, etc. Appropriate precautions need to be taken to limit during an emergency call.
unauthorized access, inappropriate disclosure to third parties,
and eavesdropping of this information. Please refer to Section 7 This data can contain personal information including vehicle
and Section 8 of [I-D.ietf-ecrit-additional-data] for more VIN, location, direction, etc. Appropriate precautions need to
information. 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.
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
skipping to change at page 23, line 13 skipping to change at page 23, line 30
established by [I-D.ietf-ecrit-additional-data]. established by [I-D.ietf-ecrit-additional-data].
14. Contributors 14. Contributors
We would like to thank Ulrich Dietz for his help with earlier We would like to thank Ulrich Dietz for his help with earlier
versions of the original version of this document. versions of the original version of this document.
15. Acknowledgements 15. Acknowledgements
We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri,
and Gunnar Hellstrom for their feedback. Wes George, and Gunnar Hellstrom for their feedback.
16. Changes from Previous Versions 16. Changes from Previous Versions
16.1. Changes from draft-ietf-03 to draft-ietf-04 16.1. 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
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
16.2. Changes from draft-ietf-02 to draft-ietf-03 16.3. Changes from draft-ietf-02 to draft-ietf-03
o Additional clarifications and corrections o Additional clarifications and corrections
16.3. Changes from draft-ietf-01 to draft-ietf-02 16.4. 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
16.4. Changes from draft-ietf-00 to draft-ietf-01 16.5. 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
16.5. Changes from draft-gellens-02 to draft-ietf-00 16.6. 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
16.6. Changes from draft-gellens-01 to -02 16.7. 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
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
16.7. Changes from draft-gellens-00 to -01 16.8. 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 MIME subtypes, in accordance with changes to
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
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
17. References 17. References
17.1. Normative References 17.1. Normative References
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
J. Winterbottom, "Additional Data Related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", draft-ietf-ecrit-additional-data-37 (work in Call", draft-ietf-ecrit-additional-data-37 (work in
progress), October 2015. progress), October 2015.
[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 (work in European eCall", draft-ietf-ecrit-ecall-03 (work in
progress), March 2015. progress), July 2015.
[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, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
<http://www.rfc-editor.org/info/rfc3023>. <http://www.rfc-editor.org/info/rfc3023>.
 End of changes. 22 change blocks. 
42 lines changed or deleted 58 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/