idnits 2.17.1 draft-ietf-ecrit-car-crash-14.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 863 has weird spacing: '...-static displ...' == Line 870 has weird spacing: '...dynamic displ...' == Line 873 has weird spacing: '... honk sound...' == Line 875 has weird spacing: '... lamp turns...' == Line 877 has weird spacing: '...-camera adds ...' -- The document date (October 9, 2016) is 2756 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 1834, but no explicit reference was found in the text == Unused Reference: 'RFC5031' is defined on line 1842, but no explicit reference was found in the text == Unused Reference: 'RFC5491' is defined on line 1852, but no explicit reference was found in the text == Unused Reference: 'RFC5962' is defined on line 1858, 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 12, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 October 9, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-14.txt 13 Abstract 15 This document describes how to use IP-based emergency services 16 mechanisms to support the next generation of emergency calls placed 17 by vehicles (automatically in the event of a crash or serious 18 incident, or manually invoked by a vehicle occupant) and conveying 19 vehicle, sensor, and location data related to the crash or incident. 20 Such calls are often referred to as "Automatic Crash Notification" 21 (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the 22 case of manual trigger. The "Advanced" qualifier refers to the 23 ability to carry a richer set of data. 25 This document also registers a MIME Content Type and Emergency Call 26 Additional Data Block for the vehicle, sensor, and location data 27 (often referred to as "crash data" even though there is not 28 necessarily a crash). An external specification for the data format, 29 contents, and structure are referenced in this document. 31 This document reuses the technical aspects of next-generation pan- 32 European eCall (a mandated and standardized system for emergency 33 calls by in-vehicle systems within Europe and other regions). 34 However, this document specifies a different set of vehicle (crash) 35 data, specifically, the Vehicle Emergency Data Set (VEDS) rather than 36 the eCall Minimum Set of Data (MSD). This document is an extension 37 of the eCall document, with the primary differences being that this 38 document makes the MSD data set optional and VEDS mandatory, and adds 39 attribute values to the eCall metadata/control object to permit 40 greater functionality. This document registers a new INFO package 41 (identical to that registered for eCall but with the addition of the 42 VEDS MIME type). This document also describes legacy (circuit- 43 switched) ACN systems and their migration to next-generation 44 emergency calling, to provide background information and context. 46 Status of This Memo 48 This Internet-Draft is submitted in full conformance with the 49 provisions of BCP 78 and BCP 79. 51 Internet-Drafts are working documents of the Internet Engineering 52 Task Force (IETF). Note that other groups may also distribute 53 working documents as Internet-Drafts. The list of current Internet- 54 Drafts is at http://datatracker.ietf.org/drafts/current/. 56 Internet-Drafts are draft documents valid for a maximum of six months 57 and may be updated, replaced, or obsoleted by other documents at any 58 time. It is inappropriate to use Internet-Drafts as reference 59 material or to cite them other than as "work in progress." 61 This Internet-Draft will expire on April 12, 2017. 63 Copyright Notice 65 Copyright (c) 2016 IETF Trust and the persons identified as the 66 document authors. All rights reserved. 68 This document is subject to BCP 78 and the IETF Trust's Legal 69 Provisions Relating to IETF Documents 70 (http://trustee.ietf.org/license-info) in effect on the date of 71 publication of this document. Please review these documents 72 carefully, as they describe your rights and restrictions with respect 73 to this document. Code Components extracted from this document must 74 include Simplified BSD License text as described in Section 4.e of 75 the Trust Legal Provisions and are provided without warranty as 76 described in the Simplified BSD License. 78 Table of Contents 80 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 81 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 82 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 83 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 9 84 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 85 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 86 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 87 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 17 88 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 17 89 9.1. New values for the 'action' attribute' . . . . . . . . . 19 90 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 19 91 9.3. The element . . . . . . . . . . . . . . . . . . . . 20 92 9.4. The element . . . . . . . . . . . . . . . 21 93 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 22 94 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 23 95 11.1. Overall Description . . . . . . . . . . . . . . . . . . 23 96 11.2. Applicability . . . . . . . . . . . . . . . . . . . . . 24 97 11.3. Info Package Name . . . . . . . . . . . . . . . . . . . 24 98 11.4. Info Package Parameters . . . . . . . . . . . . . . . . 24 99 11.5. SIP Option-Tags . . . . . . . . . . . . . . . . . . . . 24 100 11.6. INFO Request Body Parts . . . . . . . . . . . . . . . . 24 101 11.7. Info Package Usage Restrictions . . . . . . . . . . . . 25 102 11.8. Rate of INFO Requests . . . . . . . . . . . . . . . . . 25 103 11.9. Info Package Security Considerations . . . . . . . . . . 25 104 11.10. Implementation Details . . . . . . . . . . . . . . . . . 25 105 11.11. Examples . . . . . . . . . . . . . . . . . . . . . . . . 25 106 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 107 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 108 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 31 109 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 32 110 15.1. MIME Content-type Registration for 111 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 32 112 15.2. Registration of the 'VEDS' entry in the Emergency Call 113 Additional Data registry . . . . . . . . . . . . . . . . 33 114 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 33 115 15.4. Static Message Registry . . . . . . . . . . . . . . . . 34 116 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 35 117 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 36 118 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 119 17. Changes from Previous Versions . . . . . . . . . . . . . . . 37 120 17.1. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 37 121 17.2. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38 122 17.3. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38 123 17.4. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 124 17.5. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 125 17.6. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 126 17.7. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 127 17.8. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 128 17.9. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39 129 17.10. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 130 17.11. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 131 17.12. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 132 17.13. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 133 17.14. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39 134 17.15. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40 135 17.16. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40 136 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 137 18.1. Normative References . . . . . . . . . . . . . . . . . . 40 138 18.2. Informative references . . . . . . . . . . . . . . . . . 41 139 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 141 1. Terminology 143 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 144 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 145 document are to be interpreted as described in [RFC2119]. 147 This document re-uses terminology defined in Section 3 of [RFC5012]. 149 Additionally, we use the following abbreviations: 151 +--------+----------------------------------------------------------+ 152 | Term | Expansion | 153 +--------+----------------------------------------------------------+ 154 | 3GPP | 3rd Generation Partnership Project | 155 | AACN | Advanced Automatic Crash Notification | 156 | ACN | Automatic Crash Notification | 157 | APCO | Association of Public-Safety Communications Officials | 158 | EENA | European Emergency Number Association | 159 | ESInet | Emergency Services IP network | 160 | GNSS | Global Navigation Satellite System (which includes | 161 | | various systems such as the Global Positioning System or | 162 | | GPS) | 163 | IVS | In-Vehicle System | 164 | MNO | Mobile Network Operator | 165 | MSD | eCall Minimum Set of Data | 166 | NENA | National Emergency Number Association | 167 | POTS | Plain Old Telephone Service (normal, circuit-switched | 168 | | voice calls) | 169 | PSAP | Public Safety Answering Point | 170 | TSP | Telematics Service Provider | 171 | VEDS | Vehicle Emergency Data Set | 172 +--------+----------------------------------------------------------+ 174 Because the endpoints of an NG-ACN call are a PSAP and an IVS or TSP, 175 to avoid receptively writing "IVS or TSP", the term "IVS" is used to 176 represent either an IVS or TSP when discussing signaling behavior 177 (e.g., attaching VEDS data, sending an INVITE request, receiving an 178 INFO request, etc.). 180 2. Introduction 182 Emergency calls made by in-vehicle systems (e.g., automatically in 183 the event of a crash or serious incident or manually by a vehicle 184 occupant) assist in significantly reducing road deaths and injuries 185 by allowing emergency services to respond quickly and appropriately 186 to the specifics of the incident, often with better location 187 accuracy. 189 Drivers often have a poor location awareness, especially outside of 190 major cities, at night and when away from home (especially abroad). 191 In the most crucial cases, the victim(s) might not be able to call 192 because they have been injured or trapped. 194 For more than two decades, some vehicles have been equipped with 195 telematics systems which, among other features, place an emergency 196 call automatically in the event of a crash or manually in response to 197 an emergency call button. Such systems generally have on-board 198 location determination systems that make use of satellite-based 199 positioning technology, inertial sensors, gyroscopes, etc., which can 200 provide an accurate position for the vehicle. Such built-in systems 201 can take advantage of the benefits of being integrated into a 202 vehicle, such as more power capacity, ability to have larger or 203 specialized antenna, ability to be engineered to avoid or minimise 204 degradation by vehicle glass coatings, interference from other 205 vehicle systems, etc. Thus, the PSAP can be provided with a good 206 estimate of where the vehicle is during an emergency. Vehicle 207 manufacturers are increasingly adopting such systems, both for the 208 safety benefits and for the additional features and services they 209 enable (e.g., remote engine diagnostics, remote door unlock, stolen 210 vehicle tracking and disabling, etc.). 212 The general term for such systems is Automatic Crash Notification 213 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 214 used in this document as a general term. ACN systems transmit some 215 amount of data specific to the incident, referred to generally as 216 "crash data" (the term is commonly used even though there might not 217 have been a crash). While different systems transmit different 218 amounts of crash data, standardized formats, structures, and 219 mechanisms are needed to provide interoperability among systems and 220 PSAPs. 222 As of the date of this document, currently deployed in-vehicle 223 telematics systems are circuit-switched and lack a standards-based 224 ability to convey crash data directly to the PSAP (generally relying 225 on either a human advisor or an automated text-to-speech system to 226 provide the PSAP call taker with some crash data orally, or in some 227 cases via a proprietary mechanism). In most cases, the PSAP call 228 taker needs to first realize that the call is related to a vehicle 229 incident, and then listen to the data and transcribe it. Circuit- 230 switched ACN systems are referred to here as CS-ACN. 232 The transition to next-generation calling in general, and for 233 emergency calling in particular, provides an opportunity to vastly 234 improve the scope, breadth, reliability and usefulness of crash data 235 during an emergency by allowing it to be transmitted during call set- 236 up, and to be automatically processed by the PSAP and made available 237 to the call taker in an integrated, automated way, as well as provide 238 the ability for a PSAP call taker to request that a vehicle take 239 certain actions, such as flashing lights or unlocking doors. In 240 addition, vehicle manufacturers are provided an opportunity to take 241 advantage of the same standardized mechanisms for data transmission 242 and request processing for internal use if they wish (such as 243 telemetry between the vehicle and a service center for both emergency 244 and non-emergency uses, including location-based services, multi- 245 media entertainment systems, remote door unlocking, and road-side 246 assistance applications). 248 Next-generation ACN provides an opportunity for such calls to be 249 recognized and processed as such during call set-up, and routed to an 250 equipped PSAP where the vehicle data is available to assist the call 251 taker in assessing and responding to the situation. Next-generation 252 (IP-based) ACN systems are referred to here as NG-ACN. 254 An ACN call can be initiated by a vehicle occupant or automatically 255 initiated by vehicle systems in the event of a serious incident. 256 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 257 used to refer to the class of calls that are placed by an in-vehicle 258 system (IVS) or Telematics Service Providers (TSP) and that carry 259 incident-related data as well as voice.) Automatically triggered 260 calls indicate a car crash or some other serious incident (e.g., a 261 fire). Manually triggered calls are often reports of observed 262 crashes or serious hazards (such as impaired drivers or roadway 263 debris). In some implementations, manually triggered calls might be 264 more likely to be accidental. 266 This document describes how the IETF mechanisms for IP-based 267 emergency calls, including [RFC6443] and [RFC7852], are used to 268 provide the realization of next-generation ACN. 270 This document reuses the technical aspects of next-generation pan- 271 European eCall (a mandated and standardized system for emergency 272 calls by in-vehicle systems within Europe and other regions), as 273 described in [I-D.ietf-ecrit-ecall]. However, this document 274 specifies a different set of vehicle (crash) data, specifically, the 275 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 276 of Data (MSD). This document is an extension of 277 [I-D.ietf-ecrit-ecall], with the differences being that this document 278 makes the MSD data set optional and VEDS mandatory, and adds new 279 attribute values to the eCall metadata/control object defined in that 280 document. This document also registers a new INFO package (identical 281 to that defined in [I-D.ietf-ecrit-ecall] with the addition of the 282 VEDS MIME type). 284 The Association of Public-Safety Communications Officials (APCO) and 285 the National Emergency Number Association (NENA) have jointly 286 developed a standardized set of incident-related vehicle data for ACN 287 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 288 is often referred to as crash data although it is applicable in 289 incidents other than crashes. 291 VEDS provides a standard data set for the transmission, exchange, and 292 interpretation of vehicle-related data. A standard data format 293 allows the data to be generated by an IVS or TSP and interpreted by 294 PSAPs, emergency responders, and medical facilities. It includes 295 incident-related information such as airbag deployment, location and 296 compass orientation of the vehicle, spatial orientation of the 297 vehicle (e.g., upright, on its side or top or a bumper), various 298 sensor data that can indicate the potential severity of the crash and 299 the likelihood of severe injuries to the vehicle occupants, etc. 300 This data better informs the PSAP and emergency responders as to the 301 type of response that might be needed. Some of this information has 302 been included in U.S. government guidelines for field triage of 303 injured patients [triage-2008] [triage-2011]. These guidelines are 304 designed to help responders identify the potential existence of 305 severe internal injuries and to make critical decisions about how and 306 where a patient needs to be transported. 308 This document registers the 'application/EmergencyCallData.VEDS+xml' 309 MIME content-type, and registers the 'VEDS' entry in the Emergency 310 Call Additional Data registry. 312 VEDS is an XML structure (see [VEDS]) transported in SIP using the 313 'application/EmergencyCallData.VEDS+xml' MIME content-type.. 315 VEDS is a versatile structure that can accomodate varied needs. 316 However, if additional sets of data are determined to be needed 317 (e.g., in the future or in different regions), the steps to enable 318 each data block are very briefly summarized below: 320 o A standardized format and encoding (such as XML) is defined and 321 published by a Standards Development Organization (SDO) 323 o A MIME Content-Type is registered for it (typically under the 324 'Application' media type) with a sub-type starting with 325 'EmergencyCallData.' 327 o An entry for the block is added to the Emergency Call Additional 328 Data Blocks sub-registry (established by [RFC7852]); the registry 329 entry is the root of the MIME sub-type (not including the 330 'EmergencyCallData' prefix and any suffix such as '+xml') 332 o A new INFO package is registered that permits carrying the new 333 content type and the metadata/control object (defined in 334 [I-D.ietf-ecrit-ecall]) in INFO requests. 336 Section 6 describes how VEDS data and metadata/control are 337 transported within NG-ACN calls. Section 7 describes how such calls 338 are placed. 340 These mechanisms are thus used to place emergency calls that are 341 identifiable as ACN calls and that carry standardized crash data in 342 an interoperable way. 344 Calls by in-vehicle systems are placed using cellular networks, which 345 might ignore location information sent by an originating device in an 346 emergency call INVITE, instead attaching their own location 347 information (often determined in cooperation with the originating 348 device). Standardized crash data structures often include location 349 as determined by the IVS. A benefit of this is that it allows the 350 PSAP to see both the location as determined by the cellular network 351 (often in cooperation with the originating device) and the location 352 as determined by the IVS. 354 This specification inherits the ability to utilize test call 355 functionality from Section 15 of [RFC6881]. 357 3. Document Scope 359 This document is focused on how an ACN emergency call is setup and 360 incident-related data (including vehicle, sensor, and location data) 361 is transmitted to the PSAP using IETF specifications. For the direct 362 model, this is the end-to-end description (between the vehicle and 363 the PSAP). For the TSP model, this describes the call leg between 364 the TSP and the PSAP, leaving the call leg between the vehicle and 365 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 366 are then free to use the same mechanism as for the right-hand side or 367 not. 369 Note that Europe has a mandated and standardized system for emergency 370 calls by in-vehicle systems. This pan-European system is known as 371 "eCall" and is the subject of a separate document, 372 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 373 designed to operate in multiple regions might need to support eCall 374 as well as NG-ACN as described here. A vehicle IVS might determine 375 whether to use eCall or ACN by first determining the region or 376 country in which it is located (e.g., from a GNSS location fix and/or 377 identity of or information from an MNO). If other regions adopt 378 other data formats, a multi-region vehicle might need to support 379 those as well. This document adopts the call set-up and other 380 technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852]; 381 this makes it straightforward to use a different data set while 382 keeping other technical aspects unchanged. Hence, both NG-eCall and 383 the NG-ACN mechanism described here are compatible, differing 384 primarily in the specific data block that is sent (the eCall MSD in 385 the case of NG-eCall, and the APCO/NENA VEDS used in this document), 386 and some additions to the metadata/control data block. If other 387 regions adopt their own vehicle data sets, this can be similarly 388 accomodated without changing other technical aspects. Note that any 389 additional data blocks require a new INFO package to permit transport 390 within INFO requests. 392 4. Overview of Legacy Deployment Models 394 Legacy (circuit-switched) systems for placing emergency calls by in- 395 vehicle systems generally have some ability to convey at least 396 location and in some cases telematics data to the PSAP. Most such 397 systems use one of three architectural models, which are described 398 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 399 These three models are illustrated below. 401 In the TSP model, both emergency and non-emergency calls are placed 402 to a Telematics Service Provider (TSP); a proprietary technique is 403 used for data transfer (such as a proprietary in-band modem) between 404 the TSP and the vehicle. 406 In an emergency, generally the TSP call taker bridges in the PSAP and 407 communicates location, crash data (such as impact severity and trauma 408 prediction), and other data (such as the vehicle description) to the 409 PSAP call taker verbally (in some cases, a proprietary out-of-band 410 interface is used). Since the TSP knows the location of the vehicle 411 (from on-board GNSS and sensors), location-based routing is usually 412 used to route to the appropriate PSAP. In some cases, the TSP is 413 able to transmit location automatically, using similar techniques as 414 for wireless calls. Typically, a three-way voice call is established 415 between the vehicle, the TSP, and the PSAP, allowing communication 416 between the PSAP call taker, the TSP call taker, and the vehicle 417 occupants (who might be unconscious). 419 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 420 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 421 \\\----/// crash data +------+ location via trunk +------+ 423 Figure 1: Legacy TSP Model. 425 In the paired model, the IVS uses a Bluetooth link with a previously- 426 paired handset to establish an emergency call with the PSAP (by 427 dialing a standard emergency number; 9-1-1 in North America), and 428 then communicates location data to the PSAP via text-to-speech; crash 429 data might or might not be conveyed also using text-to-speech. Some 430 such systems use an automated voice prompt menu for the PSAP call 431 taker (e.g., "this is an automatic emergency call from a vehicle; 432 press 1 to open a voice path to the vehicle; press 2 to hear the 433 location read out") to allow the call taker to request location data 434 via text-to-speech. 436 +---+ 437 ///----\\\ | H | 911/etc voice call via handset +------+ 438 ||| IVS |||-->| S +----------------------------------->+ PSAP | 439 \\\----/// +---+ location via text-to-speech +------+ 441 Figure 2: Legacy Paired Model 443 In the direct model, the IVS directly places an emergency call with 444 the PSAP by dialing a standard emergency number (9-1-1 in North 445 America). Such systems might communicate location data to the PSAP 446 via text-to-speech; crash data might or might not be conveyed using 447 text-to-speech. Some such systems use an automated voice prompt menu 448 (e.g., "this is an automatic emergency call from a vehicle; press 1 449 to open a voice path to the vehicle; press 2 to hear the location 450 read out") to allow the call taker to request location data via text- 451 to-speech. 453 ///----\\\ 911/etc voice call via IVS +------+ 454 ||| IVS |||---------------------------------------->+ PSAP | 455 \\\----/// location via text-to-speech +------+ 457 Figure 3: Legacy Direct Model 459 5. Migration to Next-Generation 461 Migration of emergency calls placed by in-vehicle systems to next- 462 generation (all-IP) technology per this document provides a 463 standardized mechanism to identify such calls and to present crash 464 data with the call, as well as enabling additional communications 465 modalities and enhanced functionality. This allows ACN calls and 466 crash data to be automatically processed by the PSAP and made 467 available to the call taker in an integrated, automated way. Because 468 the crash data is carried in the initial SIP INVITE (per [RFC7852]) 469 the PSAP can present it to the call taker simultaneously with the 470 appearance of the call. The PSAP can also process the data to take 471 other actions (e.g., if multiple calls from the same location arrive 472 when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP 473 might choose to store the information and reject the calls, since the 474 IVS will receive confirmation that the information has been 475 successfully received; a PSAP could also choose to include a message 476 stating that it is aware of the incident and responders are on the 477 way; a PSAP could call the vehicle back when a call taker is 478 available). 480 Origination devices and networks, PSAPs, emergency services networks, 481 and other telephony environments are migrating to next-generation. 482 This provides opportunities for significant enhancement to 483 interoperability and functionality, especially for emergency calls 484 carrying additional data such as vehicle crash data. (In the U.S., a 485 network specifically for emergency responders is being developed. 486 This network, FirstNet, will be next-generation from the start, 487 enhancing the ability for data exchange between PSAPs and 488 responders.) 490 Migration to next-generation (NG) provides an opportunity to 491 significantly improve the handling and response to vehicle-initiated 492 emergency calls. Such calls can be recognized as originating from a 493 vehicle, routed to a PSAP equipped both technically and operationally 494 to handle such calls, and the vehicle-determined location and crash 495 data can be made available to the call taker simultaneously with the 496 call appearance. The PSAP can take advantage of enhanced 497 functionality, including the ability to request the vehicle to take 498 an action, such as sending an updated set of data, converying a 499 message to the occupants, flashing lights, unlocking doors, etc. 501 Vehicle manufacturers using the TSP model can choose to take 502 advantage of the same mechanism to carry telematics data and requests 503 and responses between the vehicle and the TSP for both emergency and 504 non-emergency calls as are used for the interface with the PSAP. 506 A next-generation IVS establishes an emergency call using the 507 emergency call solution as described in [RFC6443] and [RFC6881], with 508 the difference that the Request-URI indicates an ACN type of 509 emergency call, the IVS typically does not perform routing or 510 location queries but relies on the carrier for this, and uses Call- 511 Info header fields to indicates that vehicle crash and capabilities 512 data is attached. When an ESInet is deployed, the MNO only needs to 513 recognize the call as an emergency call and route it to an ESInet. 514 The ESInet can recognize the call as an ACN with vehicle data and can 515 route the call to an NG-ACN capable PSAP. Such a PSAP can interpret 516 the vehicle data sent with the call and make it available to the call 517 taker. 519 [I-D.ietf-ecrit-ecall] registers new service URN children within the 520 "sos" subservice. These URNs request NG-ACN resources, and 521 differentiate between manually and automatically triggered NG-ACN 522 calls (which might be subject to different treatment depending on 523 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 524 are "urn:service:sos.ecall.automatic" and 525 "urn:service:sos.ecall.manual". The same service URNs are used for 526 ACN as for eCall since in any region only one of these is supported, 527 making a distinction unnecessary. (Further, PSAP equipment might 528 support multiple data formats, allowing a PSAP to handle a vehicle 529 that erroneously sent the wrong data object.) 531 Note that in North America, routing queries performed by clients 532 outside of an ESInet typically treat all sub-services of "sos" 533 identically to "sos" with no sub-service. However, the Request-URI 534 header field retains the full sub-service; route and handling 535 decisions within an ESInet or PSAP can take the sub-service into 536 account. For example, in a region with multiple cooperating PSAPs, 537 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 538 one that specializes in vehicle-related incidents. 540 Migration of the three architectural models to next-generation (all- 541 IP) is described below. 543 In the TSP model, the IVS transmits crash and location data to the 544 TSP either by re-using the mechanisms and data objects described 545 here, or using a proprietary mechanism. In an emergency, the TSP 546 bridges in the PSAP and the TSP transmits crash and other data to the 547 PSAP using the mechanisms and data objects described here. There is 548 a three-way call between the vehicle, the TSP, and the PSAP, allowing 549 communication between the PSAP call taker, the TSP call taker, and 550 the vehicle occupants (who might be unconscious). The TSP relays 551 PSAP requests and vehicle responses. 553 proprietary 554 ///----\\\ or standard +------+ standard +------+ 555 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 556 \\\----/// crash + other data +------+ crash + other data +------+ 558 Figure 4: Next-Generation TSP Model 560 The vehicle manufacturer and the TSP can choose to use the same 561 mechanisms and data objects on the left call leg in Figure 4 as on 562 the right. (Note that the TSP model can be more difficult when the 563 vehicle is in a different country than the TSP (e.g., a US resident 564 driving in Canada or Mexico) because of the additional complexity in 565 choosing the correct PSAP based on vehicle location performed by a 566 TSP in a different country.) 567 In the direct model, the IVS communicates crash data to the PSAP 568 directly using the mechanisms and data objects described here. 570 ///----\\\ NG emergency call +------+ 571 ||| IVS |||----------------------------------------->+ PSAP | 572 \\\----/// crash + other data +------+ 574 Figure 5: Next-Generation Direct Model 576 In the paired model, the IVS uses a Bluetooth link to a previously- 577 paired handset to establish an emergency call with the PSAP; it is 578 undefined what facilities are or will be available for transmitting 579 crash data through the Bluetooth link to the handset for inclusion in 580 an NG emergency call. Hence, manufacturers that use the paired model 581 for legacy calls might choose to adopt either the direct or TSP 582 models for next-generation calls. 584 +---+ 585 ///----\\\ (undefined) | H | standard +------+ 586 ||| IVS |||------------------>| S +------------------->+ PSAP | 587 \\\----/// (undefined) +---+ crash + other data +------+ 589 Figure 6: Next-Generation Paired Model 591 If the call is routed to a PSAP that is not capable of processing the 592 vehicle data, the PSAP ignores (or does not receive) the vehicle 593 data. This is detectable by the IVS or TSP when the status response 594 to the INVITE (e.., 200 OK) lacks a control structure acknowledging 595 receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or TSP then 596 proceeds as it would for a CS-ACN call (e.g., verbal conveyance of 597 data) 599 6. Data Transport 601 [RFC7852] establishes a general mechanism for attaching blocks of 602 data to a SIP emergency call. This mechanism permits certain 603 emergency call MIME types to be attached to SIP messages. This 604 document makes use of that mechanism. This document also registers 605 an INFO package (in Section 11) to enable NG-ACN related data blocks 606 to be carried in SIP INFO requests (per [RFC6086], new INFO usages 607 require the definition of an INFO package). 609 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 610 by attaching it to a SIP message as a MIME body part per [RFC7852]. 611 The body part is identified by its MIME content-type ('application/ 612 emergencyCallData.VEDS+xml') in the Content-Type header field of the 613 body part. The body part is assigned a unique identifier which is 614 listed in a Content-ID header field in the body part. The SIP 615 message is marked as containing the VEDS data by adding (or appending 616 to) a Call-Info header field at the top level of the SIP message. 617 This Call-Info header field contains a CID URL referencing the body 618 part's unique identifier, and a 'purpose' parameter identifying the 619 data as a VEDS data block per the Emergency Call Additional Data 620 Blocks registry entry; the 'purpose' parameter's value is 621 'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO 622 request by using the INFO package defined in Section 11. 624 A PSAP or IVS transmits a metadata/control object (see 625 [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME 626 body part per [RFC7852]. The body part is identified by its MIME 627 content-type ('application/emergencyCallData.control+xml') in the 628 Content-Type header field of the body part. The body part is 629 assigned a unique identifier which is listed in a Content-ID header 630 field in the body part. The SIP message is marked as containing the 631 metadata/control block by adding (or appending to) a Call-Info header 632 field at the top level of the SIP message. This Call-Info header 633 field contains a CID URL referencing the body part's unique 634 identifier, and a 'purpose' parameter identifying the data as a 635 metadata/control block per the Emergency Call Additional Data Blocks 636 registry entry; the 'purpose' parameter's value is 637 'emergencyCallData.control'. A metadata/control object is carried in 638 a SIP INFO request by using the INFO package defined in Section 11. 640 A body part containing a VEDS or metadata/control object has a 641 Content-Disposition header field value containing "By-Reference" and 642 is always enclosed in a multipart body part. (In some cases, there 643 might be intermediate multipart body parts between the top level 644 multipart/mixed and the body part containing the VEDS or metadata/ 645 control object.) 647 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 648 initial INVITE a VEDS data block and a metadata/control object 649 informing the PSAP of its capabilities. The VEDS and metadata/ 650 control body parts (and PIDF-LO) have a Content-Disposition header 651 field with the value "By-Reference; handling=optional". Specifying 652 handling=optional prevents the INVITE from being rejected if it is 653 processed by a legacy element (e.g., a gateway between SIP and 654 circuit-switched environments) that does not understand the VEDS or 655 metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ 656 control object acknowledging receipt of the VEDS data and includes it 657 in the SIP final response to the INVITE. The metadata/control object 658 is not attached to provisional (e.g., 180) responses. 660 If the IVS receives an acknowledgment for a VEDS data object with 661 received=false, this indicates that the PSAP was unable to properly 662 decode or process the VEDS. The IVS action is not defined (e.g., it 663 might only log an error). Since the PSAP is able to request an 664 updated VEDS during the call, if an initial VEDS is unsatisfactory in 665 any way, the PSAP can choose to request another one. 667 A PSAP can request that the vehicle send an updated VEDS data block 668 during a call. To do so, the PSAP creates a metadata/control object 669 requesting VEDS data and attaches it to a SIP INFO request and sends 670 it within the dialog. The IVS then attaches an updated VEDS data 671 object to a SIP INFO request and sends it within the dialog. If the 672 IVS is unable to send the VEDS, it instead sends a metadata/control 673 object acknowledging the request with the 'success' parameter set to 674 'false' and a 'reason' parameter (and optionally a 'details' 675 parameter) indicating why the request cannot be accomplished. Per 676 [RFC6086], metadata/control objects and VEDS data are sent using the 677 INFO package defined in Section 11. In addition, to align with the 678 way a VEDS or metadata/control block is transmitted in a SIP message 679 other than an INFO request, one or more Call-Info header fields are 680 included in the SIP INFO request to reference the VEDS or metadata/ 681 control block. See Section 11 for more information on the use of 682 INFO requests within NG-ACN calls. 684 Any metadata/control object sent by a PSAP can request that the 685 vehicle perform an action (such as sending a data block, flashing 686 lights, providing a camera feed, etc.) The vehicle sends an 687 acknowledgement for any request other than a successfully executed 688 send-data action. Multiple requests with the same 'action' value 689 MUST be sent in separate body parts (to avoid any ambiguity in the 690 acknowledgement). 692 If the IVS is aware that VEDS data it sent previously has changed, it 693 MAY send an unsolicited VEDS (in any convenient SIP message, 694 including an INFO request) during the call. The PSAP sends an 695 acknowledgment for an unsolicited VEDS object (if the IVS sent the 696 unsolicited VEDS in an INFO request, the acknowledgment is sent in a 697 new INFO request, otherwise it is sent in the response to the message 698 containing the VEDS). 700 7. Call Setup 702 A next-generation In-Vehicle System (IVS) initiates an NG-ACN call 703 with a SIP INVITE using one of the SOS sub-services 704 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, 705 standard sets of crash data and capabilities data encoded in 706 standardized and registered formats, attached as additional data 707 blocks as specified in Section 4.1 of [RFC7852]. As described in 708 that document, each data block is identified by its MIME content- 709 type, and pointed to by a CID URL in a Call-Info header with a 710 'purpose' parameter value corresponding to the data block. 712 If new data blocks are needed (e.g., in other regions or in the 713 future), the steps required during standardization are briefly 714 summarized below: 716 o A set of data is standardized by an SDO or appropriate 717 organization 719 o A MIME Content-Type for the crash data set is registered with IANA 721 * If the data is specifically for use in emergency calling, the 722 MIME type is normally under the 'application' type with a 723 subtype starting with 'EmergencyCallData.' 725 * If the data format is XML, then by convention the name has a 726 suffix of '+xml' 728 o The item is registered in the Emergency Call Additional Data 729 registry, as defined in Section 9.1.7 of [RFC7852] 731 * For emergency-call-specific formats, the registered name is the 732 root of the MIME Content-Type (not including the 733 'EmergencyCallData' prefix and any suffix such as '+xml') as 734 described in Section 4.1 of [RFC7852]. 736 o A new INFO package is registered that permits carrying the the new 737 content type, the metadata/control object (defined in 738 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 739 objects, in INFO messages. 741 When placing an emergency call, the crash data set and IVS capability 742 data are transported as described in Section 6. 744 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 745 the Association of Public-Safety Communications Officials (APCO) and 746 the National Emergency Number Association (NENA) [VEDS]. It is 747 carried in body part with MIME content-type 'application/ 748 EmergencyCallData.VEDS+xml'. 750 Entities along the path between the vehicle and the PSAP are able to 751 identify the call as an ACN call and handle it appropriately. The 752 PSAP is able to identify the crash and capabilities data attached to 753 the INVITE by examining the Call-Info header fields for 'purpose' 754 parameters whose values start with 'EmergencyCallData.' The PSAP is 755 able to access the data it is capable of handling and is interested 756 in by checking the 'purpose' parameter values. 758 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 759 up and other normative requirements with the exception that in this 760 document, support for the eCall MSD is OPTIONAL and support for VEDS 761 in REQUIRED. This document also adds new attribute values to the 762 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 764 8. Call Routing 766 An Emergency Services IP Network (ESInet) is a network operated by or 767 on behalf of emergency services authorities. It handles emergency 768 call routing and processing before delivery to a PSAP. In the 769 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 770 architecture adopted by EENA, each PSAP is connected to one or more 771 ESInets. Each originating network is also connected to one or more 772 ESInets. The ESInets maintain policy-based routing rules that 773 control the routing and processing of emergency calls. The 774 centralization of such rules within ESInets allows for a cleaner 775 separation between the responsibilities of the originating network 776 and that of the emergency services network, and provides greater 777 flexibility and control over processing of emergency calls by the 778 emergency services authorities and PSAPs. This can make it easier to 779 react quickly to situations that require changes in how emergency 780 calls are routed or handled (e.g., a natural disaster closes a PSAP), 781 as well as ease in making long-term changes that affect such routing 782 (e.g., cooperative agreements to specially handle calls requiring 783 translation or relay services). 785 In an environment that uses ESInets, the originating network might 786 pass all types of emergency calls to an ESInet (all calls with a 787 service URN of or starting with "sos"). The ESInet then routs such 788 calls to an appropriate PSAP. In an environment without an ESInet, 789 the emergency services authorities and the originating carriers 790 determine how such calls are routed. 792 9. New Metadata/Control Values 794 This document adds new attribute values to the metadata/control 795 structure defined in [I-D.ietf-ecrit-ecall]. 797 In addition to the base usage from the PSAP to the IVS to 798 acknowledge receipt of crash data, the element is also 799 contained in a metadata/control block sent by the IVS to the PSAP. 800 This is used by the IVS to acknowledge receipt of a request by the 801 PSAP and indicate if the request was carried out when that request 802 would not otherwise be acknowledged (if the PSAP requests the 803 vehicle to send data and the vehicle does so, the data serves as a 804 success acknowledgement). 806 The element is used in a metadata/control block 807 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 808 inform the PSAP of the vehicle capabilities. Child elements 809 contain all actions and data types supported by the vehicle and 810 all available lamps (lights) and cameras. 812 New request values are added to the element to enable 813 the PSAP to request the vehicle to perform actions. 815 Mandatory Actions (the IVS and the PSAP MUST support): 817 o Transmit data object (VEDS MUST be supported; MSD MAY be 818 supported) 820 Optional Actions (the IVS and the PSAP MAY support): 822 o Play and/or display static (pre-defined) message 823 o Speak/display dynamic text (text supplied in action) 824 o Flash or turn on or off a lamp (light) 825 o Honk horn 826 o Enable a camera 828 The element indicates the object being acknowledged (i.e., a 829 data object or a metadata/control block containing 830 elements), and reports success or failure. 832 The element has child elements indicating 833 the actions supported by the IVS. 835 The element contains attributes to indicate the request and 836 to supply any needed information, and MAY contain a child 837 element to contain the text for a dynamic message. The 'action' 838 attribute is mandatory and indicates the specific action. 839 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 840 allowed values; this document adds new values to that registry in 841 Table 2. 843 Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block 844 in response to the VEDS data sent by the IVS in SIP requests other 845 than INFO (e.g., the INVITE). This metadata/control block is sent in 846 the SIP response to the request (e.g., the INVITE response). When 847 the PSAP needs to send a control block that is not an immediate 848 response to a VEDS or other data sent by the IVS, the control block 849 is transmitted from the PSAP to the IVS in a SIP INFO request within 850 the established dialog. The IVS sends the requested data (e.g., the 851 VEDS) or an acknowledgment (for requests other than to send data) in 852 a new INFO request. This mechanism flexibly allows the PSAP to send 853 metadata/control data to the IVS and the IVS to respond. If control 854 data sent in a response message requests the IVS to send a new VEDS 855 or other data block, or to perform an action other than sending data, 856 the IVS sends the requested data or an acknowledgment regarding the 857 action in an INFO message within the dialog. 859 9.1. New values for the 'action' attribute' 861 The following new "action" values are defined: 863 msg-static displays or plays a predefined message (translated as 864 appropriate for the language of the vehicle's interface). A 865 registry is created in Section 15.4 for messages and their IDs. 866 Vehicles include the highest registered message in their 867 element to indicate support for all messages up to 868 and including the indicated value. 870 msg-dynamic displays or speaks (via text-to-speech) a dynamic 871 message included in the request. 873 honk sounds the horn. 875 lamp turns a lamp (light) on, off, or flashes. 877 enable-camera adds a one-way media stream (established via SIP re- 878 INVITE sent by the vehicle) to enable the PSAP call taker to view 879 a feed from a camera. 881 Note that there is no 'request' action to play dynamic media (such as 882 an audio message). The PSAP can send a SIP re-INVITE to establish a 883 one-way media stream for this purpose. 885 9.2. Request Example 886 887 892 893 895 896 897 Remain calm. Help is on the way. 898 900 902 Figure 7: Request Example 904 9.3. The element 906 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 907 PSAP to acknowledge the MSD. Here, the element is also 908 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 909 to acknowledge receipt of a element that requested the IVS 910 to perform an action other than transmitting a data object (e.g., a 911 request to display a message would be acknowledged, but a request to 912 transmit VEDS data would not result in a separate element being 913 sent, since the data object itself serves as acknowledgment.) An 914 element sent by an IVS references the unique ID of the 915 metadata/control object containing the request(s) and indicates 916 whether the request was successfully performed, and if not, 917 optionally includes an explanation. 919 9.3.1. Ack Examples 920 921 926 927 928 930 932 934 Figure 8: Ack Example from IVS to PSAP 936 9.4. The element 938 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 939 the IVS to indicate its capabilities to the PSAP. 941 The element contains a child element per 942 action supported by the vehicle. The vehicle MUST support sending 943 the VEDS data object and so includes at a minimum a child 944 element with the 'action' attribute set to "send-data" and the 945 'supported-values' attribute containing all data blocks supported by 946 the IV, which MUST include 'VEDS'. All other actions are OPTIONAL. 948 If the "msg-static" action is supported, a child element 949 with the 'action' attribute set to "msg-static" is included, with the 950 'msgid' attribute set to the highest supported static message 951 supported by the vehicle. A registry is created in Section 15.4 to 952 map 'msgid' values to static text messages. By sending the highest 953 supported static message number in its element, the 954 vehicle indicates its support for all static messages in the registry 955 up to and including that value. 957 If the "lamp" action is supported, a child element with the 958 'action' attribute set to "lamp" is included, with the 'supported- 959 values' attribute set to all supported lamp IDs. A registry is 960 created in Section 15.5 to contain lamp ID values. 962 If the "enable-camera" action is supported, a child element 963 with the 'action' attribute set to "enable-camera" is included, with 964 the 'supported-values' attribute set to all supported camera IDs. A 965 registry is created in Section 15.6 to contain camera ID values. 967 9.4.1. Capabilities Example 969 970 975 976 977 980 981 982 983 984 986 988 Figure 9: Capabilities Example 990 10. Test Calls 992 An NG-ACN test call is a call that is recognized and treated to some 993 extent as an NG-ACN call but not given emergency call treatment and 994 not handled by a call taker. The specific handling of test NG-ACN 995 calls is not itself standardized; the test call facility is intended 996 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 997 successfully established with voice and/or other media communication. 998 The IVS might also be able to verify that the crash data was 999 successfully received. 1001 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 1002 ability to utilize test call functionality from Section 15 of 1003 [RFC6881]. A service URN starting with "test." indicates a test 1004 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 1005 for test calls. 1007 MNOs, emergency authorities, ESInets, and PSAPs determine how to 1008 treat a vehicle call requesting the "test" service URN so that the 1009 desired functionality is tested, but this is outside the scope of 1010 this document. (One possibility is that MNOs route such calls as 1011 non-emergency calls to an ESInet, which routes them to a PSAP that 1012 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 1013 data acknowledgment, and plays an audio clip (for example, saying 1014 that the call reached an appropriate PSAP and the vehicle data was 1015 successfully processed) in addition to supporting media loopback per 1016 [RFC6881]). 1018 Note that since test calls are placed using "test" as the parent 1019 service URN and "sos" as a child, such calls are not treated as an 1020 emergency call and so some functionality might not apply (such as 1021 preemption or service availability for devices lacking service ("non- 1022 service-initialized" or "NSI" devices) if those are available for 1023 emergency calls). 1025 11. The emergencyCallData.eCall.VEDS INFO package 1027 This document registers the 'emergencyCallData.eCall.VEDS' INFO 1028 package. 1030 Both endpoints (the IVS and the PSAP equipment) include 1031 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 1032 [RFC6086] to indicate ability to receive INFO messages carrying data 1033 as described here. 1035 Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates 1036 the ability to receive NG-ACN related body parts as specified in 1037 [TBD: THIS DOCUMENT]. 1039 An INFO request message carrying data related to an emergency call as 1040 described in [TBD: THIS DOCUMENT] has an Info-Package header field 1041 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 1043 The requirements of Section 10 of [RFC6086] are addressed in the 1044 following sections. 1046 11.1. Overall Description 1048 This section describes "what type of information is carried in INFO 1049 requests associated with the Info Package, and for what types of 1050 applications and functionalities UAs can use the Info Package." 1052 INFO requests associated with the emergencyCallData.eCall.VEDS INFO 1053 package carry data associated with emergency calls as defined in 1054 [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency 1055 calls established using SIP. The functionality is to carry vehicle 1056 data and metadata/control information between vehicles and PSAPs. 1057 Refer to [TBD: THIS DOCUMENT] for more information. 1059 11.2. Applicability 1061 This section describes "why the Info Package mechanism, rather than 1062 some other mechanism, has been chosen for the specific use-case...." 1064 The use of INFO is based on an analysis of the requirements against 1065 the intent and effects of INFO versus other approaches (which 1066 included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane 1067 transport, and non-SIP protocols). In particular, the transport of 1068 emergency call data blocks occurs within a SIP emergency dialog, per 1069 Section 6, and is normally carried in the initial INVITE and its 1070 response; the use of INFO only occurs when emergency-call-related 1071 data needs to be sent mid-call. While MESSAGE could be used, it is 1072 not tied to a SIP dialog as is INFO and thus might not be associated 1073 with the dialog. SIP OPTIONS or re-INVITE could also be used, but is 1074 seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into 1075 service, but the semantics are not a good fit, e.g., the subscribe/ 1076 notify mechanism provides one-way communication consisting of (often 1077 multiple) notifications from notifier to subscriber indicating that 1078 certain events in notifier have occurred, whereas what's needed here 1079 is two-way communication of data related to the emergency dialog. 1080 Use of the media plane mechanisms was discounted because the number 1081 of messages needing to be exchanged in a dialog is normally zero or 1082 very few, and the size of the data is likewise very small. The 1083 overhead caused by user plane setup (e.g., to use MSRP as transport) 1084 would be disproportionately large. 1086 Based on the the analyses, the SIP INFO method was chosen to provide 1087 for mid-call data transport. 1089 11.3. Info Package Name 1091 The info package name is emergencyCallData.eCall.VEDS 1093 11.4. Info Package Parameters 1095 None 1097 11.5. SIP Option-Tags 1099 None 1101 11.6. INFO Request Body Parts 1103 The body for an emergencyCallData.eCall.VEDS info package is a 1104 multipart body. Zero or one application/ 1105 emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part, 1106 zero or more application/emergencyCallData.control+xml (containing a 1107 metadata/control object) parts, and zero or one application/ 1108 emergencyCallData.eCall.MSD+per (containing an MSD) part are 1109 permitted. Intermediate multipart body parts MAY appear. 1111 The body parts are sent per [RFC6086], and in addition, to align with 1112 with how these body parts are sent in non-INFO messages, each 1113 associated body part is referenced by a Call-Info header field at the 1114 top level of the SIP message. The body part has a Content- 1115 Disposition header field set to "By-Reference". 1117 Service providers are not expected to attach [RFC7852] Additional 1118 Data to an INFO request. 1120 See [TBD: THIS DOCUMENT] for more information. 1122 11.7. Info Package Usage Restrictions 1124 Usage is limited to vehicle-initiated emergency calls as defined in 1125 [TBD: THIS DOCUMENT]. 1127 11.8. Rate of INFO Requests 1129 The rate of SIP INFO requests associated with the 1130 emergencyCallData.eCall.VEDS info package is normally quite low (most 1131 dialogs are likely to contain zero INFO requests, while others can be 1132 expected to carry an occasional request). 1134 11.9. Info Package Security Considerations 1136 The MIME content type registations for the data blocks that can be 1137 carried using this INFO package contains a discussion of the security 1138 and/or privacy considerations specific to that data block. The 1139 "Security Considerations" and "Privacy Considerations" sections of 1140 [TBD: THIS DOCUMENT] discuss security and privacy considerations of 1141 the data carried in vehicle-initiated emergency calls as described in 1142 that document. 1144 11.10. Implementation Details 1146 See [TBD: THIS DOCUMENT] for protocol details. 1148 11.11. Examples 1150 See [TBD: THIS DOCUMENT] for protocol examples. 1152 12. Example 1154 Figure 10 shows an NG-ACN call routing. The mobile network operator 1155 (MNO) routes the call to an Emergency services IP Network (ESInet), 1156 as for any emergency call. The ESInet routes the call to an 1157 appropriate NG-ACN-capable PSAP (using location information and the 1158 fact that that it is an NG-ACN call). The call is processed by the 1159 Emergency Services Routing Proxy (ESRP), as the entry point to the 1160 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 1161 PSAP, where the call is received by a call taker. (In deployments 1162 where there is no ESInet, the MNO itself routes the call directly to 1163 an appropriate NG-ACN-capable PSAP.) 1165 +---------------------------------------+ 1166 | | 1167 +------------+ | +-------+ | 1168 | | | | PSAP2 | | 1169 | | | +-------+ | 1170 | Originating| | | 1171 | Mobile | | +------+ +-------+ | 1172 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1173 | | | +------+ +-------+ | 1174 | | | | 1175 +------------+ | +-------+ | 1176 | | PSAP3 | | 1177 | +-------+ | 1178 | | 1179 | | 1180 | | 1181 | ESInet | 1182 +---------------------------------------+ 1184 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1186 The example, shown in Figure 11, illustrates a SIP emergency call 1187 INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS 1188 data block), and capabilities data (an eCall metadata/control block 1189 with extensions defined in this document) attached to the SIP INVITE 1190 message. The INVITE has a request URI containing the 1191 'urn:service:sos.ecall.automatic' service URN. 1193 The example VEDS data structure shows information about about a 1194 crashed vehicle. The example communicates that the car is a model 1195 year 2015 Saab 9-5 (a car which does not exist). The front airbag 1196 deployed as a consequence of the crash. The 1197 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 1198 passenger car (the code is set to '101') and that it is not a 1199 convertible (the 'ConvertibleIndicator' value is set to 'false'). 1201 The 'VehicleCrashPulse' element provides further information about 1202 the crash, namely that the force of impact based on the change in 1203 velocity over the duration of the crash pulse was 100 MPH. The 1204 principal direction of the force of the impact is set to '12' (which 1205 refers to 12 O'Clock, corresponding to a frontal collision). This 1206 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1207 element. 1209 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1210 quarter turns in concert with a rollover expressed as a number; in 1211 our case 1. 1213 No roll bar was deployed, as indicated in 1214 'VehicleRollbarDeployedIndicator' being set to 'false'. 1216 Next, there is information indicating seatbelt and seat sensor data 1217 for individual seat positions in the vehicle. In our example, 1218 information from the driver seat is available (value '1' in the 1219 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1220 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1221 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1222 and the seat sensor determined that the seat was occupied 1223 ('VehicleSeatOccupiedIndicator' element). 1225 Finally, information about the weight of the vehicle, which is 600 1226 kilogram in our example. 1228 In addition to the information about the vehicle, further indications 1229 are provided, namely the presence of fuel leakage 1230 ('FuelLeakingIndicator' element), an indication whether the vehicle 1231 was subjected to multiple impacts ('MultipleImpactsIndicator' 1232 element), the orientation of the vehicle at final rest 1233 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1234 that there are no parts of the vehicle on fire (the 1235 'VehicleFireIndicator' element). 1237 INVITE urn:service:sos.ecall.automatic SIP/2.0 1238 To: urn:service:sos.ecall.automatic 1239 From: ;tag=9fxced76sl 1240 Call-ID: 3848276298220188511@atlanta.example.com 1241 Geolocation: 1242 Geolocation-Routing: no 1243 Call-Info: ; 1244 purpose=EmergencyCallData.VEDS 1245 Call-Info: ; 1246 purpose=emergencyCallData.control 1247 Accept: application/sdp, application/pidf+xml, 1248 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 1262 --boundary1 1263 Content-Type: application/pidf+xml 1264 Content-ID: 1265 Content-Disposition: by-reference;handling=optional 1267 1268 1276 1277 1278 1279 1280 -34.407 150.883 1281 1282 1283 278 1284 1285 1286 1287 1288 gps 1289 1290 2012-04-5T10:18:29Z 1291 1M8GDM9A_KP042788 1292 1293 1295 --boundary1 1296 Content-Type: application/EmergencyCallData.VEDS+xml 1297 Content-ID: <1234567890@atlanta.example.com> 1298 Content-Disposition: by-reference;handling=optional 1300 1301 1305 1306 1307 Saab 1308 1309 1310 9-5 1311 1312 1314 2015 1315 1316 1317 FRONT 1318 true 1319 1320 1321 false 1322 MAIN 1323 1325 101 1326 1327 1328 1329 1331 100 1332 1333 1335 MPH 1336 1337 12 1338 1339 1 1340 1341 1342 false 1343 1344 1345 1 1346 1347 true 1348 1349 true 1350 1351 true 1352 1353 1354 1356 1358 600 1359 1360 1362 kilogram 1363 1364 1365 1366 true 1367 false 1368 true 1369 Driver 1370 1371 false 1372 1373 1375 --boundary1 1376 Content-Type: application/emergencyCallData.control+xml 1377 Content-ID: <1234567892@atlanta.example.com> 1378 Content-Disposition: by-reference;handling=optional 1380 1381 1386 1387 1388 1392 1393 1394 1395 1397 1399 1401 --boundary1-- 1403 Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call 1405 13. Security Considerations 1407 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1408 the security considerations described there and in [RFC5069] apply 1409 here. Implementors are cautioned to read and understand the 1410 discussion in those documents. 1412 As with emergency service systems where location data is supplied or 1413 determined with the assistance of an end host, there is the 1414 possibility that that location is incorrect, either intentially 1415 (e.g., in a denial of service attack against the emergency services 1416 infrastructure) or due to a malfunctioning device. The reader is 1417 referred to [RFC7378] for a discussion of some of these 1418 vulnerabilities. 1420 In addition to the security considerations discussion specific to the 1421 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1422 MAY decline to carry out any requested action (e.g., if the vehicle 1423 requires but is unable to verify the certificate used to sign the 1424 request). The vehicle MAY use any value in the reason registry to 1425 indicate why it did not take an action (e.g., the generic "unable" or 1426 the more specific "security-failure"). 1428 14. Privacy Considerations 1430 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1431 builds on [RFC7852], the data structures specified there, and the 1432 corresponding privacy considerations discussed there, apply here as 1433 well. The VEDS data structure contains optional elements that can 1434 carry identifying and personal information, both about the vehicle 1435 and about the owner, as well as location information, and so needs to 1436 be protected against unauthorized disclosure, as discussed in 1437 [RFC7852]. Local regulations may impose additional privacy 1438 protection requirements. 1440 The additional functionality enabled by this document, such as access 1441 to vehicle camera streams, carries a burden of protection and so 1442 implementations need to be careful that access is only provided 1443 within the context of an emergency call or to an emergency services 1444 provider (e.g., by verifying that the request for camera access is 1445 signed by a certificate issued by an emergency services registrar). 1447 15. IANA Considerations 1449 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1450 content type, and adds "VEDS" to the Emergency Call Additional Data 1451 registry. This document adds to and creates sub-registries in the 1452 'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall]. 1453 This document registers a new INFO package. 1455 15.1. MIME Content-type Registration for 'application/ 1456 EmergencyCall.VEDS+xml' 1458 This specification requests the registration of a new MIME content 1459 type according to the procedures of RFC 4288 [RFC4288] and guidelines 1460 in RFC 3023 [RFC3023]. 1462 MIME media type name: application 1464 MIME subtype name: EmergencyCallData.VEDS+xml 1466 Mandatory parameters: none 1468 Optional parameters: charset 1470 Indicates the character encoding of enclosed XML. 1472 Encoding considerations: Uses XML, which can employ 8-bit 1473 characters, depending on the character encoding used. See 1474 Section 3.2 of RFC 3023 [RFC3023]. 1476 Security considerations: 1478 This content type is designed to carry vehicle crash data 1479 during an emergency call. 1481 This data can contain personal information including vehicle 1482 VIN, location, direction, etc. Appropriate precautions need to 1483 be taken to limit unauthorized access, inappropriate disclosure 1484 to third parties, and eavesdropping of this information. 1485 Please refer to Section 7 and Section 8 of [RFC7852] for more 1486 information. 1488 When this content type is contained in a signed or encrypted 1489 body part, the enclosing multipart (e.g., multipart/signed or 1490 multipart/encrypted) has the same Content-ID as the data part. 1491 This allows an entity to identify and access the data blocks it 1492 is interested in without having to dive deeply into the message 1493 structure or decrypt parts it is not interested in. (The 1494 'purpose' parameter in a Call-Info header field identifies the 1495 data, and the CID URL points to the data block in the body, 1496 which has a matching Content-ID body part header field). 1498 Interoperability considerations: None 1500 Published specification: [VEDS] 1502 Applications which use this media type: Emergency Services 1504 Additional information: None 1506 Magic Number: None 1508 File Extension: .xml 1510 Macintosh file type code: 'TEXT' 1512 Persons and email addresses for further information: Randall 1513 Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, 1514 Hannes.Tschofenig@gmx.net 1516 Intended usage: LIMITED USE 1518 Author: This specification is a work item of the IETF ECRIT 1519 working group, with mailing list address . 1521 Change controller: The IESG 1523 15.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1524 Data registry 1526 This specification requests IANA to add the 'VEDS' entry to the 1527 Emergency Call Additional Data registry, with a reference to this 1528 document. The Emergency Call Additional Data registry was 1529 established by [RFC7852]. 1531 15.3. New Action Values 1533 This document adds new values for the 'action' attribute of the 1534 element in the "Action Registry" registry created by 1535 [I-D.ietf-ecrit-ecall]. 1537 +---------------+-------------------------------------+ 1538 | Name | Description | 1539 +---------------+-------------------------------------+ 1540 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1541 | | | 1542 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1543 | | | 1544 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1545 | | | 1546 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1547 | | | 1548 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1549 +---------------+-------------------------------------+ 1551 Table 2: Action Registry New Values 1553 15.4. Static Message Registry 1555 This document creates a new sub-registry called "Static Message 1556 Registry" in the "Metadata/Control Data" registry established by 1557 [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected 1558 to support all static messages translated into all languages 1559 supported by the vehicle, it is important to limit the number of such 1560 messages. As defined in [RFC5226], this registry operates under 1561 "Publication Required" rules, which require a stable, public document 1562 and implies expert review of the publication. The expert should 1563 determine that the document has been published by an appropriate 1564 emergency services organization (e.g., NENA, EENA, APCO) or by the 1565 IETF with input from an emergency services organization, and that the 1566 proposed message is sufficiently distinguishable from other messages. 1568 The contents of this registry are: 1570 ID: An integer identifier to be used in the 'msgid' attribute of a 1571 metadata/control element. 1573 Message: The text of the message. Messages are listed in the 1574 registry in English; vehicles are expected to implement 1575 translations into languages supported by the vehicle. 1577 When new messages are added to the registry, the message text is 1578 determined by the registrant; IANA assigns the IDs. Each message is 1579 assigned a consecutive integer value as its ID. This allows an IVS 1580 to indicate by a single integer value that it supports all messages 1581 with that value or lower. 1583 The initial set of values is listed in Table 3. 1585 +----+--------------------------------------------------------------+ 1586 | ID | Message | 1587 +----+--------------------------------------------------------------+ 1588 | 1 | Emergency authorities are aware of your incident and | 1589 | | location, but are unable to speak with you right now. We | 1590 | | will help you as soon as possible. | 1591 +----+--------------------------------------------------------------+ 1593 Table 3: Static Message Registry 1595 15.5. Lamp ID Registry 1597 This document creates a new sub-registry called "Lamp ID Registry" in 1598 the "Metadata/Control Data" registry established by 1599 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1600 the names of automotive lamps (lights). As defined in [RFC5226], 1601 this registry operates under "Expert Review" rules. The expert 1602 should determine that the proposed lamp name is clearly 1603 understandable and is sufficiently distinguishable from other lamp 1604 names. 1606 The contents of this registry are: 1608 Name: The identifier to be used in the 'lamp-ID' attribute of a 1609 metadata/control element. 1611 Description: A description of the lamp (light). 1613 The initial set of values is listed in Table 4. 1615 +----------------+---------------------------------------------+ 1616 | Name | Description | 1617 +----------------+---------------------------------------------+ 1618 | head | The main lamps used to light the road ahead | 1619 | | | 1620 | interior | Interior lamp, often at the top center | 1621 | | | 1622 | fog-front | Front fog lamps | 1623 | | | 1624 | fog-rear | Rear fog lamps | 1625 | | | 1626 | brake | Brake indicator lamps | 1627 | | | 1628 | brake-center | Center High Mounted Stop Lamp | 1629 | | | 1630 | position-front | Front position/parking/standing lamps | 1631 | | | 1632 | position-rear | Rear position/parking/standing lamps | 1633 | | | 1634 | turn-left | Left turn/directional lamps | 1635 | | | 1636 | turn-right | Right turn/directional lamps | 1637 | | | 1638 | hazard | Hazard/four-way lamps | 1639 +----------------+---------------------------------------------+ 1641 Table 4: Lamp ID Registry Initial Values 1643 15.6. Camera ID Registry 1645 This document creates a new sub-registry called "Camera ID Registry" 1646 in the "Metadata/Control Data" registry established by 1647 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1648 automotive cameras. As defined in [RFC5226], this registry operates 1649 under "Expert Review" rules. The expert should determine that the 1650 proposed camera name is clearly understandable and is sufficiently 1651 distinguishable from other camera names. 1653 The contents of this registry are: 1655 Name: The identifier to be used in the 'camera-ID' attribute of a 1656 control element. 1658 Description: A description of the camera. 1660 The initial set of values is listed in Table 5. 1662 +-------------+-----------------------------------------------------+ 1663 | Name | Description | 1664 +-------------+-----------------------------------------------------+ 1665 | backup | Shows what is behind the vehicle, e.g., often used | 1666 | | for driver display when the vehicle is in reverse. | 1667 | | Also known as rearview, reverse, rear visibility, | 1668 | | etc. | 1669 | | | 1670 | left-rear | Shows view to the left and behind (e.g., left side | 1671 | | rear-view mirror or blind spot view) | 1672 | | | 1673 | right-rear | Shows view to the right and behind (e.g., right | 1674 | | side rear-view mirror or blind spot view) | 1675 | | | 1676 | forward | Shows what is in front of the vehicle | 1677 | | | 1678 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1679 | | collision detection systems), separate from backup | 1680 | | view | 1681 | | | 1682 | lane | Used by systems to identify road lane and/or | 1683 | | monitor vehicle's position within lane | 1684 | | | 1685 | interior | Shows the interior (e.g., driver) | 1686 | | | 1687 | night-front | Night-vision view of what is in front of the | 1688 | | vehicle | 1689 +-------------+-----------------------------------------------------+ 1691 Table 5: Camera ID Registry Initial Values 1693 16. Acknowledgements 1695 We would like to thank Lena Chaponniere, Stephen Edge, and Christer 1696 Holmberg for their review and suggestions; Robert Sparks and Paul 1697 Kyzivat for their help with the SIP mechanisms; Michael Montag, 1698 Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, and Rex 1699 Buddenberg for their feedback; and Ulrich Dietz for his help with 1700 earlier versions of the original version of this document. 1702 17. Changes from Previous Versions 1704 17.1. Changes from draft-ietf-13 to draft-ietf-14 1706 o Body parts now always sent enclosed in multipart (even if only 1707 body part in SIP message) and hence always have a Content- 1708 Disposition of By-Reference 1709 o Fixed typos. 1711 17.2. Changes from draft-ietf-11 to draft-ietf-13 1713 o Fixed typos 1715 17.3. Changes from draft-ietf-10 to draft-ietf-11 1717 o Clarifications suggested by Christer 1718 o Corrections to Content-Disposition text and examples as suggested 1719 by Paul Kyzivat 1720 o Clarifications to Content-Disposition text and examples to clarify 1721 that handling=optional is only used in the initial INVITE 1723 17.4. Changes from draft-ietf-09 to draft-ietf-10 1725 o Fixed errors in examples found by Dale in eCall draft 1726 o Removed enclosing sub-section of INFO package registration section 1727 o Added text per Christer and Dale's suggestions that the MSD and 1728 metadata/control blocks are sent in INFO with a Call-Info header 1729 field referencing them 1730 o Other text changes per comments received from Christer and Ivo 1731 against eCall draft. 1733 17.5. Changes from draft-ietf-08 to draft-ietf-09 1735 o Added INFO package registration for eCall.VEDS 1736 o Moved element and other extension points back to 1737 eCall document so that extension points are in base spec (and also 1738 to get XML schema to compile) 1739 o Text changes for clarification. 1741 17.6. Changes from draft-ietf-07 to draft-ietf-08 1743 o Moved much of the metadata/control object from 1744 [I-D.ietf-ecrit-ecall] to this document as extensions 1745 o Editorial clarifications and simplifications 1746 o Moved "Call Routing" to be a subsection of "Call Setup" 1747 o Deleted "Profile" section and moved some of its text into 1748 "Introduction" 1750 17.7. Changes from draft-ietf-06 to draft-ietf-07 1752 o Minor editorial changes 1754 17.8. Changes from draft-ietf-05 to draft-ietf-06 1756 o Added clarifying text regarding signed and encrypted data 1757 o Additional informative text in "Migration to Next-Generation" 1758 section 1760 o Additional clarifying text regarding security and privacy. 1762 17.9. Changes from draft-ietf-04 to draft-ietf-05 1764 o Reworded security text in main document and in MIME registration 1765 for the VEDS object 1767 17.10. Changes from draft-ietf-03 to draft-ietf-04 1769 o Added example VEDS object 1770 o Additional clarifications and corrections 1771 o Removed references from Abstract 1772 o Moved Document Scope section to follow Introduction 1774 17.11. Changes from draft-ietf-02 to draft-ietf-03 1776 o Additional clarifications and corrections 1778 17.12. Changes from draft-ietf-01 to draft-ietf-02 1780 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1781 aspects including the service URN; this document no longer 1782 proposes a unique service URN for non-eCall NG-ACN calls; the same 1783 service URN is now used for all NG-ACN calls including NG-eCall 1784 and non-eCall 1785 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1786 support it 1787 o Minor wording improvements and clarifications 1789 17.13. Changes from draft-ietf-00 to draft-ietf-01 1791 o Added further discussion of test calls 1792 o Added further clarification to the document scope 1793 o Mentioned that multi-region vehicles may need to support other 1794 crash notification specifications such as eCall 1795 o Minor wording improvements and clarifications 1797 17.14. Changes from draft-gellens-02 to draft-ietf-00 1799 o Renamed from draft-gellens- to draft-ietf- 1800 o Added text to Introduction to clarify that during a CS ACN, the 1801 PSAP call taker usually needs to listen to the data and transcribe 1802 it 1804 17.15. Changes from draft-gellens-01 to -02 1806 o Fixed case of 'EmergencyCallData', in accordance with changes to 1807 [RFC7852] 1809 17.16. Changes from draft-gellens-00 to -01 1811 o Now using 'EmergencyCallData' for purpose parameter values and 1812 MIME subtypes, in accordance with changes to [RFC7852] 1813 o Added reference to RFC 6443 1814 o Fixed bug that caused Figure captions to not appear 1816 18. References 1818 18.1. Normative References 1820 [I-D.ietf-ecrit-ecall] 1821 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1822 European eCall", draft-ietf-ecrit-ecall-13 (work in 1823 progress), September 2016. 1825 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1826 Requirement Levels", BCP 14, RFC 2119, 1827 DOI 10.17487/RFC2119, March 1997, 1828 . 1830 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1831 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1832 . 1834 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1835 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1836 . 1838 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1839 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1840 December 2005, . 1842 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1843 Emergency and Other Well-Known Services", RFC 5031, 1844 DOI 10.17487/RFC5031, January 2008, 1845 . 1847 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1848 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1849 DOI 10.17487/RFC5226, May 2008, 1850 . 1852 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1853 Presence Information Data Format Location Object (PIDF-LO) 1854 Usage Clarification, Considerations, and Recommendations", 1855 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1856 . 1858 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1859 Thomson, "Dynamic Extensions to the Presence Information 1860 Data Format Location Object (PIDF-LO)", RFC 5962, 1861 DOI 10.17487/RFC5962, September 2010, 1862 . 1864 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1865 "Framework for Emergency Calling Using Internet 1866 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1867 2011, . 1869 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1870 Communications Services in Support of Emergency Calling", 1871 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1872 . 1874 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1875 J. Winterbottom, "Additional Data Related to an Emergency 1876 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1877 . 1879 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1880 NENA Data Standardization Workgroup, , "Vehicular 1881 Emergency Data Set (VEDS) version 3", July 2012, 1882 . 1885 18.2. Informative references 1887 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1888 Emergency Context Resolution with Internet Technologies", 1889 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1890 . 1892 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1893 Shanmugam, "Security Threats and Requirements for 1894 Emergency Call Marking and Mapping", RFC 5069, 1895 DOI 10.17487/RFC5069, January 2008, 1896 . 1898 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1899 Initiation Protocol (SIP) INFO Method and Package 1900 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1901 . 1903 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1904 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1905 December 2014, . 1907 [triage-2008] 1908 National Center for Injury Prevention and Control, and 1909 Centers for Disease Control and Prevention, 1910 "Recommendations from the Expert Panel: Advanced Automatic 1911 Collision Notification and Triage of the Injured Patient", 1912 2008, . 1914 [triage-2011] 1915 National Center for Injury Prevention and Control, and 1916 Centers for Disease Control and Prevention, "Guidelines 1917 for field triage of injured patients: recommendations of 1918 the National Expert Panel on Field Triage", January 2012, 1919 . 1924 Authors' Addresses 1926 Randall Gellens 1927 Core Technology Consulting 1929 Email: rg+ietf@randy.pensive.org 1931 Brian Rosen 1932 NeuStar, Inc. 1933 470 Conrad Dr 1934 Mars, PA 16046 1935 US 1937 Email: br@brianrosen.net 1939 Hannes Tschofenig 1940 Individual 1942 Email: Hannes.Tschofenig@gmx.net 1943 URI: http://www.tschofenig.priv.at