idnits 2.17.1 draft-ietf-ecrit-additional-data-25.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 2404 has weird spacing: '...element name=...' == Line 3029 has weird spacing: '...ll-Info pur...' -- The document date (December 3, 2014) is 3425 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) -- Looks like a reference, but probably isn't: '1' on line 3691 -- Looks like a reference, but probably isn't: '2' on line 3693 == Missing Reference: 'This RFC' is mentioned on line 3029, but not defined ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Qualcomm Technologies, Inc. 4 Intended status: Standards Track B. Rosen 5 Expires: June 6, 2015 NeuStar 6 H. Tschofenig 7 (no affiliation) 8 R. Marshall 9 TeleCommunication Systems, Inc. 10 J. Winterbottom 11 (no affiliation) 12 December 3, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-25.txt 17 Abstract 19 When an emergency call is sent to a Public Safety Answering Point 20 (PSAP), the device that sends it, as well as any application service 21 provider in the path of the call, or access network provider through 22 which the call originated may have information about the call, the 23 caller or the location which the PSAP may be able to use. This 24 document describes data structures and a mechanism to convey such 25 data to the PSAP. The mechanism uses a Uniform Resource Identifier 26 (URI), which may point to either an external resource or an object in 27 the body of the SIP message. The mechanism thus allows the data to 28 be passed by reference (when the URI points to an external resource) 29 or by value (when it points into the body of the message). This 30 follows the tradition of prior emergency services standardization 31 work where data can be conveyed by value within the call signaling 32 (i.e., in body of the SIP message) and also by reference. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on June 6, 2015. 50 Copyright Notice 52 Copyright (c) 2014 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 70 4. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7 71 4.1. Data Provider Information . . . . . . . . . . . . . . . . 8 72 4.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 73 4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9 74 4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9 75 4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 10 76 4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 11 77 4.1.6. Data Provider Languages(s) Supported . . . . . . . . 11 78 4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 12 79 4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12 80 4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13 81 4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13 82 4.2. Service Information . . . . . . . . . . . . . . . . . . . 16 83 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16 84 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 17 85 4.2.3. Service Mobility Environment . . . . . . . . . . . . 19 86 4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 19 87 4.3. Device Information . . . . . . . . . . . . . . . . . . . 20 88 4.3.1. Device Classification . . . . . . . . . . . . . . . . 20 89 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 22 90 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 22 91 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 22 92 4.3.5. Device/Service Specific Additional Data Structure . . 23 93 4.3.6. Device/Service Specific Additional Data Structure 94 Type . . . . . . . . . . . . . . . . . . . . . . . . 24 95 4.3.7. Issues with getting new types of data into use . . . 24 96 4.3.8. Choosing between defining a new type of block or new 97 type of device/service specific additional data . . . 25 98 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 26 99 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26 100 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26 101 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27 102 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27 103 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 30 104 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 30 105 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30 106 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30 107 5.1. Transmitting Blocks using the Call-Info Header . . . . . 32 108 5.2. Transmitting Blocks by Reference using the provided-by 109 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 110 5.3. Transmitting Blocks by Value using the provided-by 111 Element . . . . . . . . . . . . . . . . . . . . . . . . . 34 112 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 35 113 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36 114 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 48 115 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 48 116 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 50 117 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 51 118 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 52 119 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 53 120 7.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 54 121 8. Security Considerations . . . . . . . . . . . . . . . . . . . 57 122 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 58 123 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 124 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 61 125 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 61 126 10.1.2. Service Environment Registry . . . . . . . . . . . . 62 127 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 62 128 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 63 129 10.1.5. Service Provider Type Registry . . . . . . . . . . . 63 130 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 64 131 10.1.7. Device Classification Registry . . . . . . . . . . . 64 132 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 64 133 10.1.9. Device/Service Data Type Registry . . . . . . . . . 65 134 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 65 135 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 66 136 10.3. URN Sub-Namespace Registration for provided-by Registry 137 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 66 138 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 67 139 10.4.1. MIME Content-type Registration for 140 'application/EmergencyCallData.ProviderInfo+xml' . . 67 141 10.4.2. MIME Content-type Registration for 142 'application/EmergencyCallData.ServiceInfo+xml' . . 68 143 10.4.3. MIME Content-type Registration for 144 'application/EmergencyCallData.DeviceInfo+xml' . . . 69 145 10.4.4. MIME Content-type Registration for 146 'application/EmergencyCallData.SubscriberInfo+xml' . 70 147 10.4.5. MIME Content-type Registration for 148 'application/EmergencyCallData.Comment+xml' . . . . 71 149 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 72 150 10.5.1. Registration for 151 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 72 152 10.5.2. Registration for 153 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf 154 o . . . . . . . . . . . . . . . . . . . . . . . . . 73 155 10.5.3. Registration for 156 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 74 157 10.5.4. Registration for 158 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 75 159 10.5.5. Registration for 160 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI 161 nfo . . . . . . . . . . . . . . . . . . . . . . . . 76 162 10.5.6. Registration for 163 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 77 164 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 78 165 10.7. VCard Parameter Value Registration . . . . . . . . . . . 79 166 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 167 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 80 168 12.1. Normative References . . . . . . . . . . . . . . . . . . 80 169 12.2. Informational References . . . . . . . . . . . . . . . . 81 170 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 82 171 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 82 172 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 105 174 1. Introduction 176 When an IP-based emergency call is initiated, a rich set of data from 177 multiple data sources is conveyed to the Public Safety Answering 178 Point (PSAP). This data includes information about the calling party 179 identity, the multimedia capabilities of the device, the request for 180 emergency services, location information, and meta-data about the 181 sources of the data. The device, the access network provider, and 182 any service provider in the call path may have even more information 183 useful for a PSAP. This document extends the basic set of data 184 communicated with an IP-based emergency call, as described in 185 [RFC6443] and [RFC6881], in order to carry additional data which may 186 be useful to an entity or call taker handling the call. This data is 187 "additional" to the basic information found in the emergency call 188 signaling used. 190 In general, there are three categories of this additional data that 191 may be transmitted with an emergency call: 193 Data Associated with a Location: Primary location data is conveyed 194 in the Presence Information Data Format Location Object (PIDF-LO) 195 data structure as defined in RFC 4119 [RFC4119] and extended by 196 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 197 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 198 geodetic location information), and [RFC7035] (for relative 199 location). This primary location data identifies the location or 200 estimated location of the caller. However, there may exist 201 additional, secondary data which is specific to the location, such 202 as floor plans, tenant and building owner contact data, heating, 203 ventilation and air conditioning (HVAC) status, etc. Such 204 secondary location data is not included in the location data 205 structure but can be transmitted using the mechanisms defined in 206 this document. Although this document does not define any 207 structures for such data, future documents may do so following the 208 procedures defined here. 210 Data Associated with a Call: While some information is carried in 211 the call setup procedure itself (as part of the SIP headers as 212 well as in the body of the SIP message), there is additional data 213 known by the device making the call and/or a service provider 214 along the path of the call. This information may include the 215 service provider contact information, subscriber identity and 216 contact information, the type of service the service provider and 217 the access network provider offer, what type of device is being 218 used, etc. Some data is broadly applicable, while other data is 219 dependent on the type of device or service. For example, a 220 medical monitoring device may have sensor data. The data 221 structures defined in this document (Data Provider Information, 222 Device Information, and Owner/Subscriber Information) all fall 223 into the category of "Data Associated with a Call". 225 Data Associated with a Caller: This is personal data about a caller, 226 such as medical information and emergency contact data. Although 227 this document does not define any structures within this category, 228 future documents may do so following the procedures defined here. 230 While this document defines data structures only within the category 231 of Data Associated with a Call, by establishing the overall framework 232 of Additional Data, along with general mechanisms for transport of 233 such data, extension points and procedures for future extensions, it 234 minimizes the work needed to carry data in the other categories. 235 Other specifications may make use of the facilities provided here. 237 For interoperability, there needs to be a common way for the 238 information conveyed to a PSAP to be encoded and identified. 239 Identification allows emergency services authorities to know during 240 call processing which types of data are present and to determine if 241 they wish to access it. A common encoding allows the data to be 242 successfully accessed. 244 This document defines an extensible set of data structures, and 245 mechanisms to transmit this data either by value or by reference, 246 either in the Session Initiation Protocol (SIP) call signaling or in 247 the Presence Information Data Format Location Object (PIDF-LO). The 248 data structures are usable by other communication systems and 249 transports as well. The data structures are defined in Section 4, 250 and the transport mechanisms (using SIP and HTTPS) are defined in 251 Section 5. 253 Each data structure described in this document is encoded as a 254 "block" of information. Each block is an XML structure with an 255 associated Multipurpose Internet Mail Extensions (MIME) type for 256 identification within transport such as SIP and HTTPS. The set of 257 blocks is extensible. Registries are defined to identify the block 258 types that may be used and to allow blocks to be included in 259 emergency call signaling. 261 2. Terminology 263 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 264 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 265 document are to be interpreted as described in RFC 2119 [RFC2119]. 267 This document also uses terminology from [RFC5012]. We use the term 268 service provider to refer to an Application Service Provider (ASP). 269 A Voice Service Provider (VSP) is a special type of ASP. With the 270 term "Access Network Provider" we refer to the Internet Access 271 Provider (IAP) and the Internet Service Provider (ISP) without 272 further distinguishing these two entities, since the difference 273 between the two is not relevant for this document. Note that the 274 roles of ASP and access network provider may be provided by a single 275 company. An Emergency Services Provider is an entity directly 276 involved in providing emergency services. This includes PSAPs, 277 dispatch, police, fire, emergency medical, other responders, and 278 other similar agencies. 280 Within each data block definition (see Section 4), the values for the 281 "Use:" label are specified as one of the following: 283 'Required': means it MUST be present in the data structure. 285 'Conditional': means it MUST be present if the specified 286 condition(s) is met. It MAY be present if the condition(s) is not 287 met. 289 'Optional': means it MAY be present. 291 vCard is a data format for representing and exchanging a variety of 292 information about individuals and other entities. For applications 293 that use XML the format defined in vCard is not immediately 294 applicable. For this purpose an XML-based encoding of the 295 information elements defined in the vCard specification has been 296 defined and the name of that specification is xCard. Since the term 297 vCard is more familiar to most readers, we use the term xCard and 298 vCard interchangeably. 300 3. Document Scope 302 The scope of this document is explicitly limited to emergency calls. 303 The data structures defined here are not appropriate to be conveyed 304 with non-emergency calls because they carry sensitive and private 305 data. 307 4. Data Structures 309 This section defines the following five data structures, each as a 310 data block. For each block we define the MIME type, and the XML 311 encoding. The five data structures are: 313 'Data Provider': This block supplies name and contact information 314 for the entity that created the data. Section 4.1 provides the 315 details. 317 'Service Information': This block supplies information about the 318 service. The description can be found in Section 4.2. 320 'Device Information': This block supplies information about the 321 device placing the call. Device information can be found in 322 Section 4.3. 324 'Owner/Subscriber': This block supplies information about the owner 325 of the device or about the subscriber. Details can be found in 326 Section 4.4. 328 'Comment': This block provides a way to supply free form human 329 readable text to the PSAP or emergency responders. This simple 330 structure is defined in Section 4.5. 332 Each block contains a mandatory element. The 333 purpose of the element is to associate all 334 blocks added by the same data provider as a unit. The 335 element associates the data provider block to 336 each of the other blocks added as a unit. Consequently, when a data 337 provider adds additional data to an emergency call (such as device 338 information) it MUST add information about itself (via the data 339 provider block) and the blocks added contain the same value in the 340 element. All blocks added by a single entity 341 at the same time MUST have the same value. 342 The value of the element has the same syntax 343 and properties (specifically, world-uniqueness) as the value of the 344 "Message-ID" message body header field specified in RFC 5322 345 [RFC5322] except that the element is not 346 enclosed in brackets (the "<" and ">" symbols are omitted). In other 347 words, the value of a element is 348 syntactically a msg-id as specified in RFC 5322 [RFC5322]. 350 Note that the xCard format is re-used in some of the data structures 351 to provide contact information. In an xCard there is no way to 352 specify a "main" telephone number. These numbers are useful to 353 emergency responders who are called to a large enterprise. This 354 document adds a new property value to the "tel" property of the TYPE 355 parameter called "main". It can be used in any xCard in additional 356 data. 358 4.1. Data Provider Information 360 This block is intended to be supplied by any service provider in the 361 path of the call or the access network provider. It includes 362 identification and contact information. This block SHOULD be 363 supplied by every service provider in the call path, and by the 364 access network provider. Devices MAY use this block to provide 365 identifying information. The MIME subtype is "application/ 366 EmergencyCallData.ProviderInfo+xml". An access network provider 367 SHOULD provide this block either by value or by reference in the 368 provided-by section of a PIDF-LO 370 4.1.1. Data Provider String 372 Data Element: Data Provider String 374 Use: Required 376 XML Element: 378 Description: This is a plain text string suitable for displaying the 379 name of the service provider that supplied the data structure. If 380 the device creates the structure, it SHOULD use the value of the 381 contact header in the SIP INVITE. 383 Reason for Need: Inform the call taker of the identity of the entity 384 providing the data. 386 How Used by Call Taker: Allows the call taker to interpret the data 387 in this structure. The source of the information often influences 388 how the information is used, believed or verified. 390 4.1.2. Data Provider ID 392 Data Element: Data Provider ID 394 Use: Required. This data MUST be provided in order to uniquely 395 identify the service provider or access provider. 397 XML Element: 399 Description: A jurisdiction-specific code for, or the fully- 400 qualified domain name of, the access network provider or service 401 provider shown in the element that created the 402 structure. NOTE: The value SHOULD be assigned by an organization 403 appropriate for the jurisdiction. In the U.S., the provider's 404 NENA Company ID MUST appear here. Additional information can be 405 found at NENA Company Identifier Program [1] or NENA Company ID 406 [2]. The NENA Company ID MUST be in the form of a URI in the 407 following format: urn:nena:companyid:. The value 408 MAY be the fully-qualified domain name of the service provider or 409 access provider. 411 Reason for Need: Inform the call taker of the identity of the entity 412 providing the data. 414 How Used by Call Taker: Where jurisdictions have lists of providers 415 the Data Provider ID provides useful information about the data 416 source. The Data Provider ID uniquely identifies the source of 417 the data, which might be needed especially during unusual 418 circumstances and for routine logging. 420 4.1.3. Data Provider ID Series 422 Data Element: Data Provider ID Series 424 Use: Required. 426 XML Element: 428 Description: Identifies the issuer of the . The 429 Provider ID Series Registry (see Section 10.1) initially contains 430 the following valid entries: 432 * NENA 433 * EENA 435 * domain 437 Reason for Need: Identifies how to interpret the Data Provider ID. 438 The combination of ProviderIDSeries and ProviderID MUST be 439 globally unique. 441 How Used by Call Taker: Determines which provider ID registry to 442 consult for more information 444 4.1.4. Type of Data Provider 446 Data Element: Type of Data Provider 448 Use: Required. 450 XML Element: 452 Description: Identifies the type of data provider supplying the 453 data. A registry with an initial set of values is shown in 454 Figure 1 (see also Section 10.1). 456 +------------------------------+------------------------------------+ 457 | Token | Description | 458 +------------------------------+------------------------------------+ 459 |Access Network Provider | Access network service provider | 460 |Telecom Provider | Calling or origination telecom SP | 461 |Telematics Provider | A sensor based service provider, | 462 | | especially vehicle based | 463 |Language Translation Provider | A spoken language translation SP | 464 |Emergency Service Provider | An emergency service provider | 465 | | conveying information to another| 466 | | emergency service provider. | 467 |Emergency Modality Translation| An emergency call specific | 468 | | modality translation service | 469 | | e.g., for sign language | 470 |Relay Provider | A interpretation SP, for example, | 471 | | video relay for sign language | 472 | | interpreting | 473 |Other | Any other type of service provider | 474 +------------------------------+------------------------------------+ 476 Figure 1: Type of Data Provider Registry. 478 Reason for Need: Identifies the category of data provider. 480 How Used by Call Taker: This information may be helpful when 481 deciding whom to contact when further information is needed. 483 4.1.5. Data Provider Contact URI 485 Data Element: Data Provider Contact URI 487 Use: Required 489 XML Element: 491 Description: When provided by a service provider or an access 492 network provider, this information MUST be a URI to a 24/7 support 493 organization tasked to provide PSAP support for this emergency 494 call. If the call is from a device, this SHOULD be the contact 495 information of the owner of the device. The Data Provider Contact 496 URI SHOULD be a TEL URI [RFC3966] in E.164 format fully specified 497 with country code. If a TEL URI is not available, it MAY be a 498 generic SIP URI. Note that this contact information is not used 499 by PSAPs for callbacks (a call from a PSAP directly related to a 500 recently terminated emergency call, placed by the PSAP using a SIP 501 Priority header field set to "psap-callback", as described in 502 [RFC7090]). 504 Reason for Need: Additional data providers may need to be contacted 505 in error cases or other unusual circumstances. 507 How Used by Call Taker: To contact the supplier of the additional 508 data for assistance in handling the call. 510 4.1.6. Data Provider Languages(s) Supported 512 Data Element: Data Provider Language(s) supported 514 Use: Required. 516 XML Element: 518 Description: The language used by the entity at the Data Provider 519 Contact URI, as an alpha 2-character code as defined in ISO 520 639-1:2002 Codes for the representation of names of languages -- 521 Part 1: Alpha-2 code Multiple instances of this element may occur. 522 Order is significant; preferred language should appear first. The 523 content MUST reflect the languages supported at the contact URI. 525 Note that the 'language' media feature tag, defined in RFC 3840 526 [RFC3840] and the more extensive language negotiation mechanism 527 proposed with [I-D.gellens-slim-negotiating-human-language] are 528 independent of this data provider language indication. 530 Reason for Need: This information indicates if the emergency service 531 authority can directly communicate with the service provider or if 532 an interpreter will be needed. 534 How Used by Call Taker: If the call taker cannot speak any language 535 supported by the service provider, a translation service will need 536 to be added to the conversation. Alternatively, other persons at 537 the PSAP, besides the call taker, might be consulted for help 538 (depending on the urgency and the type of interaction). 540 4.1.7. xCard of Data Provider 542 Data Element: xCard of Data Provider 544 Use: Optional 546 XML Element: 548 Description: Per [RFC6351] the xcard structure is represented within 549 a element, which is a child element of a element. 550 The fact that a element is contained within a 551 element structurally permits multiple elements, however, 552 only one element SHOULD be provided. If more than one 553 appears, the first SHOULD be used. There are many fields in the 554 xCard and the creator of the data structure is encouraged to 555 provide as much information as they have available. N, ORG, ADR, 556 TEL, EMAIL are suggested at a minimum. N SHOULD contain the name 557 of the support group or device owner as appropriate. If more than 558 one TEL property is provided, a parameter from the vCard Property 559 Value registry MUST be specified on each TEL. For encoding of the 560 xCard this specification uses the XML-based encoding specified in 561 [RFC6351], referred to in this document as "xCard". 563 Reason for Need: Information needed to determine additional contact 564 information. 566 How Used by Call Taker: Assists the call taker by providing 567 additional contact information aside from what may be included in 568 the SIP INVITE or the PIDF-LO. 570 4.1.8. Subcontractor Principal 572 When the entity providing the data is a subcontractor, the Data 573 Provider Type is set to that of the primary service provider and this 574 entry is supplied to provide information regarding the subcontracting 575 entity. 577 Data Element: Subcontractor Principal 579 Use: Conditional. This data is required if the entity providing the 580 data is a subcontractor. 582 XML Element: 584 Description: Some providers outsource their obligations to handle 585 aspects of emergency services to specialized providers. If the 586 data provider is a subcontractor to another provider this element 587 contains the DataProviderString of the service provider to 588 indicate which provider the subcontractor is working for. 590 Reason for Need: Identify the entity the subcontractor works for. 592 How Used by Call Taker: Allows the call taker to understand what the 593 relationship between data providers and the service providers in 594 the path of the call are. 596 4.1.9. Subcontractor Priority 598 Data Element: Subcontractor Priority 600 Use: Conditional. This element is required if the Data Provider 601 type is set to "Subcontractor". 603 XML Element: 605 Description: If the subcontractor has to be contacted first then 606 this element MUST have the value "sub". If the provider the 607 subcontractor is working for has to be contacted first then this 608 element MUST have the value "main". 610 Reason for Need: Inform the call taker whom to contact first, if 611 support is needed. 613 How Used by Call Taker: To decide which entity to contact first if 614 assistance is needed. 616 4.1.10. ProviderInfo Example 618 619 622 string0987654321@example.org 623 624 Example VoIP Provider 625 626 urn:nena:companyid:ID123 627 NENA 628 Telecom Provider 629 tel:+1-201-555-0123 630 EN 631 633 634 635 Hannes Tschofenig 636 637 Hannes 638 Tschofenig 639 640 641 Dipl. Ing. 642 643 --0203 644 645 20090808T1430-0500 646 647 M 648 649 1 650 651 de 652 653 654 2 655 656 en 657 658 659 work 660 661 Example VoIP Provider 662 663 664 665 work 666 670 671 672 673 Linnoitustie 6 674 Espoo 675 Uusimaa 676 02600 677 Finland 678 679 680 681 682 work 683 voice 684 685 686 tel:+358 50 4871445 687 688 689 work 690 691 hannes.tschofenig@nsn.com 692 693 694 work 695 696 geo:60.210796,24.812924 697 698 699 home 700 701 702 http://www.tschofenig.priv.at/key.asc 703 704 705 Finland/Helsinki 706 707 home 708 709 http://www.tschofenig.priv.at 710 711 712 713 714 716 Figure 2: EmergencyCallData.ProviderInfo Example. 718 4.2. Service Information 720 This block describes the service that the service provider provides 721 to the caller. It SHOULD be included by all SPs in the path of the 722 call. The mime subtype is "application/ 723 EmergencyCallData.ServiceInfo+xml". 725 4.2.1. Service Environment 727 Data Element: Service Environment 729 Use: Optional when a 'ServiceType' value is 'wireless'; required 730 otherwise. 732 XML Element: 734 Description: This element defines whether a call is from a business 735 or residence caller. Currently, the only valid entries are 736 'Business', 'Residence', and 'unknown'. New values can be defined 737 via the registry created in Figure 22. 739 Reason for Need: To provide context and a hint when determining 740 equipment and manpower requirements. 742 How Used by Call Taker: Information may be used to provide context 743 and a hint to assist in determining equipment and manpower 744 requirements for emergency responders. Because there are cases 745 where the service provider does not know (such as anonymous pre- 746 paid service), and the type of service does not neccessarily 747 reflect the nature of the premises (for example, a business line 748 installed in a residence, or wireless service), and the registry 749 is not all encompassing, therefore this is at best advisory 750 information, but since it mimics a similar capability in some 751 current emergency calling systems (e.g., a field in the Automatic 752 Location Information (ALI) information used with legacy North 753 American wireline systems), it is known to be valuable. The 754 service provider uses its best information (such as a rate plan, 755 facilities used to deliver service or service description) to 756 determine the information and is not responsible for determining 757 the actual characteristics of the location from which the call 758 originated. Because the usefulness is unknown (and less clear) 759 for wireless, this element is OPTIONAL for wireless and REQUIRED 760 otherwise. 762 4.2.2. Service Type 764 Data Element: Service Delivered by Provider to End User 766 Use: Required 768 XML Element: 770 Description: This defines the type of service over which the call is 771 placed. The implied mobility of this service cannot be relied 772 upon. A registry with an initial set of values is defined in 773 Figure 3. 775 +--------------+----------------------------------------+ 776 | Name | Description | 777 +--------------+----------------------------------------+ 778 | wireless | Wireless Telephone Service: Includes | 779 | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | 780 | | not satellite) | 781 | coin | Fixed public pay/coin telephones: Any | 782 | | coin or credit card operated device | 783 | one-way | One way outbound service | 784 | prison | Inmate call/service | 785 | temp | Soft dial tone/quick service/warm | 786 | | disconnect/suspended | 787 | MLTS-hosted | Hosted multi-line telephone system | 788 | | such as Centrex | 789 | MLTS-local | Local multi-line telephone system, | 790 | | includes all PBX, key systems, | 791 | | Shared Tenant Service | 792 | sensor- | 793 | unattended | These are devices that generate DATA | 794 | | ONLY. This is a one-way information | 795 | | transmit without interactive media | 796 | sensor- | | 797 | attended | Devices that are supported by a | 798 | | monitoring service provider or that | 799 | | are capable of supporting interactive| 800 | | media | 801 | POTS | Wireline: Plain Old Telephone Service | 802 | VOIP | An over-the-top service that provides | 803 | | communication over arbitrary Internet| 804 | | access (fixed, nomadic, mobile) | 805 | remote | Off premise extension | 806 | relay | A service where there is a human third | 807 | | party agent who provides additional | 808 | | assistance. This includes sign | 809 | | language relay and telematics | 810 | | services that provide a human on the | 811 | | call. | 812 +--------------+----------------------------------------+ 814 Figure 3: Service Delivered by Provider to End User Registry. 816 More than one value MAY be returned. For example, a VoIP inmate 817 telephone service is a reasonable combination. 819 Reason for Need: Knowing the type of service may assist the PSAP 820 with the handling of the call. 822 How Used by Call Taker: Call takers often use this information to 823 determine what kinds of questions to ask callers, and how much to 824 rely on supportive information. An emergency call from a prison 825 is treated differently than a call from a sensor device. As the 826 information is not always available, and the registry is not all 827 encompassing, this is at best advisory information, but since it 828 mimics a similar capability in some current emergency calling 829 systems, it is known to be valuable. 831 4.2.3. Service Mobility Environment 833 Data Element: Service Mobility Environment 835 Use: Required 837 XML Element: 839 Description: This provides the service provider's view of the 840 mobility of the caller's device. As the service provider may not 841 know the characteristics of the actual device or access network 842 used, the value MUST NOT be relied upon. The registry specified 843 in Figure 23 reflects the following initial valid entries: 845 * Mobile: the device is able to move at any time 847 * Fixed: the device is not expected to move unless the service is 848 relocated 850 * Nomadic: the device is not expected to change its point of 851 attachment while on a call 853 * Unknown: no information is known about the service mobility 854 environment for the device 856 Reason for Need: Knowing the service provider's belief of mobility 857 may assist the PSAP with the handling of the call. 859 How Used by Call Taker: To determine whether to assume the location 860 of the caller might change. 862 4.2.4. EmergencyCallData.ServiceInfo Example 863 864 867 2468.IBOC.MLTS.1359@example.org 868 869 Business 870 MLTS-hosted 871 Fixed 872 874 Figure 4: EmergencyCallData.ServiceInfo Example. 876 4.3. Device Information 878 This block provides information about the device used to place the 879 call. It should be provided by any service provider that knows what 880 device is being used, and by the device itself. The mime subtype is 881 "application/EmergencyCallData.DeviceInfo+xml". 883 4.3.1. Device Classification 885 Data Element: Device Classification 887 Use: Optional 889 XML Element: 891 Description: This data element defines the kind of device making the 892 emergency call. If the device provides the data structure, the 893 device information SHOULD be provided. If the service provider 894 provides the structure and it knows what the device is, the 895 service provider SHOULD provide the device information. Often the 896 carrier does not know what the device is. It is possible to 897 receive two Additional Data Associated with a Call data 898 structures, one created by the device and one created by the 899 service provider. This information describes the device, not how 900 it is being used. This data element defines the kind of device 901 making the emergency call. The registry with the initial set of 902 values is shown in Figure 5. 904 +---------------+----------------------------------------+ 905 | Token | Description | 906 +---------------+----------------------------------------+ 907 |cordless | Cordless handset | 908 |fixed | Fixed phone | 909 |satellite | Satellite phone | 910 |sensor-fixed | Fixed (non mobile) sensor/alarm device | 911 |desktop | Soft client on desktop PC | 912 |laptop | Soft client on laptop type device | 913 |tablet | Soft client on tablet type device | 914 |alarm-monitored| Alarm system | 915 |sensor-mobile | Mobile sensor device | 916 |aircraft | Aircraft telematics device | 917 |automobile | Automobile/cycle/off-road telematics | 918 |truck | Truck/construction telematics | 919 |farm | Farm equipment telematics | 920 |marine | Marine telematics | 921 |personal | Personal telematics device | 922 |feature-phone | Feature- (not smart-) cellular phone | 923 |smart-phone | Smart-phone cellular phone (native) | 924 |smart-phone-app| Soft client app on smart-phone | 925 |unknown-device | Soft client on unknown device type | 926 |game | Gaming console | 927 |text-only | Other text device | 928 |NA | Not Available | 929 +---------------+----------------------------------------+ 931 Figure 5: Device Classification Registry. 933 Reason for Need: The device classification implies the capability of 934 the calling device and assists in identifying the meaning of the 935 emergency call location information that is being presented. For 936 example, does the device require human intervention to initiate a 937 call or is this call the result of programmed instructions? Does 938 the calling device have the ability to update location or 939 condition changes? Is this device interactive or a one-way 940 reporting device? 942 How Used by Call Taker: May provide the call taker context regarding 943 the caller, the capabilities of the calling device or the 944 environment in which the device is being used, and may assist in 945 understanding the location information and capabilities of the 946 calling device. For example, a cordless handset may be outside or 947 next door. 949 4.3.2. Device Manufacturer 951 Data Element: Device Manufacturer 953 Use: Optional 955 XML Element: 957 Description: The plain language name of the manufacturer of the 958 device. 960 Reason for Need: Used by PSAP management for post-mortem 961 investigation/resolution. 963 How Used by Call Taker: Probably not used by the calltaker, but by 964 PSAP management. 966 4.3.3. Device Model Number 968 Data Element: Device Model Number 970 Use: Optional 972 XML Element: 974 Description: Model number of the device. 976 Reason for Need: Used by PSAP management for after action 977 investigation/resolution. 979 How Used by Call Taker: Probably not used by the calltaker, but by 980 PSAP management. 982 4.3.4. Unique Device Identifier 984 Data Element: Unique Device Identifier 986 Use: Optional 988 XML Element: 990 XML Attribute: 992 Description: A string that identifies the specific device (or the 993 device's current SIM) making the call or creating an event. Note 994 that more than one may be present, to supply more 995 than one of the identifying values. 997 The attribute identifies the type of device 998 identifier. A registry with an initial set of values can be seen 999 in Figure 6. 1001 +--------+------------------------------------------+ 1002 | Token | Description | 1003 +--------+------------------------------------------+ 1004 | MEID | Mobile Equipment Identifier (CDMA) | 1005 | ESN | Electronic Serial Number (GSM) | 1006 | MAC | Media Access Control Address (IEEE) | 1007 | WiMAX | Device Certificate Unique ID | 1008 | IMEI | International Mobile Equipment ID (GSM) | 1009 | IMSI | International Mobile Subscriber ID (GSM) | 1010 | UDI | Unique Device Identifier | 1011 | RFID | Radio Frequency Identification | 1012 | SN | Manufacturer Serial Number | 1013 +--------+------------------------------------------+ 1015 Figure 6: Registry with Device Identifier Types. 1017 Reason for Need: Uniquely identifies the device (or, in the case of 1018 IMSI, a SIM), independent of any signaling identifiers present in 1019 the call signaling stream. 1021 How Used by Call Taker: Probably not used by the call taker; may be 1022 used by PSAP management during an investigation. 1024 Example: 12345 1026 4.3.5. Device/Service Specific Additional Data Structure 1028 Data Element: Device/service specific additional data structure 1030 Use: Optional 1032 XML Element: 1034 Description: A URI representing additional data whose schema is 1035 specific to the device or service which created it. (For example, 1036 a medical device or medical device monitoring service may have a 1037 defined set of medical data). The URI, when dereferenced, MUST 1038 yield a data structure defined by the Device/service specific 1039 additional data type value. Different data may be created by each 1040 classification; e.g., a medical device created data set. 1042 Reason for Need: Provides device/service specific data that may be 1043 used by the call taker and/or responders. 1045 How Used by Call Taker: Provide information to guide call takers to 1046 select appropriate responders, give appropriate pre-arrival 1047 instructions to callers, and advise responders of what to be 1048 prepared for. May be used by responders to guide assistance 1049 provided. 1051 4.3.6. Device/Service Specific Additional Data Structure Type 1053 Data Element: Type of device/service specific additional data 1054 structure 1056 Use: Conditional. MUST be provided when device/service specific 1057 additional URI is provided 1059 XML Element: 1061 Description: Value from a registry defined by this document to 1062 describe the type of data that can be retrieved from the device/ 1063 service specific additional data structure. Initial values are: 1065 * IEEE 1512 1067 IEEE 1512 is the USDoT model for traffic incidents. 1069 Reason for Need: This data element allows identification of 1070 externally defined schemas, which may have additional data that 1071 may assist in emergency response. 1073 How Used by Call Taker: This data element allows the end user 1074 (calltaker or first responder) to know what type of additional 1075 data may be available to aid in providing the needed emergency 1076 services. 1078 Note: Information which is specific to a location or a caller 1079 (person) should not be placed in this section. 1081 4.3.7. Issues with getting new types of data into use 1083 This document describes two mechanisms which allow extension of the 1084 kind of data provided with an emergency call: define a new block or 1085 define a new service specific additional data URL for the DeviceInfo 1086 block. While defining new data types and getting a new device or 1087 application to send the new data may be easy, getting PSAPs and 1088 responders to actually retrieve the data and use it will be 1089 difficult. New mechanism providers should understand that acquiring 1090 and using new forms of data usually require software upgrades at the 1091 PSAP and/or responders, as well as training of call takers and 1092 responders in how to interpret and use the information. Legal and 1093 operational review may also be needed. Overwhelming a call taker or 1094 responder with too much information is highly discouraged. Thus, the 1095 barrier to supporting new data is quite high. 1097 The mechanisms this document describes are meant to encourage 1098 development of widely supported, common data formats for classes of 1099 devices. If all manufacturers of a class of device use the same 1100 format, and the data can be shown to improve outcomes, then PSAPs and 1101 responders may be encouraged to upgrade their systems and train their 1102 staff to use the data. Variations, however well intentioned, are 1103 unlikely to be supported. 1105 Implementers should consider that data from sensor-based devices in 1106 some cases may not be useful to call takers or PSAPs (and privacy or 1107 other considerations may preclude the PSAP from touching the data), 1108 but may be of use to responders. Some standards being developed by 1109 other organizations to carry data from the PSAP to responders are 1110 designed to carry all additional data supplied in the call that 1111 conform to this document, even if the PSAP does not fetch or 1112 interpret the data. This allows responders to get the data even if 1113 the PSAP does not. 1115 4.3.8. Choosing between defining a new type of block or new type of 1116 device/service specific additional data 1118 For devices that have device or service specific data, there are two 1119 choices to carry it. A new block can be defined, or the device/ 1120 service specific additional data URL the DeviceInfo block can be used 1121 and a new type for it defined . The data passed would likely be the 1122 same in both cases. Considerations for choosing which mechanism to 1123 register under include: 1125 Applicability: Information which will be carried by many kinds of 1126 devices or services are more appropriately defined as separate 1127 blocks. 1129 Privacy: Information which may contain private data may be better 1130 sent in the DeviceInfo block, rather than a new block so that 1131 implementations are not tempted to send the data by value, and 1132 thus having more exposure to the data than forcing the data to be 1133 retrieved via the URL in DeviceInfo. 1135 Size: Information which may be very large may be better sent in the 1136 DeviceInfo block, rather than a new block so that implementations 1137 are not tempted to send the data by value. Conversely, data which 1138 is small may best be sent in a separate block so that it can be 1139 sent by value 1141 Availability of a server: Providing the data via the device block 1142 requires a server be made available to retrieve the data. 1143 Providing the data via new block allows it to be sent by value 1144 (CID). 1146 4.3.9. EmergencyCallData.DeviceInfo Example 1148 1149 1152 d4b3072df.201409182208075@example.org 1153 1154 fixed 1155 Nokia 1156 Lumia 800 1157 35788104 1158 1159 1161 Figure 7: EmergencyCallData.DeviceInfo Example. 1163 4.4. Owner/Subscriber Information 1165 This block describes the owner of the device (if provided by the 1166 device) or the subscriber information (if provided by a service 1167 provider). The contact location is not necessarily the location of 1168 the caller or incident, but is rather the nominal contact address. 1169 The MIME type is "application/EmergencyCallData.SubscriberInfo+xml". 1171 In some jurisdictions some or all parts of the subscriber-specific 1172 information are subject to privacy constraints. These constraints 1173 vary but dictate what information can be displayed and logged. A 1174 general privacy indicator expressing a desire for privacy is 1175 provided. The interpretation of how this is applied is left to the 1176 receiving jurisdiction as the custodians of the local regulatory 1177 requirements. 1179 4.4.1. Subscriber Data Privacy Indicator 1181 Attribute: privacyRequested, boolean. 1183 Use: Conditional. This attribute MUST be provided if the owner/ 1184 subscriber information block is not empty. 1186 Description: The subscriber data privacy indicator specifically 1187 expresses the subscriber's desire for privacy. In some 1188 jurisdictions subscriber services can have a specific "Type of 1189 Service" which prohibits information, such as the name of the 1190 subscriber, from being displayed. This attribute should be used 1191 to explicitly indicate whether the subscriber service includes 1192 such constraints. 1194 Reason for Need: Some jurisdictions require subscriber privacy to be 1195 observed when processing emergency calls. 1197 How Used by Call Taker: Where privacy is indicated the call taker 1198 may not have access to some aspects of the subscriber information. 1200 4.4.2. xCard for Subscriber's Data 1202 Data Element: xCARD for Subscriber's Data 1204 Use: Conditional. Subscriber data is provided unless it is not 1205 available. Some services, for example prepaid phones, non- 1206 initialized phones, etc., do not have information about the 1207 subscriber. 1209 XML Element: 1211 Description: Information known by the service provider or device 1212 about the subscriber; e.g., Name, Address, Individual Telephone 1213 Number, Main Telephone Number and any other data. N, ORG (if 1214 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1215 than one TEL property is provided, a parameter from the vCard 1216 Property Value registry MUST be specified on each TEL. 1218 Reason for Need: When the caller is unable to provide information, 1219 this data may be used to obtain it 1221 How Used by Call Taker: Obtaining critical information about the 1222 caller and possibly the location when it is not able to be 1223 obtained otherwise. 1225 4.4.3. EmergencyCallData.SubscriberInfo Example 1227 1228 1233 FEABFECD901@example.org 1234 1235 1236 1237 1238 Simon Perreault 1239 1240 Perreault 1241 Simon 1242 1243 1244 ing. jr 1245 M.Sc. 1246 1247 --0203 1248 1249 20090808T1430-0500 1250 1251 M 1252 1253 1 1254 1255 fr 1256 1257 1258 2 1259 1260 en 1261 1262 1263 work 1264 1265 Viagenie 1266 1267 1268 1269 work 1270 1274 1275 1276 1277 2875 boul. Laurier, suite D2-630 1278 Quebec 1279 QC 1280 G1V 2M2 1281 Canada 1282 1283 1284 1285 1286 work 1287 voice 1288 1289 1290 tel:+1-418-656-9254;ext=102 1291 1292 1293 1294 1295 work 1296 text 1297 voice 1298 cell 1299 video 1300 1301 1302 tel:+1-418-262-6501 1303 1304 1305 work 1306 1307 simon.perreault@viagenie.ca 1308 1309 1310 work 1311 1312 geo:46.766336,-71.28955 1313 1314 1315 work 1316 1317 1318 http://www.viagenie.ca/simon.perreault/simon.asc 1319 1320 1321 America/Montreal 1322 1323 home 1324 1325 http://nomis80.org 1326 1327 1328 1329 1330 1331 Figure 8: EmergencyCallData.SubscriberInfo Example. 1333 4.5. Comment 1335 This block provides a mechanism for the data provider to supply 1336 extra, human readable information to the PSAP. It is not intended 1337 for a general purpose extension mechanism nor does it aim to provide 1338 machine-readable content. The mime subtype is "application/ 1339 EmergencyCallData.Comment+xml" 1341 4.5.1. Comment 1343 Data Element: EmergencyCallData.Comment 1345 Use: Optional 1347 XML Element: 1349 Description: Human readable text providing additional information to 1350 the PSAP staff. 1352 Reason for Need: Explanatory information for values in the data 1353 structure. 1355 How Used by Call Taker: To interpret the data provided. 1357 4.5.2. EmergencyCallData.Comment Example 1359 1360 1363 string0987654321@example.org 1364 1365 This is an example text. 1366 1368 Figure 9: EmergencyCallData.Comment Example. 1370 5. Data Transport Mechanisms 1372 This section defines how to convey additional data to an emergency 1373 service provider. Two different means are specified: the first uses 1374 the call signaling; the second uses the element of a 1375 PIDF-LO [RFC4119]. 1377 1. First, the ability to embed a Uniform Resource Identifier (URI) 1378 in an existing SIP header field, the Call-Info header, is 1379 defined. The URI points to the additional data structure. The 1380 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1381 document adds a new compound token starting with the value 1382 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1383 the "purpose" parameter is set to a value starting with 1384 'EmergencyCallData', then the Call-Info header contains either an 1385 HTTPS URL pointing to an external resource or a CID (content 1386 indirection) URI that allows the data structure to be placed in 1387 the body of the SIP message. The "purpose" parameter also 1388 indicates the kind of data (by its MIME type) that is available 1389 at the URI. As the data is conveyed using a URI in the SIP 1390 signaling, the data itself may reside on an external resource, or 1391 may be contained within the body of the SIP message. When the 1392 URI refers to data at an external resource, the data is said to 1393 be passed by reference. When the URI refers to data contained 1394 within the body of the SIP message, the data is said to be passed 1395 by value. A PSAP or emergency responder is able to examine the 1396 type of data provided and selectively inspect the data it is 1397 interested in, while forwarding all of it (the values or 1398 references) to downstream entities. To be conveyed in a SIP 1399 body, additional data about a call is defined as a series of MIME 1400 objects. Each block defined in this document is an XML data 1401 structure identified by its MIME type. (Blocks defined by others 1402 may be encoded in XML or not, as identified by their MIME 1403 registration.) As usual, whenever more than one MIME part is 1404 included in the body of a message, MIME-multipart (i.e., 1405 'multipart/mixed') encloses them all. This document defines a 1406 set of XML schemas and MIME types used for each block defined 1407 here. When additional data is passed by value in the SIP 1408 signaling, each CID URL points to one block in the body. 1409 Multiple URIs are used within a Call-Info header field (or 1410 multiple Call-Info header fields) to point to multiple blocks. 1411 When additional data is provided by reference (in SIP signaling 1412 or provided-by), each HTTPS URL references one block; the data is 1413 retrieved with an HTTPS GET operation, which returns one of the 1414 blocks as an object (the blocks defined here are returned as XML 1415 objects). 1417 2. Second, the ability to embed additional data structures in the 1418 element of a PIDF-LO [RFC4119] is defined. In 1419 addition to service providers in the call path, the access 1420 network provider may also have similar information that may be 1421 valuable to the PSAP. The access network provider MAY provide 1422 location in the form of a PIDF-LO from a location server via a 1423 location configuration protocol. The data structures described 1424 in this document are not specific to the location itself, but 1425 rather provides descriptive information having to do with the 1426 immediate circumstances about the provision of the location (who 1427 the access network is, how to contact that entity, what kind of 1428 service the access network provides, subscriber information, 1429 etc.). This data is similar in nearly every respect to the data 1430 known by service providers in the path of the call. When the 1431 access network provider and service provider are separate 1432 entities, the access network does not participate in the 1433 application layer signaling (and hence cannot add a Call-Info 1434 header field to the SIP message), but may provide location 1435 information in a PIDF-LO object to assist in locating the 1436 caller's device. The element of the PIDF-LO is a 1437 mechanism for the access network provider to supply the 1438 information about the entity or organization that supplied this 1439 location information. For this reason, this document describes a 1440 namespace per RFC 4119 for inclusion in the element 1441 of a PIDF-LO for adding information known to the access network 1442 provider. The access network provider SHOULD provide additional 1443 data within a provided-by element of a PDIF-LO it returns for 1444 emergency use (e.g., if requested with a HELD "responseTime" 1445 attribute of "emergencyRouting" or "emergencyDispatch" 1446 [RFC5985]). 1448 One or more blocks of data registered in the Emergency Call 1449 Additional Data registry, as defined in Section 10.1, may be included 1450 or referenced in the SIP signaling (using the Call-Info header field) 1451 or in the element of a PIDF-LO. Every block must be 1452 one of the types in the registry. Since the data of an emergency 1453 call may come from multiple sources, the data itself needs 1454 information describing the source. Consequently, each entity adding 1455 additional data MUST supply the "Data Provider" block. All other 1456 blocks are optional, but each entity SHOULD supply any blocks where 1457 it has at least some of the information in the block. 1459 5.1. Transmitting Blocks using the Call-Info Header 1461 A URI to a block MAY be inserted in a SIP request or response method 1462 (most often INVITE or MESSAGE) with a Call-Info header field 1463 containing a purpose value starting with 'EmergencyCallData' and the 1464 type of data available at the URI. The type of data is denoted by 1465 including the root of the MIME type (not including the 1466 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1467 separator. For example, when referencing a block with MIME type 1468 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1469 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1470 "Call-Info" header field for this would be: 1472 Call-Info: https://www.example.com/23sedde3; 1473 purpose="EmergencyCallData.ProviderInfo" 1475 A Call-info header with a purpose value starting with 1476 'EmergencyCallData' MUST only be sent on an emergency call, which can 1477 be ascertained by the presence of an emergency service urn in a Route 1478 header of a SIP message. 1480 If the data is provided by reference, an HTTPS URI MUST be included 1481 and consequently Transport Layer Security (TLS) protection is applied 1482 for protecting the retrieval of the information. 1484 The data may also be supplied by value in a SIP message. In this 1485 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1486 referencing the MIME body part. 1488 More than one Call-Info header with a purpose value starting with 1489 'EmergencyCallData' can be expected, but at least one MUST be 1490 provided. The device MUST provide one if it knows no service 1491 provider is in the path of the call. The device MAY insert one if it 1492 uses a service provider. Any service provider in the path of the 1493 call MUST insert its own. For example, a device, a telematics 1494 service provider in the call path, as well as the mobile carrier 1495 handling the call will each provide one. There may be circumstances 1496 where there is a service provider who is unaware that the call is an 1497 emergency call and cannot reasonably be expected to determine that it 1498 is an emergency call. In that case, that service provider is not 1499 expected to provide EmergencyCallData. 1501 5.2. Transmitting Blocks by Reference using the provided-by Element 1503 The 'EmergencyCallDataReference' element is used to transmit an 1504 additional data block by reference within a 'provided-by' element of 1505 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1506 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1507 type of data block referenced. The value of 'ref' is an HTTPS URL 1508 that resolves to a data structure with information about the call. 1509 The value of 'purpose' is the same as used in a 'Call-Info' header 1510 field (as specified in Section 5.1). 1512 For example, to reference a block with MIME type 'application/ 1513 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1514 to 'EmergencyCallData.ProviderInfo'. An example 1515 'EmergencyCallDataReference' element for this would be: 1517 1520 The 'EmergencyCallDataReference' element transmits one additional 1521 data block; multiple additional data blocks may be transmitted by 1522 using multiple 'EmergencyCallDataReference' elements. 1524 For example: 1526 1529 1533 1537 1541 1543 Example provided-by by Reference. 1545 5.3. Transmitting Blocks by Value using the provided-by Element 1547 It is RECOMMENDED that access networks supply the data specified in 1548 this document by reference, but they MAY provide the data by value. 1550 The 'EmergencyCallDataValue' element is used to transmit one or more 1551 additional data blocks by value within a 'provided-by' element of a 1552 PIDF-LO. Each block being transmitted is placed (as a child element) 1553 inside the 'EmergencyCallDataValue' element. (The same XML structure 1554 as would be contained in the corresponding MIME type body part is 1555 placed inside the 'EmergencyCallDataValue' element.) 1557 For example: 1559 1562 1564 1567 flurbit735@es.example.com 1568 1569 Access Network Examples, Inc 1570 1571 urn:nena:companyid:Test 1572 NENA 1573 Access Network Provider 1574 1575 tel:+1-555-555-0897 1576 EN 1577 1579 1582 flurbit735@es.example.com 1583 1584 This is an example text. 1585 1586 1588 1590 1592 Example provided-by by Value. 1594 5.4. The Content-Disposition Parameter 1596 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1597 It updates and clarifies handling originally defined in RFC 3261 1598 [RFC3261] based on implementation experience. While RFC 3261 did not 1599 mandate support for 'multipart' message bodies, 'multipart/mixed' 1600 MIME bodies are used by many extensions (including this document) 1601 today. For example, adding a PIDF-LO, SDP, and additional data in 1602 body of a SIP message requires a 'multipart' message body. 1604 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1605 parameter for the Content-Disposition header field. These RFCs 1606 describe how a UAS reacts if it receives a message body whose content 1607 type or disposition type it does not understand. If the 'handling' 1608 parameter has the value "optional", the UAS ignores the message body. 1609 If the 'handling' parameter has the value "required", the UAS returns 1610 a 415 (Unsupported Media Type) response. The 'by-reference' 1611 disposition type allows a SIP message to contain a reference to the 1612 body part, and the SIP UA processes the body part according to the 1613 reference. This is the case for the Call-info header containing a 1614 Content Indirection (CID) URL. 1616 As an example, a SIP message indicates the Content-Disposition 1617 parameter in the body of the SIP message as shown in Figure 10. 1619 Content-Type: application/sdp 1621 ...Omit Content-Disposition here; defaults are ok 1622 ...SDP goes in here 1624 --boundary1 1626 Content-Type: application/pidf+xml 1627 Content-ID: 1628 Content-Disposition: by-reference;handling=optional 1630 ...PIDF-LO goes in here 1632 --boundary1-- 1634 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1635 Content-ID: <1234567890@atlanta.example.com> 1636 Content-Disposition: by-reference; handling=optional 1638 ...Data provider information data goes in here 1640 --boundary1-- 1642 Figure 10: Example for use of the Content-Disposition Parameter in 1643 SIP. 1645 6. Examples 1647 This section illustrates a longer and more complex example, as shown 1648 in Figure 11. In this example additional data is added by the end 1649 device, included by the VoIP provider (via the PIDF-LO), and provided 1650 by the access network provider. 1652 O +----+ [============] [=============] 1653 /|\ | UA | [ Access ] [ VoIP ] 1654 | +----+ [ Network ] [ Provider ] 1655 / \ [ Provider ] [ example.org ] 1656 [ ] [ ] 1657 (1) [ ] (2) [ ] 1658 Emergency Call [ ] Emergency Call [ ] 1659 -------------------------------------------------------> ] 1660 +Device Info [ ] +Device Info [ ] 1661 +Data Prov. Info [ ^ ] +Data Provider Info [ | ] 1662 +Location URI [=======.====] +Location URI [==|==========] 1663 . | 1664 . | 1665 +Location . [==============] | 1666 +Owner/Subscriber Info . [ ] (3) | 1667 +Device Info . (4) [ <----------+ 1668 +Data Provider Info #3 ..........> ] Emergency Call 1669 [ ] +Device Info 1670 [ PSAP ] +Data Prov. Info #2 1671 [ ] +Location URI 1672 [==============] 1674 Legend: 1676 --- Emergency Call Setup Procedure 1677 ... Location Retrieval/Response 1679 Figure 11: Additional Data Example Flow 1681 The example scenario starts with the end device itself adding device 1682 information, owner/subscriber information, a location URI, and data 1683 provider information to the outgoing emergency call setup message 1684 (see step #1 in Figure 11). The SIP INVITE example is shown in 1685 Figure 12. 1687 INVITE urn:service:sos SIP/2.0 1688 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1689 Max-Forwards: 70 1690 To: 1691 From: Hannes Tschofenig ;tag=9fxced76sl 1692 Call-ID: 3848276298220188511@example.com 1693 Call-Info: 1694 ;purpose=icon, 1695 ;purpose=info, 1696 1697 ;purpose=EmergencyCallData.ProviderInfo, 1699 1700 ;purpose=EmergencyCallData.DeviceInfo 1701 Geolocation: 1702 Geolocation-Routing: yes 1703 Accept: application/sdp, application/pidf+xml, 1704 application/EmergencyCallData.ProviderInfo+xml 1705 CSeq: 31862 INVITE 1706 Contact: 1707 Content-Type: multipart/mixed; boundary=boundary1 1709 Content-Length: ... 1711 --boundary1 1713 Content-Type: application/sdp 1715 ...SDP goes here 1717 --boundary1-- 1719 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1720 Content-ID: <0123456789@atlanta.example.com> 1721 Content-Disposition: by-reference;handling=optional 1722 1724 1727 d4b3072df09876543@[93.184.216.119] 1728 1729 laptop 1730 00-0d-4b-30-72-df 1732 1734 --boundary1-- 1736 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1737 Content-ID: <1234567890@atlanta.example.com> 1738 Content-Disposition: by-reference;handling=optional 1739 1740 1743 d4b3072df09876543@[93.184.216.119] 1744 1745 Hannes Tschofenig 1746 1747 Other 1748 tel:+1-555-555-0123 1749 EN 1750 1752 1753 1754 Hannes Tschofenig 1755 1756 Hannes 1757 Tschofenig 1758 1759 1760 Dipl. Ing. 1761 1762 --0203 1763 1764 20090808T1430-0500 1765 1766 M 1767 1768 1 1769 1770 de 1771 1772 1773 2 1774 1775 en 1776 1777 1778 1779 work 1780 1784 1785 1786 1787 Linnoitustie 6 1788 Espoo 1789 Uusimaa 1790 02600 1791 Finland 1792 1793 1794 1795 1796 work 1797 voice 1798 1799 1800 tel:+358 50 4871445 1801 1802 1803 work 1804 1805 hannes.tschofenig@nsn.com 1806 1807 1808 work 1809 1810 geo:60.210796,24.812924 1811 1812 1813 1814 home 1815 1816 https://www.example.com/key.asc 1817 1818 1819 Finland/Helsinki 1820 1821 home 1822 1823 http://example.com/hannes.tschofenig 1824 1825 1826 1827 1828 1829 1830 --boundary1-- 1832 Figure 12: End Device sending SIP INVITE with Additional Data. 1834 In this example, information available to the access network provider 1835 is included in the call setup message only indirectly via the use of 1836 the location reference. The PSAP has to retrieve it via a separate 1837 look-up step. Since the access network provider and the VoIP service 1838 provider are two independent entities in this scenario, the access 1839 network provider is not involved in application layer exchanges; the 1840 SIP INVITE transits the access network transparently, as illustrated 1841 in steps #1 and #2. The access network does not alter the SIP 1842 INVITE. 1844 The VoIP service provider receives the message and determines based 1845 on the Service URN that the incoming request is an emergency call. 1846 It performs typical emergency services related tasks, including 1847 location-based routing, and adds additional data, namely service and 1848 subscriber information as well as data provider information #2, to 1849 the outgoing message. For the example we assume a VoIP service 1850 provider that deploys a back-to-back user agent allowing additional 1851 data to be included in the body of the SIP message (rather than per 1852 reference in the header), which allows us to illustrate the use of 1853 multiple data provider info blocks. The resulting message is shown 1854 in Figure 13. The SIP INVITE is sent to the PSAP in step #3. 1856 INVITE sips:psap@example.org SIP/2.0 1857 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1858 Max-Forwards: 70 1859 To: 1860 From: Hannes Tschofenig ;tag=9fxced76sl 1861 Call-ID: 3848276298220188511@example.com 1862 Call-Info: 1863 ;purpose=icon, 1864 ;purpose=info, 1865 1866 ;purpose=EmergencyCallData.ProviderInfo 1867 1868 ;purpose=EmergencyCallData.DeviceInfo 1869 Call-Info: 1870 ;purpose=EmergencyCallData.ServiceInfo 1871 Call-Info: 1872 ;purpose=EmergencyCallData.ProviderInfo 1873 Geolocation: 1874 Geolocation-Routing: yes 1875 Accept: application/sdp, application/pidf+xml, 1876 application/EmergencyCallData.ProviderInfo+xml 1877 CSeq: 31862 INVITE 1878 Contact: 1879 Content-Type: multipart/mixed; boundary=boundary1 1881 Content-Length: ... 1883 --boundary1 1885 Content-Type: application/sdp 1887 ...SDP goes here 1888 --boundary1-- 1890 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1891 Content-ID: <0123456789@atlanta.example.com> 1892 Content-Disposition: by-reference;handling=optional 1893 1895 1898 d4b3072df09876543@[93.184.216.119] 1899 1900 laptop 1901 00-0d-4b-30-72-df 1903 1905 --boundary1-- 1907 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1908 Content-ID: <1234567890@atlanta.example.com> 1909 Content-Disposition: by-reference;handling=optional 1910 1911 1914 d4b3072df09876543@[93.184.216.119] 1915 1916 Hannes Tschofenig 1917 1918 Other 1919 tel:+1-555-555-0123 1920 EN 1921 1923 1924 1925 Hannes Tschofenig 1926 1927 Hannes 1928 Tschofenig 1929 1930 1931 Dipl. Ing. 1932 1933 --0203 1934 1935 20090808T1430-0500 1937 1938 M 1939 1940 1 1941 1942 de 1943 1944 1945 2 1946 1947 en 1948 1949 1950 1951 work 1952 1956 1957 1958 1959 Linnoitustie 6 1960 Espoo 1961 Uusimaa 1962 02600 1963 Finland 1964 1965 1966 1967 1968 work 1969 voice 1970 1971 1972 tel:+358 50 4871445 1973 1974 1975 work 1976 1977 hannes.tschofenig@nsn.com 1978 1979 1980 work 1981 1982 geo:60.210796,24.812924 1983 1984 1985 1986 home 1987 1988 https://www.example.com/key.asc 1989 1990 1991 Finland/Helsinki 1992 1993 home 1994 1995 http://example.com/hannes.tschofenig 1996 1997 1998 1999 2000 2001 2003 --boundary1-- 2005 Content-Type: application/EmergencyCallData.ServiceInfo+xml 2006 Content-ID: 2007 Content-Disposition: by-reference;handling=optional 2008 2009 2012 string0987654321@example.org 2013 2014 Residence 2015 VOIP 2016 Unknown 2017 2019 --boundary1-- 2021 Content-Type: application/EmergencyCallData.ProviderInfo+xml 2022 Content-ID: 2023 Content-Disposition: by-reference;handling=optional 2024 2025 2028 string0987654321@example.org 2029 2030 Example VoIP Provider 2031 2032 urn:nena:companyid:ID123 2033 NENA 2034 Service Provider 2035 sip:voip-provider@example.com 2036 EN 2037 2039 2040 2041 John Doe 2042 2043 John 2044 Doe 2045 2046 2047 2048 2049 --0203 2050 2051 20090808T1430-0500 2052 2053 M 2054 2055 1 2056 2057 en 2058 2059 2060 work 2061 2062 Example VoIP Provider 2063 2064 2065 2066 work 2067 2070 2071 2072 2073 Downing Street 10 2074 London 2075 2076 SW1A 2AA 2077 UK 2078 2079 2080 2081 2082 work 2083 voice 2084 2085 2086 sips:john.doe@example.com 2087 2088 2089 work 2090 2091 john.doe@example.com 2092 2093 2094 work 2095 2096 geo:51.503396, 0.127640 2097 2098 Europe/London 2099 2100 home 2101 2102 http://www.example.com/john.doe 2103 2104 2105 2106 2107 2109 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2111 Finally, the PSAP requests location information from the access 2112 network provider. The response is shown in Figure 14. Along with 2113 the location information, additional data is provided in the 2114 element of the PIDF-LO. This request and response is 2115 step #4. 2117 2118 2123 2124 2125 2126 2128 AU 2129 NSW 2130 Wollongong 2131 North Wollongong 2132 Flinders 2133 Street 2134 Campbell Street 2135 Gilligan's Island 2136 Corner 2137 Video Rental Store 2138 2500 2139 Westerns and Classics 2140 store 2141 Private Box 15 2142 2143 2144 2145 true 2146 2147 2013-12-10T20:00:00Z 2148 2149 2150 802.11 2152 2155 2159 2160 2163 88QV4FpfZ976T@example.com 2164 2165 University of Example 2166 2167 urn:nena:companyid:uoi 2168 NENA 2169 Other 2170 tel:+1-555-824-5222 2171 EN 2172 2174 2176 88QV4FpfZ976T@example.com 2177 2178 This is an example text. 2179 2181 2182 2183 2184 mac:00-0d-4b-30-72-df 2185 2013-07-09T20:57:29Z 2186 2187 2189 Figure 14: Access Network Provider returning PIDF-LO with Additional 2190 Data. 2192 7. XML Schemas 2194 This section defines the XML schemas of the five data blocks. 2195 Additionally, the provided-by schema is specified. 2197 7.1. EmergencyCallData.ProviderInfo XML Schema 2199 2200 2210 2213 2215 2216 2217 2218 2219 2221 2225 2226 2227 2228 2229 2230 2232 2233 2234 2237 2240 2243 2246 2249 2252 2255 2259 2262 2266 2268 2269 2271 2273 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2275 7.2. EmergencyCallData.ServiceInfo XML Schema 2277 2278 2287 2290 2293 2294 2295 2298 2301 2305 2308 2310 2311 2313 2315 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2317 7.3. EmergencyCallData.DeviceInfo XML Schema 2319 2320 2329 2332 2335 2336 2337 2340 2343 2346 2349 2351 2352 2353 2354 2357 2358 2359 2360 2362 2365 2368 2370 2371 2373 2375 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2377 7.4. EmergencyCallData.SubscriberInfo XML Schema 2378 2379 2390 2393 2395 2398 2399 2400 2401 2404 2408 2410 2411 2413 2414 2416 2418 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2420 7.5. EmergencyCallData.Comment XML Schema 2421 2422 2431 2434 2437 2438 2439 2442 2446 2448 2449 2451 2452 2453 2454 2455 2456 2457 2459 2461 Figure 19: EmergencyCallData.Comment XML Schema. 2463 7.6. provided-by XML Schema 2465 This section defines the provided-by schema. 2467 2468 2483 2485 2487 2489 2491 2494 2496 2497 2498 2501 2505 2509 2512 2514 2515 2517 2518 2519 2520 2521 2523 2524 2526 2528 2529 2530 2532 2534 2535 2536 2539 2542 2545 2548 2552 2555 2556 2558 2560 Figure 20: provided-by XML Schema. 2562 8. Security Considerations 2564 The data structures described in this document contain information 2565 usually considered private. When information is provided by value, 2566 entities that are a party to the SIP signaling (such as proxy servers 2567 and back-to-back user agents) will have access to it and need to 2568 protect it against inappropriate disclosure. An entity that is able 2569 to eavesdrop on the SIP signaling will also have access. Some media 2570 (such as in the clear Wi-Fi) is more vulnerable than others (such as 2571 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that 2572 protect against eavesdropping (such as Transport Layer Security 2573 (TLS)) SHOULD be preferentially used whenever feasible. When 2574 information is provided by reference, HTTPS is specified for 2575 dereferencing, and the provider of the information is REQUIRED to 2576 validate the credentials of the requester. While the creation of a 2577 public key infrastructure (PKI) that has global scope may be 2578 difficult, the alternatives to creating devices and services that can 2579 provide critical information securely are more daunting. The 2580 provider of the information MAY enforce any policy it wishes to use, 2581 but PSAPs and responder agencies SHOULD deploy a PKI so that 2582 providers of additional data can check the certificate of the client 2583 and decide the appropriate policy to enforce based on that 2584 certificate. 2586 Ideally, the PSAP and emergency responders will be given credentials 2587 signed by an authority trusted by the data provider. In most 2588 circumstances, nationally recognized credentials would be sufficient, 2589 and if the emergency services arranges a PKI, data providers could be 2590 provisioned with the root CA public key for a given nation. Some 2591 nations are developing a PKI for this, and related, purposes. Since 2592 calls could be made from devices where the device and/or the service 2593 provider(s) are not local to the emergency services authorities, 2594 globally recognized credentials are useful. This might be 2595 accomplished by extending the notion of the "forest guide" described 2596 in [RFC5582] to allow the forest guide to provide the credential of 2597 the PKI root for areas for which it has coverage information, but 2598 standards for such a mechanism are not yet available. In its 2599 absence, the data provider will need to obtain by out of band means 2600 the root CA credentials for any areas to which it is willing to 2601 provide additional data. With the credential of the root CA for a 2602 national emergency services PKI, the data provider server can 2603 validate the credentials of an entity requesting additional data by 2604 reference. 2606 The data provider also needs a credential that can be verified by the 2607 emergency services to know that it is receiving data from an 2608 authorized server. The emergency services authorities could provide 2609 credentials, distinguishable from credentials provided to emergency 2610 responders and PSAPs, which could be used to validate data providers. 2611 Such credentials would have to be acceptable to any PSAP or responder 2612 that could receive a call with additional data supplied by that 2613 provider. This would be extensible to global credential validation 2614 using the forest guide as mentioned above. In the absence of such 2615 credentials, the emergency services authorities could maintain a list 2616 of local data providers' credentials as provided to them out of band. 2617 At a minimum, the emergency services authorities could obtain a 2618 credential from the DNS entry of the domain in the Additional Data 2619 URI to at least validate that the server is known to the domain 2620 providing the URI. 2622 Data provided by devices by reference have similar credential 2623 validation issues as for service providers, and the solutions are the 2624 same. 2626 Much of the information supplied by service providers and devices is 2627 private and confidential; service providers and devices generally go 2628 to lengths to protect this information; disclosing it in the context 2629 of an emergency call is a trade-off to protect the greater interest 2630 of the customer in an emergency. 2632 Neither service providers nor devices will supply private information 2633 unless the call is recognized as an emergency call. In cellular 2634 telephony systems (such as those using 3GPP IMS), there are different 2635 procedures for an originating device to place an emergency versus a 2636 normal call. If a call that is really an emergency call is initiated 2637 as a normal call and the cellular service provider recognizes this, 2638 3GPP IMS permits the service provider to either accept the call 2639 anyway or reject it with a specific code that instructs the device to 2640 retry the call as an emergency call. Service providers SHOULD choose 2641 the latter, because otherwise the device will not have included the 2642 information specified in this document (since the device didn't 2643 recognize the call as being an emergency call). 2645 9. Privacy Considerations 2647 This document enables functionality for conveying additional 2648 information about the caller and the caller's device and service to 2649 the callee. Some of this information is personal data and therefore 2650 privacy concerns arise. An explicit privacy indicator for 2651 information directly relating to the caller's identity is defined and 2652 use is mandatory. However, observance of this request for privacy 2653 and what information it relates to is determined by the destination 2654 jurisdiction. 2656 There are a number of privacy concerns with non-emergency real-time 2657 communication services that are also applicable to emergency calling. 2659 Data protection regulation world-wide has, however, decided to create 2660 exceptions for emergency services since the drawbacks of disclosing 2661 personal data are outweighed by the benefit for the emergency caller. 2662 Hence, the data protection rights of individuals are commonly waived 2663 for emergency situations. There are, however, still various 2664 countries that offer some degree of anonymity for the caller towards 2665 PSAP call takers. 2667 The functionality defined in this document, however, far exceeds the 2668 amount of information sharing found in the legacy POTS system. For 2669 this reason there are additional privacy threats to consider, which 2670 are described in more detail in [RFC6973]. 2672 Stored Data Compromise: There is an increased risk of stored data 2673 compromise since additional data is collected and stored in 2674 databases. Without adequate measures to secure stored data from 2675 unauthorized or inappropriate access at access network providers, 2676 service providers, end devices, as well as PSAPs, individuals are 2677 exposed to potential financial, reputational, or physical harm. 2679 Misattribution: If the personal data collected and conveyed is 2680 incorrect or inaccurate then this may lead to misattribution. 2681 Misattribution occurs when data or communications related to one 2682 individual are attributed to another. 2684 Identification: By the nature of the additional data and its 2685 capability to provide much richer information about the caller, 2686 the call, and the location, the calling party is identified in a 2687 much better way. Some users may feel uncomfortable with this 2688 degree of information sharing even in emergency services 2689 situations. 2691 Secondary Use: There is a risk of secondary use, which is the use of 2692 collected information about an individual without the individual's 2693 consent for a purpose different from that for which the 2694 information was collected. The stated purpose of the additional 2695 data is for emergency services purposes but theoretically the same 2696 information could be used for any other call as well. 2697 Additionally, parties involved in the emergency call may retain 2698 the obtained information and may re-use it for other, non- 2699 emergency services purposes. 2701 Disclosure: When the data defined in this document is not properly 2702 protected (while in transit with traditional communication 2703 security techniques, and while stored using access control 2704 mechanisms) there is the risk of disclosure, which is the 2705 revelation of private information about an individual. 2707 To mitigate these privacy risks the following countermeasures can be 2708 taken: 2710 In regions where callers can elect to suppress certain personally 2711 identifying information, network or PSAP functionality can inspect 2712 privacy flags within the SIP headers to determine what information 2713 may be passed, stored, or displayed to comply with local policy or 2714 law. RFC 3325 [RFC3325] defines the "id" priv-value token. The 2715 presence of this privacy type in a Privacy header field indicates 2716 that the user would like the network asserted identity to be kept 2717 private with respect to SIP entities outside the trust domain with 2718 which the user authenticated, including the PSAP. 2720 This document defines various data structures that contain privacy- 2721 sensitive data. For example, identifiers for the device (e.g., 2722 serial number, MAC address) or account/SIM (e.g., IMSI), contact 2723 information for the user, location of the caller. Local regulations 2724 may govern what data must be provided in emergency calls, but in 2725 general, the emergency call system is aided by the information 2726 described in this document. There is a tradeoff between the privacy 2727 considerations and the utility of the data. For protection, this 2728 specification requires all retrieval of data passed by reference to 2729 be protected against eavesdropping and alteration via communication 2730 security techniques (namely TLS). Furthermore, security safeguards 2731 are required to prevent unauthorized access to stored data. Various 2732 security incidents over at least the past few decades have shown that 2733 data breaches are not uncommon and are often caused by lack of proper 2734 access control frameworks, software bugs (such as buffer overflows), 2735 or missing input parsing (such as SQL injection attacks). The risks 2736 of data breaches is increased with the obligation for emergency 2737 services to retain emergency call related data for extended periods 2738 (e.g., several years are the norm). 2740 Finally, it is also worth highlighting the nature of the SIP 2741 communication architecture, which introduces additional complications 2742 for privacy. Some forms of data can be sent by value in the SIP 2743 signaling or by reference (a URL in the SIP signaling). When data is 2744 sent by value, all intermediaries have access to the data. As such, 2745 these intermediaries may also introduce additional privacy risk. 2746 Therefore, in situations where the conveyed information is privacy- 2747 sensitive and intermediaries are involved, transmitting by reference 2748 might be appropriate, assuming the source of the data can operate a 2749 sufficient dereferencing infrastructure and that proper access 2750 control policies are available for distinguishing the different 2751 entities dereferencing the reference. Without access control 2752 policies any party in possession of the reference is able to resolve 2753 the reference and to obtain the data, including intermediaries. 2755 10. IANA Considerations 2757 10.1. Registry creation 2759 This document creates a new registry called 'Emergency Call 2760 Additional Data'. The following sub-registries are created for this 2761 registry. 2763 10.1.1. Provider ID Series Registry 2765 This document creates a new sub-registry called 'Additional Call Data 2766 Provider ID Series'. As defined in [RFC5226], this registry operates 2767 under "Expert Review" rules. The expert should determine that the 2768 entity requesting a new value is a legitimate issuer of service 2769 provider IDs suitable for use in Additional Call Data. 2771 Private entities issuing and using internally-generated IDs are 2772 encouraged to register and use a unique identifier. This guarantees 2773 that IDs issued and used by the entity are globally unique and 2774 distinguishable. 2776 The content of this registry includes: 2778 Name: The identifier which will be used in the 'ProviderIDSeries' 2779 element. 2781 Source: The full name of the organization issuing the identifiers. 2783 URL: A URL to the organization for further information. 2785 The initial set of values is listed in Figure 21. 2787 +-----------+--------------------------+----------------------+ 2788 | Name | Source | URL | 2789 +-----------+--------------------------+----------------------+ 2790 | NENA | National Emergency | http://www.nena.org | 2791 | | Number Association | | 2792 | EENA | European Emergency | http://www.eena.org | 2793 | | Number Association | | 2794 | domain | (The ID is a fully- | (not applicable) | 2795 | | qualified domain name) | | 2796 +-----------+--------------------------+----------------------+ 2798 Figure 21: Provider ID Series Registry. 2800 10.1.2. Service Environment Registry 2802 This document creates a new sub-registry called 'Additional Call 2803 Service Environment'. As defined in [RFC5226], this registry 2804 operates under "Expert Review" rules. The expert should determine 2805 that the entity requesting a new value is relevant for this service 2806 element, and that the new value is distinct from existing values, and 2807 its use is unambiguous. 2809 The content of this registry includes: 2811 Token: The value to be used in the element. 2813 Description: A short description of the value. 2815 The initial set of values is listed in Figure 22. 2817 +-----------+--------------------------+ 2818 | Token | Description | 2819 +-----------+--------------------------+ 2820 | Business | Business service | 2821 | Residence | Residential service | 2822 | unknown | Type of service unknown | 2823 | | (e.g., anonymous pre- | 2824 | | paid service) | 2825 +-----------+--------------------------+ 2827 Figure 22: Service Environment Registry. 2829 10.1.3. Service Type Registry 2831 This document creates a new sub-registry called 'Additional Call 2832 Service Type'. As defined in [RFC5226], this registry operates under 2833 "Expert Review" rules. The expert should determine that the entity 2834 requesting a new value is relevant for this service element and that 2835 the requested value is clearly distinct from other values so that 2836 there is no ambiguity as to when the value is to be used or which 2837 value is to be used. 2839 The content of this registry includes: 2841 Name: The value to be used in the element. 2843 Description: A short description of the value. 2845 The initial set of values is listed in Figure 3. 2847 10.1.4. Service Mobility Registry 2849 This document creates a new sub-registry called 'Additional Call 2850 Service Mobility'. As defined in [RFC5226], this registry operates 2851 under "Expert Review" rules. The expert should determine that the 2852 entity requesting a new value is relevant for this service element 2853 and that the requested value is clearly distinct from other values so 2854 that there is no ambiguity as to when the value is to be used or 2855 which value is to be used. 2857 The content of this registry includes: 2859 Token: The value used in the element. 2861 Description: A short description of the value. 2863 The initial set of values is listed in Figure 23. 2865 +-----------+----------------------------+ 2866 | Token | Description | 2867 +-----------+----------------------------+ 2868 | Mobile | The device is able to | 2869 | | move at any time | 2870 | Fixed | The device is not expected | 2871 | | to move unless the service | 2872 | | is relocated | 2873 | Nomadic | The device is not expected | 2874 | | to change its point of | 2875 | | attachment while on a call | 2876 | Unknown | No information is known | 2877 | | about the service mobility | 2878 | | environment for the device | 2879 +-----------+----------------------------+ 2881 Figure 23: Service Environment Registry. 2883 10.1.5. Service Provider Type Registry 2885 This document creates a new sub-registry called 'Service Provider 2886 Type'. As defined in [RFC5226], this registry operates under "Expert 2887 Review". The expert should determine that the proposed new value is 2888 distinct from existing values and appropriate for use in the 2889 TypeOfServicerProvider element 2891 The content of this registry includes: 2893 Tokenproviderid: The value used in the 'TypeOfProvider' element. 2895 Description: A short description of the type of service provider. 2897 The initial set of values is defined in Figure 1. 2899 10.1.6. Service Delivered Registry 2901 This document creates a new sub-registry called 'Service Delivered'. 2902 As defined in [RFC5226], this registry operates under "Expert Review" 2903 rules. The expert should consider whether the proposed service is 2904 unique from existing services and the definition of the service will 2905 be clear to implementors and PSAPs/responders. 2907 The content of this registry includes: 2909 Name: The value used in the 'ServiceType' element. 2911 Description: Short description identifying the nature of the 2912 service. 2914 The initial set of values are defined in Figure 3. 2916 10.1.7. Device Classification Registry 2918 This document creates a new sub-registry called 'Device 2919 Classification'. As defined in [RFC5226], this registry operates 2920 under "Expert Review" rules. The expert should consider whether the 2921 proposed class is unique from existing classes and the definition of 2922 the class will be clear to implementors and PSAPs/responders. 2924 The content of this registry includes: 2926 Token: Value used in the 'DeviceClassification' element. 2928 Description: Short description identifying the device type. 2930 The initial set of values are defined in Figure 5. 2932 10.1.8. Device ID Type Type Registry 2934 This document creates a new sub-registry called 'Additional Call Data 2935 Device ID Type'. As defined in [RFC5226], this registry operates 2936 under "Expert Review" rules. The expert should ascertain that the 2937 proposed type is well understood, and provides the information useful 2938 to PSAPs and responders to uniquely identify a device. 2940 The content of this registry includes: 2942 Token: The value to be placed in the 'TypeOfDeviceID' element. 2944 Description: Short description identifying the type of the device 2945 ID. 2947 The initial set of values are defined in Figure 6. 2949 10.1.9. Device/Service Data Type Registry 2951 This document creates a new sub-registry called 'Device/Service Data 2952 Type Registry'. As defined in [RFC5226], this registry operates 2953 under "Expert Review" and "Specification Required" rules. The expert 2954 should ascertain that the proposed type is well understood, and 2955 provides information useful to PSAPs and responders. The 2956 specification must contain a complete description of the data, and a 2957 precise format specification suitable to allow interoperable 2958 implementations. 2960 The content of this registry includes: 2962 Token: The value to be placed in the element. 2964 Description: Short description identifying the the data. 2966 Specification: Citation for the specification of the data. 2968 The initial set of values are listed in Figure 24. 2970 +----------+----------------------------------------+---------------+ 2971 | Token | Description | Specification | 2972 +----------+----------------------------------------+---------------+ 2973 | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006| 2974 +----------+----------------------------------------+---------------+ 2976 Figure 24: Device/Service Data Type Registry. 2978 10.1.10. Emergency Call Data Types Registry 2980 This document creates a new sub-registry called 'Emergency Call Data 2981 Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. 2982 As defined in [RFC5226], this registry operates under "Expert Review" 2983 and "Specification Required" rules. The expert is responsible for 2984 verifying that the document contains a complete and clear 2985 specification and the proposed functionality does not obviously 2986 duplicate existing functionality. 2988 The content of this registry includes: 2990 Token: The root of the data's MIME subtype (not including the 2991 'EmergencyCallData' prefix and any suffix such as '+xml') 2993 Reference: The document that describes the data object 2995 Note that the values from this registry are part of the 2996 'EmergencyCallData' compound value; when used as a value of the 2997 'purpose' parameter of the Call-Info header, the values listed in 2998 this registry are prefixed by 'EmergencyCallData.' per the the 2999 'EmergencyCallData' registation Section 10.2. 3001 The initial set of values are listed in Figure 25. 3003 +----------------+------------+ 3004 | Token | Reference | 3005 +----------------+------------+ 3006 | ProviderInfo | [This RFC] | 3007 | ServiceInfo | [This RFC] | 3008 | DeviceInfo | [This RFC] | 3009 | SubscriberInfo | [This RFC] | 3010 | Comment | [This RFC] | 3011 +----------------+------------+ 3013 Figure 25: Additional Data Blocks Registry. 3015 10.2. 'EmergencyCallData' Purpose Parameter Value 3017 This document defines the 'EmergencyCallData' value for the "purpose" 3018 parameter of the Call-Info header field. The Call-Info header and 3019 the corresponding registry for the 'purpose' parameter was 3020 established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' 3021 is a compound value; when used as a value of the 'purpose' parameter 3022 of the Call-Info header, 'EmergencyCallData' is immediately followed 3023 by a dot ('.') and a value from the 'Emergency Call Data Types' 3024 registry Section 10.1.10. 3026 Header Parameter New 3027 Field Name Value Reference 3028 ---------- --------- ----------------- --------- 3029 Call-Info purpose EmergencyCallData [This RFC] 3031 10.3. URN Sub-Namespace Registration for provided-by Registry Entry 3033 This section registers the namespace specified in Section 10.5.1 in 3034 the provided-by registry established by RFC 4119, for usage within 3035 the element of a PIDF-LO. 3037 The schema for the provided-by element used by this document is 3038 specified in Section 7.6. 3040 10.4. MIME Registrations 3042 10.4.1. MIME Content-type Registration for 'application/ 3043 EmergencyCallData.ProviderInfo+xml' 3045 This specification requests the registration of a new MIME type 3046 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3047 RFC 7303 [RFC7303]. 3049 MIME media type name: application 3051 MIME subtype name: EmergencyCallData.ProviderInfo+xml 3053 Mandatory parameters: none 3055 Optional parameters: charset (indicates the character encoding of 3056 the contents) 3058 Encoding considerations: Uses XML, which can contain 8-bit 3059 characters, depending on the character encoding. See Section 3.2 3060 of RFC 7303 [RFC7303]. 3062 Security considerations: This content type is designed to carry 3063 the data provider information, which is a sub-category of 3064 additional data about an emergency call. Since this data may 3065 contain personal information, appropriate precautions might be 3066 needed to limit unauthorized access, inappropriate disclosure, and 3067 eavesdropping of personal information. Please refer to Section 8 3068 and Section 9 for more information. 3070 Interoperability considerations: None 3072 Published specification: [TBD: This specification] 3074 Applications which use this media type: Emergency Services 3076 Additional information: 3078 Magic Number: None 3080 File Extension: .xml 3082 Macintosh file type code: 'TEXT' 3084 Person and email address for further information: Hannes 3085 Tschofenig, Hannes.Tschofenig@gmx.net 3087 Intended usage: LIMITED USE 3089 Author: This specification is a work item of the IETF ECRIT 3090 working group, with mailing list address . 3092 Change controller: The IESG 3094 10.4.2. MIME Content-type Registration for 'application/ 3095 EmergencyCallData.ServiceInfo+xml' 3097 This specification requests the registration of a new MIME type 3098 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3099 RFC 7303 [RFC7303]. 3101 MIME media type name: application 3103 MIME subtype name: EmergencyCallData.ServiceInfo+xml 3105 Mandatory parameters: none 3107 Optional parameters: charset (indicates the character encoding of 3108 the contents) 3110 Encoding considerations: Uses XML, which can contain 8-bit 3111 characters, depending on the character encoding. See Section 3.2 3112 of RFC 7303 [RFC7303]. 3114 Security considerations: This content type is designed to carry 3115 the service information, which is a sub-category of additional 3116 data about an emergency call. Since this data may contain 3117 personal information, appropriate precautions may be needed to 3118 limit unauthorized access, inappropriate disclosure, and 3119 eavesdropping of personal information. Please refer to Section 8 3120 and Section 9 for more information. 3122 Interoperability considerations: None 3124 Published specification: [TBD: This specification] 3126 Applications which use this media type: Emergency Services 3128 Additional information: 3130 Magic Number: None 3131 File Extension: .xml 3133 Macintosh file type code: 'TEXT' 3135 Person and email address for further information: Hannes 3136 Tschofenig, Hannes.Tschofenig@gmx.net 3138 Intended usage: LIMITED USE 3140 Author: This specification is a work item of the IETF ECRIT 3141 working group, with mailing list address . 3143 Change controller: The IESG 3145 10.4.3. MIME Content-type Registration for 'application/ 3146 EmergencyCallData.DeviceInfo+xml' 3148 This specification requests the registration of a new MIME type 3149 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3150 RFC 7303 [RFC7303]. 3152 MIME media type name: application 3154 MIME subtype name: EmergencyCallData.DeviceInfo+xml 3156 Mandatory parameters: none 3158 Optional parameters: charset (indicates the character encoding of 3159 the contents) 3161 Encoding considerations: Uses XML, which can contain 8-bit 3162 characters, depending on the character encoding. See Section 3.2 3163 of RFC 7303 [RFC7303]. 3165 Security considerations: This content type is designed to carry 3166 device information, which is a sub-category of additional data 3167 about an emergency call. Since this data contains personal 3168 information, appropriate precautions need to be taken to limit 3169 unauthorized access, inappropriate disclosure to third parties, 3170 and eavesdropping of this information. Please refer to Section 8 3171 and Section 9 for more information. 3173 Interoperability considerations: None 3175 Published specification: [TBD: This specification] 3177 Applications which use this media type: Emergency Services 3178 Additional information: 3180 Magic Number: None 3182 File Extension: .xml 3184 Macintosh file type code: 'TEXT' 3186 Person and email address for further information: Hannes 3187 Tschofenig, Hannes.Tschofenig@gmx.net 3189 Intended usage: LIMITED USE 3191 Author: This specification is a work item of the IETF ECRIT 3192 working group, with mailing list address . 3194 Change controller: The IESG 3196 10.4.4. MIME Content-type Registration for 'application/ 3197 EmergencyCallData.SubscriberInfo+xml' 3199 This specification requests the registration of a new MIME type 3200 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3201 RFC 7303 [RFC7303]. 3203 MIME media type name: application 3205 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 3207 Mandatory parameters: none 3209 Optional parameters: charset (indicates the character encoding of 3210 the contents) 3212 Encoding considerations: Uses XML, which can contain 8-bit 3213 characters, depending on the character encoding. See Section 3.2 3214 of RFC 7303 [RFC7303]. 3216 Security considerations: This content type is designed to carry 3217 owner/subscriber information, which is a sub-category of 3218 additional data about an emergency call. Since this data contains 3219 personal information, appropriate precautions need to be taken to 3220 limit unauthorized access, inappropriate disclosure to third 3221 parties, and eavesdropping of this information. Please refer to 3222 Section 8 and Section 9 for more information. 3224 Interoperability considerations: None 3225 Published specification: [TBD: This specification] 3227 Applications which use this media type: Emergency Services 3229 Additional information: 3231 Magic Number: None 3233 File Extension: .xml 3235 Macintosh file type code: 'TEXT' 3237 Person and email address for further information: Hannes 3238 Tschofenig, Hannes.Tschofenig@gmx.net 3240 Intended usage: LIMITED USE 3242 Author: This specification is a work item of the IETF ECRIT 3243 working group, with mailing list address . 3245 Change controller: The IESG 3247 10.4.5. MIME Content-type Registration for 'application/ 3248 EmergencyCallData.Comment+xml' 3250 This specification requests the registration of a new MIME type 3251 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3252 RFC 7303 [RFC7303]. 3254 MIME media type name: application 3256 MIME subtype name: EmergencyCallData.Comment+xml 3258 Mandatory parameters: none 3260 Optional parameters: charset (indicates the character encoding of 3261 the contents) 3263 Encoding considerations: Uses XML, which can contain 8-bit 3264 characters, depending on the character encoding. See Section 3.2 3265 of RFC 7303 [RFC7303]. 3267 Security considerations: This content type is designed to carry a 3268 comment, which is a sub-category of additional data about an 3269 emergency call. This data may contain personal information. 3270 Appropriate precautions may be needed to limit unauthorized 3271 access, inappropriate disclosure to third parties, and 3272 eavesdropping of this information. Please refer to Section 8 and 3273 Section 9 for more information. 3275 Interoperability considerations: None 3277 Published specification: [TBD: This specification] 3279 Applications which use this media type: Emergency Services 3281 Additional information: 3283 Magic Number: None 3285 File Extension: .xml 3287 Macintosh file type code: 'TEXT' 3289 Person and email address for further information: Hannes 3290 Tschofenig, Hannes.Tschofenig@gmx.net 3292 Intended usage: LIMITED USE 3294 Author: This specification is a work item of the IETF ECRIT 3295 working group, with mailing list address . 3297 Change controller: The IESG 3299 10.5. URN Sub-Namespace Registration 3301 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3303 This section registers a new XML namespace, as per the guidelines in 3304 RFC 3688 [RFC3688]. 3306 URI: urn:ietf:params:xml:ns:EmergencyCallData 3308 Registrant Contact: IETF, ECRIT working group, , as 3309 delegated by the IESG . 3311 XML: 3313 BEGIN 3314 3315 3317 3318 3319 3321 Namespace for Additional Emergency Call Data 3322 3323 3324

Namespace for Additional Data related to an Emergency Call 3325

3326

See [TBD: This document].

3327 3328 3329 END 3331 10.5.2. Registration for 3332 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3334 This section registers a new XML namespace, as per the guidelines in 3335 RFC 3688 [RFC3688]. 3337 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3339 Registrant Contact: IETF, ECRIT working group, , as 3340 delegated by the IESG . 3342 XML: 3344 BEGIN 3345 3346 3348 3349 3350 3352 Namespace for Additional Emergency Call Data: 3353 Data Provider Information 3354 3355 3356

Namespace for Additional Data related to an Emergency Call 3357

3358

Data Provider Information

3359

See [TBD: This document].

3360 3361 3362 END 3364 10.5.3. Registration for 3365 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3367 This section registers a new XML namespace, as per the guidelines in 3368 RFC 3688 [RFC3688]. 3370 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3372 Registrant Contact: IETF, ECRIT working group, , as 3373 delegated by the IESG . 3375 XML: 3377 BEGIN 3378 3379 3381 3382 3383 3385 Namespace for Additional Emergency Call Data: 3386 Service Information 3387 3388 3389

Namespace for Additional Data related to an Emergency Call 3390

3391

Service Information

3392

See [TBD: This document].

3393 3394 3395 END 3397 10.5.4. Registration for 3398 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3400 This section registers a new XML namespace, as per the guidelines in 3401 RFC 3688 [RFC3688]. 3403 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3405 Registrant Contact: IETF, ECRIT working group, , as 3406 delegated by the IESG . 3408 XML: 3410 BEGIN 3411 3412 3414 3415 3416 3418 Namespace for Additional Emergency Call Data: 3419 Device Information 3420 3421 3422

Namespace for Additional Data related to an Emergency Call 3423

3424

Device Information

3425

See [TBD: This document].

3426 3427 3428 END 3430 10.5.5. Registration for 3431 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3433 This section registers a new XML namespace, as per the guidelines in 3434 RFC 3688 [RFC3688]. 3436 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3438 Registrant Contact: IETF, ECRIT working group, , as 3439 delegated by the IESG . 3441 XML: 3443 BEGIN 3444 3445 3447 3448 3449 3451 Namespace for Additional Emergency Call Data: 3452 Owner/Subscriber Information 3453 3454 3455

Namespace for Additional Data related to an Emergency Call 3456

3457

Owner/Subscriber Information

3458

See [TBD: This document].

3459 3460 3461 END 3463 10.5.6. Registration for 3464 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3466 This section registers a new XML namespace, as per the guidelines in 3467 RFC 3688 [RFC3688]. 3469 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3471 Registrant Contact: IETF, ECRIT working group, , as 3472 delegated by the IESG . 3474 XML: 3476 BEGIN 3477 3478 3480 3481 3482 3484 Namespace for Additional Emergency Call Data:Comment 3485 3486 3487 3488

Namespace for Additional Data related to an Emergency Call 3489

3490

Comment

3491

See [TBD: This document].

3492 3493 3494 END 3496 10.6. Schema Registrations 3498 This specification registers five schemas, as per the guidelines in 3499 RFC 3688 [RFC3688]. 3501 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3503 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3504 delegated by the IESG (iesg@ietf.org). 3506 XML: The XML schema can be found in Figure 15. 3508 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3510 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3511 delegated by the IESG (iesg@ietf.org). 3513 XML: The XML schema can be found in Figure 16. 3515 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3517 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3518 delegated by the IESG (iesg@ietf.org). 3520 XML: The XML schema can be found in Figure 17. 3522 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3523 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3524 delegated by the IESG (iesg@ietf.org). 3526 XML: The XML schema can be found in Section 7.4. 3528 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3530 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3531 delegated by the IESG (iesg@ietf.org). 3533 XML: The XML schema can be found in Section 7.5. 3535 10.7. VCard Parameter Value Registration 3537 This document registers a new value in the vCARD Parameter Values 3538 registry as defined by [RFC6350] with the following template: 3540 Value: main 3542 Purpose: The main telephone number, typically of an enterprise, as 3543 opposed to a direct dial number of an individual employee 3545 Conformance: This value can be used with the "TYPE" parameter 3546 applied on the "TEL" property. 3548 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3549 00 3551 11. Acknowledgments 3553 This work was originally started in NENA and has benefitted from a 3554 large number of participants in NENA standardization efforts, 3555 originally in the Long Term Definition Working Group, the Data 3556 Technical Committee and most recently the Additional Data working 3557 group. The authors are grateful for the initial work and extended 3558 comments provided by many NENA participants, including Delaine 3559 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3560 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3561 and Robert (Bob) Sherry. 3563 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3564 Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris 3565 Santer, and Archie Cobbs for their review comments. Guy Caron 3566 deserves special mention for his detailed and extensive review 3567 comments. 3569 12. References 3571 12.1. Normative References 3573 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3574 Requirement Levels", BCP 14, RFC 2119, March 1997. 3576 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3577 Locators", RFC 2392, August 1998. 3579 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3580 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3581 and QSIG Objects", RFC 3204, December 2001. 3583 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3584 A., Peterson, J., Sparks, R., Handley, M., and E. 3585 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3586 June 2002. 3588 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3589 Extensions to the Session Initiation Protocol (SIP) for 3590 Asserted Identity within Trusted Networks", RFC 3325, 3591 November 2002. 3593 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3594 Extensions (MIME) Parameter", RFC 3459, January 2003. 3596 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3597 January 2004. 3599 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3600 Format", RFC 4119, December 2005. 3602 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3603 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3604 May 2008. 3606 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 3607 October 2008. 3609 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3610 Initiation Protocol (SIP)", RFC 5621, September 2009. 3612 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3613 August 2011. 3615 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3616 6351, August 2011. 3618 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3619 Specifications and Registration Procedures", BCP 13, RFC 3620 6838, January 2013. 3622 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 3623 July 2014. 3625 12.2. Informational References 3627 [I-D.gellens-slim-negotiating-human-language] 3628 Gellens, R., "Negotiating Human Language in Real-Time 3629 Communications", draft-gellens-slim-negotiating-human- 3630 language (work in progress), October 2014. 3632 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3633 "Indicating User Agent Capabilities in the Session 3634 Initiation Protocol (SIP)", RFC 3840, August 2004. 3636 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3637 3966, December 2004. 3639 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3640 Emergency Context Resolution with Internet Technologies", 3641 RFC 5012, January 2008. 3643 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3644 Format for Presence Information Data Format Location 3645 Object (PIDF-LO)", RFC 5139, February 2008. 3647 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3648 Presence Information Data Format Location Object (PIDF-LO) 3649 Usage Clarification, Considerations, and Recommendations", 3650 RFC 5491, March 2009. 3652 [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and 3653 Framework", RFC 5582, September 2009. 3655 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3656 Thomson, "Dynamic Extensions to the Presence Information 3657 Data Format Location Object (PIDF-LO)", RFC 5962, 3658 September 2010. 3660 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3661 5985, September 2010. 3663 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3664 "Framework for Emergency Calling Using Internet 3665 Multimedia", RFC 6443, December 2011. 3667 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3668 R. George, "Specifying Civic Address Extensions in the 3669 Presence Information Data Format Location Object (PIDF- 3670 LO)", RFC 6848, January 2013. 3672 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3673 Communications Services in Support of Emergency Calling", 3674 BCP 181, RFC 6881, March 2013. 3676 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3677 Morris, J., Hansen, M., and R. Smith, "Privacy 3678 Considerations for Internet Protocols", RFC 6973, July 3679 2013. 3681 [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3682 Thomson, "Relative Location Representation", RFC 7035, 3683 October 2013. 3685 [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3686 Patel, "Public Safety Answering Point (PSAP) Callback", 3687 RFC 7090, April 2014. 3689 12.3. URIs 3691 [1] http://www.nena.org/?page=cid2014 3693 [2] http://www.nena.org/?page=CompanyID 3695 Appendix A. XML Schema for vCard/xCard 3697 This section contains the vCard/xCard XML schema version of the Relax 3698 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3699 XML schemas defined in this document. The schema in RFC 6351 3700 [RFC6351] is the normative source and this section is informative 3701 only. 3703 3704 3708 3714 3715 3716 vCard Format Specification 3717 3718 3719 3720 3721 3722 3723 3724 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3739 3740 3741 3743 3744 3745 3746 3747 3749 3750 3751 3753 3754 3755 3756 3757 3759 3760 3761 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3806 3807 3808 3809 3812 3813 3814 Section 5: Parameters 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4740 4741 4742 4743 4744 4745 4746 4748 4749 4750 4751 4752 4753 4754 4756 4757 4758 4760 4762 4763 4764 4766 4767 4768 4769 4771 Authors' Addresses 4773 Randall Gellens 4774 Qualcomm Technologies, Inc. 4775 5775 Morehouse Drive 4776 San Diego, CA 92121 4777 US 4779 Email: rg+ietf@qti.qualcomm.com 4781 Brian Rosen 4782 NeuStar 4783 470 Conrad Dr. 4784 Mars, PA 16046 4785 US 4787 Phone: +1 724 382 1051 4788 Email: br@brianrosen.net 4790 Hannes Tschofenig 4791 (no affiliation) 4793 Email: Hannes.Tschofenig@gmx.net 4794 URI: http://www.tschofenig.priv.at 4796 Roger Marshall 4797 TeleCommunication Systems, Inc. 4798 2401 Elliott Avenue 4799 Seattle, WA 98121 4800 US 4802 Phone: +1 206 792 2424 4803 Email: rmarshall@telecomsys.com 4804 URI: http://www.telecomsys.com 4806 James Winterbottom 4807 (no affiliation) 4808 AU 4810 Email: a.james.winterbottom@gmail.com