idnits 2.17.00 (12 Aug 2021) /tmp/idnits62345/draft-ietf-ecrit-car-crash-08.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 : ---------------------------------------------------------------------------- ** There are 18 instances of too long lines in the document, the longest one being 8 characters in excess of 72. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 6, 2016) is 2144 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: 'RFC4119' is defined on line 1967, but no explicit reference was found in the text == Unused Reference: 'RFC5031' is defined on line 1975, but no explicit reference was found in the text == Unused Reference: 'RFC5491' is defined on line 1985, but no explicit reference was found in the text == Unused Reference: 'RFC5962' is defined on line 1991, but no explicit reference was found in the text == Outdated reference: draft-ietf-ecrit-additional-data has been published as RFC 7852 == Outdated reference: draft-ietf-ecrit-ecall has been published as RFC 8147 ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Downref: Normative reference to an Informational RFC: RFC 6443 -- Possible downref: Non-RFC (?) normative reference: ref. 'VEDS' Summary: 5 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Consultant 4 Intended status: Standards Track B. Rosen 5 Expires: January 7, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 July 6, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-08.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 primary differences being that this 38 document makes the MSD data set optional and VEDS mandatory, and 39 extends the eCall metadata/control object to permit greater 40 functionality. This document also describes legacy (circuit- 41 switched) ACN systems and their migration to next-generation 42 emergency calling, to provide background information and context. 44 Status of This Memo 46 This Internet-Draft is submitted in full conformance with the 47 provisions of BCP 78 and BCP 79. 49 Internet-Drafts are working documents of the Internet Engineering 50 Task Force (IETF). Note that other groups may also distribute 51 working documents as Internet-Drafts. The list of current Internet- 52 Drafts is at http://datatracker.ietf.org/drafts/current/. 54 Internet-Drafts are draft documents valid for a maximum of six months 55 and may be updated, replaced, or obsoleted by other documents at any 56 time. It is inappropriate to use Internet-Drafts as reference 57 material or to cite them other than as "work in progress." 59 This Internet-Draft will expire on January 7, 2017. 61 Copyright Notice 63 Copyright (c) 2016 IETF Trust and the persons identified as the 64 document authors. All rights reserved. 66 This document is subject to BCP 78 and the IETF Trust's Legal 67 Provisions Relating to IETF Documents 68 (http://trustee.ietf.org/license-info) in effect on the date of 69 publication of this document. Please review these documents 70 carefully, as they describe your rights and restrictions with respect 71 to this document. Code Components extracted from this document must 72 include Simplified BSD License text as described in Section 4.e of 73 the Trust Legal Provisions and are provided without warranty as 74 described in the Simplified BSD License. 76 Table of Contents 78 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 79 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 80 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 81 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9 82 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 83 6. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 13 84 6.1. Call Routing . . . . . . . . . . . . . . . . . . . . . . 15 85 7. eCall Metadata/Control Extensions . . . . . . . . . . . . . . 16 86 7.1. New values for the 'action' attribute' . . . . . . . . . 17 87 7.2. element extensions . . . . . . . . . . . . . . . . 17 88 7.3. The element . . . . . . . . . . . . . . . 19 89 7.4. element extensions . . . . . . . . . . . . . . 21 90 8. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 23 91 9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 92 10. Security Considerations . . . . . . . . . . . . . . . . . . . 30 93 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . 30 94 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 95 12.1. MIME Content-type Registration for 96 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 31 98 12.2. Registration of the 'VEDS' entry in the Emergency Call 99 Additional Data registry . . . . . . . . . . . . . . . . 32 100 12.3. Additions to the eCall Control Extension Registry . . . 32 101 12.4. eCall Action Extensions . . . . . . . . . . . . . . . . 34 102 12.5. eCall Static Message Registry . . . . . . . . . . . . . 34 103 12.6. eCall Reason Registry . . . . . . . . . . . . . . . . . 35 104 12.7. eCall Lamp ID Registry . . . . . . . . . . . . . . . . . 36 105 12.8. eCall Camera ID Registry . . . . . . . . . . . . . . . . 37 106 13. eCall Control Block Schema . . . . . . . . . . . . . . . . . 38 107 14. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 41 108 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41 109 16. Changes from Previous Versions . . . . . . . . . . . . . . . 41 110 16.1. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 41 111 16.2. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 42 112 16.3. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 42 113 16.4. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 42 114 16.5. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 42 115 16.6. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 42 116 16.7. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 42 117 16.8. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 42 118 16.9. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 43 119 16.10. Changes from draft-gellens-01 to -02 . . . . . . . . . . 43 120 16.11. Changes from draft-gellens-00 to -01 . . . . . . . . . . 43 121 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 122 17.1. Normative References . . . . . . . . . . . . . . . . . . 43 123 17.2. Informative references . . . . . . . . . . . . . . . . . 44 124 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 126 1. Terminology 128 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 129 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 130 document are to be interpreted as described in [RFC2119]. 132 This document re-uses terminology defined in Section 3 of [RFC5012]. 134 Additionally, we use the following abbreviations: 136 +--------+----------------------------------------------------------+ 137 | Term | Expansion | 138 +--------+----------------------------------------------------------+ 139 | 3GPP | 3rd Generation Partnership Project | 140 | AACN | Advanced Automatic Crash Notification | 141 | ACN | Automatic Crash Notification | 142 | APCO | Association of Public-Safety Communications Officials | 143 | EENA | European Emergency Number Association | 144 | ESInet | Emergency Services IP network | 145 | GNSS | Global Navigation Satellite System (which includes | 146 | | various systems such as the Global Positioning System or | 147 | | GPS) | 148 | IVS | In-Vehicle System | 149 | MNO | Mobile Network Operator | 150 | MSD | eCall Minimum Set of Data | 151 | NENA | National Emergency Number Association | 152 | POTS | Plain Old Telephone Service (normal, circuit-switched | 153 | | voice calls) | 154 | PSAP | Public Safety Answering Point | 155 | TSP | Telematics Service Provider | 156 | VEDS | Vehicle Emergency Data Set | 157 +--------+----------------------------------------------------------+ 159 2. Introduction 161 Emergency calls made by in-vehicle systems (e.g., automatically in 162 the event of a crash or serious incident or manually by a vehicle 163 occupant) assist in significantly reducing road deaths and injuries 164 by allowing emergency services to respond quickly and appropriately 165 to the specifics of the incident, often with better location 166 accuracy. 168 Drivers often have a poor location awareness, especially outside of 169 major cities, at night and when away from home (especially abroad). 170 In the most crucial cases, the victim(s) might not be able to call 171 because they have been injured or trapped. 173 For more than two decades, some vehicles have been equipped with 174 telematics systems that, among other features, place an emergency 175 call automatically in the event of a crash or manually in response to 176 an emergency call button. Such systems generally have on-board 177 location determination systems that make use of satellite-based 178 positioning technology, inertial sensors, gyroscopes, etc., which can 179 provide an accurate position for the vehicle. Such built-in systems 180 can take advantage of the benefits of being integrated into a 181 vehicle, such as more power capacity, ability to have larger or 182 specialized antenna, ability to be engineered to avoid or minimise 183 degradation by vehicle glass coatings, interference from other 184 vehicle systems, etc. Thus, the PSAP can be provided with a good 185 estimate of where the vehicle is during an emergency. Vehicle 186 manufacturers are increasingly adopting such systems, both for the 187 safety benefits and for the additional features and services they 188 enable (e.g., remote engine diagnostics, remote door unlock, stolen 189 vehicle tracking and disabling, etc.). 191 The general term for such systems is Automatic Crash Notification 192 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 193 used in this document as a general term. ACN systems transmit some 194 amount of data specific to the incident, referred to generally as 195 "crash data" (the term is commonly used even though there might not 196 have been a crash). While different systems transmit different 197 amounts of crash data, standardized formats, structures, and 198 mechanisms are needed to provide interoperability among systems and 199 PSAPs. 201 As of the date of this document, currently deployed in-vehicle 202 telematics systems are circuit-switched and lack a standards-based 203 ability to convey crash data directly to the PSAP (generally relying 204 on either a human advisor or an automated text-to-speech system to 205 provide the PSAP call taker with some crash data orally, or in some 206 cases via a proprietary mechanism). In most cases, the PSAP call 207 taker needs to first realize that the call is related to a vehicle 208 incident, and then listen to the data and transcribe it. Circuit- 209 switched ACN systems are referred to here as CS-ACN. 211 The transition to next-generation calling in general, and emergency 212 calling in particular, provides an opportunity to vastly improve the 213 scope, breadth, reliability and usefulness of crash data during an 214 emergency by allowing it to be transmitted during call set-up, and to 215 be automatically processed by the PSAP and made available to the call 216 taker in an integrated, automated way, as well as provide the ability 217 for a PSAP call taker to request that a vehicle take certain actions, 218 such as flashing lights or unlocking doors. In addition, vehicle 219 manufacturers are provided an opportunity to take advantage of the 220 same standardized mechanisms for data transmission and request 221 processing for internal use if they wish (such as telemetry between 222 the vehicle and a service center for both emergency and non-emergency 223 uses, including location-based services, multi-media entertainment 224 systems, remote door unlocking, and road-side assistance 225 applications). 227 Next-generation ACN provides an opportunity for such calls to be 228 recognized and processed as such during call set-up, and routed to an 229 equipped PSAP where the vehicle data is available to assist the call 230 taker in assessing and responding to the situation. Next-generation 231 (IP-based) ACN systems are referred to here as NG-ACN. 233 An ACN call can initiated by a vehicle occupant or automatically 234 initiated by vehicle systems in the event of a serious incident. 235 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 236 used to refer to the class of calls that are placed by an in-vehicle 237 system (IVS) or Telematics Service Providers (TSP) and that carry 238 incident-related data as well as voice.) Automatically triggered 239 calls indicate a car crash or some other serious incident (e.g., a 240 fire). Manually triggered calls are often reports of observed 241 crashes or serious hazards (such as impaired drivers or roadway 242 debris). Depending on the design, manually triggered calls might be 243 more likely to be accidental. 245 This document describes how the IETF mechanisms for IP-based 246 emergency calls, including [RFC6443] and 247 [I-D.ietf-ecrit-additional-data], are used to provide the realization 248 of next-generation ACN. 250 This document reuses the technical aspects of next-generation pan- 251 European eCall (a mandated and standardized system for emergency 252 calls by in-vehicle systems within Europe and other regions), as 253 described in [I-D.ietf-ecrit-ecall]. However, this document 254 specifies a different set of vehicle (crash) data, specifically, the 255 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 256 of Data (MSD). This document is an extension of 257 [I-D.ietf-ecrit-ecall], with the differences being that this document 258 makes the MSD data set optional and VEDS mandatory, and adds 259 extension elements, attributes, and values to the eCall metadata/ 260 control object defined in that document. 262 The Association of Public-Safety Communications Officials (APCO) and 263 the National Emergency Number Association (NENA) have jointly 264 developed a standardized set of incident-related vehicle data for ACN 265 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 266 is often referred to as crash data although it is applicable in 267 incidents other than crashes. 269 VEDS provides a standard data set for the transmission, exchange, and 270 interpretation of vehicle-related data. A standard data format 271 allows the data to be generated by an IVS or TSP and interpreted by 272 PSAPs, emergency responders, and medical facilities. It includes 273 incident-related information such as airbag deployment, location and 274 compass orientation of the vehicle, spatial orientation of the 275 vehicle (e.g., upright, on its side or top or a bumper), various 276 sensor data that can indicate the potential severity of the crash and 277 the likelihood of severe injuries to the vehicle occupants, etc. 278 This data better informs the PSAP and emergency responders as to the 279 type of response that might be needed. Some of this information has 280 been included in U.S. government guidelines for field triage of 281 injured patients [triage-2008] [triage-2011]. These guidelines are 282 designed to help responders identify the potential existence of 283 severe internal injuries and to make critical decisions about how and 284 where a patient needs to be transported. 286 This document registers the 'application/EmergencyCallData.VEDS+xml' 287 MIME content-type, and registers the 'VEDS' entry in the Emergency 288 Call Additional Data registry. 290 VEDS is an XML structure (see [VEDS]) transported in SIP using the 291 'application/EmergencyCallData.VEDS+xml' MIME content-type. The 292 'VEDS' entry in the Emergency Call Additional Data registry is used 293 to construct a 'purpose' parameter value to indicate VEDS data in a 294 Call-Info header (as described in [I-D.ietf-ecrit-additional-data]). 296 VEDS is a versatile structure that can accomodate varied needs. 297 However, if additional sets of data are determined to be needed 298 (e.g., in the future or in different regions), the steps to enable 299 each data block are very briefly summarized below: 301 o A standardized format and encoding (such as XML) is defined and 302 published by a Standards Development Organization (SDO) 304 o A MIME Content-Type is registered for it (typically under the 305 'Application' media type) with a sub-type starting with 306 'EmergencyCallData.' 308 o An entry for the block is added to the Emergency Call Additional 309 Data Blocks sub-registry (established by 310 [I-D.ietf-ecrit-additional-data]); the registry entry is the root 311 of the MIME sub-type (not including the 'EmergencyCallData' prefix 312 and any suffix such as '+xml') 314 A next-generation In-Vehicle System (IVS) or TSP transmits crash data 315 by encoding it in a standardized and registered format (such as VEDS) 316 and attaching it to a SIP message as a MIME body part. The body part 317 is identified by its MIME content-type (such as 'application/ 318 EmergencyCallData.VEDS+xml') in the Content-Type header field of the 319 body part. The body part is assigned a unique identifier which is 320 listed in a Content-ID header field in the body part. The SIP 321 message is marked as containing the crash data by adding a Call-Info 322 header field at the top level of the message. This Call-Info header 323 field contains a CID URL referencing the body part's unique 324 identifier, and a 'purpose' parameter identifying the data as the 325 crash data per the registry entry. The 'purpose' parameter's value 326 is 'EmergencyCallData.' plus the value associated with the data type 327 in the registry; for VEDS data, "purpose=EmergencyCallData.VEDS". 329 These mechanisms are thus used to place emergency calls that are 330 identifiable as ACN calls and that carry one or more standardized 331 crash data objects in an interoperable way. 333 Calls by in-vehicle systems are placed via cellular networks, which 334 might ignore location sent by an originating device in an emergency 335 call INVITE, instead attaching their own location (often determined 336 in cooperation with the originating device). Standardized crash data 337 structures often include location as determined by the IVS. A 338 benefit of this is that it allows the PSAP to see both the location 339 as determined by the cellular network (often in cooperation with the 340 originating device) and the location as determined by the IVS. 342 This specification inherits the ability to utilize test call 343 functionality from Section 15 of [RFC6881]. 345 3. Document Scope 347 This document is focused on how an ACN emergency call is setup and 348 incident-related data (including vehicle, sensor, and location data) 349 is transmitted to the PSAP using IETF specifications. For the direct 350 model, this is the end-to-end description (between the vehicle and 351 the PSAP). For the TSP model, this describes the call leg between 352 the TSP and the PSAP, leaving the call leg between the vehicle and 353 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 354 are then free to use the same mechanism as for the right-hand side or 355 not. 357 Note that Europe has a mandated and standardized system for emergency 358 calls by in-vehicle systems. This pan-European system is known as 359 "eCall" and is the subject of a separate document, 360 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 361 designed to operate in multiple regions might need to support eCall 362 as well as the ACN described here. In this case, a vehicle IVS might 363 determine whether to use eCall or ACN by first determining a region 364 or country in which it is located (e.g., from a GNSS location fix 365 and/or identity of or information from an MNO). If other regions 366 adopt other data formats, a multi-region vehicle might need to 367 support those as well. This document adopts the call set-up and 368 other technical aspects of [I-D.ietf-ecrit-ecall], which uses 369 [I-D.ietf-ecrit-additional-data]; this makes it straightforward to 370 use a different data set while keeping other technical aspects 371 unchanged. Hence, both NG-eCall and the NG-ACN mechanism described 372 here are compatible, differing primarily in the specific data block 373 that is sent (the eCall MSD in the case of NG-eCall, and the APCO/ 374 NENA VEDS used in this document), and some additions to the metadata/ 375 control data block. If other regions adopt their own vehicle data 376 sets, this can be similarly accomodated without changing other 377 technical aspects. 379 4. Overview of Legacy Deployment Models 381 Legacy (circuit-switched) systems for placing emergency calls by in- 382 vehicle systems generally have some ability to convey at least 383 location and in some cases telematics data to the PSAP. Most such 384 systems use one of three architectural models, which are described 385 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 386 These three models are illustrated below. 388 In the TSP model, both emergency and non-emergency calls are placed 389 to a Telematics Service Provider (TSP); a proprietary technique is 390 used for data transfer (such as a proprietary in-band modem) between 391 the TSP and the vehicle. 393 In an emergency, generally the TSP call taker bridges in the PSAP and 394 communicates location, crash data (such as impact severity and trauma 395 prediction), and other data (such as the vehicle description) to the 396 PSAP call taker verbally (in some cases, a proprietary out-of-band 397 interface is used). Since the TSP knows the location of the vehicle 398 (from on-board GNSS and sensors), location-based routing is usually 399 used to route to the appropriate PSAP. In some cases, the TSP is 400 able to transmit location automatically, using similar techniques as 401 for wireless calls. Typically, a three-way voice call is established 402 between the vehicle, the TSP, and the PSAP, allowing communication 403 between the PSAP call taker, the TSP call taker, and the vehicle 404 occupants (who might be unconscious). 406 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 407 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 408 \\\----/// crash data +------+ location via trunk +------+ 410 Figure 1: Legacy TSP Model. 412 In the paired model, the IVS uses a Bluetooth link with a previously- 413 paired handset to establish an emergency call with the PSAP (by 414 dialing a standard emergency number; 9-1-1 in North America), and 415 then communicates location data to the PSAP via text-to-speech; crash 416 data might or might not be conveyed also using text-to-speech. Some 417 such systems use an automated voice prompt menu for the PSAP call 418 taker (e.g., "this is an automatic emergency call from a vehicle; 419 press 1 to open a voice path to the vehicle; press 2 to hear the 420 location read out") to allow the call taker to request location data 421 via text-to-speech. 423 +---+ 424 ///----\\\ | H | 911/etc voice call via handset +------+ 425 ||| IVS |||-->| S +----------------------------------->+ PSAP | 426 \\\----/// +---+ location via text-to-speech +------+ 428 Figure 2: Legacy Paired Model 430 In the direct model, the IVS directly places an emergency call with 431 the PSAP by dialing a standard emergency number (9-1-1 in North 432 America). Such systems might communicate location data to the PSAP 433 via text-to-speech; crash data might or might not be conveyed using 434 text-to-speech. Some such systems use an automated voice prompt menu 435 (e.g., "this is an automatic emergency call from a vehicle; press 1 436 to open a voice path to the vehicle; press 2 to hear the location 437 read out") to allow the call taker to request location data via text- 438 to-speech. 440 ///----\\\ 911/etc voice call via IVS +------+ 441 ||| IVS |||---------------------------------------->+ PSAP | 442 \\\----/// location via text-to-speech +------+ 444 Figure 3: Legacy Direct Model 446 5. Migration to Next-Generation 448 Migration of emergency calls placed by in-vehicle systems to next- 449 generation (all-IP) technology per this document provides a 450 standardized mechanism to identify such calls and to present crash 451 data with the call, as well as enabling additional communications 452 modalities and enhanced functionality. This allows ACN calls and 453 crash data to be automatically processed by the PSAP and made 454 available to the call taker in an integrated, automated way. Because 455 the crash data is carried in the initial SIP INVITE (per 456 [I-D.ietf-ecrit-additional-data]) the PSAP can present it to the call 457 taker simultaneously with the appearance of the call. The PSAP can 458 also process the data to take other actions (e.g., if multiple calls 459 from the same location arrive when the PSAP is busy and a subset of 460 them are NG-ACN calls, a PSAP might choose to store the information 461 and reject the calls, since the IVS will receive confirmation that 462 the information has been successfully received; a PSAP could also 463 choose to include a message stating that it is aware of the incident 464 and responders are on the way; a PSAP could call the vehicle back 465 when a call taker is available). 467 Origination devices and networks, PSAPs, emergency services networks, 468 and other telephony environments are migrating to next-generation. 470 This provides opportunities for significant enhancement to 471 interoperability and functionality, especially for emergency calls 472 carrying additional data such as vehicle crash data. (In the U.S., a 473 network specifically for emergency responders is being developed. 474 This network, FirstNet, will be next-generation from the start, 475 enhancing the ability for data exchange between PSAPs and 476 responders.) 478 Migration to next-generation (NG) provides an opportunity to 479 significantly improve the handling and response to vehicle-initiated 480 emergency calls. Such calls can be recognized as originating from a 481 vehicle, routed to a PSAP equipped both technically and operationally 482 to handle such calls, and the vehicle-determined location and crash 483 data can be made available to the call taker simultaneously with the 484 call appearance. The PSAP can take advantage of enhanced 485 functionality, including the ability to request the vehicle to take 486 an action, such as sending an updated set of data, converying a 487 message to the occupants, flashing lights, unlocking doors, etc. 489 Vehicle manufacturers using the TSP model can choose to take 490 advantage of the same mechanism to carry telematics data and requests 491 and responses between the vehicle and the TSP for both emergency and 492 non-emergency calls as are used for the interface with the PSAP. 494 A next-generation IVS establishes an emergency call using the 495 emergency call solution as described in [RFC6443] and [RFC6881], with 496 the difference that the Request-URI indicates an ACN type of 497 emergency call, the IVS typically does not perform routing or 498 location queries but relies on the carrier for this, and uses Call- 499 Info header fields to indicates that vehicle crash and capabilities 500 data is attached. When an ESInet is deployed, the MNO only needs to 501 recognize the call as an emergency call and route it to an ESInet. 502 The ESInet can recognize the call as an ACN with vehicle data and can 503 route the call to an NG-ACN capable PSAP. Such a PSAP can interpret 504 the vehicle data sent with the call and make it available to the call 505 taker. 507 [I-D.ietf-ecrit-ecall] registers new service URN children within the 508 "sos" subservice. These URNs request NG-ACN resources, and 509 differentiate between manually and automatically triggered NG-ACN 510 calls (which might be subject to different treatment depending on 511 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 512 are "urn:service:sos.ecall.automatic" and 513 "urn:service:sos.ecall.manual". The same service URNs are used for 514 ACN as for eCall since in any region only one of these is supported, 515 making a distinction unnecessary. (Further, PSAP equipment might 516 support multiple data formats, allowing a PSAP to handle a vehicle 517 that erroneously sent the wrong data object.) 518 Note that in North America, routing queries performed by clients 519 outside of an ESInet typically treat all sub-services of "sos" 520 identically to "sos" with no sub-service. However, the Request-URI 521 header field retains the full sub-service; route and handling 522 decisions within an ESInet or PSAP can take the sub-service into 523 account. For example, in a region with multiple cooperating PSAPs, 524 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 525 one that specializes in vehicle-related incidents. 527 Migration of the three architectural models to next-generation (all- 528 IP) is described below. 530 In the TSP model, the IVS transmits crash and location data to the 531 TSP either by re-using the mechanisms and data objects described 532 here, or using a proprietary mechanism. In an emergency, the TSP 533 bridges in the PSAP and the TSP transmits crash and other data to the 534 PSAP using the mechanisms and data objects described here. There is 535 a three-way call between the vehicle, the TSP, and the PSAP, allowing 536 communication between the PSAP call taker, the TSP call taker, and 537 the vehicle occupants (who might be unconscious). The TSP relays 538 PSAP requests and vehicle responses. 540 proprietary 541 ///----\\\ or standard +------+ standard +------+ 542 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 543 \\\----/// crash + other data +------+ crash + other data +------+ 545 Figure 4: Next-Generation TSP Model 547 The vehicle manufacturer and the TSP can choose to use the same 548 mechanisms and data objects on the left call leg in Figure 4 as on 549 the right. (Note that the TSP model can be more difficult when the 550 vehicle is in a different country than the TSP (e.g., a US resident 551 driving in Canada or Mexico) because of the additional complexity in 552 choosing the correct PSAP based on vehicle location performed by a 553 TSP in a different country.) 555 In the direct model, the IVS communicates crash data to the PSAP 556 directly using the mechanisms and data objects described here. 558 ///----\\\ NG emergency call +------+ 559 ||| IVS |||----------------------------------------->+ PSAP | 560 \\\----/// crash + other data +------+ 562 Figure 5: Next-Generation Direct Model 564 In the paired model, the IVS uses a Bluetooth link to a previously- 565 paired handset to establish an emergency call with the PSAP; it is 566 undefined what facilities are or will be available for transmitting 567 crash data through the Bluetooth link to the handset for inclusion in 568 an NG emergency call. Hence, manufacturers that use the paired model 569 for legacy calls might choose to adopt either the direct or TSP 570 models for next-generation calls. 572 +---+ 573 ///----\\\ (undefined) | H | standard +------+ 574 ||| IVS |||------------------>| S +------------------->+ PSAP | 575 \\\----/// (undefined) +---+ crash + other data +------+ 577 Figure 6: Next-Generation Paired Model 579 If the call is routed to a PSAP that is not capable of processing the 580 vehicle data, the PSAP ignores (or does not receive) the vehicle 581 data. This is detectable by the IVS or TSP when the status response 582 to the INVITE (e.., 200 OK) lacks an eCall control structure 583 acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or 584 TSP then proceeds as it would for a CS-ACN call (e.g., verbal 585 conveyance of data) 587 6. Call Setup 589 A next-generation In-Vehicle System (IVS) initiates an NG-ACN call 590 with a SIP INVITE using one of the SOS sub-services 591 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, 592 standard sets of crash data and capabilities data encoded in 593 standardized and registered formats, attached as additional data 594 blocks as specified in Section 4.1 of 595 [I-D.ietf-ecrit-additional-data]. As described in that document, 596 each data block is identified by its MIME content-type, and pointed 597 to by a CID URL in a Call-Info header with a 'purpose' parameter 598 value corresponding to the data block. 600 Should new data blocks be needed (e.g., in other regions or in the 601 future), the steps required during standardization are: 603 o A set of data is standardized by an SDO or appropriate 604 organization 606 o A MIME Content-Type for the crash data set is registered with IANA 608 * If the data is specifically for use in emergency calling, the 609 MIME type is normally under the 'application' type with a 610 subtype starting with 'EmergencyCallData.' 612 * If the data format is XML, then by convention the name has a 613 suffix of '+xml' 615 o The item is registered in the Emergency Call Additional Data 616 registry, as defined in Section 9.1.7 of 617 [I-D.ietf-ecrit-additional-data] 619 * For emergency-call-specific formats, the registered name is the 620 root of the MIME Content-Type (not including the 621 'EmergencyCallData' prefix and any suffix such as '+xml') as 622 described in Section 4.1 of [I-D.ietf-ecrit-additional-data]. 624 When placing an emergency call: 626 o The crash data set is created and encoded per its specification 628 o IVS capability data is encoded per the specification in 629 [I-D.ietf-ecrit-ecall] as extended in this document 631 o The crash data set and capabilities data are attached to the 632 emergency call INVITE as specified in Section 4.1 of 633 [I-D.ietf-ecrit-additional-data], that is, as MIME body parts 634 identified by the MIME Content-Type in the body part's Content- 635 Type header field 637 o Each body part is assigned a unique identifier label in the 638 Content-ID header field of the body part 640 o Call-Info header fields at the top level of the INVITE are added 641 that reference the crash data and capabilities data and identify 642 each by its MIME root (as registered in the Emergency Call 643 Additional Data registry) 645 * The crash and capabilities data are referenced in Call-Info 646 header fields by CID URLs that contain the unique Content ID 647 assigned to the body part 649 * The crash and capabilities data are identified in the Call-Info 650 header fields by a 'purpose' parameter whose value is 651 'EmergencyCallData.' concatenated with the specific data 652 block's entry in the Emergency Call Additional Data registry 654 * A Call-Info header field can be either solely to reference one 655 item of data (and hence have only the one URL) or can also 656 contain other URLs referencing other data 658 o Any additional data sets are included by following the same steps 660 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 661 the Association of Public-Safety Communications Officials (APCO) and 662 the National Emergency Number Association (NENA) [VEDS]. The 663 'application/EmergencyCallData.VEDS+xml' MIME content-type is used to 664 identify it. The 'VEDS' entry in the Emergency Call Additional Data 665 registry is used to construct a 'purpose' parameter value for 666 conveying VEDS data in a Call-Info header. 668 The VEDS data is attached as a body part with MIME content type 669 'application/EmergencyCallData.VEDS+xml' which is pointed at by a 670 Call-Info URL of type CID with a 'purpose' parameter of 671 'EmergencyCallData.VEDS'. 673 Entities along the path between the vehicle and the PSAP are able to 674 identify the call as an ACN call and handle it appropriately. The 675 PSAP is able to identify the crash data as well as any other 676 additional data attached to the INVITE by examining the Call-Info 677 header fields for 'purpose' parameters whose values start with 678 'EmergencyCallData.' The PSAP is able to access the data it is 679 capable of handling and is interested in by checking the 'purpose' 680 parameter values. 682 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 683 up and other normative requirements with the exception that in this 684 document, support for the eCall MSD is OPTIONAL and support for VEDS 685 in REQUIRED. This document also extends the metadata/control object 686 defined in [I-D.ietf-ecrit-ecall] by adding new elements, attributes, 687 and values. 689 6.1. Call Routing 691 An Emergency Services IP Network (ESInet) is a network operated by or 692 on behalf of emergency services authorities. It handles emergency 693 call routing and processing before delivery to a PSAP. In the 694 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 695 architecture adopted by EENA, each PSAP is connected to one or more 696 ESInets. Each originating network is also connected to one or more 697 ESInets. The ESInets maintain policy-based routing rules which 698 control the routing and processing of emergency calls. The 699 centralization of such rules within ESInets provides for a cleaner 700 separation between the responsibilities of the originating network 701 and that of the emergency services network, and provides greater 702 flexibility and control over processing of emergency calls by the 703 emergency services authorities and PSAPs. This makes it easier to 704 react quickly to unusual situations that require changes in how 705 emergency calls are routed or handled (e.g., a natural disaster 706 closes a PSAP), as well as ease in making long-term changes that 707 affect such routing (e.g., cooperative agreements to specially handle 708 calls requiring translation or relay services). 710 In an environment that uses ESInets, the originating network need 711 only detect that the service URN of an emergency call is or starts 712 with "sos", passing all types of emergency calls to an ESInet. The 713 ESInet is then responsible for routing such calls to an appropriate 714 PSAP. In an environment without an ESInet, the emergency services 715 authorities and the originating carriers determine how such calls are 716 routed. 718 7. eCall Metadata/Control Extensions 720 This document extends the eCall metadata/control structure defined in 721 [I-D.ietf-ecrit-ecall] by adding new elements, attributes, and 722 values. 724 The element is permitted in a control block sent by the IVS 725 to the PSAP, to acknowledge receipt of a request by the PSAP and 726 indicate if the request was carried out, when that request would 727 not otherwise be acknowledged (if the PSAP requests the vehicle to 728 send data and the vehicle does so, the data serves as a success 729 acknowledgement). 731 A new element is added; used in a control block 732 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 733 inform the PSAP of the vehicle capabilities. Child elements 734 contain all actions and data types supported by the vehicle and 735 all available lamps (lights) and cameras. 737 New request values are added to the element to enable 738 the PSAP to request the vehicle to perform actions. 740 Mandatory Actions (the IVS and the PSAP MUST support): 742 o Transmit data object (VEDS MUST be supported; MSD MAY be 743 supported) 745 Optional Actions (the IVS and the PSAP MAY support): 747 o Play and/or display static (pre-defined) message 748 o Speak/display dynamic text (text supplied in action) 749 o Flash or turn on or off a lamp (light) 750 o Honk horn 751 o Enable a camera 753 The element indicates the object being acknowledged (i.e., a 754 data object or a element), and reports success or failure. 756 The element has child elements to indicate 757 the actions supported by the IVS. 759 The element contains attributes to indicate the request and 760 to supply any needed information, and MAY contain a child 761 element to contain the text for a dynamic message. The 'action' 762 attribute is mandatory and indicates the specific action. 763 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 764 allowed values; this document adds new values to that registry in 765 Table 3. 767 7.1. New values for the 'action' attribute' 769 The following new "action" values are defined: 771 'msg-static' displays or plays a predefined message (translated as 772 appropriate for the language of the vehicle's interface). A registry 773 is created in Section 12.5 for messages and their IDs. Vehicles 774 include the highest registered message in their 775 element to indicate support for all messages up to and including the 776 indicated value. 778 'msg-dynamic' displays or speaks (via text-to-speech) a dynamic 779 message included in the request. 781 'honk' sounds the horn. 783 'lamp' turns a lamp (light) on, off, or flashes. 785 'enable-camera' adds a one-way media stream (established via SIP re- 786 INVITE sent by the vehicle) to enable the PSAP call taker to view a 787 feed from a camera. 789 Note that there is no 'request' action to play dynamic media (such as 790 an audio message). The PSAP can send a SIP re-INVITE to establish a 791 one-way media stream for this purpose. 793 7.2. element extensions 795 The element is extended to be transmitted by the IVS to the 796 PSAP to acknowledge receipt of a element that requested the 797 IVS to perform an action other than transmitting a data object (e.g., 798 a request to display a message would be acknowledged, but a request 799 to transmit a data object would not result in a separate 800 element being sent, since the data object itself serves as 801 acknowledgment.) An element sent by an IVS references the 802 unique ID of the request being acknowledged, indicates whether the 803 request was successfully performed, and if not, optionally includes 804 an explanation. 806 The element has the following new child elements: 808 7.2.1. New Child Element of the element 810 The element has the following new child element: 812 Name: actionResult 813 Usage: Optional 814 Description: An element indicates the result of an 815 action (other than a 'send-data' action). When an element 816 is in response to a control object with multiple 817 elements (that are not 'send-data' actions), the element 818 contains an element for each. 819 The element has the following 820 attributes: 822 Name: action 823 Usage: Mandatory 824 Type: token 825 Description: Contains the value of the 'action' attribute of the 826 element 828 Name: success 829 Usage: Mandatory 830 Type: Boolean 831 Description: Indicates if the action was successfully 832 accomplished 834 Name: reason 835 Usage: Conditional 836 Type: token 837 Description: Used when 'success' is "False", this attribute 838 contains a reason code for a failure. A registry for reason 839 codes is defined in Section 12.6. 841 Name: details 842 Usage: optional 843 Type: string 844 Description: Contains further explanation of the circumstances of 845 a success or failure. The contents are implementation-specific 846 and human-readable. 848 Example: 850 Example: 853 7.2.2. Ack Examples 855 856 862 863 864 866 868 870 Figure 7: Ack Example from IVS to PSAP 872 7.3. The element 874 The element is transmitted by the IVS to indicate to 875 the PSAP its capabilities. No attributes for this element are 876 currently defined. The following child elements are defined: 878 7.3.1. Child Elements of the element 880 The element has the following child elements: 882 Name: request 883 Usage: Mandatory 884 Description: The element contains a child 885 element per action supported by the vehicle. 887 Because support for a 'send-data' action is REQUIRED, a 888 child element with a "send-data" 'action' attribute is also 889 REQUIRED. The 'supported-datatypes' attribute is REQUIRED in this 890 element within a element, and MUST 891 contain at a minimum the 'VEDS' data block value; it SHOULD 892 contain all data blocks supported by the IVS. 894 All other actions are OPTIONAL. 896 If the "msg-static" action is supported, a child element 897 with a "msg-static" 'action' attribute is sent, with a 'msgid' 898 attribute set to the highest supported static message supported by 899 the vehicle. A registry is created in Section 12.5 to map 'msgid' 900 values to static text messages. By sending the highest supported 901 static message number in its element, the vehicle 902 indicates its support for all static messages in the registry up 903 to and including that value. 905 If the "lamp" action is supported, a child element with 906 a "lamp" 'action' is sent, with a 'supported-lamps' attribute set 907 to all supported lamp IDs. 909 If the "enable-camera" action is supported, a child 910 element with an "enable-camera" 'action' is sent, with a 911 'supported-cameras' attribute set to all supported camera IDs. 913 Examples: 914 915 917 918 920 7.3.2. Capabilities Example 922 923 929 930 931 934 935 936 937 938 940 942 Figure 8: Capabilities Example 944 7.4. element extensions 946 This document extends the element to be permitted one or 947 more times on its own or as a child elements of a 948 element. The following new attributes, values, and child elements 949 are defined for the element: 951 7.4.1. New Attributes of the element 953 The element has the following new attributes: 955 Name: msgid 956 Usage: Conditional 957 Type: int 958 Description: Mandatory with a "msg-static" action. Indicates the 959 identifier of the static message to be displayed and/or spoken for 960 the vehicle occupants. This document establishes an IANA registry 961 for messages and their IDs, in Section 12.5 962 Example: msgid="3" 964 Name: persistance 965 Usage: Optional 966 Type: duration 967 Description: Specifies how long to carry on the specified action, 968 for example, how long to continue honking or flashing. If absent, 969 the default is for the duration of the ACN call. 970 Example: persistance="PT1H" 972 Name: supported-datatypes 973 Usage: Conditional 974 Type: string 975 Description: Used with a 'send-data' action in a element 976 that is a child of a element, this attribute lists 977 all data blocks that the vehicle can transmit, using the same 978 identifier as in the 'purpose' attribute in a Call-Info header 979 field to point to the data block. Permitted values are contained 980 in the 'Emergency Call Data Types' IANA registry established in 981 [I-D.ietf-ecrit-additional-data]. Multiple values are separated 982 with a semicolon. 983 Example: supported-datatypes="VEDS; eCall.MSD" 985 Name: lamp-action 986 Usage: Conditional 987 Type: token 988 Description: Used with a 'lamp' action, indicates if the lamp is to 989 be illuminated, turned off, or flashed. Permitted values are 990 'on', 'off', and 'flash'. 992 Example: lamp-action="flash" 994 Name: lamp-ID 995 Usage: Conditional 996 Type: token 997 Description: Used with a 'lamp' action, indicates which lamp the 998 action affects. Permitted values are contained in the registry of 999 lamp-ID tokens created in Section 12.7 1000 Example: lamp-ID="hazard" 1002 Name: supported-lamps 1003 Usage: Conditional 1004 Type: string 1005 Description: Used with a 'lamp' action in a element that 1006 is a child of a element, this attribute lists all 1007 supported lamps, using values in the registry of lamp-ID tokens 1008 created in Section 12.7. Multiple values are separated with a 1009 semicolon. 1010 Example: supported-lamps="head; interior; fog-front; fog-rear; 1011 brake; position-front; position-rear; turn-left; turn-right; 1012 hazard" 1014 Name: camera-ID 1015 Usage: Conditional 1016 Type: token 1017 Description: Used with an 'enable-camera' action, indicates which 1018 camera to enable. Permitted values are contained in the registry 1019 of camera-ID tokens created in Section 12.8. When a vehicle 1020 camera is enabled, the IVS sends a re-INVITE to negotiate a one- 1021 way media stream for the camera. 1022 Example: camera-ID="backup" 1024 Name: supported-cameras 1025 Usage: Conditional 1026 Type: string 1027 Description: Used with an 'enable-camera' action in a 1028 element that is a child of a element, this attribute 1029 lists all cameras that the vehicle supports (can add as a video 1030 feed in the current dialog), using the same identifiers as are 1031 used in the 'camera-ID' attribute (contained in the camera ID 1032 registry in Section 12.8). Multiple values are separated with a 1033 semicolon. 1034 Example: supported-cameras="backup; interior" 1036 7.4.2. New Child Elements of the element 1038 The element has the following new child elements: 1040 Name: text 1041 Usage: Conditional 1042 Type: string 1043 Description: Used within a element to 1044 contain the text to be displayed and/or spoken (via text-to- 1045 speech) for the vehicle occupants. 1046 Example: Emergency authorities are aware of your incident and 1047 location. Due to a multi-vehicle incident in your area, no one is 1048 able to speak with you right now. Please remain calm. We will 1049 assist you soon. 1051 7.4.3. Request Example 1053 1054 1060 1061 1063 1064 1065 Remain calm. Help is on the way. 1066 1068 1070 Figure 9: Request Example 1072 8. Test Calls 1074 An NG-ACN test call is a call that is recognized and treated to some 1075 extent as an NG-ACN call but not given emergency call treatment and 1076 not handled by a call taker. The specific handling of test NG-ACN 1077 calls is not itself standardized; the test call facility is intended 1078 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 1079 successfully established with voice and/or other media communication. 1080 The IVS might also be able to verify that the crash data was 1081 successfully received. 1083 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 1084 ability to utilize test call functionality from Section 15 of 1085 [RFC6881]. A service URN starting with "test." indicates a test 1086 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 1087 for test calls. 1089 MNOs, emergency authorities, ESInets, and PSAPs determine how to 1090 treat a vehicle call requesting the "test" service URN so that the 1091 desired functionality is tested, but this is outside the scope of 1092 this document. (One possibility is that MNOs route such calls as 1093 non-emergency calls to an ESInet, which routes them to a PSAP that 1094 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 1095 data acknowledgment, and plays an audio clip (for example, saying 1096 that the call reached an appropriate PSAP and the vehicle data was 1097 successfully processed) in addition to supporting media loopback per 1098 [RFC6881]). 1100 Note that since test calls are placed using "test" as the parent 1101 service URN and "sos" as a child, such calls are not treated as an 1102 emergency call and so some functionality might not apply (such as 1103 preemption or service availability for devices lacking service ("non- 1104 service-initialized" or "NSI" devices) if those are available for 1105 emergency calls). 1107 9. Example 1109 Figure 10 shows an NG-ACN call routing. The mobile network operator 1110 (MNO) routes the call to an Emergency services IP Network (ESInet), 1111 as for any emergency call. The ESInet routes the call to an 1112 appropriate NG-ACN-capable PSAP (using location information and the 1113 fact that that it is an NG-ACN call). The call is processed by the 1114 Emergency Services Routing Proxy (ESRP), as the entry point to the 1115 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 1116 PSAP, where the call is received by a call taker. (In deployments 1117 where there is no ESInet, the MNO itself routes the call directly to 1118 an appropriate NG-ACN-capable PSAP.) 1119 +---------------------------------------+ 1120 | | 1121 +------------+ | +-------+ | 1122 | | | | PSAP2 | | 1123 | | | +-------+ | 1124 | Originating| | | 1125 | Mobile | | +------+ +-------+ | 1126 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1127 | | | +------+ +-------+ | 1128 | | | | 1129 +------------+ | +-------+ | 1130 | | PSAP3 | | 1131 | +-------+ | 1132 | | 1133 | | 1134 | | 1135 | ESInet | 1136 +---------------------------------------+ 1138 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1140 The example, shown in Figure 11, illustrates a SIP emergency call 1141 INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS 1142 data block), and capabilities data (an eCall metadata/control block 1143 with extensions defined in this document) attached to the SIP INVITE 1144 message. The INVITE has a request URI containing the 1145 'urn:service:sos.ecall.automatic' service URN. 1147 The example VEDS data structure shows information about about a 1148 crashed vehicle. The example communicates that the car is a model 1149 year 2015 Saab 9-5 (a car which does not exist). The front airbag 1150 deployed as a consequence of the crash. The 1151 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 1152 passenger car (the code is set to '101') and that it is not a 1153 convertible (the 'ConvertibleIndicator' value is set to 'false'). 1155 The 'VehicleCrashPulse' element provides further information about 1156 the crash, namely that the force of impact based on the change in 1157 velocity over the duration of the crash pulse was 100 MPH. The 1158 principal direction of the force of the impact is set to '12' (which 1159 refers to 12 O'Clock, corresponding to a frontal collision). This 1160 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1161 element. 1163 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1164 quarter turns in concert with a rollover expressed as a number; in 1165 our case 1. 1167 No roll bar was deployed, as indicated in 1168 'VehicleRollbarDeployedIndicator' being set to 'false'. 1170 Next, there is information indicating seatbelt and seat sensor data 1171 for individual seat positions in the vehicle. In our example, 1172 information from the driver seat is available (value '1' in the 1173 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1174 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1175 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1176 and the seat sensor determined that the seat was occupied 1177 ('VehicleSeatOccupiedIndicator' element). 1179 Finally, information about the weight of the vehicle, which is 600 1180 kilogram in our example. 1182 In addition to the information about the vehicle, further indications 1183 are provided, namely the presence of fuel leakage 1184 ('FuelLeakingIndicator' element), an indication whether the vehicle 1185 was subjected to multiple impacts ('MultipleImpactsIndicator' 1186 element), the orientation of the vehicle at final rest 1187 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1188 that there are no parts of the vehicle on fire (the 1189 'VehicleFireIndicator' element). 1191 INVITE urn:service:sos.ecall.automatic SIP/2.0 1192 To: urn:service:sos.ecall.automatic 1193 From: ;tag=9fxced76sl 1194 Call-ID: 3848276298220188511@atlanta.example.com 1195 Geolocation: 1196 Geolocation-Routing: no 1197 Call-Info: cid:1234567890@atlanta.example.com; 1198 purpose=EmergencyCallData.VEDS 1199 Call-Info: cid:1234567892@atlanta.example.com; 1200 purpose=EmergencyCallData.ecall.control 1201 Accept: application/sdp, application/pidf+xml, 1202 application/emergencyCallData.eCall.control+xml 1203 Recv-Info: emergencyCallData.eCall 1204 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1205 SUBSCRIBE, NOTIFY, UPDATE 1206 CSeq: 31862 INVITE 1207 Content-Type: multipart/mixed; boundary=boundary1 1208 Content-Length: ... 1210 --boundary1 1211 Content-Type: application/sdp 1213 ...Session Description Protocol (SDP) goes here 1214 --boundary1 1215 Content-Type: application/pidf+xml 1216 Content-ID: 1218 1219 1227 1228 1229 1230 1231 -34.407 150.883 1232 1233 1234 278 1235 1236 1237 1238 1239 gps 1240 1241 2012-04-5T10:18:29Z 1242 1M8GDM9A_KP042788 1243 1244 1246 --boundary1 1247 Content-Type: application/EmergencyCallData.VEDS+xml 1248 Content-ID: 1234567890@atlanta.example.com 1249 Content-Disposition: by-reference;handling=optional 1251 1252 1256 1257 1258 Saab 1259 1260 1261 9-5 1263 1264 1266 2015 1267 1268 1269 FRONT 1270 true 1271 1272 1273 false 1274 MAIN 1275 1277 101 1278 1279 1280 1281 1283 100 1284 1285 1287 MPH 1288 1289 12 1290 1291 1 1292 1293 1294 false 1295 1296 1297 1 1298 1299 true 1300 1301 true 1302 1303 true 1304 1305 1306 1308 1310 600 1311 1312 1314 kilogram 1315 1316 1317 1318 true 1319 false 1320 true 1321 Driver 1322 1323 false 1324 1325 1327 --boundary1 1328 Content-Type: application/EmergencyCallData.ecall.control+xml 1329 Content-ID: 1234567892@atlanta.example.com 1330 Content-Disposition: by-reference;handling=optional 1332 1333 1339 1340 1341 1345 1346 1347 1348 1350 1352 1354 --boundary1-- 1356 Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call 1358 10. Security Considerations 1360 Since this document relies on [I-D.ietf-ecrit-ecall] and 1361 [I-D.ietf-ecrit-additional-data], the security considerations 1362 described there and in [RFC5069] apply here. Implementors are 1363 cautioned to read and understand the discussion in those documents. 1365 As with emergency service systems where location data is supplied or 1366 determined with the assistance of an end host, there is the 1367 possibility that that location is incorrect, either intentially 1368 (e.g., in a denial of service attack against the emergency services 1369 infrastructure) or due to a malfunctioning device. The reader is 1370 referred to [RFC7378] for a discussion of some of these 1371 vulnerabilities. 1373 In addition to the security considerations discussion specific to the 1374 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1375 MAY decline to carry out any requested action (e.g., if the vehicle 1376 requires but is unable to verify the certificate used to sign the 1377 request). The vehicle MAY use any value in the reason registry to 1378 indicate why it did not take an action (e.g., the generic "unable" or 1379 the more specific "security-failure"). 1381 11. Privacy Considerations 1383 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1384 builds on [I-D.ietf-ecrit-additional-data], the data structures 1385 specified there, and the corresponding privacy considerations 1386 discussed there, apply here as well. The VEDS data structure 1387 contains optional elements that can carry identifying and personal 1388 information, both about the vehicle and about the owner, as well as 1389 location information, and so needs to be protected against 1390 unauthorized disclosure, as discussed in 1391 [I-D.ietf-ecrit-additional-data]. Local regulations may impose 1392 additional privacy protection requirements. 1394 12. IANA Considerations 1396 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1397 content type, and adds "VEDS" to the Emergency Call Additional Data 1398 registry. This document adds to and creates new sub-registries in 1399 the 'eCall Control Data' registry created in [I-D.ietf-ecrit-ecall]. 1401 12.1. MIME Content-type Registration for 'application/ 1402 EmergencyCall.VEDS+xml' 1404 This specification requests the registration of a new MIME type 1405 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1406 RFC 3023 [RFC3023]. 1408 MIME media type name: application 1410 MIME subtype name: EmergencyCallData.VEDS+xml 1412 Mandatory parameters: none 1414 Optional parameters: charset 1416 Indicates the character encoding of enclosed XML. 1418 Encoding considerations: Uses XML, which can employ 8-bit 1419 characters, depending on the character encoding used. See 1420 Section 3.2 of RFC 3023 [RFC3023]. 1422 Security considerations: 1424 This content type is designed to carry vehicle crash data 1425 during an emergency call. 1427 This data can contain personal information including vehicle 1428 VIN, location, direction, etc. Appropriate precautions need to 1429 be taken to limit unauthorized access, inappropriate disclosure 1430 to third parties, and eavesdropping of this information. 1431 Please refer to Section 7 and Section 8 of 1432 [I-D.ietf-ecrit-additional-data] for more information. 1434 When this content type is contained in a signed or encrypted 1435 body part, the enclosing multipart (e.g., multipart/signed or 1436 multipart/encrypted) has the same Content-ID as the data part. 1437 This allows an entity to identify and access the data blocks it 1438 is interested in without having to dive deeply into the message 1439 structure or decrypt parts it is not interested in. (The 1440 'purpose' parameter in a Call-Info header field identifies the 1441 data, and the CID URL points to the data block in the body, 1442 which has a matching Content-ID body part header field). 1444 Interoperability considerations: None 1446 Published specification: [VEDS] 1448 Applications which use this media type: Emergency Services 1449 Additional information: None 1451 Magic Number: None 1453 File Extension: .xml 1455 Macintosh file type code: 'TEXT' 1457 Persons and email addresses for further information: Randall 1458 Gellensm rg+ietf (at) randy.pensive.org; Hannes Tschofenig, 1459 Hannes.Tschofenig (at) gmx.net 1461 Intended usage: LIMITED USE 1463 Author: This specification is a work item of the IETF ECRIT 1464 working group, with mailing list address . 1466 Change controller: The IESG 1468 12.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1469 Data registry 1471 This specification requests IANA to add the 'VEDS' entry to the 1472 Emergency Call Additional Data registry, with a reference to this 1473 document. The Emergency Call Additional Data registry has been 1474 established by [I-D.ietf-ecrit-additional-data]. 1476 12.3. Additions to the eCall Control Extension Registry 1478 This document uses the "eCall Control Extension Registry" to add new 1479 elements, attributes, and values to the eCall metadata/control 1480 object, as per [I-D.ietf-ecrit-ecall]: 1482 +-----------+---------------------+---------------------------------+ 1483 | Type | Name | Description | 1484 +-----------+---------------------+---------------------------------+ 1485 | Attribute | msgid | See Section 7.2 of this | 1486 | | | document | 1487 | | | | 1488 | Attribute | persistance | See Section 7.2 of this | 1489 | | | document | 1490 | | | | 1491 | Attribute | supported-datatypes | See Section 7.2 of this | 1492 | | | document | 1493 | | | | 1494 | Attribute | lamp-action | See Section 7.2 of this | 1495 | | | document | 1496 | | | | 1497 | Attribute | lamp-ID | See Section 7.2 of this | 1498 | | | document | 1499 | | | | 1500 | Attribute | supported-lamps | See Section 7.2 of this | 1501 | | | document | 1502 | | | | 1503 | Attribute | camera-ID | See Section 7.2 of this | 1504 | | | document | 1505 | | | | 1506 | Element | text | See Section 7.4.2 of this | 1507 | | | document | 1508 | | | | 1509 | Element | actionResult | See Section 7.2.1 of this | 1510 | | | document | 1511 | | | | 1512 | Attribute | action | See Section 7.2.1 of this | 1513 | | | document | 1514 | | | | 1515 | Attribute | success | See Section 7.2.1 of this | 1516 | | | document | 1517 | | | | 1518 | Attribute | reason | See Section 7.2.1 of this | 1519 | | | document | 1520 | | | | 1521 | Attribute | details | See Section 7.2.1 of this | 1522 | | | document | 1523 +-----------+---------------------+---------------------------------+ 1525 Table 2: eCall Control Extension Registry New Values 1527 12.4. eCall Action Extensions 1529 This document adds new values for the 'action' attribute of the 1530 element in the "eCall Control Action Registry" registry 1531 created by [I-D.ietf-ecrit-ecall]. 1533 +---------------+------------------------------+ 1534 | Name | Description | 1535 +---------------+------------------------------+ 1536 | msg-static | Section 7.1 of this document | 1537 | | | 1538 | msg-dynamic | Section 7.1 of this document | 1539 | | | 1540 | honk | Section 7.1 of this document | 1541 | | | 1542 | lamp | Section 7.1 of this document | 1543 | | | 1544 | enable-camera | Section 7.1 of this document | 1545 +---------------+------------------------------+ 1547 Table 3: eCall Control Action Registry New Values 1549 12.5. eCall Static Message Registry 1551 This document creates a new sub-registry called "eCall Static Message 1552 Registry" in the "eCall Control Data" registry established by 1553 [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected 1554 to support all static messages translated into all languages 1555 supported by the vehicle, it is important to limit the number of such 1556 messages. As defined in [RFC5226], this registry operates under 1557 "Publication Required" rules, which require a stable, public document 1558 and imply expert review of the publication. The expert should 1559 determine that the document has been published by an appropriate 1560 emergency services organization (e.g., NENA, EENA, APCO) or by the 1561 IETF with input from an emergency services organization, and that the 1562 proposed message is sufficiently distinguishable from other messages. 1564 The content of this registry includes: 1566 ID: An integer identifier to be used in the 'msgid' attribute of an 1567 eCall control element. 1569 Message: The text of the message. Messages are listed in the 1570 registry in English; vehicles are expected to implement 1571 translations into languages supported by the vehicle. 1573 When new messages are added to the registry, the message text is 1574 determined by the registrant; IANA assigns the IDs. Each message is 1575 assigned a consecutive integer value as its ID. This allows an IVS 1576 to indicate by a single integer value that it supports all messages 1577 with that value or lower. 1579 The initial set of values is listed in Table 4. 1581 +----+--------------------------------------------------------------+ 1582 | ID | Message | 1583 +----+--------------------------------------------------------------+ 1584 | 1 | Emergency authorities are aware of your incident and | 1585 | | location, but are unable to speak with you right now. We | 1586 | | will help you as soon as possible. | 1587 +----+--------------------------------------------------------------+ 1589 Table 4: eCall Static Message Registry 1591 12.6. eCall Reason Registry 1593 This document creates a new sub-registry called "eCall Reason 1594 Registry" in the "eCall Control Data" registry established by 1595 [I-D.ietf-ecrit-ecall]. This new sub-registry contains values for 1596 the 'reason' attribute of the element. As defined in 1597 [RFC5226], this registry operates under "Expert Review" rules. The 1598 expert should determine that the proposed reason is sufficiently 1599 distinguishable from other reasons and that the proposed description 1600 is understandable and correctly worded. 1602 The content of this registry includes: 1604 ID: A short string identifying the reason, for use in the 'reason' 1605 attribute of an element. 1607 Description: A description of the reason. 1609 The initial set of values is listed in Table 5. 1611 +------------------+------------------------------------------------+ 1612 | ID | Description | 1613 +------------------+------------------------------------------------+ 1614 | unsupported | The 'action' is not supported. | 1615 | | | 1616 | unable | The 'action' could not be accomplished. | 1617 | | | 1618 | data-unsupported | The data item referenced in a 'send-data' | 1619 | | request is not supported. | 1620 | | | 1621 | security-failure | The authenticity of the request or the | 1622 | | authority of the requestor could not be | 1623 | | verified. | 1624 +------------------+------------------------------------------------+ 1626 Table 5: eCall Reason Registry 1628 12.7. eCall Lamp ID Registry 1630 This document creates a new sub-registry called "eCall Lamp ID 1631 Registry" in the "eCall Control Data" registry established by 1632 [I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names 1633 of automotive lamps (lights). As defined in [RFC5226], this registry 1634 operates under "Expert Review" rules. The expert should determine 1635 that the proposed lamp name is clearly understandable and is 1636 sufficiently distinguishable from other lamp names. 1638 The content of this registry includes: 1640 Name: The identifier to be used in the 'lamp-ID' attribute of an 1641 eCall control element. 1643 Description: A description of the lamp (light). 1645 The initial set of values is listed in Table 6. 1647 +----------------+---------------------------------------------+ 1648 | Name | Description | 1649 +----------------+---------------------------------------------+ 1650 | head | The main lamps used to light the road ahead | 1651 | | | 1652 | interior | Interior lamp, often at the top center | 1653 | | | 1654 | fog-front | Front fog lamps | 1655 | | | 1656 | fog-rear | Rear fog lamps | 1657 | | | 1658 | brake | Brake indicator lamps | 1659 | | | 1660 | position-front | Front position/parking/standing lamps | 1661 | | | 1662 | position-rear | Rear position/parking/standing lamps | 1663 | | | 1664 | turn-left | Left turn/directional lamps | 1665 | | | 1666 | turn-right | Right turn/directional lamps | 1667 | | | 1668 | hazard | Hazard/four-way lamps | 1669 +----------------+---------------------------------------------+ 1671 Table 6: eCall Lamp ID Registry Initial Values 1673 12.8. eCall Camera ID Registry 1675 This document creates a new sub-registry called "eCall Camera ID 1676 Registry" in the "eCall Control Data" registry established by 1677 [I-D.ietf-ecrit-ecall]. This new sub-registry standardizes the names 1678 of automotive camera. As defined in [RFC5226], this registry 1679 operates under "Expert Review" rules. The expert should determine 1680 that the proposed camera name is clearly understandable and is 1681 sufficiently distinguishable from other camera names. 1683 The content of this registry includes: 1685 Name: The identifier to be used in the 'camera-ID' attribute of an 1686 eCall control element. 1688 Description: A description of the camera. 1690 The initial set of values is listed in Table 7. 1692 +-------------+-----------------------------------------------------+ 1693 | Name | Description | 1694 +-------------+-----------------------------------------------------+ 1695 | backup | Shows what is behind the vehicle, e.g., often used | 1696 | | for driver display when the vehicle is in reverse. | 1697 | | Also known as rearview, reverse, etc. | 1698 | | | 1699 | left-rear | Shows view to the left and behind (e.g., left side | 1700 | | rear-view mirror or blind spot view) | 1701 | | | 1702 | right-rear | Shows view to the right and behind (e.g., right | 1703 | | side rear-view mirror or blind spot view) | 1704 | | | 1705 | forward | Shows what is in front of the vehicle | 1706 | | | 1707 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1708 | | collision detection systems), separate from backup | 1709 | | view | 1710 | | | 1711 | lane | Used by systems to identify road lane and/or | 1712 | | monitor vehicle's position within lane | 1713 | | | 1714 | interior | Shows the interior (e.g., driver) | 1715 | | | 1716 | night-front | Night-vision view of what is in front of the | 1717 | | vehicle | 1718 +-------------+-----------------------------------------------------+ 1720 Table 7: eCall Camera ID Registry Initial Values 1722 13. eCall Control Block Schema 1724 This section presents an XML schema of the eCall control block after 1725 applying the extensions defined in this document. Note that the text 1726 is normative; this schema is informative. 1728 1729 1737 1740 1743 1744 1745 1746 1747 1749 1750 1751 1754 1755 1756 1757 1758 1760 1761 1762 1763 1764 1766 1767 1770 1773 1775 1776 conditionally 1777 mandatory when @success='false" 1778 to indicate reason code for a 1779 failure 1780 1781 1782 1784 1785 1787 1788 1791 1792 1795 1797 1798 1799 1800 1802 1803 1804 1805 1806 1810 1813 1814 1815 1816 1817 1819 1820 1821 1822 1823 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1852 1854 Figure 12: eCall Control Block Schema 1856 14. Contributors 1858 We would like to thank Ulrich Dietz for his help with earlier 1859 versions of the original version of this document. 1861 15. Acknowledgements 1863 We would like to thank Michael Montag, Arnoud van Wijk, Ban Al-Bakri, 1864 Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback. 1866 16. Changes from Previous Versions 1868 16.1. Changes from draft-ietf-07 to draft-ietf-08 1870 o Moved much of the metadata/control object from 1871 [I-D.ietf-ecrit-ecall] to this document as extensions 1872 o Editorial clarifications and simplifications 1873 o Moved "Call Routing" to be a subsection of "Call Setup" 1874 o Deleted "Profile" section and moved some of its text into 1875 "Introduction" 1877 16.2. Changes from draft-ietf-06 to draft-ietf-07 1879 o Minor editorial changes 1881 16.3. Changes from draft-ietf-05 to draft-ietf-06 1883 o Added clarifying text regarding signed and encrypted data 1884 o Additional informative text in "Migration to Next-Generation" 1885 section 1886 o Additional clarifying text regarding security and privacy. 1888 16.4. Changes from draft-ietf-04 to draft-ietf-05 1890 o Reworded security text in main document and in MIME registration 1891 for the VEDS object 1893 16.5. Changes from draft-ietf-03 to draft-ietf-04 1895 o Added example VEDS object 1896 o Additional clarifications and corrections 1897 o Removed references from Abstract 1898 o Moved Document Scope section to follow Introduction 1900 16.6. Changes from draft-ietf-02 to draft-ietf-03 1902 o Additional clarifications and corrections 1904 16.7. Changes from draft-ietf-01 to draft-ietf-02 1906 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1907 aspects including the service URN; this document no longer 1908 proposes a unique service URN for non-eCall NG-ACN calls; the same 1909 service URN is now used for all NG-ACN calls including NG-eCall 1910 and non-eCall 1911 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1912 support it 1913 o Minor wording improvements and clarifications 1915 16.8. Changes from draft-ietf-00 to draft-ietf-01 1917 o Added further discussion of test calls 1918 o Added further clarification to the document scope 1919 o Mentioned that multi-region vehicles may need to support other 1920 crash notification specifications such as eCall 1921 o Minor wording improvements and clarifications 1923 16.9. Changes from draft-gellens-02 to draft-ietf-00 1925 o Renamed from draft-gellens- to draft-ietf- 1926 o Added text to Introduction to clarify that during a CS ACN, the 1927 PSAP call taker usually needs to listen to the data and transcribe 1928 it 1930 16.10. Changes from draft-gellens-01 to -02 1932 o Fixed case of 'EmergencyCallData', in accordance with changes to 1933 [I-D.ietf-ecrit-additional-data] 1935 16.11. Changes from draft-gellens-00 to -01 1937 o Now using 'EmergencyCallData' for purpose parameter values and 1938 MIME subtypes, in accordance with changes to 1939 [I-D.ietf-ecrit-additional-data] 1940 o Added reference to RFC 6443 1941 o Fixed bug that caused Figure captions to not appear 1943 17. References 1945 17.1. Normative References 1947 [I-D.ietf-ecrit-additional-data] 1948 Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1949 J. Winterbottom, "Additional Data Related to an Emergency 1950 Call", draft-ietf-ecrit-additional-data-38 (work in 1951 progress), April 2016. 1953 [I-D.ietf-ecrit-ecall] 1954 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1955 European eCall", draft-ietf-ecrit-ecall-07 (work in 1956 progress), February 2016. 1958 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1959 Requirement Levels", BCP 14, RFC 2119, 1960 DOI 10.17487/RFC2119, March 1997, 1961 . 1963 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1964 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1965 . 1967 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1968 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1969 . 1971 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1972 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1973 December 2005, . 1975 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1976 Emergency and Other Well-Known Services", RFC 5031, 1977 DOI 10.17487/RFC5031, January 2008, 1978 . 1980 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1981 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1982 DOI 10.17487/RFC5226, May 2008, 1983 . 1985 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1986 Presence Information Data Format Location Object (PIDF-LO) 1987 Usage Clarification, Considerations, and Recommendations", 1988 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1989 . 1991 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1992 Thomson, "Dynamic Extensions to the Presence Information 1993 Data Format Location Object (PIDF-LO)", RFC 5962, 1994 DOI 10.17487/RFC5962, September 2010, 1995 . 1997 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1998 "Framework for Emergency Calling Using Internet 1999 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 2000 2011, . 2002 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 2003 Communications Services in Support of Emergency Calling", 2004 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 2005 . 2007 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 2008 NENA Data Standardization Workgroup, , "Vehicular 2009 Emergency Data Set (VEDS) version 3", July 2012, 2010 . 2013 17.2. Informative references 2015 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 2016 Emergency Context Resolution with Internet Technologies", 2017 RFC 5012, DOI 10.17487/RFC5012, January 2008, 2018 . 2020 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 2021 Shanmugam, "Security Threats and Requirements for 2022 Emergency Call Marking and Mapping", RFC 5069, 2023 DOI 10.17487/RFC5069, January 2008, 2024 . 2026 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 2027 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 2028 December 2014, . 2030 [triage-2008] 2031 National Center for Injury Prevention and Control, and 2032 Centers for Disease Control and Prevention, 2033 "Recommendations from the Expert Panel: Advanced Automatic 2034 Collision Notification and Triage of the Injured Patient", 2035 2008, . 2037 [triage-2011] 2038 National Center for Injury Prevention and Control, and 2039 Centers for Disease Control and Prevention, "Guidelines 2040 for field triage of injured patients: recommendations of 2041 the National Expert Panel on Field Triage", January 2012, 2042 . 2047 Authors' Addresses 2049 Randall Gellens 2050 Consultant 2051 6755 Mira Mesa Blvd 123-151 2052 San Diego 92121 2053 US 2055 Email: rg+ietf@randy.pensive.org 2057 Brian Rosen 2058 NeuStar, Inc. 2059 470 Conrad Dr 2060 Mars, PA 16046 2061 US 2063 Email: br@brianrosen.net 2064 Hannes Tschofenig 2065 Individual 2067 Email: Hannes.Tschofenig@gmx.net 2068 URI: http://www.tschofenig.priv.at