idnits 2.17.1 draft-ietf-ecrit-additional-data-29.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 19 instances of too long lines in the document, the longest one being 16 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 3056 has weird spacing: '...ll-Info pur...' -- The document date (March 8, 2015) is 3336 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 3725 -- Looks like a reference, but probably isn't: '2' on line 3727 == Missing Reference: 'This RFC' is mentioned on line 3056, but not defined ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-03) exists of draft-gellens-slim-negotiating-human-language-00 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: September 9, 2015 NeuStar 6 H. Tschofenig 8 R. Marshall 9 TeleCommunication Systems, Inc. 10 J. Winterbottom 11 March 8, 2015 13 Additional Data Related to an Emergency Call 14 draft-ietf-ecrit-additional-data-29.txt 16 Abstract 18 When an emergency call is sent to a Public Safety Answering Point 19 (PSAP), the device that sends it, as well as any application service 20 provider in the path of the call, or access network provider through 21 which the call originated may have information about the call, the 22 caller or the location which the PSAP may be able to use. This 23 document describes data structures and a mechanism to convey such 24 data to the PSAP. The mechanism uses a Uniform Resource Identifier 25 (URI), which may point to either an external resource or an object in 26 the body of the SIP message. The mechanism thus allows the data to 27 be passed by reference (when the URI points to an external resource) 28 or by value (when it points into the body of the message). This 29 follows the tradition of prior emergency services standardization 30 work where data can be conveyed by value within the call signaling 31 (i.e., in body of the SIP message) and also by reference. 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at http://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on September 9, 2015. 50 Copyright Notice 52 Copyright (c) 2015 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 99 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 26 100 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26 101 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26 102 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27 103 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27 104 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 30 105 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 30 106 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30 107 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30 108 5.1. Transmitting Blocks using the Call-Info Header . . . . . 32 109 5.2. Transmitting Blocks by Reference using the provided-by 110 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 111 5.3. Transmitting Blocks by Value using the provided-by 112 Element . . . . . . . . . . . . . . . . . . . . . . . . . 34 113 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 35 114 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36 115 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 48 116 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 48 117 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 50 118 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 51 119 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 53 120 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 54 121 7.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 55 122 8. Security Considerations . . . . . . . . . . . . . . . . . . . 58 123 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 59 124 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 125 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 62 126 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 62 127 10.1.2. Service Environment Registry . . . . . . . . . . . . 63 128 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 63 129 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 64 130 10.1.5. Service Provider Type Registry . . . . . . . . . . . 64 131 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 65 132 10.1.7. Device Classification Registry . . . . . . . . . . . 65 133 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 65 134 10.1.9. Device/Service Data Type Registry . . . . . . . . . 66 135 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 66 136 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 67 137 10.3. URN Sub-Namespace Registration for provided-by Registry 138 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 68 139 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 68 140 10.4.1. MIME Content-type Registration for 141 'application/EmergencyCallData.ProviderInfo+xml' . . 68 142 10.4.2. MIME Content-type Registration for 143 'application/EmergencyCallData.ServiceInfo+xml' . . 69 144 10.4.3. MIME Content-type Registration for 145 'application/EmergencyCallData.DeviceInfo+xml' . . . 70 146 10.4.4. MIME Content-type Registration for 147 'application/EmergencyCallData.SubscriberInfo+xml' . 71 148 10.4.5. MIME Content-type Registration for 149 'application/EmergencyCallData.Comment+xml' . . . . 72 150 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 73 151 10.5.1. Registration for 152 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 73 153 10.5.2. Registration for 154 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf 155 o . . . . . . . . . . . . . . . . . . . . . . . . . 74 156 10.5.3. Registration for 157 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 75 158 10.5.4. Registration for 159 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 76 160 10.5.5. Registration for 161 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI 162 nfo . . . . . . . . . . . . . . . . . . . . . . . . 77 163 10.5.6. Registration for 164 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 78 165 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 79 166 10.7. VCard Parameter Value Registration . . . . . . . . . . . 80 167 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 80 168 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 81 169 12.1. Normative References . . . . . . . . . . . . . . . . . . 81 170 12.2. Informational References . . . . . . . . . . . . . . . . 82 171 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 83 172 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 83 173 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 106 175 1. Introduction 177 When an IP-based emergency call is initiated, a rich set of data from 178 multiple data sources is conveyed to the Public Safety Answering 179 Point (PSAP). This data includes information about the calling party 180 identity, the multimedia capabilities of the device, the request for 181 emergency services, location information, and meta-data about the 182 sources of the data. The device, the access network provider, and 183 any service provider in the call path may have even more information 184 useful for a PSAP. This document extends the basic set of data 185 communicated with an IP-based emergency call, as described in 186 [RFC6443] and [RFC6881], in order to carry additional data which may 187 be useful to an entity or call taker handling the call. This data is 188 "additional" to the basic information found in the emergency call 189 signaling used. 191 In general, there are three categories of this additional data that 192 may be transmitted with an emergency call: 194 Data Associated with a Location: Primary location data is conveyed 195 in the Presence Information Data Format Location Object (PIDF-LO) 196 data structure as defined in RFC 4119 [RFC4119] and extended by 197 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 198 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 199 geodetic location information), and [RFC7035] (for relative 200 location). This primary location data identifies the location or 201 estimated location of the caller. However, there may exist 202 additional, secondary data which is specific to the location, such 203 as floor plans, tenant and building owner contact data, heating, 204 ventilation and air conditioning (HVAC) status, etc. Such 205 secondary location data is not included in the location data 206 structure but can be transmitted using the mechanisms defined in 207 this document. Although this document does not define any 208 structures for such data, future documents may do so following the 209 procedures defined here. 211 Data Associated with a Call: While some information is carried in 212 the call setup procedure itself (as part of the SIP headers as 213 well as in the body of the SIP message), there is additional data 214 known by the device making the call and/or a service provider 215 along the path of the call. This information may include the 216 service provider contact information, subscriber identity and 217 contact information, the type of service the service provider and 218 the access network provider offer, what type of device is being 219 used, etc. Some data is broadly applicable, while other data is 220 dependent on the type of device or service. For example, a 221 medical monitoring device may have sensor data. The data 222 structures defined in this document (Data Provider Information, 223 Device Information, and Owner/Subscriber Information) all fall 224 into the category of "Data Associated with a Call". 226 Data Associated with a Caller: This is personal data about a caller, 227 such as medical information and emergency contact data. Although 228 this document does not define any structures within this category, 229 future documents may do so following the procedures defined here. 231 While this document defines data structures only within the category 232 of Data Associated with a Call, by establishing the overall framework 233 of Additional Data, along with general mechanisms for transport of 234 such data, extension points and procedures for future extensions, it 235 minimizes the work needed to carry data in the other categories. 236 Other specifications may make use of the facilities provided here. 238 For interoperability, there needs to be a common way for the 239 information conveyed to a PSAP to be encoded and identified. 240 Identification allows emergency services authorities to know during 241 call processing which types of data are present and to determine if 242 they wish to access it. A common encoding allows the data to be 243 successfully accessed. 245 This document defines an extensible set of data structures, and 246 mechanisms to transmit this data either by value or by reference, 247 either in the Session Initiation Protocol (SIP) call signaling or in 248 the Presence Information Data Format Location Object (PIDF-LO). The 249 data structures are usable by other communication systems and 250 transports as well. The data structures are defined in Section 4, 251 and the transport mechanisms (using SIP and HTTPS) are defined in 252 Section 5. 254 Each data structure described in this document is encoded as a 255 "block" of information. Each block is an XML structure with an 256 associated Multipurpose Internet Mail Extensions (MIME) type for 257 identification within transport such as SIP and HTTPS. The set of 258 blocks is extensible. Registries are defined to identify the block 259 types that may be used and to allow blocks to be included in 260 emergency call signaling. 262 2. Terminology 264 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 265 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 266 document are to be interpreted as described in RFC 2119 [RFC2119]. 268 This document also uses terminology from [RFC5012]. We use the term 269 service provider to refer to an Application Service Provider (ASP). 270 A Voice Service Provider (VSP) is a special type of ASP. With the 271 term "Access Network Provider" we refer to the Internet Access 272 Provider (IAP) and the Internet Service Provider (ISP) without 273 further distinguishing these two entities, since the difference 274 between the two is not relevant for this document. Note that the 275 roles of ASP and access network provider may be provided by a single 276 company. An Emergency Services Provider is an entity directly 277 involved in providing emergency services. This includes PSAPs, 278 dispatch, police, fire, emergency medical, other responders, and 279 other similar agencies. 281 Within each data block definition (see Section 4), the values for the 282 "Use:" label are specified as one of the following: 284 'Required': means it MUST be present in the data structure. 286 'Conditional': means it MUST be present if the specified 287 condition(s) is met. It MAY be present if the condition(s) is not 288 met. 290 'Optional': means it MAY be present. 292 vCard is a data format for representing and exchanging a variety of 293 information about individuals and other entities. For applications 294 that use XML the format defined in vCard is not immediately 295 applicable. For this purpose an XML-based encoding of the 296 information elements defined in the vCard specification has been 297 defined and the name of that specification is xCard. Since the term 298 vCard is more familiar to most readers, we use the term xCard and 299 vCard interchangeably. 301 3. Document Scope 303 The scope of this document is explicitly limited to emergency calls. 304 The data structures defined here are not appropriate to be conveyed 305 with non-emergency calls because they carry sensitive and private 306 data. 308 4. Data Structures 310 This section defines the following five data structures, each as a 311 data block. For each block we define the MIME type, and the XML 312 encoding. The five data structures are: 314 'Data Provider': This block supplies name and contact information 315 for the entity that created the data. Section 4.1 provides the 316 details. 318 'Service Information': This block supplies information about the 319 service. The description can be found in Section 4.2. 321 'Device Information': This block supplies information about the 322 device placing the call. Device information can be found in 323 Section 4.3. 325 'Owner/Subscriber': This block supplies information about the owner 326 of the device or about the subscriber. Details can be found in 327 Section 4.4. 329 'Comment': This block provides a way to supply free form human 330 readable text to the PSAP or emergency responders. This simple 331 structure is defined in Section 4.5. 333 Each block contains a mandatory element. The 334 purpose of the element is to associate all 335 blocks added by the same data provider as a unit. The 336 element associates the data provider block to 337 each of the other blocks added as a unit. Consequently, when a data 338 provider adds additional data to an emergency call (such as device 339 information) it MUST add information about itself (via the data 340 provider block) and the blocks added contain the same value in the 341 element. All blocks added by a single entity 342 at the same time MUST have the same value. 343 The value of the element has the same syntax 344 and properties (specifically, world-uniqueness) as the value of the 345 "Message-ID" message body header field specified in RFC 5322 346 [RFC5322] except that the element is not 347 enclosed in brackets (the "<" and ">" symbols are omitted). In other 348 words, the value of a element is 349 syntactically a msg-id as specified in RFC 5322 [RFC5322]. 351 Note that the xCard format is re-used in some of the data structures 352 to provide contact information. In an xCard there is no way to 353 specify a "main" telephone number. These numbers are useful to 354 emergency responders who are called to a large enterprise. This 355 document adds a new property value to the "tel" property of the TYPE 356 parameter called "main". It can be used in any xCard in additional 357 data. 359 4.1. Data Provider Information 361 This block is intended to be supplied by any service provider in the 362 path of the call or the access network provider. It includes 363 identification and contact information. This block SHOULD be 364 supplied by every service provider in the call path, and by the 365 access network provider. Devices MAY use this block to provide 366 identifying information. The MIME subtype is "application/ 367 EmergencyCallData.ProviderInfo+xml". An access network provider 368 SHOULD provide this block either by value or by reference in the 369 provided-by section of a PIDF-LO 371 4.1.1. Data Provider String 373 Data Element: Data Provider String 375 Use: Required 377 XML Element: 379 Description: This is a plain text string suitable for displaying the 380 name of the service provider that supplied the data structure. If 381 the device creates the structure, it SHOULD use the value of the 382 contact header in the SIP INVITE. 384 Reason for Need: Inform the call taker of the identity of the entity 385 providing the data. 387 How Used by Call Taker: Allows the call taker to interpret the data 388 in this structure. The source of the information often influences 389 how the information is used, believed or verified. 391 4.1.2. Data Provider ID 393 Data Element: Data Provider ID 395 Use: Required. This data MUST be provided in order to uniquely 396 identify the service provider or access provider. 398 XML Element: 400 Description: A jurisdiction-specific code for, or the fully- 401 qualified domain name of, the access network provider or service 402 provider shown in the element that created the 403 structure. NOTE: The value SHOULD be assigned by an organization 404 appropriate for the jurisdiction. In the U.S., the provider's 405 NENA Company ID MUST appear here. Additional information can be 406 found at NENA Company Identifier Program [1] or NENA Company ID 407 [2]. The NENA Company ID MUST be in the form of a URI in the 408 following format: urn:nena:companyid:. The value 409 MAY be the fully-qualified domain name of the service provider or 410 access provider. 412 Reason for Need: Inform the call taker of the identity of the entity 413 providing the data. 415 How Used by Call Taker: Where jurisdictions have lists of providers 416 the Data Provider ID provides useful information about the data 417 source. The Data Provider ID uniquely identifies the source of 418 the data, which might be needed especially during unusual 419 circumstances and for routine logging. 421 4.1.3. Data Provider ID Series 423 Data Element: Data Provider ID Series 425 Use: Required. 427 XML Element: 429 Description: Identifies the issuer of the . The 430 Provider ID Series Registry (see Section 10.1) initially contains 431 the following valid entries: 433 * NENA 434 * EENA 436 * domain 438 Reason for Need: Identifies how to interpret the Data Provider ID. 439 The combination of ProviderIDSeries and ProviderID MUST be 440 globally unique. 442 How Used by Call Taker: Determines which provider ID registry to 443 consult for more information 445 4.1.4. Type of Data Provider 447 Data Element: Type of Data Provider 449 Use: Required. 451 XML Element: 453 Description: Identifies the type of data provider supplying the 454 data. A registry with an initial set of values is shown in 455 Figure 1 (see also Section 10.1). 457 +------------------------------+------------------------------------+ 458 | Token | Description | 459 +------------------------------+------------------------------------+ 460 |Access Network Provider | Access network service provider | 461 |Telecom Provider | Calling or origination telecom SP | 462 |Telematics Provider | A sensor based service provider, | 463 | | especially vehicle based | 464 |Language Translation Provider | A spoken language translation SP | 465 |Emergency Service Provider | An emergency service provider | 466 | | conveying information to another| 467 | | emergency service provider. | 468 |Emergency Modality Translation| An emergency call specific | 469 | | modality translation service | 470 | | e.g., for sign language | 471 |Relay Provider | A interpretation SP, for example, | 472 | | video relay for sign language | 473 | | interpreting | 474 |Other | Any other type of service provider | 475 +------------------------------+------------------------------------+ 477 Figure 1: Type of Data Provider Registry. 479 Reason for Need: Identifies the category of data provider. 481 How Used by Call Taker: This information may be helpful when 482 deciding whom to contact when further information is needed. 484 4.1.5. Data Provider Contact URI 486 Data Element: Data Provider Contact URI 488 Use: Required 490 XML Element: 492 Description: When provided by a service provider or an access 493 network provider, this information MUST be a URI to a 24/7 support 494 organization tasked to provide PSAP support for this emergency 495 call. If the call is from a device, this SHOULD be the contact 496 information of the owner of the device. The Data Provider Contact 497 URI SHOULD be a TEL URI [RFC3966] in E.164 format fully specified 498 with country code. If a TEL URI is not available, it MAY be a 499 generic SIP URI. Note that this contact information is not used 500 by PSAPs for callbacks (a call from a PSAP directly related to a 501 recently terminated emergency call, placed by the PSAP using a SIP 502 Priority header field set to "psap-callback", as described in 503 [RFC7090]). 505 Reason for Need: Additional data providers may need to be contacted 506 in error cases or other unusual circumstances. 508 How Used by Call Taker: To contact the supplier of the additional 509 data for assistance in handling the call. 511 4.1.6. Data Provider Languages(s) Supported 513 Data Element: Data Provider Language(s) supported 515 Use: Required. 517 XML Element: 519 Description: This field encodes the language used by the entity at 520 the Data Provider Contact URI. The content of this field consists 521 of a single token from the language tags registry, which can be 522 found at [LanguageTagRegistry], and is defined in [RFC5646]. 523 Multiple instances of this element may occur but the order is 524 significant and the preferred language should appear first. The 525 content MUST reflect the languages supported at the contact URI. 527 Note that the 'language' media feature tag, defined in RFC 3840 528 [RFC3840] and the more extensive language negotiation mechanism 529 proposed with [I-D.gellens-slim-negotiating-human-language] are 530 independent of this data provider language indication. 532 Reason for Need: This information indicates if the emergency service 533 authority can directly communicate with the service provider or if 534 an interpreter will be needed. 536 How Used by Call Taker: If the call taker cannot speak any language 537 supported by the service provider, a translation service will need 538 to be added to the conversation. Alternatively, other persons at 539 the PSAP, besides the call taker, might be consulted for help 540 (depending on the urgency and the type of interaction). 542 4.1.7. xCard of Data Provider 544 Data Element: xCard of Data Provider 546 Use: Optional 548 XML Element: 550 Description: Per [RFC6351] the xcard structure is represented within 551 a element. Although multiple elements may be 552 contained in a structure only one element SHOULD be 553 provided. If more than one appears, the first SHOULD be used. 554 There are many fields in the xCard and the creator of the data 555 structure is encouraged to provide as much information as they 556 have available. N, ORG, ADR, TEL, EMAIL are suggested at a 557 minimum. N SHOULD contain the name of the support group or device 558 owner as appropriate. If more than one TEL property is provided, 559 a parameter from the vCard Property Value registry MUST be 560 specified on each TEL. For encoding of the xCard this 561 specification uses the XML-based encoding specified in [RFC6351], 562 referred to in this document as "xCard". 564 Reason for Need: Information needed to determine additional contact 565 information. 567 How Used by Call Taker: Assists the call taker by providing 568 additional contact information aside from what may be included in 569 the SIP INVITE or the PIDF-LO. 571 4.1.8. Subcontractor Principal 573 When the entity providing the data is a subcontractor, the Data 574 Provider Type is set to that of the primary service provider and this 575 entry is supplied to provide information regarding the subcontracting 576 entity. 578 Data Element: Subcontractor Principal 580 Use: Conditional. This data is required if the entity providing the 581 data is a subcontractor. 583 XML Element: 585 Description: Some providers outsource their obligations to handle 586 aspects of emergency services to specialized providers. If the 587 data provider is a subcontractor to another provider this element 588 contains the DataProviderString of the service provider to 589 indicate which provider the subcontractor is working for. 591 Reason for Need: Identify the entity the subcontractor works for. 593 How Used by Call Taker: Allows the call taker to understand what the 594 relationship between data providers and the service providers in 595 the path of the call are. 597 4.1.9. Subcontractor Priority 599 Data Element: Subcontractor Priority 601 Use: Conditional. This element is required if the Data Provider 602 type is set to "Subcontractor". 604 XML Element: 606 Description: If the subcontractor has to be contacted first then 607 this element MUST have the value "sub". If the provider the 608 subcontractor is working for has to be contacted first then this 609 element MUST have the value "main". 611 Reason for Need: Inform the call taker whom to contact first, if 612 support is needed. 614 How Used by Call Taker: To decide which entity to contact first if 615 assistance is needed. 617 4.1.10. ProviderInfo Example 619 620 623 string0987654321@example.org 624 626 Example VoIP Provider 627 628 urn:nena:companyid:ID123 629 NENA 630 Telecom Provider 631 tel:+1-201-555-0123 632 en 633 635 636 Hannes Tschofenig 637 638 Hannes 639 Tschofenig 640 641 642 Dipl. Ing. 643 644 --0203 645 646 20090808T1430-0500 647 648 M 649 650 1 651 652 de 653 654 655 2 656 657 en 658 659 660 work 661 662 Example VoIP Provider 663 664 665 666 work 667 671 672 673 674 Linnoitustie 6 675 Espoo 676 Uusimaa 677 02600 678 Finland 679 680 681 682 683 work 684 voice 685 686 687 tel:+358 50 4871445 688 689 690 work 691 692 hannes.tschofenig@nsn.com 693 694 695 work 696 697 geo:60.210796,24.812924 698 699 700 home 701 702 703 http://www.tschofenig.priv.at/key.asc 704 705 706 Finland/Helsinki 707 708 home 709 710 http://www.tschofenig.priv.at 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 Simon Perreault 1238 1239 Perreault 1240 Simon 1241 1242 1243 ing. jr 1244 M.Sc. 1245 1246 --0203 1247 1248 20090808T1430-0500 1249 1250 M 1251 1252 1 1253 1254 fr 1255 1256 1257 2 1258 1259 en 1260 1261 1262 work 1263 1264 Viagenie 1265 1266 1267 1268 work 1269 1273 1274 1275 1276 2875 boul. Laurier, suite D2-630 1277 Quebec 1278 QC 1279 G1V 2M2 1280 Canada 1281 1282 1283 1284 1285 work 1286 voice 1287 1288 1289 tel:+1-418-656-9254;ext=102 1290 1291 1292 1293 1294 work 1295 text 1296 voice 1297 cell 1298 video 1299 1300 1301 tel:+1-418-262-6501 1302 1303 1304 work 1305 1306 simon.perreault@viagenie.ca 1307 1308 1309 work 1310 1311 geo:46.766336,-71.28955 1312 1313 1314 work 1315 1316 1317 http://www.viagenie.ca/simon.perreault/simon.asc 1318 1319 1320 America/Montreal 1321 1322 home 1323 1324 http://nomis80.org 1325 1326 1327 1328 1330 Figure 8: EmergencyCallData.SubscriberInfo Example. 1332 4.5. Comment 1334 This block provides a mechanism for the data provider to supply 1335 extra, human readable information to the PSAP. It is not intended 1336 for a general purpose extension mechanism nor does it aim to provide 1337 machine-readable content. The mime subtype is "application/ 1338 EmergencyCallData.Comment+xml" 1340 4.5.1. Comment 1342 Data Element: EmergencyCallData.Comment 1344 Use: Optional 1346 XML Element: 1348 Description: Human readable text providing additional information to 1349 the PSAP staff. 1351 Reason for Need: Explanatory information for values in the data 1352 structure. 1354 How Used by Call Taker: To interpret the data provided. 1356 4.5.2. EmergencyCallData.Comment Example 1358 1359 1362 string0987654321@example.org 1363 1364 This is an example text. 1365 1367 Figure 9: EmergencyCallData.Comment Example. 1369 5. Data Transport Mechanisms 1371 This section defines how to convey additional data to an emergency 1372 service provider. Two different means are specified: the first uses 1373 the call signaling; the second uses the element of a 1374 PIDF-LO [RFC4119]. 1376 1. First, the ability to embed a Uniform Resource Identifier (URI) 1377 in an existing SIP header field, the Call-Info header, is 1378 defined. The URI points to the additional data structure. The 1379 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1380 document adds a new compound token starting with the value 1381 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1382 the "purpose" parameter is set to a value starting with 1383 'EmergencyCallData', then the Call-Info header contains either an 1384 HTTPS URL pointing to an external resource or a CID (content 1385 indirection) URI that allows the data structure to be placed in 1386 the body of the SIP message. The "purpose" parameter also 1387 indicates the kind of data (by its MIME type) that is available 1388 at the URI. As the data is conveyed using a URI in the SIP 1389 signaling, the data itself may reside on an external resource, or 1390 may be contained within the body of the SIP message. When the 1391 URI refers to data at an external resource, the data is said to 1392 be passed by reference. When the URI refers to data contained 1393 within the body of the SIP message, the data is said to be passed 1394 by value. A PSAP or emergency responder is able to examine the 1395 type of data provided and selectively inspect the data it is 1396 interested in, while forwarding all of it (the values or 1397 references) to downstream entities. To be conveyed in a SIP 1398 body, additional data about a call is defined as a series of MIME 1399 objects. Each block defined in this document is an XML data 1400 structure identified by its MIME type. (Blocks defined by others 1401 may be encoded in XML or not, as identified by their MIME 1402 registration.) As usual, whenever more than one MIME part is 1403 included in the body of a message, MIME-multipart (i.e., 1404 'multipart/mixed') encloses them all. This document defines a 1405 set of XML schemas and MIME types used for each block defined 1406 here. When additional data is passed by value in the SIP 1407 signaling, each CID URL points to one block in the body. 1408 Multiple URIs are used within a Call-Info header field (or 1409 multiple Call-Info header fields) to point to multiple blocks. 1410 When additional data is provided by reference (in SIP signaling 1411 or provided-by), each HTTPS URL references one block; the data is 1412 retrieved with an HTTPS GET operation, which returns one of the 1413 blocks as an object (the blocks defined here are returned as XML 1414 objects). 1416 2. Second, the ability to embed additional data structures in the 1417 element of a PIDF-LO [RFC4119] is defined. In 1418 addition to service providers in the call path, the access 1419 network provider may also have similar information that may be 1420 valuable to the PSAP. The access network provider MAY provide 1421 location in the form of a PIDF-LO from a location server via a 1422 location configuration protocol. The data structures described 1423 in this document are not specific to the location itself, but 1424 rather provides descriptive information having to do with the 1425 immediate circumstances about the provision of the location (who 1426 the access network is, how to contact that entity, what kind of 1427 service the access network provides, subscriber information, 1428 etc.). This data is similar in nearly every respect to the data 1429 known by service providers in the path of the call. When the 1430 access network provider and service provider are separate 1431 entities, the access network does not participate in the 1432 application layer signaling (and hence cannot add a Call-Info 1433 header field to the SIP message), but may provide location 1434 information in a PIDF-LO object to assist in locating the 1435 caller's device. The element of the PIDF-LO is a 1436 mechanism for the access network provider to supply the 1437 information about the entity or organization that supplied this 1438 location information. For this reason, this document describes a 1439 namespace per RFC 4119 for inclusion in the element 1440 of a PIDF-LO for adding information known to the access network 1441 provider. The access network provider SHOULD provide additional 1442 data within a element of a PDIF-LO it returns for 1443 emergency use (e.g., if requested with a HELD "responseTime" 1444 attribute of "emergencyRouting" or "emergencyDispatch" 1445 [RFC5985]). 1447 One or more blocks of data registered in the Emergency Call 1448 Additional Data registry, as defined in Section 10.1, may be included 1449 or referenced in the SIP signaling (using the Call-Info header field) 1450 or in the element of a PIDF-LO. Every block must be 1451 one of the types in the registry. Since the data of an emergency 1452 call may come from multiple sources, the data itself needs 1453 information describing the source. Consequently, each entity adding 1454 additional data MUST supply the "Data Provider" block. All other 1455 blocks are optional, but each entity SHOULD supply any blocks where 1456 it has at least some of the information in the block. 1458 5.1. Transmitting Blocks using the Call-Info Header 1460 A URI to a block MAY be inserted in any SIP request or response 1461 method (most often INVITE or MESSAGE) with a Call-Info header field 1462 containing a purpose value starting with 'EmergencyCallData' and the 1463 type of data available at the URI. The type of data is denoted by 1464 including the root of the MIME type (not including the 1465 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1466 separator. For example, when referencing a block with MIME type 1467 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1468 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1469 "Call-Info" header field for this would be: 1471 Call-Info: https://www.example.com/23sedde3; 1472 purpose="EmergencyCallData.ProviderInfo" 1474 A Call-info header with a purpose value starting with 1475 'EmergencyCallData' MUST only be sent on an emergency call, which can 1476 be ascertained by the presence of an emergency service urn in a Route 1477 header of a SIP message. 1479 If the data is provided by reference, an HTTPS URI MUST be included 1480 and consequently Transport Layer Security (TLS) protection is applied 1481 for protecting the retrieval of the information. 1483 The data may also be supplied by value in any SIP request or response 1484 method that is permitted to contain a body (i.e., not a BYE request). 1485 In this case, Content Indirection (CID) [RFC2392] is used, with the 1486 CID URL referencing the MIME body part containing the data. 1488 Transmitting data by value is especially useful in certain cases, 1489 such as when the data exists in or is generated by the originating 1490 device, but is not intended for very large data blocks. Additional 1491 security and privacy considerations apply to data transmitted by 1492 value, as discussed in Section 8 and Section 9. 1494 More than one Call-Info header with a purpose value starting with 1495 'EmergencyCallData' can be expected, but at least one MUST be 1496 provided. The device MUST provide one if it knows no service 1497 provider is in the path of the call. The device MAY insert one if it 1498 uses a service provider. Any service provider in the path of the 1499 call MUST insert its own. For example, a device, a telematics 1500 service provider in the call path, as well as the mobile carrier 1501 handling the call will each provide one. There may be circumstances 1502 where there is a service provider who is unaware that the call is an 1503 emergency call and cannot reasonably be expected to determine that it 1504 is an emergency call. In that case, that service provider is not 1505 expected to provide EmergencyCallData. 1507 5.2. Transmitting Blocks by Reference using the provided-by Element 1509 The element is used to transmit an 1510 additional data block by reference within a element of 1511 a PIDF-LO. The element has two 1512 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1513 type of data block referenced. The value of 'ref' is an HTTPS URL 1514 that resolves to a data structure with information about the call. 1515 The value of 'purpose' is the same as used in a 'Call-Info' header 1516 field (as specified in Section 5.1). 1518 For example, to reference a block with MIME type 'application/ 1519 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1520 to 'EmergencyCallData.ProviderInfo'. An example 1521 'EmergencyCallDataReference' element for this would be: 1523 1526 The 'EmergencyCallDataReference' element transmits one additional 1527 data block; multiple additional data blocks may be transmitted by 1528 using multiple 'EmergencyCallDataReference' elements. 1530 For example: 1532 1533 1537 1541 1545 1549 1551 Example provided-by by Reference. 1553 5.3. Transmitting Blocks by Value using the provided-by Element 1555 It is RECOMMENDED that access networks supply the data specified in 1556 this document by reference, but they MAY provide the data by value. 1558 The element is used to transmit one or more 1559 additional data blocks by value within a element of a 1560 PIDF-LO. Each block being transmitted is placed (as a child element) 1561 inside the element. (The same XML structure 1562 as would be contained in the corresponding MIME type body part is 1563 placed inside the element.) 1565 For example: 1567 1568 1572 1574 1577 flurbit735@es.example.com 1578 1579 Access Network Examples, Inc 1580 1581 urn:nena:companyid:Test 1582 NENA 1583 Access Network Provider 1584 1585 tel:+1-555-555-0897 1586 en 1587 1589 1592 flurbit735@es.example.com 1593 1594 This is an example text. 1595 1596 1598 1600 1602 Example provided-by by Value. 1604 5.4. The Content-Disposition Parameter 1606 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1607 It updates and clarifies handling originally defined in RFC 3261 1608 [RFC3261] based on implementation experience. While RFC 3261 did not 1609 mandate support for 'multipart' message bodies, 'multipart/mixed' 1610 MIME bodies are used by many extensions (including this document) 1611 today. For example, adding a PIDF-LO, SDP, and additional data in 1612 body of a SIP message requires a 'multipart' message body. 1614 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1615 parameter for the Content-Disposition header field. These RFCs 1616 describe how a UAS reacts if it receives a message body whose content 1617 type or disposition type it does not understand. If the 'handling' 1618 parameter has the value "optional", the UAS ignores the message body. 1619 If the 'handling' parameter has the value "required", the UAS returns 1620 a 415 (Unsupported Media Type) response. The 'by-reference' 1621 disposition type allows a SIP message to contain a reference to the 1622 body part, and the SIP UA processes the body part according to the 1623 reference. This is the case for the Call-info header containing a 1624 Content Indirection (CID) URL. 1626 As an example, a SIP message indicates the Content-Disposition 1627 parameter in the body of the SIP message as shown in Figure 10. 1629 Content-Type: application/sdp 1631 ...Omit Content-Disposition here; defaults are ok 1632 ...SDP goes in here 1634 --boundary1 1636 Content-Type: application/pidf+xml 1637 Content-ID: 1638 Content-Disposition: by-reference;handling=optional 1640 ...PIDF-LO goes in here 1642 --boundary1-- 1644 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1645 Content-ID: <1234567890@atlanta.example.com> 1646 Content-Disposition: by-reference; handling=optional 1648 ...Data provider information data goes in here 1650 --boundary1-- 1652 Figure 10: Example for use of the Content-Disposition Parameter in 1653 SIP. 1655 6. Examples 1657 This section illustrates a longer and more complex example, as shown 1658 in Figure 11. In this example additional data is added by the end 1659 device, included by the VoIP provider (via the PIDF-LO), and provided 1660 by the access network provider. 1662 O +----+ [============] [=============] 1663 /|\ | UA | [ Access ] [ VoIP ] 1664 | +----+ [ Network ] [ Provider ] 1665 / \ [ Provider ] [ example.org ] 1666 [ ] [ ] 1667 (1) [ ] (2) [ ] 1668 Emergency Call [ ] Emergency Call [ ] 1669 -------------------------------------------------------> ] 1670 +Device Info [ ] +Device Info [ ] 1671 +Data Prov. Info [ ^ ] +Data Provider Info [ | ] 1672 +Location URI [=======.====] +Location URI [==|==========] 1673 . | 1674 . | 1675 +Location . [==============] | 1676 +Owner/Subscriber Info . [ ] (3) | 1677 +Device Info . (4) [ <----------+ 1678 +Data Provider Info #3 ..........> ] Emergency Call 1679 [ ] +Device Info 1680 [ PSAP ] +Data Prov. Info #2 1681 [ ] +Location URI 1682 [==============] 1684 Legend: 1686 --- Emergency Call Setup Procedure 1687 ... Location Retrieval/Response 1689 Figure 11: Additional Data Example Flow 1691 The example scenario starts with the end device itself adding device 1692 information, owner/subscriber information, a location URI, and data 1693 provider information to the outgoing emergency call setup message 1694 (see step #1 in Figure 11). The SIP INVITE example is shown in 1695 Figure 12. 1697 INVITE urn:service:sos SIP/2.0 1698 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1699 Max-Forwards: 70 1700 To: 1701 From: Hannes Tschofenig ;tag=9fxced76sl 1702 Call-ID: 3848276298220188511@example.com 1703 Call-Info: 1704 ;purpose=icon, 1705 ;purpose=info, 1706 1707 ;purpose=EmergencyCallData.ProviderInfo, 1708 1709 ;purpose=EmergencyCallData.DeviceInfo 1710 Geolocation: 1711 Geolocation-Routing: yes 1712 Accept: application/sdp, application/pidf+xml, 1713 application/EmergencyCallData.ProviderInfo+xml 1714 CSeq: 31862 INVITE 1715 Contact: 1716 Content-Type: multipart/mixed; boundary=boundary1 1718 Content-Length: ... 1720 --boundary1 1722 Content-Type: application/sdp 1724 ...SDP goes here 1726 --boundary1-- 1728 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1729 Content-ID: <0123456789@atlanta.example.com> 1730 Content-Disposition: by-reference;handling=optional 1731 1733 1736 d4b3072df09876543@[93.184.216.119] 1737 1738 laptop 1739 00-0d-4b-30-72-df 1741 1743 --boundary1-- 1745 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1746 Content-ID: <1234567890@atlanta.example.com> 1747 Content-Disposition: by-reference;handling=optional 1748 1749 1752 d4b3072df09876543@[93.184.216.119] 1753 1754 Hannes Tschofenig 1755 1756 Other 1757 tel:+1-555-555-0123 1758 en 1759 1761 1762 Hannes Tschofenig 1763 1764 Hannes 1765 Tschofenig 1766 1767 1768 Dipl. Ing. 1769 1770 --0203 1771 1772 20090808T1430-0500 1773 1774 M 1775 1776 1 1777 1778 de 1779 1780 1781 2 1782 1783 en 1784 1785 1786 1787 work 1788 1792 1793 1794 1795 Linnoitustie 6 1796 Espoo 1797 Uusimaa 1798 02600 1799 Finland 1800 1801 1802 1803 1804 work 1805 voice 1806 1807 1808 tel:+358 50 4871445 1809 1810 1811 work 1812 1813 hannes.tschofenig@nsn.com 1814 1815 1816 work 1817 1818 geo:60.210796,24.812924 1819 1820 1821 1822 home 1823 1824 https://www.example.com/key.asc 1825 1826 1827 Finland/Helsinki 1828 1829 home 1830 1831 http://example.com/hannes.tschofenig 1832 1833 1834 1835 1836 1837 --boundary1-- 1839 Figure 12: End Device sending SIP INVITE with Additional Data. 1841 In this example, information available to the access network provider 1842 is included in the call setup message only indirectly via the use of 1843 the location reference. The PSAP has to retrieve it via a separate 1844 look-up step. Since the access network provider and the VoIP service 1845 provider are two independent entities in this scenario, the access 1846 network provider is not involved in application layer exchanges; the 1847 SIP INVITE transits the access network transparently, as illustrated 1848 in steps #1 and #2. The access network does not alter the SIP 1849 INVITE. 1851 The VoIP service provider receives the message and determines based 1852 on the Service URN that the incoming request is an emergency call. 1853 It performs typical emergency services related tasks, including 1854 location-based routing, and adds additional data, namely service and 1855 subscriber information as well as data provider information #2, to 1856 the outgoing message. For the example we assume a VoIP service 1857 provider that deploys a back-to-back user agent allowing additional 1858 data to be included in the body of the SIP message (rather than per 1859 reference in the header), which allows us to illustrate the use of 1860 multiple data provider info blocks. The resulting message is shown 1861 in Figure 13. The SIP INVITE is sent to the PSAP in step #3. 1863 INVITE sips:psap@example.org SIP/2.0 1864 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1865 Max-Forwards: 70 1866 To: 1867 From: Hannes Tschofenig ;tag=9fxced76sl 1868 Call-ID: 3848276298220188511@example.com 1869 Call-Info: 1870 ;purpose=icon, 1871 ;purpose=info, 1872 1873 ;purpose=EmergencyCallData.ProviderInfo 1874 1875 ;purpose=EmergencyCallData.DeviceInfo 1876 Call-Info: 1877 ;purpose=EmergencyCallData.ServiceInfo 1878 Call-Info: 1879 ;purpose=EmergencyCallData.ProviderInfo 1880 Geolocation: 1881 Geolocation-Routing: yes 1882 Accept: application/sdp, application/pidf+xml, 1883 application/EmergencyCallData.ProviderInfo+xml 1884 CSeq: 31862 INVITE 1885 Contact: 1886 Content-Type: multipart/mixed; boundary=boundary1 1888 Content-Length: ... 1890 --boundary1 1892 Content-Type: application/sdp 1893 ...SDP goes here 1895 --boundary1-- 1897 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1898 Content-ID: <0123456789@atlanta.example.com> 1899 Content-Disposition: by-reference;handling=optional 1900 1902 1905 d4b3072df09876543@[93.184.216.119] 1906 1907 laptop 1908 00-0d-4b-30-72-df 1910 1912 --boundary1-- 1914 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1915 Content-ID: <1234567890@atlanta.example.com> 1916 Content-Disposition: by-reference;handling=optional 1917 1918 1921 d4b3072df09876543@[93.184.216.119] 1922 1923 Hannes Tschofenig 1924 1925 Other 1926 tel:+1-555-555-0123 1927 en 1928 1930 1931 Hannes Tschofenig 1932 1933 Hannes 1934 Tschofenig 1935 1936 1937 Dipl. Ing. 1938 1939 --0203 1940 1941 20090808T1430-0500 1942 1943 M 1944 1945 1 1946 1947 de 1948 1949 1950 2 1951 1952 en 1953 1954 1955 1956 work 1957 1961 1962 1963 1964 Linnoitustie 6 1965 Espoo 1966 Uusimaa 1967 02600 1968 Finland 1969 1970 1971 1972 1973 work 1974 voice 1975 1976 1977 tel:+358 50 4871445 1978 1979 1980 work 1981 1982 hannes.tschofenig@nsn.com 1983 1984 1985 work 1986 1987 geo:60.210796,24.812924 1988 1989 1990 1991 home 1992 1993 https://www.example.com/key.asc 1994 1995 1996 Finland/Helsinki 1997 1998 home 1999 2000 http://example.com/hannes.tschofenig 2001 2002 2003 2004 2005 2007 --boundary1-- 2009 Content-Type: application/EmergencyCallData.ServiceInfo+xml 2010 Content-ID: 2011 Content-Disposition: by-reference;handling=optional 2012 2013 2016 string0987654321@example.org 2017 2018 Residence 2019 VOIP 2020 Unknown 2021 2023 --boundary1-- 2025 Content-Type: application/EmergencyCallData.ProviderInfo+xml 2026 Content-ID: 2027 Content-Disposition: by-reference;handling=optional 2028 2029 2032 string0987654321@example.org 2033 2034 Example VoIP Provider 2035 2036 urn:nena:companyid:ID123 2037 NENA 2038 Service Provider 2039 sip:voip-provider@example.com 2040 en 2041 2043 2044 John Doe 2045 2046 John 2047 Doe 2048 2049 2050 2051 2052 --0203 2053 2054 20090808T1430-0500 2055 2056 M 2057 2058 1 2059 2060 en 2061 2062 2063 work 2064 2065 Example VoIP Provider 2066 2067 2068 2069 work 2070 2073 2074 2075 2076 Downing Street 10 2077 London 2078 2079 SW1A 2AA 2080 UK 2081 2082 2083 2084 2085 work 2086 voice 2087 2088 2089 sips:john.doe@example.com 2090 2091 2092 work 2093 2094 john.doe@example.com 2095 2096 2097 work 2098 2099 geo:51.503396, 0.127640 2100 2101 Europe/London 2102 2103 home 2104 2105 http://www.example.com/john.doe 2106 2107 2108 2109 2111 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2113 Finally, the PSAP requests location information from the access 2114 network provider. The response is shown in Figure 14. Along with 2115 the location information, additional data is provided in the 2116 element of the PIDF-LO. This request and response is 2117 step #4. 2119 2120 2125 2126 2127 2128 2130 AU 2131 NSW 2132 Wollongong 2133 North Wollongong 2134 Flinders 2135 Street 2136 Campbell Street 2137 Gilligan's Island 2138 Corner 2139 Video Rental Store 2140 2500 2141 Westerns and Classics 2142 store 2143 Private Box 15 2144 2145 2146 2147 true 2148 2149 2013-12-10T20:00:00Z 2150 2151 2152 802.11 2154 2157 2161 2162 2165 88QV4FpfZ976T@example.com 2166 2167 University of Example 2168 2169 urn:nena:companyid:uoi 2170 NENA 2171 Other 2172 tel:+1-555-824-5222 2173 en 2174 2176 2178 88QV4FpfZ976T@example.com 2179 2180 This is an example text. 2181 2183 2184 2185 2186 mac:00-0d-4b-30-72-df 2187 2013-07-09T20:57:29Z 2188 2189 2191 Figure 14: Access Network Provider returning PIDF-LO with Additional 2192 Data. 2194 7. XML Schemas 2196 This section defines the XML schemas of the five data blocks. 2197 Additionally, the provided-by schema is specified. 2199 7.1. EmergencyCallData.ProviderInfo XML Schema 2201 2202 2212 2215 2217 2222 2223 2224 2225 2227 2228 2230 2231 2232 2235 2238 2241 2244 2247 2250 2251 2252 2253 2259 2260 2261 2263 2265 2266 2267 2269 2270 2271 2272 2275 2279 2281 2282 2284 2286 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2288 7.2. EmergencyCallData.ServiceInfo XML Schema 2289 2290 2299 2302 2305 2306 2307 2310 2313 2317 2320 2322 2323 2325 2327 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2329 7.3. EmergencyCallData.DeviceInfo XML Schema 2331 2332 2341 2344 2347 2348 2349 2352 2355 2358 2361 2363 2364 2365 2366 2369 2370 2371 2372 2374 2377 2380 2382 2383 2385 2387 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2389 7.4. EmergencyCallData.SubscriberInfo XML Schema 2391 2392 2403 2406 2408 2411 2412 2413 2414 2415 2418 2419 2420 2421 2423 2424 2425 2427 2429 2430 2432 2433 2434 2436 2438 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2440 7.5. EmergencyCallData.Comment XML Schema 2441 2442 2451 2454 2457 2458 2459 2462 2466 2468 2469 2471 2472 2473 2474 2475 2476 2477 2479 2481 Figure 19: EmergencyCallData.Comment XML Schema. 2483 7.6. provided-by XML Schema 2485 This section defines the provided-by schema. 2487 2488 2503 2505 2507 2509 2511 2514 2516 2517 2518 2522 2526 2529 2531 2533 2535 2536 2537 2538 2539 2541 2542 2544 2546 2547 2548 2550 2552 2553 2554 2557 2560 2563 2566 2570 2573 2574 2576 2578 Figure 20: provided-by XML Schema. 2580 8. Security Considerations 2582 The data structures described in this document contain information 2583 usually considered private. When information is provided by value, 2584 entities that are a party to the SIP signaling (such as proxy servers 2585 and back-to-back user agents) will have access to it and need to 2586 protect it against inappropriate disclosure. An entity that is able 2587 to eavesdrop on the SIP signaling will also have access. Some media 2588 (such as in the clear Wi-Fi) is more vulnerable than others (such as 2589 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that 2590 protect against eavesdropping (such as Transport Layer Security 2591 (TLS)) SHOULD be preferentially used whenever feasible. When 2592 information is provided by reference, HTTPS is specified for 2593 dereferencing, and the provider of the information is REQUIRED to 2594 validate the credentials of the requester. While the creation of a 2595 public key infrastructure (PKI) that has global scope may be 2596 difficult, the alternatives to creating devices and services that can 2597 provide critical information securely are more daunting. The 2598 provider of the information MAY enforce any policy it wishes to use, 2599 but PSAPs and responder agencies SHOULD deploy a PKI so that 2600 providers of additional data can check the certificate of the client 2601 and decide the appropriate policy to enforce based on that 2602 certificate. 2604 Ideally, the PSAP and emergency responders will be given credentials 2605 signed by an authority trusted by the data provider. In most 2606 circumstances, nationally recognized credentials would be sufficient, 2607 and if the emergency services arranges a PKI, data providers could be 2608 provisioned with the root CA public key for a given nation. Some 2609 nations are developing a PKI for this, and related, purposes. Since 2610 calls could be made from devices where the device and/or the service 2611 provider(s) are not local to the emergency services authorities, 2612 globally recognized credentials are useful. This might be 2613 accomplished by extending the notion of the "forest guide" described 2614 in [RFC5582] to allow the forest guide to provide the credential of 2615 the PKI root for areas for which it has coverage information, but 2616 standards for such a mechanism are not yet available. In its 2617 absence, the data provider will need to obtain by out of band means 2618 the root CA credentials for any areas to which it is willing to 2619 provide additional data. With the credential of the root CA for a 2620 national emergency services PKI, the data provider server can 2621 validate the credentials of an entity requesting additional data by 2622 reference. 2624 The data provider also needs a credential that can be verified by the 2625 emergency services to know that it is receiving data from an 2626 authorized server. The emergency services authorities could provide 2627 credentials, distinguishable from credentials provided to emergency 2628 responders and PSAPs, which could be used to validate data providers. 2629 Such credentials would have to be acceptable to any PSAP or responder 2630 that could receive a call with additional data supplied by that 2631 provider. This would be extensible to global credential validation 2632 using the forest guide as mentioned above. In the absence of such 2633 credentials, the emergency services authorities could maintain a list 2634 of local data providers' credentials as provided to them out of band. 2635 At a minimum, the emergency services authorities could obtain a 2636 credential from the DNS entry of the domain in the Additional Data 2637 URI to at least validate that the server is known to the domain 2638 providing the URI. 2640 Data provided by devices by reference have similar credential 2641 validation issues as for service providers, and the solutions are the 2642 same. 2644 Much of the information supplied by service providers and devices is 2645 private and confidential; service providers and devices generally go 2646 to lengths to protect this information; disclosing it in the context 2647 of an emergency call is a trade-off to protect the greater interest 2648 of the customer in an emergency. 2650 Neither service providers nor devices will supply private information 2651 unless the call is recognized as an emergency call. In cellular 2652 telephony systems (such as those using 3GPP IMS), there are different 2653 procedures for an originating device to place an emergency versus a 2654 normal call. If a call that is really an emergency call is initiated 2655 as a normal call and the cellular service provider recognizes this, 2656 3GPP IMS permits the service provider to either accept the call 2657 anyway or reject it with a specific code that instructs the device to 2658 retry the call as an emergency call. Service providers SHOULD choose 2659 the latter, because otherwise the device will not have included the 2660 information specified in this document (since the device didn't 2661 recognize the call as being an emergency call). 2663 9. Privacy Considerations 2665 This document enables functionality for conveying additional 2666 information about the caller and the caller's device and service to 2667 the callee. Some of this information is personal data and therefore 2668 privacy concerns arise. An explicit privacy indicator for 2669 information directly relating to the caller's identity is defined and 2670 use is mandatory. However, observance of this request for privacy 2671 and what information it relates to is determined by the destination 2672 jurisdiction. 2674 There are a number of privacy concerns with non-emergency real-time 2675 communication services that are also applicable to emergency calling. 2677 Data protection regulation world-wide has, however, decided to create 2678 exceptions for emergency services since the drawbacks of disclosing 2679 personal data are outweighed by the benefit for the emergency caller. 2680 Hence, the data protection rights of individuals are commonly waived 2681 for emergency situations. There are, however, still various 2682 countries that offer some degree of anonymity for the caller towards 2683 PSAP call takers. 2685 The functionality defined in this document, however, far exceeds the 2686 amount of information sharing found in the legacy POTS system. For 2687 this reason there are additional privacy threats to consider, which 2688 are described in more detail in [RFC6973]. 2690 Stored Data Compromise: There is an increased risk of stored data 2691 compromise since additional data is collected and stored in 2692 databases. Without adequate measures to secure stored data from 2693 unauthorized or inappropriate access at access network providers, 2694 service providers, end devices, as well as PSAPs, individuals are 2695 exposed to potential financial, reputational, or physical harm. 2697 Misattribution: If the personal data collected and conveyed is 2698 incorrect or inaccurate then this may lead to misattribution. 2699 Misattribution occurs when data or communications related to one 2700 individual are attributed to another. 2702 Identification: By the nature of the additional data and its 2703 capability to provide much richer information about the caller, 2704 the call, and the location, the calling party is identified in a 2705 much better way. Some users may feel uncomfortable with this 2706 degree of information sharing even in emergency services 2707 situations. 2709 Secondary Use: There is a risk of secondary use, which is the use of 2710 collected information about an individual without the individual's 2711 consent for a purpose different from that for which the 2712 information was collected. The stated purpose of the additional 2713 data is for emergency services purposes but theoretically the same 2714 information could be used for any other call as well. 2715 Additionally, parties involved in the emergency call may retain 2716 the obtained information and may re-use it for other, non- 2717 emergency services purposes. 2719 Disclosure: When the data defined in this document is not properly 2720 protected (while in transit with traditional communication 2721 security techniques, and while stored using access control 2722 mechanisms) there is the risk of disclosure, which is the 2723 revelation of private information about an individual. 2725 To mitigate these privacy risks the following countermeasures can be 2726 taken: 2728 In regions where callers can elect to suppress certain personally 2729 identifying information, network or PSAP functionality can inspect 2730 privacy flags within the SIP headers to determine what information 2731 may be passed, stored, or displayed to comply with local policy or 2732 law. RFC 3325 [RFC3325] defines the "id" priv-value token. The 2733 presence of this privacy type in a Privacy header field indicates 2734 that the user would like the network asserted identity to be kept 2735 private with respect to SIP entities outside the trust domain with 2736 which the user authenticated, including the PSAP. 2738 This document defines various data structures that contain privacy- 2739 sensitive data. For example, identifiers for the device (e.g., 2740 serial number, MAC address) or account/SIM (e.g., IMSI), contact 2741 information for the user, location of the caller. Local regulations 2742 may govern what data must be provided in emergency calls, but in 2743 general, the emergency call system is aided by the information 2744 described in this document. There is a tradeoff between the privacy 2745 considerations and the utility of the data. For protection, this 2746 specification requires all retrieval of data passed by reference to 2747 be protected against eavesdropping and alteration via communication 2748 security techniques (namely TLS). Furthermore, security safeguards 2749 are required to prevent unauthorized access to stored data. Various 2750 security incidents over at least the past few decades have shown that 2751 data breaches are not uncommon and are often caused by lack of proper 2752 access control frameworks, software bugs (such as buffer overflows), 2753 or missing input parsing (such as SQL injection attacks). The risks 2754 of data breaches is increased with the obligation for emergency 2755 services to retain emergency call related data for extended periods 2756 (e.g., several years are the norm). 2758 Finally, it is also worth highlighting the nature of the SIP 2759 communication architecture, which introduces additional complications 2760 for privacy. Some forms of data can be sent by value in the SIP 2761 signaling or by reference (a URL in the SIP signaling). When data is 2762 sent by value, all intermediaries have access to the data. As such, 2763 these intermediaries may also introduce additional privacy risk. 2764 Therefore, in situations where the conveyed information is privacy- 2765 sensitive and intermediaries are involved, transmitting by reference 2766 might be appropriate, assuming the source of the data can operate a 2767 sufficient dereferencing infrastructure and that proper access 2768 control policies are available for distinguishing the different 2769 entities dereferencing the reference. Without access control 2770 policies any party in possession of the reference is able to resolve 2771 the reference and to obtain the data, including intermediaries. 2773 10. IANA Considerations 2775 10.1. Registry creation 2777 This document creates a new registry called 'Emergency Call 2778 Additional Data'. The following sub-registries are created for this 2779 registry. 2781 10.1.1. Provider ID Series Registry 2783 This document creates a new sub-registry called 'Additional Call Data 2784 Provider ID Series'. As defined in [RFC5226], this registry operates 2785 under "Expert Review" rules. The expert should determine that the 2786 entity requesting a new value is a legitimate issuer of service 2787 provider IDs suitable for use in Additional Call Data. 2789 Private entities issuing and using internally-generated IDs are 2790 encouraged to register and use a unique identifier. This guarantees 2791 that IDs issued and used by the entity are globally unique and 2792 distinguishable. 2794 The content of this registry includes: 2796 Name: The identifier which will be used in the 'ProviderIDSeries' 2797 element. 2799 Source: The full name of the organization issuing the identifiers. 2801 URL: A URL to the organization for further information. 2803 The initial set of values is listed in Figure 21. 2805 +-----------+--------------------------+----------------------+ 2806 | Name | Source | URL | 2807 +-----------+--------------------------+----------------------+ 2808 | NENA | National Emergency | http://www.nena.org | 2809 | | Number Association | | 2810 | EENA | European Emergency | http://www.eena.org | 2811 | | Number Association | | 2812 | domain | (The ID is a fully- | (not applicable) | 2813 | | qualified domain name) | | 2814 +-----------+--------------------------+----------------------+ 2816 Figure 21: Provider ID Series Registry. 2818 10.1.2. Service Environment Registry 2820 This document creates a new sub-registry called 'Additional Call 2821 Service Environment'. As defined in [RFC5226], this registry 2822 operates under "Expert Review" rules. The expert should determine 2823 that the entity requesting a new value is relevant for this service 2824 element, and that the new value is distinct from existing values, and 2825 its use is unambiguous. 2827 The content of this registry includes: 2829 Token: The value to be used in the element. 2831 Description: A s[RFC4119]hort description of the value. 2833 The initial set of values is listed in Figure 22. 2835 +-----------+--------------------------+ 2836 | Token | Description | 2837 +-----------+--------------------------+ 2838 | Business | Business service | 2839 | Residence | Residential service | 2840 | unknown | Type of service unknown | 2841 | | (e.g., anonymous pre- | 2842 | | paid service) | 2843 +-----------+--------------------------+ 2845 Figure 22: Service Environment Registry. 2847 10.1.3. Service Type Registry 2849 This document creates a new sub-registry called 'Additional Call 2850 Service Type'. As defined in [RFC5226], this registry operates under 2851 "Expert Review" rules. The expert should determine that the entity 2852 requesting a new value is relevant for this service element and that 2853 the requested value is clearly distinct from other values so that 2854 there is no ambiguity as to when the value is to be used or which 2855 value is to be used. 2857 The content of this registry includes: 2859 Name: The value to be used in the element. 2861 Description: A short description of the value. 2863 The initial set of values is listed in Figure 3. 2865 10.1.4. Service Mobility Registry 2867 This document creates a new sub-registry called 'Additional Call 2868 Service Mobility'. As defined in [RFC5226], this registry operates 2869 under "Expert Review" rules. The expert should determine that the 2870 entity requesting a new value is relevant for this service element 2871 and that the requested value is clearly distinct from other values so 2872 that there is no ambiguity as to when the value is to be used or 2873 which value is to be used. 2875 The content of this registry includes: 2877 Token: The value used in the element. 2879 Description: A short description of the value. 2881 The initial set of values is listed in Figure 23. 2883 +-----------+----------------------------+ 2884 | Token | Description | 2885 +-----------+----------------------------+ 2886 | Mobile | The device is able to | 2887 | | move at any time | 2888 | Fixed | The device is not expected | 2889 | | to move unless the service | 2890 | | is relocated | 2891 | Nomadic | The device is not expected | 2892 | | to change its point of | 2893 | | attachment while on a call | 2894 | Unknown | No information is known | 2895 | | about the service mobility | 2896 | | environment for the device | 2897 +-----------+----------------------------+ 2899 Figure 23: Service Environment Registry. 2901 10.1.5. Service Provider Type Registry 2903 This document creates a new sub-registry called 'Service Provider 2904 Type'. As defined in [RFC5226], this registry operates under "Expert 2905 Review". The expert should determine that the proposed new value is 2906 distinct from existing values and appropriate for use in the 2907 TypeOfServicerProvider element 2909 The content of this registry includes: 2911 Tokenproviderid: The value used in the 'TypeOfProvider' element. 2913 Description: A short description of the type of service provider. 2915 The initial set of values is defined in Figure 1. 2917 10.1.6. Service Delivered Registry 2919 This document creates a new sub-registry called 'Service Delivered'. 2920 As defined in [RFC5226], this registry operates under "Expert Review" 2921 rules. The expert should consider whether the proposed service is 2922 unique from existing services and the definition of the service will 2923 be clear to implementors and PSAPs/responders. 2925 The content of this registry includes: 2927 Name: The value used in the 'ServiceType' element. 2929 Description: Short description identifying the nature of the 2930 service. 2932 The initial set of values are defined in Figure 3. 2934 10.1.7. Device Classification Registry 2936 This document creates a new sub-registry called 'Device 2937 Classification'. As defined in [RFC5226], this registry operates 2938 under "Expert Review" rules. The expert should consider whether the 2939 proposed class is unique from existing classes and the definition of 2940 the class will be clear to implementors and PSAPs/responders. 2942 The content of this registry includes: 2944 Token: Value used in the 'DeviceClassification' element. 2946 Description: Short description identifying the device type. 2948 The initial set of values are defined in Figure 5. 2950 10.1.8. Device ID Type Type Registry 2952 This document creates a new sub-registry called 'Additional Call Data 2953 Device ID Type'. As defined in [RFC5226], this registry operates 2954 under "Expert Review" rules. The expert should ascertain that the 2955 proposed type is well understood, and provides the information useful 2956 to PSAPs and responders to uniquely identify a device. 2958 The content of this registry includes: 2960 Token: The value to be placed in the 'TypeOfDeviceID' element. 2962 Description: Short description identifying the type of the device 2963 ID. 2965 The initial set of values are defined in Figure 6. 2967 10.1.9. Device/Service Data Type Registry 2969 This document creates a new sub-registry called 'Device/Service Data 2970 Type Registry'. As defined in [RFC5226], this registry operates 2971 under "Expert Review" and "Specification Required" rules. The expert 2972 should ascertain that the proposed type is well understood, and 2973 provides information useful to PSAPs and responders. The 2974 specification must contain a complete description of the data, and a 2975 precise format specification suitable to allow interoperable 2976 implementations. 2978 The content of this registry includes: 2980 Token: The value to be placed in the element. 2982 Description: Short description identifying the the data. 2984 Specification: Citation for the specification of the data. 2986 The initial set of values are listed in Figure 24. 2988 +----------+----------------------------------------+---------------+ 2989 | Token | Description | Specification | 2990 +----------+----------------------------------------+---------------+ 2991 | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006| 2992 +----------+----------------------------------------+---------------+ 2994 Figure 24: Device/Service Data Type Registry. 2996 10.1.10. Emergency Call Data Types Registry 2998 This document creates a new sub-registry called 'Emergency Call Data 2999 Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. 3000 As defined in [RFC5226], this registry operates under "Expert Review" 3001 and "Specification Required" rules. The expert is responsible for 3002 verifying that the document contains a complete and clear 3003 specification and the proposed functionality does not obviously 3004 duplicate existing functionality. 3006 The registry contains an entry for every data block that can be sent 3007 with an emergency call using the mechanisms as specified in this 3008 document. Each data block is identified by the "root" of its MIME 3009 subtype (which is the part after 'EmergencyCallData.'). If the MIME 3010 subtype does not start with 'EmergencyCallData.' then it cannot be 3011 registered here nor used in a Call-Info header as specified in this 3012 document. The subtype MAY exist under any MIME type (although most 3013 commonly these are under 'Application/' this is NOT REQUIRED). 3015 The content of this registry includes: 3017 Token: The root of the data's MIME subtype (not including the 3018 'EmergencyCallData' prefix and any suffix such as '+xml') 3020 Reference: The document that describes the data object 3022 Note that the values from this registry are part of the 3023 'EmergencyCallData' compound value; when used as a value of the 3024 'purpose' parameter of the Call-Info header, the values listed in 3025 this registry are prefixed by 'EmergencyCallData.' per the the 3026 'EmergencyCallData' registation Section 10.2. 3028 The initial set of values are listed in Figure 25. 3030 +----------------+------------+ 3031 | Token | Reference | 3032 +----------------+------------+ 3033 | ProviderInfo | [This RFC] | 3034 | ServiceInfo | [This RFC] | 3035 | DeviceInfo | [This RFC] | 3036 | SubscriberInfo | [This RFC] | 3037 | Comment | [This RFC] | 3038 +----------------+------------+ 3040 Figure 25: Additional Data Blocks Registry. 3042 10.2. 'EmergencyCallData' Purpose Parameter Value 3044 This document defines the 'EmergencyCallData' value for the "purpose" 3045 parameter of the Call-Info header field. The Call-Info header and 3046 the corresponding registry for the 'purpose' parameter was 3047 established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' 3048 is a compound value; when used as a value of the 'purpose' parameter 3049 of the Call-Info header, 'EmergencyCallData' is immediately followed 3050 by a dot ('.') and a value from the 'Emergency Call Data Types' 3051 registry Section 10.1.10. 3053 Header Parameter New 3054 Field Name Value Reference 3055 ---------- --------- ----------------- --------- 3056 Call-Info purpose EmergencyCallData [This RFC] 3058 10.3. URN Sub-Namespace Registration for provided-by Registry Entry 3060 This section registers the namespace specified in Section 10.5.1 in 3061 the provided-by registry established by RFC 4119, for usage within 3062 the element of a PIDF-LO. 3064 The schema for the element used by this document is 3065 specified in Section 7.6. 3067 10.4. MIME Registrations 3069 10.4.1. MIME Content-type Registration for 'application/ 3070 EmergencyCallData.ProviderInfo+xml' 3072 This specification requests the registration of a new MIME type 3073 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3074 RFC 7303 [RFC7303]. 3076 MIME media type name: application 3078 MIME subtype name: EmergencyCallData.ProviderInfo+xml 3080 Mandatory parameters: none 3082 Optional parameters: charset (indicates the character encoding of 3083 the contents) 3085 Encoding considerations: Uses XML, which can contain 8-bit 3086 characters, depending on the character encoding. See Section 3.2 3087 of RFC 7303 [RFC7303]. 3089 Security considerations: This content type is designed to carry 3090 the data provider information, which is a sub-category of 3091 additional data about an emergency call. Since this data may 3092 contain personal information, appropriate precautions might be 3093 needed to limit unauthorized access, inappropriate disclosure, and 3094 eavesdropping of personal information. Please refer to Section 8 3095 and Section 9 for more information. 3097 Interoperability considerations: None 3098 Published specification: [TBD: This specification] 3100 Applications which use this media type: Emergency Services 3102 Additional information: 3104 Magic Number: None 3106 File Extension: .xml 3108 Macintosh file type code: 'TEXT' 3110 Person and email address for further information: Hannes 3111 Tschofenig, Hannes.Tschofenig@gmx.net 3113 Intended usage: LIMITED USE 3115 Author: This specification is a work item of the IETF ECRIT 3116 working group, with mailing list address . 3118 Change controller: The IESG 3120 10.4.2. MIME Content-type Registration for 'application/ 3121 EmergencyCallData.ServiceInfo+xml' 3123 This specification requests the registration of a new MIME type 3124 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3125 RFC 7303 [RFC7303]. 3127 MIME media type name: application 3129 MIME subtype name: EmergencyCallData.ServiceInfo+xml 3131 Mandatory parameters: none 3133 Optional parameters: charset (indicates the character encoding of 3134 the contents) 3136 Encoding considerations: Uses XML, which can contain 8-bit 3137 characters, depending on the character encoding. See Section 3.2 3138 of RFC 7303 [RFC7303]. 3140 Security considerations: This content type is designed to carry 3141 the service information, which is a sub-category of additional 3142 data about an emergency call. Since this data may contain 3143 personal information, appropriate precautions may be needed to 3144 limit unauthorized access, inappropriate disclosure, and 3145 eavesdropping of personal information. Please refer to Section 8 3146 and Section 9 for more information. 3148 Interoperability considerations: None 3150 Published specification: [TBD: This specification] 3152 Applications which use this media type: Emergency Services 3154 Additional information: 3156 Magic Number: None 3158 File Extension: .xml 3160 Macintosh file type code: 'TEXT' 3162 Person and email address for further information: Hannes 3163 Tschofenig, Hannes.Tschofenig@gmx.net 3165 Intended usage: LIMITED USE 3167 Author: This specification is a work item of the IETF ECRIT 3168 working group, with mailing list address . 3170 Change controller: The IESG 3172 10.4.3. MIME Content-type Registration for 'application/ 3173 EmergencyCallData.DeviceInfo+xml' 3175 This specification requests the registration of a new MIME type 3176 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3177 RFC 7303 [RFC7303]. 3179 MIME media type name: application 3181 MIME subtype name: EmergencyCallData.DeviceInfo+xml 3183 Mandatory parameters: none 3185 Optional parameters: charset (indicates the character encoding of 3186 the contents) 3188 Encoding considerations: Uses XML, which can contain 8-bit 3189 characters, depending on the character encoding. See Section 3.2 3190 of RFC 7303 [RFC7303]. 3192 Security considerations: This content type is designed to carry 3193 device information, which is a sub-category of additional data 3194 about an emergency call. Since this data contains personal 3195 information, appropriate precautions need to be taken to limit 3196 unauthorized access, inappropriate disclosure to third parties, 3197 and eavesdropping of this information. Please refer to Section 8 3198 and Section 9 for more information. 3200 Interoperability considerations: None 3202 Published specification: [TBD: This specification] 3204 Applications which use this media type: Emergency Services 3206 Additional information: 3208 Magic Number: None 3210 File Extension: .xml 3212 Macintosh file type code: 'TEXT' 3214 Person and email address for further information: Hannes 3215 Tschofenig, Hannes.Tschofenig@gmx.net 3217 Intended usage: LIMITED USE 3219 Author: This specification is a work item of the IETF ECRIT 3220 working group, with mailing list address . 3222 Change controller: The IESG 3224 10.4.4. MIME Content-type Registration for 'application/ 3225 EmergencyCallData.SubscriberInfo+xml' 3227 This specification requests the registration of a new MIME type 3228 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3229 RFC 7303 [RFC7303]. 3231 MIME media type name: application 3233 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 3235 Mandatory parameters: none 3237 Optional parameters: charset (indicates the character encoding of 3238 the contents) 3239 Encoding considerations: Uses XML, which can contain 8-bit 3240 characters, depending on the character encoding. See Section 3.2 3241 of RFC 7303 [RFC7303]. 3243 Security considerations: This content type is designed to carry 3244 owner/subscriber information, which is a sub-category of 3245 additional data about an emergency call. Since this data contains 3246 personal information, appropriate precautions need to be taken to 3247 limit unauthorized access, inappropriate disclosure to third 3248 parties, and eavesdropping of this information. Please refer to 3249 Section 8 and Section 9 for more information. 3251 Interoperability considerations: None 3253 Published specification: [TBD: This specification] 3255 Applications which use this media type: Emergency Services 3257 Additional information: 3259 Magic Number: None 3261 File Extension: .xml 3263 Macintosh file type code: 'TEXT' 3265 Person and email address for further information: Hannes 3266 Tschofenig, Hannes.Tschofenig@gmx.net 3268 Intended usage: LIMITED USE 3270 Author: This specification is a work item of the IETF ECRIT 3271 working group, with mailing list address . 3273 Change controller: The IESG 3275 10.4.5. MIME Content-type Registration for 'application/ 3276 EmergencyCallData.Comment+xml' 3278 This specification requests the registration of a new MIME type 3279 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3280 RFC 7303 [RFC7303]. 3282 MIME media type name: application 3284 MIME subtype name: EmergencyCallData.Comment+xml 3286 Mandatory parameters: none 3287 Optional parameters: charset (indicates the character encoding of 3288 the contents) 3290 Encoding considerations: Uses XML, which can contain 8-bit 3291 characters, depending on the character encoding. See Section 3.2 3292 of RFC 7303 [RFC7303]. 3294 Security considerations: This content type is designed to carry a 3295 comment, which is a sub-category of additional data about an 3296 emergency call. This data may contain personal information. 3297 Appropriate precautions may be needed to limit unauthorized 3298 access, inappropriate disclosure to third parties, and 3299 eavesdropping of this information. Please refer to Section 8 and 3300 Section 9 for more information. 3302 Interoperability considerations: None 3304 Published specification: [TBD: This specification] 3306 Applications which use this media type: Emergency Services 3308 Additional information: 3310 Magic Number: None 3312 File Extension: .xml 3314 Macintosh file type code: 'TEXT' 3316 Person and email address for further information: Hannes 3317 Tschofenig, Hannes.Tschofenig@gmx.net 3319 Intended usage: LIMITED USE 3321 Author: This specification is a work item of the IETF ECRIT 3322 working group, with mailing list address . 3324 Change controller: The IESG 3326 10.5. URN Sub-Namespace Registration 3328 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3330 This section registers a new XML namespace, as per the guidelines in 3331 RFC 3688 [RFC3688]. 3333 URI: urn:ietf:params:xml:ns:EmergencyCallData 3334 Registrant Contact: IETF, ECRIT working group, , as 3335 delegated by the IESG . 3337 XML: 3339 BEGIN 3340 3341 3343 3344 3345 3347 Namespace for Additional Emergency Call Data 3348 3349 3350

Namespace for Additional Data related to an Emergency Call 3351

3352

See [TBD: This document].

3353 3354 3355 END 3357 10.5.2. Registration for 3358 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3360 This section registers a new XML namespace, as per the guidelines in 3361 RFC 3688 [RFC3688]. 3363 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3365 Registrant Contact: IETF, ECRIT working group, , as 3366 delegated by the IESG . 3368 XML: 3370 BEGIN 3371 3372 3374 3375 3376 3378 Namespace for Additional Emergency Call Data: 3379 Data Provider Information 3380 3381 3382

Namespace for Additional Data related to an Emergency Call 3383

3384

Data Provider Information

3385

See [TBD: This document].

3386 3387 3388 END 3390 10.5.3. Registration for 3391 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3393 This section registers a new XML namespace, as per the guidelines in 3394 RFC 3688 [RFC3688]. 3396 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3398 Registrant Contact: IETF, ECRIT working group, , as 3399 delegated by the IESG . 3401 XML: 3403 BEGIN 3404 3405 3407 3408 3409 3411 Namespace for Additional Emergency Call Data: 3412 Service Information 3413 3414 3415

Namespace for Additional Data related to an Emergency Call 3416

3417

Service Information

3418

See [TBD: This document].

3419 3420 3421 END 3423 10.5.4. Registration for 3424 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3426 This section registers a new XML namespace, as per the guidelines in 3427 RFC 3688 [RFC3688]. 3429 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3431 Registrant Contact: IETF, ECRIT working group, , as 3432 delegated by the IESG . 3434 XML: 3436 BEGIN 3437 3438 3440 3441 3442 3444 Namespace for Additional Emergency Call Data: 3445 Device Information 3446 3447 3448

Namespace for Additional Data related to an Emergency Call 3449

3450

Device Information

3451

See [TBD: This document].

3452 3453 3454 END 3456 10.5.5. Registration for 3457 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3459 This section registers a new XML namespace, as per the guidelines in 3460 RFC 3688 [RFC3688]. 3462 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3464 Registrant Contact: IETF, ECRIT working group, , as 3465 delegated by the IESG . 3467 XML: 3469 BEGIN 3470 3471 3473 3474 3475 3477 Namespace for Additional Emergency Call Data: 3478 Owner/Subscriber Information 3479 3480 3481

Namespace for Additional Data related to an Emergency Call 3482

3483

Owner/Subscriber Information

3484

See [TBD: This document].

3485 3486 3487 END 3489 10.5.6. Registration for 3490 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3492 This section registers a new XML namespace, as per the guidelines in 3493 RFC 3688 [RFC3688]. 3495 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3497 Registrant Contact: IETF, ECRIT working group, , as 3498 delegated by the IESG . 3500 XML: 3502 BEGIN 3503 3504 3506 3507 3508 3510 Namespace for Additional Emergency Call Data:Comment 3511 3512 3513 3514

Namespace for Additional Data related to an Emergency Call 3515

3516

Comment

3517

See [TBD: This document].

3518 3519 3520 END 3522 10.6. Schema Registrations 3524 This specification registers five schemas, as per the guidelines in 3525 RFC 3688 [RFC3688]. 3527 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3529 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3530 delegated by the IESG (iesg@ietf.org). 3532 XML: The XML schema can be found in Figure 15. 3534 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3536 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3537 delegated by the IESG (iesg@ietf.org). 3539 XML: The XML schema can be found in Figure 16. 3541 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3543 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3544 delegated by the IESG (iesg@ietf.org). 3546 XML: The XML schema can be found in Figure 17. 3548 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3549 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3550 delegated by the IESG (iesg@ietf.org). 3552 XML: The XML schema can be found in Section 7.4. 3554 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3556 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3557 delegated by the IESG (iesg@ietf.org). 3559 XML: The XML schema can be found in Section 7.5. 3561 10.7. VCard Parameter Value Registration 3563 This document registers a new value in the vCARD Parameter Values 3564 registry as defined by [RFC6350] with the following template: 3566 Value: main 3568 Purpose: The main telephone number, typically of an enterprise, as 3569 opposed to a direct dial number of an individual employee 3571 Conformance: This value can be used with the "TYPE" parameter 3572 applied on the "TEL" property. 3574 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3575 00 3577 11. Acknowledgments 3579 This work was originally started in NENA and has benefitted from a 3580 large number of participants in NENA standardization efforts, 3581 originally in the Long Term Definition Working Group, the Data 3582 Technical Committee and most recently the Additional Data working 3583 group. The authors are grateful for the initial work and extended 3584 comments provided by many NENA participants, including Delaine 3585 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3586 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3587 and Robert (Bob) Sherry. Amursana Khiyod, Robert Sherry, Frank 3588 Rahoi, Scott Ross, Tom Klepetka provided valuable feedback regarding 3589 the vCard/xCard use in this specification. 3591 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3592 Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris 3593 Santer, and Archie Cobbs for their review comments. Guy Caron 3594 deserves special mention for his detailed and extensive review 3595 comments. 3597 12. References 3599 12.1. Normative References 3601 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3602 Requirement Levels", BCP 14, RFC 2119, March 1997. 3604 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3605 Locators", RFC 2392, August 1998. 3607 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3608 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3609 and QSIG Objects", RFC 3204, December 2001. 3611 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3612 A., Peterson, J., Sparks, R., Handley, M., and E. 3613 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3614 June 2002. 3616 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3617 Extensions (MIME) Parameter", RFC 3459, January 2003. 3619 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3620 January 2004. 3622 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3623 Format", RFC 4119, December 2005. 3625 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3626 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3627 May 2008. 3629 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 3630 October 2008. 3632 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3633 Initiation Protocol (SIP)", RFC 5621, September 2009. 3635 [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying 3636 Languages", BCP 47, RFC 5646, September 2009. 3638 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3639 August 2011. 3641 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3642 6351, August 2011. 3644 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3645 Specifications and Registration Procedures", BCP 13, RFC 3646 6838, January 2013. 3648 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 3649 July 2014. 3651 12.2. Informational References 3653 [I-D.gellens-slim-negotiating-human-language] 3654 Randy, R., "Negotiating Human Language in Real-Time 3655 Communications", draft-gellens-slim-negotiating-human- 3656 language-00 (work in progress), October 2014. 3658 [LanguageTagRegistry] 3659 IANA, "Language Subtag Registry", Feb 2015. 3661 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3662 Extensions to the Session Initiation Protocol (SIP) for 3663 Asserted Identity within Trusted Networks", RFC 3325, 3664 November 2002. 3666 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3667 "Indicating User Agent Capabilities in the Session 3668 Initiation Protocol (SIP)", RFC 3840, August 2004. 3670 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3671 3966, December 2004. 3673 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3674 Emergency Context Resolution with Internet Technologies", 3675 RFC 5012, January 2008. 3677 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3678 Format for Presence Information Data Format Location 3679 Object (PIDF-LO)", RFC 5139, February 2008. 3681 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3682 Presence Information Data Format Location Object (PIDF-LO) 3683 Usage Clarification, Considerations, and Recommendations", 3684 RFC 5491, March 2009. 3686 [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and 3687 Framework", RFC 5582, September 2009. 3689 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3690 Thomson, "Dynamic Extensions to the Presence Information 3691 Data Format Location Object (PIDF-LO)", RFC 5962, 3692 September 2010. 3694 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3695 5985, September 2010. 3697 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3698 "Framework for Emergency Calling Using Internet 3699 Multimedia", RFC 6443, December 2011. 3701 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3702 R. George, "Specifying Civic Address Extensions in the 3703 Presence Information Data Format Location Object (PIDF- 3704 LO)", RFC 6848, January 2013. 3706 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3707 Communications Services in Support of Emergency Calling", 3708 BCP 181, RFC 6881, March 2013. 3710 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3711 Morris, J., Hansen, M., and R. Smith, "Privacy 3712 Considerations for Internet Protocols", RFC 6973, July 3713 2013. 3715 [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3716 Thomson, "Relative Location Representation", RFC 7035, 3717 October 2013. 3719 [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3720 Patel, "Public Safety Answering Point (PSAP) Callback", 3721 RFC 7090, April 2014. 3723 12.3. URIs 3725 [1] http://www.nena.org/?page=cid2014 3727 [2] http://www.nena.org/?page=CompanyID 3729 Appendix A. XML Schema for vCard/xCard 3731 This section contains the vCard/xCard XML schema version of the Relax 3732 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3733 XML schemas defined in this document. The schema in RFC 6351 3734 [RFC6351] is the normative source and this section is informative 3735 only. 3737 3738 3742 3748 3749 3750 vCard Format Specification 3751 3752 3753 3754 3755 3756 3757 3758 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3773 3774 3775 3777 3778 3779 3780 3781 3783 3784 3785 3787 3788 3789 3790 3791 3793 3794 3795 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3840 3841 3842 3843 3847 3848 3849 Section 5: Parameters 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 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 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 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 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 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 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 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 4245 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 4294 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 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 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 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4678 4679 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 4739 4740 4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753 4754 4755 4756 4757 4758 4759 4760 4761 4762 4763 4764 4765 4766 4767 4768 4769 4770 4771 4772 4773 4774 4775 4777 4778 4779 4780 4781 4782 4783 4785 4786 4787 4788 4789 4790 4791 4793 4794 4795 4797 4799 4800 4801 4803 4804 4805 4806 4808 Authors' Addresses 4810 Randall Gellens 4811 Qualcomm Technologies, Inc. 4812 5775 Morehouse Drive 4813 San Diego, CA 92121 4814 US 4816 Email: rg+ietf@qti.qualcomm.com 4818 Brian Rosen 4819 NeuStar 4820 470 Conrad Dr. 4821 Mars, PA 16046 4822 US 4824 Phone: +1 724 382 1051 4825 Email: br@brianrosen.net 4827 Hannes Tschofenig 4828 Hall in Tirol 6060 4829 Austria 4831 Email: Hannes.tschofenig@gmx.net 4832 URI: http://www.tschofenig.priv.at 4834 Roger Marshall 4835 TeleCommunication Systems, Inc. 4836 2401 Elliott Avenue 4837 Seattle, WA 98121 4838 US 4840 Phone: +1 206 792 2424 4841 Email: rmarshall@telecomsys.com 4842 URI: http://www.telecomsys.com 4843 James Winterbottom 4844 AU 4846 Email: a.james.winterbottom@gmail.com