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