Next-Generation Vehicle-Initiated Emergency Calls
draft-ietf-ecrit-car-crash-05
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8148.
|
|
---|---|---|---|
Authors | Randall Gellens , Brian Rosen , Hannes Tschofenig | ||
Last updated | 2015-11-05 | ||
Replaces | draft-gellens-ecrit-car-crash | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews |
GENART Last Call review
(of
-20)
by Dan Romascanu
Almost ready
|
||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 8148 (Proposed Standard) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-ietf-ecrit-car-crash-05
gt; <dyn:heading>278</dyn:heading> <dyn:direction><dyn:direction> </dyn:Dynamic> </gp:location-info> <gp:usage-rules/> <method>gps</method> </gp:geopriv> <timestamp>2012-04-5T10:18:29Z</timestamp> <dm:deviceID>1M8GDM9A_KP042788</dm:deviceID> </dm:device> </presence> --boundary1 Content-Type: application/EmergencyCallData.VEDS+xml Content-ID: 1234567890@atlanta.example.com Content-Disposition: by-reference;handling=optional <?xml version="1.0" encoding="UTF-8"?> <AutomatedCrashNotification xmlns="http://www.veds.org/acn/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" <Crash> <CrashVehicle> <ItemMakeName xmlns="http://niem.gov/niem/niem-core/2.0"> Saab </ItemMakeName> <ItemModelName xmlns="http://niem.gov/niem/niem-core/2.0"> 9-5 </ItemModelName> <ItemModelYearDate xmlns="http://niem.gov/niem/niem-core/2.0"> 2015 </ItemModelYearDate> <Airbag> <AirbagCategoryCode>FRONT</AirbagCategoryCode> <AirbagDeployedIndicator>true </AirbagDeployedIndicator> Gellens, et al. Expires May 8, 2016 [Page 19] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 </Airbag> <ConvertibleIndicator>false</ConvertibleIndicator> <PowerSourceCategoryCode>MAIN</PowerSourceCategoryCode> <VehicleBodyCategoryCode xmlns="http://niem.gov/niem/domains/jxdm/4.1"> 101 </VehicleBodyCategoryCode> <VehicleCrashPulse> <CrashPulseChangeInVelocityMeasure> <MeasurePointValue xmlns="http://niem.gov/niem/niem-core/2.0"> 100 </MeasurePointValue> <MeasureUnitText xmlns="http://niem.gov/niem/niem-core/2.0"> MPH</MeasureUnitText> </CrashPulseChangeInVelocityMeasure> <CrashPulsePrincipalDirectionOfForceValue>12 </CrashPulsePrincipalDirectionOfForceValue> <CrashPulseRolloverQuarterTurnsValue>1 </CrashPulseRolloverQuarterTurnsValue> </VehicleCrashPulse> <VehicleRollbarDeployedIndicator>false </VehicleRollbarDeployedIndicator> <VehicleSeat> <VehicleSeatLocationCategoryCode>1 </VehicleSeatLocationCategoryCode> <VehicleSeatOccupiedIndicator>true </VehicleSeatOccupiedIndicator> <VehicleSeatbeltFastenedIndicator>true </VehicleSeatbeltFastenedIndicator> <VehicleSeatbeltMonitoredIndicator>true </VehicleSeatbeltMonitoredIndicator> </VehicleSeat> <VehicleUnladenWeightMeasure xmlns="http://niem.gov/niem/niem-core/2.0"> <MeasurePointValue xmlns="http://niem.gov/niem/niem-core/2.0"> 600 </MeasurePointValue> <MeasureUnitText xmlns="http://niem.gov/niem/niem-core/2.0"> kilogram </MeasureUnitText> </VehicleUnladenWeightMeasure> </CrashVehicle> <FuelLeakingIndicator>true</FuelLeakingIndicator> <MultipleImpactsIndicator>false</MultipleImpactsIndicator> Gellens, et al. Expires May 8, 2016 [Page 20] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 <SevereInjuryIndicator>true</SevereInjuryIndicator> <VehicleFinalRestOrientationCategoryCode>Driver </VehicleFinalRestOrientationCategoryCode> <VehicleFireIndicator>false</VehicleFireIndicator> </Crash> </AutomatedCrashNotification> --boundary1-- Figure 8: SIP INVITE indicating a Vehicule-Initated Emergency Call 11. Security Considerations Since this document relies on [I-D.ietf-ecrit-ecall] and [I-D.ietf-ecrit-additional-data], the security considerations described there and in [RFC5069] apply here. Implementors are strongly cautioned to read and understand the discussion in those documents. 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 Since this document builds on [I-D.ietf-ecrit-ecall], which itself builds on [I-D.ietf-ecrit-additional-data], the data structures specified there, and the corresponding privacy considerations discussed there, apply here as well. The VEDS data structure contains optional elements that can carry identifying and personal information, both about the vehicle and about the owner, as well as location information, and so needs to be protected against unauthorized disclosure, as discussed in [I-D.ietf-ecrit-additional-data]. Local regulations may impose additional privacy protection requirements. 13. IANA Considerations Gellens, et al. Expires May 8, 2016 [Page 21] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 13.1. MIME Content-type Registration for 'application/ EmergencyCall.VEDS+xml' This specification requests the registration of a new MIME type according to the procedures of RFC 4288 [RFC4288] and guidelines in RFC 3023 [RFC3023]. MIME media type name: application MIME subtype name: EmergencyCallData.VEDS+xml Mandatory parameters: none Optional parameters: charset Indicates the character encoding of enclosed XML. Encoding considerations: Uses XML, which can employ 8-bit characters, depending on the character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. Security considerations: 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. 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' Gellens, et al. Expires May 8, 2016 [Page 22] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 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 <ecrit@ietf.org>. Change controller: The IESG <ietf@ietf.org> 13.2. Registration of the 'VEDS' entry in the Emergency Call Additional Data registry This specification requests IANA to add the 'VEDS' entry to the Emergency Call Additional Data registry, with a reference to this document. The Emergency Call Additional Data registry has been established by [I-D.ietf-ecrit-additional-data]. 14. Contributors 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 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 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 o Additional clarifications and corrections Gellens, et al. Expires May 8, 2016 [Page 23] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 16.4. 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 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 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 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 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 [I-D.ietf-ecrit-additional-data] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and J. Winterbottom, "Additional Data Related to an Emergency Call", draft-ietf-ecrit-additional-data-37 (work in progress), October 2015. Gellens, et al. Expires May 8, 2016 [Page 24] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 [I-D.ietf-ecrit-ecall] Gellens, R. and H. Tschofenig, "Next-Generation Pan- European eCall", draft-ietf-ecrit-ecall-03 (work in progress), July 2015. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, <http://www.rfc-editor.org/info/rfc3023>. [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, <http://www.rfc-editor.org/info/rfc4119>. [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, December 2005, <http://www.rfc-editor.org/info/rfc4288>. [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services", RFC 5031, DOI 10.17487/RFC5031, January 2008, <http://www.rfc-editor.org/info/rfc5031>. [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations", RFC 5491, DOI 10.17487/RFC5491, March 2009, <http://www.rfc-editor.org/info/rfc5491>. [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. Thomson, "Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)", RFC 5962, DOI 10.17487/RFC5962, September 2010, <http://www.rfc-editor.org/info/rfc5962>. [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, "Framework for Emergency Calling Using Internet Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 2011, <http://www.rfc-editor.org/info/rfc6443>. [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for Communications Services in Support of Emergency Calling", BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, <http://www.rfc-editor.org/info/rfc6881>. Gellens, et al. Expires May 8, 2016 [Page 25] Internet-Draft Vehicle-Initiated Emergency Calls November 2015 [VEDS] "Vehicular Emergency Data Set (VEDS) version 3", July 2012, <https://www.apcointl.org/resources/telematics/aacn- and-veds.html>. 17.2. Informative references [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for Emergency Context Resolution with Internet Technologies", RFC 5012, DOI 10.17487/RFC5012, January 2008, <http://www.rfc-editor.org/info/rfc5012>. [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. Shanmugam, "Security Threats and Requirements for Emergency Call Marking and Mapping", RFC 5069, DOI 10.17487/RFC5069, January 2008, <http://www.rfc-editor.org/info/rfc5069>. [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, December 2014, <http://www.rfc-editor.org/info/rfc7378>. Authors' Addresses Randall Gellens Qualcomm Technologies, Inc 5775 Morehouse Drive San Diego 92651 US Email: rg+ietf@randy.pensive.org Brian Rosen NeuStar, Inc. 470 Conrad Dr Mars, PA 16046 US Email: br@brianrosen.net Hannes Tschofenig (Individual) Email: Hannes.Tschofenig@gmx.net URI: http://www.tschofenig.priv.at Gellens, et al. Expires May 8, 2016 [Page 26]