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