idnits 2.17.1 draft-ietf-ecrit-car-crash-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 19, 2016) is 2986 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5031' is defined on line 1172, but no explicit reference was found in the text == Outdated reference: A later version (-38) exists of draft-ietf-ecrit-additional-data-37 == Outdated reference: A later version (-27) exists of draft-ietf-ecrit-ecall-03 ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Downref: Normative reference to an Informational RFC: RFC 6443 -- Possible downref: Non-RFC (?) normative reference: ref. 'VEDS' Summary: 3 errors (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Qualcomm Technologies, Inc 4 Intended status: Standards Track B. Rosen 5 Expires: August 22, 2016 NeuStar, Inc. 6 H. Tschofenig 7 (Individual) 8 February 19, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-07.txt 13 Abstract 15 This document describes how to use IP-based emergency services 16 mechanisms to support the next generation of emergency calls placed 17 by vehicles (automatically in the event of a crash or serious 18 incident, or manually invoked by a vehicle occupant) and conveying 19 vehicle, sensor, and location data related to the crash or incident. 20 Such calls are often referred to as "Automatic Crash Notification" 21 (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the 22 case of manual trigger. The "Advanced" qualifier refers to the 23 ability to carry a richer set of data. 25 This document also registers a MIME Content Type and an Emergency 26 Call Additional Data Block for the vehicle, sensor, and location data 27 (often referred to as "crash data" even though there is not 28 necessarily a crash). An external specification for the data format, 29 contents, and structure are referenced in this document. 31 This document reuses the technical aspects of next-generation pan- 32 European eCall (a mandated and standardized system for emergency 33 calls by in-vehicle systems within Europe and other regions). 34 However, this document specifies a different set of vehicle (crash) 35 data, specifically, the Vehicle Emergency Data Set (VEDS) rather than 36 the eCall Minimum Set of Data (MSD). This document is an extension 37 of the eCall document, with the differences being that this document 38 makes the MSD data set optional and VEDS mandatory. This document 39 also discusses legacy (curcuit-switched) ACN systems and their 40 migration to next-generation emergency calling. 42 Status of This Memo 44 This Internet-Draft is submitted in full conformance with the 45 provisions of BCP 78 and BCP 79. 47 Internet-Drafts are working documents of the Internet Engineering 48 Task Force (IETF). Note that other groups may also distribute 49 working documents as Internet-Drafts. The list of current Internet- 50 Drafts is at http://datatracker.ietf.org/drafts/current/. 52 Internet-Drafts are draft documents valid for a maximum of six months 53 and may be updated, replaced, or obsoleted by other documents at any 54 time. It is inappropriate to use Internet-Drafts as reference 55 material or to cite them other than as "work in progress." 57 This Internet-Draft will expire on August 22, 2016. 59 Copyright Notice 61 Copyright (c) 2016 IETF Trust and the persons identified as the 62 document authors. All rights reserved. 64 This document is subject to BCP 78 and the IETF Trust's Legal 65 Provisions Relating to IETF Documents 66 (http://trustee.ietf.org/license-info) in effect on the date of 67 publication of this document. Please review these documents 68 carefully, as they describe your rights and restrictions with respect 69 to this document. Code Components extracted from this document must 70 include Simplified BSD License text as described in Section 4.e of 71 the Trust Legal Provisions and are provided without warranty as 72 described in the Simplified BSD License. 74 Table of Contents 76 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 77 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 78 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 79 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 80 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 81 6. Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 82 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 12 83 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15 84 9. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 16 85 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 86 11. Security Considerations . . . . . . . . . . . . . . . . . . . 21 87 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21 88 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 89 13.1. MIME Content-type Registration for 90 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 22 91 13.2. Registration of the 'VEDS' entry in the Emergency Call 92 Additional Data registry . . . . . . . . . . . . . . . . 23 93 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 94 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 95 16. Changes from Previous Versions . . . . . . . . . . . . . . . 23 96 16.1. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 23 97 16.2. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 24 98 16.3. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 24 99 16.4. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 24 100 16.5. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 24 101 16.6. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 24 102 16.7. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 24 103 16.8. Changes from draft-gellens-01 to -02 . . . . . . . . . . 24 104 16.9. Changes from draft-gellens-00 to -01 . . . . . . . . . . 25 105 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 106 17.1. Normative References . . . . . . . . . . . . . . . . . . 25 107 17.2. Informative references . . . . . . . . . . . . . . . . . 26 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 110 1. Terminology 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in [RFC2119]. 116 This document re-uses terminology defined in Section 3 of [RFC5012]. 118 Additionally, we use the following abbreviations: 120 +--------+----------------------------------------------------------+ 121 | Term | Expansion | 122 +--------+----------------------------------------------------------+ 123 | 3GPP | 3rd Generation Partnership Project | 124 | AACN | Advanced Automatic Crash Notification | 125 | ACN | Automatic Crash Notification | 126 | APCO | Association of Public-Safety Communications Officials | 127 | EENA | European Emergency Number Association | 128 | ESInet | Emergency Services IP network | 129 | GNSS | Global Satellite Navigation System (which includes the | 130 | | various such systems including the Global Positioning | 131 | | System or GPS) | 132 | IVS | In-Vehicle System | 133 | MNO | Mobile Network Operator | 134 | NENA | National Emergency Number Association | 135 | TSP | Telematics Service Provider | 136 | VEDS | Vehicle Emergency Data Set | 137 +--------+----------------------------------------------------------+ 139 2. Introduction 141 Emergency calls made by in-vehicle systems (e.g., in the event of a 142 crash) assist in significantly reducing road deaths and injuries by 143 allowing emergency services to respond quickly and often with better 144 location. 146 Drivers often have a poor location awareness, especially outside of 147 major cities, at night and when away from home (especially abroad). 148 In the most crucial cases, the victim(s) might not be able to call 149 because they have been injured or trapped. 151 For more than a decade, some vehicles have been equipped with 152 telematics systems that, among other features, place an emergency 153 call automatically in the event of a crash or manually in response to 154 an emergency call button. Such systems generally have on-board 155 location determination systems that make use of satellite-based 156 positioning technology, inertial sensors, gyroscopes, etc., to 157 provide a fairly accurate position for the vehicle. Such built-in 158 systems can take advantage of the benefits of being integrated into a 159 vehicle, such as more reliable power, ability to have larger or 160 specialized antenna, ability to be engineered to avoid or minimise 161 degradation by vehicle glass coatings, interference from other 162 vehicle systems, etc. Thus, the PSAP can be provided with a good 163 estimate of where the vehicle is during an emergency. Vehicle 164 manufacturers are increasingly adopting such systems, both for the 165 safety benefits and for the additional features and services they 166 enable (e.g., remote engine diagnostics, remote door unlock, stolen 167 vehicle tracking and disabling, etc.). 169 The general term for such systems is Automatic Crash Notification 170 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 171 used in this document as a general term. ACN systems transmit some 172 amount of data specific to the incident, referred to generally as 173 "crash data" (the term is commonly used even though there might not 174 have been a crash). While different systems transmit different 175 amounts of crash data, standardized formats, structures, and 176 mechanisms are needed to provide interoperability among systems and 177 PSAPs. 179 As of the date of this document, currently deployed in-vehicle 180 telematics systems are circuit-switched and lack a standards-based 181 ability to convey crash data directly to the PSAP (generally relying 182 on either a human call taker or an automated system to provide the 183 PSAP call taker with some crash data orally, or possibly a 184 proprietary mechanism). The PSAP call taker needs to first realize 185 that the call is related to a vehicle incident, and in most cases 186 must then listen to the data and transcribe it. 188 The transition to next-generation calling in general, and emergency 189 calling in particular, provides an opportunity to vastly improve the 190 scope, breadth, reliability and usefulness of crash data during an 191 emergency by allowing it to be presented alongside the call, and to 192 be automatically processed by the PSAP and made available to the call 193 taker in an integrated, automated way. In addition, vehicle 194 manufacturers are provided an opportunity to take advantage of the 195 same standardized mechanisms for data transmission for internal use 196 if they wish (such as telemetry between the vehicle and a service 197 center for both emergency and non-emergency uses, including location- 198 based services, multi-media entertainment systems, and road-side 199 assistance applications). 201 Next-generation ACN provides an opportunity for such calls to be 202 recognized and processed as such during call set-up, and optionally 203 routed to an upgraded PSAP where the vehicle data is available to 204 assist the call taker in assessing and responding to the situation. 206 An ACN call can be either occupant-initiated or automatically 207 triggered. (The "A" in "ACN" does stand for "Automatic," but the 208 term is often used to refer to the class of calls that are placed by 209 an in-vehicle system (IVS) and that carry incident-related data as 210 well as voice.) Automatically triggered calls indicate a car crash 211 or some other serious incident (e.g., a fire) and carry a greater 212 presumption of risk of injury. Manually triggered calls are often 213 reports of serious hazards (such as impaired drivers or roadway 214 debris) and might require different responses depending on the 215 situation. Manually triggered calls are also more likely to be false 216 (e.g., accidental) calls and so might be subject to different 217 operational handling by the PSAP. 219 This document describes how the IETF mechanisms for IP-based 220 emergency calls, including [RFC6443] and 221 [I-D.ietf-ecrit-additional-data], are used to provide the realization 222 of next-generation ACN. 224 This document reuses the technical aspects of next-generation pan- 225 European eCall (a mandated and standardized system for emergency 226 calls by in-vehicle systems within Europe and other regions), as 227 described in [I-D.ietf-ecrit-ecall]. However, this document 228 specifies a different set of vehicle (crash) data, specifically, the 229 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 230 of Data (MSD). This document is an extension of 231 [I-D.ietf-ecrit-ecall], with the differences being that this document 232 makes the MSD data set optional and VEDS mandatory. 234 The Association of Public-Safety Communications Officials (APCO) and 235 the National Emergency Number Association (NENA) have jointly 236 developed a standardized set of incident-related vehicle data for ACN 237 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 238 is often referred to as crash data although it is applicable in 239 incidents other than crashes. 241 VEDS provides a standard data set for the transmission, exchange, and 242 interpretation of vehicle-related data. A standard data format 243 allows the data to be generated by an IVS, and interpreted by PSAPs, 244 emergency responders, and medical facilities (including those capable 245 of providing trauma level patient care). It includes incident- 246 related information such as airbag deployment, location of the 247 vehicle, if the vehicle was involved in a rollover, various sensor 248 data that can indicate the potential severity of the crash and the 249 likelihood of severe injuries to the vehicle occupants, etc. This 250 data better informs the PSAP and emergency responders as to the type 251 of response that might be needed. This information was recently 252 included in the federal guidelines for field triage of injured 253 patients. These guidelines are designed to help responders at the 254 accident scene identify the potential existence of severe internal 255 injuries and to make critical decisions about how and where a patient 256 needs to be transported. 258 This document registers the 'application/EmergencyCallData.VEDS+xml' 259 MIME content-type, and registers the 'VEDS' entry in the Emergency 260 Call Additional Data registry. 262 VEDS is an XML structure (see [VEDS]). The 'application/ 263 EmergencyCallData.VEDS+xml' MIME content-type is used to identify it. 264 The 'VEDS' entry in the Emergency Call Additional Data registry is 265 used to construct a 'purpose' parameter value for conveying VEDS data 266 in a Call-Info header (as described in 267 [I-D.ietf-ecrit-additional-data]). 269 VEDS is a versatile structure that can accomodate varied needs. 270 However, if additional sets of data are determined to be needed 271 (e.g., in the future or in different regions), the steps to enable 272 each data block are very briefly summarized below: 274 o A standardized format and encoding (such as XML) is defined and 275 published by a Standards Development Organization (SDO) 277 o A MIME Content-Type is registered for it (typically under the 278 'Application' media type) with a sub-type starting with 279 'EmergencyCallData.' 281 o An entry for the block is added to the Emergency Call Additional 282 Data Blocks sub-registry (established by 283 [I-D.ietf-ecrit-additional-data]); the registry entry is the root 284 of the MIME sub-type (not including the 'EmergencyCallData' prefix 285 and any suffix such as '+xml') 287 A next-generation In-Vehicle System (IVS) transmits crash data by 288 encoding it in a standardized and registered format (such as VEDS) 289 and attaching it to an INVITE as a MIME body part. The body part is 290 identified by its MIME content-type (such as 'application/ 291 EmergencyCallData.VEDS+xml') in the Content-Type header field of the 292 body part. The body part is assigned a unique identifier which is 293 listed in a Content-ID header field in the body part. The INVITE is 294 marked as containing the crash data by adding a Call-Info header 295 field at the top level of the INVITE. This Call-Info header field 296 contains a CID URL referencing the body part's unique identifier, and 297 a 'purpose' parameter identifying the data as the crash data per the 298 registry entry; the 'purpose' parameter's value is 299 'EmergencyCallData.' and the root of the MIME type (the 300 'EmergencyCallData' prefix is not repeated), omitting any suffix such 301 as '+xml' (e.g., 'purpose=EmergencyCallData.VEDS'). 303 These mechanisms are thus used to place emergency calls that are 304 identifiable as ACN calls and that carry one or more standardized 305 crash data objects in an interoperable way. 307 3. Document Scope 309 This document is focused on the interface to the PSAP, that is, how 310 an ACN emergency call is setup and incident-related data (including 311 vehicle, sensor, and location data) is transmitted to the PSAP using 312 IETF specifications. (The goal is to re-use specifications rather 313 than to invent new.) For the direct model, this is the end-to-end 314 description (between the vehicle and the PSAP). For the TSP model, 315 this describes the right-hand side (between the TSP and the PSAP), 316 leaving the left-hand side (between the vehicle and the TSP) up to 317 the entities involved (i.e., IVS and TSP vendors) who are then free 318 to use the same mechanism as for the right-hand side (or not). 320 Note that while ACN systems in the U.S. and other regions are not 321 currently (as of the date of this document) mandated, Europe has a 322 mandated and standardized system for emergency calls by in-vehicle 323 systems. This pan-European system is known as "eCall" and is the 324 subject of a separate document, [I-D.ietf-ecrit-ecall], which this 325 document build on. Vehicles designed to operate in multiple regions 326 might need to support eCall as well as the ACN described here. If 327 other regions devise their own specifications or data formats, a 328 multi-region vehicle might need to support those as well. This 329 document adopts the call set-up and other technical aspects of 330 [I-D.ietf-ecrit-ecall], which uses [I-D.ietf-ecrit-additional-data], 331 which makes it easy to substitute a different data set while keeping 332 other technical aspects unchanged. Hence, both NG-eCall and the NG- 333 ACN mechanism described here are fully compatible, differing only in 334 the specific data block that is sent (the eCall MSD in the case of 335 NG-eCall, and the APCO/NENA VEDS used in this document). If other 336 regions adopt their own data set, this can be similarly accomodated 337 without changing other technical aspects. 339 4. Overview of Legacy Deployment Models 341 Legacy (circuit-switched) systems for placing emergency calls by in- 342 vehicle systems, including automatic crash notification systems, 343 generally have some ability to convey at least location and in some 344 cases telematics data to the PSAP. Most such systems use one of 345 three architectural models, which are described here as: "Telematics 346 Service Provider" (TSP), "direct", and "paired". These three models 347 are illustrated below. 349 In the TSP model, both emergency and non-emergency calls are placed 350 to a Telematics Service Provider (TSP); a proprietary technique is 351 used for data transfer (such as proprietary in-band modems) to the 352 TSP. 354 In an emergency, the TSP call taker bridges in the PSAP and 355 communicates location, crash data (such as impact severity and trauma 356 prediction), and other data (such as the vehicle description) to the 357 PSAP call taker verbally. Since the TSP knows the location of the 358 vehicle (from on-board GNSS), location-based routing is usually used 359 to route to the appropriate PSAP. In some cases, the TSP is able to 360 transmit location automatically, using similar techniques as for 361 wireless calls. Typically, a three-way voice call is established 362 between the vehicle, the TSP, and the PSAP, allowing communication 363 between the PSAP call taker, the TSP call taker, and the vehicle 364 occupants (who might be unconscious). 366 ///----\\\ proprietary +------+ 911 trunk +------+ 367 ||| IVS |||-------------->+ TSP +------------------>+ PSAP | 368 \\\----/// crash data +------+ +------+ 370 Figure 1: Legacy TSP Model. 372 In the paired model, the IVS uses a Bluetooth link with a previously- 373 paired handset to establish an emergency call with the PSAP (by 374 dialing a standard emergency number such as 9-1-1), and then 375 communicates location data to the PSAP via text-to-speech; crash data 376 might or might not be conveyed also using text-to-speech in an 377 initial voice greeting. Some such systems use an automated voice 378 prompt menu for the PSAP call taker (e.g., "this is an automatic 379 emergency call from a vehicle; press 1 to open a voice path to the 380 vehicle; press 2 to hear the location read out") to allow the call 381 taker to request location data via text-to-speech. 383 +---+ 384 ///----\\\ | H | 911/etc voice call via handset +------+ 385 ||| IVS |||-->| S +----------------------------------->+ PSAP | 386 \\\----/// +---+ location via text-to-speech +------+ 388 Figure 2: Legacy Paired Model 390 In the direct model, the IVS directly places an emergency call with 391 the PSAP by dialing a standard emergency number such as 9-1-1. Such 392 systems might communicate location data to the PSAP via text-to- 393 speech; crash data might or might not be conveyed using text-to- 394 speech in an initial voice greeting. Some such systems use an 395 automated voice prompt menu (e.g., "this is an automatic emergency 396 call from a vehicle; press 1 to open a voice path to the vehicle; 397 press 2 to hear the location read out") to allow the call taker to 398 request location data via text-to-speech. 400 ///----\\\ 911/etc voice call via IVS +------+ 401 ||| IVS |||---------------------------------------->+ PSAP | 402 \\\----/// location via text-to-speech +------+ 404 Figure 3: Legacy Direct Model 406 5. Migration to Next-Generation 408 Migration of emergency calls placed by in-vehicle systems to next- 409 generation (all-IP) technology provides a standardized mechanism to 410 identify such calls and to present crash data with the call, as well 411 as enabling additional communications modalities and enhanced 412 functionality. This allows ACN calls and crash data to be 413 automatically processed by the PSAP and made available to the call 414 taker in an integrated, automated way. Because the crash data is 415 carried in the initial SIP INVITE (per 416 [I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call 417 taker simultaneously with the appearance of the call. 419 Origination networks, PSAPs, emergency services networks, and other 420 telephony environments are all migrating to next-generation. This 421 provides opportunities for significant enhancement to 422 interoperability, especially for emergency calls carrying additional 423 data such as vehicle crash data. Note that in the U.S., a network 424 specifically for emergency responders is being developed. This 425 network, FirstNet, will be next-generation from the start, enhancing 426 the ability for data exchange between PSAPs and responders. 428 Migration to next-generation (NG) thus provides an opportunity to 429 significantly improve the handling and response to vehicle-initiated 430 emergency calls. Such calls can be recognized as originating from a 431 vehicle, routed to a PSAP equipped both technically and operationally 432 to handle such calls, and the vehicle-determined location and crash 433 data can be made available to the call taker simultaneously with the 434 call appearance. 436 Vehicle manufacturers using the TSP model can choose to take 437 advantage of the same mechanism to carry telematics data between the 438 vehicle and the TSP for both emergency and non-emergency calls as are 439 used to convey this data to the PSAP. 441 A next-generation IVS establishes an emergency call using the 442 emergency call solution as described in [RFC6443] and [RFC6881], with 443 the difference that the Request-URI indicates an ACN type of 444 emergency call and a Call-Info header field indicates that vehicle 445 crash data is attached. When an ESInet is deployed, the MNO only 446 needs to recognize the call as an emergency call and route it to an 447 ESInet. The ESInet can recognize the call as an ACN with vehicle 448 data and can route the call to an NG-ACN capable PSAP. Such a PSAP 449 can interpret the vehicle data sent with the call and make it 450 available to the call taker. 452 Because of the need to identify and specially process Next-Generation 453 ACN calls (as discussed above), [I-D.ietf-ecrit-ecall] registers new 454 service URN children within the "sos" subservice. These URNs provide 455 a mechanism by which an NG-ACN call is identified, and differentiate 456 between manually and automatically triggered NG-ACN calls, which 457 might be subject to different treatment depending on policy. (The 458 two service URNs registered in [I-D.ietf-ecrit-ecall] are 459 urn:service:sos.ecall.automatic and urn:service:sos.ecall.manual.) 461 Note that in North America, routing queries performed by clients 462 outside of an ESInet typically treat all sub-services of "sos" 463 identically to "sos" with no sub-service. However, the Request-URI 464 header field retains the full sub-service; route and handling 465 decisions within an ESInet or PSAP can take the sub-service into 466 account. For example, in a region with multiple cooperating PSAPs, 467 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 468 one that specializes in vehicle-related incidents. 470 Migration of the three architectural models to next-generation (all- 471 IP) is described below. 473 In the TSP model, the IVS transmits crash and location data to the 474 TSP using either a protocol that is based on a proprietary design or 475 one that re-uses the mechanisms and data objects described here. In 476 an emergency, the TSP call taker bridges in the PSAP and the TSP 477 transmits crash and other data to the PSAP using the mechanisms and 478 data objects described here. There is a three-way call between the 479 vehicle, the TSP, and the PSAP, allowing communication between the 480 PSAP call taker, the TSP call taker, and the vehicle occupants (who 481 might be unconscious). 483 proprietary 484 ///----\\\ or standard +------+ standard +------+ 485 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 486 \\\----/// crash + other data +------+ crash + other data +------+ 488 Figure 4: Next-Generation TSP Model 490 The vehicle manufacturer and the TSP can choose to use the same 491 mechanisms and data objects to transmit crash and location data from 492 the vehicle to the TSP as are described here to transmit such data 493 from to the PSAP. 495 In the direct model, the IVS communicates crash data to the PSAP 496 directly using the mechanisms and data objects described here. 498 ///----\\\ NG emergency call +------+ 499 ||| IVS |||----------------------------------------->+ PSAP | 500 \\\----/// crash + other data +------+ 502 Figure 5: Next-Generation Direct Model 504 In the paired model, the IVS uses a Bluetooth link to a previously- 505 paired handset to establish an emergency call with the PSAP; it is 506 undefined what facilities are or will be available for transmitting 507 crash data through the Bluetooth link to the handset for inclusion in 508 an NG emergency call. Hence, manufacturers that use the paired model 509 for legacy calls might choose to adopt either the direct or TSP 510 models for next-generation calls. 512 +---+ 513 ///----\\\ (undefined) | H | standard +------+ 514 ||| IVS |||------------------>| S +------------------->+ PSAP | 515 \\\----/// (undefined) +---+ crash + other data +------+ 517 Figure 6: Next-Generation Paired Model 519 If the call is routed to a PSAP that is not capable of processing the 520 vehicle data, the PSAP ignores (or does not receive) the vehicle 521 data. This is detectable by the IVS or TSP when it receives a 200 OK 522 to the INVITE which lacks an eCall control structure acknowledging 523 receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then 524 proceeds as it would for a non-NG ACN call (e.g., verbal conveyance 525 of data) 527 6. Profile 529 In the context of emergncy calls placed by an in-vehicle system it is 530 assumed that the car is equipped with a built-in GNSS receiver. For 531 this reason only geodetic location information will be sent within an 532 emergency call. The following location shapes MUST be implemented: 533 2d and 3d Point (see Section 5.2.1 of [RFC5491]), Circle (see 534 Section 5.2.3 of [RFC5491]), and Ellipsoid (see Section 5.2.7 of 535 [RFC5491]). The coordinate reference systems (CRS) specified in 536 [RFC5491] are also mandatory for this document. The 537 element, as defined in [RFC5962] which indicates the direction of 538 travel of the vehicle, is important for dispatch and hence it MUST be 539 included in the PIDF-LO [RFC4119]. The element specified 540 in [RFC5962] MUST be implemented and MAY be included. 542 Calls by in-vehicle systems are placed via cellular networks, which 543 might ignore location sent by an originating device in an emergency 544 call INVITE, instead attaching their own location (often determined 545 in cooperation with the originating device). Standardized crash data 546 structures often include location as determined by the IVS. A 547 benefit of this is that it allows the PSAP to see both the location 548 as determined by the cellular network (often in cooperation with the 549 originating device) and the location as determined by the IVS. 551 This specification inherits the ability to utilize test call 552 functionality from Section 15 of [RFC6881]. 554 7. Call Setup 556 It is important that ACN calls be easily identifiable as such at all 557 stages of call handling, and that automatic versus manual triggering 558 be known. ACN calls differ from general emergency calls in several 559 aspects, including the presence of standardized crash data, the fact 560 that the call is known to be placed by an in-vehicle system (which 561 has implications for PSAP operational processes), and, especially for 562 automatic calls, information that can indicate a likelihood of severe 563 injury and hence need for trauma services. Knowledge that a call is 564 an ACN and further that it was automatically or manually invoked 565 carries a range of implications about the call, the circumstances, 566 and the vehicle occupants. Calls by in-vehicle systems can be 567 considered a specific sub-class of general emergency calls and are 568 optimally handled by a PSAP with the technical and operational 569 capabilities to serve such calls. (This is especially so in 570 environments such as the U.S. where there are many PSAPs and where 571 individual PSAPs have a range of capabilities.) Technical 572 capabilities include the ability to recognize and process 573 standardized crash data. Operational capabilities include training 574 and processes for assessing severe injury likelihood and responding 575 appropriately (e.g., dispatching trauma-capable medical responders or 576 those trained and equipped to extract occupants from crashed vehicles 577 and handle gasoline or other hazardous materials, transporting 578 victims to a trauma center, alerting the receiving facility, etc.). 580 Because ACN calls differ in significant ways from general emergency 581 calls, and because such calls typically generally are best handled by 582 PSAPs equipped technically to interpet and make use of crash data, 583 and operationally to handle emergency calls placed by in-vehicle 584 systems, [I-D.ietf-ecrit-ecall] registers SOS sub-services. Using a 585 sub-service allows the call to be treated as an amergency call and 586 makes it readily obvious that the call is an ACN; a further child 587 element distinguishes calls automatically placed due to a crash or 588 other serious incident (such as a fire) from those manually invoked 589 by a vehicle occupant (specifically, "SOS.ecall.automatic" and 590 "SOS.ecall.manual"). The distinction between automatic and manual 591 invocation is also significant; automatically triggered calls 592 indicate a car crash or some other serious incident (e.g., a fire) 593 and carry a greater presumption of risk of injury and hence need for 594 specific responders (such as trauma or fire). Manually triggered 595 calls are often reports of serious hazards (such as impaired drivers 596 or roadway debris) and might require different responses depending on 597 the situation. Manually triggered calls also have a greater chance 598 of being false (e.g., accidental) calls and might thus be subject to 599 different handling by the PSAP. 601 A next-generation In-Vehicle System (IVS) transmits crash data by 602 encoding it in a standardized and registered format and attaching it 603 to an INVITE as an additional data block as specified in Section 4.1 604 of [I-D.ietf-ecrit-additional-data]. As described in that document, 605 the block is identified by its MIME content-type, and pointed to by a 606 CID URL in a Call-Info header with a 'purpose' parameter value 607 corresponding to the block. 609 Specifically, the steps required during standardization are: 611 o A set of crash data is standardized by an SDO or appropriate 612 organization 614 o A MIME Content-Type for the crash data set is registered with IANA 616 * If the data is specifically for use in emergency calling, the 617 MIME type is normally under the 'application' type with a 618 subtype starting with 'EmergencyCallData.' 620 * If the data format is XML, then by convention the name has a 621 suffix of '+xml' 623 o The item is registered in the Emergency Call Additional Data 624 registry, as defined in Section 9.1.7 of 625 [I-D.ietf-ecrit-additional-data] 627 * For emergency-call-specific formats, the registered name is the 628 root of the MIME Content-Type (not including the 629 'EmergencyCallData' prefix and any suffix such as '+xml') as 630 described in Section 4.1 of [I-D.ietf-ecrit-additional-data] 632 When placing an emergency call: 634 o The crash data set is created and encoded per its specification 636 o The crash data set is attached to the emergency call INVITE as 637 specified in Section 4.1 of [I-D.ietf-ecrit-additional-data], that 638 is, as a MIME body part identified by its MIME Content-Type in the 639 body part's Content-Type header field 641 o The body part is assigned a unique identifier label in a Content- 642 ID header field of the body part 644 o A Call-Info header field at the top level of the INVITE is added 645 that references the crash data and identifies it by its MIME root 646 (as registered in the Emergency Call Additional Data registry) 648 * The crash data is referenced in the Call-Info header field by a 649 CID URL that contains the unique Content ID assigned to the 650 crash data body part 652 * The crash data is identified in the Call-Info header field by a 653 'purpose' parameter whose value is 'EmergencyCallData.' 654 concatenated with the specific crash data entry in the 655 Emergency Call Additional Data registry 657 * The Call-Info header field MAY be either solely to reference 658 the crash data (and hence have only the one URL) or can also 659 contain other URLs referencing other data 661 o Additional crash data sets MAY be included by following the same 662 steps 664 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 665 the Association of Public-Safety Communications Officials (APCO) and 666 the National Emergency Number Association (NENA) [VEDS]. The 667 'application/EmergencyCallData.VEDS+xml' MIME content-type is used to 668 identify it. The 'VEDS' entry in the Emergency Call Additional Data 669 registry is used to construct a 'purpose' parameter value for 670 conveying VEDS data in a Call-Info header. 672 The VEDS data is attached as a body part with MIME content type 673 'application/EmergencyCallData.VEDS+xml' which is pointed at by a 674 Call-Info URL of type CID with a 'purpose' parameter of 675 'EmergencyCallData.VEDS'. 677 Entities along the path between the vehicle and the PSAP are able to 678 identify the call as an ACN call and handle it appropriately. The 679 PSAP is able to identify the crash data as well as any other 680 additional data attached to the INVITE by examining the Call-Info 681 header fields for 'purpose' parameters whose values start with 682 'EmergencyCallData.' The PSAP is able to access and the data it is 683 capable of handling and is interested in by checking the 'purpose' 684 parameter values. 686 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 687 up and other normative requirements except that in this document, 688 support for the eCall MSD is OPTIONAL and support for VEDS in 689 REQUIRED. 691 8. Call Routing 693 An Emergency Services IP Network (ESInet) is a network operated by or 694 on behalf of emergency services authorities. It handles emergency 695 call routing and processing before delivery to a PSAP. In the 696 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 697 architecture adopted by EENA, each PSAP is connected to one or more 698 ESInets. Each originating network is also connected to one or more 699 ESInets. The ESInets maintain policy-based routing rules which 700 control the routing and processing of emergency calls. The 701 centralization of such rules within ESInets provides for a cleaner 702 separation between the responsibilities of the originating network 703 and that of the emergency services network, and provides greater 704 flexibility and control over processing of emergency calls by the 705 emergency services authorities. This makes it easier to react 706 quickly to unusual situations that require changes in how emergency 707 calls are routed or handled (e.g., a natural disaster closes a PSAP), 708 as well as ease in making long-term changes that affect such routing 709 (e.g., cooperative agreements to specially handle calls requiring 710 translation or relay services). 712 In an environment that uses ESInets, the originating network need 713 only detect that the service URN of an emergency call is or starts 714 with "sos", passing all types of emergency calls to an ESInet. The 715 ESInet is then responsible for routing such calls to an appropriate 716 PSAP. In an environment without an ESInet, the emergency services 717 authorities and the originating carriers would need to determine how 718 such calls are routed. 720 9. Test Calls 722 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 723 ability to utilize test call functionality from Section 15 of 724 [RFC6881]. 726 A service URN starting with "test." indicates a request for an 727 automated test. Per [I-D.ietf-ecrit-ecall], 728 "urn:service:test.sos.ecall.automatic" indicates such a test feature. 729 This functionality is defined in [RFC6881]. 731 Note that since test calls are placed using "test" as the parent 732 service URN and "sos" as a child, such calls are not treated as an 733 emergency call and so some functionality will not apply (such as 734 preemption or service availability for devices lacking service ("non- 735 service-initialized" or "NSI") if those are available for emergency 736 calls); this is by design. MNOs can recognize test calls and treat 737 them in a way that tests as much functionality as desired, but this 738 is outside the scope of this document. 740 10. Example 742 Figure 7 shows an emergency call placed by a vehicle whereby location 743 information and VEDS crash data are both attached to the SIP INVITE 744 message. The INVITE has a request URI containing the 745 'urn:service:sos.ecall.automatic' service URN and is thus recognized 746 as an ACN type of emergency call, and is also recognizable as an 747 emergency call because the request URI starts with 'urn:service:sos'. 748 The mobile network operator (MNO) routes the call to an Emergency 749 services IP Network (ESInet), as for any emergency call. The ESInet 750 processes the call as an ACN and routes the call to an appropriate 751 ACN-capable PSAP (using location information and the fact that that 752 it is an ACN). The call is processed by the Emergency Services 753 Routing Proxy (ESRP), as the entry point to the ESInet. The ESRP 754 routes the call to an appropriate ACN-capable PSAP, where the call is 755 received by a call taker. (In deployments where there is no ESInet, 756 the MNO itself routes the call directly to an appropriate ACN-capable 757 PSAP.) 758 +---------------------------------------+ 759 | | 760 +------------+ | +-------+ | 761 | | | | PSAP2 | | 762 | | | +-------+ | 763 | Originating| | | 764 | Mobile | | +------+ +-------+ | 765 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 766 | | | +------+ +-------+ | 767 | | | | 768 +------------+ | +-------+ | 769 | | PSAP3 | | 770 | +-------+ | 771 | | 772 | | 773 | | 774 | ESInet | 775 +---------------------------------------+ 777 Figure 7: Example of Vehicle-Placed Emergency Call Message Flow 779 The example, shown in Figure 8, illustrates a SIP emergency call 780 INVITE that is being conveyed with location information (a PIDF-LO) 781 and crash data (as VEDS data). 783 The example VEDS data structure shows information about about a 784 crashed vehicle. The example communicates that the car is a model 785 year 2015 Saab 9-5 (a car which does not exist). The front airbag 786 deployed as a consequence of the crash. The 787 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 788 passenger car (the code is set to '101') and that it is not a 789 convertible (the 'ConvertibleIndicator' value is set to 'false'). 791 The 'VehicleCrashPulse' element provides further information about 792 the crash, namely that the force of impact based on the change in 793 velocity over the duration of the crash pulse was 100 MPH. The 794 principal direction of the force of the impact is set to '12' (which 795 refers to 12 O'Clock, corresponding to a frontal collision). This 796 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 797 element. 799 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 800 quarter turns in concert with a rollover expressed as a number; in 801 our case 1. 803 No roll bar was deployed, as indicated in 804 'VehicleRollbarDeployedIndicator' being set to 'false'. 806 Next, there is information indicating seatbelt and seat sensor data 807 for individual seat positions in the vehicle. In our example, 808 information from the driver seat is available (value '1' in the 809 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 810 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 811 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 812 and the seat sensor determined that the seat is occupied 813 ('VehicleSeatOccupiedIndicator' element). 815 Finally, information about the weight of the vehicle, which is 600 816 kilogram in our example. 818 In addition to the information about the vehicle, further indications 819 are provided, namely the presence of fuel leakage 820 ('FuelLeakingIndicator' element), an indication whether the vehicle 821 was subjected to multiple impacts ('MultipleImpactsIndicator' 822 element), the orientation of the vehicle at final rest 823 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 824 that there are no parts of the vehicle on fire (the 825 'VehicleFireIndicator' element). 827 INVITE urn:service:sos.ecall.automatic SIP/2.0 828 To: urn:service:sos.ecall.automatic 829 From: ;tag=9fxced76sl 830 Call-ID: 3848276298220188511@atlanta.example.com 831 Geolocation: 832 Geolocation-Routing: no 833 Call-Info: cid:1234567890@atlanta.example.com; 834 purpose=EmergencyCallData.VEDS 835 Accept: application/sdp, application/pidf+xml 836 CSeq: 31862 INVITE 837 Content-Type: multipart/mixed; boundary=boundary1 838 Content-Length: ... 840 --boundary1 841 Content-Type: application/sdp 843 ...Session Description Protocol (SDP) goes here 845 --boundary1 846 Content-Type: application/pidf+xml 847 Content-ID: 849 850 858 859 860 861 862 -34.407 150.883 863 864 865 278 866 867 868 869 870 gps 871 872 2012-04-5T10:18:29Z 873 1M8GDM9A_KP042788 874 875 877 --boundary1 878 Content-Type: application/EmergencyCallData.VEDS+xml 879 Content-ID: 1234567890@atlanta.example.com 880 Content-Disposition: by-reference;handling=optional 882 883 887 888 889 Saab 890 891 892 9-5 893 894 896 2015 897 898 899 FRONT 900 true 901 903 904 false 905 MAIN 906 908 101 909 910 911 912 914 100 915 916 918 MPH 919 920 12 921 922 1 923 924 925 false 926 927 928 1 929 930 true 931 932 true 933 934 true 935 936 937 939 941 600 942 943 945 kilogram 946 947 948 949 true 950 false 951 true 952 Driver 953 954 false 955 956 958 --boundary1-- 960 Figure 8: SIP INVITE indicating a Vehicule-Initated Emergency Call 962 11. Security Considerations 964 Since this document relies on [I-D.ietf-ecrit-ecall] and 965 [I-D.ietf-ecrit-additional-data], the security considerations 966 described there and in [RFC5069] apply here. Implementors are 967 strongly cautioned to read and understand the discussion in those 968 documents. 970 As with emergency service systems where location data is supplied or 971 determined with the assistance of an end host, there is the 972 possibility that that location is incorrect, either intentially (in 973 case of an a denial of service attack against the emergency services 974 infrastructure) or due to a malfunctioning device. The reader is 975 referred to [RFC7378] for a discussion of some of these 976 vulnerabilities. 978 12. Privacy Considerations 980 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 981 builds on [I-D.ietf-ecrit-additional-data], the data structures 982 specified there, and the corresponding privacy considerations 983 discussed there, apply here as well. The VEDS data structure 984 contains optional elements that can carry identifying and personal 985 information, both about the vehicle and about the owner, as well as 986 location information, and so needs to be protected against 987 unauthorized disclosure, as discussed in 988 [I-D.ietf-ecrit-additional-data]. Local regulations may impose 989 additional privacy protection requirements. 991 13. IANA Considerations 992 13.1. MIME Content-type Registration for 'application/ 993 EmergencyCall.VEDS+xml' 995 This specification requests the registration of a new MIME type 996 according to the procedures of RFC 4288 [RFC4288] and guidelines in 997 RFC 3023 [RFC3023]. 999 MIME media type name: application 1001 MIME subtype name: EmergencyCallData.VEDS+xml 1003 Mandatory parameters: none 1005 Optional parameters: charset 1007 Indicates the character encoding of enclosed XML. 1009 Encoding considerations: Uses XML, which can employ 8-bit 1010 characters, depending on the character encoding used. See 1011 Section 3.2 of RFC 3023 [RFC3023]. 1013 Security considerations: 1015 This content type is designed to carry vehicle crash data 1016 during an emergency call. 1018 This data can contain personal information including vehicle 1019 VIN, location, direction, etc. Appropriate precautions need to 1020 be taken to limit unauthorized access, inappropriate disclosure 1021 to third parties, and eavesdropping of this information. 1022 Please refer to Section 7 and Section 8 of 1023 [I-D.ietf-ecrit-additional-data] for more information. 1025 When this content type is contained in a signed or encrypted 1026 body part, the enclosing multipart (e.g., multipart/signed or 1027 multipart/encrypted) has the same Content-ID as the data part. 1028 This allows an entity to identify and access the data blocks it 1029 is interested in without having to dive deeply into the message 1030 structure or decrypt parts it is not interested in. (The 1031 'purpose' parameter in a Call-Info header field identifies the 1032 data, and the CID URL points to the data block in the body, 1033 which has a matching Content-ID body part header field). 1035 Interoperability considerations: None 1037 Published specification: [VEDS] 1039 Applications which use this media type: Emergency Services 1040 Additional information: None 1042 Magic Number: None 1044 File Extension: .xml 1046 Macintosh file type code: 'TEXT' 1048 Person and email address for further information: Hannes 1049 Tschofenig, Hannes.Tschofenig@gmx.net 1051 Intended usage: LIMITED USE 1053 Author: This specification is a work item of the IETF ECRIT 1054 working group, with mailing list address . 1056 Change controller: The IESG 1058 13.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1059 Data registry 1061 This specification requests IANA to add the 'VEDS' entry to the 1062 Emergency Call Additional Data registry, with a reference to this 1063 document. The Emergency Call Additional Data registry has been 1064 established by [I-D.ietf-ecrit-additional-data]. 1066 14. Contributors 1068 We would like to thank Ulrich Dietz for his help with earlier 1069 versions of the original version of this document. 1071 15. Acknowledgements 1073 We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, 1074 Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback. 1076 16. Changes from Previous Versions 1078 16.1. Changes from draft-ietf-05 to draft-ietf-06 1080 o Added clarifying text regarding signed and encrypted data 1081 o Additional informative text in "Migration to Next-Generation" 1082 section 1083 o Additional clarifying text regarding security and privacy. 1085 16.2. Changes from draft-ietf-04 to draft-ietf-05 1087 o Reworded security text in main document and in MIME registration 1088 for the VEDS object 1090 16.3. Changes from draft-ietf-03 to draft-ietf-04 1092 o Added example VEDS object 1093 o Additional clarifications and corrections 1094 o Removed references from Abstract 1095 o Moved Document Scope section to follow Introduction 1097 16.4. Changes from draft-ietf-02 to draft-ietf-03 1099 o Additional clarifications and corrections 1101 16.5. Changes from draft-ietf-01 to draft-ietf-02 1103 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1104 aspects including the service URN; this document no longer 1105 proposes a unique service URN for non-eCall NG-ACN calls; the same 1106 service URN is now used for all NG-ACN calls including NG-eCall 1107 and non-eCall 1108 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1109 support it 1110 o Minor wording improvements and clarifications 1112 16.6. Changes from draft-ietf-00 to draft-ietf-01 1114 o Added further discussion of test calls 1115 o Added further clarification to the document scope 1116 o Mentioned that multi-region vehicles may need to support other 1117 crash notification specifications such as eCall 1118 o Minor wording improvements and clarifications 1120 16.7. Changes from draft-gellens-02 to draft-ietf-00 1122 o Renamed from draft-gellens- to draft-ietf- 1123 o Added text to Introduction to clarify that during a CS ACN, the 1124 PSAP call taker usually needs to listen to the data and transcribe 1125 it 1127 16.8. Changes from draft-gellens-01 to -02 1129 o Fixed case of 'EmergencyCallData', in accordance with changes to 1130 [I-D.ietf-ecrit-additional-data] 1132 16.9. Changes from draft-gellens-00 to -01 1134 o Now using 'EmergencyCallData' for purpose parameter values and 1135 MIME subtypes, in accordance with changes to 1136 [I-D.ietf-ecrit-additional-data] 1137 o Added reference to RFC 6443 1138 o Fixed bug that caused Figure captions to not appear 1140 17. References 1142 17.1. Normative References 1144 [I-D.ietf-ecrit-additional-data] 1145 Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1146 J. Winterbottom, "Additional Data Related to an Emergency 1147 Call", draft-ietf-ecrit-additional-data-37 (work in 1148 progress), October 2015. 1150 [I-D.ietf-ecrit-ecall] 1151 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1152 European eCall", draft-ietf-ecrit-ecall-03 (work in 1153 progress), July 2015. 1155 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1156 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 1157 RFC2119, March 1997, 1158 . 1160 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1161 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1162 . 1164 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1165 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1166 . 1168 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1169 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1170 December 2005, . 1172 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1173 Emergency and Other Well-Known Services", RFC 5031, DOI 1174 10.17487/RFC5031, January 2008, 1175 . 1177 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1178 Presence Information Data Format Location Object (PIDF-LO) 1179 Usage Clarification, Considerations, and Recommendations", 1180 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1181 . 1183 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1184 Thomson, "Dynamic Extensions to the Presence Information 1185 Data Format Location Object (PIDF-LO)", RFC 5962, DOI 1186 10.17487/RFC5962, September 2010, 1187 . 1189 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1190 "Framework for Emergency Calling Using Internet 1191 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1192 2011, . 1194 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1195 Communications Services in Support of Emergency Calling", 1196 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1197 . 1199 [VEDS] "Vehicular Emergency Data Set (VEDS) version 3", July 1200 2012, . 1203 17.2. Informative references 1205 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1206 Emergency Context Resolution with Internet Technologies", 1207 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1208 . 1210 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1211 Shanmugam, "Security Threats and Requirements for 1212 Emergency Call Marking and Mapping", RFC 5069, DOI 1213 10.17487/RFC5069, January 2008, 1214 . 1216 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1217 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1218 December 2014, . 1220 Authors' Addresses 1221 Randall Gellens 1222 Qualcomm Technologies, Inc 1223 5775 Morehouse Drive 1224 San Diego 92651 1225 US 1227 Email: rg+ietf@randy.pensive.org 1229 Brian Rosen 1230 NeuStar, Inc. 1231 470 Conrad Dr 1232 Mars, PA 16046 1233 US 1235 Email: br@brianrosen.net 1237 Hannes Tschofenig 1238 (Individual) 1240 Email: Hannes.Tschofenig@gmx.net 1241 URI: http://www.tschofenig.priv.at