idnits 2.17.1 draft-ietf-ecrit-car-crash-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 807 has weird spacing: '...dynamic displ...' == Line 810 has weird spacing: '... honk sound...' == Line 812 has weird spacing: '... lamp turns...' == Line 814 has weird spacing: '...-camera adds ...' -- The document date (August 1, 2016) is 2825 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4119' is defined on line 1734, but no explicit reference was found in the text == Unused Reference: 'RFC5031' is defined on line 1742, but no explicit reference was found in the text == Unused Reference: 'RFC5491' is defined on line 1752, but no explicit reference was found in the text == Unused Reference: 'RFC5962' is defined on line 1758, but no explicit reference was found in the text == Outdated reference: A later version (-27) exists of draft-ietf-ecrit-ecall-10 ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) ** Downref: Normative reference to an Informational RFC: RFC 6443 -- Possible downref: Non-RFC (?) normative reference: ref. 'VEDS' Summary: 5 errors (**), 0 flaws (~~), 10 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: February 2, 2017 NeuStar, Inc. 6 H. Tschofenig 7 Individual 8 August 1, 2016 10 Next-Generation Vehicle-Initiated Emergency Calls 11 draft-ietf-ecrit-car-crash-09.txt 13 Abstract 15 This document describes how to use IP-based emergency services 16 mechanisms to support the next generation of emergency calls placed 17 by vehicles (automatically in the event of a crash or serious 18 incident, or manually invoked by a vehicle occupant) and conveying 19 vehicle, sensor, and location data related to the crash or incident. 20 Such calls are often referred to as "Automatic Crash Notification" 21 (ACN), or "Advanced Automatic Crash Notification" (AACN), even in the 22 case of manual trigger. The "Advanced" qualifier refers to the 23 ability to carry a richer set of data. 25 This document also registers a MIME Content Type and Emergency Call 26 Additional Data Block for the vehicle, sensor, and location data 27 (often referred to as "crash data" even though there is not 28 necessarily a crash). An external specification for the data format, 29 contents, and structure are referenced in this document. 31 This document reuses the technical aspects of next-generation pan- 32 European eCall (a mandated and standardized system for emergency 33 calls by in-vehicle systems within Europe and other regions). 34 However, this document specifies a different set of vehicle (crash) 35 data, specifically, the Vehicle Emergency Data Set (VEDS) rather than 36 the eCall Minimum Set of Data (MSD). This document is an extension 37 of the eCall document, with the primary differences being that this 38 document makes the MSD data set optional and VEDS mandatory, and adds 39 attribute values to the eCall metadata/control object to permit 40 greater functionality. This document registers a new INFO package 41 (identical to that registered for eCall but with the addition of the 42 VEDS MIME type). This document also describes legacy (circuit- 43 switched) ACN systems and their migration to next-generation 44 emergency calling, to provide background information and context. 46 Status of This Memo 48 This Internet-Draft is submitted in full conformance with the 49 provisions of BCP 78 and BCP 79. 51 Internet-Drafts are working documents of the Internet Engineering 52 Task Force (IETF). Note that other groups may also distribute 53 working documents as Internet-Drafts. The list of current Internet- 54 Drafts is at http://datatracker.ietf.org/drafts/current/. 56 Internet-Drafts are draft documents valid for a maximum of six months 57 and may be updated, replaced, or obsoleted by other documents at any 58 time. It is inappropriate to use Internet-Drafts as reference 59 material or to cite them other than as "work in progress." 61 This Internet-Draft will expire on February 2, 2017. 63 Copyright Notice 65 Copyright (c) 2016 IETF Trust and the persons identified as the 66 document authors. All rights reserved. 68 This document is subject to BCP 78 and the IETF Trust's Legal 69 Provisions Relating to IETF Documents 70 (http://trustee.ietf.org/license-info) in effect on the date of 71 publication of this document. Please review these documents 72 carefully, as they describe your rights and restrictions with respect 73 to this document. Code Components extracted from this document must 74 include Simplified BSD License text as described in Section 4.e of 75 the Trust Legal Provisions and are provided without warranty as 76 described in the Simplified BSD License. 78 Table of Contents 80 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 81 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 82 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 8 83 4. Overview of Legacy Deployment Models . . . . . . . . . . . . 8 84 5. Migration to Next-Generation . . . . . . . . . . . . . . . . 10 85 6. Data Transport . . . . . . . . . . . . . . . . . . . . . . . 13 86 7. Call Setup . . . . . . . . . . . . . . . . . . . . . . . . . 14 87 8. Call Routing . . . . . . . . . . . . . . . . . . . . . . . . 15 88 9. New Metadata/Control Values . . . . . . . . . . . . . . . . . 16 89 9.1. New values for the 'action' attribute' . . . . . . . . . 17 90 9.2. Request Example . . . . . . . . . . . . . . . . . . . . . 18 91 9.3. The element . . . . . . . . . . . . . . . . . . . . 18 92 9.4. The element . . . . . . . . . . . . . . . 19 93 10. Test Calls . . . . . . . . . . . . . . . . . . . . . . . . . 20 94 11. The emergencyCallData.eCall.VEDS INFO package . . . . . . . . 21 95 11.1. INFO Package Requirements . . . . . . . . . . . . . . . 22 96 12. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 97 13. Security Considerations . . . . . . . . . . . . . . . . . . . 29 98 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 29 99 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 100 15.1. MIME Content-type Registration for 101 'application/EmergencyCall.VEDS+xml' . . . . . . . . . . 30 102 15.2. Registration of the 'VEDS' entry in the Emergency Call 103 Additional Data registry . . . . . . . . . . . . . . . . 31 104 15.3. New Action Values . . . . . . . . . . . . . . . . . . . 32 105 15.4. Static Message Registry . . . . . . . . . . . . . . . . 32 106 15.5. Lamp ID Registry . . . . . . . . . . . . . . . . . . . . 33 107 15.6. Camera ID Registry . . . . . . . . . . . . . . . . . . . 34 108 16. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 35 109 17. Changes from Previous Versions . . . . . . . . . . . . . . . 35 110 17.1. Changes from draft-ietf-08 to draft-ietf-09 . . . . . . 35 111 17.2. Changes from draft-ietf-07 to draft-ietf-08 . . . . . . 36 112 17.3. Changes from draft-ietf-06 to draft-ietf-07 . . . . . . 36 113 17.4. Changes from draft-ietf-05 to draft-ietf-06 . . . . . . 36 114 17.5. Changes from draft-ietf-04 to draft-ietf-05 . . . . . . 36 115 17.6. Changes from draft-ietf-03 to draft-ietf-04 . . . . . . 36 116 17.7. Changes from draft-ietf-02 to draft-ietf-03 . . . . . . 36 117 17.8. Changes from draft-ietf-01 to draft-ietf-02 . . . . . . 36 118 17.9. Changes from draft-ietf-00 to draft-ietf-01 . . . . . . 37 119 17.10. Changes from draft-gellens-02 to draft-ietf-00 . . . . . 37 120 17.11. Changes from draft-gellens-01 to -02 . . . . . . . . . . 37 121 17.12. Changes from draft-gellens-00 to -01 . . . . . . . . . . 37 122 18. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 123 18.1. Normative References . . . . . . . . . . . . . . . . . . 37 124 18.2. Informative references . . . . . . . . . . . . . . . . . 39 125 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 127 1. Terminology 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 130 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 131 document are to be interpreted as described in [RFC2119]. 133 This document re-uses terminology defined in Section 3 of [RFC5012]. 135 Additionally, we use the following abbreviations: 137 +--------+----------------------------------------------------------+ 138 | Term | Expansion | 139 +--------+----------------------------------------------------------+ 140 | 3GPP | 3rd Generation Partnership Project | 141 | AACN | Advanced Automatic Crash Notification | 142 | ACN | Automatic Crash Notification | 143 | APCO | Association of Public-Safety Communications Officials | 144 | EENA | European Emergency Number Association | 145 | ESInet | Emergency Services IP network | 146 | GNSS | Global Navigation Satellite System (which includes | 147 | | various systems such as the Global Positioning System or | 148 | | GPS) | 149 | IVS | In-Vehicle System | 150 | MNO | Mobile Network Operator | 151 | MSD | eCall Minimum Set of Data | 152 | NENA | National Emergency Number Association | 153 | POTS | Plain Old Telephone Service (normal, circuit-switched | 154 | | voice calls) | 155 | PSAP | Public Safety Answering Point | 156 | TSP | Telematics Service Provider | 157 | VEDS | Vehicle Emergency Data Set | 158 +--------+----------------------------------------------------------+ 160 2. Introduction 162 Emergency calls made by in-vehicle systems (e.g., automatically in 163 the event of a crash or serious incident or manually by a vehicle 164 occupant) assist in significantly reducing road deaths and injuries 165 by allowing emergency services to respond quickly and appropriately 166 to the specifics of the incident, often with better location 167 accuracy. 169 Drivers often have a poor location awareness, especially outside of 170 major cities, at night and when away from home (especially abroad). 171 In the most crucial cases, the victim(s) might not be able to call 172 because they have been injured or trapped. 174 For more than two decades, some vehicles have been equipped with 175 telematics systems which, among other features, place an emergency 176 call automatically in the event of a crash or manually in response to 177 an emergency call button. Such systems generally have on-board 178 location determination systems that make use of satellite-based 179 positioning technology, inertial sensors, gyroscopes, etc., which can 180 provide an accurate position for the vehicle. Such built-in systems 181 can take advantage of the benefits of being integrated into a 182 vehicle, such as more power capacity, ability to have larger or 183 specialized antenna, ability to be engineered to avoid or minimise 184 degradation by vehicle glass coatings, interference from other 185 vehicle systems, etc. Thus, the PSAP can be provided with a good 186 estimate of where the vehicle is during an emergency. Vehicle 187 manufacturers are increasingly adopting such systems, both for the 188 safety benefits and for the additional features and services they 189 enable (e.g., remote engine diagnostics, remote door unlock, stolen 190 vehicle tracking and disabling, etc.). 192 The general term for such systems is Automatic Crash Notification 193 (ACN) or "Advanced Automatic Crash Notification" (AACN). "ACN" is 194 used in this document as a general term. ACN systems transmit some 195 amount of data specific to the incident, referred to generally as 196 "crash data" (the term is commonly used even though there might not 197 have been a crash). While different systems transmit different 198 amounts of crash data, standardized formats, structures, and 199 mechanisms are needed to provide interoperability among systems and 200 PSAPs. 202 As of the date of this document, currently deployed in-vehicle 203 telematics systems are circuit-switched and lack a standards-based 204 ability to convey crash data directly to the PSAP (generally relying 205 on either a human advisor or an automated text-to-speech system to 206 provide the PSAP call taker with some crash data orally, or in some 207 cases via a proprietary mechanism). In most cases, the PSAP call 208 taker needs to first realize that the call is related to a vehicle 209 incident, and then listen to the data and transcribe it. Circuit- 210 switched ACN systems are referred to here as CS-ACN. 212 The transition to next-generation calling in general, and for 213 emergency calling in particular, provides an opportunity to vastly 214 improve the scope, breadth, reliability and usefulness of crash data 215 during an emergency by allowing it to be transmitted during call set- 216 up, and to be automatically processed by the PSAP and made available 217 to the call taker in an integrated, automated way, as well as provide 218 the ability for a PSAP call taker to request that a vehicle take 219 certain actions, such as flashing lights or unlocking doors. In 220 addition, vehicle manufacturers are provided an opportunity to take 221 advantage of the same standardized mechanisms for data transmission 222 and request processing for internal use if they wish (such as 223 telemetry between the vehicle and a service center for both emergency 224 and non-emergency uses, including location-based services, multi- 225 media entertainment systems, remote door unlocking, and road-side 226 assistance applications). 228 Next-generation ACN provides an opportunity for such calls to be 229 recognized and processed as such during call set-up, and routed to an 230 equipped PSAP where the vehicle data is available to assist the call 231 taker in assessing and responding to the situation. Next-generation 232 (IP-based) ACN systems are referred to here as NG-ACN. 234 An ACN call can be initiated by a vehicle occupant or automatically 235 initiated by vehicle systems in the event of a serious incident. 236 (The "A" in "ACN" does stand for "Automatic," but the term is broadly 237 used to refer to the class of calls that are placed by an in-vehicle 238 system (IVS) or Telematics Service Providers (TSP) and that carry 239 incident-related data as well as voice.) Automatically triggered 240 calls indicate a car crash or some other serious incident (e.g., a 241 fire). Manually triggered calls are often reports of observed 242 crashes or serious hazards (such as impaired drivers or roadway 243 debris). In some implementations, manually triggered calls might be 244 more likely to be accidental. 246 This document describes how the IETF mechanisms for IP-based 247 emergency calls, including [RFC6443] and [RFC7852], are used to 248 provide the realization of next-generation ACN. 250 This document reuses the technical aspects of next-generation pan- 251 European eCall (a mandated and standardized system for emergency 252 calls by in-vehicle systems within Europe and other regions), as 253 described in [I-D.ietf-ecrit-ecall]. However, this document 254 specifies a different set of vehicle (crash) data, specifically, the 255 Vehicle Emergency Data Set (VEDS) rather than the eCall Minimum Set 256 of Data (MSD). This document is an extension of 257 [I-D.ietf-ecrit-ecall], with the differences being that this document 258 makes the MSD data set optional and VEDS mandatory, and adds new 259 attribute values to the eCall metadata/control object defined in that 260 document. This document also registers a new INFO package (identical 261 to that defined in [I-D.ietf-ecrit-ecall] with the addition of the 262 VEDS MIME type). 264 The Association of Public-Safety Communications Officials (APCO) and 265 the National Emergency Number Association (NENA) have jointly 266 developed a standardized set of incident-related vehicle data for ACN 267 use, called the Vehicle Emergency Data Set (VEDS) [VEDS]. Such data 268 is often referred to as crash data although it is applicable in 269 incidents other than crashes. 271 VEDS provides a standard data set for the transmission, exchange, and 272 interpretation of vehicle-related data. A standard data format 273 allows the data to be generated by an IVS or TSP and interpreted by 274 PSAPs, emergency responders, and medical facilities. It includes 275 incident-related information such as airbag deployment, location and 276 compass orientation of the vehicle, spatial orientation of the 277 vehicle (e.g., upright, on its side or top or a bumper), various 278 sensor data that can indicate the potential severity of the crash and 279 the likelihood of severe injuries to the vehicle occupants, etc. 280 This data better informs the PSAP and emergency responders as to the 281 type of response that might be needed. Some of this information has 282 been included in U.S. government guidelines for field triage of 283 injured patients [triage-2008] [triage-2011]. These guidelines are 284 designed to help responders identify the potential existence of 285 severe internal injuries and to make critical decisions about how and 286 where a patient needs to be transported. 288 This document registers the 'application/EmergencyCallData.VEDS+xml' 289 MIME content-type, and registers the 'VEDS' entry in the Emergency 290 Call Additional Data registry. 292 VEDS is an XML structure (see [VEDS]) transported in SIP using the 293 'application/EmergencyCallData.VEDS+xml' MIME content-type.. 295 VEDS is a versatile structure that can accomodate varied needs. 296 However, if additional sets of data are determined to be needed 297 (e.g., in the future or in different regions), the steps to enable 298 each data block are very briefly summarized below: 300 o A standardized format and encoding (such as XML) is defined and 301 published by a Standards Development Organization (SDO) 303 o A MIME Content-Type is registered for it (typically under the 304 'Application' media type) with a sub-type starting with 305 'EmergencyCallData.' 307 o An entry for the block is added to the Emergency Call Additional 308 Data Blocks sub-registry (established by [RFC7852]); the registry 309 entry is the root of the MIME sub-type (not including the 310 'EmergencyCallData' prefix and any suffix such as '+xml') 312 o A new INFO package is registered that permits carrying the new 313 content type and the metadata/control object (defined in 314 [I-D.ietf-ecrit-ecall]) in INFO messages. 316 Section 6 describes how VEDA data and metadata/control are 317 transported within NG-ACN calls. Section 7 describes how such calls 318 are places. 320 These mechanisms are thus used to place emergency calls that are 321 identifiable as ACN calls and that carry standardized crash data in 322 an interoperable way. 324 Calls by in-vehicle systems are placed via cellular networks, which 325 might ignore location information sent by an originating device in an 326 emergency call INVITE, instead attaching their own location 327 information (often determined in cooperation with the originating 328 device). Standardized crash data structures often include location 329 as determined by the IVS. A benefit of this is that it allows the 330 PSAP to see both the location as determined by the cellular network 331 (often in cooperation with the originating device) and the location 332 as determined by the IVS. 334 This specification inherits the ability to utilize test call 335 functionality from Section 15 of [RFC6881]. 337 3. Document Scope 339 This document is focused on how an ACN emergency call is setup and 340 incident-related data (including vehicle, sensor, and location data) 341 is transmitted to the PSAP using IETF specifications. For the direct 342 model, this is the end-to-end description (between the vehicle and 343 the PSAP). For the TSP model, this describes the call leg between 344 the TSP and the PSAP, leaving the call leg between the vehicle and 345 the TSP up to the entities involved (i.e., IVS and TSP vendors) who 346 are then free to use the same mechanism as for the right-hand side or 347 not. 349 Note that Europe has a mandated and standardized system for emergency 350 calls by in-vehicle systems. This pan-European system is known as 351 "eCall" and is the subject of a separate document, 352 [I-D.ietf-ecrit-ecall], which this document builds on. Vehicles 353 designed to operate in multiple regions might need to support eCall 354 as well as NG-ACN as described here. A vehicle IVS might determine 355 whether to use eCall or ACN by first determining the region or 356 country in which it is located (e.g., from a GNSS location fix and/or 357 identity of or information from an MNO). If other regions adopt 358 other data formats, a multi-region vehicle might need to support 359 those as well. This document adopts the call set-up and other 360 technical aspects of [I-D.ietf-ecrit-ecall], which uses [RFC7852]; 361 this makes it straightforward to use a different data set while 362 keeping other technical aspects unchanged. Hence, both NG-eCall and 363 the NG-ACN mechanism described here are compatible, differing 364 primarily in the specific data block that is sent (the eCall MSD in 365 the case of NG-eCall, and the APCO/NENA VEDS used in this document), 366 and some additions to the metadata/control data block. If other 367 regions adopt their own vehicle data sets, this can be similarly 368 accomodated without changing other technical aspects. Note that any 369 additional data blocks require a new INFO package to permit transport 370 within INFO messages. 372 4. Overview of Legacy Deployment Models 374 Legacy (circuit-switched) systems for placing emergency calls by in- 375 vehicle systems generally have some ability to convey at least 376 location and in some cases telematics data to the PSAP. Most such 377 systems use one of three architectural models, which are described 378 here as: "Telematics Service Provider" (TSP), "direct", and "paired". 379 These three models are illustrated below. 381 In the TSP model, both emergency and non-emergency calls are placed 382 to a Telematics Service Provider (TSP); a proprietary technique is 383 used for data transfer (such as a proprietary in-band modem) between 384 the TSP and the vehicle. 386 In an emergency, generally the TSP call taker bridges in the PSAP and 387 communicates location, crash data (such as impact severity and trauma 388 prediction), and other data (such as the vehicle description) to the 389 PSAP call taker verbally (in some cases, a proprietary out-of-band 390 interface is used). Since the TSP knows the location of the vehicle 391 (from on-board GNSS and sensors), location-based routing is usually 392 used to route to the appropriate PSAP. In some cases, the TSP is 393 able to transmit location automatically, using similar techniques as 394 for wireless calls. Typically, a three-way voice call is established 395 between the vehicle, the TSP, and the PSAP, allowing communication 396 between the PSAP call taker, the TSP call taker, and the vehicle 397 occupants (who might be unconscious). 399 ///----\\\ proprietary +------+ 911 trunk or POTS +------+ 400 ||| IVS |||-------------->+ TSP +------------------->+ PSAP | 401 \\\----/// crash data +------+ location via trunk +------+ 403 Figure 1: Legacy TSP Model. 405 In the paired model, the IVS uses a Bluetooth link with a previously- 406 paired handset to establish an emergency call with the PSAP (by 407 dialing a standard emergency number; 9-1-1 in North America), and 408 then communicates location data to the PSAP via text-to-speech; crash 409 data might or might not be conveyed also using text-to-speech. Some 410 such systems use an automated voice prompt menu for the PSAP call 411 taker (e.g., "this is an automatic emergency call from a vehicle; 412 press 1 to open a voice path to the vehicle; press 2 to hear the 413 location read out") to allow the call taker to request location data 414 via text-to-speech. 416 +---+ 417 ///----\\\ | H | 911/etc voice call via handset +------+ 418 ||| IVS |||-->| S +----------------------------------->+ PSAP | 419 \\\----/// +---+ location via text-to-speech +------+ 421 Figure 2: Legacy Paired Model 423 In the direct model, the IVS directly places an emergency call with 424 the PSAP by dialing a standard emergency number (9-1-1 in North 425 America). Such systems might communicate location data to the PSAP 426 via text-to-speech; crash data might or might not be conveyed using 427 text-to-speech. Some such systems use an automated voice prompt menu 428 (e.g., "this is an automatic emergency call from a vehicle; press 1 429 to open a voice path to the vehicle; press 2 to hear the location 430 read out") to allow the call taker to request location data via text- 431 to-speech. 433 ///----\\\ 911/etc voice call via IVS +------+ 434 ||| IVS |||---------------------------------------->+ PSAP | 435 \\\----/// location via text-to-speech +------+ 437 Figure 3: Legacy Direct Model 439 5. Migration to Next-Generation 441 Migration of emergency calls placed by in-vehicle systems to next- 442 generation (all-IP) technology per this document provides a 443 standardized mechanism to identify such calls and to present crash 444 data with the call, as well as enabling additional communications 445 modalities and enhanced functionality. This allows ACN calls and 446 crash data to be automatically processed by the PSAP and made 447 available to the call taker in an integrated, automated way. Because 448 the crash data is carried in the initial SIP INVITE (per [RFC7852]) 449 the PSAP can present it to the call taker simultaneously with the 450 appearance of the call. The PSAP can also process the data to take 451 other actions (e.g., if multiple calls from the same location arrive 452 when the PSAP is busy and a subset of them are NG-ACN calls, a PSAP 453 might choose to store the information and reject the calls, since the 454 IVS will receive confirmation that the information has been 455 successfully received; a PSAP could also choose to include a message 456 stating that it is aware of the incident and responders are on the 457 way; a PSAP could call the vehicle back when a call taker is 458 available). 460 Origination devices and networks, PSAPs, emergency services networks, 461 and other telephony environments are migrating to next-generation. 462 This provides opportunities for significant enhancement to 463 interoperability and functionality, especially for emergency calls 464 carrying additional data such as vehicle crash data. (In the U.S., a 465 network specifically for emergency responders is being developed. 466 This network, FirstNet, will be next-generation from the start, 467 enhancing the ability for data exchange between PSAPs and 468 responders.) 469 Migration to next-generation (NG) provides an opportunity to 470 significantly improve the handling and response to vehicle-initiated 471 emergency calls. Such calls can be recognized as originating from a 472 vehicle, routed to a PSAP equipped both technically and operationally 473 to handle such calls, and the vehicle-determined location and crash 474 data can be made available to the call taker simultaneously with the 475 call appearance. The PSAP can take advantage of enhanced 476 functionality, including the ability to request the vehicle to take 477 an action, such as sending an updated set of data, converying a 478 message to the occupants, flashing lights, unlocking doors, etc. 480 Vehicle manufacturers using the TSP model can choose to take 481 advantage of the same mechanism to carry telematics data and requests 482 and responses between the vehicle and the TSP for both emergency and 483 non-emergency calls as are used for the interface with the PSAP. 485 A next-generation IVS establishes an emergency call using the 486 emergency call solution as described in [RFC6443] and [RFC6881], with 487 the difference that the Request-URI indicates an ACN type of 488 emergency call, the IVS typically does not perform routing or 489 location queries but relies on the carrier for this, and uses Call- 490 Info header fields to indicates that vehicle crash and capabilities 491 data is attached. When an ESInet is deployed, the MNO only needs to 492 recognize the call as an emergency call and route it to an ESInet. 493 The ESInet can recognize the call as an ACN with vehicle data and can 494 route the call to an NG-ACN capable PSAP. Such a PSAP can interpret 495 the vehicle data sent with the call and make it available to the call 496 taker. 498 [I-D.ietf-ecrit-ecall] registers new service URN children within the 499 "sos" subservice. These URNs request NG-ACN resources, and 500 differentiate between manually and automatically triggered NG-ACN 501 calls (which might be subject to different treatment depending on 502 policy). The two service URNs registered in [I-D.ietf-ecrit-ecall] 503 are "urn:service:sos.ecall.automatic" and 504 "urn:service:sos.ecall.manual". The same service URNs are used for 505 ACN as for eCall since in any region only one of these is supported, 506 making a distinction unnecessary. (Further, PSAP equipment might 507 support multiple data formats, allowing a PSAP to handle a vehicle 508 that erroneously sent the wrong data object.) 510 Note that in North America, routing queries performed by clients 511 outside of an ESInet typically treat all sub-services of "sos" 512 identically to "sos" with no sub-service. However, the Request-URI 513 header field retains the full sub-service; route and handling 514 decisions within an ESInet or PSAP can take the sub-service into 515 account. For example, in a region with multiple cooperating PSAPs, 516 an NG-ACN call might be routed to a PSAP that is NG-ACN capable, or 517 one that specializes in vehicle-related incidents. 519 Migration of the three architectural models to next-generation (all- 520 IP) is described below. 522 In the TSP model, the IVS transmits crash and location data to the 523 TSP either by re-using the mechanisms and data objects described 524 here, or using a proprietary mechanism. In an emergency, the TSP 525 bridges in the PSAP and the TSP transmits crash and other data to the 526 PSAP using the mechanisms and data objects described here. There is 527 a three-way call between the vehicle, the TSP, and the PSAP, allowing 528 communication between the PSAP call taker, the TSP call taker, and 529 the vehicle occupants (who might be unconscious). The TSP relays 530 PSAP requests and vehicle responses. 532 proprietary 533 ///----\\\ or standard +------+ standard +------+ 534 ||| IVS ||| ------------------->+ TSP +------------------->+ PSAP | 535 \\\----/// crash + other data +------+ crash + other data +------+ 537 Figure 4: Next-Generation TSP Model 539 The vehicle manufacturer and the TSP can choose to use the same 540 mechanisms and data objects on the left call leg in Figure 4 as on 541 the right. (Note that the TSP model can be more difficult when the 542 vehicle is in a different country than the TSP (e.g., a US resident 543 driving in Canada or Mexico) because of the additional complexity in 544 choosing the correct PSAP based on vehicle location performed by a 545 TSP in a different country.) 547 In the direct model, the IVS communicates crash data to the PSAP 548 directly using the mechanisms and data objects described here. 550 ///----\\\ NG emergency call +------+ 551 ||| IVS |||----------------------------------------->+ PSAP | 552 \\\----/// crash + other data +------+ 554 Figure 5: Next-Generation Direct Model 556 In the paired model, the IVS uses a Bluetooth link to a previously- 557 paired handset to establish an emergency call with the PSAP; it is 558 undefined what facilities are or will be available for transmitting 559 crash data through the Bluetooth link to the handset for inclusion in 560 an NG emergency call. Hence, manufacturers that use the paired model 561 for legacy calls might choose to adopt either the direct or TSP 562 models for next-generation calls. 564 +---+ 565 ///----\\\ (undefined) | H | standard +------+ 566 ||| IVS |||------------------>| S +------------------->+ PSAP | 567 \\\----/// (undefined) +---+ crash + other data +------+ 569 Figure 6: Next-Generation Paired Model 571 If the call is routed to a PSAP that is not capable of processing the 572 vehicle data, the PSAP ignores (or does not receive) the vehicle 573 data. This is detectable by the IVS or TSP when the status response 574 to the INVITE (e.., 200 OK) lacks an eCall control structure 575 acknowledging receipt of the data [I-D.ietf-ecrit-ecall]. The IVS or 576 TSP then proceeds as it would for a CS-ACN call (e.g., verbal 577 conveyance of data) 579 6. Data Transport 581 [RFC7852] establishes a general mechanism for attaching blocks of 582 data to a SIP emergency call. This mechanism permits certain 583 emergency call MIME types to be attached to SIP messages. This 584 document makes use of that mechanism. 586 An In-Vehicle System (IVS) transmits a VEDS data block (see [VEDS]) 587 by attaching it to a SIP message as a MIME body part per [RFC7852]. 588 The body part is identified by its MIME content-type ('application/ 589 emergencyCallData.eCall.VEDS+xml') in the Content-Type header field 590 of the body part. The body part is assigned a unique identifier 591 which is listed in a Content-ID header field in the body part. The 592 SIP message is marked as containing the VEDS data by adding (or 593 appending to) a Call-Info header field at the top level of the SIP 594 message. This Call-Info header field contains a CID URL referencing 595 the body part's unique identifier, and a 'purpose' parameter 596 identifying the data as a VEDS data block per the Emergency Call 597 Additional Data Blocks registry entry; the 'purpose' parameter's 598 value is 'emergencyCallData.VEDS'. 600 A PSAP or IVS transmits a metadata/control object (see 601 [I-D.ietf-ecrit-ecall]) by attaching it to a SIP message as a MIME 602 body part per [RFC7852]. The body part is identified by its MIME 603 content-type ('application/emergencyCallData.eCall.control+xml') in 604 the Content-Type header field of the body part. The body part is 605 assigned a unique identifier which is listed in a Content-ID header 606 field in the body part. The SIP message is marked as containing the 607 metadata/control block by adding (or appending to) a Call-Info header 608 field at the top level of the SIP message. This Call-Info header 609 field contains a CID URL referencing the body part's unique 610 identifier, and a 'purpose' parameter identifying the data as a 611 metadata/control block per the Emergency Call Additional Data Blocks 612 registry entry; the 'purpose' parameter's value is 613 'emergencyCallData.eCall.control'. 615 An In-Vehicle System (IVS) initiating an NG-ACN call includes in the 616 initial INVITE a VEDS data block and a metadata/control object 617 informing the PSAP of its capabilities. The PSAP creates a metadata/ 618 control object acknowledging receipt of the VEDS data and includes it 619 to the SIP response to the INVITE. 621 A PSAP can request the vehicle to send an updated VEDS data block 622 during a call. The PSAP creates a metadata/control object requesting 623 the VEDS data and attaches it to a SIP INFO message which it sends 624 within the dialog. The IVS then attaches an updated VEDS data to a 625 SIP INFO message and sends it within the dialog. The metadata/ 626 control object and the VEDS are attached to an INFO message in the 627 same way they are attached to other messages (such as the INVITE and 628 the reply to the INVITE as discussed above). INFO messages are sent 629 using an appropriate INFO Package. See Section 11 for more 630 information. 632 When data is being carried in an INFO request message, the body part 633 also carries a Content-Disposition header field set to "Info- 634 Package". 636 7. Call Setup 638 A next-generation In-Vehicle System (IVS) initiates an NG-ACN call 639 with a SIP INVITE using one of the SOS sub-services 640 "SOS.ecall.automatic" or "SOS.ecall.manual" in the Request-URI, 641 standard sets of crash data and capabilities data encoded in 642 standardized and registered formats, attached as additional data 643 blocks as specified in Section 4.1 of [RFC7852]. As described in 644 that document, each data block is identified by its MIME content- 645 type, and pointed to by a CID URL in a Call-Info header with a 646 'purpose' parameter value corresponding to the data block. 648 If new data blocks are needed (e.g., in other regions or in the 649 future), the steps required during standardization are briefly 650 summarized below: 652 o A set of data is standardized by an SDO or appropriate 653 organization 655 o A MIME Content-Type for the crash data set is registered with IANA 657 * If the data is specifically for use in emergency calling, the 658 MIME type is normally under the 'application' type with a 659 subtype starting with 'EmergencyCallData.' 661 * If the data format is XML, then by convention the name has a 662 suffix of '+xml' 664 o The item is registered in the Emergency Call Additional Data 665 registry, as defined in Section 9.1.7 of [RFC7852] 667 * For emergency-call-specific formats, the registered name is the 668 root of the MIME Content-Type (not including the 669 'EmergencyCallData' prefix and any suffix such as '+xml') as 670 described in Section 4.1 of [RFC7852]. 672 o A new INFO package is registered that permits carrying the the new 673 content type, the metadata/control object (defined in 674 [I-D.ietf-ecrit-ecall]), and for compatibility, the MSD and VEDS 675 objects, in INFO messages. 677 When placing an emergency call, the crash data set and IVS capability 678 data are transported as described in Section 6. 680 The Vehicle Emergency Data Set (VEDS) is an XML structure defined by 681 the Association of Public-Safety Communications Officials (APCO) and 682 the National Emergency Number Association (NENA) [VEDS]. It is 683 carried in body part with MIME content-type 'application/ 684 EmergencyCallData.VEDS+xml'. 686 Entities along the path between the vehicle and the PSAP are able to 687 identify the call as an ACN call and handle it appropriately. The 688 PSAP is able to identify the crash and capabilities data attached to 689 the INVITE by examining the Call-Info header fields for 'purpose' 690 parameters whose values start with 'EmergencyCallData.' The PSAP is 691 able to access the data it is capable of handling and is interested 692 in by checking the 'purpose' parameter values. 694 This document extends [I-D.ietf-ecrit-ecall] by reusing the call set- 695 up and other normative requirements with the exception that in this 696 document, support for the eCall MSD is OPTIONAL and support for VEDS 697 in REQUIRED. This document also adds new attribute values to the 698 metadata/control object defined in [I-D.ietf-ecrit-ecall]. 700 8. Call Routing 702 An Emergency Services IP Network (ESInet) is a network operated by or 703 on behalf of emergency services authorities. It handles emergency 704 call routing and processing before delivery to a PSAP. In the 705 NG9-1-1 architecture adopted by NENA as well as the NG1-1-2 706 architecture adopted by EENA, each PSAP is connected to one or more 707 ESInets. Each originating network is also connected to one or more 708 ESInets. The ESInets maintain policy-based routing rules which 709 control the routing and processing of emergency calls. The 710 centralization of such rules within ESInets provides for a cleaner 711 separation between the responsibilities of the originating network 712 and that of the emergency services network, and provides greater 713 flexibility and control over processing of emergency calls by the 714 emergency services authorities and PSAPs. This makes it easier to 715 react quickly to unusual situations that require changes in how 716 emergency calls are routed or handled (e.g., a natural disaster 717 closes a PSAP), as well as ease in making long-term changes that 718 affect such routing (e.g., cooperative agreements to specially handle 719 calls requiring translation or relay services). 721 In an environment that uses ESInets, the originating network need 722 only detect that the service URN of an emergency call is or starts 723 with "sos", passing all types of emergency calls to an ESInet. The 724 ESInet is then responsible for routing such calls to an appropriate 725 PSAP. In an environment without an ESInet, the emergency services 726 authorities and the originating carriers determine how such calls are 727 routed. 729 9. New Metadata/Control Values 731 This document adds new attribute values to the metadata/control 732 structure defined in [I-D.ietf-ecrit-ecall]. 734 In addition to the base usage from the PSAP to the IVS to 735 acknowledge receipt of crash data, the element is also 736 contained in a metadata/control block sent by the IVS to the PSAP. 737 This is used by the IVS to acknowledge receipt of a request by the 738 PSAP and indicate if the request was carried out when that request 739 would not otherwise be acknowledged (if the PSAP requests the 740 vehicle to send data and the vehicle does so, the data serves as a 741 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. 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 765 The element indicates the object being acknowledged (i.e., a 766 data object or a metadata/control block containing 767 elements), and reports success or failure. 769 The element has child elements indicating 770 the actions supported by the IVS. 772 The element contains attributes to indicate the request and 773 to supply any needed information, and MAY contain a child 774 element to contain the text for a dynamic message. The 'action' 775 attribute is mandatory and indicates the specific action. 776 [I-D.ietf-ecrit-ecall] established an IANA registry to contain the 777 allowed values; this document adds new values to that registry in 778 Table 2. 780 Per [I-D.ietf-ecrit-ecall], the PSAP sends a control/metadata block 781 in response to the VEDS data sent by the IVS in SIP requests other 782 than INFO (e.g., the INVITE). This metadata/control block is sent in 783 the SIP response to the request (e.g., the INVITE response). When 784 the PSAP needs to send a control block that is not an immediate 785 response to a VEDS or other data sent by the IVS, the control block 786 is transmitted from the PSAP to the IVS in a SIP INFO request within 787 the established dialog. The IVS sends the requested data (e.g., the 788 VEDS) or an acknowledgment (for requests other than to send data) in 789 a new INFO request. This mechanism flexibly allows the PSAP to send 790 metadata/control data to the IVS and the IVS to respond. If control 791 data sent in a response message requests the IVS to send a new VEDS 792 or other data block, or to perform an action other than sending data, 793 the IVS sends the requested data or an acknowledgment regarding the 794 action in an INFO message within the dialog. 796 9.1. New values for the 'action' attribute' 798 The following new "action" values are defined: 800 msg-static: displays or plays a predefined message (translated as 801 appropriate for the language of the vehicle's interface). A 802 registry is created in Section 15.4 for messages and their IDs. 803 Vehicles include the highest registered message in their 804 element to indicate support for all messages up to 805 and including the indicated value. 807 msg-dynamic displays or speaks (via text-to-speech) a dynamic 808 message included in the request. 810 honk sounds the horn. 812 lamp turns a lamp (light) on, off, or flashes. 814 enable-camera adds a one-way media stream (established via SIP re- 815 INVITE sent by the vehicle) to enable the PSAP call taker to view 816 a feed from a camera. 818 Note that there is no 'request' action to play dynamic media (such as 819 an audio message). The PSAP can send a SIP re-INVITE to establish a 820 one-way media stream for this purpose. 822 9.2. Request Example 824 825 831 832 834 835 836 Remain calm. Help is on the way. 837 839 841 Figure 7: Request Example 843 9.3. The element 845 In [I-D.ietf-ecrit-ecall], the element is transmitted by the 846 PSAP to acknowledge the MSD. Here, the element is also 847 transmitted by the PSAP to acknowledge the VEDS data and by the IVS 848 to acknowledge receipt of a element that requested the IVS 849 to perform an action other than transmitting a data object (e.g., a 850 request to display a message would be acknowledged, but a request to 851 transmit VEDS data would not result in a separate element being 852 sent, since the data object itself serves as acknowledgment.) An 853 element sent by an IVS references the unique ID of the 854 metadata/control object containing the request(s) and indicates 855 whether the request was successfully performed, and if not, 856 optionally includes an explanation. 858 9.3.1. Ack Examples 860 861 867 868 869 871 873 875 Figure 8: Ack Example from IVS to PSAP 877 9.4. The element 879 The element ([I-D.ietf-ecrit-ecall]) is transmitted by 880 the IVS to indicate its capabilities to the PSAP. 882 The element contains a child element per 883 action supported by the vehicle. The vehicle MUST support sending 884 the VEDS data object and so includes at a minimum a child 885 element with the 'action' attribute set to "send-data" and the 886 'supported-values' attribute containing all data blocks supported by 887 the IV, which MUST include 'VEDS'. All other actions are OPTIONAL. 889 If the "msg-static" action is supported, a child element 890 with the 'action' attribute set to "msg-static" is included, with the 891 'msgid' attribute set to the highest supported static message 892 supported by the vehicle. A registry is created in Section 15.4 to 893 map 'msgid' values to static text messages. By sending the highest 894 supported static message number in its element, the 895 vehicle indicates its support for all static messages in the registry 896 up to and including that value. 898 If the "lamp" action is supported, a child element with the 899 'action' attribute set to "lamp" is included, with the 'supported- 900 values' attribute set to all supported lamp IDs. A registry is 901 created in Section 15.5 to contain lamp ID values. 903 If the "enable-camera" action is supported, a child element 904 with the 'action' attribute set to "enable-camera" is included, with 905 the 'supported-values' attribute set to all supported camera IDs. A 906 registry is created in Section 15.6 to contain camera ID values. 908 9.4.1. Capabilities Example 910 911 917 918 919 922 923 924 925 926 928 930 Figure 9: Capabilities Example 932 10. Test Calls 934 An NG-ACN test call is a call that is recognized and treated to some 935 extent as an NG-ACN call but not given emergency call treatment and 936 not handled by a call taker. The specific handling of test NG-ACN 937 calls is not itself standardized; the test call facility is intended 938 to allow the IVS, user, or TSP to verify that an NG-ACN call can be 939 successfully established with voice and/or other media communication. 941 The IVS might also be able to verify that the crash data was 942 successfully received. 944 This document builds on [I-D.ietf-ecrit-ecall], which inherits the 945 ability to utilize test call functionality from Section 15 of 946 [RFC6881]. A service URN starting with "test." indicates a test 947 call. [I-D.ietf-ecrit-ecall] registered "urn:service:test.sos.ecall" 948 for test calls. 950 MNOs, emergency authorities, ESInets, and PSAPs determine how to 951 treat a vehicle call requesting the "test" service URN so that the 952 desired functionality is tested, but this is outside the scope of 953 this document. (One possibility is that MNOs route such calls as 954 non-emergency calls to an ESInet, which routes them to a PSAP that 955 supports NG-ACN calls; the PSAP accepts test calls, sends a crash 956 data acknowledgment, and plays an audio clip (for example, saying 957 that the call reached an appropriate PSAP and the vehicle data was 958 successfully processed) in addition to supporting media loopback per 959 [RFC6881]). 961 Note that since test calls are placed using "test" as the parent 962 service URN and "sos" as a child, such calls are not treated as an 963 emergency call and so some functionality might not apply (such as 964 preemption or service availability for devices lacking service ("non- 965 service-initialized" or "NSI" devices) if those are available for 966 emergency calls). 968 11. The emergencyCallData.eCall.VEDS INFO package 970 This document registers the 'emergencyCallData.eCall.VEDS' INFO 971 package. 973 Both endpoints (the IVS and the PSAP equipment) include 974 'emergencyCallData.eCall.VEDS' in a Recv-Info header field per 975 [RFC6086] to indicate ability to receive INFO messages carrying data 976 as described here. 978 Support for the 'emergencyCallData.eCall.VEDS' INFO package indicates 979 the ability to receive the VEDS body part as specified in [TBD: THIS 980 DOCUMENT] and the metadata/control body part as specified in 981 [I-D.ietf-ecrit-ecall]. 983 An INFO request message carrying data related to an emergency call as 984 described in [TBD: THIS DOCUMENT] has an Info-Package header field 985 set to 'emergencyCallData.eCall.VEDS' per [RFC6086]. 987 11.1. INFO Package Requirements 989 The requirements of Section 10 of [RFC6086] are addressed in the 990 following sections. 992 11.1.1. Overall Description 994 This section describes "what type of information is carried in INFO 995 requests associated with the Info Package, and for what types of 996 applications and functionalities UAs can use the Info Package." 998 INFO requests associated with the emergencyCallData.eCall.VEDS INFO 999 package carry data associated with emergency calls as defined in 1000 [TBD: THIS DOCUMENT]. The application is vehicle-initiated emergency 1001 calls established using SIP. The functionality is to carry vehicle 1002 data and metadata/control information between vehicles and PSAPs. 1003 Refer to [TBD: THIS DOCUMENT] for more information. 1005 11.1.2. Applicability 1007 This section describes "why the Info Package mechanism, rather than 1008 some other mechanism, has been chosen for the specific use-case...." 1010 The use of INFO is based on an analysis of the requirements against 1011 the intent and effects of INFO versus other approaches (which 1012 included SIP MESSAGE, SIP OPTIONS, SIP re-INVITE, media plane 1013 transport, and non-SIP protocols). In particular, the transport of 1014 emergency call data blocks occurs within a SIP emergency dialog, per 1015 Section 6, and is normally carried in the initial INVITE and its 1016 response; the use of INFO only occurs when emergency-call-related 1017 data needs to be sent mid-call. While MESSAGE could be used, it is 1018 not tied to a SIP dialog as is INFO and thus might not be associated 1019 with the dialog. SIP OPTIONS or re-INVITE could also be used, but is 1020 seen as less clean than INFO. SUBSCRIBE/NOTIFY could be coerced into 1021 service, but the semantics are not a good fit, e.g., the subscribe/ 1022 notify mechanism provides one-way communication consisting of (often 1023 multiple) notifications from notifier to subscriber indicating that 1024 certain events in notifier have occurred, whereas what's needed here 1025 is two-way communication of data related to the emergency dialog. 1026 Use of the media plane mechanisms was discounted because the number 1027 of messages needing to be exchanged in a dialog is normally zero or 1028 very few, and the size of the data is likewise very small. The 1029 overhead caused by user plane setup (e.g., to use MSRP as transport) 1030 would be disproportionately large. 1032 Based on the the analyses, the SIP INFO method was chosen to provide 1033 for mid-call data transport. 1035 11.1.3. Info Package Name 1037 The info package name is emergencyCallData.eCall.VEDS 1039 11.1.4. Info Package Parameters 1041 None 1043 11.1.5. SIP Option-Tags 1045 None 1047 11.1.6. INFO Message Body Parts 1049 The 'application/emergencyCallData.eCall.VEDS+xml' and 'application/ 1050 emergencyCallData.eCall.control+xml' MIME types are associated with 1051 this INFO package. See [TBD: THIS DOCUMENT] and 1052 [I-D.ietf-ecrit-ecall] for more information. 1054 11.1.7. Info Package Usage Restrictions 1056 Usage is limited to vehicle-initiated emergency calls as defined in 1057 [TBD: THIS DOCUMENT]. 1059 11.1.8. Rate of INFO Requests 1061 The rate of SIP INFO requests associated with the 1062 emergencyCallData.eCall.VEDS info package is normally quite low (most 1063 dialogs are likely to contain zero INFO requests, while others can be 1064 expected to carry an occasional request). 1066 11.1.9. Info Package Security Considerations 1068 The MIME content type registations for the data blocks that can be 1069 carried using this IFO package contains a discussion of the security 1070 and/or privacy considerations specific to that data block. The 1071 "Security Considerations" and "Privacy Considerations" sections of 1072 [TBD: THIS DOCUMENT] discuss security and privacy considerations of 1073 the data carried in vehicle-initiated emergency calls as described in 1074 that document. 1076 11.1.10. Implementation Details 1078 See [TBD: THIS DOCUMENT] for protocol details. 1080 11.1.11. Examples 1082 See [TBD: THIS DOCUMENT] for protocol examples. 1084 12. Example 1086 Figure 10 shows an NG-ACN call routing. The mobile network operator 1087 (MNO) routes the call to an Emergency services IP Network (ESInet), 1088 as for any emergency call. The ESInet routes the call to an 1089 appropriate NG-ACN-capable PSAP (using location information and the 1090 fact that that it is an NG-ACN call). The call is processed by the 1091 Emergency Services Routing Proxy (ESRP), as the entry point to the 1092 ESInet. The ESRP routes the call to an appropriate NG-ACN-capable 1093 PSAP, where the call is received by a call taker. (In deployments 1094 where there is no ESInet, the MNO itself routes the call directly to 1095 an appropriate NG-ACN-capable PSAP.) 1097 +---------------------------------------+ 1098 | | 1099 +------------+ | +-------+ | 1100 | | | | PSAP2 | | 1101 | | | +-------+ | 1102 | Originating| | | 1103 | Mobile | | +------+ +-------+ | 1104 Vehicle-->| Network |--+->| ESRP |---->| PSAP1 |--> Call-Taker | 1105 | | | +------+ +-------+ | 1106 | | | | 1107 +------------+ | +-------+ | 1108 | | PSAP3 | | 1109 | +-------+ | 1110 | | 1111 | | 1112 | | 1113 | ESInet | 1114 +---------------------------------------+ 1116 Figure 10: Example of Vehicle-Placed Emergency Call Message Flow 1118 The example, shown in Figure 11, illustrates a SIP emergency call 1119 INVITE with location information (a PIDF-LO), VEDS crash data (a VEDS 1120 data block), and capabilities data (an eCall metadata/control block 1121 with extensions defined in this document) attached to the SIP INVITE 1122 message. The INVITE has a request URI containing the 1123 'urn:service:sos.ecall.automatic' service URN. 1125 The example VEDS data structure shows information about about a 1126 crashed vehicle. The example communicates that the car is a model 1127 year 2015 Saab 9-5 (a car which does not exist). The front airbag 1128 deployed as a consequence of the crash. The 1129 'VehicleBodyCategoryCode' indicates that the crashed vehicle is a 1130 passenger car (the code is set to '101') and that it is not a 1131 convertible (the 'ConvertibleIndicator' value is set to 'false'). 1133 The 'VehicleCrashPulse' element provides further information about 1134 the crash, namely that the force of impact based on the change in 1135 velocity over the duration of the crash pulse was 100 MPH. The 1136 principal direction of the force of the impact is set to '12' (which 1137 refers to 12 O'Clock, corresponding to a frontal collision). This 1138 value is described in the 'CrashPulsePrincipalDirectionOfForceValue' 1139 element. 1141 The 'CrashPulseRolloverQuarterTurnsValue' indicates the number of 1142 quarter turns in concert with a rollover expressed as a number; in 1143 our case 1. 1145 No roll bar was deployed, as indicated in 1146 'VehicleRollbarDeployedIndicator' being set to 'false'. 1148 Next, there is information indicating seatbelt and seat sensor data 1149 for individual seat positions in the vehicle. In our example, 1150 information from the driver seat is available (value '1' in the 1151 'VehicleSeatLocationCategoryCode' element), that the seatbelt was 1152 monitored ('VehicleSeatbeltMonitoredIndicator' element), that the 1153 seatbelt was fastened ('VehicleSeatbeltFastenedIndicator' element) 1154 and the seat sensor determined that the seat was occupied 1155 ('VehicleSeatOccupiedIndicator' element). 1157 Finally, information about the weight of the vehicle, which is 600 1158 kilogram in our example. 1160 In addition to the information about the vehicle, further indications 1161 are provided, namely the presence of fuel leakage 1162 ('FuelLeakingIndicator' element), an indication whether the vehicle 1163 was subjected to multiple impacts ('MultipleImpactsIndicator' 1164 element), the orientation of the vehicle at final rest 1165 ('VehicleFinalRestOrientationCategoryCode' element) and an indication 1166 that there are no parts of the vehicle on fire (the 1167 'VehicleFireIndicator' element). 1169 INVITE urn:service:sos.ecall.automatic SIP/2.0 1170 To: urn:service:sos.ecall.automatic 1171 From: ;tag=9fxced76sl 1172 Call-ID: 3848276298220188511@atlanta.example.com 1173 Geolocation: 1174 Geolocation-Routing: no 1175 Call-Info: cid:1234567890@atlanta.example.com; 1176 purpose=EmergencyCallData.VEDS 1177 Call-Info: cid:1234567892@atlanta.example.com; 1178 purpose=EmergencyCallData.ecall.control 1179 Accept: application/sdp, application/pidf+xml, 1180 application/emergencyCallData.eCall.control+xml 1181 Recv-Info: emergencyCallData.eCall 1182 Allow: INVITE, ACK, PRACK, INFO, OPTIONS, CANCEL, REFER, BYE, 1183 SUBSCRIBE, NOTIFY, UPDATE 1184 CSeq: 31862 INVITE 1185 Content-Type: multipart/mixed; boundary=boundary1 1186 Content-Length: ... 1188 --boundary1 1189 Content-Type: application/sdp 1191 ...Session Description Protocol (SDP) goes here 1193 --boundary1 1194 Content-Type: application/pidf+xml 1195 Content-ID: 1197 1198 1206 1207 1208 1209 1210 -34.407 150.883 1211 1212 1213 278 1214 1215 1216 1217 1218 gps 1219 1220 2012-04-5T10:18:29Z 1221 1M8GDM9A_KP042788 1222 1223 1224 --boundary1 1225 Content-Type: application/EmergencyCallData.VEDS+xml 1226 Content-ID: 1234567890@atlanta.example.com 1227 Content-Disposition: by-reference;handling=optional 1229 1230 1234 1235 1236 Saab 1237 1238 1239 9-5 1240 1241 1243 2015 1244 1245 1246 FRONT 1247 true 1248 1249 1250 false 1251 MAIN 1252 1254 101 1255 1256 1257 1258 1260 100 1261 1262 1264 MPH 1265 1266 12 1267 1268 1 1269 1270 1271 false 1272 1273 1274 1 1275 1276 true 1277 1278 true 1279 1280 true 1281 1282 1283 1285 1287 600 1288 1289 1291 kilogram 1292 1293 1294 1295 true 1296 false 1297 true 1298 Driver 1299 1300 false 1301 1302 1304 --boundary1 1305 Content-Type: application/EmergencyCallData.ecall.control+xml 1306 Content-ID: 1234567892@atlanta.example.com 1307 Content-Disposition: by-reference;handling=optional 1309 1310 1316 1317 1318 1322 1323 1324 1325 1327 1329 1331 --boundary1-- 1333 Figure 11: SIP INVITE indicating a Vehicule-Initated Emergency Call 1335 13. Security Considerations 1337 Since this document relies on [I-D.ietf-ecrit-ecall] and [RFC7852], 1338 the security considerations described there and in [RFC5069] apply 1339 here. Implementors are cautioned to read and understand the 1340 discussion in those documents. 1342 As with emergency service systems where location data is supplied or 1343 determined with the assistance of an end host, there is the 1344 possibility that that location is incorrect, either intentially 1345 (e.g., in a denial of service attack against the emergency services 1346 infrastructure) or due to a malfunctioning device. The reader is 1347 referred to [RFC7378] for a discussion of some of these 1348 vulnerabilities. 1350 In addition to the security considerations discussion specific to the 1351 metadata/control object in [I-D.ietf-ecrit-ecall], note that vehicles 1352 MAY decline to carry out any requested action (e.g., if the vehicle 1353 requires but is unable to verify the certificate used to sign the 1354 request). The vehicle MAY use any value in the reason registry to 1355 indicate why it did not take an action (e.g., the generic "unable" or 1356 the more specific "security-failure"). 1358 14. Privacy Considerations 1360 Since this document builds on [I-D.ietf-ecrit-ecall], which itself 1361 builds on [RFC7852], the data structures specified there, and the 1362 corresponding privacy considerations discussed there, apply here as 1363 well. The VEDS data structure contains optional elements that can 1364 carry identifying and personal information, both about the vehicle 1365 and about the owner, as well as location information, and so needs to 1366 be protected against unauthorized disclosure, as discussed in 1368 [RFC7852]. Local regulations may impose additional privacy 1369 protection requirements. 1371 The additional functionality enabled by this document, such as access 1372 to vehicle camera streams, carries a burden of protection and so 1373 implementations need to be careful that access is only provided 1374 within the context of an emergency call or to an emergency services 1375 provider (e.g., by verifying that the request for camera access is 1376 signed by a certificate issued by an emergency services registrar). 1378 15. IANA Considerations 1380 This document registers the 'application/EmergencyCall.VEDS+xml' MIME 1381 content type, and adds "VEDS" to the Emergency Call Additional Data 1382 registry. This document adds to and creates sub-registries in the 1383 'Metadata/Control Data' registry created in [I-D.ietf-ecrit-ecall]. 1384 This document registers a new INFO package. 1386 15.1. MIME Content-type Registration for 'application/ 1387 EmergencyCall.VEDS+xml' 1389 This specification requests the registration of a new MIME content 1390 type according to the procedures of RFC 4288 [RFC4288] and guidelines 1391 in RFC 3023 [RFC3023]. 1393 MIME media type name: application 1395 MIME subtype name: EmergencyCallData.VEDS+xml 1397 Mandatory parameters: none 1399 Optional parameters: charset 1401 Indicates the character encoding of enclosed XML. 1403 Encoding considerations: Uses XML, which can employ 8-bit 1404 characters, depending on the character encoding used. See 1405 Section 3.2 of RFC 3023 [RFC3023]. 1407 Security considerations: 1409 This content type is designed to carry vehicle crash data 1410 during an emergency call. 1412 This data can contain personal information including vehicle 1413 VIN, location, direction, etc. Appropriate precautions need to 1414 be taken to limit unauthorized access, inappropriate disclosure 1415 to third parties, and eavesdropping of this information. 1417 Please refer to Section 7 and Section 8 of [RFC7852] for more 1418 information. 1420 When this content type is contained in a signed or encrypted 1421 body part, the enclosing multipart (e.g., multipart/signed or 1422 multipart/encrypted) has the same Content-ID as the data part. 1423 This allows an entity to identify and access the data blocks it 1424 is interested in without having to dive deeply into the message 1425 structure or decrypt parts it is not interested in. (The 1426 'purpose' parameter in a Call-Info header field identifies the 1427 data, and the CID URL points to the data block in the body, 1428 which has a matching Content-ID body part header field). 1430 Interoperability considerations: None 1432 Published specification: [VEDS] 1434 Applications which use this media type: Emergency Services 1436 Additional information: None 1438 Magic Number: None 1440 File Extension: .xml 1442 Macintosh file type code: 'TEXT' 1444 Persons and email addresses for further information: Randall 1445 Gellensm rg+ietf@randy.pensive.org; Hannes Tschofenig, 1446 Hannes.Tschofenig@gmx.net 1448 Intended usage: LIMITED USE 1450 Author: This specification is a work item of the IETF ECRIT 1451 working group, with mailing list address . 1453 Change controller: The IESG 1455 15.2. Registration of the 'VEDS' entry in the Emergency Call Additional 1456 Data registry 1458 This specification requests IANA to add the 'VEDS' entry to the 1459 Emergency Call Additional Data registry, with a reference to this 1460 document. The Emergency Call Additional Data registry was 1461 established by [RFC7852]. 1463 15.3. New Action Values 1465 This document adds new values for the 'action' attribute of the 1466 element in the "Action Registry" registry created by 1467 [I-D.ietf-ecrit-ecall]. 1469 +---------------+-------------------------------------+ 1470 | Name | Description | 1471 +---------------+-------------------------------------+ 1472 | msg-static | Section 9.1 of [TBD: THIS DOCUMENT] | 1473 | | | 1474 | msg-dynamic | Section 9.1 of [TBD: THIS DOCUMENT] | 1475 | | | 1476 | honk | Section 9.1 of [TBD: THIS DOCUMENT] | 1477 | | | 1478 | lamp | Section 9.1 of [TBD: THIS DOCUMENT] | 1479 | | | 1480 | enable-camera | Section 9.1 of [TBD: THIS DOCUMENT] | 1481 +---------------+-------------------------------------+ 1483 Table 2: Action Registry New Values 1485 15.4. Static Message Registry 1487 This document creates a new sub-registry called "Static Message 1488 Registry" in the "Metadata/Control Data" registry established by 1489 [I-D.ietf-ecrit-ecall]. Because all compliant vehicles are expected 1490 to support all static messages translated into all languages 1491 supported by the vehicle, it is important to limit the number of such 1492 messages. As defined in [RFC5226], this registry operates under 1493 "Publication Required" rules, which require a stable, public document 1494 and implies expert review of the publication. The expert should 1495 determine that the document has been published by an appropriate 1496 emergency services organization (e.g., NENA, EENA, APCO) or by the 1497 IETF with input from an emergency services organization, and that the 1498 proposed message is sufficiently distinguishable from other messages. 1500 The contents of this registry are: 1502 ID: An integer identifier to be used in the 'msgid' attribute of a 1503 metadata/control element. 1505 Message: The text of the message. Messages are listed in the 1506 registry in English; vehicles are expected to implement 1507 translations into languages supported by the vehicle. 1509 When new messages are added to the registry, the message text is 1510 determined by the registrant; IANA assigns the IDs. Each message is 1511 assigned a consecutive integer value as its ID. This allows an IVS 1512 to indicate by a single integer value that it supports all messages 1513 with that value or lower. 1515 The initial set of values is listed in Table 3. 1517 +----+--------------------------------------------------------------+ 1518 | ID | Message | 1519 +----+--------------------------------------------------------------+ 1520 | 1 | Emergency authorities are aware of your incident and | 1521 | | location, but are unable to speak with you right now. We | 1522 | | will help you as soon as possible. | 1523 +----+--------------------------------------------------------------+ 1525 Table 3: Static Message Registry 1527 15.5. Lamp ID Registry 1529 This document creates a new sub-registry called "Lamp ID Registry" in 1530 the "Metadata/Control Data" registry established by 1531 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1532 the names of automotive lamps (lights). As defined in [RFC5226], 1533 this registry operates under "Expert Review" rules. The expert 1534 should determine that the proposed lamp name is clearly 1535 understandable and is sufficiently distinguishable from other lamp 1536 names. 1538 The contents of this registry are: 1540 Name: The identifier to be used in the 'lamp-ID' attribute of a 1541 metadata/control element. 1543 Description: A description of the lamp (light). 1545 The initial set of values is listed in Table 4. 1547 +----------------+---------------------------------------------+ 1548 | Name | Description | 1549 +----------------+---------------------------------------------+ 1550 | head | The main lamps used to light the road ahead | 1551 | | | 1552 | interior | Interior lamp, often at the top center | 1553 | | | 1554 | fog-front | Front fog lamps | 1555 | | | 1556 | fog-rear | Rear fog lamps | 1557 | | | 1558 | brake | Brake indicator lamps | 1559 | | | 1560 | brake-center | Center High Mounted Stop Lamp | 1561 | | | 1562 | position-front | Front position/parking/standing lamps | 1563 | | | 1564 | position-rear | Rear position/parking/standing lamps | 1565 | | | 1566 | turn-left | Left turn/directional lamps | 1567 | | | 1568 | turn-right | Right turn/directional lamps | 1569 | | | 1570 | hazard | Hazard/four-way lamps | 1571 +----------------+---------------------------------------------+ 1573 Table 4: Lamp ID Registry Initial Values 1575 15.6. Camera ID Registry 1577 This document creates a new sub-registry called "Camera ID Registry" 1578 in the "Metadata/Control Data" registry established by 1579 [I-D.ietf-ecrit-ecall]. This new sub-registry uniquely identifies 1580 automotive cameras. As defined in [RFC5226], this registry operates 1581 under "Expert Review" rules. The expert should determine that the 1582 proposed camera name is clearly understandable and is sufficiently 1583 distinguishable from other camera names. 1585 The contents of this registry are: 1587 Name: The identifier to be used in the 'camera-ID' attribute of an 1588 eCall control element. 1590 Description: A description of the camera. 1592 The initial set of values is listed in Table 5. 1594 +-------------+-----------------------------------------------------+ 1595 | Name | Description | 1596 +-------------+-----------------------------------------------------+ 1597 | backup | Shows what is behind the vehicle, e.g., often used | 1598 | | for driver display when the vehicle is in reverse. | 1599 | | Also known as rearview, reverse, rear visibility, | 1600 | | etc. | 1601 | | | 1602 | left-rear | Shows view to the left and behind (e.g., left side | 1603 | | rear-view mirror or blind spot view) | 1604 | | | 1605 | right-rear | Shows view to the right and behind (e.g., right | 1606 | | side rear-view mirror or blind spot view) | 1607 | | | 1608 | forward | Shows what is in front of the vehicle | 1609 | | | 1610 | rear-wide | Shows what is behind vehicle (e.g., used by rear- | 1611 | | collision detection systems), separate from backup | 1612 | | view | 1613 | | | 1614 | lane | Used by systems to identify road lane and/or | 1615 | | monitor vehicle's position within lane | 1616 | | | 1617 | interior | Shows the interior (e.g., driver) | 1618 | | | 1619 | night-front | Night-vision view of what is in front of the | 1620 | | vehicle | 1621 +-------------+-----------------------------------------------------+ 1623 Table 5: Camera ID Registry Initial Values 1625 16. Acknowledgements 1627 We would like to thank Christer Holmberg for his suggestions; Michael 1628 Montag, Arnoud van Wijk, Ban Al-Bakri, Wes George, Gunnar Hellstrom, 1629 and Rex Buddenberg for their feedback; and Ulrich Dietz for his help 1630 with earlier versions of the original version of this document. 1632 17. Changes from Previous Versions 1634 17.1. Changes from draft-ietf-08 to draft-ietf-09 1636 o Added INFO package registration for eCall.VEDS 1637 o Moved element and other extension points back to 1638 eCall document so that extension points are in base spec (and also 1639 to get XML schema to compile) 1640 o Text changes for clarification. 1642 17.2. Changes from draft-ietf-07 to draft-ietf-08 1644 o Moved much of the metadata/control object from 1645 [I-D.ietf-ecrit-ecall] to this document as extensions 1646 o Editorial clarifications and simplifications 1647 o Moved "Call Routing" to be a subsection of "Call Setup" 1648 o Deleted "Profile" section and moved some of its text into 1649 "Introduction" 1651 17.3. Changes from draft-ietf-06 to draft-ietf-07 1653 o Minor editorial changes 1655 17.4. Changes from draft-ietf-05 to draft-ietf-06 1657 o Added clarifying text regarding signed and encrypted data 1658 o Additional informative text in "Migration to Next-Generation" 1659 section 1660 o Additional clarifying text regarding security and privacy. 1662 17.5. Changes from draft-ietf-04 to draft-ietf-05 1664 o Reworded security text in main document and in MIME registration 1665 for the VEDS object 1667 17.6. Changes from draft-ietf-03 to draft-ietf-04 1669 o Added example VEDS object 1670 o Additional clarifications and corrections 1671 o Removed references from Abstract 1672 o Moved Document Scope section to follow Introduction 1674 17.7. Changes from draft-ietf-02 to draft-ietf-03 1676 o Additional clarifications and corrections 1678 17.8. Changes from draft-ietf-01 to draft-ietf-02 1680 o This document now refers to [I-D.ietf-ecrit-ecall] for technical 1681 aspects including the service URN; this document no longer 1682 proposes a unique service URN for non-eCall NG-ACN calls; the same 1683 service URN is now used for all NG-ACN calls including NG-eCall 1684 and non-eCall 1685 o Added discussion of an NG-ACN call placed to a PSAP that doesn't 1686 support it 1687 o Minor wording improvements and clarifications 1689 17.9. Changes from draft-ietf-00 to draft-ietf-01 1691 o Added further discussion of test calls 1692 o Added further clarification to the document scope 1693 o Mentioned that multi-region vehicles may need to support other 1694 crash notification specifications such as eCall 1695 o Minor wording improvements and clarifications 1697 17.10. Changes from draft-gellens-02 to draft-ietf-00 1699 o Renamed from draft-gellens- to draft-ietf- 1700 o Added text to Introduction to clarify that during a CS ACN, the 1701 PSAP call taker usually needs to listen to the data and transcribe 1702 it 1704 17.11. Changes from draft-gellens-01 to -02 1706 o Fixed case of 'EmergencyCallData', in accordance with changes to 1707 [RFC7852] 1709 17.12. Changes from draft-gellens-00 to -01 1711 o Now using 'EmergencyCallData' for purpose parameter values and 1712 MIME subtypes, in accordance with changes to [RFC7852] 1713 o Added reference to RFC 6443 1714 o Fixed bug that caused Figure captions to not appear 1716 18. References 1718 18.1. Normative References 1720 [I-D.ietf-ecrit-ecall] 1721 Gellens, R. and H. Tschofenig, "Next-Generation Pan- 1722 European eCall", draft-ietf-ecrit-ecall-10 (work in 1723 progress), July 2016. 1725 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1726 Requirement Levels", BCP 14, RFC 2119, 1727 DOI 10.17487/RFC2119, March 1997, 1728 . 1730 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1731 Types", RFC 3023, DOI 10.17487/RFC3023, January 2001, 1732 . 1734 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1735 Format", RFC 4119, DOI 10.17487/RFC4119, December 2005, 1736 . 1738 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1739 Registration Procedures", RFC 4288, DOI 10.17487/RFC4288, 1740 December 2005, . 1742 [RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for 1743 Emergency and Other Well-Known Services", RFC 5031, 1744 DOI 10.17487/RFC5031, January 2008, 1745 . 1747 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1748 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1749 DOI 10.17487/RFC5226, May 2008, 1750 . 1752 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 1753 Presence Information Data Format Location Object (PIDF-LO) 1754 Usage Clarification, Considerations, and Recommendations", 1755 RFC 5491, DOI 10.17487/RFC5491, March 2009, 1756 . 1758 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 1759 Thomson, "Dynamic Extensions to the Presence Information 1760 Data Format Location Object (PIDF-LO)", RFC 5962, 1761 DOI 10.17487/RFC5962, September 2010, 1762 . 1764 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1765 "Framework for Emergency Calling Using Internet 1766 Multimedia", RFC 6443, DOI 10.17487/RFC6443, December 1767 2011, . 1769 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 1770 Communications Services in Support of Emergency Calling", 1771 BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013, 1772 . 1774 [RFC7852] Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and 1775 J. Winterbottom, "Additional Data Related to an Emergency 1776 Call", RFC 7852, DOI 10.17487/RFC7852, July 2016, 1777 . 1779 [VEDS] Advanced Automatic Crash Notification (AACN) Joint APCO/ 1780 NENA Data Standardization Workgroup, , "Vehicular 1781 Emergency Data Set (VEDS) version 3", July 2012, 1782 . 1785 18.2. Informative references 1787 [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for 1788 Emergency Context Resolution with Internet Technologies", 1789 RFC 5012, DOI 10.17487/RFC5012, January 2008, 1790 . 1792 [RFC5069] Taylor, T., Ed., Tschofenig, H., Schulzrinne, H., and M. 1793 Shanmugam, "Security Threats and Requirements for 1794 Emergency Call Marking and Mapping", RFC 5069, 1795 DOI 10.17487/RFC5069, January 2008, 1796 . 1798 [RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session 1799 Initiation Protocol (SIP) INFO Method and Package 1800 Framework", RFC 6086, DOI 10.17487/RFC6086, January 2011, 1801 . 1803 [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed., 1804 "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378, 1805 December 2014, . 1807 [triage-2008] 1808 National Center for Injury Prevention and Control, and 1809 Centers for Disease Control and Prevention, 1810 "Recommendations from the Expert Panel: Advanced Automatic 1811 Collision Notification and Triage of the Injured Patient", 1812 2008, . 1814 [triage-2011] 1815 National Center for Injury Prevention and Control, and 1816 Centers for Disease Control and Prevention, "Guidelines 1817 for field triage of injured patients: recommendations of 1818 the National Expert Panel on Field Triage", January 2012, 1819 . 1824 Authors' Addresses 1826 Randall Gellens 1827 Core Technology Consulting 1829 Email: rg+ietf@randy.pensive.org 1830 Brian Rosen 1831 NeuStar, Inc. 1832 470 Conrad Dr 1833 Mars, PA 16046 1834 US 1836 Email: br@brianrosen.net 1838 Hannes Tschofenig 1839 Individual 1841 Email: Hannes.Tschofenig@gmx.net 1842 URI: http://www.tschofenig.priv.at