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