idnits 2.17.1 draft-ietf-ecrit-car-crash-11.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 7 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 860 has weird spacing: '...dynamic displ...' == Line 863 has weird spacing: '... honk sound...' == Line 865 has weird spacing: '... lamp turns...' == Line 867 has weird spacing: '...-camera adds ...' -- The document date (September 22, 2016) is 2766 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 1827, but no explicit reference was found in the text == Unused Reference: 'RFC5031' is defined on line 1835, but no explicit reference was found in the text == Unused Reference: 'RFC5491' is defined on line 1845, but no explicit reference was found in the text == Unused Reference: 'RFC5962' is defined on line 1851, but no explicit reference was found in the text == Outdated reference: A later version (-27) exists of draft-ietf-ecrit-ecall-11 ** 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 (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Core Technology Consulting 4 Intended status: Standards Track B. Rosen 5 Expires: March 26, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 September 22, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-11.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 Emergency Call 26 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 adds 39 attribute values to the eCall metadata/control object to permit 40 greater functionality. This document registers a new INFO package 41 (identical to that registered for eCall but with the addition of the 42 VEDS MIME type). This document also describes legacy (circuit- 43 switched) ACN systems and their migration to next-generation 44 emergency calling, to provide background information and context. 46 Status of This Memo 48 This Internet-Draft is submitted in full conformance with the 49 provisions of BCP 78 and BCP 79. 51 Internet-Drafts are working documents of the Internet Engineering 52 Task Force (IETF). Note that other groups may also distribute 53 working documents as Internet-Drafts. The list of current Internet- 54 Drafts is at http://datatracker.ietf.org/drafts/current/. 56 Internet-Drafts are draft documents valid for a maximum of six months 57 and may be updated, replaced, or obsoleted by other documents at any 58 time. It is inappropriate to use Internet-Drafts as reference 59 material or to cite them other than as "work in progress." 61 This Internet-Draft will expire on March 26, 2017. 63 Copyright Notice 65 Copyright (c) 2016 IETF Trust and the persons identified as the 66 document authors. All rights reserved. 68 This document is subject to BCP 78 and the IETF Trust's Legal 69 Provisions Relating to IETF Documents 70 (http://trustee.ietf.org/license-info) in effect on the date of 71 publication of this document. Please review these documents 72 carefully, as they describe your rights and restrictions with respect 73 to this document. Code Components extracted from this document must 74 include Simplified BSD License text as described in Section 4.e of 75 the Trust Legal Provisions and are provided without warranty as 76 described in the Simplified BSD License. 78 Table of Contents 80 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 81 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 82 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 83 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9 84 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 85 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 86 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 87 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 16 88 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 89 9.1. New values for the 'action' attribute' . . . . . . . . . 18 90 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19 91 9.3. The element . . . . . . . . . . . . . . . . . . . . 19 92 9.4. The element . . . . . . . . . . . . . . . 20 93 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21 94 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 22 95 11.1. Overall Description . . . . . . . . . . . . . . . . . . 23 96 11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 23 97 11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 23 98 11.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 99 11.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 100 11.6. INFO Message Body Parts . . . . . . . . . . . . . . . . 24 101 11.7. Info Package Usage Restrictions . . . . . . . . . . . . 25 102 11.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 103 11.9. Info Package Security Considerations . . . . . . . . . . 25 104 11.10. Implementation Details . . . . . . . . . . . . . . . . . 25 105 11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 25 106 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 107 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 108 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 109 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 110 15.1. MIME Content-type Registration for 111 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 112 15.2. Registration of the 'VEDS' entry in the Emergency Call 113 Additional Data registry . . . . . . . . . . . . . . . . 33 114 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 33 115 15.4. Static Message Registry . . . . . . . . . . . . . . . . 34 116 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35 117 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36 118 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 119 17. Changes from Previous Versions . . . . . . . . . . . . . . . 37 120 17.1. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37 121 17.2. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 122 17.3. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 123 17.4. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 124 17.5. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 125 17.6. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 126 17.7. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 38 127 17.8. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 128 17.9. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 129 17.10. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 130 17.11. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 131 17.12. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39 132 17.13. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39 133 17.14. Changes from draft-gellens-00 to -01 . . . . . . . . . . 39 134 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 135 18.1. Normative References . . . . . . . . . . . . . . . . . . 40 136 18.2. Informative references . . . . . . . . . . . . . . . . . 41 137 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 139 1. Terminology 141 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 142 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 143 document are to be interpreted as described in [RFC2119]. 145 This document re-uses terminology defined in Section 3 of [RFC5012]. 147 Additionally, we use the following abbreviations: 149 +--------+----------------------------------------------------------+ 150 | Term | Expansion | 151 +--------+----------------------------------------------------------+ 152 | 3GPP | 3rd Generation Partnership Project | 153 | AACN | Advanced Automatic Crash Notification | 154 | ACN | Automatic Crash Notification | 155 | APCO | Association of Public-Safety Communications Officials | 156 | EENA | European Emergency Number Association | 157 | ESInet | Emergency Services IP network | 158 | GNSS | Global Navigation Satellite System (which includes | 159 | | various systems such as the Global Positioning System or | 160 | | GPS) | 161 | IVS | In-Vehicle System | 162 | MNO | Mobile Network Operator | 163 | MSD | eCall Minimum Set of Data | 164 | NENA | National Emergency Number Association | 165 | POTS | Plain Old Telephone Service (normal, circuit-switched | 166 | | voice calls) | 167 | PSAP | Public Safety Answering Point | 168 | TSP | Telematics Service Provider | 169 | VEDS | Vehicle Emergency Data Set | 170 +--------+----------------------------------------------------------+ 172 2. Introduction 174 Emergency calls made by in-vehicle systems (e.g., automatically in 175 the event of a crash or serious incident or manually by a vehicle 176 occupant) assist in significantly reducing road deaths and injuries 177 by allowing emergency services to respond quickly and appropriately 178 to the specifics of the incident, often with better location 179 accuracy. 181 Drivers often have a poor location awareness, especially outside of 182 major cities, at night and when away from home (especially abroad). 183 In the most crucial cases, the victim(s) might not be able to call 184 because they have been injured or trapped. 186 For more than two decades, some vehicles have been equipped with 187 telematics systems which, among other features, place an emergency 188 call automatically in the event of a crash or manually in response to 189 an emergency call button. Such systems generally have on-board 190 location determination systems that make use of satellite-based 191 positioning technology, inertial sensors, gyroscopes, etc., which can 192 provide an accurate position for the vehicle. Such built-in systems 193 can take advantage of the benefits of being integrated into a 194 vehicle, such as more power capacity, ability to have larger or 195 specialized antenna, ability to be engineered to avoid or minimise 196 degradation by vehicle glass coatings, interference from other 197 vehicle systems, etc. Thus, the PSAP can be provided with a good 198 estimate of where the vehicle is during an emergency. Vehicle 199 manufacturers are increasingly adopting such systems, both for the 200 safety benefits and for the additional features and services they 201 enable (e.g., remote engine diagnostics, remote door unlock, stolen 202 vehicle tracking and disabling, etc.). 204 The general term for such systems is Automatic Crash Notification 205 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 206 used in this document as a general term. ACN systems transmit some 207 amount of data specific to the incident, referred to generally as 208 "crash data" (the term is commonly used even though there might not 209 have been a crash). While different systems transmit different 210 amounts of crash data, standardized formats, structures, and 211 mechanisms are needed to provide interoperability among systems and 212 PSAPs. 214 As of the date of this document, currently deployed in-vehicle 215 telematics systems are circuit-switched and lack a standards-based 216 ability to convey crash data directly to the PSAP (generally relying 217 on either a human advisor or an automated text-to-speech system to 218 provide the PSAP call taker with some crash data orally, or in some 219 cases via a proprietary mechanism). In most cases, the PSAP call 220 taker needs to first realize that the call is related to a vehicle 221 incident, and then listen to the data and transcribe it. Circuit- 222 switched ACN systems are referred to here as CS-ACN. 224 The transition to next-generation calling in general, and for 225 emergency calling in particular, provides an opportunity to vastly 226 improve the scope, breadth, reliability and usefulness of crash data 227 during an emergency by allowing it to be transmitted during call set- 228 up, and to be automatically processed by the PSAP and made available 229 to the call taker in an integrated, automated way, as well as provide 230 the ability for a PSAP call taker to request that a vehicle take 231 certain actions, such as flashing lights or unlocking doors. In 232 addition, vehicle manufacturers are provided an opportunity to take 233 advantage of the same standardized mechanisms for data transmission 234 and request processing for internal use if they wish (such as 235 telemetry between the vehicle and a service center for both emergency 236 and non-emergency uses, including location-based services, multi- 237 media entertainment systems, remote door unlocking, and road-side 238 assistance applications). 240 Next-generation ACN provides an opportunity for such calls to be 241 recognized and processed as such during call set-up, and routed to an 242 equipped PSAP where the vehicle data is available to assist the call 243 taker in assessing and responding to the situation. Next-generation 244 (IP-based) ACN systems are referred to here as NG-ACN. 246 An ACN call can be initiated by a vehicle occupant or automatically 247 initiated by vehicle systems in the event of a serious incident. 248 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 249 used to refer to the class of calls that are placed by an in-vehicle 250 system (IVS) or Telematics Service Providers (TSP) and that carry 251 incident-related data as well as voice.) Automatically triggered 252 calls indicate a car crash or some other serious incident (e.g., a 253 fire). Manually triggered calls are often reports of observed 254 crashes or serious hazards (such as impaired drivers or roadway 255 debris). In some implementations, manually triggered calls might be 256 more likely to be accidental. 258 This document describes how the IETF mechanisms for IP-based 259 emergency calls, including [RFC6443] and [RFC7852], are used to 260 provide the realization of next-generation ACN. 262 This document reuses the technical aspects of next-generation pan- 263 European eCall (a mandated and standardized system for emergency 264 calls by in-vehicle systems within Europe and other regions), as 265 described in [I-D.ietf-ecrit-ecall]. However, this document 266 specifies a different set of vehicle (crash) data, specifically, the 267 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 268 of Data (MSD). This document is an extension of 269 [I-D.ietf-ecrit-ecall], with the differences being that this document 270 makes the MSD data set optional and VEDS mandatory, and adds new 271 attribute values to the eCall metadata/control object defined in that 272 document. This document also registers a new INFO package (identical 273 to that defined in [I-D.ietf-ecrit-ecall] with the addition of the 274 VEDS MIME type). 276 The Association of Public-Safety Communications Officials (APCO) and 277 the National Emergency Number Association (NENA) have jointly 278 developed a standardized set of incident-related vehicle data for ACN 279 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 280 is often referred to as crash data although it is applicable in 281 incidents other than crashes. 283 VEDS provides a standard data set for the transmission, exchange, and 284 interpretation of vehicle-related data. A standard data format 285 allows the data to be generated by an IVS or TSP and interpreted by 286 PSAPs, emergency responders, and medical facilities. It includes 287 incident-related information such as airbag deployment, location and 288 compass orientation of the vehicle, spatial orientation of the 289 vehicle (e.g., upright, on its side or top or a bumper), various 290 sensor data that can indicate the potential severity of the crash and 291 the likelihood of severe injuries to the vehicle occupants, etc. 292 This data better informs the PSAP and emergency responders as to the 293 type of response that might be needed. Some of this information has 294 been included in U.S. government guidelines for field triage of 295 injured patients [triage-2008] [triage-2011]. These guidelines are 296 designed to help responders identify the potential existence of 297 severe internal injuries and to make critical decisions about how and 298 where a patient needs to be transported. 300 This document registers the 'application/EmergencyCallData.VEDS+xml' 301 MIME content-type, and registers the 'VEDS' entry in the Emergency 302 Call Additional Data registry. 304 VEDS is an XML structure (see [VEDS]) transported in SIP using the 305 'application/EmergencyCallData.VEDS+xml' MIME content-type.. 307 VEDS is a versatile structure that can accomodate varied needs. 308 However, if additional sets of data are determined to be needed 309 (e.g., in the future or in different regions), the steps to enable 310 each data block are very briefly summarized below: 312 o A standardized format and encoding (such as XML) is defined and 313 published by a Standards Development Organization (SDO) 315 o A MIME Content-Type is registered for it (typically under the 316 'Application' media type) with a sub-type starting with 317 'EmergencyCallData.' 319 o An entry for the block is added to the Emergency Call Additional 320 Data Blocks sub-registry (established by [RFC7852]); the registry 321 entry is the root of the MIME sub-type (not including the 322 'EmergencyCallData' prefix and any suffix such as '+xml') 324 o A new INFO package is registered that permits carrying the new 325 content type and the metadata/control object (defined in 326 [I-D.ietf-ecrit-ecall]) in INFO requests. 328 Section 6 describes how VEDS data and metadata/control are 329 transported within NG-ACN calls. Section 7 describes how such calls 330 are placed. 332 These mechanisms are thus used to place emergency calls that are 333 identifiable as ACN calls and that carry standardized crash data in 334 an interoperable way. 336 Calls by in-vehicle systems are placed using cellular networks, which 337 might ignore location information sent by an originating device in an 338 emergency call INVITE, instead attaching their own location 339 information (often determined in cooperation with the originating 340 device). Standardized crash data structures often include location 341 as determined by the IVS. A benefit of this is that it allows the 342 PSAP to see both the location as determined by the cellular network 343 (often in cooperation with the originating device) and the location 344 as determined by the IVS. 346 This specification inherits the ability to utilize test call 347 functionality from Section 15 of [RFC6881]. 349 3. Document Scope 351 This document is focused on how an ACN emergency call is setup and 352 incident-related data (including vehicle, sensor, and location data) 353 is transmitted to the PSAP using IETF specifications. For the direct 354 model, this is the end-to-end description (between the vehicle and 355 the PSAP). For the TSP model, this describes the call leg between 356 the TSP and the PSAP, leaving the call leg between the vehicle and 357 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 358 are then free to use the same mechanism as for the right-hand side or 359 not. 361 Note that Europe has a mandated and standardized system for emergency 362 calls by in-vehicle systems. This pan-European system is known as 363 "eCall" and is the subject of a separate document, 364 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 365 designed to operate in multiple regions might need to support eCall 366 as well as NG-ACN as described here. A vehicle IVS might determine 367 whether to use eCall or ACN by first determining the region or 368 country in which it is located (e.g., from a GNSS location fix and/or 369 identity of or information from an MNO). If other regions adopt 370 other data formats, a multi-region vehicle might need to support 371 those as well. This document adopts the call set-up and other 372 technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852]; 373 this makes it straightforward to use a different data set while 374 keeping other technical aspects unchanged. Hence, both NG-eCall and 375 the NG-ACN mechanism described here are compatible, differing 376 primarily in the specific data block that is sent (the eCall MSD in 377 the case of NG-eCall, and the APCO/NENA VEDS used in this document), 378 and some additions to the metadata/control data block. If other 379 regions adopt their own vehicle data sets, this can be similarly 380 accomodated without changing other technical aspects. Note that any 381 additional data blocks require a new INFO package to permit transport 382 within INFO requests. 384 4. Overview of Legacy Deployment Models 386 Legacy (circuit-switched) systems for placing emergency calls by in- 387 vehicle systems generally have some ability to convey at least 388 location and in some cases telematics data to the PSAP. Most such 389 systems use one of three architectural models, which are described 390 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 391 These three models are illustrated below. 393 In the TSP model, both emergency and non-emergency calls are placed 394 to a Telematics Service Provider (TSP); a proprietary technique is 395 used for data transfer (such as a proprietary in-band modem) between 396 the TSP and the vehicle. 398 In an emergency, generally the TSP call taker bridges in the PSAP and 399 communicates location, crash data (such as impact severity and trauma 400 prediction), and other data (such as the vehicle description) to the 401 PSAP call taker verbally (in some cases, a proprietary out-of-band 402 interface is used). Since the TSP knows the location of the vehicle 403 (from on-board GNSS and sensors), location-based routing is usually 404 used to route to the appropriate PSAP. In some cases, the TSP is 405 able to transmit location automatically, using similar techniques as 406 for wireless calls. Typically, a three-way voice call is established 407 between the vehicle, the TSP, and the PSAP, allowing communication 408 between the PSAP call taker, the TSP call taker, and the vehicle 409 occupants (who might be unconscious). 411 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 412 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 413 \\\----/// crash data +------+ location via trunk +------+ 415 Figure 1: Legacy TSP Model. 417 In the paired model, the IVS uses a Bluetooth link with a previously- 418 paired handset to establish an emergency call with the PSAP (by 419 dialing a standard emergency number; 9-1-1 in North America), and 420 then communicates location data to the PSAP via text-to-speech; crash 421 data might or might not be conveyed also using text-to-speech. Some 422 such systems use an automated voice prompt menu for the PSAP call 423 taker (e.g., "this is an automatic emergency call from a vehicle; 424 press 1 to open a voice path to the vehicle; press 2 to hear the 425 location read out") to allow the call taker to request location data 426 via text-to-speech. 428 +---+ 429 ///----\\\ | H | 911/etc voice call via handset +------+ 430 ||| IVS |||-->| S +----------------------------------->+ PSAP | 431 \\\----/// +---+ location via text-to-speech +------+ 433 Figure 2: Legacy Paired Model 435 In the direct model, the IVS directly places an emergency call with 436 the PSAP by dialing a standard emergency number (9-1-1 in North 437 America). Such systems might communicate location data to the PSAP 438 via text-to-speech; crash data might or might not be conveyed using 439 text-to-speech. Some such systems use an automated voice prompt menu 440 (e.g., "this is an automatic emergency call from a vehicle; press 1 441 to open a voice path to the vehicle; press 2 to hear the location 442 read out") to allow the call taker to request location data via text- 443 to-speech. 445 ///----\\\ 911/etc voice call via IVS +------+ 446 ||| IVS |||---------------------------------------->+ PSAP | 447 \\\----/// location via text-to-speech +------+ 449 Figure 3: Legacy Direct Model 451 5. Migration to Next-Generation 453 Migration of emergency calls placed by in-vehicle systems to next- 454 generation (all-IP) technology per this document provides a 455 standardized mechanism to identify such calls and to present crash 456 data with the call, as well as enabling additional communications 457 modalities and enhanced functionality. This allows ACN calls and 458 crash data to be automatically processed by the PSAP and made 459 available to the call taker in an integrated, automated way. Because 460 the crash data is carried in the initial SIP INVITE (per [RFC7852]) 461 the PSAP can present it to the call taker simultaneously with the 462 appearance of the call. The PSAP can also process the data to take 463 other actions (e.g., if multiple calls from the same location arrive 464 when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP 465 might choose to store the information and reject the calls, since the 466 IVS will receive confirmation that the information has been 467 successfully received; a PSAP could also choose to include a message 468 stating that it is aware of the incident and responders are on the 469 way; a PSAP could call the vehicle back when a call taker is 470 available). 472 Origination devices and networks, PSAPs, emergency services networks, 473 and other telephony environments are migrating to next-generation. 475 This provides opportunities for significant enhancement to 476 interoperability and functionality, especially for emergency calls 477 carrying additional data such as vehicle crash data. (In the U.S., a 478 network specifically for emergency responders is being developed. 479 This network, FirstNet, will be next-generation from the start, 480 enhancing the ability for data exchange between PSAPs and 481 responders.) 483 Migration to next-generation (NG) provides an opportunity to 484 significantly improve the handling and response to vehicle-initiated 485 emergency calls. Such calls can be recognized as originating from a 486 vehicle, routed to a PSAP equipped both technically and operationally 487 to handle such calls, and the vehicle-determined location and crash 488 data can be made available to the call taker simultaneously with the 489 call appearance. The PSAP can take advantage of enhanced 490 functionality, including the ability to request the vehicle to take 491 an action, such as sending an updated set of data, converying a 492 message to the occupants, flashing lights, unlocking doors, etc. 494 Vehicle manufacturers using the TSP model can choose to take 495 advantage of the same mechanism to carry telematics data and requests 496 and responses between the vehicle and the TSP for both emergency and 497 non-emergency calls as are used for the interface with the PSAP. 499 A next-generation IVS establishes an emergency call using the 500 emergency call solution as described in [RFC6443] and [RFC6881], with 501 the difference that the Request-URI indicates an ACN type of 502 emergency call, the IVS typically does not perform routing or 503 location queries but relies on the carrier for this, and uses Call- 504 Info header fields to indicates that vehicle crash and capabilities 505 data is attached. When an ESInet is deployed, the MNO only needs to 506 recognize the call as an emergency call and route it to an ESInet. 507 The ESInet can recognize the call as an ACN with vehicle data and can 508 route the call to an NG-ACN capable PSAP. Such a PSAP can interpret 509 the vehicle data sent with the call and make it available to the call 510 taker. 512 [I-D.ietf-ecrit-ecall] registers new service URN children within the 513 "sos" subservice. These URNs request NG-ACN resources, and 514 differentiate between manually and automatically triggered NG-ACN 515 calls (which might be subject to different treatment depending on 516 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 517 are "urn:service:sos.ecall.automatic" and 518 "urn:service:sos.ecall.manual". The same service URNs are used for 519 ACN as for eCall since in any region only one of these is supported, 520 making a distinction unnecessary. (Further, PSAP equipment might 521 support multiple data formats, allowing a PSAP to handle a vehicle 522 that erroneously sent the wrong data object.) 523 Note that in North America, routing queries performed by clients 524 outside of an ESInet typically treat all sub-services of "sos" 525 identically to "sos" with no sub-service. However, the Request-URI 526 header field retains the full sub-service; route and handling 527 decisions within an ESInet or PSAP can take the sub-service into 528 account. For example, in a region with multiple cooperating PSAPs, 529 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 530 one that specializes in vehicle-related incidents. 532 Migration of the three architectural models to next-generation (all- 533 IP) is described below. 535 In the TSP model, the IVS transmits crash and location data to the 536 TSP either by re-using the mechanisms and data objects described 537 here, or using a proprietary mechanism. In an emergency, the TSP 538 bridges in the PSAP and the TSP transmits crash and other data to the 539 PSAP using the mechanisms and data objects described here. There is 540 a three-way call between the vehicle, the TSP, and the PSAP, allowing 541 communication between the PSAP call taker, the TSP call taker, and 542 the vehicle occupants (who might be unconscious). The TSP relays 543 PSAP requests and vehicle responses. 545 proprietary 546 ///----\\\ or standard +------+ standard +------+ 547 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 548 \\\----/// crash + other data +------+ crash + other data +------+ 550 Figure 4: Next-Generation TSP Model 552 The vehicle manufacturer and the TSP can choose to use the same 553 mechanisms and data objects on the left call leg in Figure 4 as on 554 the right. (Note that the TSP model can be more difficult when the 555 vehicle is in a different country than the TSP (e.g., a US resident 556 driving in Canada or Mexico) because of the additional complexity in 557 choosing the correct PSAP based on vehicle location performed by a 558 TSP in a different country.) 560 In the direct model, the IVS communicates crash data to the PSAP 561 directly using the mechanisms and data objects described here. 563 ///----\\\ NG emergency call +------+ 564 ||| IVS |||----------------------------------------->+ PSAP | 565 \\\----/// crash + other data +------+ 567 Figure 5: Next-Generation Direct Model 569 In the paired model, the IVS uses a Bluetooth link to a previously- 570 paired handset to establish an emergency call with the PSAP; it is 571 undefined what facilities are or will be available for transmitting 572 crash data through the Bluetooth link to the handset for inclusion in 573 an NG emergency call. Hence, manufacturers that use the paired model 574 for legacy calls might choose to adopt either the direct or TSP 575 models for next-generation calls. 577 +---+ 578 ///----\\\ (undefined) | H | standard +------+ 579 ||| IVS |||------------------>| S +------------------->+ PSAP | 580 \\\----/// (undefined) +---+ crash + other data +------+ 582 Figure 6: Next-Generation Paired Model 584 If the call is routed to a PSAP that is not capable of processing the 585 vehicle data, the PSAP ignores (or does not receive) the vehicle 586 data. This is detectable by the IVS or TSP when the status response 587 to the INVITE (e.., 200 OK) lacks a control structure acknowledging 588 receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then 589 proceeds as it would for a CS-ACN call (e.g., verbal conveyance of 590 data) 592 6. Data Transport 594 [RFC7852] establishes a general mechanism for attaching blocks of 595 data to a SIP emergency call. This mechanism permits certain 596 emergency call MIME types to be attached to SIP messages. This 597 document makes use of that mechanism. This document also registers 598 an INFO package (in Section 11) to enable NG-ACN related data blocks 599 to be carried in SIP INFO requests (per [RFC6086], new INFO usages 600 require the definition of an INFO package). 602 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 603 by attaching it to a SIP message as a MIME body part per [RFC7852]. 604 The body part is identified by its MIME content-type ('application/ 605 emergencyCallData.eCall.VEDS+xml') in the Content-Type header field 606 of the body part. The body part is assigned a unique identifier 607 which is listed in a Content-ID header field in the body part. The 608 SIP message is marked as containing the VEDS data by adding (or 609 appending to) a Call-Info header field at the top level of the SIP 610 message. This Call-Info header field contains a CID URL referencing 611 the body part's unique identifier, and a 'purpose' parameter 612 identifying the data as a VEDS data block per the Emergency Call 613 Additional Data Blocks registry entry; the 'purpose' parameter's 614 value is 'emergencyCallData.VEDS'. A VEDS data block is carried in a 615 SIP INFO request by using the INFO package defined in Section 11. 617 A PSAP or IVS transmits a metadata/control object (see 618 [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME 619 body part per [RFC7852]. The body part is identified by its MIME 620 content-type ('application/emergencyCallData.control+xml') in the 621 Content-Type header field of the body part. The body part is 622 assigned a unique identifier which is listed in a Content-ID header 623 field in the body part. The SIP message is marked as containing the 624 metadata/control block by adding (or appending to) a Call-Info header 625 field at the top level of the SIP message. This Call-Info header 626 field contains a CID URL referencing the body part's unique 627 identifier, and a 'purpose' parameter identifying the data as a 628 metadata/control block per the Emergency Call Additional Data Blocks 629 registry entry; the 'purpose' parameter's value is 630 'emergencyCallData.control'. A metadata/control object is carried in 631 a SIP INFO request by using the INFO package defined in Section 11. 633 As is necessary with message bodies, if a VEDS or a metadata/control 634 block is sent in the same message with another body part, a 635 multipart/mixed body part encloses all body parts. In some cases, 636 there are intermediate multipart body parts between the top level 637 multipart/mixed and the body part containing the VEDS or metadata/ 638 control object. 640 A body part containing a VEDS or metadata/control object has a 641 Content-Disposition header field value containing "By-Reference" 642 unless it is the only body part in a SIP INFO request, in which case, 643 per [RFC6086], "INFO-Package" is used. 645 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 646 initial INVITE a VEDS data block and a metadata/control object 647 informing the PSAP of its capabilities. The VEDS and metadata/ 648 control body parts (and PIDF-LO) have a Content-Disposition header 649 field with the value "By-Reference; handling=optional". Specifying 650 handling=optional prevents the INVITE from being rejected if it is 651 processed by a legacy element (e.g., a gateway between SIP and 652 circuit-switched environments) that does not understand the VEDS or 653 metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ 654 control object acknowledging receipt of the VEDS data and includes it 655 in the SIP final response to the INVITE. The metadata/control object 656 is not attached to provisional (e.g., 180) responses. 658 If the IVS receives an acknowledgment for a VEDS data object with 659 received=false, it indicates some fault with the transfer of the 660 VEDS, the VEDS content, or the PSAP's ability to properly receive, 661 decode and act on the VEDS. The IVS action is not defined (e.g., it 662 might only log an error). Since the PSAP is able to request an 663 updated VEDS during the call, if an initial VEDS is unsatisfactory in 664 any way, the PSAP can choose to request another one. 666 A PSAP can request that the vehicle send an updated VEDS data block 667 during a call. To do so, the PSAP creates a metadata/control object 668 requesting VEDS data and attaches it to a SIP INFO request and sends 669 it within the dialog. The IVS then attaches an updated VEDS data 670 object to a SIP INFO request and sends it within the dialog. If the 671 IVS is unable to send the VEDS, it instead sends a metadata/control 672 object acknowledging the request with the 'success' parameter set to 673 'false' and a 'reason' parameter (and optionally a 'details' 674 parameter) indicating why the request cannot be accomplished. Per 675 [RFC6086], metadata/control objects and VEDS data are sent using the 676 INFO package defined in Section 11. In addition, to align with the 677 way a VEDS or metadata/control block is transmitted in a SIP message 678 other than an INFO request, one or more Call-Info header fields are 679 included in the SIP INFO request to reference the VEDS or metadata/ 680 control block. See Section 11 for more information on the use of 681 INFO requests within NG-ACN calls. 683 If the IVS is aware that VEDS data it sent previously has changed, it 684 MAY send an unsolicited VEDS (in any convenient SIP message, 685 including an INFO request) during the call. The PSAP sends an 686 acknowledgment of an unsolicited VEDS object (if the IVS sent the 687 unsolicited VEDS in an INFO request, the acknowledgment is sent in a 688 new INFO request, otherwise it is sent in the response to the message 689 containing the VEDS). 691 7. Call Setup 693 A next-generation In-Vehicle System (IVS) initiates an NG-ACN call 694 with a SIP INVITE using one of the SOS sub-services 695 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, 696 standard sets of crash data and capabilities data encoded in 697 standardized and registered formats, attached as additional data 698 blocks as specified in Section 4.1 of [RFC7852]. As described in 699 that document, each data block is identified by its MIME content- 700 type, and pointed to by a CID URL in a Call-Info header with a 701 'purpose' parameter value corresponding to the data block. 703 If new data blocks are needed (e.g., in other regions or in the 704 future), the steps required during standardization are briefly 705 summarized below: 707 o A set of data is standardized by an SDO or appropriate 708 organization 710 o A MIME Content-Type for the crash data set is registered with IANA 711 * If the data is specifically for use in emergency calling, the 712 MIME type is normally under the 'application' type with a 713 subtype starting with 'EmergencyCallData.' 715 * If the data format is XML, then by convention the name has a 716 suffix of '+xml' 718 o The item is registered in the Emergency Call Additional Data 719 registry, as defined in Section 9.1.7 of [RFC7852] 721 * For emergency-call-specific formats, the registered name is the 722 root of the MIME Content-Type (not including the 723 'EmergencyCallData' prefix and any suffix such as '+xml') as 724 described in Section 4.1 of [RFC7852]. 726 o A new INFO package is registered that permits carrying the the new 727 content type, the metadata/control object (defined in 728 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 729 objects, in INFO messages. 731 When placing an emergency call, the crash data set and IVS capability 732 data are transported as described in Section 6. 734 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 735 the Association of Public-Safety Communications Officials (APCO) and 736 the National Emergency Number Association (NENA) [VEDS]. It is 737 carried in body part with MIME content-type 'application/ 738 EmergencyCallData.VEDS+xml'. 740 Entities along the path between the vehicle and the PSAP are able to 741 identify the call as an ACN call and handle it appropriately. The 742 PSAP is able to identify the crash and capabilities data attached to 743 the INVITE by examining the Call-Info header fields for 'purpose' 744 parameters whose values start with 'EmergencyCallData.' The PSAP is 745 able to access the data it is capable of handling and is interested 746 in by checking the 'purpose' parameter values. 748 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 749 up and other normative requirements with the exception that in this 750 document, support for the eCall MSD is OPTIONAL and support for VEDS 751 in REQUIRED. This document also adds new attribute values to the 752 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 754 8. Call Routing 756 An Emergency Services IP Network (ESInet) is a network operated by or 757 on behalf of emergency services authorities. It handles emergency 758 call routing and processing before delivery to a PSAP. In the 759 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 760 architecture adopted by EENA, each PSAP is connected to one or more 761 ESInets. Each originating network is also connected to one or more 762 ESInets. The ESInets maintain policy-based routing rules that 763 control the routing and processing of emergency calls. The 764 centralization of such rules within ESInets allows for a cleaner 765 separation between the responsibilities of the originating network 766 and that of the emergency services network, and provides greater 767 flexibility and control over processing of emergency calls by the 768 emergency services authorities and PSAPs. This can make it easier to 769 react quickly to situations that require changes in how emergency 770 calls are routed or handled (e.g., a natural disaster closes a PSAP), 771 as well as ease in making long-term changes that affect such routing 772 (e.g., cooperative agreements to specially handle calls requiring 773 translation or relay services). 775 In an environment that uses ESInets, the originating network might 776 pass all types of emergency calls to an ESInet (all calls with a 777 service URN of or starting with "sos"). The ESInet then routs such 778 calls to an appropriate PSAP. In an environment without an ESInet, 779 the emergency services authorities and the originating carriers 780 determine how such calls are routed. 782 9. New Metadata/Control Values 784 This document adds new attribute values to the metadata/control 785 structure defined in [I-D.ietf-ecrit-ecall]. 787 In addition to the base usage from the PSAP to the IVS to 788 acknowledge receipt of crash data, the element is also 789 contained in a metadata/control block sent by the IVS to the PSAP. 790 This is used by the IVS to acknowledge receipt of a request by the 791 PSAP and indicate if the request was carried out when that request 792 would not otherwise be acknowledged (if the PSAP requests the 793 vehicle to send data and the vehicle does so, the data serves as a 794 success acknowledgement). 796 The element is used in a metadata/control block 797 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 798 inform the PSAP of the vehicle capabilities. Child elements 799 contain all actions and data types supported by the vehicle and 800 all available lamps (lights) and cameras. 802 New request values are added to the element to enable 803 the PSAP to request the vehicle to perform actions. 805 Mandatory Actions (the IVS and the PSAP MUST support): 807 o Transmit data object (VEDS MUST be supported; MSD MAY be 808 supported) 810 Optional Actions (the IVS and the PSAP MAY support): 812 o Play and/or display static (pre-defined) message 813 o Speak/display dynamic text (text supplied in action) 814 o Flash or turn on or off a lamp (light) 815 o Honk horn 816 o Enable a camera 818 The element indicates the object being acknowledged (i.e., a 819 data object or a metadata/control block containing 820 elements), and reports success or failure. 822 The element has child elements indicating 823 the actions supported by the IVS. 825 The element contains attributes to indicate the request and 826 to supply any needed information, and MAY contain a child 827 element to contain the text for a dynamic message. The 'action' 828 attribute is mandatory and indicates the specific action. 829 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 830 allowed values; this document adds new values to that registry in 831 Table 2. 833 Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block 834 in response to the VEDS data sent by the IVS in SIP requests other 835 than INFO (e.g., the INVITE). This metadata/control block is sent in 836 the SIP response to the request (e.g., the INVITE response). When 837 the PSAP needs to send a control block that is not an immediate 838 response to a VEDS or other data sent by the IVS, the control block 839 is transmitted from the PSAP to the IVS in a SIP INFO request within 840 the established dialog. The IVS sends the requested data (e.g., the 841 VEDS) or an acknowledgment (for requests other than to send data) in 842 a new INFO request. This mechanism flexibly allows the PSAP to send 843 metadata/control data to the IVS and the IVS to respond. If control 844 data sent in a response message requests the IVS to send a new VEDS 845 or other data block, or to perform an action other than sending data, 846 the IVS sends the requested data or an acknowledgment regarding the 847 action in an INFO message within the dialog. 849 9.1. New values for the 'action' attribute' 851 The following new "action" values are defined: 853 msg-static: displays or plays a predefined message (translated as 854 appropriate for the language of the vehicle's interface). A 855 registry is created in Section 15.4 for messages and their IDs. 856 Vehicles include the highest registered message in their 857 element to indicate support for all messages up to 858 and including the indicated value. 860 msg-dynamic displays or speaks (via text-to-speech) a dynamic 861 message included in the request. 863 honk sounds the horn. 865 lamp turns a lamp (light) on, off, or flashes. 867 enable-camera adds a one-way media stream (established via SIP re- 868 INVITE sent by the vehicle) to enable the PSAP call taker to view 869 a feed from a camera. 871 Note that there is no 'request' action to play dynamic media (such as 872 an audio message). The PSAP can send a SIP re-INVITE to establish a 873 one-way media stream for this purpose. 875 9.2. Request Example 877 878 883 884 886 887 888 Remain calm. Help is on the way. 889 891 893 Figure 7: Request Example 895 9.3. The element 897 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 898 PSAP to acknowledge the MSD. Here, the element is also 899 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 900 to acknowledge receipt of a element that requested the IVS 901 to perform an action other than transmitting a data object (e.g., a 902 request to display a message would be acknowledged, but a request to 903 transmit VEDS data would not result in a separate element being 904 sent, since the data object itself serves as acknowledgment.) An 905 element sent by an IVS references the unique ID of the 906 metadata/control object containing the request(s) and indicates 907 whether the request was successfully performed, and if not, 908 optionally includes an explanation. 910 9.3.1. Ack Examples 912 913 918 919 920 922 924 926 Figure 8: Ack Example from IVS to PSAP 928 9.4. The element 930 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 931 the IVS to indicate its capabilities to the PSAP. 933 The element contains a child element per 934 action supported by the vehicle. The vehicle MUST support sending 935 the VEDS data object and so includes at a minimum a child 936 element with the 'action' attribute set to "send-data" and the 937 'supported-values' attribute containing all data blocks supported by 938 the IV, which MUST include 'VEDS'. All other actions are OPTIONAL. 940 If the "msg-static" action is supported, a child element 941 with the 'action' attribute set to "msg-static" is included, with the 942 'msgid' attribute set to the highest supported static message 943 supported by the vehicle. A registry is created in Section 15.4 to 944 map 'msgid' values to static text messages. By sending the highest 945 supported static message number in its element, the 946 vehicle indicates its support for all static messages in the registry 947 up to and including that value. 949 If the "lamp" action is supported, a child element with the 950 'action' attribute set to "lamp" is included, with the 'supported- 951 values' attribute set to all supported lamp IDs. A registry is 952 created in Section 15.5 to contain lamp ID values. 954 If the "enable-camera" action is supported, a child element 955 with the 'action' attribute set to "enable-camera" is included, with 956 the 'supported-values' attribute set to all supported camera IDs. A 957 registry is created in Section 15.6 to contain camera ID values. 959 9.4.1. Capabilities Example 961 962 967 968 969 972 973 974 975 976 978 980 Figure 9: Capabilities Example 982 10. Test Calls 984 An NG-ACN test call is a call that is recognized and treated to some 985 extent as an NG-ACN call but not given emergency call treatment and 986 not handled by a call taker. The specific handling of test NG-ACN 987 calls is not itself standardized; the test call facility is intended 988 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 989 successfully established with voice and/or other media communication. 990 The IVS might also be able to verify that the crash data was 991 successfully received. 993 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 994 ability to utilize test call functionality from Section 15 of 995 [RFC6881]. A service URN starting with "test." indicates a test 996 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 997 for test calls. 999 MNOs, emergency authorities, ESInets, and PSAPs determine how to 1000 treat a vehicle call requesting the "test" service URN so that the 1001 desired functionality is tested, but this is outside the scope of 1002 this document. (One possibility is that MNOs route such calls as 1003 non-emergency calls to an ESInet, which routes them to a PSAP that 1004 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 1005 data acknowledgment, and plays an audio clip (for example, saying 1006 that the call reached an appropriate PSAP and the vehicle data was 1007 successfully processed) in addition to supporting media loopback per 1008 [RFC6881]). 1010 Note that since test calls are placed using "test" as the parent 1011 service URN and "sos" as a child, such calls are not treated as an 1012 emergency call and so some functionality might not apply (such as 1013 preemption or service availability for devices lacking service ("non- 1014 service-initialized" or "NSI" devices) if those are available for 1015 emergency calls). 1017 11. The emergencyCallData.eCall.VEDS INFO package 1019 This document registers the 'emergencyCallData.eCall.VEDS' INFO 1020 package. 1022 Both endpoints (the IVS and the PSAP equipment) include 1023 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 1024 [RFC6086] to indicate ability to receive INFO messages carrying data 1025 as described here. 1027 Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates 1028 the ability to receive NG-ACN related body parts as specified in 1029 [TBD: THIS DOCUMENT]. 1031 An INFO request message carrying data related to an emergency call as 1032 described in [TBD: THIS DOCUMENT] has an Info-Package header field 1033 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 1035 The requirements of Section 10 of [RFC6086] are addressed in the 1036 following sections. 1038 11.1. Overall Description 1040 This section describes "what type of information is carried in INFO 1041 requests associated with the Info Package, and for what types of 1042 applications and functionalities UAs can use the Info Package." 1044 INFO requests associated with the emergencyCallData.eCall.VEDS INFO 1045 package carry data associated with emergency calls as defined in 1046 [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency 1047 calls established using SIP. The functionality is to carry vehicle 1048 data and metadata/control information between vehicles and PSAPs. 1049 Refer to [TBD: THIS DOCUMENT] for more information. 1051 11.2. Applicability 1053 This section describes "why the Info Package mechanism, rather than 1054 some other mechanism, has been chosen for the specific use-case...." 1056 The use of INFO is based on an analysis of the requirements against 1057 the intent and effects of INFO versus other approaches (which 1058 included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane 1059 transport, and non-SIP protocols). In particular, the transport of 1060 emergency call data blocks occurs within a SIP emergency dialog, per 1061 Section 6, and is normally carried in the initial INVITE and its 1062 response; the use of INFO only occurs when emergency-call-related 1063 data needs to be sent mid-call. While MESSAGE could be used, it is 1064 not tied to a SIP dialog as is INFO and thus might not be associated 1065 with the dialog. SIP OPTIONS or re-INVITE could also be used, but is 1066 seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into 1067 service, but the semantics are not a good fit, e.g., the subscribe/ 1068 notify mechanism provides one-way communication consisting of (often 1069 multiple) notifications from notifier to subscriber indicating that 1070 certain events in notifier have occurred, whereas what's needed here 1071 is two-way communication of data related to the emergency dialog. 1072 Use of the media plane mechanisms was discounted because the number 1073 of messages needing to be exchanged in a dialog is normally zero or 1074 very few, and the size of the data is likewise very small. The 1075 overhead caused by user plane setup (e.g., to use MSRP as transport) 1076 would be disproportionately large. 1078 Based on the the analyses, the SIP INFO method was chosen to provide 1079 for mid-call data transport. 1081 11.3. Info Package Name 1083 The info package name is emergencyCallData.eCall.VEDS 1085 11.4. Info Package Parameters 1087 None 1089 11.5. SIP Option-Tags 1091 None 1093 11.6. INFO Message Body Parts 1095 The body for an emergencyCallData.eCall.VEDS info package is: 1097 o an application/emergencyCallData.eCall.VEDS+xml (containing a VEDS 1098 data block), or 1100 o an application/emergencyCallData.control+xml (containing a 1101 metadata/control object), or 1103 o an application/emergencyCallData.eCall.MSD+per (containing an 1104 MSD), or 1106 o a multipart body containing: 1108 * zero or one application/emergencyCallData.eCall.VEDS+xml part 1109 (containing a VEDS data block), 1111 * zero or more application/emergencyCallData.control+xml 1112 (containing a metadata/control object), 1114 * zero or one application/emergencyCallData.eCall.MSD+per part 1115 (containing an MSD), 1117 The body parts are sent per [RFC6086], and in addition, to align with 1118 with how these body parts are sent in non-INFO messages, each 1119 associated body part is referenced by a Call-Info header field at the 1120 top level of the SIP message. If the body part is the only body 1121 part, it has a Content-Disposition header field value of "INFO- 1122 Package". If the body part is contained within a multipart, it has a 1123 Content-Disposition header field value of "By-Reference". 1125 Service providers are not expected to attach [RFC7852] Additional 1126 Data to an INFO request. 1128 See [TBD: THIS DOCUMENT] for more information. 1130 11.7. Info Package Usage Restrictions 1132 Usage is limited to vehicle-initiated emergency calls as defined in 1133 [TBD: THIS DOCUMENT]. 1135 11.8. Rate of INFO Requests 1137 The rate of SIP INFO requests associated with the 1138 emergencyCallData.eCall.VEDS info package is normally quite low (most 1139 dialogs are likely to contain zero INFO requests, while others can be 1140 expected to carry an occasional request). 1142 11.9. Info Package Security Considerations 1144 The MIME content type registations for the data blocks that can be 1145 carried using this INFO package contains a discussion of the security 1146 and/or privacy considerations specific to that data block. The 1147 "Security Considerations" and "Privacy Considerations" sections of 1148 [TBD: THIS DOCUMENT] discuss security and privacy considerations of 1149 the data carried in vehicle-initiated emergency calls as described in 1150 that document. 1152 11.10. Implementation Details 1154 See [TBD: THIS DOCUMENT] for protocol details. 1156 11.11. Examples 1158 See [TBD: THIS DOCUMENT] for protocol examples. 1160 12. Example 1162 Figure 10 shows an NG-ACN call routing. The mobile network operator 1163 (MNO) routes the call to an Emergency services IP Network (ESInet), 1164 as for any emergency call. The ESInet routes the call to an 1165 appropriate NG-ACN-capable PSAP (using location information and the 1166 fact that that it is an NG-ACN call). The call is processed by the 1167 Emergency Services Routing Proxy (ESRP), as the entry point to the 1168 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 1169 PSAP, where the call is received by a call taker. (In deployments 1170 where there is no ESInet, the MNO itself routes the call directly to 1171 an appropriate NG-ACN-capable PSAP.) 1172 +---------------------------------------+ 1173 | | 1174 +------------+ | +-------+ | 1175 | | | | PSAP2 | | 1176 | | | +-------+ | 1177 | Originating| | | 1178 | Mobile | | +------+ +-------+ | 1179 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1180 | | | +------+ +-------+ | 1181 | | | | 1182 +------------+ | +-------+ | 1183 | | PSAP3 | | 1184 | +-------+ | 1185 | | 1186 | | 1187 | | 1188 | ESInet | 1189 +---------------------------------------+ 1191 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1193 The example, shown in Figure 11, illustrates a SIP emergency call 1194 INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS 1195 data block), and capabilities data (an eCall metadata/control block 1196 with extensions defined in this document) attached to the SIP INVITE 1197 message. The INVITE has a request URI containing the 1198 'urn:service:sos.ecall.automatic' service URN. 1200 The example VEDS data structure shows information about about a 1201 crashed vehicle. The example communicates that the car is a model 1202 year 2015 Saab 9-5 (a car which does not exist). The front airbag 1203 deployed as a consequence of the crash. The 1204 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 1205 passenger car (the code is set to '101') and that it is not a 1206 convertible (the 'ConvertibleIndicator' value is set to 'false'). 1208 The 'VehicleCrashPulse' element provides further information about 1209 the crash, namely that the force of impact based on the change in 1210 velocity over the duration of the crash pulse was 100 MPH. The 1211 principal direction of the force of the impact is set to '12' (which 1212 refers to 12 O'Clock, corresponding to a frontal collision). This 1213 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1214 element. 1216 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1217 quarter turns in concert with a rollover expressed as a number; in 1218 our case 1. 1220 No roll bar was deployed, as indicated in 1221 'VehicleRollbarDeployedIndicator' being set to 'false'. 1223 Next, there is information indicating seatbelt and seat sensor data 1224 for individual seat positions in the vehicle. In our example, 1225 information from the driver seat is available (value '1' in the 1226 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1227 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1228 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1229 and the seat sensor determined that the seat was occupied 1230 ('VehicleSeatOccupiedIndicator' element). 1232 Finally, information about the weight of the vehicle, which is 600 1233 kilogram in our example. 1235 In addition to the information about the vehicle, further indications 1236 are provided, namely the presence of fuel leakage 1237 ('FuelLeakingIndicator' element), an indication whether the vehicle 1238 was subjected to multiple impacts ('MultipleImpactsIndicator' 1239 element), the orientation of the vehicle at final rest 1240 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1241 that there are no parts of the vehicle on fire (the 1242 'VehicleFireIndicator' element). 1244 INVITE urn:service:sos.ecall.automatic SIP/2.0 1245 To: urn:service:sos.ecall.automatic 1246 From: ;tag=9fxced76sl 1247 Call-ID: 3848276298220188511@atlanta.example.com 1248 Geolocation: 1249 Geolocation-Routing: no 1250 Call-Info: ; 1251 purpose=EmergencyCallData.VEDS 1252 Call-Info: ; 1253 purpose=emergencyCallData.control 1254 Accept: application/sdp, application/pidf+xml, 1255 application/emergencyCallData.control+xml 1256 Recv-Info: emergencyCallData.eCall 1257 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1258 SUBSCRIBE, NOTIFY, UPDATE 1259 CSeq: 31862 INVITE 1260 Content-Type: multipart/mixed; boundary=boundary1 1261 Content-Length: ... 1263 --boundary1 1264 Content-Type: application/sdp 1266 ...Session Description Protocol (SDP) goes here 1267 --boundary1 1268 Content-Type: application/pidf+xml 1269 Content-ID: 1270 Content-Disposition: by-reference;handling=optional 1272 1273 1281 1282 1283 1284 1285 -34.407 150.883 1286 1287 1288 278 1289 1290 1291 1292 1293 gps 1294 1295 2012-04-5T10:18:29Z 1296 1M8GDM9A_KP042788 1297 1298 1300 --boundary1 1301 Content-Type: application/EmergencyCallData.VEDS+xml 1302 Content-ID: <1234567890@atlanta.example.com> 1303 Content-Disposition: by-reference;handling=optional 1305 1306 1310 1311 1312 Saab 1313 1314 1315 9-5 1316 1317 1319 2015 1320 1321 1322 FRONT 1323 true 1324 1325 1326 false 1327 MAIN 1328 1330 101 1331 1332 1333 1334 1336 100 1337 1338 1340 MPH 1341 1342 12 1343 1344 1 1345 1346 1347 false 1348 1349 1350 1 1351 1352 true 1353 1354 true 1355 1356 true 1357 1358 1359 1361 1363 600 1364 1365 1367 kilogram 1368 1369 1370 1371 true 1372 false 1373 true 1374 Driver 1375 1376 false 1377 1378 1380 --boundary1 1381 Content-Type: application/emergencyCallData.control+xml 1382 Content-ID: <1234567892@atlanta.example.com> 1383 Content-Disposition: by-reference;handling=optional 1385 1386 1391 1392 1393 1397 1398 1399 1400 1402 1404 1406 --boundary1-- 1408 Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call 1410 13. Security Considerations 1412 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1413 the security considerations described there and in [RFC5069] apply 1414 here. Implementors are cautioned to read and understand the 1415 discussion in those documents. 1417 As with emergency service systems where location data is supplied or 1418 determined with the assistance of an end host, there is the 1419 possibility that that location is incorrect, either intentially 1420 (e.g., in a denial of service attack against the emergency services 1421 infrastructure) or due to a malfunctioning device. The reader is 1422 referred to [RFC7378] for a discussion of some of these 1423 vulnerabilities. 1425 In addition to the security considerations discussion specific to the 1426 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1427 MAY decline to carry out any requested action (e.g., if the vehicle 1428 requires but is unable to verify the certificate used to sign the 1429 request). The vehicle MAY use any value in the reason registry to 1430 indicate why it did not take an action (e.g., the generic "unable" or 1431 the more specific "security-failure"). 1433 14. Privacy Considerations 1435 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1436 builds on [RFC7852], the data structures specified there, and the 1437 corresponding privacy considerations discussed there, apply here as 1438 well. The VEDS data structure contains optional elements that can 1439 carry identifying and personal information, both about the vehicle 1440 and about the owner, as well as location information, and so needs to 1441 be protected against unauthorized disclosure, as discussed in 1442 [RFC7852]. Local regulations may impose additional privacy 1443 protection requirements. 1445 The additional functionality enabled by this document, such as access 1446 to vehicle camera streams, carries a burden of protection and so 1447 implementations need to be careful that access is only provided 1448 within the context of an emergency call or to an emergency services 1449 provider (e.g., by verifying that the request for camera access is 1450 signed by a certificate issued by an emergency services registrar). 1452 15. IANA Considerations 1454 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1455 content type, and adds "VEDS" to the Emergency Call Additional Data 1456 registry. This document adds to and creates sub-registries in the 1457 'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall]. 1458 This document registers a new INFO package. 1460 15.1. MIME Content-type Registration for 'application/ 1461 EmergencyCall.VEDS+xml' 1463 This specification requests the registration of a new MIME content 1464 type according to the procedures of RFC 4288 [RFC4288] and guidelines 1465 in RFC 3023 [RFC3023]. 1467 MIME media type name: application 1469 MIME subtype name: EmergencyCallData.VEDS+xml 1471 Mandatory parameters: none 1473 Optional parameters: charset 1475 Indicates the character encoding of enclosed XML. 1477 Encoding considerations: Uses XML, which can employ 8-bit 1478 characters, depending on the character encoding used. See 1479 Section 3.2 of RFC 3023 [RFC3023]. 1481 Security considerations: 1483 This content type is designed to carry vehicle crash data 1484 during an emergency call. 1486 This data can contain personal information including vehicle 1487 VIN, location, direction, etc. Appropriate precautions need to 1488 be taken to limit unauthorized access, inappropriate disclosure 1489 to third parties, and eavesdropping of this information. 1490 Please refer to Section 7 and Section 8 of [RFC7852] for more 1491 information. 1493 When this content type is contained in a signed or encrypted 1494 body part, the enclosing multipart (e.g., multipart/signed or 1495 multipart/encrypted) has the same Content-ID as the data part. 1496 This allows an entity to identify and access the data blocks it 1497 is interested in without having to dive deeply into the message 1498 structure or decrypt parts it is not interested in. (The 1499 'purpose' parameter in a Call-Info header field identifies the 1500 data, and the CID URL points to the data block in the body, 1501 which has a matching Content-ID body part header field). 1503 Interoperability considerations: None 1504 Published specification: [VEDS] 1506 Applications which use this media type: Emergency Services 1508 Additional information: None 1510 Magic Number: None 1512 File Extension: .xml 1514 Macintosh file type code: 'TEXT' 1516 Persons and email addresses for further information: Randall 1517 Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, 1518 Hannes.Tschofenig@gmx.net 1520 Intended usage: LIMITED USE 1522 Author: This specification is a work item of the IETF ECRIT 1523 working group, with mailing list address . 1525 Change controller: The IESG 1527 15.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1528 Data registry 1530 This specification requests IANA to add the 'VEDS' entry to the 1531 Emergency Call Additional Data registry, with a reference to this 1532 document. The Emergency Call Additional Data registry was 1533 established by [RFC7852]. 1535 15.3. New Action Values 1537 This document adds new values for the 'action' attribute of the 1538 element in the "Action Registry" registry created by 1539 [I-D.ietf-ecrit-ecall]. 1541 +---------------+-------------------------------------+ 1542 | Name | Description | 1543 +---------------+-------------------------------------+ 1544 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1545 | | | 1546 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1547 | | | 1548 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1549 | | | 1550 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1551 | | | 1552 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1553 +---------------+-------------------------------------+ 1555 Table 2: Action Registry New Values 1557 15.4. Static Message Registry 1559 This document creates a new sub-registry called "Static Message 1560 Registry" in the "Metadata/Control Data" registry established by 1561 [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected 1562 to support all static messages translated into all languages 1563 supported by the vehicle, it is important to limit the number of such 1564 messages. As defined in [RFC5226], this registry operates under 1565 "Publication Required" rules, which require a stable, public document 1566 and implies expert review of the publication. The expert should 1567 determine that the document has been published by an appropriate 1568 emergency services organization (e.g., NENA, EENA, APCO) or by the 1569 IETF with input from an emergency services organization, and that the 1570 proposed message is sufficiently distinguishable from other messages. 1572 The contents of this registry are: 1574 ID: An integer identifier to be used in the 'msgid' attribute of a 1575 metadata/control element. 1577 Message: The text of the message. Messages are listed in the 1578 registry in English; vehicles are expected to implement 1579 translations into languages supported by the vehicle. 1581 When new messages are added to the registry, the message text is 1582 determined by the registrant; IANA assigns the IDs. Each message is 1583 assigned a consecutive integer value as its ID. This allows an IVS 1584 to indicate by a single integer value that it supports all messages 1585 with that value or lower. 1587 The initial set of values is listed in Table 3. 1589 +----+--------------------------------------------------------------+ 1590 | ID | Message | 1591 +----+--------------------------------------------------------------+ 1592 | 1 | Emergency authorities are aware of your incident and | 1593 | | location, but are unable to speak with you right now. We | 1594 | | will help you as soon as possible. | 1595 +----+--------------------------------------------------------------+ 1597 Table 3: Static Message Registry 1599 15.5. Lamp ID Registry 1601 This document creates a new sub-registry called "Lamp ID Registry" in 1602 the "Metadata/Control Data" registry established by 1603 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1604 the names of automotive lamps (lights). As defined in [RFC5226], 1605 this registry operates under "Expert Review" rules. The expert 1606 should determine that the proposed lamp name is clearly 1607 understandable and is sufficiently distinguishable from other lamp 1608 names. 1610 The contents of this registry are: 1612 Name: The identifier to be used in the 'lamp-ID' attribute of a 1613 metadata/control element. 1615 Description: A description of the lamp (light). 1617 The initial set of values is listed in Table 4. 1619 +----------------+---------------------------------------------+ 1620 | Name | Description | 1621 +----------------+---------------------------------------------+ 1622 | head | The main lamps used to light the road ahead | 1623 | | | 1624 | interior | Interior lamp, often at the top center | 1625 | | | 1626 | fog-front | Front fog lamps | 1627 | | | 1628 | fog-rear | Rear fog lamps | 1629 | | | 1630 | brake | Brake indicator lamps | 1631 | | | 1632 | brake-center | Center High Mounted Stop Lamp | 1633 | | | 1634 | position-front | Front position/parking/standing lamps | 1635 | | | 1636 | position-rear | Rear position/parking/standing lamps | 1637 | | | 1638 | turn-left | Left turn/directional lamps | 1639 | | | 1640 | turn-right | Right turn/directional lamps | 1641 | | | 1642 | hazard | Hazard/four-way lamps | 1643 +----------------+---------------------------------------------+ 1645 Table 4: Lamp ID Registry Initial Values 1647 15.6. Camera ID Registry 1649 This document creates a new sub-registry called "Camera ID Registry" 1650 in the "Metadata/Control Data" registry established by 1651 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1652 automotive cameras. As defined in [RFC5226], this registry operates 1653 under "Expert Review" rules. The expert should determine that the 1654 proposed camera name is clearly understandable and is sufficiently 1655 distinguishable from other camera names. 1657 The contents of this registry are: 1659 Name: The identifier to be used in the 'camera-ID' attribute of a 1660 control element. 1662 Description: A description of the camera. 1664 The initial set of values is listed in Table 5. 1666 +-------------+-----------------------------------------------------+ 1667 | Name | Description | 1668 +-------------+-----------------------------------------------------+ 1669 | backup | Shows what is behind the vehicle, e.g., often used | 1670 | | for driver display when the vehicle is in reverse. | 1671 | | Also known as rearview, reverse, rear visibility, | 1672 | | etc. | 1673 | | | 1674 | left-rear | Shows view to the left and behind (e.g., left side | 1675 | | rear-view mirror or blind spot view) | 1676 | | | 1677 | right-rear | Shows view to the right and behind (e.g., right | 1678 | | side rear-view mirror or blind spot view) | 1679 | | | 1680 | forward | Shows what is in front of the vehicle | 1681 | | | 1682 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1683 | | collision detection systems), separate from backup | 1684 | | view | 1685 | | | 1686 | lane | Used by systems to identify road lane and/or | 1687 | | monitor vehicle's position within lane | 1688 | | | 1689 | interior | Shows the interior (e.g., driver) | 1690 | | | 1691 | night-front | Night-vision view of what is in front of the | 1692 | | vehicle | 1693 +-------------+-----------------------------------------------------+ 1695 Table 5: Camera ID Registry Initial Values 1697 16. Acknowledgements 1699 We would like to thank Lena Chaponniere, Stephen Edge, and Christer 1700 Holmberg for their review and suggestions; Robert Sparks and Paul 1701 Kyzivat for their help with the SIP mechanisms; Michael Montag, 1702 Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex 1703 Buddenberg for their feedback; and Ulrich Dietz for his help with 1704 earlier versions of the original version of this document. 1706 17. Changes from Previous Versions 1708 17.1. Changes from draft-ietf-10 to draft-ietf-11 1710 o Clarifications suggested by Christer 1711 o Corrections to Content-Disposition text and examples as suggested 1712 by Paul Kyzivat 1714 o Clarifications to Content-Disposition text and examples to clarify 1715 that handling=optional is only used in the initial INVITE 1717 17.2. Changes from draft-ietf-09 to draft-ietf-10 1719 o Fixed errors in examples found by Dale in eCall draft 1720 o Removed enclosing sub-section of INFO package registration section 1721 o Added text per Christer and Dale's suggestions that the MSD and 1722 metadata/control blocks are sent in INFO with a Call-Info header 1723 field referencing them 1724 o Other text changes per comments received from Christer and Ivo 1725 against eCall draft. 1727 17.3. Changes from draft-ietf-08 to draft-ietf-09 1729 o Added INFO package registration for eCall.VEDS 1730 o Moved element and other extension points back to 1731 eCall document so that extension points are in base spec (and also 1732 to get XML schema to compile) 1733 o Text changes for clarification. 1735 17.4. Changes from draft-ietf-07 to draft-ietf-08 1737 o Moved much of the metadata/control object from 1738 [I-D.ietf-ecrit-ecall] to this document as extensions 1739 o Editorial clarifications and simplifications 1740 o Moved "Call Routing" to be a subsection of "Call Setup" 1741 o Deleted "Profile" section and moved some of its text into 1742 "Introduction" 1744 17.5. Changes from draft-ietf-06 to draft-ietf-07 1746 o Minor editorial changes 1748 17.6. Changes from draft-ietf-05 to draft-ietf-06 1750 o Added clarifying text regarding signed and encrypted data 1751 o Additional informative text in "Migration to Next-Generation" 1752 section 1753 o Additional clarifying text regarding security and privacy. 1755 17.7. Changes from draft-ietf-04 to draft-ietf-05 1757 o Reworded security text in main document and in MIME registration 1758 for the VEDS object 1760 17.8. Changes from draft-ietf-03 to draft-ietf-04 1762 o Added example VEDS object 1763 o Additional clarifications and corrections 1764 o Removed references from Abstract 1765 o Moved Document Scope section to follow Introduction 1767 17.9. Changes from draft-ietf-02 to draft-ietf-03 1769 o Additional clarifications and corrections 1771 17.10. Changes from draft-ietf-01 to draft-ietf-02 1773 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1774 aspects including the service URN; this document no longer 1775 proposes a unique service URN for non-eCall NG-ACN calls; the same 1776 service URN is now used for all NG-ACN calls including NG-eCall 1777 and non-eCall 1778 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1779 support it 1780 o Minor wording improvements and clarifications 1782 17.11. Changes from draft-ietf-00 to draft-ietf-01 1784 o Added further discussion of test calls 1785 o Added further clarification to the document scope 1786 o Mentioned that multi-region vehicles may need to support other 1787 crash notification specifications such as eCall 1788 o Minor wording improvements and clarifications 1790 17.12. Changes from draft-gellens-02 to draft-ietf-00 1792 o Renamed from draft-gellens- to draft-ietf- 1793 o Added text to Introduction to clarify that during a CS ACN, the 1794 PSAP call taker usually needs to listen to the data and transcribe 1795 it 1797 17.13. Changes from draft-gellens-01 to -02 1799 o Fixed case of 'EmergencyCallData', in accordance with changes to 1800 [RFC7852] 1802 17.14. Changes from draft-gellens-00 to -01 1804 o Now using 'EmergencyCallData' for purpose parameter values and 1805 MIME subtypes, in accordance with changes to [RFC7852] 1806 o Added reference to RFC 6443 1807 o Fixed bug that caused Figure captions to not appear 1809 18. References 1811 18.1. Normative References 1813 [I-D.ietf-ecrit-ecall] 1814 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1815 European eCall", draft-ietf-ecrit-ecall-11 (work in 1816 progress), August 2016. 1818 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1819 Requirement Levels", BCP 14, RFC 2119, 1820 DOI 10.17487/RFC2119, March 1997, 1821 . 1823 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1824 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1825 . 1827 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1828 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1829 . 1831 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1832 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1833 December 2005, . 1835 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1836 Emergency and Other Well-Known Services", RFC 5031, 1837 DOI 10.17487/RFC5031, January 2008, 1838 . 1840 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1841 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1842 DOI 10.17487/RFC5226, May 2008, 1843 . 1845 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1846 Presence Information Data Format Location Object (PIDF-LO) 1847 Usage Clarification, Considerations, and Recommendations", 1848 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1849 . 1851 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1852 Thomson, "Dynamic Extensions to the Presence Information 1853 Data Format Location Object (PIDF-LO)", RFC 5962, 1854 DOI 10.17487/RFC5962, September 2010, 1855 . 1857 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1858 "Framework for Emergency Calling Using Internet 1859 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1860 2011, . 1862 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1863 Communications Services in Support of Emergency Calling", 1864 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1865 . 1867 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1868 J. Winterbottom, "Additional Data Related to an Emergency 1869 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1870 . 1872 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1873 NENA Data Standardization Workgroup, , "Vehicular 1874 Emergency Data Set (VEDS) version 3", July 2012, 1875 . 1878 18.2. Informative references 1880 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1881 Emergency Context Resolution with Internet Technologies", 1882 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1883 . 1885 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1886 Shanmugam, "Security Threats and Requirements for 1887 Emergency Call Marking and Mapping", RFC 5069, 1888 DOI 10.17487/RFC5069, January 2008, 1889 . 1891 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1892 Initiation Protocol (SIP) INFO Method and Package 1893 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1894 . 1896 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1897 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1898 December 2014, . 1900 [triage-2008] 1901 National Center for Injury Prevention and Control, and 1902 Centers for Disease Control and Prevention, 1903 "Recommendations from the Expert Panel: Advanced Automatic 1904 Collision Notification and Triage of the Injured Patient", 1905 2008, . 1907 [triage-2011] 1908 National Center for Injury Prevention and Control, and 1909 Centers for Disease Control and Prevention, "Guidelines 1910 for field triage of injured patients: recommendations of 1911 the National Expert Panel on Field Triage", January 2012, 1912 . 1917 Authors' Addresses 1919 Randall Gellens 1920 Core Technology Consulting 1922 Email: rg+ietf@randy.pensive.org 1924 Brian Rosen 1925 NeuStar, Inc. 1926 470 Conrad Dr 1927 Mars, PA 16046 1928 US 1930 Email: br@brianrosen.net 1932 Hannes Tschofenig 1933 Individual 1935 Email: Hannes.Tschofenig@gmx.net 1936 URI: http://www.tschofenig.priv.at