idnits 2.17.00 (12 Aug 2021) /tmp/idnits56737/draft-ietf-ecrit-car-crash-23.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 801 has weird spacing: '...-static displ...' == Line 816 has weird spacing: '...dynamic displ...' == Line 819 has weird spacing: '... honk sound...' == Line 821 has weird spacing: '... lamp turns...' == Line 832 has weird spacing: '...-camera adds ...' == (1 more instance...) -- The document date (January 19, 2017) is 1941 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: draft-ietf-ecrit-ecall has been published as RFC 8147 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Possible downref: Non-RFC (?) normative reference: ref. 'VEDS' Summary: 1 error (**), 0 flaws (~~), 8 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: July 23, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 January 19, 2017 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-23.txt 13 Abstract 15 This document describes how to use IP-based emergency services 16 mechanisms to support the next generation of emergency calls placed 17 by vehicles (automatically in the event of a crash or serious 18 incident, or manually invoked by a vehicle occupant) and conveying 19 vehicle, sensor, and location data related to the crash or incident. 20 Such calls are often referred to as "Automatic Crash Notification" 21 (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the 22 case of manual trigger. The "Advanced" qualifier refers to the 23 ability to carry a richer set of data. 25 This document also registers a MIME media type and Emergency Call 26 Additional Data Block for the vehicle, sensor, and location data 27 (often referred to as "crash data" even though there is not 28 necessarily a crash) and a SIP INFO package to enable carrying this 29 and related data in SIP INFO requests. An external specification for 30 the data format, contents, and structure are referenced in this 31 document. 33 This document reuses the technical aspects of next-generation pan- 34 European eCall (a mandated and standardized system for emergency 35 calls by in-vehicle systems within Europe and other regions). 36 However, this document specifies use of a different set of vehicle 37 (crash) data, specifically, the Vehicle Emergency Data Set (VEDS) 38 rather than the eCall Minimum Set of Data (MSD). This document is an 39 extension of the IETF eCall document, with the primary differences 40 being that this document makes the MSD data set optional and VEDS 41 mandatory, and adds attribute values to the metadata/control object 42 to permit greater functionality. This document registers a new SIP 43 INFO package (identical to that registered for eCall but with the 44 addition of the VEDS MIME type). This document also describes legacy 45 (circuit-switched) ACN systems and their migration to next-generation 46 emergency calling, to provide background information and context. 48 Status of This Memo 50 This Internet-Draft is submitted in full conformance with the 51 provisions of BCP 78 and BCP 79. 53 Internet-Drafts are working documents of the Internet Engineering 54 Task Force (IETF). Note that other groups may also distribute 55 working documents as Internet-Drafts. The list of current Internet- 56 Drafts is at http://datatracker.ietf.org/drafts/current/. 58 Internet-Drafts are draft documents valid for a maximum of six months 59 and may be updated, replaced, or obsoleted by other documents at any 60 time. It is inappropriate to use Internet-Drafts as reference 61 material or to cite them other than as "work in progress." 63 This Internet-Draft will expire on July 23, 2017. 65 Copyright Notice 67 Copyright (c) 2017 IETF Trust and the persons identified as the 68 document authors. All rights reserved. 70 This document is subject to BCP 78 and the IETF Trust's Legal 71 Provisions Relating to IETF Documents 72 (http://trustee.ietf.org/license-info) in effect on the date of 73 publication of this document. Please review these documents 74 carefully, as they describe your rights and restrictions with respect 75 to this document. Code Components extracted from this document must 76 include Simplified BSD License text as described in Section 4.e of 77 the Trust Legal Provisions and are provided without warranty as 78 described in the Simplified BSD License. 80 Table of Contents 82 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 83 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 84 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 85 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 86 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 9 87 6. Vehicle Data . . . . . . . . . . . . . . . . . . . . . . . . 12 88 7. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 89 8. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 15 90 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 16 91 9.1. New values for the 'action' attribute' . . . . . . . . . 17 92 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 18 93 9.3. The element . . . . . . . . . . . . . . . . . . . . 19 94 9.4. The element . . . . . . . . . . . . . . . 20 95 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 21 96 11. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 97 12. Security Considerations . . . . . . . . . . . . . . . . . . . 27 98 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 28 99 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 100 14.1. MIME Media Type Registration for 101 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 28 102 14.2. Registration of the 'VEDS' entry in the Emergency Call 103 Data Types registry . . . . . . . . . . . . . . . . . . 30 104 14.3. New Action Values . . . . . . . . . . . . . . . . . . . 30 105 14.4. Emergency Call Static Message Registry . . . . . . . . . 30 106 14.5. Emergency Call Vehicle Lamp ID Registry . . . . . . . . 31 107 14.6. Emergency Call Vehicle Camera ID Registry . . . . . . . 32 108 14.7. The emergencyCallData.eCall.VEDS SIP INFO package . . . 33 109 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 36 110 16. Changes from Previous Versions . . . . . . . . . . . . . . . 37 111 16.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 37 112 16.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 37 113 16.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 37 114 16.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 37 115 16.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 37 116 16.6. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 37 117 16.7. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 37 118 16.8. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 119 16.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 38 120 16.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 38 121 16.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 38 122 16.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 38 123 16.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 38 124 16.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 38 125 16.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 126 16.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 39 127 16.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 39 128 16.18. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 39 129 16.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 39 130 16.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 39 131 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 132 17.1. Normative References . . . . . . . . . . . . . . . . . . 40 133 17.2. Informative references . . . . . . . . . . . . . . . . . 41 134 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 136 1. Terminology 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in [RFC2119]. 142 This document re-uses terminology defined in Section 3 of [RFC5012]. 144 Additionally, we use the following abbreviations: 146 +--------+----------------------------------------------------------+ 147 | Term | Expansion | 148 +--------+----------------------------------------------------------+ 149 | 3GPP | 3rd Generation Partnership Project | 150 | AACN | Advanced Automatic Crash Notification | 151 | ACN | Automatic Crash Notification | 152 | APCO | Association of Public-Safety Communications Officials | 153 | EENA | European Emergency Number Association | 154 | ESInet | Emergency Services IP network | 155 | GNSS | Global Navigation Satellite System (which includes | 156 | | various systems such as the Global Positioning System or | 157 | | GPS) | 158 | IVS | In-Vehicle System | 159 | MNO | Mobile Network Operator | 160 | MSD | eCall Minimum Set of Data | 161 | NENA | National Emergency Number Association | 162 | NG | Next-Generation | 163 | POTS | Plain Old Telephone Service (normal, circuit-switched | 164 | | voice calls) | 165 | PSAP | Public Safety Answering Point | 166 | TSP | Telematics Service Provider | 167 | VEDS | Vehicle Emergency Data Set | 168 +--------+----------------------------------------------------------+ 170 Because the endpoints of a Next-Generation ACN call are a PSAP and an 171 IVS or TSP, to avoid receptively writing "IVS or TSP", the term "IVS" 172 is used to represent either an IVS or TSP when discussing signaling 173 behavior (e.g., sending VEDS data, sending a SIP INVITE request, 174 receiving a SIP INFO request, etc.). 176 2. Introduction 178 Emergency calls made by in-vehicle systems (e.g., automatically in 179 the event of a crash or serious incident or manually by a vehicle 180 occupant) assist in significantly reducing road deaths and injuries 181 by allowing emergency services to respond quickly and appropriately 182 to the specifics of the incident, often with better location 183 accuracy. 185 Drivers often have a poor location awareness, especially outside of 186 major cities, at night and when away from home (especially abroad). 187 In the most crucial cases, the victim(s) might not be able to call 188 because they have been injured or trapped. 190 For more than two decades, some vehicles have been equipped with 191 telematics systems which, among other features, place an emergency 192 call automatically in the event of a crash or manually in response to 193 an emergency call button. Such systems generally have on-board 194 location determination systems that make use of satellite-based 195 positioning technology, inertial sensors, gyroscopes, etc., which can 196 provide an accurate position for the vehicle. Such built-in systems 197 can take advantage of the benefits of being integrated into a 198 vehicle, such as more power capacity, ability to have larger or 199 specialized antenna, ability to be engineered to avoid or minimise 200 degradation by vehicle glass coatings, interference from other 201 vehicle systems, etc. Thus, the PSAP can be provided with a good 202 estimate of where the vehicle is during an emergency. Vehicle 203 manufacturers are increasingly adopting such systems, both for the 204 safety benefits and for the additional features and services they 205 enable (e.g., remote engine diagnostics, remote door unlock, stolen 206 vehicle tracking and disabling, etc.). 208 The general term for such systems is Automatic Crash Notification 209 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 210 used in this document as a general term. ACN systems transmit some 211 amount of data specific to the incident, referred to generally as 212 "crash data" (the term is commonly used even though there might not 213 have been a crash). While different systems transmit different 214 amounts of crash data, standardized formats, structures, and 215 mechanisms are needed to provide interoperability among systems and 216 PSAPs. 218 As of the date of this document, currently deployed in-vehicle 219 telematics systems are circuit-switched and lack a standards-based 220 ability to convey crash data directly to the PSAP (generally relying 221 on either a human advisor or an automated text-to-speech system to 222 provide the PSAP call taker with some crash data orally, or in some 223 cases via a proprietary mechanism). In most cases, the PSAP call 224 taker needs to first realize that the call is related to a vehicle 225 incident, and then listen to the data and transcribe it. Circuit- 226 switched ACN systems are referred to here as CS-ACN. 228 The transition to next-generation calling in general, and for 229 emergency calling in particular, provides an opportunity to vastly 230 improve the scope, breadth, reliability and usefulness of crash data 231 during an emergency by allowing a standardized set to be transmitted 232 during call set-up; to be automatically processed by the PSAP and 233 made available to the call taker in an integrated, automated way; as 234 well as provide the ability for a PSAP call taker to request that a 235 vehicle take certain actions, such as flashing lights or unlocking 236 doors. In addition, vehicle manufacturers are provided an 237 opportunity to take advantage of the same standardized mechanisms for 238 data transmission and request processing for internal use if they 239 wish (such as telemetry between the vehicle and a service center for 240 both emergency and non-emergency uses, including location-based 241 services, multi-media entertainment systems, remote door unlocking, 242 remote diagnostics, and road-side assistance applications). 244 Next-generation ACN provides an opportunity for such calls to be 245 recognized and processed as such during call set-up, and routed to an 246 equipped PSAP where the vehicle data is available to assist the call 247 taker in assessing and responding to the situation. Next-generation 248 (IP-based) ACN systems are referred to here as NG-ACN. 250 An ACN call can be initiated by a vehicle occupant or automatically 251 initiated by vehicle systems in the event of a serious incident. 252 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 253 used to refer to the class of calls that are placed by an in-vehicle 254 system (IVS) or Telematics Service Providers (TSP) and that carry 255 incident-related data as well as voice.) Automatically triggered 256 calls indicate a car crash or some other serious incident (e.g., a 257 fire). Manually triggered calls include reports of observed crashes 258 or serious hazards (such as impaired drivers or roadway debris). 260 The Association of Public-Safety Communications Officials (APCO) and 261 the National Emergency Number Association (NENA) have jointly 262 developed a standardized set of incident-related vehicle data for ACN 263 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 264 is often referred to as crash data although it is applicable in 265 incidents other than crashes. 267 This document describes how the IETF mechanisms for IP-based 268 emergency calls are used to provide the realization of next- 269 generation ACN. Although this specification is designed with the 270 requirements for North America ACN in mind (and both APCO and NENA 271 are based in the U.S.), it is specified generically such that the 272 technology can be re-used or extended to suit requirements in other 273 regions. 275 This document reuses the technical aspects of next-generation pan- 276 European eCall (a mandated and standardized system for emergency 277 calls by in-vehicle systems within Europe), as described in 278 [I-D.ietf-ecrit-ecall]. However, this document specifies use of a 279 different set of vehicle (crash) data, specifically, the Vehicle 280 Emergency Data Set (VEDS) rather than the eCall Minimum Set of Data 281 (MSD). This document is an extension of [I-D.ietf-ecrit-ecall], with 282 the differences being that this document makes the MSD data set 283 optional and VEDS mandatory, and adds new attribute values to the 284 metadata/control object defined in that document. This document also 285 registers a new SIP INFO package (identical to that defined in 286 [I-D.ietf-ecrit-ecall] with the addition of the VEDS MIME type). 288 This document registers the 'application/EmergencyCallData.VEDS+xml' 289 MIME media type, registers the 'VEDS' entry in the Emergency Call 290 Data Types registry, and registers a SIP INFO package to enable 291 carrying this and related data in SIP INFO requests. 293 Section 6 introduces VEDS. Section 7 describes how VEDS data and 294 metadata/control blocks are transported within NG-ACN calls. 295 Section 8 describes how such calls are placed. 297 These mechanisms are used to place emergency calls that are 298 identifiable as ACN calls and that carry standardized crash data in 299 an interoperable way. 301 Calls by in-vehicle systems are placed using cellular networks, which 302 might ignore location information sent by an originating device in an 303 emergency call INVITE, instead substituting their own location 304 information (often determined in cooperation with the originating 305 device). Standardized crash data structures often include location 306 as determined by the IVS. A benefit of this is that it allows the 307 PSAP to see both the location as determined by the cellular network 308 (often in cooperation with the originating device) and the location 309 as determined by the IVS. 311 This specification inherits the ability to utilize test call 312 functionality from Section 15 of [RFC6881]. 314 3. Document Scope 316 This document is focused on how an ACN emergency call is setup and 317 incident-related data (including vehicle, sensor, and location data) 318 is transmitted to the PSAP using IETF specifications. For the direct 319 model, this is the end-to-end description (between the vehicle and 320 the PSAP). For the TSP model, this describes the call leg between 321 the TSP and the PSAP, leaving the call leg between the vehicle and 322 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 323 are then free to use the same mechanism as for the other leg or not. 325 Note that Europe has a mandated and standardized system for emergency 326 calls by in-vehicle systems. This pan-European system is known as 327 "eCall" and is the subject of a separate document, 328 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 329 designed to operate in multiple regions might need to support eCall 330 as well as NG-ACN as described here. A vehicle IVS might determine 331 whether to use eCall or ACN by first determining the region or 332 country in which it is located (e.g., from a GNSS location estimate 333 and/or identity of or information from an MNO). If other regions 334 adopt other data formats, a multi-region vehicle might need to 335 support those as well. This document adopts the call set-up and 336 other technical aspects of [I-D.ietf-ecrit-ecall], which uses 337 [RFC7852]; this makes it straightforward to use a different data set 338 while keeping other technical aspects unchanged. Hence, both NG- 339 eCall and the NG-ACN mechanism described here are compatible, 340 differing primarily in the specific data block that is sent (the 341 eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in 342 this document), and some additions to the metadata/control data 343 block. If other regions adopt their own vehicle data sets, this can 344 be similarly accomodated without changing other technical aspects. 345 Note that any additional data formats require a new SIP INFO package 346 to permit transport within SIP INFO requests. 348 4. Overview of Legacy Deployment Models 350 Legacy (circuit-switched) systems for placing emergency calls by in- 351 vehicle systems generally have some ability to convey at least 352 location and in some cases telematics data to the PSAP. Most such 353 systems use one of three architectural models, which are described 354 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 355 These three models are illustrated below. 357 In the TSP model, both emergency and non-emergency calls are placed 358 to a Telematics Service Provider (TSP); a proprietary technique is 359 used for data transfer (such as a proprietary in-band modem) between 360 the TSP and the vehicle. 362 In an emergency, generally the TSP call taker bridges in the PSAP and 363 communicates location, crash data (such as impact severity and trauma 364 prediction), and other data (such as the vehicle description) to the 365 PSAP call taker verbally (in some cases, a proprietary out-of-band 366 interface is used). Since the TSP knows the location of the vehicle 367 (from on-board GNSS and sensors), location-based routing is usually 368 used to route to the appropriate PSAP. In some cases, the TSP is 369 able to transmit location automatically, using similar techniques as 370 for wireless calls. Typically, a three-way voice call is established 371 between the vehicle, the TSP, and the PSAP, allowing communication 372 between the PSAP call taker, the TSP call taker, and the vehicle 373 occupants (who might be unconscious). 375 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 376 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 377 \\\----/// crash data +------+ location via trunk +------+ 379 Figure 1: Legacy TSP Model. 381 In the paired model, the IVS uses a local link (typically Bluetooth 382 [Bluetooth]) with a previously-paired handset to establish an 383 emergency call with the PSAP (by dialing a standard emergency number; 384 9-1-1 in North America), and then communicates location data to the 385 PSAP via text-to-speech; crash data might or might not be conveyed 386 also using text-to-speech. Some such systems use an automated voice 387 prompt menu for the PSAP call taker (e.g., "this is an automatic 388 emergency call from a vehicle; press 1 to open a voice path to the 389 vehicle; press 2 to hear the location read out") to allow the call 390 taker to request location data via text-to-speech. 392 +---+ 393 ///----\\\ | H | 911/etc voice call via handset +------+ 394 ||| IVS |||-->| S +----------------------------------->+ PSAP | 395 \\\----/// +---+ location via text-to-speech +------+ 397 Figure 2: Legacy Paired Model 399 In the direct model, the IVS directly places an emergency call with 400 the PSAP by dialing a standard emergency number (9-1-1 in North 401 America). Such systems might communicate location data to the PSAP 402 via text-to-speech; crash data might or might not be conveyed using 403 text-to-speech. Some such systems use an automated voice prompt menu 404 (e.g., "this is an automatic emergency call from a vehicle; press 1 405 to open a voice path to the vehicle; press 2 to hear the location 406 read out") to allow the call taker to request location data via text- 407 to-speech. 409 ///----\\\ 911/etc voice call via IVS +------+ 410 ||| IVS |||---------------------------------------->+ PSAP | 411 \\\----/// location via text-to-speech +------+ 413 Figure 3: Legacy Direct Model 415 5. Migration to Next-Generation 417 Migration of emergency calls placed by in-vehicle systems to next- 418 generation (all-IP) technology per this document provides a 419 standardized mechanism to identify such calls and to convey crash 420 data with the call setup, as well as enabling additional 421 communications modalities and enhanced functionality. This allows 422 ACN calls and crash data to be automatically processed by the PSAP 423 and made available to the call taker in an integrated, automated way. 424 Because the crash data is carried in the initial SIP INVITE (per 425 [RFC7852]) the PSAP can present it to the call taker simultaneously 426 with the appearance of the call. The PSAP can also process the data 427 to take other actions (e.g., if multiple calls from the same location 428 arrive when the PSAP is busy and a subset of them are NG-ACN calls, a 429 PSAP might choose to store the information and reject the calls, 430 since the IVS will receive confirmation that the information has been 431 successfully received; a PSAP could also choose to include a message 432 stating that it is aware of the incident and responders are on the 433 way; a PSAP could call the vehicle back when a call taker is 434 available). 436 The migration of origination devices and networks, PSAPs, emergency 437 services networks, and other telephony environments to next- 438 generation provides enhanced interoperability and functionality, 439 especially for emergency calls carrying additional data such as 440 vehicle crash data. (In the U.S., a network specifically for 441 emergency responders is being developed. This network, FirstNet, 442 will be next-generation from the start, enhancing the ability for 443 data exchange between PSAPs and responders.) 445 NG-ACN calls can be recognized as originating from a vehicle, routed 446 to a PSAP prepared both technically and operationally to handle such 447 calls, and the vehicle-determined location and crash data made 448 available to the call taker simultaneously with the call appearance. 449 The PSAP can take advantage of enhanced functionality, including the 450 ability to request the vehicle to take an action, such as sending an 451 updated set of data, converying a message to the occupants, flashing 452 lights, unlocking doors, etc. 454 Vehicle manufacturers using the TSP model can choose to take 455 advantage of the same mechanism to carry telematics data and requests 456 and responses between the vehicle and the TSP for both emergency and 457 non-emergency calls as are used for the interface with the PSAP. 459 A next-generation IVS establishes a next-generation emergency call 460 (see [RFC6443] and [RFC6881]), with an initial INVITE containing a 461 Request-URI indicating an ACN type of emergency call and Call-Info 462 header fields indicating that both vehicle crash and capabilities 463 data are included; the IVS typically does not perform routing or 464 location queries but relies on the carrier for this. 466 [I-D.ietf-ecrit-ecall] registers new service URN children within the 467 "sos" subservice. These URNs request NG-ACN resources, and 468 differentiate between manually and automatically triggered NG-ACN 469 calls (which might be subject to different treatment depending on 470 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 471 are "urn:service:sos.ecall.automatic" and 472 "urn:service:sos.ecall.manual". The same service URNs are used for 473 ACN as for eCall since in any region only one of these is supported, 474 making a distinction unnecessary. (Further, PSAP equipment might 475 support multiple data formats, allowing a PSAP to handle a vehicle 476 that erroneously sent the wrong data object.) 477 Note that in North America, routing queries performed by clients 478 outside of an ESInet typically treat all sub-services of "sos" 479 identically to "sos" with no sub-service. However, the Request-URI 480 header field retains the full sub-service; route and handling 481 decisions within an ESInet or PSAP can take the sub-service into 482 account. For example, in a region with multiple cooperating PSAPs, 483 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 484 one that specializes in vehicle-related incidents. 486 Migration of the three architectural models to next-generation (all- 487 IP) is described below. 489 In the TSP model, the IVS transmits crash and location data to the 490 TSP either by re-using the mechanisms and data objects described in 491 this document, or using a proprietary mechanism. In an emergency, 492 the TSP bridges in the PSAP and the TSP transmits crash and other 493 data to the PSAP using the mechanisms and data objects described in 494 this document. There is a three-way call between the vehicle, the 495 TSP, and the PSAP, allowing communication between the PSAP call 496 taker, the TSP call taker, and the vehicle occupants (who might be 497 unconscious). The TSP relays PSAP requests and vehicle responses. 499 proprietary 500 ///----\\\ or standard +------+ standard +------+ 501 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 502 \\\----/// crash + other data +------+ crash + other data +------+ 504 Figure 4: Next-Generation TSP Model 506 The vehicle manufacturer and the TSP can choose to use the same 507 mechanisms and data objects on the left call leg in Figure 4 as on 508 the right. (Note that the TSP model can be more difficult when the 509 vehicle is in a different country than the TSP (e.g., a US resident 510 driving in Canada) because of the additional complexity in choosing 511 the correct PSAP based on vehicle location performed by a TSP in a 512 different country.) 514 In the direct model, the IVS communicates crash data to the PSAP 515 directly using the mechanisms and data objects described in this 516 document. 518 ///----\\\ NG emergency call +------+ 519 ||| IVS |||----------------------------------------->+ PSAP | 520 \\\----/// crash + other data +------+ 522 Figure 5: Next-Generation Direct Model 524 In the paired model, the IVS uses a Bluetooth link to a previously- 525 paired handset to establish an emergency call with the PSAP; it is 526 unclear what facilities are or will be available for transmitting 527 crash data through the Bluetooth link to the handset for inclusion in 528 an NG emergency call. Hence, manufacturers that use the paired model 529 for legacy calls might choose to adopt either the direct or TSP 530 models for next-generation calls. 532 +---+ 533 ///----\\\ (undefined) | H | standard +------+ 534 ||| IVS |||------------------>| S +------------------->+ PSAP | 535 \\\----/// (undefined) +---+ crash + other data +------+ 537 Figure 6: Next-Generation Paired Model 539 If the call is routed to a PSAP that is not capable of processing the 540 vehicle data, the PSAP ignores (or does not receive) the vehicle 541 data. This is detectable by the IVS or TSP when the status response 542 to the INVITE (e.g., 200 OK) lacks a metadata/control structure 543 acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or 544 TSP then proceeds as it would for a CS-ACN call (e.g., verbal 545 conveyance of data) 547 6. Vehicle Data 549 The Association of Public-Safety Communications Officials (APCO) and 550 the National Emergency Number Association (NENA) have jointly 551 developed a standardized set of incident-related vehicle data for ACN 552 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 553 is often referred to as crash data although it is applicable in 554 incidents other than crashes. 556 VEDS provides a standard data set for the transmission, exchange, and 557 interpretation of vehicle-related data. A standard data format 558 allows the data to be generated by an IVS or TSP and interpreted by 559 PSAPs, emergency responders, and medical facilities. It includes 560 incident-related information such as airbag deployment, location and 561 compass orientation of the vehicle, spatial orientation of the 562 vehicle (e.g., upright, on its side or roof or a bumper), various 563 sensor data that can indicate the potential severity of the crash and 564 the likelihood of severe injuries to the vehicle occupants, etc. 565 This data better informs the PSAP and emergency responders as to the 566 type of response that might be needed. Some of this information has 567 been included in U.S. government guidelines for field triage of 568 injured patients [triage-2008] [triage-2011]. These guidelines are 569 designed to help responders identify the potential existence of 570 severe internal injuries and to make critical decisions about how and 571 where a patient needs to be transported. 573 VEDS is an XML structure (see [VEDS]) transported in SIP using the 574 'application/EmergencyCallData.VEDS+xml' MIME media type. 576 If new data blocks are needed (e.g., in other regions or for enhanced 577 data), the steps required during standardization are briefly 578 summarized below: 580 o A set of data is standardized by an SDO or appropriate 581 organization 582 o A MIME media type for the crash data set is registered with IANA 584 * If the data is specifically for use in emergency calling, the 585 MIME media type is normally under the 'application' type with a 586 subtype starting with 'EmergencyCallData.' 587 * If the data format is XML, then by convention the name has a 588 suffix of '+xml' 589 o The item is registered in the Emergency Call Data Types registry, 590 as defined in Section 11.1.9 of [RFC7852] 592 * For emergency-call-specific formats, the registered name is the 593 root of the MIME media type (not including the 594 'EmergencyCallData' prefix and any suffix such as '+xml') as 595 described in Section 4.1 of [RFC7852]. 596 o A new SIP INFO package is registered that permits carrying the new 597 media type, the metadata/control object (defined in 598 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 599 objects, in SIP INFO requests. 601 7. Data Transport 603 [RFC7852] establishes a general mechanism for including blocks of 604 data within a SIP emergency call. This document makes use of that 605 mechanism. This document also registers a SIP INFO package (in 606 Section 14.7) to enable NG-ACN related data blocks to be carried in 607 SIP INFO requests (per [RFC6086], new SIP INFO method usages require 608 the definition of a SIP INFO package). 610 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 611 the Association of Public-Safety Communications Officials (APCO) and 612 the National Emergency Number Association (NENA) [VEDS]. It is 613 carried in a body part with MIME media type 'application/ 614 EmergencyCallData.VEDS+xml'. 616 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 617 by including it as a body part of a SIP message per [RFC7852]. The 618 body part is identified by its MIME media type ('application/ 619 emergencyCallData.VEDS+xml') in the Content-Type header field of the 620 body part. The body part is assigned a unique identifier which is 621 listed in a Content-ID header field in the body part. The SIP 622 message is marked as containing the VEDS data by adding (or appending 623 to) a Call-Info header field at the top level of the SIP message. 624 This Call-Info header field contains a CID URL referencing the body 625 part's unique identifier, and a 'purpose' parameter identifying the 626 data as a VEDS data block per the Emergency Call Additional Data 627 Types registry entry; the 'purpose' parameter's value is 628 'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO 629 request by using the SIP INFO package defined in Section 14.7. 631 A PSAP or IVS transmits a metadata/control object (see 632 [I-D.ietf-ecrit-ecall]) by including it in a SIP message as a MIME 633 body part per [RFC7852]. The body part is identified by its MIME 634 media type ('application/emergencyCallData.control+xml') in the 635 Content-Type header field of the body part. The body part is 636 assigned a unique identifier which is listed in a Content-ID header 637 field in the body part. The SIP message is marked as containing the 638 metadata/control block by adding (or appending to) a Call-Info header 639 field at the top level of the SIP message. This Call-Info header 640 field contains a CID URL referencing the body part's unique 641 identifier, and a 'purpose' parameter identifying the data as a 642 metadata/control block per the Emergency Call Additional Data Types 643 registry entry; the 'purpose' parameter's value is 644 'emergencyCallData.control'. A metadata/control object is carried in 645 a SIP INFO request by using the SIP INFO package defined in 646 Section 14.7. 648 A body part containing a VEDS or metadata/control object has a 649 Content-Disposition header field value containing "By-Reference" and 650 is always enclosed in a multipart body part (even if it would 651 otherwise be the only body part in the SIP message), since as of the 652 date of this document, the use of Content-ID as a SIP header field is 653 not defined (while it is defined for use as a MIME header field). 655 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 656 initial INVITE a VEDS data block and a metadata/control object 657 informing the PSAP of its capabilities. The VEDS and metadata/ 658 control body parts (and PIDF-LO) have a Content-Disposition header 659 field with the value "By-Reference; handling=optional". Specifying 660 handling=optional prevents the INVITE from being rejected if it is 661 processed by a legacy element (e.g., a gateway between SIP and 662 circuit-switched environments) that does not understand the VEDS or 663 metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ 664 control object acknowledging receipt of the VEDS data and includes it 665 in the SIP final response to the INVITE. The metadata/control object 666 is not included in provisional (e.g., 180) responses. 668 If the IVS receives an acknowledgment for a VEDS data object with 669 received=false, this indicates that the PSAP was unable to properly 670 decode or process the VEDS. The IVS action is not defined (e.g., it 671 might only log an error). Since the PSAP is able to request an 672 updated VEDS during the call, if an initial VEDS is unsatisfactory in 673 any way, the PSAP can choose to request another one. 675 A PSAP can request that the vehicle send an updated VEDS data block 676 during a call. To do so, the PSAP creates a metadata/control object 677 requesting VEDS data and includes it as a body part of a SIP INFO 678 request sent within the dialog. The IVS then includes an updated 679 VEDS data object as a body part of a SIP INFO request and sends it 680 within the dialog. If the IVS is unable to send the VEDS, it instead 681 sends a metadata/control object acknowledging the request with the 682 'success' parameter set to 'false' and a 'reason' parameter (and 683 optionally a 'details' parameter) indicating why the request cannot 684 be accomplished. Per [RFC6086], metadata/control objects and VEDS 685 data are sent using the SIP INFO package defined in Section 14.7. In 686 addition, to align with the way a VEDS or metadata/control block is 687 transmitted in a SIP message other than a SIP INFO request, one or 688 more Call-Info header fields are included in the SIP INFO request 689 referencing the VEDS or metadata/control block. See Section 14.7 for 690 more information on the use of SIP INFO requests within NG-ACN calls. 692 Any metadata/control object sent by a PSAP can request that the 693 vehicle perform an action (such as sending a data block, flashing 694 lights, providing a camera feed, etc.) The vehicle sends an 695 acknowledgement for any request other than a successfully executed 696 send-data action. Multiple requests with the same 'action' value 697 MUST be sent in separate body parts (to avoid any ambiguity in the 698 acknowledgement). 700 If the IVS is aware that VEDS data it sent previously has changed, it 701 MAY send an unsolicited VEDS in any convenient SIP message, including 702 a SIP INFO request during the call. The PSAP sends an acknowledgment 703 for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS 704 in a SIP INFO request, the acknowledgment is sent in a new SP INFO 705 request, otherwise it is sent in the reply to the SIP request 706 containing the VEDS). 708 8. Call Setup 710 A next-generation In-Vehicle System (IVS) initiating an NG-ACN call 711 sends a SIP INVITE request using one of the SOS sub-services 712 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI. This 713 SIP INVITE request includes standard sets of both crash and 714 capabilities data as described in Section 7. 716 Entities along the path between the vehicle and the PSAP are able to 717 identify the call as an ACN call and handle it appropriately. The 718 PSAP is able to identify the crash and capabilities data included in 719 the SIP INVITE request by examining the Call-Info header fields for 720 'purpose' parameters whose values start with 'EmergencyCallData.' 721 The PSAP is able to access the data it is capable of handling and is 722 interested in by checking the 'purpose' parameter values. 724 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 725 up and other normative requirements with the exception that in this 726 document, support for the eCall MSD is OPTIONAL and support for VEDS 727 in REQUIRED. This document also adds new attribute values to the 728 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 730 9. New Metadata/Control Values 732 This document adds new attribute values to the metadata/control 733 structure defined in [I-D.ietf-ecrit-ecall]. 735 In addition to the base usage from the PSAP to the IVS to 736 acknowledge receipt of crash data, the element is also 737 contained in a metadata/control block sent by the IVS to the PSAP. 738 This is used by the IVS to acknowledge receipt of a request by the 739 PSAP and indicate if the request was carried out when that request 740 would not otherwise be acknowledged (if the PSAP requests the 741 vehicle to send data and the vehicle does so, the data serves as a 742 success acknowledgement). 743 The element is used in a metadata/control block 744 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 745 inform the PSAP of the vehicle capabilities. Child elements 746 contain all actions and data types supported by the vehicle and 747 all available lamps (lights) and cameras. 748 New request values are added to the element to enable 749 the PSAP to request the vehicle to perform actions. 751 Mandatory Actions (the IVS and the PSAP MUST support): 753 o Transmit data object (VEDS MUST be supported; MSD MAY be 754 supported) 756 Optional Actions (the IVS and the PSAP MAY support): 758 o Play and/or display static (pre-defined) message 759 o Speak/display dynamic text (text supplied in action) 760 o Flash or turn on or off a lamp (light) 761 o Honk horn 762 o Lock or unlock doors 763 o Enable a camera 764 The element indicates the object being acknowledged (i.e., a 765 data object or a metadata/control block containing 766 elements), and reports success or failure. 768 The element has child elements indicating 769 the actions supported by the IVS. 771 The element contains attributes to indicate the request and 772 to supply any needed information, and MAY contain a child 773 element to contain the text for a dynamic message. The 'action' 774 attribute is mandatory and indicates the specific action. 775 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 776 allowed values; this document adds new values to that registry in 777 Table 2. 779 Per [I-D.ietf-ecrit-ecall], the PSAP sends a metadata/control block 780 in response to the VEDS data sent by the IVS in SIP requests other 781 than INFO (e.g., the INVITE). This metadata/control block is sent in 782 the SIP response to the request (e.g., the INVITE response). When 783 the PSAP needs to send a control block that is not an immediate 784 response to a VEDS or other data sent by the IVS, the metadata/ 785 control block is transmitted from the PSAP to the IVS in a SIP INFO 786 request within the established dialog. The IVS sends the requested 787 data (e.g., the VEDS) or an acknowledgment (for requests other than 788 to send data or to indicate an inability to send the requested data) 789 in a new SIP INFO request. This mechanism flexibly allows the PSAP 790 to send metadata/control data to the IVS and the IVS to respond. If 791 a metadata/control block sent in a SIP response message requests the 792 IVS to send a new VEDS or other data block, or to perform an action 793 other than sending data, the IVS sends the requested data or an 794 acknowledgment regarding the action in a SIP INFO request within the 795 dialog. 797 9.1. New values for the 'action' attribute' 799 The following new "action" values are defined: 801 msg-static displays or plays a predefined message (translated as 802 appropriate for the language of the vehicle's interface). A 803 registry is created in Section 14.4 for messages and their IDs. 804 Vehicles include the highest registered message in their 805 element to indicate support for all messages up to 806 and including the indicated value. A registry of message 807 identification values is defined in Section 14.4. There is only 808 one static message initially defined (listed in Table 3). Because 809 all compliant vehicles are expected to support all static messages 810 translated into all languages supported by the vehicle, it is 811 important to limit the number of such messages. Therefore, this 812 registry operates under "Specification Required" rules as defined 813 in [RFC5226], which require a stable, public document and implies 814 expert review of the publication. 816 msg-dynamic displays or speaks (via text-to-speech) a dynamic 817 message contained in a child element within the request. 819 honk sounds the horn. 821 lamp turns a lamp (light) on, off, or flashes. The lamp is 822 identified by a lamp ID token contained in an "element-id" 823 attribute of the request. The desired state of the lamp is either 824 "on", "off", or "flash" as indicated in a "requested-state" 825 attribute. The duration of the lamp's requested state is 826 specified in a "persistence" attribute. A registry of lamp 827 identification values is defined in Section 14.5. The initial 828 values (listed in Table 4) are head, interior, fog-front, fog- 829 rear, brake, brake-center, position-front, position-rear, turn- 830 left, turn-right, and hazard. 832 enable-camera adds a one-way media stream (established via SIP re- 833 INVITE sent by the vehicle) to enable the PSAP call taker to view 834 a feed from a camera. A registry of camera identification values 835 is defined in Section 14.6. The initial values (listed in 836 Table 5) are backup, left-rear, right-rear, forward, rear-wide, 837 lane, interior, night-front, night-rear, night-left, and night- 838 right. 840 door-lock locks or unlocks all door locks. A "requested-state" 841 attribute contains either "locked" or "unlocked" to indicate if 842 the doors are to be locked or unlocked. 844 Note that there is no 'request' action to play dynamic media (such as 845 an audio message). The PSAP can send a SIP re-INVITE to establish a 846 one-way media stream for this purpose. 848 9.2. Request Example 849 850 854 855 857 858 859 Remain calm. Help is on the way. 860 862 864 Figure 7: Request Example 866 9.3. The element 868 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 869 PSAP to acknowledge the MSD. Here, the element is also 870 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 871 to acknowledge receipt of a element that requested the IVS 872 to perform an action other than transmitting a data object (e.g., a 873 request to display a message would be acknowledged, but a request to 874 transmit VEDS data would not result in a separate element being 875 sent, since the data object itself serves as acknowledgment.) An 876 element sent by an IVS references the unique ID of the 877 metadata/control object containing the request(s) and indicates 878 whether the request was successfully performed, and if not, 879 optionally includes an explanation. 881 9.3.1. Ack Examples 882 883 887 888 889 891 893 895 Figure 8: Ack Example from IVS to PSAP 897 9.4. The element 899 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 900 the IVS to indicate its capabilities to the PSAP. 902 The element contains a child element per 903 action supported by the vehicle. The vehicle MUST support sending 904 the VEDS data object and so includes at a minimum a child 905 element with the 'action' attribute set to "send-data" and the 906 'supported-values' attribute containing all data blocks supported by 907 the IVS, which MUST include 'VEDS'. All other actions are OPTIONAL. 909 If the "msg-static" action is supported, a child element 910 with the 'action' attribute set to "msg-static" is included, with the 911 'int-id' attribute set to the highest supported static message 912 supported by the vehicle. A registry is created in Section 14.4 to 913 map 'int-id' values to static text messages. By sending the highest 914 supported static message number in its element, the 915 vehicle indicates its support for all static messages in the registry 916 up to and including that value. 918 If the "lamp" action is supported, a child element with the 919 'action' attribute set to "lamp" is included, with the 'supported- 920 values' attribute set to all supported lamp IDs. A registry is 921 created in Section 14.5 to contain lamp ID values. 923 If the "enable-camera" action is supported, a child element 924 with the 'action' attribute set to "enable-camera" is included, with 925 the 'supported-values' attribute set to all supported camera IDs. A 926 registry is created in Section 14.6 to contain camera ID values. 928 9.4.1. Capabilities Example 930 931 935 936 937 941 942 943 944 946 947 949 951 Figure 9: Capabilities Example 953 10. Test Calls 955 An NG-ACN test call is a call that is recognized and treated to some 956 extent as an NG-ACN call but not given emergency call treatment and 957 not handled by a call taker. The specific handling of test NG-ACN 958 calls is not itself standardized; the test call facility is intended 959 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 960 successfully established with voice and/or other media communication. 961 The IVS might also be able to verify that the crash data was 962 successfully received. 964 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 965 ability to utilize test call functionality from Section 15 of 966 [RFC6881]. A service URN starting with "test." indicates a test 967 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 968 for test calls. 970 MNOs, emergency authorities, ESInets, and PSAPs determine how to 971 treat a vehicle call requesting the "test" service URN so that the 972 desired functionality is tested, but this is outside the scope of 973 this document. (One possibility is that MNOs route such calls as 974 non-emergency calls to an ESInet, which routes them to a PSAP that 975 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 976 data acknowledgment, and plays an audio clip (for example, saying 977 that the call reached an appropriate PSAP and the vehicle data was 978 successfully processed) in addition to supporting media loopback per 979 [RFC6881]). 981 Note that since test calls are placed using "test" as the parent 982 service URN and "sos" as a child, such calls are not treated as an 983 emergency call and so some functionality might not apply (such as 984 preemption or service availability for devices lacking service ("non- 985 service-initialized" or "NSI" devices) if those are available for 986 emergency calls). 988 11. Example 990 Figure 10 shows an NG-ACN call routing. The mobile network operator 991 (MNO) routes the call to an Emergency services IP Network (ESInet), 992 as for any emergency call. The ESInet routes the call to an 993 appropriate NG-ACN-capable PSAP (using location information and the 994 fact that that it is an NG-ACN call). The call is processed by the 995 Emergency Services Routing Proxy (ESRP), as the entry point to the 996 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 997 PSAP, where the call is received by a call taker. (In deployments 998 where there is no ESInet, the MNO itself routes the call directly to 999 an appropriate NG-ACN-capable PSAP.) 1001 +---------------------------------------+ 1002 | | 1003 +------------+ | +-------+ | 1004 | | | | PSAP2 | | 1005 | | | +-------+ | 1006 | Originating| | | 1007 | Mobile | | +------+ +-------+ | 1008 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1009 | | | +------+ +-------+ | 1010 | | | | 1011 +------------+ | +-------+ | 1012 | | PSAP3 | | 1013 | +-------+ | 1014 | | 1015 | | 1016 | | 1017 | ESInet | 1018 +---------------------------------------+ 1020 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1022 The example, shown in Figure 11, illustrates a SIP emergency call 1023 INVITE request with location information (a PIDF-LO), VEDS crash data 1024 (a VEDS data block), and capabilities data (a metadata/control block 1025 with extensions defined in this document) included in the SIP INVITE 1026 request message. The INVITE has a request URI containing the 1027 'urn:service:sos.ecall.automatic' service URN. 1029 The example VEDS data structure shows information about a crashed 1030 vehicle. The example communicates that the car is a model year 2015 1031 Saab 9-5 (a car which does not exist). The front airbag deployed as 1032 a consequence of the crash. The 'VehicleBodyCategoryCode' indicates 1033 that the crashed vehicle is a passenger car (the code is set to 1034 '101') and that it is not a convertible (the 'ConvertibleIndicator' 1035 value is set to 'false'). 1037 The 'VehicleCrashPulse' element provides further information about 1038 the crash, namely that the force of impact based on the change in 1039 velocity over the duration of the crash pulse was 100 MPH. The 1040 principal direction of the force of the impact is set to '12' (which 1041 refers to 12 O'Clock, corresponding to a frontal collision). This 1042 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1043 element. 1045 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1046 quarter turns in concert with a rollover expressed as a number; in 1047 our case 1. 1049 No roll bar was deployed, as indicated in 1050 'VehicleRollbarDeployedIndicator' being set to 'false'. 1052 Next, there is information indicating seatbelt and seat sensor data 1053 for individual seat positions in the vehicle. In our example, 1054 information from the driver seat is available (value '1' in the 1055 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1056 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1057 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1058 and the seat sensor determined that the seat was occupied 1059 ('VehicleSeatOccupiedIndicator' element). 1061 Finally, information about the weight of the vehicle, which is 600 1062 kilogram in our example. 1064 In addition to the information about the vehicle, further indications 1065 are provided, namely the presence of fuel leakage 1066 ('FuelLeakingIndicator' element), an indication whether the vehicle 1067 was subjected to multiple impacts ('MultipleImpactsIndicator' 1068 element), the orientation of the vehicle at final rest 1069 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1070 that there are no parts of the vehicle on fire (the 1071 'VehicleFireIndicator' element). 1073 INVITE urn:service:sos.ecall.automatic SIP/2.0 1074 To: urn:service:sos.ecall.automatic 1075 From: ;tag=9fxced76sl 1076 Call-ID: 3848276298220188511@atlanta.example.com 1077 Geolocation: 1078 Geolocation-Routing: no 1079 Call-Info: ; 1080 purpose=EmergencyCallData.VEDS 1081 Call-Info: ; 1082 purpose=emergencyCallData.control 1083 Accept: application/sdp, application/pidf+xml, 1084 application/emergencyCallData.control+xml 1085 Recv-Info: emergencyCallData.eCall 1086 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1087 SUBSCRIBE, NOTIFY, UPDATE 1088 CSeq: 31862 INVITE 1089 Content-Type: multipart/mixed; boundary=boundary1 1090 Content-Length: ... 1092 --boundary1 1093 Content-Type: application/sdp 1095 ...Session Description Protocol (SDP) goes here 1097 --boundary1 1098 Content-Type: application/pidf+xml 1099 Content-ID: 1100 Content-Disposition: by-reference;handling=optional 1102 1103 1111 1112 1113 1114 1115 -34.407 150.883 1116 1117 1118 278 1119 1120 1121 1122 1123 gps 1124 1125 2012-04-5T10:18:29Z 1126 1M8GDM9A_KP042788 1127 1128 1130 --boundary1 1131 Content-Type: application/EmergencyCallData.VEDS+xml 1132 Content-ID: <1234567890@atlanta.example.com> 1133 Content-Disposition: by-reference;handling=optional 1135 1136 1140 1141 1142 Saab 1143 1144 1145 9-5 1146 1147 1149 2015 1150 1151 1152 FRONT 1153 true 1154 1155 1156 false 1157 MAIN 1158 1160 101 1161 1162 1163 1164 1166 100 1167 1168 1170 MPH 1171 1172 12 1173 1174 1 1175 1176 1177 false 1178 1179 1180 1 1181 1182 true 1183 1184 true 1185 1186 true 1187 1188 1189 1191 1193 600 1194 1195 1197 kilogram 1198 1199 1200 1201 true 1202 false 1203 true 1204 Driver 1205 1206 false 1207 1208 1210 --boundary1 1211 Content-Type: application/emergencyCallData.control+xml 1212 Content-ID: <1234567892@atlanta.example.com> 1213 Content-Disposition: by-reference;handling=optional 1214 1215 1219 1220 1221 1225 1226 1227 1228 1230 1231 1233 1235 --boundary1-- 1237 Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call 1239 12. Security Considerations 1241 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1242 the security considerations described there and in [RFC5069] apply 1243 here. Implementors are cautioned to read and understand the 1244 discussion in those documents. 1246 As with emergency service systems where location data is supplied or 1247 determined with the assistance of an end host, there is the 1248 possibility that that location is incorrect, either intentially 1249 (e.g., in a denial of service attack against the emergency services 1250 infrastructure) or due to a malfunctioning device. The reader is 1251 referred to [RFC7378] for a discussion of some of these 1252 vulnerabilities. 1254 In addition to the security considerations discussion specific to the 1255 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1256 MAY decline to carry out any requested action (e.g., if the vehicle 1257 requires but is unable to verify the certificate used to sign the 1258 request). The vehicle MAY use any value in the reason registry to 1259 indicate why it did not take an action (e.g., the generic "unable" or 1260 the more specific "security-failure"). Because some actions carry 1261 more potential risk than others (e.g., unlocking a door versus 1262 flashing lights), vehicle policy MAY decline to carry out some 1263 requests in some circumstances (e.g., declining a request to unlock 1264 doors, send an updated VEDS, or enable a camera received in a 1265 vehicle-terminated call while carrying out such requests received in 1266 a vehicle-initiated emergency call). 1268 13. Privacy Considerations 1270 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1271 builds on [RFC7852], the data structures specified there, and the 1272 corresponding privacy considerations discussed there, apply here as 1273 well. The VEDS data structure contains optional elements that can 1274 carry identifying and personal information, both about the vehicle 1275 and about the owner, as well as location information, and so needs to 1276 be protected against unauthorized disclosure, as discussed in 1277 [RFC7852]. Local regulations may impose additional privacy 1278 protection requirements. 1280 The additional functionality enabled by this document, such as access 1281 to vehicle camera streams, carries a burden of protection and so 1282 implementations need to be careful that access is only provided 1283 within the context of an emergency call or to an emergency services 1284 provider (e.g., by verifying that the request for camera access is 1285 signed by a certificate issued by an emergency services registrar). 1287 14. IANA Considerations 1289 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1290 media type, and adds "VEDS" to the Emergency Call Data Types 1291 registry. This document adds to and creates sub-registries in the 1292 "Emergency Call Metadata/Control Data" registry created in 1293 [I-D.ietf-ecrit-ecall]. This document registers a new SIP INFO 1294 package. 1296 14.1. MIME Media Type Registration for 'application/ 1297 EmergencyCall.VEDS+xml' 1299 This specification requests the registration of a new MIME media type 1300 according to the procedures of RFC 6838 [RFC6838] and guidelines in 1301 RFC 7303 [RFC7303]. 1303 MIME media type name: application 1305 MIME subtype name: EmergencyCallData.VEDS+xml 1307 Mandatory parameters: none 1309 Optional parameters: charset 1310 Indicates the character encoding of enclosed XML. 1312 Encoding considerations: Uses XML, which can employ 8-bit 1313 characters, depending on the character encoding used. See 1314 Section 3.2 of RFC 7303 [RFC7303]. 1316 Security considerations: 1318 This media type is designed to carry vehicle crash data during 1319 an emergency call. 1321 This data can contain personal information including vehicle 1322 VIN, location, direction, etc. Appropriate precautions need to 1323 be taken to limit unauthorized access, inappropriate disclosure 1324 to third parties, and eavesdropping of this information. 1325 Please refer to Section 9 and Section 10 of [RFC7852] for more 1326 information. 1328 When this media type is contained in a signed or encrypted body 1329 part, the enclosing multipart (e.g., multipart/signed or 1330 multipart/encrypted) has the same Content-ID as the data part. 1331 This allows an entity to identify and access the data blocks it 1332 is interested in without having to dive deeply into the message 1333 structure or decrypt parts it is not interested in. (The 1334 'purpose' parameter in a Call-Info header field identifies the 1335 data, and the CID URL points to the data block in the body, 1336 which has a matching Content-ID body part header field). 1338 Interoperability considerations: None 1340 Published specification: [VEDS] 1342 Applications which use this media type: Emergency Services 1344 Additional information: None 1346 Magic Number: None 1348 File Extension: .xml 1350 Macintosh file type code: 'TEXT' 1352 Persons and email addresses for further information: Randall 1353 Gellens rg+ietf@randy.pensive.org; Hannes Tschofenig, 1354 Hannes.Tschofenig@gmx.net 1356 Intended usage: LIMITED USE 1357 Author: This specification is a work item of the IETF ECRIT 1358 working group, with mailing list address . 1360 Change controller: The IESG 1362 14.2. Registration of the 'VEDS' entry in the Emergency Call Data Types 1363 registry 1365 This specification requests IANA to add the 'VEDS' entry to the 1366 Emergency Call Data Types registry, with a reference to this 1367 document; the 'Data About' value is 'The Call'. The Emergency Call 1368 Data types registry was established by [RFC7852]. 1370 14.3. New Action Values 1372 This document adds new values for the 'action' attribute of the 1373 element in the "Emergency Call Action" registry created by 1374 [I-D.ietf-ecrit-ecall]. 1376 +---------------+-------------------------------------+ 1377 | Name | Description | 1378 +---------------+-------------------------------------+ 1379 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1380 | | | 1381 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1382 | | | 1383 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1384 | | | 1385 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1386 | | | 1387 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1388 | | | 1389 | door-lock | Section 9.1 of [TBD: THIS DOCUMENT] | 1390 +---------------+-------------------------------------+ 1392 Table 2: Emergency Call Action Registry New Values 1394 14.4. Emergency Call Static Message Registry 1396 This document creates a new sub-registry called "Emergency Call 1397 Static Message" in the "Emergency Call Metadata/Control Data" 1398 registry established by [I-D.ietf-ecrit-ecall]. Because all 1399 compliant vehicles are expected to support all static messages 1400 translated into all languages supported by the vehicle, it is 1401 important to limit the number of such messages. As defined in 1402 [RFC5226], this registry operates under "Specification Required" 1403 rules, which require a stable, public document and implies expert 1404 review of the publication. The expert should determine that the 1405 document has been published by an appropriate emergency services 1406 organization (e.g., NENA, EENA, APCO) or by the IETF with input from 1407 an emergency services organization, and that the proposed message is 1408 sufficiently distinguishable from other messages. 1410 The contents of this registry are: 1412 ID: An integer identifier to be used in the 'int-id' attribute of a 1413 metadata/control element. 1415 Message: The text of the message. Messages are listed in the 1416 registry in English; vehicles are expected to implement 1417 translations into languages supported by the vehicle. 1419 When new messages are added to the registry, the message text is 1420 determined by the registrant; IANA assigns the IDs. Each message is 1421 assigned a consecutive integer value as its ID. This allows an IVS 1422 to indicate by a single integer value that it supports all messages 1423 with that value or lower. 1425 The initial set of values is listed in Table 3. 1427 +----+--------------------------------------------------------------+ 1428 | ID | Message | 1429 +----+--------------------------------------------------------------+ 1430 | 1 | Emergency services has received your information and | 1431 | | location, but cannot speak with you right now. We will get | 1432 | | help to you as soon as possible. | 1433 +----+--------------------------------------------------------------+ 1435 Table 3: Emergency Call Static Message Registry Initial Values 1437 14.5. Emergency Call Vehicle Lamp ID Registry 1439 This document creates a new sub-registry called "Emergency Call 1440 Vehicle Lamp ID" in the "Emergency Call Metadata/Control Data" 1441 registry established by [I-D.ietf-ecrit-ecall]. This new sub- 1442 registry uniquely identifies the names of automotive lamps (lights). 1443 As defined in [RFC5226], this registry operates under "Expert Review" 1444 rules. The expert should determine that the proposed lamp name is 1445 clearly understandable and is sufficiently distinguishable from other 1446 lamp names. 1448 The contents of this registry are: 1450 Name: The identifier to be used in the 'element-id' attribute of a 1451 metadata/control element. 1453 Description: A description of the lamp (light). 1455 The initial set of values is listed in Table 4. 1457 +----------------+---------------------------------------------+ 1458 | Name | Description | 1459 +----------------+---------------------------------------------+ 1460 | head | The main lamps used to light the road ahead | 1461 | | | 1462 | interior | Interior lamp, often at the top center | 1463 | | | 1464 | fog-front | Front fog lamps | 1465 | | | 1466 | fog-rear | Rear fog lamps | 1467 | | | 1468 | brake | Brake indicator lamps | 1469 | | | 1470 | brake-center | Center High Mounted Stop Lamp | 1471 | | | 1472 | position-front | Front position/parking/standing lamps | 1473 | | | 1474 | position-rear | Rear position/parking/standing lamps | 1475 | | | 1476 | turn-left | Left turn/directional lamps | 1477 | | | 1478 | turn-right | Right turn/directional lamps | 1479 | | | 1480 | hazard | Hazard/four-way lamps | 1481 +----------------+---------------------------------------------+ 1483 Table 4: Emergency Call Lamp ID Registry Initial Values 1485 14.6. Emergency Call Vehicle Camera ID Registry 1487 This document creates a new sub-registry called "Emergency Call 1488 Vehicle Camera ID" in the "Emergency Call Metadata/Control Data" 1489 registry established by [I-D.ietf-ecrit-ecall]. This new sub- 1490 registry uniquely identifies automotive cameras. As defined in 1491 [RFC5226], this registry operates under "Expert Review" rules. The 1492 expert should determine that the proposed camera name is clearly 1493 understandable and is sufficiently distinguishable from other camera 1494 names. 1496 The contents of this registry are: 1498 Name: The identifier to be used in the 'element-id' attribute of a 1499 control element. 1501 Description: A description of the camera. 1503 The initial set of values is listed in Table 5. 1505 +-------------+-----------------------------------------------------+ 1506 | Name | Description | 1507 +-------------+-----------------------------------------------------+ 1508 | backup | Shows what is behind the vehicle, e.g., often used | 1509 | | for driver display when the vehicle is in reverse. | 1510 | | Also known as rearview, reverse, rear visibility, | 1511 | | etc. | 1512 | | | 1513 | left-rear | Shows view to the left and behind (e.g., left side | 1514 | | rear-view mirror or blind spot view) | 1515 | | | 1516 | right-rear | Shows view to the right and behind (e.g., right | 1517 | | side rear-view mirror or blind spot view) | 1518 | | | 1519 | forward | Shows what is in front of the vehicle | 1520 | | | 1521 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1522 | | collision detection systems), separate from backup | 1523 | | view | 1524 | | | 1525 | lane | Used by systems to identify road lane and/or | 1526 | | monitor vehicle's position within lane | 1527 | | | 1528 | interior | Shows the interior (e.g., driver) | 1529 | | | 1530 | night-front | Night-vision view of what is in front of the | 1531 | | vehicle | 1532 | | | 1533 | night-rear | Night-vision view of what is behind the vehicle | 1534 | | | 1535 | night-left | Night-vision view of what is to the left of the | 1536 | | vehicle | 1537 | | | 1538 | night-right | Night-vision view of what is to the right of the | 1539 | | vehicle | 1540 +-------------+-----------------------------------------------------+ 1542 Table 5: Emergency Call Vehicle Camera ID Registry Initial Values 1544 14.7. The emergencyCallData.eCall.VEDS SIP INFO package 1546 This document registers the 'emergencyCallData.eCall.VEDS' SIP INFO 1547 package. 1549 Both endpoints (the IVS and the PSAP equipment) include 1550 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 1551 [RFC6086] to indicate ability to receive SIP INFO messages carrying 1552 data as described here. 1554 Support for the 'emergencyCallData.eCall.VEDS' SIP INFO package 1555 indicates the ability to receive NG-ACN related body parts as 1556 specified in [TBD: THIS DOCUMENT]. 1558 A SIP INFO request message carrying data related to an emergency call 1559 as described in [TBD: THIS DOCUMENT] has an Info-Package header field 1560 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 1562 The requirements of Section 10 of [RFC6086] are addressed in the 1563 following sections. 1565 14.7.1. Overall Description 1567 This section describes "what type of information is carried in Info 1568 requests associated with the Info Package, and for what types of 1569 applications and functionalities UAs can use the Info Package." 1571 SIP INFO requests associated with the emergencyCallData.eCall.VEDS 1572 SIP INFO package carry data associated with emergency calls as 1573 defined in [TBD: THIS DOCUMENT]. The application is vehicle- 1574 initiated emergency calls established using SIP. The functionality 1575 is to carry vehicle data and metadata/control information between 1576 vehicles and PSAPs. Refer to [TBD: THIS DOCUMENT] for more 1577 information. 1579 14.7.2. Applicability 1581 This section describes "why the Info Package mechanism, rather than 1582 some other mechanism, has been chosen for the specific use-case...." 1584 The use of the SIP INFO method is based on an analysis of the 1585 requirements against the intent and effects of the INFO method versus 1586 other approaches (which included the SIP MESSAGE method, SIP OPTIONS 1587 method, SIP re-INVITE method, media plane transport, and non-SIP 1588 protocols). In particular, the transport of emergency call data 1589 blocks occurs within a SIP emergency dialog, per Section 7, and is 1590 normally carried in the initial INVITE request and its response; the 1591 use of the INFO method only occurs when emergency-call-related data 1592 needs to be sent mid-call. While the SIP MESSAGE method could be 1593 used, it is not tied to a SIP dialog as is the INFO method and thus 1594 might not be associated with the dialog. Both the SIP OPTIONS or re- 1595 INVITE methods could also be used, but is seen as less clean than the 1596 INFO method. The SIP SUBSCRIBE/NOTIFY method could be coerced into 1597 service, but the semantics are not a good fit, e.g., the subscribe/ 1598 notify mechanism provides one-way communication consisting of (often 1599 multiple) notifications from notifier to subscriber indicating that 1600 certain events in notifier have occurred, whereas what's needed here 1601 is two-way communication of data related to the emergency dialog. 1602 Use of the media plane mechanisms was discounted because the number 1603 of messages needing to be exchanged in a dialog is normally zero or 1604 very few, and the size of the data is likewise very small. The 1605 overhead caused by user plane setup (e.g., to use MSRP as transport) 1606 would be disproportionately large. 1608 Based on the analyses, the SIP INFO method was chosen to provide for 1609 mid-call data transport. 1611 14.7.3. Info Package Name 1613 The SIP INFO package name is emergencyCallData.eCall.VEDS 1615 14.7.4. Info Package Parameters 1617 None 1619 14.7.5. SIP Option-Tags 1621 None 1623 14.7.6. INFO Request Body Parts 1625 The body of an emergencyCallData.eCall.VEDS SIP INFO package is a 1626 multipart body which MAY contain zero or one application/ 1627 emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part, 1628 zero or more application/emergencyCallData.control+xml (containing a 1629 metadata/control object) parts, and zero or one application/ 1630 emergencyCallData.eCall.MSD+per (containing an MSD) part. At least 1631 one VEDS, MSD, or metadata/control body part is expected; the 1632 behavior upon receiving a SIP INFO request with none is undefined. 1634 The body parts are sent per [RFC6086], and in addition, to align with 1635 with how these body parts are sent in non-INFO messages, each 1636 associated body part is referenced by a Call-Info header field at the 1637 top level of the SIP message. The body part has a Content- 1638 Disposition header field set to "By-Reference". 1640 A VEDS or metadata/control block is always enclosed in a multipart 1641 body part (even if it would otherwise be the only body part in the 1642 SIP message), since as of the date of this document, the use of 1643 Content-ID as a SIP header field is not defined (while it is defined 1644 for use as a MIME header field). The innermost multipart that 1645 contains only body parts associated with the SIP INFO package has a 1646 Content-Disposition value of Info-Package. 1648 Service providers are not expected to add [RFC7852] Additional Data 1649 to SIP INFO requests. 1651 See [TBD: THIS DOCUMENT] for more information. 1653 14.7.7. Info Package Usage Restrictions 1655 Usage is limited to vehicle-initiated emergency calls as defined in 1656 [TBD: THIS DOCUMENT]. 1658 14.7.8. Rate of INFO Requests 1660 The SIP INFO request is used within an established emergency call 1661 dialog for the PSAP to request the IVS to send an updated data set, 1662 and for the IVS to send the requested data set. Because this is 1663 normally done only on manual request of the PSAP call taker (who 1664 suspects some aspect of the vehicle state has changed), the rate of 1665 SIP INFO requests associated with the emergencyCallData.eCall.VEDS 1666 SIP INFO package is normally quite low (most dialogs are likely to 1667 contain zero SIP INFO requests, while others can be expected to carry 1668 an occasional request). 1670 14.7.9. Info Package Security Considerations 1672 The MIME media type registations for the data blocks that can be 1673 carried using this SIP INFO package contains a discussion of the 1674 security and/or privacy considerations specific to that data block. 1675 The "Security Considerations" and "Privacy Considerations" sections 1676 of [TBD: THIS DOCUMENT] discuss security and privacy considerations 1677 of the data carried in vehicle-initiated emergency calls as described 1678 in that document. 1680 14.7.10. Implementation Details 1682 See [TBD: THIS DOCUMENT] for protocol details. 1684 14.7.11. Examples 1686 See [TBD: THIS DOCUMENT] for protocol examples. 1688 15. Acknowledgements 1690 We would like to thank Lena Chaponniere, Alissa Cooper, Stephen Edge, 1691 Christer Holmberg, Allison Mankin, and Dan Romascanu for their review 1692 and suggestions; Robert Sparks and Paul Kyzivat for their help with 1693 the SIP mechanisms; Michael Montag, Arnoud van Wijk, Ban Al-Bakri, 1694 Wes George, Gunnar Hellstrom, and Rex Buddenberg for their feedback; 1695 and Ulrich Dietz for his help with earlier versions of the original 1696 version of this document. 1698 16. Changes from Previous Versions 1700 RFC Editor: Please remove this section prior to publication. 1702 16.1. Changes from draft-ietf-18 to draft-ietf-19 1704 o Fixed various nits 1706 16.2. Changes from draft-ietf-17 to draft-ietf-18 1708 o Added additional text to "Rate of Info Requests" 1709 o Further corrected "content type" to "media type" 1711 16.3. Changes from draft-ietf-16 to draft-ietf-17 1713 o Clarified that an INFO request is expected to have at least one 1714 VEDS, MSD or metadata/control body part 1715 o Corrected "content type" to "media type" 1717 16.4. Changes from draft-ietf-14 to draft-ietf-15 1719 o Moved VEDS text from Introduction to new Vehicle Data section 1720 o Various clarifications and simplifications 1722 16.5. Changes from draft-ietf-13 to draft-ietf-14 1724 o Body parts now always sent enclosed in multipart (even if only 1725 body part in SIP message) and hence always have a Content- 1726 Disposition of By-Reference 1727 o Fixed typos. 1729 16.6. Changes from draft-ietf-11 to draft-ietf-13 1731 o Fixed typos 1733 16.7. Changes from draft-ietf-10 to draft-ietf-11 1735 o Clarifications suggested by Christer 1736 o Corrections to Content-Disposition text and examples as suggested 1737 by Paul Kyzivat 1738 o Clarifications to Content-Disposition text and examples to clarify 1739 that handling=optional is only used in the initial INVITE 1741 16.8. Changes from draft-ietf-09 to draft-ietf-10 1743 o Fixed errors in examples found by Dale in eCall draft 1744 o Removed enclosing sub-section of INFO package registration section 1745 o Added text per Christer and Dale's suggestions that the MSD and 1746 metadata/control blocks are sent in INFO with a Call-Info header 1747 field referencing them 1748 o Other text changes per comments received from Christer and Ivo 1749 against eCall draft. 1751 16.9. Changes from draft-ietf-08 to draft-ietf-09 1753 o Added INFO package registration for eCall.VEDS 1754 o Moved element and other extension points back to 1755 eCall document so that extension points are in base spec (and also 1756 to get XML schema to compile) 1757 o Text changes for clarification. 1759 16.10. Changes from draft-ietf-07 to draft-ietf-08 1761 o Moved much of the metadata/control object from 1762 [I-D.ietf-ecrit-ecall] to this document as extensions 1763 o Editorial clarifications and simplifications 1764 o Moved "Call Routing" to be a subsection of "Call Setup" 1765 o Deleted "Profile" section and moved some of its text into 1766 "Introduction" 1768 16.11. Changes from draft-ietf-06 to draft-ietf-07 1770 o Minor editorial changes 1772 16.12. Changes from draft-ietf-05 to draft-ietf-06 1774 o Added clarifying text regarding signed and encrypted data 1775 o Additional informative text in "Migration to Next-Generation" 1776 section 1777 o Additional clarifying text regarding security and privacy. 1779 16.13. Changes from draft-ietf-04 to draft-ietf-05 1781 o Reworded security text in main document and in MIME registration 1782 for the VEDS object 1784 16.14. Changes from draft-ietf-03 to draft-ietf-04 1786 o Added example VEDS object 1787 o Additional clarifications and corrections 1788 o Removed references from Abstract 1789 o Moved Document Scope section to follow Introduction 1791 16.15. Changes from draft-ietf-02 to draft-ietf-03 1793 o Additional clarifications and corrections 1795 16.16. Changes from draft-ietf-01 to draft-ietf-02 1797 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1798 aspects including the service URN; this document no longer 1799 proposes a unique service URN for non-eCall NG-ACN calls; the same 1800 service URN is now used for all NG-ACN calls including NG-eCall 1801 and non-eCall 1802 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1803 support it 1804 o Minor wording improvements and clarifications 1806 16.17. Changes from draft-ietf-00 to draft-ietf-01 1808 o Added further discussion of test calls 1809 o Added further clarification to the document scope 1810 o Mentioned that multi-region vehicles may need to support other 1811 crash notification specifications such as eCall 1812 o Minor wording improvements and clarifications 1814 16.18. Changes from draft-gellens-02 to draft-ietf-00 1816 o Renamed from draft-gellens- to draft-ietf- 1817 o Added text to Introduction to clarify that during a CS ACN, the 1818 PSAP call taker usually needs to listen to the data and transcribe 1819 it 1821 16.19. Changes from draft-gellens-01 to -02 1823 o Fixed case of 'EmergencyCallData', in accordance with changes to 1824 [RFC7852] 1826 16.20. Changes from draft-gellens-00 to -01 1828 o Now using 'EmergencyCallData' for purpose parameter values and 1829 MIME subtypes, in accordance with changes to [RFC7852] 1830 o Added reference to RFC 6443 1831 o Fixed bug that caused Figure captions to not appear 1833 17. References 1835 17.1. Normative References 1837 [I-D.ietf-ecrit-ecall] 1838 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1839 European eCall", draft-ietf-ecrit-ecall-24 (work in 1840 progress), January 2017. 1842 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1843 Requirement Levels", BCP 14, RFC 2119, 1844 DOI 10.17487/RFC2119, March 1997, 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 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1853 Initiation Protocol (SIP) INFO Method and Package 1854 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1855 . 1857 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 1858 Specifications and Registration Procedures", BCP 13, 1859 RFC 6838, DOI 10.17487/RFC6838, January 2013, 1860 . 1862 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1863 Communications Services in Support of Emergency Calling", 1864 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1865 . 1867 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 1868 DOI 10.17487/RFC7303, July 2014, 1869 . 1871 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1872 J. Winterbottom, "Additional Data Related to an Emergency 1873 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1874 . 1876 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1877 NENA Data Standardization Workgroup, , "Vehicular 1878 Emergency Data Set (VEDS) version 3", July 2012, 1879 . 1882 17.2. Informative references 1884 [Bluetooth] 1885 Bluetooth Special Interest Group, , "Bluetooth 1886 Specifications", . 1889 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1890 Emergency Context Resolution with Internet Technologies", 1891 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1892 . 1894 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1895 Shanmugam, "Security Threats and Requirements for 1896 Emergency Call Marking and Mapping", RFC 5069, 1897 DOI 10.17487/RFC5069, January 2008, 1898 . 1900 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1901 "Framework for Emergency Calling Using Internet 1902 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1903 2011, . 1905 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1906 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1907 December 2014, . 1909 [triage-2008] 1910 National Center for Injury Prevention and Control, and 1911 Centers for Disease Control and Prevention, 1912 "Recommendations from the Expert Panel: Advanced Automatic 1913 Collision Notification and Triage of the Injured Patient", 1914 2008, . 1916 [triage-2011] 1917 National Center for Injury Prevention and Control, and 1918 Centers for Disease Control and Prevention, "Guidelines 1919 for field triage of injured patients: recommendations of 1920 the National Expert Panel on Field Triage", January 2012, 1921 . 1926 Authors' Addresses 1928 Randall Gellens 1929 Core Technology Consulting 1931 Email: rg+ietf@randy.pensive.org 1933 Brian Rosen 1934 NeuStar, Inc. 1935 470 Conrad Dr 1936 Mars, PA 16046 1937 US 1939 Email: br@brianrosen.net 1941 Hannes Tschofenig 1942 Individual 1944 Email: Hannes.Tschofenig@gmx.net 1945 URI: http://www.tschofenig.priv.at