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