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