idnits 2.17.1 draft-ietf-ecrit-car-crash-20.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 834 has weird spacing: '...-camera adds ...' -- The document date (December 15, 2016) is 2688 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-27) exists of draft-ietf-ecrit-ecall-20 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Possible downref: Non-RFC (?) normative reference: ref. 'VEDS' Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Core Technology Consulting 4 Intended status: Standards Track B. Rosen 5 Expires: June 18, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 December 15, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-20.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 a different set of vehicle (crash) 37 data, specifically, the Vehicle Emergency Data Set (VEDS) rather than 38 the eCall Minimum Set of Data (MSD). This document is an extension 39 of the eCall document, with the primary differences being that this 40 document makes the MSD data set optional and VEDS mandatory, and adds 41 attribute values to the metadata/control object to permit greater 42 functionality. This document registers a new SIP INFO package 43 (identical to that registered for eCall but with the addition of the 44 VEDS MIME type). This document also describes legacy (circuit- 45 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 June 18, 2017. 65 Copyright Notice 67 Copyright (c) 2016 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. Lamp State Registry . . . . . . . . . . . . . . . . . . 32 108 14.7. Emergency Call Vehicle Camera ID Registry . . . . . . . 33 109 14.8. The emergencyCallData.eCall.VEDS SIP INFO package . . . 34 110 15. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 111 16. Changes from Previous Versions . . . . . . . . . . . . . . . 37 112 16.1. Changes from draft-ietf-18 to draft-ietf-19 . . . . . . 37 113 16.2. Changes from draft-ietf-17 to draft-ietf-18 . . . . . . 38 114 16.3. Changes from draft-ietf-16 to draft-ietf-17 . . . . . . 38 115 16.4. Changes from draft-ietf-14 to draft-ietf-15 . . . . . . 38 116 16.5. Changes from draft-ietf-13 to draft-ietf-14 . . . . . . 38 117 16.6. Changes from draft-ietf-11 to draft-ietf-13 . . . . . . 38 118 16.7. Changes from draft-ietf-10 to draft-ietf-11 . . . . . . 38 119 16.8. Changes from draft-ietf-09 to draft-ietf-10 . . . . . . 38 120 16.9. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 39 121 16.10. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 39 122 16.11. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 39 123 16.12. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 39 124 16.13. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 39 125 16.14. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 39 126 16.15. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 39 127 16.16. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 40 128 16.17. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 40 129 16.18. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 40 130 16.19. Changes from draft-gellens-01 to -02 . . . . . . . . . . 40 131 16.20. Changes from draft-gellens-00 to -01 . . . . . . . . . . 40 132 17. References . . . . . . . . . . . . . . . . . . . . . . . . . 40 133 17.1. Normative References . . . . . . . . . . . . . . . . . . 40 134 17.2. Informative references . . . . . . . . . . . . . . . . . 41 135 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42 137 1. Terminology 139 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 140 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 141 document are to be interpreted as described in [RFC2119]. 143 This document re-uses terminology defined in Section 3 of [RFC5012]. 145 Additionally, we use the following abbreviations: 147 +--------+----------------------------------------------------------+ 148 | Term | Expansion | 149 +--------+----------------------------------------------------------+ 150 | 3GPP | 3rd Generation Partnership Project | 151 | AACN | Advanced Automatic Crash Notification | 152 | ACN | Automatic Crash Notification | 153 | APCO | Association of Public-Safety Communications Officials | 154 | EENA | European Emergency Number Association | 155 | ESInet | Emergency Services IP network | 156 | GNSS | Global Navigation Satellite System (which includes | 157 | | various systems such as the Global Positioning System or | 158 | | GPS) | 159 | IVS | In-Vehicle System | 160 | MNO | Mobile Network Operator | 161 | MSD | eCall Minimum Set of Data | 162 | NENA | National Emergency Number Association | 163 | NG | Next-Generation | 164 | POTS | Plain Old Telephone Service (normal, circuit-switched | 165 | | voice calls) | 166 | PSAP | Public Safety Answering Point | 167 | TSP | Telematics Service Provider | 168 | VEDS | Vehicle Emergency Data Set | 169 +--------+----------------------------------------------------------+ 171 Because the endpoints of a Next-Generation ACN call are a PSAP and an 172 IVS or TSP, to avoid receptively writing "IVS or TSP", the term "IVS" 173 is used to represent either an IVS or TSP when discussing signaling 174 behavior (e.g., sending VEDS data, sending a SIP INVITE request, 175 receiving a SIP INFO request, etc.). 177 2. Introduction 179 Emergency calls made by in-vehicle systems (e.g., automatically in 180 the event of a crash or serious incident or manually by a vehicle 181 occupant) assist in significantly reducing road deaths and injuries 182 by allowing emergency services to respond quickly and appropriately 183 to the specifics of the incident, often with better location 184 accuracy. 186 Drivers often have a poor location awareness, especially outside of 187 major cities, at night and when away from home (especially abroad). 188 In the most crucial cases, the victim(s) might not be able to call 189 because they have been injured or trapped. 191 For more than two decades, some vehicles have been equipped with 192 telematics systems which, among other features, place an emergency 193 call automatically in the event of a crash or manually in response to 194 an emergency call button. Such systems generally have on-board 195 location determination systems that make use of satellite-based 196 positioning technology, inertial sensors, gyroscopes, etc., which can 197 provide an accurate position for the vehicle. Such built-in systems 198 can take advantage of the benefits of being integrated into a 199 vehicle, such as more power capacity, ability to have larger or 200 specialized antenna, ability to be engineered to avoid or minimise 201 degradation by vehicle glass coatings, interference from other 202 vehicle systems, etc. Thus, the PSAP can be provided with a good 203 estimate of where the vehicle is during an emergency. Vehicle 204 manufacturers are increasingly adopting such systems, both for the 205 safety benefits and for the additional features and services they 206 enable (e.g., remote engine diagnostics, remote door unlock, stolen 207 vehicle tracking and disabling, etc.). 209 The general term for such systems is Automatic Crash Notification 210 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 211 used in this document as a general term. ACN systems transmit some 212 amount of data specific to the incident, referred to generally as 213 "crash data" (the term is commonly used even though there might not 214 have been a crash). While different systems transmit different 215 amounts of crash data, standardized formats, structures, and 216 mechanisms are needed to provide interoperability among systems and 217 PSAPs. 219 As of the date of this document, currently deployed in-vehicle 220 telematics systems are circuit-switched and lack a standards-based 221 ability to convey crash data directly to the PSAP (generally relying 222 on either a human advisor or an automated text-to-speech system to 223 provide the PSAP call taker with some crash data orally, or in some 224 cases via a proprietary mechanism). In most cases, the PSAP call 225 taker needs to first realize that the call is related to a vehicle 226 incident, and then listen to the data and transcribe it. Circuit- 227 switched ACN systems are referred to here as CS-ACN. 229 The transition to next-generation calling in general, and for 230 emergency calling in particular, provides an opportunity to vastly 231 improve the scope, breadth, reliability and usefulness of crash data 232 during an emergency by allowing a standardized set to be transmitted 233 during call set-up; to be automatically processed by the PSAP and 234 made available to the call taker in an integrated, automated way; as 235 well as provide the ability for a PSAP call taker to request that a 236 vehicle take certain actions, such as flashing lights or unlocking 237 doors. In addition, vehicle manufacturers are provided an 238 opportunity to take advantage of the same standardized mechanisms for 239 data transmission and request processing for internal use if they 240 wish (such as telemetry between the vehicle and a service center for 241 both emergency and non-emergency uses, including location-based 242 services, multi-media entertainment systems, remote door unlocking, 243 remote diagnostics, and road-side assistance applications). 245 Next-generation ACN provides an opportunity for such calls to be 246 recognized and processed as such during call set-up, and routed to an 247 equipped PSAP where the vehicle data is available to assist the call 248 taker in assessing and responding to the situation. Next-generation 249 (IP-based) ACN systems are referred to here as NG-ACN. 251 An ACN call can be initiated by a vehicle occupant or automatically 252 initiated by vehicle systems in the event of a serious incident. 253 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 254 used to refer to the class of calls that are placed by an in-vehicle 255 system (IVS) or Telematics Service Providers (TSP) and that carry 256 incident-related data as well as voice.) Automatically triggered 257 calls indicate a car crash or some other serious incident (e.g., a 258 fire). Manually triggered calls include reports of observed crashes 259 or serious hazards (such as impaired drivers or roadway debris). 261 The Association of Public-Safety Communications Officials (APCO) and 262 the National Emergency Number Association (NENA) have jointly 263 developed a standardized set of incident-related vehicle data for ACN 264 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 265 is often referred to as crash data although it is applicable in 266 incidents other than crashes. 268 This document describes how the IETF mechanisms for IP-based 269 emergency calls are used to provide the realization of next- 270 generation ACN. Although this specification is designed with the 271 requirements for North America ACN in mind (and both APCO and NENA 272 are based in the U.S.), it is specified generically such that the 273 technology can be re-used or extended to suit requirements in other 274 regions. 276 This document reuses the technical aspects of next-generation pan- 277 European eCall (a mandated and standardized system for emergency 278 calls by in-vehicle systems within Europe), as described in 279 [I-D.ietf-ecrit-ecall]. However, this document specifies a different 280 set of vehicle (crash) data, specifically, the Vehicle Emergency Data 281 Set (VEDS) rather than the eCall Minimum Set of Data (MSD). This 282 document is an extension of [I-D.ietf-ecrit-ecall], with the 283 differences being that this document makes the MSD data set optional 284 and VEDS mandatory, and adds new attribute values to the metadata/ 285 control object defined in that document. This document also 286 registers a new SIP INFO package (identical to that defined in 287 [I-D.ietf-ecrit-ecall] with the addition of the VEDS MIME type). 289 This document registers the 'application/EmergencyCallData.VEDS+xml' 290 MIME media type, registers the 'VEDS' entry in the Emergency Call 291 Data Types registry, and registers a SIP INFO package to enable 292 carrying this and related data in SIP INFO requests. 294 Section 6 introduces VEDS. Section 7 describes how VEDS data and 295 metadata/control blocks are transported within NG-ACN calls. 296 Section 8 describes how such calls are placed. 298 These mechanisms are used to place emergency calls that are 299 identifiable as ACN calls and that carry standardized crash data in 300 an interoperable way. 302 Calls by in-vehicle systems are placed using cellular networks, which 303 might ignore location information sent by an originating device in an 304 emergency call INVITE, instead substituting their own location 305 information (often determined in cooperation with the originating 306 device). Standardized crash data structures often include location 307 as determined by the IVS. A benefit of this is that it allows the 308 PSAP to see both the location as determined by the cellular network 309 (often in cooperation with the originating device) and the location 310 as determined by the IVS. 312 This specification inherits the ability to utilize test call 313 functionality from Section 15 of [RFC6881]. 315 3. Document Scope 317 This document is focused on how an ACN emergency call is setup and 318 incident-related data (including vehicle, sensor, and location data) 319 is transmitted to the PSAP using IETF specifications. For the direct 320 model, this is the end-to-end description (between the vehicle and 321 the PSAP). For the TSP model, this describes the call leg between 322 the TSP and the PSAP, leaving the call leg between the vehicle and 323 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 324 are then free to use the same mechanism as for the other leg or not. 326 Note that Europe has a mandated and standardized system for emergency 327 calls by in-vehicle systems. This pan-European system is known as 328 "eCall" and is the subject of a separate document, 329 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 330 designed to operate in multiple regions might need to support eCall 331 as well as NG-ACN as described here. A vehicle IVS might determine 332 whether to use eCall or ACN by first determining the region or 333 country in which it is located (e.g., from a GNSS location estimate 334 and/or identity of or information from an MNO). If other regions 335 adopt other data formats, a multi-region vehicle might need to 336 support those as well. This document adopts the call set-up and 337 other technical aspects of [I-D.ietf-ecrit-ecall], which uses 338 [RFC7852]; this makes it straightforward to use a different data set 339 while keeping other technical aspects unchanged. Hence, both NG- 340 eCall and the NG-ACN mechanism described here are compatible, 341 differing primarily in the specific data block that is sent (the 342 eCall MSD in the case of NG-eCall, and the APCO/NENA VEDS used in 343 this document), and some additions to the metadata/control data 344 block. If other regions adopt their own vehicle data sets, this can 345 be similarly accomodated without changing other technical aspects. 346 Note that any additional data formats require a new SIP INFO package 347 to permit transport within SIP INFO requests. 349 4. Overview of Legacy Deployment Models 351 Legacy (circuit-switched) systems for placing emergency calls by in- 352 vehicle systems generally have some ability to convey at least 353 location and in some cases telematics data to the PSAP. Most such 354 systems use one of three architectural models, which are described 355 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 356 These three models are illustrated below. 358 In the TSP model, both emergency and non-emergency calls are placed 359 to a Telematics Service Provider (TSP); a proprietary technique is 360 used for data transfer (such as a proprietary in-band modem) between 361 the TSP and the vehicle. 363 In an emergency, generally the TSP call taker bridges in the PSAP and 364 communicates location, crash data (such as impact severity and trauma 365 prediction), and other data (such as the vehicle description) to the 366 PSAP call taker verbally (in some cases, a proprietary out-of-band 367 interface is used). Since the TSP knows the location of the vehicle 368 (from on-board GNSS and sensors), location-based routing is usually 369 used to route to the appropriate PSAP. In some cases, the TSP is 370 able to transmit location automatically, using similar techniques as 371 for wireless calls. Typically, a three-way voice call is established 372 between the vehicle, the TSP, and the PSAP, allowing communication 373 between the PSAP call taker, the TSP call taker, and the vehicle 374 occupants (who might be unconscious). 376 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 377 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 378 \\\----/// crash data +------+ location via trunk +------+ 380 Figure 1: Legacy TSP Model. 382 In the paired model, the IVS uses a Bluetooth link with a previously- 383 paired handset to establish an emergency call with the PSAP (by 384 dialing a standard emergency number; 9-1-1 in North America), and 385 then communicates location data to the PSAP via text-to-speech; crash 386 data might or might not be conveyed also using text-to-speech. Some 387 such systems use an automated voice prompt menu for the PSAP call 388 taker (e.g., "this is an automatic emergency call from a vehicle; 389 press 1 to open a voice path to the vehicle; press 2 to hear the 390 location read out") to allow the call taker to request location data 391 via text-to-speech. 393 +---+ 394 ///----\\\ | H | 911/etc voice call via handset +------+ 395 ||| IVS |||-->| S +----------------------------------->+ PSAP | 396 \\\----/// +---+ location via text-to-speech +------+ 398 Figure 2: Legacy Paired Model 400 In the direct model, the IVS directly places an emergency call with 401 the PSAP by dialing a standard emergency number (9-1-1 in North 402 America). Such systems might communicate location data to the PSAP 403 via text-to-speech; crash data might or might not be conveyed using 404 text-to-speech. Some such systems use an automated voice prompt menu 405 (e.g., "this is an automatic emergency call from a vehicle; press 1 406 to open a voice path to the vehicle; press 2 to hear the location 407 read out") to allow the call taker to request location data via text- 408 to-speech. 410 ///----\\\ 911/etc voice call via IVS +------+ 411 ||| IVS |||---------------------------------------->+ PSAP | 412 \\\----/// location via text-to-speech +------+ 414 Figure 3: Legacy Direct Model 416 5. Migration to Next-Generation 418 Migration of emergency calls placed by in-vehicle systems to next- 419 generation (all-IP) technology per this document provides a 420 standardized mechanism to identify such calls and to convey crash 421 data with the call setup, as well as enabling additional 422 communications modalities and enhanced functionality. This allows 423 ACN calls and crash data to be automatically processed by the PSAP 424 and made available to the call taker in an integrated, automated way. 425 Because the crash data is carried in the initial SIP INVITE (per 426 [RFC7852]) the PSAP can present it to the call taker simultaneously 427 with the appearance of the call. The PSAP can also process the data 428 to take other actions (e.g., if multiple calls from the same location 429 arrive when the PSAP is busy and a subset of them are NG-ACN calls, a 430 PSAP might choose to store the information and reject the calls, 431 since the IVS will receive confirmation that the information has been 432 successfully received; a PSAP could also choose to include a message 433 stating that it is aware of the incident and responders are on the 434 way; a PSAP could call the vehicle back when a call taker is 435 available). 437 The migration of origination devices and networks, PSAPs, emergency 438 services networks, and other telephony environments to next- 439 generation provides enhanced interoperability and functionality, 440 especially for emergency calls carrying additional data such as 441 vehicle crash data. (In the U.S., a network specifically for 442 emergency responders is being developed. This network, FirstNet, 443 will be next-generation from the start, enhancing the ability for 444 data exchange between PSAPs and responders.) 446 NG-ACN calls can be recognized as originating from a vehicle, routed 447 to a PSAP prepared both technically and operationally to handle such 448 calls, and the vehicle-determined location and crash data made 449 available to the call taker simultaneously with the call appearance. 450 The PSAP can take advantage of enhanced functionality, including the 451 ability to request the vehicle to take an action, such as sending an 452 updated set of data, converying a message to the occupants, flashing 453 lights, unlocking doors, etc. 455 Vehicle manufacturers using the TSP model can choose to take 456 advantage of the same mechanism to carry telematics data and requests 457 and responses between the vehicle and the TSP for both emergency and 458 non-emergency calls as are used for the interface with the PSAP. 460 A next-generation IVS establishes a next-generation emergency call 461 (see [RFC6443] and [RFC6881]), with an initial INVITE containing a 462 Request-URI indicating an ACN type of emergency call and Call-Info 463 header fields indicating that both vehicle crash and capabilities 464 data are included; the IVS typically does not perform routing or 465 location queries but relies on the carrier for this. 467 [I-D.ietf-ecrit-ecall] registers new service URN children within the 468 "sos" subservice. These URNs request NG-ACN resources, and 469 differentiate between manually and automatically triggered NG-ACN 470 calls (which might be subject to different treatment depending on 471 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 472 are "urn:service:sos.ecall.automatic" and 473 "urn:service:sos.ecall.manual". The same service URNs are used for 474 ACN as for eCall since in any region only one of these is supported, 475 making a distinction unnecessary. (Further, PSAP equipment might 476 support multiple data formats, allowing a PSAP to handle a vehicle 477 that erroneously sent the wrong data object.) 478 Note that in North America, routing queries performed by clients 479 outside of an ESInet typically treat all sub-services of "sos" 480 identically to "sos" with no sub-service. However, the Request-URI 481 header field retains the full sub-service; route and handling 482 decisions within an ESInet or PSAP can take the sub-service into 483 account. For example, in a region with multiple cooperating PSAPs, 484 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 485 one that specializes in vehicle-related incidents. 487 Migration of the three architectural models to next-generation (all- 488 IP) is described below. 490 In the TSP model, the IVS transmits crash and location data to the 491 TSP either by re-using the mechanisms and data objects described in 492 this document, or using a proprietary mechanism. In an emergency, 493 the TSP bridges in the PSAP and the TSP transmits crash and other 494 data to the PSAP using the mechanisms and data objects described in 495 this document. There is a three-way call between the vehicle, the 496 TSP, and the PSAP, allowing communication between the PSAP call 497 taker, the TSP call taker, and the vehicle occupants (who might be 498 unconscious). The TSP relays PSAP requests and vehicle responses. 500 proprietary 501 ///----\\\ or standard +------+ standard +------+ 502 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 503 \\\----/// crash + other data +------+ crash + other data +------+ 505 Figure 4: Next-Generation TSP Model 507 The vehicle manufacturer and the TSP can choose to use the same 508 mechanisms and data objects on the left call leg in Figure 4 as on 509 the right. (Note that the TSP model can be more difficult when the 510 vehicle is in a different country than the TSP (e.g., a US resident 511 driving in Canada) because of the additional complexity in choosing 512 the correct PSAP based on vehicle location performed by a TSP in a 513 different country.) 515 In the direct model, the IVS communicates crash data to the PSAP 516 directly using the mechanisms and data objects described in this 517 document. 519 ///----\\\ NG emergency call +------+ 520 ||| IVS |||----------------------------------------->+ PSAP | 521 \\\----/// crash + other data +------+ 523 Figure 5: Next-Generation Direct Model 525 In the paired model, the IVS uses a Bluetooth link to a previously- 526 paired handset to establish an emergency call with the PSAP; it is 527 unclear what facilities are or will be available for transmitting 528 crash data through the Bluetooth link to the handset for inclusion in 529 an NG emergency call. Hence, manufacturers that use the paired model 530 for legacy calls might choose to adopt either the direct or TSP 531 models for next-generation calls. 533 +---+ 534 ///----\\\ (undefined) | H | standard +------+ 535 ||| IVS |||------------------>| S +------------------->+ PSAP | 536 \\\----/// (undefined) +---+ crash + other data +------+ 538 Figure 6: Next-Generation Paired Model 540 If the call is routed to a PSAP that is not capable of processing the 541 vehicle data, the PSAP ignores (or does not receive) the vehicle 542 data. This is detectable by the IVS or TSP when the status response 543 to the INVITE (e.g., 200 OK) lacks a metadata/control structure 544 acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or 545 TSP then proceeds as it would for a CS-ACN call (e.g., verbal 546 conveyance of data) 548 6. Vehicle Data 550 The Association of Public-Safety Communications Officials (APCO) and 551 the National Emergency Number Association (NENA) have jointly 552 developed a standardized set of incident-related vehicle data for ACN 553 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 554 is often referred to as crash data although it is applicable in 555 incidents other than crashes. 557 VEDS provides a standard data set for the transmission, exchange, and 558 interpretation of vehicle-related data. A standard data format 559 allows the data to be generated by an IVS or TSP and interpreted by 560 PSAPs, emergency responders, and medical facilities. It includes 561 incident-related information such as airbag deployment, location and 562 compass orientation of the vehicle, spatial orientation of the 563 vehicle (e.g., upright, on its side or roof or a bumper), various 564 sensor data that can indicate the potential severity of the crash and 565 the likelihood of severe injuries to the vehicle occupants, etc. 566 This data better informs the PSAP and emergency responders as to the 567 type of response that might be needed. Some of this information has 568 been included in U.S. government guidelines for field triage of 569 injured patients [triage-2008] [triage-2011]. These guidelines are 570 designed to help responders identify the potential existence of 571 severe internal injuries and to make critical decisions about how and 572 where a patient needs to be transported. 574 VEDS is an XML structure (see [VEDS]) transported in SIP using the 575 'application/EmergencyCallData.VEDS+xml' MIME media type. 577 If new data blocks are needed (e.g., in other regions or for enhanced 578 data), the steps required during standardization are briefly 579 summarized below: 581 o A set of data is standardized by an SDO or appropriate 582 organization 583 o A MIME media type for the crash data set is registered with IANA 585 * If the data is specifically for use in emergency calling, the 586 MIME media type is normally under the 'application' type with a 587 subtype starting with 'EmergencyCallData.' 588 * If the data format is XML, then by convention the name has a 589 suffix of '+xml' 590 o The item is registered in the Emergency Call Data Types registry, 591 as defined in Section 11.1.9 of [RFC7852] 593 * For emergency-call-specific formats, the registered name is the 594 root of the MIME media type (not including the 595 'EmergencyCallData' prefix and any suffix such as '+xml') as 596 described in Section 4.1 of [RFC7852]. 597 o A new SIP INFO package is registered that permits carrying the the 598 new media type, the metadata/control object (defined in 599 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 600 objects, in SIP INFO requests. 602 7. Data Transport 604 [RFC7852] establishes a general mechanism for including blocks of 605 data within a SIP emergency call. This document makes use of that 606 mechanism. This document also registers a SIP INFO package (in 607 Section 14.8) to enable NG-ACN related data blocks to be carried in 608 SIP INFO requests (per [RFC6086], new SIP INFO method usages require 609 the definition of a SIP INFO package). 611 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 612 the Association of Public-Safety Communications Officials (APCO) and 613 the National Emergency Number Association (NENA) [VEDS]. It is 614 carried in a body part with MIME media type 'application/ 615 EmergencyCallData.VEDS+xml'. 617 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 618 by including it as a body part of a SIP message per [RFC7852]. The 619 body part is identified by its MIME media type ('application/ 620 emergencyCallData.VEDS+xml') in the Content-Type header field of the 621 body part. The body part is assigned a unique identifier which is 622 listed in a Content-ID header field in the body part. The SIP 623 message is marked as containing the VEDS data by adding (or appending 624 to) a Call-Info header field at the top level of the SIP message. 625 This Call-Info header field contains a CID URL referencing the body 626 part's unique identifier, and a 'purpose' parameter identifying the 627 data as a VEDS data block per the Emergency Call Additional Data 628 Types registry entry; the 'purpose' parameter's value is 629 'emergencyCallData.VEDS'. A VEDS data block is carried in a SIP INFO 630 request by using the SIP INFO package defined in Section 14.8. 632 A PSAP or IVS transmits a metadata/control object (see 633 [I-D.ietf-ecrit-ecall]) by including it in a SIP message as a MIME 634 body part per [RFC7852]. The body part is identified by its MIME 635 media type ('application/emergencyCallData.control+xml') in the 636 Content-Type header field of the body part. The body part is 637 assigned a unique identifier which is listed in a Content-ID header 638 field in the body part. The SIP message is marked as containing the 639 metadata/control block by adding (or appending to) a Call-Info header 640 field at the top level of the SIP message. This Call-Info header 641 field contains a CID URL referencing the body part's unique 642 identifier, and a 'purpose' parameter identifying the data as a 643 metadata/control block per the Emergency Call Additional Data Types 644 registry entry; the 'purpose' parameter's value is 645 'emergencyCallData.control'. A metadata/control object is carried in 646 a SIP INFO request by using the SIP INFO package defined in 647 Section 14.8. 649 A body part containing a VEDS or metadata/control object has a 650 Content-Disposition header field value containing "By-Reference" and 651 is always enclosed in a multipart body part (even if it would 652 otherwise be the only body part in the SIP message), since as of the 653 date of this document, the use of Content-ID as a SIP header field is 654 not defined (while it is defined for use as a MIME header field). 656 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 657 initial INVITE a VEDS data block and a metadata/control object 658 informing the PSAP of its capabilities. The VEDS and metadata/ 659 control body parts (and PIDF-LO) have a Content-Disposition header 660 field with the value "By-Reference; handling=optional". Specifying 661 handling=optional prevents the INVITE from being rejected if it is 662 processed by a legacy element (e.g., a gateway between SIP and 663 circuit-switched environments) that does not understand the VEDS or 664 metadata/control (or PIDF-LO) objects. The PSAP creates a metadata/ 665 control object acknowledging receipt of the VEDS data and includes it 666 in the SIP final response to the INVITE. The metadata/control object 667 is not included in provisional (e.g., 180) responses. 669 If the IVS receives an acknowledgment for a VEDS data object with 670 received=false, this indicates that the PSAP was unable to properly 671 decode or process the VEDS. The IVS action is not defined (e.g., it 672 might only log an error). Since the PSAP is able to request an 673 updated VEDS during the call, if an initial VEDS is unsatisfactory in 674 any way, the PSAP can choose to request another one. 676 A PSAP can request that the vehicle send an updated VEDS data block 677 during a call. To do so, the PSAP creates a metadata/control object 678 requesting VEDS data and includes it as a body part of a SIP INFO 679 request sent within the dialog. The IVS then includes an updated 680 VEDS data object as a body part of a SIP INFO request and sends it 681 within the dialog. If the IVS is unable to send the VEDS, it instead 682 sends a metadata/control object acknowledging the request with the 683 'success' parameter set to 'false' and a 'reason' parameter (and 684 optionally a 'details' parameter) indicating why the request cannot 685 be accomplished. Per [RFC6086], metadata/control objects and VEDS 686 data are sent using the SIP INFO package defined in Section 14.8. In 687 addition, to align with the way a VEDS or metadata/control block is 688 transmitted in a SIP message other than a SIP INFO request, one or 689 more Call-Info header fields are included in the SIP INFO request 690 referencing the VEDS or metadata/control block. See Section 14.8 for 691 more information on the use of SIP INFO requests within NG-ACN calls. 693 Any metadata/control object sent by a PSAP can request that the 694 vehicle perform an action (such as sending a data block, flashing 695 lights, providing a camera feed, etc.) The vehicle sends an 696 acknowledgement for any request other than a successfully executed 697 send-data action. Multiple requests with the same 'action' value 698 MUST be sent in separate body parts (to avoid any ambiguity in the 699 acknowledgement). 701 If the IVS is aware that VEDS data it sent previously has changed, it 702 MAY send an unsolicited VEDS in any convenient SIP message, including 703 a SIP INFO request during the call. The PSAP sends an acknowledgment 704 for an unsolicited VEDS object (if the IVS sent the unsolicited VEDS 705 in a SIP INFO request, the acknowledgment is sent in a new SP INFO 706 request, otherwise it is sent in the reply to the SIP request 707 containing the VEDS). 709 8. Call Setup 711 A next-generation In-Vehicle System (IVS) initiating an NG-ACN call 712 sends a SIP INVITE request using one of the SOS sub-services 713 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI. This 714 SIP INVITE request includes standard sets of both crash and 715 capabilities data as described in Section 7. 717 Entities along the path between the vehicle and the PSAP are able to 718 identify the call as an ACN call and handle it appropriately. The 719 PSAP is able to identify the crash and capabilities data included in 720 the SIP INVITE request by examining the Call-Info header fields for 721 'purpose' parameters whose values start with 'EmergencyCallData.' 722 The PSAP is able to access the data it is capable of handling and is 723 interested in by checking the 'purpose' parameter values. 725 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 726 up and other normative requirements with the exception that in this 727 document, support for the eCall MSD is OPTIONAL and support for VEDS 728 in REQUIRED. This document also adds new attribute values to the 729 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 731 9. New Metadata/Control Values 733 This document adds new attribute values to the metadata/control 734 structure defined in [I-D.ietf-ecrit-ecall]. 736 In addition to the base usage from the PSAP to the IVS to 737 acknowledge receipt of crash data, the element is also 738 contained in a metadata/control block sent by the IVS to the PSAP. 739 This is used by the IVS to acknowledge receipt of a request by the 740 PSAP and indicate if the request was carried out when that request 741 would not otherwise be acknowledged (if the PSAP requests the 742 vehicle to send data and the vehicle does so, the data serves as a 743 success acknowledgement). 744 The element is used in a metadata/control block 745 sent from the IVS to the PSAP (e.g., in the initial INVITE) to 746 inform the PSAP of the vehicle capabilities. Child elements 747 contain all actions and data types supported by the vehicle and 748 all available lamps (lights) and cameras. 749 New request values are added to the element to enable 750 the PSAP to request the vehicle to perform actions. 752 Mandatory Actions (the IVS and the PSAP MUST support): 754 o Transmit data object (VEDS MUST be supported; MSD MAY be 755 supported) 757 Optional Actions (the IVS and the PSAP MAY support): 759 o Play and/or display static (pre-defined) message 760 o Speak/display dynamic text (text supplied in action) 761 o Flash or turn on or off a lamp (light) 762 o Honk horn 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 824 indicated by a lamp state token contained 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. A registry of lamp states is 831 defined in Section 14.6. The initial values (listed in Table 5) 832 are "on", "off", and "flash". 834 enable-camera adds a one-way media stream (established via SIP re- 835 INVITE sent by the vehicle) to enable the PSAP call taker to view 836 a feed from a camera. A registry of camera identification values 837 is defined in Section 14.7. The initial values (listed in 838 Table 6) are backup, left-rear, right-rear, forward, rear-wide, 839 lane, interior, and night-front. 841 Note that there is no 'request' action to play dynamic media (such as 842 an audio message). The PSAP can send a SIP re-INVITE to establish a 843 one-way media stream for this purpose. 845 9.2. Request Example 846 847 851 852 854 855 856 Remain calm. Help is on the way. 857 859 861 Figure 7: Request Example 863 9.3. The element 865 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 866 PSAP to acknowledge the MSD. Here, the element is also 867 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 868 to acknowledge receipt of a element that requested the IVS 869 to perform an action other than transmitting a data object (e.g., a 870 request to display a message would be acknowledged, but a request to 871 transmit VEDS data would not result in a separate element being 872 sent, since the data object itself serves as acknowledgment.) An 873 element sent by an IVS references the unique ID of the 874 metadata/control object containing the request(s) and indicates 875 whether the request was successfully performed, and if not, 876 optionally includes an explanation. 878 9.3.1. Ack Examples 879 880 884 885 886 888 890 892 Figure 8: Ack Example from IVS to PSAP 894 9.4. The element 896 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 897 the IVS to indicate its capabilities to the PSAP. 899 The element contains a child element per 900 action supported by the vehicle. The vehicle MUST support sending 901 the VEDS data object and so includes at a minimum a child 902 element with the 'action' attribute set to "send-data" and the 903 'supported-values' attribute containing all data blocks supported by 904 the IVS, which MUST include 'VEDS'. All other actions are OPTIONAL. 906 If the "msg-static" action is supported, a child element 907 with the 'action' attribute set to "msg-static" is included, with the 908 'int-id' attribute set to the highest supported static message 909 supported by the vehicle. A registry is created in Section 14.4 to 910 map 'int-id' values to static text messages. By sending the highest 911 supported static message number in its element, the 912 vehicle indicates its support for all static messages in the registry 913 up to and including that value. 915 If the "lamp" action is supported, a child element with the 916 'action' attribute set to "lamp" is included, with the 'supported- 917 values' attribute set to all supported lamp IDs. A registry is 918 created in Section 14.5 to contain lamp ID values. 920 If the "enable-camera" action is supported, a child element 921 with the 'action' attribute set to "enable-camera" is included, with 922 the 'supported-values' attribute set to all supported camera IDs. A 923 registry is created in Section 14.7 to contain camera ID values. 925 9.4.1. Capabilities Example 927 928 932 933 934 938 939 940 941 943 945 947 Figure 9: Capabilities Example 949 10. Test Calls 951 An NG-ACN test call is a call that is recognized and treated to some 952 extent as an NG-ACN call but not given emergency call treatment and 953 not handled by a call taker. The specific handling of test NG-ACN 954 calls is not itself standardized; the test call facility is intended 955 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 956 successfully established with voice and/or other media communication. 957 The IVS might also be able to verify that the crash data was 958 successfully received. 960 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 961 ability to utilize test call functionality from Section 15 of 962 [RFC6881]. A service URN starting with "test." indicates a test 963 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 964 for test calls. 966 MNOs, emergency authorities, ESInets, and PSAPs determine how to 967 treat a vehicle call requesting the "test" service URN so that the 968 desired functionality is tested, but this is outside the scope of 969 this document. (One possibility is that MNOs route such calls as 970 non-emergency calls to an ESInet, which routes them to a PSAP that 971 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 972 data acknowledgment, and plays an audio clip (for example, saying 973 that the call reached an appropriate PSAP and the vehicle data was 974 successfully processed) in addition to supporting media loopback per 975 [RFC6881]). 977 Note that since test calls are placed using "test" as the parent 978 service URN and "sos" as a child, such calls are not treated as an 979 emergency call and so some functionality might not apply (such as 980 preemption or service availability for devices lacking service ("non- 981 service-initialized" or "NSI" devices) if those are available for 982 emergency calls). 984 11. Example 986 Figure 10 shows an NG-ACN call routing. The mobile network operator 987 (MNO) routes the call to an Emergency services IP Network (ESInet), 988 as for any emergency call. The ESInet routes the call to an 989 appropriate NG-ACN-capable PSAP (using location information and the 990 fact that that it is an NG-ACN call). The call is processed by the 991 Emergency Services Routing Proxy (ESRP), as the entry point to the 992 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 993 PSAP, where the call is received by a call taker. (In deployments 994 where there is no ESInet, the MNO itself routes the call directly to 995 an appropriate NG-ACN-capable PSAP.) 997 +---------------------------------------+ 998 | | 999 +------------+ | +-------+ | 1000 | | | | PSAP2 | | 1001 | | | +-------+ | 1002 | Originating| | | 1003 | Mobile | | +------+ +-------+ | 1004 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1005 | | | +------+ +-------+ | 1006 | | | | 1007 +------------+ | +-------+ | 1008 | | PSAP3 | | 1009 | +-------+ | 1010 | | 1011 | | 1012 | | 1013 | ESInet | 1014 +---------------------------------------+ 1016 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1018 The example, shown in Figure 11, illustrates a SIP emergency call 1019 INVITE request with location information (a PIDF-LO), VEDS crash data 1020 (a VEDS data block), and capabilities data (a metadata/control block 1021 with extensions defined in this document) included in the SIP INVITE 1022 request message. The INVITE has a request URI containing the 1023 'urn:service:sos.ecall.automatic' service URN. 1025 The example VEDS data structure shows information about a crashed 1026 vehicle. The example communicates that the car is a model year 2015 1027 Saab 9-5 (a car which does not exist). The front airbag deployed as 1028 a consequence of the crash. The 'VehicleBodyCategoryCode' indicates 1029 that the crashed vehicle is a passenger car (the code is set to 1030 '101') and that it is not a convertible (the 'ConvertibleIndicator' 1031 value is set to 'false'). 1033 The 'VehicleCrashPulse' element provides further information about 1034 the crash, namely that the force of impact based on the change in 1035 velocity over the duration of the crash pulse was 100 MPH. The 1036 principal direction of the force of the impact is set to '12' (which 1037 refers to 12 O'Clock, corresponding to a frontal collision). This 1038 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1039 element. 1041 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1042 quarter turns in concert with a rollover expressed as a number; in 1043 our case 1. 1045 No roll bar was deployed, as indicated in 1046 'VehicleRollbarDeployedIndicator' being set to 'false'. 1048 Next, there is information indicating seatbelt and seat sensor data 1049 for individual seat positions in the vehicle. In our example, 1050 information from the driver seat is available (value '1' in the 1051 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1052 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1053 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1054 and the seat sensor determined that the seat was occupied 1055 ('VehicleSeatOccupiedIndicator' element). 1057 Finally, information about the weight of the vehicle, which is 600 1058 kilogram in our example. 1060 In addition to the information about the vehicle, further indications 1061 are provided, namely the presence of fuel leakage 1062 ('FuelLeakingIndicator' element), an indication whether the vehicle 1063 was subjected to multiple impacts ('MultipleImpactsIndicator' 1064 element), the orientation of the vehicle at final rest 1065 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1066 that there are no parts of the vehicle on fire (the 1067 'VehicleFireIndicator' element). 1069 INVITE urn:service:sos.ecall.automatic SIP/2.0 1070 To: urn:service:sos.ecall.automatic 1071 From: ;tag=9fxced76sl 1072 Call-ID: 3848276298220188511@atlanta.example.com 1073 Geolocation: 1074 Geolocation-Routing: no 1075 Call-Info: ; 1076 purpose=EmergencyCallData.VEDS 1077 Call-Info: ; 1078 purpose=emergencyCallData.control 1079 Accept: application/sdp, application/pidf+xml, 1080 application/emergencyCallData.control+xml 1081 Recv-Info: emergencyCallData.eCall 1082 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1083 SUBSCRIBE, NOTIFY, UPDATE 1084 CSeq: 31862 INVITE 1085 Content-Type: multipart/mixed; boundary=boundary1 1086 Content-Length: ... 1088 --boundary1 1089 Content-Type: application/sdp 1091 ...Session Description Protocol (SDP) goes here 1093 --boundary1 1094 Content-Type: application/pidf+xml 1095 Content-ID: 1096 Content-Disposition: by-reference;handling=optional 1098 1099 1107 1108 1109 1110 1111 -34.407 150.883 1112 1113 1114 278 1115 1116 1117 1118 1119 gps 1120 1121 2012-04-5T10:18:29Z 1122 1M8GDM9A_KP042788 1123 1124 1126 --boundary1 1127 Content-Type: application/EmergencyCallData.VEDS+xml 1128 Content-ID: <1234567890@atlanta.example.com> 1129 Content-Disposition: by-reference;handling=optional 1131 1132 1136 1137 1138 Saab 1139 1140 1141 9-5 1142 1143 1145 2015 1146 1147 1148 FRONT 1149 true 1150 1151 1152 false 1153 MAIN 1154 1156 101 1157 1158 1159 1160 1162 100 1163 1164 1166 MPH 1167 1168 12 1169 1170 1 1171 1172 1173 false 1174 1175 1176 1 1177 1178 true 1179 1180 true 1181 1182 true 1183 1184 1185 1187 1189 600 1190 1191 1193 kilogram 1194 1195 1196 1197 true 1198 false 1199 true 1200 Driver 1201 1202 false 1203 1204 1206 --boundary1 1207 Content-Type: application/emergencyCallData.control+xml 1208 Content-ID: <1234567892@atlanta.example.com> 1209 Content-Disposition: by-reference;handling=optional 1210 1211 1215 1216 1217 1221 1222 1223 1224 1226 1228 1230 --boundary1-- 1232 Figure 11: SIP INVITE for a Vehicle-Initated Emergency Call 1234 12. Security Considerations 1236 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1237 the security considerations described there and in [RFC5069] apply 1238 here. Implementors are cautioned to read and understand the 1239 discussion in those documents. 1241 As with emergency service systems where location data is supplied or 1242 determined with the assistance of an end host, there is the 1243 possibility that that location is incorrect, either intentially 1244 (e.g., in a denial of service attack against the emergency services 1245 infrastructure) or due to a malfunctioning device. The reader is 1246 referred to [RFC7378] for a discussion of some of these 1247 vulnerabilities. 1249 In addition to the security considerations discussion specific to the 1250 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1251 MAY decline to carry out any requested action (e.g., if the vehicle 1252 requires but is unable to verify the certificate used to sign the 1253 request). The vehicle MAY use any value in the reason registry to 1254 indicate why it did not take an action (e.g., the generic "unable" or 1255 the more specific "security-failure"). 1257 13. Privacy Considerations 1259 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1260 builds on [RFC7852], the data structures specified there, and the 1261 corresponding privacy considerations discussed there, apply here as 1262 well. The VEDS data structure contains optional elements that can 1263 carry identifying and personal information, both about the vehicle 1264 and about the owner, as well as location information, and so needs to 1265 be protected against unauthorized disclosure, as discussed in 1266 [RFC7852]. Local regulations may impose additional privacy 1267 protection requirements. 1269 The additional functionality enabled by this document, such as access 1270 to vehicle camera streams, carries a burden of protection and so 1271 implementations need to be careful that access is only provided 1272 within the context of an emergency call or to an emergency services 1273 provider (e.g., by verifying that the request for camera access is 1274 signed by a certificate issued by an emergency services registrar). 1276 14. IANA Considerations 1278 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1279 media type, and adds "VEDS" to the Emergency Call Data Types 1280 registry. This document adds to and creates sub-registries in the 1281 "Emergency Call Metadata/Control Data" registry created in 1282 [I-D.ietf-ecrit-ecall]. This document registers a new SIP INFO 1283 package. 1285 14.1. MIME Media Type Registration for 'application/ 1286 EmergencyCall.VEDS+xml' 1288 This specification requests the registration of a new MIME media type 1289 according to the procedures of RFC 6838 [RFC6838] and guidelines in 1290 RFC 7303 [RFC7303]. 1292 MIME media type name: application 1294 MIME subtype name: EmergencyCallData.VEDS+xml 1296 Mandatory parameters: none 1298 Optional parameters: charset 1300 Indicates the character encoding of enclosed XML. 1302 Encoding considerations: Uses XML, which can employ 8-bit 1303 characters, depending on the character encoding used. See 1304 Section 3.2 of RFC 7303 [RFC7303]. 1306 Security considerations: 1308 This media type is designed to carry vehicle crash data during 1309 an emergency call. 1311 This data can contain personal information including vehicle 1312 VIN, location, direction, etc. Appropriate precautions need to 1313 be taken to limit unauthorized access, inappropriate disclosure 1314 to third parties, and eavesdropping of this information. 1315 Please refer to Section 9 and Section 10 of [RFC7852] for more 1316 information. 1318 When this media type is contained in a signed or encrypted body 1319 part, the enclosing multipart (e.g., multipart/signed or 1320 multipart/encrypted) has the same Content-ID as the data part. 1321 This allows an entity to identify and access the data blocks it 1322 is interested in without having to dive deeply into the message 1323 structure or decrypt parts it is not interested in. (The 1324 'purpose' parameter in a Call-Info header field identifies the 1325 data, and the CID URL points to the data block in the body, 1326 which has a matching Content-ID body part header field). 1328 Interoperability considerations: None 1330 Published specification: [VEDS] 1332 Applications which use this media type: Emergency Services 1334 Additional information: None 1336 Magic Number: None 1338 File Extension: .xml 1340 Macintosh file type code: 'TEXT' 1342 Persons and email addresses for further information: Randall 1343 Gellens rg+ietf@randy.pensive.org; Hannes Tschofenig, 1344 Hannes.Tschofenig@gmx.net 1346 Intended usage: LIMITED USE 1348 Author: This specification is a work item of the IETF ECRIT 1349 working group, with mailing list address . 1351 Change controller: The IESG 1353 14.2. Registration of the 'VEDS' entry in the Emergency Call Data Types 1354 registry 1356 This specification requests IANA to add the 'VEDS' entry to the 1357 Emergency Call Data Types registry, with a reference to this 1358 document; the 'Data About' value is 'The Call'. The Emergency Call 1359 Data types registry was established by [RFC7852]. 1361 14.3. New Action Values 1363 This document adds new values for the 'action' attribute of the 1364 element in the "Emergency Call Action" registry created by 1365 [I-D.ietf-ecrit-ecall]. 1367 +---------------+-------------------------------------+ 1368 | Name | Description | 1369 +---------------+-------------------------------------+ 1370 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1371 | | | 1372 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1373 | | | 1374 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1375 | | | 1376 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1377 | | | 1378 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1379 +---------------+-------------------------------------+ 1381 Table 2: Emergency Call Action Registry New Values 1383 14.4. Emergency Call Static Message Registry 1385 This document creates a new sub-registry called "Emergency Call 1386 Static Message" in the "Emergency Call Metadata/Control Data" 1387 registry established by [I-D.ietf-ecrit-ecall]. Because all 1388 compliant vehicles are expected to support all static messages 1389 translated into all languages supported by the vehicle, it is 1390 important to limit the number of such messages. As defined in 1391 [RFC5226], this registry operates under "Specification Required" 1392 rules, which require a stable, public document and implies expert 1393 review of the publication. The expert should determine that the 1394 document has been published by an appropriate emergency services 1395 organization (e.g., NENA, EENA, APCO) or by the IETF with input from 1396 an emergency services organization, and that the proposed message is 1397 sufficiently distinguishable from other messages. 1399 The contents of this registry are: 1401 ID: An integer identifier to be used in the 'int-id' attribute of a 1402 metadata/control element. 1404 Message: The text of the message. Messages are listed in the 1405 registry in English; vehicles are expected to implement 1406 translations into languages supported by the vehicle. 1408 When new messages are added to the registry, the message text is 1409 determined by the registrant; IANA assigns the IDs. Each message is 1410 assigned a consecutive integer value as its ID. This allows an IVS 1411 to indicate by a single integer value that it supports all messages 1412 with that value or lower. 1414 The initial set of values is listed in Table 3. 1416 +----+--------------------------------------------------------------+ 1417 | ID | Message | 1418 +----+--------------------------------------------------------------+ 1419 | 1 | Emergency services has noted your information and location, | 1420 | | but cannot speak with you right now. We will help you as | 1421 | | soon as possible. | 1422 +----+--------------------------------------------------------------+ 1424 Table 3: Emergency Call Static Message Registry Initial Values 1426 14.5. Emergency Call Vehicle Lamp ID Registry 1428 This document creates a new sub-registry called "Emergency Call 1429 Vehicle Lamp ID" in the "Emergency Call Metadata/Control Data" 1430 registry established by [I-D.ietf-ecrit-ecall]. This new sub- 1431 registry uniquely identifies the names of automotive lamps (lights). 1432 As defined in [RFC5226], this registry operates under "Expert Review" 1433 rules. The expert should determine that the proposed lamp name is 1434 clearly understandable and is sufficiently distinguishable from other 1435 lamp names. 1437 The contents of this registry are: 1439 Name: The identifier to be used in the 'element-id' attribute of a 1440 metadata/control element. 1442 Description: A description of the lamp (light). 1444 The initial set of values is listed in Table 4. 1446 +----------------+---------------------------------------------+ 1447 | Name | Description | 1448 +----------------+---------------------------------------------+ 1449 | head | The main lamps used to light the road ahead | 1450 | | | 1451 | interior | Interior lamp, often at the top center | 1452 | | | 1453 | fog-front | Front fog lamps | 1454 | | | 1455 | fog-rear | Rear fog lamps | 1456 | | | 1457 | brake | Brake indicator lamps | 1458 | | | 1459 | brake-center | Center High Mounted Stop Lamp | 1460 | | | 1461 | position-front | Front position/parking/standing lamps | 1462 | | | 1463 | position-rear | Rear position/parking/standing lamps | 1464 | | | 1465 | turn-left | Left turn/directional lamps | 1466 | | | 1467 | turn-right | Right turn/directional lamps | 1468 | | | 1469 | hazard | Hazard/four-way lamps | 1470 +----------------+---------------------------------------------+ 1472 Table 4: Emergency Call Lamp ID Registry Initial Values 1474 14.6. Lamp State Registry 1476 This document creates a new sub-registry called "Lamp State" in the 1477 "Emergency Call Metadata/Control Data" registry established by 1478 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1479 the states that lamps (lights) can be placed into. As defined in 1480 [RFC5226], this registry operates under "Expert Review" rules. The 1481 expert should determine that the proposed lamp state is clearly 1482 understandable and is sufficiently distinguishable from other lamp 1483 states. 1485 The contents of this registry are: 1487 Name: The identifier to be used in the 'requested-state' attribute 1488 of a metadata/control element. 1490 Description: A description of state of a lamp (light). 1492 The initial set of values is listed in Table 5. 1494 +-------+----------------------------------------+ 1495 | Name | Description | 1496 +-------+----------------------------------------+ 1497 | on | The lamp is on (illuminated) | 1498 | | | 1499 | off | The lamp is off (extinguished) | 1500 | | | 1501 | flash | The lamp alternates between on and off | 1502 +-------+----------------------------------------+ 1504 Table 5: Lamp State Registry Initial Values 1506 14.7. Emergency Call Vehicle Camera ID Registry 1508 This document creates a new sub-registry called "Emergency Call 1509 Vehicle Camera ID" in the "Emergency Call Metadata/Control Data" 1510 registry established by [I-D.ietf-ecrit-ecall]. This new sub- 1511 registry uniquely identifies automotive cameras. As defined in 1512 [RFC5226], this registry operates under "Expert Review" rules. The 1513 expert should determine that the proposed camera name is clearly 1514 understandable and is sufficiently distinguishable from other camera 1515 names. 1517 The contents of this registry are: 1519 Name: The identifier to be used in the 'element-id' attribute of a 1520 control element. 1522 Description: A description of the camera. 1524 The initial set of values is listed in Table 6. 1526 +-------------+-----------------------------------------------------+ 1527 | Name | Description | 1528 +-------------+-----------------------------------------------------+ 1529 | backup | Shows what is behind the vehicle, e.g., often used | 1530 | | for driver display when the vehicle is in reverse. | 1531 | | Also known as rearview, reverse, rear visibility, | 1532 | | etc. | 1533 | | | 1534 | left-rear | Shows view to the left and behind (e.g., left side | 1535 | | rear-view mirror or blind spot view) | 1536 | | | 1537 | right-rear | Shows view to the right and behind (e.g., right | 1538 | | side rear-view mirror or blind spot view) | 1539 | | | 1540 | forward | Shows what is in front of the vehicle | 1541 | | | 1542 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1543 | | collision detection systems), separate from backup | 1544 | | view | 1545 | | | 1546 | lane | Used by systems to identify road lane and/or | 1547 | | monitor vehicle's position within lane | 1548 | | | 1549 | interior | Shows the interior (e.g., driver) | 1550 | | | 1551 | night-front | Night-vision view of what is in front of the | 1552 | | vehicle | 1553 +-------------+-----------------------------------------------------+ 1555 Table 6: Emergency Call Vehicle Camera ID Registry Initial Values 1557 14.8. The emergencyCallData.eCall.VEDS SIP INFO package 1559 This document registers the 'emergencyCallData.eCall.VEDS' SIP INFO 1560 package. 1562 Both endpoints (the IVS and the PSAP equipment) include 1563 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 1564 [RFC6086] to indicate ability to receive SIP INFO messages carrying 1565 data as described here. 1567 Support for the 'emergencyCallData.eCall.VEDS' SIP INFO package 1568 indicates the ability to receive NG-ACN related body parts as 1569 specified in [TBD: THIS DOCUMENT]. 1571 A SIP INFO request message carrying data related to an emergency call 1572 as described in [TBD: THIS DOCUMENT] has an Info-Package header field 1573 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 1575 The requirements of Section 10 of [RFC6086] are addressed in the 1576 following sections. 1578 14.8.1. Overall Description 1580 This section describes "what type of information is carried in Info 1581 requests associated with the Info Package, and for what types of 1582 applications and functionalities UAs can use the Info Package." 1584 SIP INFO requests associated with the emergencyCallData.eCall.VEDS 1585 SIP INFO package carry data associated with emergency calls as 1586 defined in [TBD: THIS DOCUMENT]. The application is vehicle- 1587 initiated emergency calls established using SIP. The functionality 1588 is to carry vehicle data and metadata/control information between 1589 vehicles and PSAPs. Refer to [TBD: THIS DOCUMENT] for more 1590 information. 1592 14.8.2. Applicability 1594 This section describes "why the Info Package mechanism, rather than 1595 some other mechanism, has been chosen for the specific use-case...." 1597 The use of the SIP INFO method is based on an analysis of the 1598 requirements against the intent and effects of the INFO method versus 1599 other approaches (which included the SIP MESSAGE method, SIP OPTIONS 1600 method, SIP re-INVITE method, media plane transport, and non-SIP 1601 protocols). In particular, the transport of emergency call data 1602 blocks occurs within a SIP emergency dialog, per Section 7, and is 1603 normally carried in the initial INVITE request and its response; the 1604 use of the INFO method only occurs when emergency-call-related data 1605 needs to be sent mid-call. While the SIP MESSAGE method could be 1606 used, it is not tied to a SIP dialog as is the INFO method and thus 1607 might not be associated with the dialog. Both the SIP OPTIONS or re- 1608 INVITE methods could also be used, but is seen as less clean than the 1609 INFO method. The SIP SUBSCRIBE/NOTIFY method could be coerced into 1610 service, but the semantics are not a good fit, e.g., the subscribe/ 1611 notify mechanism provides one-way communication consisting of (often 1612 multiple) notifications from notifier to subscriber indicating that 1613 certain events in notifier have occurred, whereas what's needed here 1614 is two-way communication of data related to the emergency dialog. 1615 Use of the media plane mechanisms was discounted because the number 1616 of messages needing to be exchanged in a dialog is normally zero or 1617 very few, and the size of the data is likewise very small. The 1618 overhead caused by user plane setup (e.g., to use MSRP as transport) 1619 would be disproportionately large. 1621 Based on the the analyses, the SIP INFO method was chosen to provide 1622 for mid-call data transport. 1624 14.8.3. Info Package Name 1626 The SIP INFO package name is emergencyCallData.eCall.VEDS 1628 14.8.4. Info Package Parameters 1630 None 1632 14.8.5. SIP Option-Tags 1634 None 1636 14.8.6. INFO Request Body Parts 1638 The body of an emergencyCallData.eCall.VEDS SIP INFO package is a 1639 multipart body which MAY contain zero or one application/ 1640 emergencyCallData.eCall.VEDS+xml (containing a VEDS data block) part, 1641 zero or more application/emergencyCallData.control+xml (containing a 1642 metadata/control object) parts, and zero or one application/ 1643 emergencyCallData.eCall.MSD+per (containing an MSD) part. At least 1644 one VEDS, MSD, or metadata/control body part is expected; the 1645 behavior upon receiving a SIP INFO request with none is undefined. 1647 The body parts are sent per [RFC6086], and in addition, to align with 1648 with how these body parts are sent in non-INFO messages, each 1649 associated body part is referenced by a Call-Info header field at the 1650 top level of the SIP message. The body part has a Content- 1651 Disposition header field set to "By-Reference". 1653 A VEDS or metadata/control block is always enclosed in a multipart 1654 body part (even if it would otherwise be the only body part in the 1655 SIP message), since as of the date of this document, the use of 1656 Content-ID as a SIP header field is not defined (while it is defined 1657 for use as a MIME header field). The innermost multipart that 1658 contains only body parts associated with the SIP INFO package has a 1659 Content-Disposition value of Info-Package. 1661 Service providers are not expected to add [RFC7852] Additional Data 1662 to SIP INFO requests. 1664 See [TBD: THIS DOCUMENT] for more information. 1666 14.8.7. Info Package Usage Restrictions 1668 Usage is limited to vehicle-initiated emergency calls as defined in 1669 [TBD: THIS DOCUMENT]. 1671 14.8.8. Rate of INFO Requests 1673 The SIP INFO request is used within an established emergency call 1674 dialog for the PSAP to request the IVS to send an updated data set, 1675 and for the IVS to send the requested data set. Because this is 1676 normally done only on manual request of the PSAP call taker (who 1677 suspects some aspect of the vehicle state has changed), the rate of 1678 SIP INFO requests associated with the emergencyCallData.eCall.VEDS 1679 SIP INFO package is normally quite low (most dialogs are likely to 1680 contain zero SIP INFO requests, while others can be expected to carry 1681 an occasional request). 1683 14.8.9. Info Package Security Considerations 1685 The MIME media type registations for the data blocks that can be 1686 carried using this SIP INFO package contains a discussion of the 1687 security and/or privacy considerations specific to that data block. 1688 The "Security Considerations" and "Privacy Considerations" sections 1689 of [TBD: THIS DOCUMENT] discuss security and privacy considerations 1690 of the data carried in vehicle-initiated emergency calls as described 1691 in that document. 1693 14.8.10. Implementation Details 1695 See [TBD: THIS DOCUMENT] for protocol details. 1697 14.8.11. Examples 1699 See [TBD: THIS DOCUMENT] for protocol examples. 1701 15. Acknowledgements 1703 We would like to thank Lena Chaponniere, Alissa Cooper, Stephen Edge, 1704 Christer Holmberg, and Allison Mankin for their review and 1705 suggestions; Robert Sparks and Paul Kyzivat for their help with the 1706 SIP mechanisms; Michael Montag, Arnoud van Wijk, Ban Al-Bakri, Wes 1707 George, Gunnar Hellstrom, and Rex Buddenberg for their feedback; and 1708 Ulrich Dietz for his help with earlier versions of the original 1709 version of this document. 1711 16. Changes from Previous Versions 1713 16.1. Changes from draft-ietf-18 to draft-ietf-19 1715 o Fixed various nits 1717 16.2. Changes from draft-ietf-17 to draft-ietf-18 1719 o Added additional text to "Rate of Info Requests" 1720 o Further corrected "content type" to "media type" 1722 16.3. Changes from draft-ietf-16 to draft-ietf-17 1724 o Clarified that an INFO request is expected to have at least one 1725 VEDS, MSD or metadata/control body part 1726 o Corrected "content type" to "media type" 1728 16.4. Changes from draft-ietf-14 to draft-ietf-15 1730 o Moved VEDS text from Introduction to new Vehicle Data section 1731 o Various clarifications and simplifications 1733 16.5. Changes from draft-ietf-13 to draft-ietf-14 1735 o Body parts now always sent enclosed in multipart (even if only 1736 body part in SIP message) and hence always have a Content- 1737 Disposition of By-Reference 1738 o Fixed typos. 1740 16.6. Changes from draft-ietf-11 to draft-ietf-13 1742 o Fixed typos 1744 16.7. Changes from draft-ietf-10 to draft-ietf-11 1746 o Clarifications suggested by Christer 1747 o Corrections to Content-Disposition text and examples as suggested 1748 by Paul Kyzivat 1749 o Clarifications to Content-Disposition text and examples to clarify 1750 that handling=optional is only used in the initial INVITE 1752 16.8. Changes from draft-ietf-09 to draft-ietf-10 1754 o Fixed errors in examples found by Dale in eCall draft 1755 o Removed enclosing sub-section of INFO package registration section 1756 o Added text per Christer and Dale's suggestions that the MSD and 1757 metadata/control blocks are sent in INFO with a Call-Info header 1758 field referencing them 1759 o Other text changes per comments received from Christer and Ivo 1760 against eCall draft. 1762 16.9. Changes from draft-ietf-08 to draft-ietf-09 1764 o Added INFO package registration for eCall.VEDS 1765 o Moved element and other extension points back to 1766 eCall document so that extension points are in base spec (and also 1767 to get XML schema to compile) 1768 o Text changes for clarification. 1770 16.10. Changes from draft-ietf-07 to draft-ietf-08 1772 o Moved much of the metadata/control object from 1773 [I-D.ietf-ecrit-ecall] to this document as extensions 1774 o Editorial clarifications and simplifications 1775 o Moved "Call Routing" to be a subsection of "Call Setup" 1776 o Deleted "Profile" section and moved some of its text into 1777 "Introduction" 1779 16.11. Changes from draft-ietf-06 to draft-ietf-07 1781 o Minor editorial changes 1783 16.12. Changes from draft-ietf-05 to draft-ietf-06 1785 o Added clarifying text regarding signed and encrypted data 1786 o Additional informative text in "Migration to Next-Generation" 1787 section 1788 o Additional clarifying text regarding security and privacy. 1790 16.13. Changes from draft-ietf-04 to draft-ietf-05 1792 o Reworded security text in main document and in MIME registration 1793 for the VEDS object 1795 16.14. Changes from draft-ietf-03 to draft-ietf-04 1797 o Added example VEDS object 1798 o Additional clarifications and corrections 1799 o Removed references from Abstract 1800 o Moved Document Scope section to follow Introduction 1802 16.15. Changes from draft-ietf-02 to draft-ietf-03 1804 o Additional clarifications and corrections 1806 16.16. Changes from draft-ietf-01 to draft-ietf-02 1808 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1809 aspects including the service URN; this document no longer 1810 proposes a unique service URN for non-eCall NG-ACN calls; the same 1811 service URN is now used for all NG-ACN calls including NG-eCall 1812 and non-eCall 1813 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1814 support it 1815 o Minor wording improvements and clarifications 1817 16.17. Changes from draft-ietf-00 to draft-ietf-01 1819 o Added further discussion of test calls 1820 o Added further clarification to the document scope 1821 o Mentioned that multi-region vehicles may need to support other 1822 crash notification specifications such as eCall 1823 o Minor wording improvements and clarifications 1825 16.18. Changes from draft-gellens-02 to draft-ietf-00 1827 o Renamed from draft-gellens- to draft-ietf- 1828 o Added text to Introduction to clarify that during a CS ACN, the 1829 PSAP call taker usually needs to listen to the data and transcribe 1830 it 1832 16.19. Changes from draft-gellens-01 to -02 1834 o Fixed case of 'EmergencyCallData', in accordance with changes to 1835 [RFC7852] 1837 16.20. Changes from draft-gellens-00 to -01 1839 o Now using 'EmergencyCallData' for purpose parameter values and 1840 MIME subtypes, in accordance with changes to [RFC7852] 1841 o Added reference to RFC 6443 1842 o Fixed bug that caused Figure captions to not appear 1844 17. References 1846 17.1. Normative References 1848 [I-D.ietf-ecrit-ecall] 1849 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1850 European eCall", draft-ietf-ecrit-ecall-20 (work in 1851 progress), November 2016. 1853 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1854 Requirement Levels", BCP 14, RFC 2119, 1855 DOI 10.17487/RFC2119, March 1997, 1856 . 1858 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1859 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1860 DOI 10.17487/RFC5226, May 2008, 1861 . 1863 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1864 Initiation Protocol (SIP) INFO Method and Package 1865 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1866 . 1868 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 1869 Specifications and Registration Procedures", BCP 13, 1870 RFC 6838, DOI 10.17487/RFC6838, January 2013, 1871 . 1873 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1874 Communications Services in Support of Emergency Calling", 1875 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1876 . 1878 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 1879 DOI 10.17487/RFC7303, July 2014, 1880 . 1882 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1883 J. Winterbottom, "Additional Data Related to an Emergency 1884 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1885 . 1887 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1888 NENA Data Standardization Workgroup, , "Vehicular 1889 Emergency Data Set (VEDS) version 3", July 2012, 1890 . 1893 17.2. Informative references 1895 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1896 Emergency Context Resolution with Internet Technologies", 1897 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1898 . 1900 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1901 Shanmugam, "Security Threats and Requirements for 1902 Emergency Call Marking and Mapping", RFC 5069, 1903 DOI 10.17487/RFC5069, January 2008, 1904 . 1906 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1907 "Framework for Emergency Calling Using Internet 1908 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1909 2011, . 1911 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1912 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1913 December 2014, . 1915 [triage-2008] 1916 National Center for Injury Prevention and Control, and 1917 Centers for Disease Control and Prevention, 1918 "Recommendations from the Expert Panel: Advanced Automatic 1919 Collision Notification and Triage of the Injured Patient", 1920 2008, . 1922 [triage-2011] 1923 National Center for Injury Prevention and Control, and 1924 Centers for Disease Control and Prevention, "Guidelines 1925 for field triage of injured patients: recommendations of 1926 the National Expert Panel on Field Triage", January 2012, 1927 . 1932 Authors' Addresses 1934 Randall Gellens 1935 Core Technology Consulting 1937 Email: rg+ietf@randy.pensive.org 1939 Brian Rosen 1940 NeuStar, Inc. 1941 470 Conrad Dr 1942 Mars, PA 16046 1943 US 1945 Email: br@brianrosen.net 1946 Hannes Tschofenig 1947 Individual 1949 Email: Hannes.Tschofenig@gmx.net 1950 URI: http://www.tschofenig.priv.at