idnits 2.17.00 (12 Aug 2021) /tmp/idnits4409/draft-ietf-ecrit-car-crash-12.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 866 has weird spacing: '...dynamic displ...' == Line 869 has weird spacing: '... honk sound...' == Line 871 has weird spacing: '... lamp turns...' == Line 873 has weird spacing: '...-camera adds ...' -- The document date (September 25, 2016) is 2063 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 1836, but no explicit reference was found in the text == Unused Reference: 'RFC5031' is defined on line 1844, but no explicit reference was found in the text == Unused Reference: 'RFC5491' is defined on line 1854, but no explicit reference was found in the text == Unused Reference: 'RFC5962' is defined on line 1860, but no explicit reference was found in the text == 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 (~~), 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 29, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 September 25, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-12.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 29, 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 . . . . . . . . . . . . . . . . . . . . . . . . 17 88 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 89 9.1. New values for the 'action' attribute' . . . . . . . . . 19 90 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19 91 9.3. The element . . . . . . . . . . . . . . . . . . . . 20 92 9.4. The element . . . . . . . . . . . . . . . 21 93 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 22 94 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23 95 11.1. Overall Description . . . . . . . . . . . . . . . . . . 23 96 11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24 97 11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24 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 . . . . . . . . . . . . . . . . . 26 105 11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 26 106 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 107 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 108 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 32 109 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 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 . . . . . . . . . . . . . . . . 34 114 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 34 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 Because the endpoints of an NG-ACN call are a PSAP and an IVS or TSP, 173 to avoid receptively writing "IVS or TSP", the term "IVS" is used to 174 represent either an IVS or TSP when discussing signaling behavior 175 (e.g., attaching VEDS data, sending an INVITE request, receiving an 176 INFO request, etc.). 178 2. Introduction 180 Emergency calls made by in-vehicle systems (e.g., automatically in 181 the event of a crash or serious incident or manually by a vehicle 182 occupant) assist in significantly reducing road deaths and injuries 183 by allowing emergency services to respond quickly and appropriately 184 to the specifics of the incident, often with better location 185 accuracy. 187 Drivers often have a poor location awareness, especially outside of 188 major cities, at night and when away from home (especially abroad). 189 In the most crucial cases, the victim(s) might not be able to call 190 because they have been injured or trapped. 192 For more than two decades, some vehicles have been equipped with 193 telematics systems which, among other features, place an emergency 194 call automatically in the event of a crash or manually in response to 195 an emergency call button. Such systems generally have on-board 196 location determination systems that make use of satellite-based 197 positioning technology, inertial sensors, gyroscopes, etc., which can 198 provide an accurate position for the vehicle. Such built-in systems 199 can take advantage of the benefits of being integrated into a 200 vehicle, such as more power capacity, ability to have larger or 201 specialized antenna, ability to be engineered to avoid or minimise 202 degradation by vehicle glass coatings, interference from other 203 vehicle systems, etc. Thus, the PSAP can be provided with a good 204 estimate of where the vehicle is during an emergency. Vehicle 205 manufacturers are increasingly adopting such systems, both for the 206 safety benefits and for the additional features and services they 207 enable (e.g., remote engine diagnostics, remote door unlock, stolen 208 vehicle tracking and disabling, etc.). 210 The general term for such systems is Automatic Crash Notification 211 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 212 used in this document as a general term. ACN systems transmit some 213 amount of data specific to the incident, referred to generally as 214 "crash data" (the term is commonly used even though there might not 215 have been a crash). While different systems transmit different 216 amounts of crash data, standardized formats, structures, and 217 mechanisms are needed to provide interoperability among systems and 218 PSAPs. 220 As of the date of this document, currently deployed in-vehicle 221 telematics systems are circuit-switched and lack a standards-based 222 ability to convey crash data directly to the PSAP (generally relying 223 on either a human advisor or an automated text-to-speech system to 224 provide the PSAP call taker with some crash data orally, or in some 225 cases via a proprietary mechanism). In most cases, the PSAP call 226 taker needs to first realize that the call is related to a vehicle 227 incident, and then listen to the data and transcribe it. Circuit- 228 switched ACN systems are referred to here as CS-ACN. 230 The transition to next-generation calling in general, and for 231 emergency calling in particular, provides an opportunity to vastly 232 improve the scope, breadth, reliability and usefulness of crash data 233 during an emergency by allowing it to be transmitted during call set- 234 up, and to be automatically processed by the PSAP and made available 235 to the call taker in an integrated, automated way, as well as provide 236 the ability for a PSAP call taker to request that a vehicle take 237 certain actions, such as flashing lights or unlocking doors. In 238 addition, vehicle manufacturers are provided an opportunity to take 239 advantage of the same standardized mechanisms for data transmission 240 and request processing for internal use if they wish (such as 241 telemetry between the vehicle and a service center for both emergency 242 and non-emergency uses, including location-based services, multi- 243 media entertainment systems, remote door unlocking, and road-side 244 assistance applications). 246 Next-generation ACN provides an opportunity for such calls to be 247 recognized and processed as such during call set-up, and routed to an 248 equipped PSAP where the vehicle data is available to assist the call 249 taker in assessing and responding to the situation. Next-generation 250 (IP-based) ACN systems are referred to here as NG-ACN. 252 An ACN call can be initiated by a vehicle occupant or automatically 253 initiated by vehicle systems in the event of a serious incident. 254 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 255 used to refer to the class of calls that are placed by an in-vehicle 256 system (IVS) or Telematics Service Providers (TSP) and that carry 257 incident-related data as well as voice.) Automatically triggered 258 calls indicate a car crash or some other serious incident (e.g., a 259 fire). Manually triggered calls are often reports of observed 260 crashes or serious hazards (such as impaired drivers or roadway 261 debris). In some implementations, manually triggered calls might be 262 more likely to be accidental. 264 This document describes how the IETF mechanisms for IP-based 265 emergency calls, including [RFC6443] and [RFC7852], are used to 266 provide the realization of next-generation ACN. 268 This document reuses the technical aspects of next-generation pan- 269 European eCall (a mandated and standardized system for emergency 270 calls by in-vehicle systems within Europe and other regions), as 271 described in [I-D.ietf-ecrit-ecall]. However, this document 272 specifies a different set of vehicle (crash) data, specifically, the 273 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 274 of Data (MSD). This document is an extension of 275 [I-D.ietf-ecrit-ecall], with the differences being that this document 276 makes the MSD data set optional and VEDS mandatory, and adds new 277 attribute values to the eCall metadata/control object defined in that 278 document. This document also registers a new INFO package (identical 279 to that defined in [I-D.ietf-ecrit-ecall] with the addition of the 280 VEDS MIME type). 282 The Association of Public-Safety Communications Officials (APCO) and 283 the National Emergency Number Association (NENA) have jointly 284 developed a standardized set of incident-related vehicle data for ACN 285 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 286 is often referred to as crash data although it is applicable in 287 incidents other than crashes. 289 VEDS provides a standard data set for the transmission, exchange, and 290 interpretation of vehicle-related data. A standard data format 291 allows the data to be generated by an IVS or TSP and interpreted by 292 PSAPs, emergency responders, and medical facilities. It includes 293 incident-related information such as airbag deployment, location and 294 compass orientation of the vehicle, spatial orientation of the 295 vehicle (e.g., upright, on its side or top or a bumper), various 296 sensor data that can indicate the potential severity of the crash and 297 the likelihood of severe injuries to the vehicle occupants, etc. 298 This data better informs the PSAP and emergency responders as to the 299 type of response that might be needed. Some of this information has 300 been included in U.S. government guidelines for field triage of 301 injured patients [triage-2008] [triage-2011]. These guidelines are 302 designed to help responders identify the potential existence of 303 severe internal injuries and to make critical decisions about how and 304 where a patient needs to be transported. 306 This document registers the 'application/EmergencyCallData.VEDS+xml' 307 MIME content-type, and registers the 'VEDS' entry in the Emergency 308 Call Additional Data registry. 310 VEDS is an XML structure (see [VEDS]) transported in SIP using the 311 'application/EmergencyCallData.VEDS+xml' MIME content-type.. 313 VEDS is a versatile structure that can accomodate varied needs. 314 However, if additional sets of data are determined to be needed 315 (e.g., in the future or in different regions), the steps to enable 316 each data block are very briefly summarized below: 318 o A standardized format and encoding (such as XML) is defined and 319 published by a Standards Development Organization (SDO) 321 o A MIME Content-Type is registered for it (typically under the 322 'Application' media type) with a sub-type starting with 323 'EmergencyCallData.' 325 o An entry for the block is added to the Emergency Call Additional 326 Data Blocks sub-registry (established by [RFC7852]); the registry 327 entry is the root of the MIME sub-type (not including the 328 'EmergencyCallData' prefix and any suffix such as '+xml') 330 o A new INFO package is registered that permits carrying the new 331 content type and the metadata/control object (defined in 332 [I-D.ietf-ecrit-ecall]) in INFO requests. 334 Section 6 describes how VEDS data and metadata/control are 335 transported within NG-ACN calls. Section 7 describes how such calls 336 are placed. 338 These mechanisms are thus used to place emergency calls that are 339 identifiable as ACN calls and that carry standardized crash data in 340 an interoperable way. 342 Calls by in-vehicle systems are placed using cellular networks, which 343 might ignore location information sent by an originating device in an 344 emergency call INVITE, instead attaching their own location 345 information (often determined in cooperation with the originating 346 device). Standardized crash data structures often include location 347 as determined by the IVS. A benefit of this is that it allows the 348 PSAP to see both the location as determined by the cellular network 349 (often in cooperation with the originating device) and the location 350 as determined by the IVS. 352 This specification inherits the ability to utilize test call 353 functionality from Section 15 of [RFC6881]. 355 3. Document Scope 357 This document is focused on how an ACN emergency call is setup and 358 incident-related data (including vehicle, sensor, and location data) 359 is transmitted to the PSAP using IETF specifications. For the direct 360 model, this is the end-to-end description (between the vehicle and 361 the PSAP). For the TSP model, this describes the call leg between 362 the TSP and the PSAP, leaving the call leg between the vehicle and 363 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 364 are then free to use the same mechanism as for the right-hand side or 365 not. 367 Note that Europe has a mandated and standardized system for emergency 368 calls by in-vehicle systems. This pan-European system is known as 369 "eCall" and is the subject of a separate document, 370 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 371 designed to operate in multiple regions might need to support eCall 372 as well as NG-ACN as described here. A vehicle IVS might determine 373 whether to use eCall or ACN by first determining the region or 374 country in which it is located (e.g., from a GNSS location fix and/or 375 identity of or information from an MNO). If other regions adopt 376 other data formats, a multi-region vehicle might need to support 377 those as well. This document adopts the call set-up and other 378 technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852]; 379 this makes it straightforward to use a different data set while 380 keeping other technical aspects unchanged. Hence, both NG-eCall and 381 the NG-ACN mechanism described here are compatible, differing 382 primarily in the specific data block that is sent (the eCall MSD in 383 the case of NG-eCall, and the APCO/NENA VEDS used in this document), 384 and some additions to the metadata/control data block. If other 385 regions adopt their own vehicle data sets, this can be similarly 386 accomodated without changing other technical aspects. Note that any 387 additional data blocks require a new INFO package to permit transport 388 within INFO requests. 390 4. Overview of Legacy Deployment Models 392 Legacy (circuit-switched) systems for placing emergency calls by in- 393 vehicle systems generally have some ability to convey at least 394 location and in some cases telematics data to the PSAP. Most such 395 systems use one of three architectural models, which are described 396 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 397 These three models are illustrated below. 399 In the TSP model, both emergency and non-emergency calls are placed 400 to a Telematics Service Provider (TSP); a proprietary technique is 401 used for data transfer (such as a proprietary in-band modem) between 402 the TSP and the vehicle. 404 In an emergency, generally the TSP call taker bridges in the PSAP and 405 communicates location, crash data (such as impact severity and trauma 406 prediction), and other data (such as the vehicle description) to the 407 PSAP call taker verbally (in some cases, a proprietary out-of-band 408 interface is used). Since the TSP knows the location of the vehicle 409 (from on-board GNSS and sensors), location-based routing is usually 410 used to route to the appropriate PSAP. In some cases, the TSP is 411 able to transmit location automatically, using similar techniques as 412 for wireless calls. Typically, a three-way voice call is established 413 between the vehicle, the TSP, and the PSAP, allowing communication 414 between the PSAP call taker, the TSP call taker, and the vehicle 415 occupants (who might be unconscious). 417 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 418 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 419 \\\----/// crash data +------+ location via trunk +------+ 421 Figure 1: Legacy TSP Model. 423 In the paired model, the IVS uses a Bluetooth link with a previously- 424 paired handset to establish an emergency call with the PSAP (by 425 dialing a standard emergency number; 9-1-1 in North America), and 426 then communicates location data to the PSAP via text-to-speech; crash 427 data might or might not be conveyed also using text-to-speech. Some 428 such systems use an automated voice prompt menu for the PSAP call 429 taker (e.g., "this is an automatic emergency call from a vehicle; 430 press 1 to open a voice path to the vehicle; press 2 to hear the 431 location read out") to allow the call taker to request location data 432 via text-to-speech. 434 +---+ 435 ///----\\\ | H | 911/etc voice call via handset +------+ 436 ||| IVS |||-->| S +----------------------------------->+ PSAP | 437 \\\----/// +---+ location via text-to-speech +------+ 439 Figure 2: Legacy Paired Model 441 In the direct model, the IVS directly places an emergency call with 442 the PSAP by dialing a standard emergency number (9-1-1 in North 443 America). Such systems might communicate location data to the PSAP 444 via text-to-speech; crash data might or might not be conveyed using 445 text-to-speech. Some such systems use an automated voice prompt menu 446 (e.g., "this is an automatic emergency call from a vehicle; press 1 447 to open a voice path to the vehicle; press 2 to hear the location 448 read out") to allow the call taker to request location data via text- 449 to-speech. 451 ///----\\\ 911/etc voice call via IVS +------+ 452 ||| IVS |||---------------------------------------->+ PSAP | 453 \\\----/// location via text-to-speech +------+ 455 Figure 3: Legacy Direct Model 457 5. Migration to Next-Generation 459 Migration of emergency calls placed by in-vehicle systems to next- 460 generation (all-IP) technology per this document provides a 461 standardized mechanism to identify such calls and to present crash 462 data with the call, as well as enabling additional communications 463 modalities and enhanced functionality. This allows ACN calls and 464 crash data to be automatically processed by the PSAP and made 465 available to the call taker in an integrated, automated way. Because 466 the crash data is carried in the initial SIP INVITE (per [RFC7852]) 467 the PSAP can present it to the call taker simultaneously with the 468 appearance of the call. The PSAP can also process the data to take 469 other actions (e.g., if multiple calls from the same location arrive 470 when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP 471 might choose to store the information and reject the calls, since the 472 IVS will receive confirmation that the information has been 473 successfully received; a PSAP could also choose to include a message 474 stating that it is aware of the incident and responders are on the 475 way; a PSAP could call the vehicle back when a call taker is 476 available). 478 Origination devices and networks, PSAPs, emergency services networks, 479 and other telephony environments are migrating to next-generation. 480 This provides opportunities for significant enhancement to 481 interoperability and functionality, especially for emergency calls 482 carrying additional data such as vehicle crash data. (In the U.S., a 483 network specifically for emergency responders is being developed. 484 This network, FirstNet, will be next-generation from the start, 485 enhancing the ability for data exchange between PSAPs and 486 responders.) 488 Migration to next-generation (NG) provides an opportunity to 489 significantly improve the handling and response to vehicle-initiated 490 emergency calls. Such calls can be recognized as originating from a 491 vehicle, routed to a PSAP equipped both technically and operationally 492 to handle such calls, and the vehicle-determined location and crash 493 data can be made available to the call taker simultaneously with the 494 call appearance. The PSAP can take advantage of enhanced 495 functionality, including the ability to request the vehicle to take 496 an action, such as sending an updated set of data, converying a 497 message to the occupants, flashing lights, unlocking doors, etc. 499 Vehicle manufacturers using the TSP model can choose to take 500 advantage of the same mechanism to carry telematics data and requests 501 and responses between the vehicle and the TSP for both emergency and 502 non-emergency calls as are used for the interface with the PSAP. 504 A next-generation IVS establishes an emergency call using the 505 emergency call solution as described in [RFC6443] and [RFC6881], with 506 the difference that the Request-URI indicates an ACN type of 507 emergency call, the IVS typically does not perform routing or 508 location queries but relies on the carrier for this, and uses Call- 509 Info header fields to indicates that vehicle crash and capabilities 510 data is attached. When an ESInet is deployed, the MNO only needs to 511 recognize the call as an emergency call and route it to an ESInet. 512 The ESInet can recognize the call as an ACN with vehicle data and can 513 route the call to an NG-ACN capable PSAP. Such a PSAP can interpret 514 the vehicle data sent with the call and make it available to the call 515 taker. 517 [I-D.ietf-ecrit-ecall] registers new service URN children within the 518 "sos" subservice. These URNs request NG-ACN resources, and 519 differentiate between manually and automatically triggered NG-ACN 520 calls (which might be subject to different treatment depending on 521 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 522 are "urn:service:sos.ecall.automatic" and 523 "urn:service:sos.ecall.manual". The same service URNs are used for 524 ACN as for eCall since in any region only one of these is supported, 525 making a distinction unnecessary. (Further, PSAP equipment might 526 support multiple data formats, allowing a PSAP to handle a vehicle 527 that erroneously sent the wrong data object.) 529 Note that in North America, routing queries performed by clients 530 outside of an ESInet typically treat all sub-services of "sos" 531 identically to "sos" with no sub-service. However, the Request-URI 532 header field retains the full sub-service; route and handling 533 decisions within an ESInet or PSAP can take the sub-service into 534 account. For example, in a region with multiple cooperating PSAPs, 535 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 536 one that specializes in vehicle-related incidents. 538 Migration of the three architectural models to next-generation (all- 539 IP) is described below. 541 In the TSP model, the IVS transmits crash and location data to the 542 TSP either by re-using the mechanisms and data objects described 543 here, or using a proprietary mechanism. In an emergency, the TSP 544 bridges in the PSAP and the TSP transmits crash and other data to the 545 PSAP using the mechanisms and data objects described here. There is 546 a three-way call between the vehicle, the TSP, and the PSAP, allowing 547 communication between the PSAP call taker, the TSP call taker, and 548 the vehicle occupants (who might be unconscious). The TSP relays 549 PSAP requests and vehicle responses. 551 proprietary 552 ///----\\\ or standard +------+ standard +------+ 553 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 554 \\\----/// crash + other data +------+ crash + other data +------+ 556 Figure 4: Next-Generation TSP Model 558 The vehicle manufacturer and the TSP can choose to use the same 559 mechanisms and data objects on the left call leg in Figure 4 as on 560 the right. (Note that the TSP model can be more difficult when the 561 vehicle is in a different country than the TSP (e.g., a US resident 562 driving in Canada or Mexico) because of the additional complexity in 563 choosing the correct PSAP based on vehicle location performed by a 564 TSP in a different country.) 565 In the direct model, the IVS communicates crash data to the PSAP 566 directly using the mechanisms and data objects described here. 568 ///----\\\ NG emergency call +------+ 569 ||| IVS |||----------------------------------------->+ PSAP | 570 \\\----/// crash + other data +------+ 572 Figure 5: Next-Generation Direct Model 574 In the paired model, the IVS uses a Bluetooth link to a previously- 575 paired handset to establish an emergency call with the PSAP; it is 576 undefined what facilities are or will be available for transmitting 577 crash data through the Bluetooth link to the handset for inclusion in 578 an NG emergency call. Hence, manufacturers that use the paired model 579 for legacy calls might choose to adopt either the direct or TSP 580 models for next-generation calls. 582 +---+ 583 ///----\\\ (undefined) | H | standard +------+ 584 ||| IVS |||------------------>| S +------------------->+ PSAP | 585 \\\----/// (undefined) +---+ crash + other data +------+ 587 Figure 6: Next-Generation Paired Model 589 If the call is routed to a PSAP that is not capable of processing the 590 vehicle data, the PSAP ignores (or does not receive) the vehicle 591 data. This is detectable by the IVS or TSP when the status response 592 to the INVITE (e.., 200 OK) lacks a control structure acknowledging 593 receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then 594 proceeds as it would for a CS-ACN call (e.g., verbal conveyance of 595 data) 597 6. Data Transport 599 [RFC7852] establishes a general mechanism for attaching blocks of 600 data to a SIP emergency call. This mechanism permits certain 601 emergency call MIME types to be attached to SIP messages. This 602 document makes use of that mechanism. This document also registers 603 an INFO package (in Section 11) to enable NG-ACN related data blocks 604 to be carried in SIP INFO requests (per [RFC6086], new INFO usages 605 require the definition of an INFO package). 607 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 608 by attaching it to a SIP message as a MIME body part per [RFC7852]. 609 The body part is identified by its MIME content-type ('application/ 610 emergencyCallData.eCall.VEDS+xml') in the Content-Type header field 611 of the body part. The body part is assigned a unique identifier 612 which is listed in a Content-ID header field in the body part. The 613 SIP message is marked as containing the VEDS data by adding (or 614 appending to) a Call-Info header field at the top level of the SIP 615 message. This Call-Info header field contains a CID URL referencing 616 the body part's unique identifier, and a 'purpose' parameter 617 identifying the data as a VEDS data block per the Emergency Call 618 Additional Data Blocks registry entry; the 'purpose' parameter's 619 value is 'emergencyCallData.VEDS'. A VEDS data block is carried in a 620 SIP INFO request by using the INFO package defined in Section 11. 622 A PSAP or IVS transmits a metadata/control object (see 623 [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME 624 body part per [RFC7852]. The body part is identified by its MIME 625 content-type ('application/emergencyCallData.control+xml') in the 626 Content-Type header field of the body part. The body part is 627 assigned a unique identifier which is listed in a Content-ID header 628 field in the body part. The SIP message is marked as containing the 629 metadata/control block by adding (or appending to) a Call-Info header 630 field at the top level of the SIP message. This Call-Info header 631 field contains a CID URL referencing the body part's unique 632 identifier, and a 'purpose' parameter identifying the data as a 633 metadata/control block per the Emergency Call Additional Data Blocks 634 registry entry; the 'purpose' parameter's value is 635 'emergencyCallData.control'. A metadata/control object is carried in 636 a SIP INFO request by using the INFO package defined in Section 11. 638 As is necessary with message bodies, if a VEDS or a metadata/control 639 block is sent in the same message with another body part, a 640 multipart/mixed body part encloses all body parts. In some cases, 641 there are intermediate multipart body parts between the top level 642 multipart/mixed and the body part containing the VEDS or metadata/ 643 control object. 645 A body part containing a VEDS or metadata/control object has a 646 Content-Disposition header field value containing "By-Reference" 647 unless it is the only body part in a SIP INFO request, in which case, 648 per [RFC6086], "INFO-Package" is used. 650 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 651 initial INVITE a VEDS data block and a metadata/control object 652 informing the PSAP of its capabilities. The VEDS and metadata/ 653 control body parts (and PIDF-LO) have a Content-Disposition header 654 field with the value "By-Reference; handling=optional". Specifying 655 handling=optional prevents the INVITE from being rejected if it is 656 processed by a legacy element (e.g., a gateway between SIP and 657 circuit-switched environments) that does not understand the VEDS or 658 metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ 659 control object acknowledging receipt of the VEDS data and includes it 660 in the SIP final response to the INVITE. The metadata/control object 661 is not attached to provisional (e.g., 180) responses. 663 If the IVS receives an acknowledgment for a VEDS data object with 664 received=false, it indicates some fault with the transfer of the 665 VEDS, the VEDS content, or the PSAP's ability to properly receive, 666 decode and act on the VEDS. The IVS action is not defined (e.g., it 667 might only log an error). Since the PSAP is able to request an 668 updated VEDS during the call, if an initial VEDS is unsatisfactory in 669 any way, the PSAP can choose to request another one. 671 A PSAP can request that the vehicle send an updated VEDS data block 672 during a call. To do so, the PSAP creates a metadata/control object 673 requesting VEDS data and attaches it to a SIP INFO request and sends 674 it within the dialog. The IVS then attaches an updated VEDS data 675 object to a SIP INFO request and sends it within the dialog. If the 676 IVS is unable to send the VEDS, it instead sends a metadata/control 677 object acknowledging the request with the 'success' parameter set to 678 'false' and a 'reason' parameter (and optionally a 'details' 679 parameter) indicating why the request cannot be accomplished. Per 680 [RFC6086], metadata/control objects and VEDS data are sent using the 681 INFO package defined in Section 11. In addition, to align with the 682 way a VEDS or metadata/control block is transmitted in a SIP message 683 other than an INFO request, one or more Call-Info header fields are 684 included in the SIP INFO request to reference the VEDS or metadata/ 685 control block. See Section 11 for more information on the use of 686 INFO requests within NG-ACN calls. 688 If the IVS is aware that VEDS data it sent previously has changed, it 689 MAY send an unsolicited VEDS (in any convenient SIP message, 690 including an INFO request) during the call. The PSAP sends an 691 acknowledgment of an unsolicited VEDS object (if the IVS sent the 692 unsolicited VEDS in an INFO request, the acknowledgment is sent in a 693 new INFO request, otherwise it is sent in the response to the message 694 containing the VEDS). 696 7. Call Setup 698 A next-generation In-Vehicle System (IVS) initiates an NG-ACN call 699 with a SIP INVITE using one of the SOS sub-services 700 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, 701 standard sets of crash data and capabilities data encoded in 702 standardized and registered formats, attached as additional data 703 blocks as specified in Section 4.1 of [RFC7852]. As described in 704 that document, each data block is identified by its MIME content- 705 type, and pointed to by a CID URL in a Call-Info header with a 706 'purpose' parameter value corresponding to the data block. 708 If new data blocks are needed (e.g., in other regions or in the 709 future), the steps required during standardization are briefly 710 summarized below: 712 o A set of data is standardized by an SDO or appropriate 713 organization 715 o A MIME Content-Type for the crash data set is registered with IANA 717 * If the data is specifically for use in emergency calling, the 718 MIME type is normally under the 'application' type with a 719 subtype starting with 'EmergencyCallData.' 721 * If the data format is XML, then by convention the name has a 722 suffix of '+xml' 724 o The item is registered in the Emergency Call Additional Data 725 registry, as defined in Section 9.1.7 of [RFC7852] 727 * For emergency-call-specific formats, the registered name is the 728 root of the MIME Content-Type (not including the 729 'EmergencyCallData' prefix and any suffix such as '+xml') as 730 described in Section 4.1 of [RFC7852]. 732 o A new INFO package is registered that permits carrying the the new 733 content type, the metadata/control object (defined in 734 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 735 objects, in INFO messages. 737 When placing an emergency call, the crash data set and IVS capability 738 data are transported as described in Section 6. 740 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 741 the Association of Public-Safety Communications Officials (APCO) and 742 the National Emergency Number Association (NENA) [VEDS]. It is 743 carried in body part with MIME content-type 'application/ 744 EmergencyCallData.VEDS+xml'. 746 Entities along the path between the vehicle and the PSAP are able to 747 identify the call as an ACN call and handle it appropriately. The 748 PSAP is able to identify the crash and capabilities data attached to 749 the INVITE by examining the Call-Info header fields for 'purpose' 750 parameters whose values start with 'EmergencyCallData.' The PSAP is 751 able to access the data it is capable of handling and is interested 752 in by checking the 'purpose' parameter values. 754 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 755 up and other normative requirements with the exception that in this 756 document, support for the eCall MSD is OPTIONAL and support for VEDS 757 in REQUIRED. This document also adds new attribute values to the 758 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 760 8. Call Routing 762 An Emergency Services IP Network (ESInet) is a network operated by or 763 on behalf of emergency services authorities. It handles emergency 764 call routing and processing before delivery to a PSAP. In the 765 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 766 architecture adopted by EENA, each PSAP is connected to one or more 767 ESInets. Each originating network is also connected to one or more 768 ESInets. The ESInets maintain policy-based routing rules that 769 control the routing and processing of emergency calls. The 770 centralization of such rules within ESInets allows for a cleaner 771 separation between the responsibilities of the originating network 772 and that of the emergency services network, and provides greater 773 flexibility and control over processing of emergency calls by the 774 emergency services authorities and PSAPs. This can make it easier to 775 react quickly to situations that require changes in how emergency 776 calls are routed or handled (e.g., a natural disaster closes a PSAP), 777 as well as ease in making long-term changes that affect such routing 778 (e.g., cooperative agreements to specially handle calls requiring 779 translation or relay services). 781 In an environment that uses ESInets, the originating network might 782 pass all types of emergency calls to an ESInet (all calls with a 783 service URN of or starting with "sos"). The ESInet then routs such 784 calls to an appropriate PSAP. In an environment without an ESInet, 785 the emergency services authorities and the originating carriers 786 determine how such calls are routed. 788 9. New Metadata/Control Values 790 This document adds new attribute values to the metadata/control 791 structure defined in [I-D.ietf-ecrit-ecall]. 793 In addition to the base usage from the PSAP to the IVS to 794 acknowledge receipt of crash data, the element is also 795 contained in a metadata/control block sent by the IVS to the PSAP. 796 This is used by the IVS to acknowledge receipt of a request by the 797 PSAP and indicate if the request was carried out when that request 798 would not otherwise be acknowledged (if the PSAP requests the 799 vehicle to send data and the vehicle does so, the data serves as a 800 success acknowledgement). 802 The element is used in a metadata/control block 803 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 804 inform the PSAP of the vehicle capabilities. Child elements 805 contain all actions and data types supported by the vehicle and 806 all available lamps (lights) and cameras. 808 New request values are added to the element to enable 809 the PSAP to request the vehicle to perform actions. 811 Mandatory Actions (the IVS and the PSAP MUST support): 813 o Transmit data object (VEDS MUST be supported; MSD MAY be 814 supported) 816 Optional Actions (the IVS and the PSAP MAY support): 818 o Play and/or display static (pre-defined) message 819 o Speak/display dynamic text (text supplied in action) 820 o Flash or turn on or off a lamp (light) 821 o Honk horn 822 o Enable a camera 824 The element indicates the object being acknowledged (i.e., a 825 data object or a metadata/control block containing 826 elements), and reports success or failure. 828 The element has child elements indicating 829 the actions supported by the IVS. 831 The element contains attributes to indicate the request and 832 to supply any needed information, and MAY contain a child 833 element to contain the text for a dynamic message. The 'action' 834 attribute is mandatory and indicates the specific action. 835 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 836 allowed values; this document adds new values to that registry in 837 Table 2. 839 Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block 840 in response to the VEDS data sent by the IVS in SIP requests other 841 than INFO (e.g., the INVITE). This metadata/control block is sent in 842 the SIP response to the request (e.g., the INVITE response). When 843 the PSAP needs to send a control block that is not an immediate 844 response to a VEDS or other data sent by the IVS, the control block 845 is transmitted from the PSAP to the IVS in a SIP INFO request within 846 the established dialog. The IVS sends the requested data (e.g., the 847 VEDS) or an acknowledgment (for requests other than to send data) in 848 a new INFO request. This mechanism flexibly allows the PSAP to send 849 metadata/control data to the IVS and the IVS to respond. If control 850 data sent in a response message requests the IVS to send a new VEDS 851 or other data block, or to perform an action other than sending data, 852 the IVS sends the requested data or an acknowledgment regarding the 853 action in an INFO message within the dialog. 855 9.1. New values for the 'action' attribute' 857 The following new "action" values are defined: 859 msg-static: displays or plays a predefined message (translated as 860 appropriate for the language of the vehicle's interface). A 861 registry is created in Section 15.4 for messages and their IDs. 862 Vehicles include the highest registered message in their 863 element to indicate support for all messages up to 864 and including the indicated value. 866 msg-dynamic displays or speaks (via text-to-speech) a dynamic 867 message included in the request. 869 honk sounds the horn. 871 lamp turns a lamp (light) on, off, or flashes. 873 enable-camera adds a one-way media stream (established via SIP re- 874 INVITE sent by the vehicle) to enable the PSAP call taker to view 875 a feed from a camera. 877 Note that there is no 'request' action to play dynamic media (such as 878 an audio message). The PSAP can send a SIP re-INVITE to establish a 879 one-way media stream for this purpose. 881 9.2. Request Example 882 883 888 889 891 892 893 Remain calm. Help is on the way. 894 896 898 Figure 7: Request Example 900 9.3. The element 902 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 903 PSAP to acknowledge the MSD. Here, the element is also 904 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 905 to acknowledge receipt of a element that requested the IVS 906 to perform an action other than transmitting a data object (e.g., a 907 request to display a message would be acknowledged, but a request to 908 transmit VEDS data would not result in a separate element being 909 sent, since the data object itself serves as acknowledgment.) An 910 element sent by an IVS references the unique ID of the 911 metadata/control object containing the request(s) and indicates 912 whether the request was successfully performed, and if not, 913 optionally includes an explanation. 915 9.3.1. Ack Examples 916 917 922 923 924 926 928 930 Figure 8: Ack Example from IVS to PSAP 932 9.4. The element 934 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 935 the IVS to indicate its capabilities to the PSAP. 937 The element contains a child element per 938 action supported by the vehicle. The vehicle MUST support sending 939 the VEDS data object and so includes at a minimum a child 940 element with the 'action' attribute set to "send-data" and the 941 'supported-values' attribute containing all data blocks supported by 942 the IV, which MUST include 'VEDS'. All other actions are OPTIONAL. 944 If the "msg-static" action is supported, a child element 945 with the 'action' attribute set to "msg-static" is included, with the 946 'msgid' attribute set to the highest supported static message 947 supported by the vehicle. A registry is created in Section 15.4 to 948 map 'msgid' values to static text messages. By sending the highest 949 supported static message number in its element, the 950 vehicle indicates its support for all static messages in the registry 951 up to and including that value. 953 If the "lamp" action is supported, a child element with the 954 'action' attribute set to "lamp" is included, with the 'supported- 955 values' attribute set to all supported lamp IDs. A registry is 956 created in Section 15.5 to contain lamp ID values. 958 If the "enable-camera" action is supported, a child element 959 with the 'action' attribute set to "enable-camera" is included, with 960 the 'supported-values' attribute set to all supported camera IDs. A 961 registry is created in Section 15.6 to contain camera ID values. 963 9.4.1. Capabilities Example 965 966 971 972 973 976 977 978 979 980 982 984 Figure 9: Capabilities Example 986 10. Test Calls 988 An NG-ACN test call is a call that is recognized and treated to some 989 extent as an NG-ACN call but not given emergency call treatment and 990 not handled by a call taker. The specific handling of test NG-ACN 991 calls is not itself standardized; the test call facility is intended 992 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 993 successfully established with voice and/or other media communication. 994 The IVS might also be able to verify that the crash data was 995 successfully received. 997 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 998 ability to utilize test call functionality from Section 15 of 999 [RFC6881]. A service URN starting with "test." indicates a test 1000 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 1001 for test calls. 1003 MNOs, emergency authorities, ESInets, and PSAPs determine how to 1004 treat a vehicle call requesting the "test" service URN so that the 1005 desired functionality is tested, but this is outside the scope of 1006 this document. (One possibility is that MNOs route such calls as 1007 non-emergency calls to an ESInet, which routes them to a PSAP that 1008 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 1009 data acknowledgment, and plays an audio clip (for example, saying 1010 that the call reached an appropriate PSAP and the vehicle data was 1011 successfully processed) in addition to supporting media loopback per 1012 [RFC6881]). 1014 Note that since test calls are placed using "test" as the parent 1015 service URN and "sos" as a child, such calls are not treated as an 1016 emergency call and so some functionality might not apply (such as 1017 preemption or service availability for devices lacking service ("non- 1018 service-initialized" or "NSI" devices) if those are available for 1019 emergency calls). 1021 11. The emergencyCallData.eCall.VEDS INFO package 1023 This document registers the 'emergencyCallData.eCall.VEDS' INFO 1024 package. 1026 Both endpoints (the IVS and the PSAP equipment) include 1027 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 1028 [RFC6086] to indicate ability to receive INFO messages carrying data 1029 as described here. 1031 Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates 1032 the ability to receive NG-ACN related body parts as specified in 1033 [TBD: THIS DOCUMENT]. 1035 An INFO request message carrying data related to an emergency call as 1036 described in [TBD: THIS DOCUMENT] has an Info-Package header field 1037 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 1039 The requirements of Section 10 of [RFC6086] are addressed in the 1040 following sections. 1042 11.1. Overall Description 1044 This section describes "what type of information is carried in INFO 1045 requests associated with the Info Package, and for what types of 1046 applications and functionalities UAs can use the Info Package." 1048 INFO requests associated with the emergencyCallData.eCall.VEDS INFO 1049 package carry data associated with emergency calls as defined in 1050 [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency 1051 calls established using SIP. The functionality is to carry vehicle 1052 data and metadata/control information between vehicles and PSAPs. 1053 Refer to [TBD: THIS DOCUMENT] for more information. 1055 11.2. Applicability 1057 This section describes "why the Info Package mechanism, rather than 1058 some other mechanism, has been chosen for the specific use-case...." 1060 The use of INFO is based on an analysis of the requirements against 1061 the intent and effects of INFO versus other approaches (which 1062 included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane 1063 transport, and non-SIP protocols). In particular, the transport of 1064 emergency call data blocks occurs within a SIP emergency dialog, per 1065 Section 6, and is normally carried in the initial INVITE and its 1066 response; the use of INFO only occurs when emergency-call-related 1067 data needs to be sent mid-call. While MESSAGE could be used, it is 1068 not tied to a SIP dialog as is INFO and thus might not be associated 1069 with the dialog. SIP OPTIONS or re-INVITE could also be used, but is 1070 seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into 1071 service, but the semantics are not a good fit, e.g., the subscribe/ 1072 notify mechanism provides one-way communication consisting of (often 1073 multiple) notifications from notifier to subscriber indicating that 1074 certain events in notifier have occurred, whereas what's needed here 1075 is two-way communication of data related to the emergency dialog. 1076 Use of the media plane mechanisms was discounted because the number 1077 of messages needing to be exchanged in a dialog is normally zero or 1078 very few, and the size of the data is likewise very small. The 1079 overhead caused by user plane setup (e.g., to use MSRP as transport) 1080 would be disproportionately large. 1082 Based on the the analyses, the SIP INFO method was chosen to provide 1083 for mid-call data transport. 1085 11.3. Info Package Name 1087 The info package name is emergencyCallData.eCall.VEDS 1089 11.4. Info Package Parameters 1091 None 1093 11.5. SIP Option-Tags 1095 None 1097 11.6. INFO Message Body Parts 1099 The body for an emergencyCallData.eCall.VEDS info package is: 1101 o an application/emergencyCallData.eCall.VEDS+xml (containing a VEDS 1102 data block), or 1104 o an application/emergencyCallData.control+xml (containing a 1105 metadata/control object), or 1107 o an application/emergencyCallData.eCall.MSD+per (containing an 1108 MSD), or 1110 o a multipart body containing: 1112 * zero or one application/emergencyCallData.eCall.VEDS+xml part 1113 (containing a VEDS data block), 1115 * zero or more application/emergencyCallData.control+xml 1116 (containing a metadata/control object), 1118 * zero or one application/emergencyCallData.eCall.MSD+per part 1119 (containing an MSD), 1121 The body parts are sent per [RFC6086], and in addition, to align with 1122 with how these body parts are sent in non-INFO messages, each 1123 associated body part is referenced by a Call-Info header field at the 1124 top level of the SIP message. If the body part is the only body 1125 part, it has a Content-Disposition header field value of "INFO- 1126 Package". If the body part is contained within a multipart, it has a 1127 Content-Disposition header field value of "By-Reference". 1129 Service providers are not expected to attach [RFC7852] Additional 1130 Data to an INFO request. 1132 See [TBD: THIS DOCUMENT] for more information. 1134 11.7. Info Package Usage Restrictions 1136 Usage is limited to vehicle-initiated emergency calls as defined in 1137 [TBD: THIS DOCUMENT]. 1139 11.8. Rate of INFO Requests 1141 The rate of SIP INFO requests associated with the 1142 emergencyCallData.eCall.VEDS info package is normally quite low (most 1143 dialogs are likely to contain zero INFO requests, while others can be 1144 expected to carry an occasional request). 1146 11.9. Info Package Security Considerations 1148 The MIME content type registations for the data blocks that can be 1149 carried using this INFO package contains a discussion of the security 1150 and/or privacy considerations specific to that data block. The 1151 "Security Considerations" and "Privacy Considerations" sections of 1153 [TBD: THIS DOCUMENT] discuss security and privacy considerations of 1154 the data carried in vehicle-initiated emergency calls as described in 1155 that document. 1157 11.10. Implementation Details 1159 See [TBD: THIS DOCUMENT] for protocol details. 1161 11.11. Examples 1163 See [TBD: THIS DOCUMENT] for protocol examples. 1165 12. Example 1167 Figure 10 shows an NG-ACN call routing. The mobile network operator 1168 (MNO) routes the call to an Emergency services IP Network (ESInet), 1169 as for any emergency call. The ESInet routes the call to an 1170 appropriate NG-ACN-capable PSAP (using location information and the 1171 fact that that it is an NG-ACN call). The call is processed by the 1172 Emergency Services Routing Proxy (ESRP), as the entry point to the 1173 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 1174 PSAP, where the call is received by a call taker. (In deployments 1175 where there is no ESInet, the MNO itself routes the call directly to 1176 an appropriate NG-ACN-capable PSAP.) 1178 +---------------------------------------+ 1179 | | 1180 +------------+ | +-------+ | 1181 | | | | PSAP2 | | 1182 | | | +-------+ | 1183 | Originating| | | 1184 | Mobile | | +------+ +-------+ | 1185 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1186 | | | +------+ +-------+ | 1187 | | | | 1188 +------------+ | +-------+ | 1189 | | PSAP3 | | 1190 | +-------+ | 1191 | | 1192 | | 1193 | | 1194 | ESInet | 1195 +---------------------------------------+ 1197 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1199 The example, shown in Figure 11, illustrates a SIP emergency call 1200 INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS 1201 data block), and capabilities data (an eCall metadata/control block 1202 with extensions defined in this document) attached to the SIP INVITE 1203 message. The INVITE has a request URI containing the 1204 'urn:service:sos.ecall.automatic' service URN. 1206 The example VEDS data structure shows information about about a 1207 crashed vehicle. The example communicates that the car is a model 1208 year 2015 Saab 9-5 (a car which does not exist). The front airbag 1209 deployed as a consequence of the crash. The 1210 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 1211 passenger car (the code is set to '101') and that it is not a 1212 convertible (the 'ConvertibleIndicator' value is set to 'false'). 1214 The 'VehicleCrashPulse' element provides further information about 1215 the crash, namely that the force of impact based on the change in 1216 velocity over the duration of the crash pulse was 100 MPH. The 1217 principal direction of the force of the impact is set to '12' (which 1218 refers to 12 O'Clock, corresponding to a frontal collision). This 1219 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1220 element. 1222 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1223 quarter turns in concert with a rollover expressed as a number; in 1224 our case 1. 1226 No roll bar was deployed, as indicated in 1227 'VehicleRollbarDeployedIndicator' being set to 'false'. 1229 Next, there is information indicating seatbelt and seat sensor data 1230 for individual seat positions in the vehicle. In our example, 1231 information from the driver seat is available (value '1' in the 1232 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1233 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1234 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1235 and the seat sensor determined that the seat was occupied 1236 ('VehicleSeatOccupiedIndicator' element). 1238 Finally, information about the weight of the vehicle, which is 600 1239 kilogram in our example. 1241 In addition to the information about the vehicle, further indications 1242 are provided, namely the presence of fuel leakage 1243 ('FuelLeakingIndicator' element), an indication whether the vehicle 1244 was subjected to multiple impacts ('MultipleImpactsIndicator' 1245 element), the orientation of the vehicle at final rest 1246 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1247 that there are no parts of the vehicle on fire (the 1248 'VehicleFireIndicator' element). 1250 INVITE urn:service:sos.ecall.automatic SIP/2.0 1251 To: urn:service:sos.ecall.automatic 1252 From: ;tag=9fxced76sl 1253 Call-ID: 3848276298220188511@atlanta.example.com 1254 Geolocation: 1255 Geolocation-Routing: no 1256 Call-Info: ; 1257 purpose=EmergencyCallData.VEDS 1258 Call-Info: ; 1259 purpose=emergencyCallData.control 1260 Accept: application/sdp, application/pidf+xml, 1261 application/emergencyCallData.control+xml 1262 Recv-Info: emergencyCallData.eCall 1263 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1264 SUBSCRIBE, NOTIFY, UPDATE 1265 CSeq: 31862 INVITE 1266 Content-Type: multipart/mixed; boundary=boundary1 1267 Content-Length: ... 1269 --boundary1 1270 Content-Type: application/sdp 1272 ...Session Description Protocol (SDP) goes here 1274 --boundary1 1275 Content-Type: application/pidf+xml 1276 Content-ID: 1277 Content-Disposition: by-reference;handling=optional 1279 1280 1288 1289 1290 1291 1292 -34.407 150.883 1293 1294 1295 278 1296 1297 1299 1300 1301 gps 1302 1303 2012-04-5T10:18:29Z 1304 1M8GDM9A_KP042788 1305 1306 1308 --boundary1 1309 Content-Type: application/EmergencyCallData.VEDS+xml 1310 Content-ID: <1234567890@atlanta.example.com> 1311 Content-Disposition: by-reference;handling=optional 1313 1314 1318 1319 1320 Saab 1321 1322 1323 9-5 1324 1325 1327 2015 1328 1329 1330 FRONT 1331 true 1332 1333 1334 false 1335 MAIN 1336 1338 101 1339 1340 1341 1342 1344 100 1345 1346 1348 MPH 1349 1350 12 1351 1352 1 1353 1354 1355 false 1356 1357 1358 1 1359 1360 true 1361 1362 true 1363 1364 true 1365 1366 1367 1369 1371 600 1372 1373 1375 kilogram 1376 1377 1378 1379 true 1380 false 1381 true 1382 Driver 1383 1384 false 1385 1386 1388 --boundary1 1389 Content-Type: application/emergencyCallData.control+xml 1390 Content-ID: <1234567892@atlanta.example.com> 1391 Content-Disposition: by-reference;handling=optional 1393 1394 1399 1400 1401 1405 1406 1407 1408 1410 1412 1414 --boundary1-- 1416 Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call 1418 13. Security Considerations 1420 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1421 the security considerations described there and in [RFC5069] apply 1422 here. Implementors are cautioned to read and understand the 1423 discussion in those documents. 1425 As with emergency service systems where location data is supplied or 1426 determined with the assistance of an end host, there is the 1427 possibility that that location is incorrect, either intentially 1428 (e.g., in a denial of service attack against the emergency services 1429 infrastructure) or due to a malfunctioning device. The reader is 1430 referred to [RFC7378] for a discussion of some of these 1431 vulnerabilities. 1433 In addition to the security considerations discussion specific to the 1434 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1435 MAY decline to carry out any requested action (e.g., if the vehicle 1436 requires but is unable to verify the certificate used to sign the 1437 request). The vehicle MAY use any value in the reason registry to 1438 indicate why it did not take an action (e.g., the generic "unable" or 1439 the more specific "security-failure"). 1441 14. Privacy Considerations 1443 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1444 builds on [RFC7852], the data structures specified there, and the 1445 corresponding privacy considerations discussed there, apply here as 1446 well. The VEDS data structure contains optional elements that can 1447 carry identifying and personal information, both about the vehicle 1448 and about the owner, as well as location information, and so needs to 1449 be protected against unauthorized disclosure, as discussed in 1450 [RFC7852]. Local regulations may impose additional privacy 1451 protection requirements. 1453 The additional functionality enabled by this document, such as access 1454 to vehicle camera streams, carries a burden of protection and so 1455 implementations need to be careful that access is only provided 1456 within the context of an emergency call or to an emergency services 1457 provider (e.g., by verifying that the request for camera access is 1458 signed by a certificate issued by an emergency services registrar). 1460 15. IANA Considerations 1462 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1463 content type, and adds "VEDS" to the Emergency Call Additional Data 1464 registry. This document adds to and creates sub-registries in the 1465 'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall]. 1466 This document registers a new INFO package. 1468 15.1. MIME Content-type Registration for 'application/ 1469 EmergencyCall.VEDS+xml' 1471 This specification requests the registration of a new MIME content 1472 type according to the procedures of RFC 4288 [RFC4288] and guidelines 1473 in RFC 3023 [RFC3023]. 1475 MIME media type name: application 1477 MIME subtype name: EmergencyCallData.VEDS+xml 1479 Mandatory parameters: none 1481 Optional parameters: charset 1483 Indicates the character encoding of enclosed XML. 1485 Encoding considerations: Uses XML, which can employ 8-bit 1486 characters, depending on the character encoding used. See 1487 Section 3.2 of RFC 3023 [RFC3023]. 1489 Security considerations: 1491 This content type is designed to carry vehicle crash data 1492 during an emergency call. 1494 This data can contain personal information including vehicle 1495 VIN, location, direction, etc. Appropriate precautions need to 1496 be taken to limit unauthorized access, inappropriate disclosure 1497 to third parties, and eavesdropping of this information. 1498 Please refer to Section 7 and Section 8 of [RFC7852] for more 1499 information. 1501 When this content type is contained in a signed or encrypted 1502 body part, the enclosing multipart (e.g., multipart/signed or 1503 multipart/encrypted) has the same Content-ID as the data part. 1504 This allows an entity to identify and access the data blocks it 1505 is interested in without having to dive deeply into the message 1506 structure or decrypt parts it is not interested in. (The 1507 'purpose' parameter in a Call-Info header field identifies the 1508 data, and the CID URL points to the data block in the body, 1509 which has a matching Content-ID body part header field). 1511 Interoperability considerations: None 1513 Published specification: [VEDS] 1515 Applications which use this media type: Emergency Services 1517 Additional information: None 1519 Magic Number: None 1521 File Extension: .xml 1523 Macintosh file type code: 'TEXT' 1525 Persons and email addresses for further information: Randall 1526 Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, 1527 Hannes.Tschofenig@gmx.net 1529 Intended usage: LIMITED USE 1531 Author: This specification is a work item of the IETF ECRIT 1532 working group, with mailing list address . 1534 Change controller: The IESG 1536 15.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1537 Data registry 1539 This specification requests IANA to add the 'VEDS' entry to the 1540 Emergency Call Additional Data registry, with a reference to this 1541 document. The Emergency Call Additional Data registry was 1542 established by [RFC7852]. 1544 15.3. New Action Values 1546 This document adds new values for the 'action' attribute of the 1547 element in the "Action Registry" registry created by 1548 [I-D.ietf-ecrit-ecall]. 1550 +---------------+-------------------------------------+ 1551 | Name | Description | 1552 +---------------+-------------------------------------+ 1553 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1554 | | | 1555 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1556 | | | 1557 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1558 | | | 1559 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1560 | | | 1561 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1562 +---------------+-------------------------------------+ 1564 Table 2: Action Registry New Values 1566 15.4. Static Message Registry 1568 This document creates a new sub-registry called "Static Message 1569 Registry" in the "Metadata/Control Data" registry established by 1570 [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected 1571 to support all static messages translated into all languages 1572 supported by the vehicle, it is important to limit the number of such 1573 messages. As defined in [RFC5226], this registry operates under 1574 "Publication Required" rules, which require a stable, public document 1575 and implies expert review of the publication. The expert should 1576 determine that the document has been published by an appropriate 1577 emergency services organization (e.g., NENA, EENA, APCO) or by the 1578 IETF with input from an emergency services organization, and that the 1579 proposed message is sufficiently distinguishable from other messages. 1581 The contents of this registry are: 1583 ID: An integer identifier to be used in the 'msgid' attribute of a 1584 metadata/control element. 1586 Message: The text of the message. Messages are listed in the 1587 registry in English; vehicles are expected to implement 1588 translations into languages supported by the vehicle. 1590 When new messages are added to the registry, the message text is 1591 determined by the registrant; IANA assigns the IDs. Each message is 1592 assigned a consecutive integer value as its ID. This allows an IVS 1593 to indicate by a single integer value that it supports all messages 1594 with that value or lower. 1596 The initial set of values is listed in Table 3. 1598 +----+--------------------------------------------------------------+ 1599 | ID | Message | 1600 +----+--------------------------------------------------------------+ 1601 | 1 | Emergency authorities are aware of your incident and | 1602 | | location, but are unable to speak with you right now. We | 1603 | | will help you as soon as possible. | 1604 +----+--------------------------------------------------------------+ 1606 Table 3: Static Message Registry 1608 15.5. Lamp ID Registry 1610 This document creates a new sub-registry called "Lamp ID Registry" in 1611 the "Metadata/Control Data" registry established by 1612 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1613 the names of automotive lamps (lights). As defined in [RFC5226], 1614 this registry operates under "Expert Review" rules. The expert 1615 should determine that the proposed lamp name is clearly 1616 understandable and is sufficiently distinguishable from other lamp 1617 names. 1619 The contents of this registry are: 1621 Name: The identifier to be used in the 'lamp-ID' attribute of a 1622 metadata/control element. 1624 Description: A description of the lamp (light). 1626 The initial set of values is listed in Table 4. 1628 +----------------+---------------------------------------------+ 1629 | Name | Description | 1630 +----------------+---------------------------------------------+ 1631 | head | The main lamps used to light the road ahead | 1632 | | | 1633 | interior | Interior lamp, often at the top center | 1634 | | | 1635 | fog-front | Front fog lamps | 1636 | | | 1637 | fog-rear | Rear fog lamps | 1638 | | | 1639 | brake | Brake indicator lamps | 1640 | | | 1641 | brake-center | Center High Mounted Stop Lamp | 1642 | | | 1643 | position-front | Front position/parking/standing lamps | 1644 | | | 1645 | position-rear | Rear position/parking/standing lamps | 1646 | | | 1647 | turn-left | Left turn/directional lamps | 1648 | | | 1649 | turn-right | Right turn/directional lamps | 1650 | | | 1651 | hazard | Hazard/four-way lamps | 1652 +----------------+---------------------------------------------+ 1654 Table 4: Lamp ID Registry Initial Values 1656 15.6. Camera ID Registry 1658 This document creates a new sub-registry called "Camera ID Registry" 1659 in the "Metadata/Control Data" registry established by 1660 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1661 automotive cameras. As defined in [RFC5226], this registry operates 1662 under "Expert Review" rules. The expert should determine that the 1663 proposed camera name is clearly understandable and is sufficiently 1664 distinguishable from other camera names. 1666 The contents of this registry are: 1668 Name: The identifier to be used in the 'camera-ID' attribute of a 1669 control element. 1671 Description: A description of the camera. 1673 The initial set of values is listed in Table 5. 1675 +-------------+-----------------------------------------------------+ 1676 | Name | Description | 1677 +-------------+-----------------------------------------------------+ 1678 | backup | Shows what is behind the vehicle, e.g., often used | 1679 | | for driver display when the vehicle is in reverse. | 1680 | | Also known as rearview, reverse, rear visibility, | 1681 | | etc. | 1682 | | | 1683 | left-rear | Shows view to the left and behind (e.g., left side | 1684 | | rear-view mirror or blind spot view) | 1685 | | | 1686 | right-rear | Shows view to the right and behind (e.g., right | 1687 | | side rear-view mirror or blind spot view) | 1688 | | | 1689 | forward | Shows what is in front of the vehicle | 1690 | | | 1691 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1692 | | collision detection systems), separate from backup | 1693 | | view | 1694 | | | 1695 | lane | Used by systems to identify road lane and/or | 1696 | | monitor vehicle's position within lane | 1697 | | | 1698 | interior | Shows the interior (e.g., driver) | 1699 | | | 1700 | night-front | Night-vision view of what is in front of the | 1701 | | vehicle | 1702 +-------------+-----------------------------------------------------+ 1704 Table 5: Camera ID Registry Initial Values 1706 16. Acknowledgements 1708 We would like to thank Lena Chaponniere, Stephen Edge, and Christer 1709 Holmberg for their review and suggestions; Robert Sparks and Paul 1710 Kyzivat for their help with the SIP mechanisms; Michael Montag, 1711 Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex 1712 Buddenberg for their feedback; and Ulrich Dietz for his help with 1713 earlier versions of the original version of this document. 1715 17. Changes from Previous Versions 1717 17.1. Changes from draft-ietf-10 to draft-ietf-11 1719 o Clarifications suggested by Christer 1720 o Corrections to Content-Disposition text and examples as suggested 1721 by Paul Kyzivat 1723 o Clarifications to Content-Disposition text and examples to clarify 1724 that handling=optional is only used in the initial INVITE 1726 17.2. Changes from draft-ietf-09 to draft-ietf-10 1728 o Fixed errors in examples found by Dale in eCall draft 1729 o Removed enclosing sub-section of INFO package registration section 1730 o Added text per Christer and Dale's suggestions that the MSD and 1731 metadata/control blocks are sent in INFO with a Call-Info header 1732 field referencing them 1733 o Other text changes per comments received from Christer and Ivo 1734 against eCall draft. 1736 17.3. Changes from draft-ietf-08 to draft-ietf-09 1738 o Added INFO package registration for eCall.VEDS 1739 o Moved element and other extension points back to 1740 eCall document so that extension points are in base spec (and also 1741 to get XML schema to compile) 1742 o Text changes for clarification. 1744 17.4. Changes from draft-ietf-07 to draft-ietf-08 1746 o Moved much of the metadata/control object from 1747 [I-D.ietf-ecrit-ecall] to this document as extensions 1748 o Editorial clarifications and simplifications 1749 o Moved "Call Routing" to be a subsection of "Call Setup" 1750 o Deleted "Profile" section and moved some of its text into 1751 "Introduction" 1753 17.5. Changes from draft-ietf-06 to draft-ietf-07 1755 o Minor editorial changes 1757 17.6. Changes from draft-ietf-05 to draft-ietf-06 1759 o Added clarifying text regarding signed and encrypted data 1760 o Additional informative text in "Migration to Next-Generation" 1761 section 1762 o Additional clarifying text regarding security and privacy. 1764 17.7. Changes from draft-ietf-04 to draft-ietf-05 1766 o Reworded security text in main document and in MIME registration 1767 for the VEDS object 1769 17.8. Changes from draft-ietf-03 to draft-ietf-04 1771 o Added example VEDS object 1772 o Additional clarifications and corrections 1773 o Removed references from Abstract 1774 o Moved Document Scope section to follow Introduction 1776 17.9. Changes from draft-ietf-02 to draft-ietf-03 1778 o Additional clarifications and corrections 1780 17.10. Changes from draft-ietf-01 to draft-ietf-02 1782 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1783 aspects including the service URN; this document no longer 1784 proposes a unique service URN for non-eCall NG-ACN calls; the same 1785 service URN is now used for all NG-ACN calls including NG-eCall 1786 and non-eCall 1787 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1788 support it 1789 o Minor wording improvements and clarifications 1791 17.11. Changes from draft-ietf-00 to draft-ietf-01 1793 o Added further discussion of test calls 1794 o Added further clarification to the document scope 1795 o Mentioned that multi-region vehicles may need to support other 1796 crash notification specifications such as eCall 1797 o Minor wording improvements and clarifications 1799 17.12. Changes from draft-gellens-02 to draft-ietf-00 1801 o Renamed from draft-gellens- to draft-ietf- 1802 o Added text to Introduction to clarify that during a CS ACN, the 1803 PSAP call taker usually needs to listen to the data and transcribe 1804 it 1806 17.13. Changes from draft-gellens-01 to -02 1808 o Fixed case of 'EmergencyCallData', in accordance with changes to 1809 [RFC7852] 1811 17.14. Changes from draft-gellens-00 to -01 1813 o Now using 'EmergencyCallData' for purpose parameter values and 1814 MIME subtypes, in accordance with changes to [RFC7852] 1815 o Added reference to RFC 6443 1816 o Fixed bug that caused Figure captions to not appear 1818 18. References 1820 18.1. Normative References 1822 [I-D.ietf-ecrit-ecall] 1823 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1824 European eCall", draft-ietf-ecrit-ecall-11 (work in 1825 progress), August 2016. 1827 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1828 Requirement Levels", BCP 14, RFC 2119, 1829 DOI 10.17487/RFC2119, March 1997, 1830 . 1832 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1833 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1834 . 1836 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1837 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1838 . 1840 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1841 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1842 December 2005, . 1844 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1845 Emergency and Other Well-Known Services", RFC 5031, 1846 DOI 10.17487/RFC5031, January 2008, 1847 . 1849 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1850 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1851 DOI 10.17487/RFC5226, May 2008, 1852 . 1854 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1855 Presence Information Data Format Location Object (PIDF-LO) 1856 Usage Clarification, Considerations, and Recommendations", 1857 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1858 . 1860 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1861 Thomson, "Dynamic Extensions to the Presence Information 1862 Data Format Location Object (PIDF-LO)", RFC 5962, 1863 DOI 10.17487/RFC5962, September 2010, 1864 . 1866 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1867 "Framework for Emergency Calling Using Internet 1868 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1869 2011, . 1871 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1872 Communications Services in Support of Emergency Calling", 1873 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1874 . 1876 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1877 J. Winterbottom, "Additional Data Related to an Emergency 1878 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1879 . 1881 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1882 NENA Data Standardization Workgroup, , "Vehicular 1883 Emergency Data Set (VEDS) version 3", July 2012, 1884 . 1887 18.2. Informative references 1889 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1890 Emergency Context Resolution with Internet Technologies", 1891 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1892 . 1894 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1895 Shanmugam, "Security Threats and Requirements for 1896 Emergency Call Marking and Mapping", RFC 5069, 1897 DOI 10.17487/RFC5069, January 2008, 1898 . 1900 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1901 Initiation Protocol (SIP) INFO Method and Package 1902 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1903 . 1905 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1906 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1907 December 2014, . 1909 [triage-2008] 1910 National Center for Injury Prevention and Control, and 1911 Centers for Disease Control and Prevention, 1912 "Recommendations from the Expert Panel: Advanced Automatic 1913 Collision Notification and Triage of the Injured Patient", 1914 2008, . 1916 [triage-2011] 1917 National Center for Injury Prevention and Control, and 1918 Centers for Disease Control and Prevention, "Guidelines 1919 for field triage of injured patients: recommendations of 1920 the National Expert Panel on Field Triage", January 2012, 1921 . 1926 Authors' Addresses 1928 Randall Gellens 1929 Core Technology Consulting 1931 Email: rg+ietf@randy.pensive.org 1933 Brian Rosen 1934 NeuStar, Inc. 1935 470 Conrad Dr 1936 Mars, PA 16046 1937 US 1939 Email: br@brianrosen.net 1941 Hannes Tschofenig 1942 Individual 1944 Email: Hannes.Tschofenig@gmx.net 1945 URI: http://www.tschofenig.priv.at