idnits 2.17.00 (12 Aug 2021) /tmp/idnits31281/draft-ietf-ecrit-additional-data-23.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 58 instances of too long lines in the document, the longest one being 18 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 2349 has weird spacing: '...element name=...' == Line 2960 has weird spacing: '...ll-Info pur...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (October 02, 2014) is 2787 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 404 -- Looks like a reference, but probably isn't: '2' on line 405 == Missing Reference: 'This RFC' is mentioned on line 2960, but not defined == Unused Reference: 'RFC2045' is defined on line 3496, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ecrit-psap-callback' is defined on line 3559, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: draft-ietf-ecrit-psap-callback has been published as RFC 7090 Summary: 3 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track H. Tschofenig 5 Expires: April 5, 2015 (no affiliation) 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 11 (no affiliation) 12 October 02, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-23.txt 17 Abstract 19 When an emergency call is sent to a Public Safety Answering Point 20 (PSAP), the device that sends it, as well as any application service 21 provider in the path of the call, or access network provider through 22 which the call originated may have information about the call, the 23 caller or the location which the PSAP may be able to use. This 24 document describes data structures and a mechanism to convey such 25 data to the PSAP. The mechanism uses a Uniform Resource Identifier 26 (URI), which may point to either an external resource or an object in 27 the body of the SIP message. The mechanism thus allows the data to 28 be passed by reference (when the URI points to an external resource) 29 or by value (when it points into the body of the message). This 30 follows the tradition of prior emergency services standardization 31 work where data can be conveyed by value within the call signaling 32 (i.e., in body of the SIP message) and also by reference. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on April 5, 2015. 50 Copyright Notice 52 Copyright (c) 2014 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 70 4. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7 71 4.1. Data Provider Information . . . . . . . . . . . . . . . . 8 72 4.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 73 4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9 74 4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9 75 4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 10 76 4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 11 77 4.1.6. Data Provider Languages(s) Supported . . . . . . . . 11 78 4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 12 79 4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12 80 4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13 81 4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13 82 4.2. Service Information . . . . . . . . . . . . . . . . . . . 16 83 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16 84 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16 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 . . . . . . . . . . . . . . . . . 21 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 . . . . . . . . . . . . . . . . . . . . . . . . 23 95 4.3.7. Issues with getting new types of data into use . . . 24 96 4.3.8. Choosing between defining a new type of block or new 97 type of device/service specific additional data . . . 25 98 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 25 99 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26 100 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26 101 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27 102 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27 103 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29 104 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 29 105 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30 106 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30 107 5.1. Transmitting Blocks using the Call-Info Header . . . . . 32 108 5.2. Transmitting Blocks by Reference using the Provided-By 109 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 110 5.3. Transmitting Blocks by Value using the Provided-By 111 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 112 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 34 113 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36 114 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 47 115 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 47 116 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 49 117 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 49 118 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 51 119 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 51 120 7.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 52 121 8. Security Considerations . . . . . . . . . . . . . . . . . . . 54 122 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 56 123 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59 124 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 59 125 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 59 126 10.1.2. Service Environment Registry . . . . . . . . . . . . 60 127 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 60 128 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 61 129 10.1.5. Service Provider Type Registry . . . . . . . . . . . 61 130 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 62 131 10.1.7. Device Classification Registry . . . . . . . . . . . 62 132 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 63 133 10.1.9. Device/Service Data Type Registry . . . . . . . . . 63 134 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 63 135 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 64 136 10.3. URN Sub-Namespace Registration for provided-by Registry 137 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 65 138 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 65 139 10.4.1. MIME Content-type Registration for 140 'application/EmergencyCallData.ProviderInfo+xml' . . 65 141 10.4.2. MIME Content-type Registration for 142 'application/EmergencyCallData.ServiceInfo+xml' . . 66 143 10.4.3. MIME Content-type Registration for 144 'application/EmergencyCallData.DeviceInfo+xml' . . . 67 145 10.4.4. MIME Content-type Registration for 146 'application/EmergencyCallData.SubscriberInfo+xml' . 68 147 10.4.5. MIME Content-type Registration for 148 'application/EmergencyCallData.Comment+xml' . . . . 69 149 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 71 150 10.5.1. Registration for 151 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 71 152 10.5.2. Registration for 153 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf 154 o . . . . . . . . . . . . . . . . . . . . . . . . . 71 155 10.5.3. Registration for 156 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 72 157 10.5.4. Registration for 158 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 73 159 10.5.5. Registration for 160 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI 161 nfo . . . . . . . . . . . . . . . . . . . . . . . . 73 162 10.5.6. Registration for 163 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 74 164 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 75 165 10.7. VCard Parameter Value Registration . . . . . . . . . . . 76 166 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 76 167 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 76 168 12.1. Normative References . . . . . . . . . . . . . . . . . . 76 169 12.2. Informational References . . . . . . . . . . . . . . . . 77 170 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 79 171 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 101 173 1. Introduction 175 When an IP-based emergency call is initiated, a rich set of data from 176 multiple data sources is conveyed to the Public Safety Answering 177 Point (PSAP). This data includes information about the calling party 178 identity, the multimedia capabilities of the device, the request for 179 emergency services, location information, and meta-data about the 180 sources of the data. The device, the access network provider, and 181 any service provider in the call path may have even more information 182 useful for a PSAP. This document extends the basic set of data 183 communicated with an IP-based emergency call, as described in 184 [RFC6443] and [RFC6881], in order to carry additional data which may 185 be useful to an entity or call taker handling the call. This data is 186 "additional" to the basic information found in the emergency call 187 signaling used. 189 In general, there are three categories of this additional data that 190 may be transmitted with an emergency call: 192 Data Associated with a Location: Primary location data is conveyed 193 in the Presence Information Data Format Location Object (PIDF-LO) 194 data structure as defined in RFC 4119 [RFC4119] and extended by 195 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 196 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 197 geodetic location information), and [RFC7035] (for relative 198 location). This primary location data identifies the location or 199 estimated location of the caller. However, there may exist 200 additional, secondary data which is specific to the location, such 201 as floor plans, tenant and building owner contact data, heating, 202 ventilation and air conditioning (HVAC) status, etc. Such 203 secondary location data is not included in the location data 204 structure but can be transmitted using the mechanisms defined in 205 this document. Although this document does not define any 206 structures for such data, future documents may do so following the 207 procedures defined here. 209 Data Associated with a Call: While some information is carried in 210 the call setup procedure itself (as part of the SIP headers as 211 well as in the body of the SIP message), there is additional data 212 known by the device making the call and/or a service provider 213 along the path of the call. This information may include the 214 service provider contact information, subscriber identity and 215 contact information, the type of service the service provider and 216 the access network provider offer, what type of device is being 217 used, etc. Some data is broadly applicable, while other data is 218 dependent on the type of device or service. For example, a 219 medical monitoring device may have sensor data. The data 220 structures defined in this document (Data Provider Information, 221 Device Information, and Owner/Subscriber Information) all fall 222 into the category of "Data Associated with a Call". 224 Data Associated with a Caller: This is personal data about a caller, 225 such as medical information and emergency contact data. Although 226 this document does not define any structures within this category, 227 future documents may do so following the procedures defined here. 229 While this document defines data structures only within the category 230 of Data Associated with a Call, by establishing the overall framework 231 of Additional Data, along with general mechanisms for transport of 232 such data, extension points and procedures for future extensions, it 233 minimizes the work needed to carry data in the other categories. 234 Other specifications may make use of the facilities provided here. 236 For interoperability, there needs to be a common way for the 237 information conveyed to a PSAP to be encoded and identified. 238 Identification allows emergency services authorities to know during 239 call processing which types of data are present and to determine if 240 they wish to access it. A common encoding allows the data to be 241 successfully accessed. 243 This document defines an extensible set of data structures, and 244 mechanisms to transmit this data either by value or by reference, 245 either in the Session Initiation Protocol (SIP) call signaling or in 246 the Presence Information Data Format Location Object (PIDF-LO). The 247 data structures are usable by other communication systems and 248 transports as well. The data structures are defined in Section 4, 249 and the transport mechanisms (using SIP and HTTPS) are defined in 250 Section 5. 252 Each data structure described in this document is encoded as a 253 "block" of information. Each block is an XML structure with an 254 associated Multipurpose Internet Mail Extensions (MIME) type for 255 identification within transport such as SIP and HTTPS. The set of 256 blocks is extensible. Registries are defined to identify the block 257 types that may be used and to allow blocks to be included in 258 emergency call signaling. 260 2. Terminology 262 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 263 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 264 document are to be interpreted as described in RFC 2119 [RFC2119]. 266 This document also uses terminology from [RFC5012]. We use the term 267 service provider to refer to an Application Service Provider (ASP). 268 A Voice Service Provider (VSP) is a special type of ASP. With the 269 term "Access Network Provider" we refer to the Internet Access 270 Provider (IAP) and the Internet Service Provider (ISP) without 271 further distinguishing these two entities, since the difference 272 between the two is not relevant for this document. Note that the 273 roles of ASP and access network provider may be provided by a single 274 company. An Emergency Services Provider is an entity directly 275 involved in providing emergency services. This includes PSAPs, 276 dispatch, police, fire, emergency medical, other responders, and 277 other similar agencies. 279 Within each data block definition (see Section 4), the values for the 280 "Use:" label are specified as one of the following: 282 'Required': means it MUST be present in the data structure. 284 'Conditional': means it MUST be present if the specified 285 condition(s) is met. It MAY be present if the condition(s) is not 286 met. 288 'Optional': means it MAY be present. 290 vCard is a data format for representing and exchanging a variety of 291 information about individuals and other entities. For applications 292 that use XML the format defined in vCard is not immediately 293 applicable. For this purpose an XML-based encoding of the 294 information elements defined in the vCard specification has been 295 defined and the name of that specification is xCard. Since the term 296 vCard is more familiar to most readers, we use the term xCard and 297 vCard interchangeably. 299 3. Document Scope 301 The scope of this document is explicitly limited to emergency calls. 302 The data structures defined here are not appropriate to be conveyed 303 with non-emergency calls because they carry sensitive and private 304 data. 306 4. Data Structures 308 This section defines the following five data structures, each as a 309 data block. For each block we define the MIME type, and the XML 310 encoding. The five data structures are: 312 'Data Provider': This block supplies name and contact information 313 for the entity that created the data. Section 4.1 provides the 314 details. 316 'Service Information': This block supplies information about the 317 service. The description can be found in Section 4.2. 319 'Device Information': This block supplies information about the 320 device placing the call. Device information can be found in 321 Section 4.3. 323 'Owner/Subscriber': This block supplies information about the owner 324 of the device or about the subscriber. Details can be found in 325 Section 4.4. 327 'Comment': This block provides a way to supply free form human 328 readable text to the PSAP or emergency responders. This simple 329 structure is defined in Section 4.5. 331 Each block contains a mandatory element. The 332 purpose of the element is to associate all 333 blocks added by the same data provider as a unit. The 334 element associates the data provider block to 335 each of the other blocks added as a unit. Consequently, when a data 336 provider adds additional data to an emergency call (such as device 337 information) it MUST add information about itself (via the data 338 provider block) and the blocks added contain the same value in the 339 element. All blocks added by a single entity 340 at the same time MUST have the same value. 341 The value of the element has the same syntax 342 and properties (specifically, world-uniqueness) as the value of the 343 "Message-ID" message body header field specified in RFC 5322 344 [RFC5322] except that the element is not 345 enclosed in brackets (the "<" and ">" symbols are omitted). In other 346 words, the value of a element is 347 syntactically a msg-id as specified in RFC 5322 [RFC5322]. 349 Note that the xCard format is re-used in some of the data structures 350 to provide contact information. In an xCard there is no way to 351 specify a "main" telephone number. These numbers are useful to 352 emergency responders who are called to a large enterprise. This 353 document adds a new property value to the "tel" property of the TYPE 354 parameter called "main". It can be used in any xCard in additional 355 data. 357 4.1. Data Provider Information 359 This block is intended to be supplied by any service provider in the 360 path of the call or the access network provider. It includes 361 identification and contact information. This block SHOULD be 362 supplied by every service provider in the call path, and by the 363 access network provider. Devices MAY use this block to provide 364 identifying information. The MIME subtype is "application/ 365 EmergencyCallData.ProviderInfo+xml". An access network provider 366 SHOULD provide this block either by value or by reference in the 367 Provided-By section of a PIDF-LO 369 4.1.1. Data Provider String 371 Data Element: Data Provider String 373 Use: Required 375 XML Element: 377 Description: This is a plain text string suitable for displaying the 378 name of the service provider that supplied the data structure. If 379 the device creates the structure, it SHOULD use the value of the 380 contact header in the SIP INVITE. 382 Reason for Need: Inform the call taker of the identity of the entity 383 providing the data. 385 How Used by Call Taker: Allows the call taker to interpret the data 386 in this structure. The source of the information often influences 387 how the information is used, believed or verified. 389 4.1.2. Data Provider ID 391 Data Element: Data Provider ID 393 Use: Required. This data MUST be provided in order to uniquely 394 identify the service provider or access provider. 396 XML Element: 398 Description: A jurisdiction-specific code for, or the fully- 399 qualified domain name of, the access network provider or service 400 provider shown in the element that created the 401 structure. NOTE: The value SHOULD be assigned by an organization 402 appropriate for the jurisdiction. In the U.S., the provider's 403 NENA Company ID MUST appear here. Additional information can be 404 found at NENA Company Identifier Program [1] or NENA Company ID 405 [2]. The NENA Company ID MUST be in the form of a URI in the 406 following format: urn:nena:companyid:. The value 407 MAY be the fully-qualified domain name of the service provider or 408 access provider. 410 Reason for Need: Inform the call taker of the identity of the entity 411 providing the data. 413 How Used by Call Taker: Where jurisdictions have lists of providers 414 the Data Provider ID provides useful information about the data 415 source. The Data Provider ID uniquely identifies the source of 416 the data, which might be needed especially during unusual 417 circumstances and for routine logging. 419 4.1.3. Data Provider ID Series 421 Data Element: Data Provider ID Series 423 Use: Required. 425 XML Element: 427 Description: Identifies the issuer of the . The 428 Provider ID Series Registry (see Section 10.1) initially contains 429 the following valid entries: 431 * NENA 432 * EENA 434 * domain 436 Reason for Need: Identifies how to interpret the Data Provider ID. 437 The combination of ProviderIDSeries and ProviderID MUST be 438 globally unique. 440 How Used by Call Taker: Determines which provider ID registry to 441 consult for more information 443 4.1.4. Type of Data Provider 445 Data Element: Type of Data Provider 447 Use: Required. 449 XML Element: 451 Description: Identifies the type of data provider supplying the 452 data. A registry with an initial set of values is shown in Figure 453 1 (see also Section 10.1). 455 +------------------------------+------------------------------------+ 456 | Token | Description | 457 +------------------------------+------------------------------------+ 458 |Access Network Provider | Access network service provider | 459 |Telecom Provider | Calling or origination telecom SP | 460 |Telematics Provider | A sensor based service provider, | 461 | | especially vehicle based | 462 |Language Translation Provider | A spoken language translation SP | 463 |Emergency Service Provider | An emergency service provider | 464 | | conveying information to another| 465 | | emergency service provider. | 466 |Emergency Modality Translation| An emergency call specific | 467 | | modality translation service | 468 | | e.g., for sign language | 469 |Relay Provider | A interpretation SP, for example, | 470 | | video relay for sign language | 471 | | interpreting | 472 |Other | Any other type of service provider | 473 +------------------------------+------------------------------------+ 475 Figure 1: Type of Data Provider Registry. 477 Reason for Need: Identifies the category of data provider. 479 How Used by Call Taker: This information may be helpful when 480 deciding whom to contact when further information is needed. 482 4.1.5. Data Provider Contact URI 484 Data Element: Data Provider Contact URI 486 Use: Required 488 XML Element: 490 Description: When provided by a service provider or an access 491 network provider, this information MUST be a URI to a 24/7 support 492 organization tasked to provide PSAP support for this emergency 493 call. If the call is from a device, this SHOULD be the contact 494 information of the owner of the device. The Data Provider Contact 495 URI SHOULD be a TEL URI [RFC3966] in E.164 format fully specified 496 with country code. If a TEL URI is not available, it MAY be a 497 generic SIP URI. Note that this contact information is not used 498 by PSAPs for callbacks (a call from a PSAP directly related to a 499 recently terminated emergency call, placed by the PSAP using a SIP 500 Priority header field set to "psap-callback", as described in 501 [RFC7090]). 503 Reason for Need: Additional data providers may need to be contacted 504 in error cases or other unusual circumstances. 506 How Used by Call Taker: To contact the supplier of the additional 507 data for assistance in handling the call. 509 4.1.6. Data Provider Languages(s) Supported 511 Data Element: Data Provider Language(s) supported 513 Use: Required. 515 XML Element: 517 Description: The language used by the entity at the Data Provider 518 Contact URI, as an alpha 2-character code as defined in ISO 519 639-1:2002 Codes for the representation of names of languages -- 520 Part 1: Alpha-2 code Multiple instances of this element may occur. 521 Order is significant; preferred language should appear first. The 522 content MUST reflect the languages supported at the contact URI. 524 Note that the 'language' media feature tag, defined in RFC 3840 525 [RFC3840] and the more extensive language negotiation mechanism 526 proposed with [I-D.gellens-mmusic-negotiating-human-language] are 527 independent of this data provider language indication. 529 Reason for Need: This information indicates if the emergency service 530 authority can directly communicate with the service provider or if 531 an interpreter will be needed. 533 How Used by Call Taker: If the call taker cannot speak any language 534 supported by the service provider, a translation service will need 535 to be added to the conversation. Alternatively, other persons at 536 the PSAP, besides the call taker, might be consulted for help 537 (depending on the urgency and the type of interaction). 539 4.1.7. xCard of Data Provider 541 Data Element: xCard of Data Provider 543 Use: Optional 545 XML Element: 547 Description: There are many fields in the xCard and the creator of 548 the data structure is encouraged to provide as much information as 549 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 550 minimum. N SHOULD contain the name of the support group or device 551 owner as appropriate. If more than one TEL property is provided, 552 a parameter from the vCard Property Value registry MUST be 553 specified on each TEL. For encoding of the xCard this 554 specification uses the XML-based encoding specified in [RFC6351], 555 referred to in this document as "xCard" 557 Reason for Need: Information needed to determine additional contact 558 information. 560 How Used by Call Taker: Assists the call taker by providing 561 additional contact information aside from what may be included in 562 the SIP INVITE or the PIDF-LO. 564 4.1.8. Subcontractor Principal 566 When the entity providing the data is a subcontractor, the Data 567 Provider Type is set to that of the primary service provider and this 568 entry is supplied to provide information regarding the subcontracting 569 entity. 571 Data Element: Subcontractor Principal 572 Use: Conditional. This data is required if the entity providing the 573 data is a subcontractor. 575 XML Element: 577 Description: Some providers outsource their obligations to handle 578 aspects of emergency services to specialized providers. If the 579 data provider is a subcontractor to another provider this element 580 contains the DataProviderString of the service provider to 581 indicate which provider the subcontractor is working for. 583 Reason for Need: Identify the entity the subcontractor works for. 585 How Used by Call Taker: Allows the call taker to understand what the 586 relationship between data providers and the service providers in 587 the path of the call are. 589 4.1.9. Subcontractor Priority 591 Data Element: Subcontractor Priority 593 Use: Conditional. This element is required if the Data Provider 594 type is set to "Subcontractor". 596 XML Element: 598 Description: If the subcontractor has to be contacted first then 599 this element MUST have the value "sub". If the provider the 600 subcontractor is working for has to be contacted first then this 601 element MUST have the value "main". 603 Reason for Need: Inform the call taker whom to contact first, if 604 support is needed. 606 How Used by Call Taker: To decide which entity to contact first if 607 assistance is needed. 609 4.1.10. ProviderInfo Example 611 612 615 12345 616 string0987654321@example.org 617 618 Example VoIP Provider 619 620 urn:nena:companyid:ID123 621 NENA 622 Telecom Provider 623 tel:+1-201-555-0123 624 EN 625 627 628 Hannes Tschofenig 629 630 Hannes 631 Tschofenig 632 633 634 Dipl. Ing. 635 636 --0203 637 638 20090808T1430-0500 639 640 M 641 642 1 643 644 de 645 646 647 2 648 649 en 650 651 652 work 653 654 Example VoIP Provider 655 656 657 658 work 659 663 664 665 666 Linnoitustie 6 667 Espoo 668 Uusimaa 669 02600 670 Finland 671 672 673 674 675 work 676 voice 677 678 679 tel:+358 50 4871445 680 681 682 work 683 684 hannes.tschofenig@nsn.com 685 686 687 work 688 689 geo:60.210796,24.812924 690 691 692 home 693 694 695 http://www.tschofenig.priv.at/key.asc 696 697 698 Finland/Helsinki 699 700 home 701 702 http://www.tschofenig.priv.at 703 704 705 706 708 Figure 2: EmergencyCallData.ProviderInfo Example. 710 4.2. Service Information 712 This block describes the service that the service provider provides 713 to the caller. It SHOULD be included by all SPs in the path of the 714 call. The mime subtype is "application/ 715 EmergencyCallData.ServiceInfo+xml". 717 4.2.1. Service Environment 719 Data Element: Service Environment 721 Use: Optional when a 'ServiceType' value is 'wireless'; required 722 otherwise. 724 XML Element: 726 Description: This element defines whether a call is from a business 727 or residence caller. Currently, the only valid entries are 728 'Business', 'Residence', and 'unknown'. New values can be defined 729 via the registry created in Figure 22. 731 Reason for Need: To provide context and a hint when determining 732 equipment and manpower requirements. 734 How Used by Call Taker: Information may be used to provide context 735 and a hint to assist in determining equipment and manpower 736 requirements for emergency responders. Because there are cases 737 where the service provider does not know (such as anonymous pre- 738 paid service), and the type of service does not neccessarily 739 reflect the nature of the premises (for example, a business line 740 installed in a residence, or wireless service), and the registry 741 is not all encompassing, therefore this is at best advisory 742 information, but since it mimics a similar capability in some 743 current emergency calling systems (e.g., a field in the Automatic 744 Location Information (ALI) information used with legacy North 745 American wireline systems), it is known to be valuable. The 746 service provider uses its best information (such as a rate plan, 747 facilities used to deliver service or service description) to 748 determine the information and is not responsible for determining 749 the actual characteristics of the location from which the call 750 originated. Because the usefulness is unknown (and less clear) 751 for wireless, this element is OPTIONAL for wireless and REQUIRED 752 otherwise. 754 4.2.2. Service Type 756 Data Element: Service Delivered by Provider to End User 757 Use: Required 759 XML Element: 761 Description: This defines the type of service over which the call is 762 placed. The implied mobility of this service cannot be relied 763 upon. A registry with an initial set of values is defined in 764 Figure 3. 766 +--------------+----------------------------------------+ 767 | Name | Description | 768 +--------------+----------------------------------------+ 769 | wireless | Wireless Telephone Service: Includes | 770 | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | 771 | | not satellite) | 772 | coin | Fixed public pay/coin telephones: Any | 773 | | coin or credit card operated device | 774 | one-way | One way outbound service | 775 | prison | Inmate call/service | 776 | temp | Soft dial tone/quick service/warm | 777 | | disconnect/suspended | 778 | MLTS-hosted | Hosted multi-line telephone system | 779 | | such as Centrex | 780 | MLTS-local | Local multi-line telephone system, | 781 | | includes all PBX, key systems, | 782 | | Shared Tenant Service | 783 | sensor- | 784 | unattended | These are devices that generate DATA | 785 | | ONLY. This is a one-way information | 786 | | transmit without interactive media | 787 | sensor- | | 788 | attended | Devices that are supported by a | 789 | | monitoring service provider or that | 790 | | are capable of supporting interactive| 791 | | media | 792 | POTS | Wireline: Plain Old Telephone Service | 793 | VOIP | An over-the-top service that provides | 794 | | communication over arbitrary Internet| 795 | | access (fixed, nomadic, mobile) | 796 | remote | Off premise extension | 797 | relay | A service where there is a human third | 798 | | party agent who provides additional | 799 | | assistance. This includes sign | 800 | | language relay and telematics | 801 | | services that provide a human on the | 802 | | call. | 803 +--------------+----------------------------------------+ 805 Figure 3: Service Delivered by Provider to End User Registry. 807 More than one value MAY be returned. For example, a VoIP inmate 808 telephone service is a reasonable combination. 810 Reason for Need: Knowing the type of service may assist the PSAP 811 with the handling of the call. 813 How Used by Call Taker: Call takers often use this information to 814 determine what kinds of questions to ask callers, and how much to 815 rely on supportive information. An emergency call from a prison 816 is treated differently than a call from a sensor device. As the 817 information is not always available, and the registry is not all 818 encompassing, this is at best advisory information, but since it 819 mimics a similar capability in some current emergency calling 820 systems, it is known to be valuable. 822 4.2.3. Service Mobility Environment 824 Data Element: Service Mobility Environment 826 Use: Required 828 XML Element: 830 Description: This provides the service provider's view of the 831 mobility of the caller's device. As the service provider may not 832 know the characteristics of the actual device or access network 833 used, the value MUST NOT be relied upon. The registry specified 834 in Figure 23 reflects the following initial valid entries: 836 * Mobile: the device is able to move at any time 838 * Fixed: the device is not expected to move unless the service is 839 relocated 841 * Nomadic: the device is not expected to change its point of 842 attachment while on a call 844 * Unknown: no information is known about the service mobility 845 environment for the device 847 Reason for Need: Knowing the service provider's belief of mobility 848 may assist the PSAP with the handling of the call. 850 How Used by Call Taker: To determine whether to assume the location 851 of the caller might change. 853 4.2.4. EmergencyCallData.ServiceInfo Example 855 856 859 2468.IBOC.MLTS.1359@example.org 860 861 12345 862 Business 863 MLTS-hosted 864 Fixed 865 867 Figure 4: EmergencyCallData.ServiceInfo Example. 869 4.3. Device Information 871 This block provides information about the device used to place the 872 call. It should be provided by any service provider that knows what 873 device is being used, and by the device itself. The mime subtype is 874 "application/EmergencyCallData.DeviceInfo+xml". 876 4.3.1. Device Classification 878 Data Element: Device Classification 880 Use: Optional 882 XML Element: 884 Description: This data element defines the kind of device making the 885 emergency call. If the device provides the data structure, the 886 device information SHOULD be provided. If the service provider 887 provides the structure and it knows what the device is, the 888 service provider SHOULD provide the device information. Often the 889 carrier does not know what the device is. It is possible to 890 receive two Additional Data Associated with a Call data 891 structures, one created by the device and one created by the 892 service provider. This information describes the device, not how 893 it is being used. This data element defines the kind of device 894 making the emergency call. The registry with the initial set of 895 values is shown in Figure 5. 897 +---------------+----------------------------------------+ 898 | Token | Description | 899 +---------------+----------------------------------------+ 900 |cordless | Cordless handset | 901 |fixed | Fixed phone | 902 |satellite | Satellite phone | 903 |sensor-fixed | Fixed (non mobile) sensor/alarm device | 904 |desktop | Soft client on desktop PC | 905 |laptop | Soft client on laptop type device | 906 |tablet | Soft client on tablet type device | 907 |alarm-monitored| Alarm system | 908 |sensor-mobile | Mobile sensor device | 909 |aircraft | Aircraft telematics device | 910 |automobile | Automobile/cycle/off-road telematics | 911 |truck | Truck/construction telematics | 912 |farm | Farm equipment telematics | 913 |marine | Marine telematics | 914 |personal | Personal telematics device | 915 |feature-phone | Feature- (not smart-) cellular phone | 916 |smart-phone | Smart-phone cellular phone (native) | 917 |smart-phone-app| Soft client app on smart-phone | 918 |unknown-device | Soft client on unknown device type | 919 |game | Gaming console | 920 |text-only | Other text device | 921 |NA | Not Available | 922 +---------------+----------------------------------------+ 924 Figure 5: Device Classification Registry. 926 Reason for Need: The device classification implies the capability of 927 the calling device and assists in identifying the meaning of the 928 emergency call location information that is being presented. For 929 example, does the device require human intervention to initiate a 930 call or is this call the result of programmed instructions? Does 931 the calling device have the ability to update location or 932 condition changes? Is this device interactive or a one-way 933 reporting device? 935 How Used by Call Taker: May provide the call taker context regarding 936 the caller, the capabilities of the calling device or the 937 environment in which the device is being used, and may assist in 938 understanding the location information and capabilities of the 939 calling device. For example, a cordless handset may be outside or 940 next door. 942 4.3.2. Device Manufacturer 944 Data Element: Device Manufacturer 946 Use: Optional 948 XML Element: 950 Description: The plain language name of the manufacturer of the 951 device. 953 Reason for Need: Used by PSAP management for post-mortem 954 investigation/resolution. 956 How Used by Call Taker: Probably not used by the calltaker, but by 957 PSAP management. 959 4.3.3. Device Model Number 961 Data Element: Device Model Number 963 Use: Optional 965 XML Element: 967 Description: Model number of the device. 969 Reason for Need: Used by PSAP management for after action 970 investigation/resolution. 972 How Used by Call Taker: Probably not used by the calltaker, but by 973 PSAP management. 975 4.3.4. Unique Device Identifier 977 Data Element: Unique Device Identifier 979 Use: Optional 981 XML Element: 983 XML Attribute: 985 Description: A string that identifies the specific device (or the 986 device's current SIM) making the call or creating an event. Note 987 that more than one may be present, to supply more 988 than one of the identifying values. 990 The attribute identifies the type of device 991 identifier. A registry with an initial set of values can be seen 992 in Figure 6. 994 +--------+------------------------------------------+ 995 | Token | Description | 996 +--------+------------------------------------------+ 997 | MEID | Mobile Equipment Identifier (CDMA) | 998 | ESN | Electronic Serial Number (GSM) | 999 | MAC | Media Access Control Address (IEEE) | 1000 | WiMAX | Device Certificate Unique ID | 1001 | IMEI | International Mobile Equipment ID (GSM) | 1002 | IMSI | International Mobile Subscriber ID (GSM) | 1003 | UDI | Unique Device Identifier | 1004 | RFID | Radio Frequency Identification | 1005 | SN | Manufacturer Serial Number | 1006 +--------+------------------------------------------+ 1008 Figure 6: Registry with Device Identifier Types. 1010 Reason for Need: Uniquely identifies the device (or, in the case of 1011 IMSI, a SIM), independent of any signaling identifiers present in 1012 the call signaling stream. 1014 How Used by Call Taker: Probably not used by the call taker; may be 1015 used by PSAP management during an investigation. 1017 Example: 12345 1019 4.3.5. Device/Service Specific Additional Data Structure 1021 Data Element: Device/service specific additional data structure 1023 Use: Optional 1025 XML Element: 1027 Description: A URI representing additional data whose schema is 1028 specific to the device or service which created it. (For example, 1029 a medical device or medical device monitoring service may have a 1030 defined set of medical data). The URI, when dereferenced, MUST 1031 yield a data structure defined by the Device/service specific 1032 additional data type value. Different data may be created by each 1033 classification; e.g., a medical device created data set. 1035 Reason for Need: Provides device/service specific data that may be 1036 used by the call taker and/or responders. 1038 How Used by Call Taker: Provide information to guide call takers to 1039 select appropriate responders, give appropriate pre-arrival 1040 instructions to callers, and advise responders of what to be 1041 prepared for. May be used by responders to guide assistance 1042 provided. 1044 4.3.6. Device/Service Specific Additional Data Structure Type 1046 Data Element: Type of device/service specific additional data 1047 structure 1049 Use: Conditional. MUST be provided when device/service specific 1050 additional URI is provided 1052 XML Element: 1054 Description: Value from a registry defined by this document to 1055 describe the type of data that can be retrieved from the device/ 1056 service specific additional data structure. Initial values are: 1058 * IEEE 1512 1060 IEEE 1512 is the USDoT model for traffic incidents. 1062 Reason for Need: This data element allows identification of 1063 externally defined schemas, which may have additional data that 1064 may assist in emergency response. 1066 How Used by Call Taker: This data element allows the end user 1067 (calltaker or first responder) to know what type of additional 1068 data may be available to aid in providing the needed emergency 1069 services. 1071 Note: Information which is specific to a location or a caller 1072 (person) should not be placed in this section. 1074 4.3.7. Issues with getting new types of data into use 1076 This document describes two mechanisms which allow extension of the 1077 kind of data provided with an emergency call: define a new block or 1078 define a new service specific additional data URL for the DeviceInfo 1079 block. While defining new data types and getting a new device or 1080 application to send the new data may be easy, getting PSAPs and 1081 responders to actually retrieve the data and use it will be 1082 difficult. New mechanism providers should understand that acquiring 1083 and using new forms of data usually require software upgrades at the 1084 PSAP and/or responders, as well as training of call takers and 1085 responders in how to interpret and use the information. Legal and 1086 operational review may also be needed. Overwhelming a call taker or 1087 responder with too much information is highly discouraged. Thus, the 1088 barrier to supporting new data is quite high. 1090 The mechanisms this document describes are meant to encourage 1091 development of widely supported, common data formats for classes of 1092 devices. If all manufacturers of a class of device use the same 1093 format, and the data can be shown to improve outcomes, then PSAPs and 1094 responders may be encouraged to upgrade their systems and train their 1095 staff to use the data. Variations, however well intentioned, are 1096 unlikely to be supported. 1098 Implementers should consider that data from sensor-based devices in 1099 some cases may not be useful to call takers or PSAPs (and privacy or 1100 other considerations may preclude the PSAP from touching the data), 1101 but may be of use to responders. Some standards being developed by 1102 other organizations to carry data from the PSAP to responders are 1103 designed to carry all additional data supplied in the call that 1104 conform to this document, even if the PSAP does not fetch or 1105 interpret the data. This allows responders to get the data even if 1106 the PSAP does not. 1108 4.3.8. Choosing between defining a new type of block or new type of 1109 device/service specific additional data 1111 For devices that have device or service specific data, there are two 1112 choices to carry it. A new block can be defined, or the device/ 1113 service specific additional data URL the DeviceInfo block can be used 1114 and a new type for it defined . The data passed would likely be the 1115 same in both cases. Considerations for choosing which mechanism to 1116 register under include: 1118 Applicability: Information which will be carried by many kinds of 1119 devices or services are more appropriately defined as separate 1120 blocks. 1122 Privacy: Information which may contain private data may be better 1123 sent in the DeviceInfo block, rather than a new block so that 1124 implementations are not tempted to send the data by value, and 1125 thus having more exposure to the data than forcing the data to be 1126 retrieved via the URL in DeviceInfo. 1128 Size: Information which may be very large may be better sent in the 1129 DeviceInfo block, rather than a new block so that implementations 1130 are not tempted to send the data by value. Conversely, data which 1131 is small may best be sent in a separate block so that it can be 1132 sent by value 1134 Availability of a server: Providing the data via the device block 1135 requires a server be made available to retrieve the data. 1136 Providing the data via new block allows it to be sent by value 1137 (CID). 1139 4.3.9. EmergencyCallData.DeviceInfo Example 1141 1142 1145 d4b3072df.201409182208075@example.org 1146 1147 12345 1148 fixed 1149 Nokia 1150 Lumia 800 1151 35788104 1152 1153 1155 Figure 7: EmergencyCallData.DeviceInfo Example. 1157 4.4. Owner/Subscriber Information 1159 This block describes the owner of the device (if provided by the 1160 device) or the subscriber information (if provided by a service 1161 provider). The contact location is not necessarily the location of 1162 the caller or incident, but is rather the nominal contact address. 1163 The MIME type is "application/EmergencyCallData.SubscriberInfo+xml". 1165 In some jurisdictions some or all parts of the subscriber-specific 1166 information are subject to privacy constraints. These constraints 1167 vary but dictate what information can be displayed and logged. A 1168 general privacy indicator expressing a desire for privacy is 1169 provided. The interpretation of how this is applied is left to the 1170 receiving jurisdiction as the custodians of the local regulatory 1171 requirements. 1173 4.4.1. Subscriber Data Privacy Indicator 1175 Attribute: privacyRequested, boolean. 1177 Use: Conditional. This attribute MUST be provided if the owner/ 1178 subscriber information block is not empty. 1180 Description: The subscriber data privacy indicator specifically 1181 expresses the subscriber's desire for privacy. In some 1182 jurisdictions subscriber services can have a specific "Type of 1183 Service" which prohibits information, such as the name of the 1184 subscriber, from being displayed. This attribute should be used 1185 to explicitly indicate whether the subscriber service includes 1186 such constraints. 1188 Reason for Need: Some jurisdictions require subscriber privacy to be 1189 observed when processing emergency calls. 1191 How Used by Call Taker: Where privacy is indicated the call taker 1192 may not have access to some aspects of the subscriber information. 1194 4.4.2. xCard for Subscriber's Data 1196 Data Element: xCARD for Subscriber's Data 1198 Use: Conditional. Subscriber data is provided unless it is not 1199 available. Some services, for example prepaid phones, non- 1200 initialized phones, etc., do not have information about the 1201 subscriber. 1203 XML Element: 1205 Description: Information known by the service provider or device 1206 about the subscriber; e.g., Name, Address, Individual Telephone 1207 Number, Main Telephone Number and any other data. N, ORG (if 1208 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1209 than one TEL property is provided, a parameter from the vCard 1210 Property Value registry MUST be specified on each TEL. 1212 Reason for Need: When the caller is unable to provide information, 1213 this data may be used to obtain it 1215 How Used by Call Taker: Obtaining critical information about the 1216 caller and possibly the location when it is not able to be 1217 obtained otherwise. 1219 4.4.3. EmergencyCallData.SubscriberInfo Example 1221 1222 1226 FEABFECD901@example.org 1227 1228 1229 1230 1231 Simon Perreault 1232 1233 Perreault 1234 Simon 1235 1236 1237 ing. jr 1238 M.Sc. 1239 1240 --0203 1241 1242 20090808T1430-0500 1243 1244 M 1245 1246 1 1247 1248 fr 1249 1250 1251 2 1252 1253 en 1254 1255 1256 work 1257 1258 Viagenie 1259 1260 1261 1262 work 1263 1267 1268 1269 1270 2875 boul. Laurier, suite D2-630 1271 Quebec 1272 QC 1273 G1V 2M2 1274 Canada 1275 1276 1277 1278 1279 work 1280 voice 1281 1282 1283 tel:+1-418-656-9254;ext=102 1284 1285 1286 1287 1288 work 1289 text 1290 voice 1291 cell 1292 video 1293 1294 1295 tel:+1-418-262-6501 1296 1297 1298 work 1299 1300 simon.perreault@viagenie.ca 1301 1302 1303 work 1304 1305 geo:46.766336,-71.28955 1306 1307 1308 work 1309 1310 1311 http://www.viagenie.ca/simon.perreault/simon.asc 1312 1313 1314 America/Montreal 1315 1316 home 1317 1318 http://nomis80.org 1319 1320 1321 1322 1323 1325 Figure 8: EmergencyCallData.SubscriberInfo Example. 1327 4.5. Comment 1329 This block provides a mechanism for the data provider to supply 1330 extra, human readable information to the PSAP. It is not intended 1331 for a general purpose extension mechanism nor does it aim to provide 1332 machine-readable content. The mime subtype is "application/ 1333 EmergencyCallData.Comment+xml" 1335 4.5.1. Comment 1336 Data Element: EmergencyCallData.Comment 1338 Use: Optional 1340 XML Element: 1342 Description: Human readable text providing additional information to 1343 the PSAP staff. 1345 Reason for Need: Explanatory information for values in the data 1346 structure. 1348 How Used by Call Taker: To interpret the data provided. 1350 4.5.2. EmergencyCallData.Comment Example 1352 1353 1356 string0987654321@example.org 1357 1358 This is an example text. 1359 1361 Figure 9: EmergencyCallData.Comment Example. 1363 5. Data Transport Mechanisms 1365 This section defines how to convey additional data to an emergency 1366 service provider. Two different means are specified: the first uses 1367 the call signaling; the second uses the element of a 1368 PIDF-LO [RFC4119]. 1370 1. First, the ability to embed a Uniform Resource Identifier (URI) 1371 in an existing SIP header field, the Call-Info header, is 1372 defined. The URI points to the additional data structure. The 1373 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1374 document adds a new compound token starting with the value 1375 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1376 the "purpose" parameter is set to a value starting with 1377 'EmergencyCallData', then the Call-Info header contains either an 1378 HTTPS URL pointing to an external resource or a CID (content 1379 indirection) URI that allows the data structure to be placed in 1380 the body of the SIP message. The "purpose" parameter also 1381 indicates the kind of data (by its MIME type) that is available 1382 at the URI. As the data is conveyed using a URI in the SIP 1383 signaling, the data itself may reside on an external resource, or 1384 may be contained within the body of the SIP message. When the 1385 URI refers to data at an external resource, the data is said to 1386 be passed by reference. When the URI refers to data contained 1387 within the body of the SIP message, the data is said to be passed 1388 by value. A PSAP or emergency responder is able to examine the 1389 type of data provided and selectively inspect the data it is 1390 interested in, while forwarding all of it (the values or 1391 references) to downstream entities. To be conveyed in a SIP 1392 body, additional data about a call is defined as a series of MIME 1393 objects. Each block defined in this document is an XML data 1394 structure identified by its MIME type. (Blocks defined by others 1395 may be encoded in XML or not, as identified by their MIME 1396 registration.) As usual, whenever more than one MIME part is 1397 included in the body of a message, MIME-multipart (i.e., 1398 'multipart/mixed') encloses them all. This document defines a 1399 set of XML schemas and MIME types used for each block defined 1400 here. When additional data is passed by value in the SIP 1401 signaling, each CID URL points to one block in the body. 1402 Multiple URIs are used within a Call-Info header field (or 1403 multiple Call-Info header fields) to point to multiple blocks. 1404 When additional data is provided by reference (in SIP signaling 1405 or Provided-By), each HTTPS URL references one block; the data is 1406 retrieved with an HTTPS GET operation, which returns one of the 1407 blocks as an object (the blocks defined here are returned as XML 1408 objects). 1410 2. Second, the ability to embed additional data structures in the 1411 element of a PIDF-LO [RFC4119] is defined. In 1412 addition to service providers in the call path, the access 1413 network provider may also have similar information that may be 1414 valuable to the PSAP. The access network provider MAY provide 1415 location in the form of a PIDF-LO from a location server via a 1416 location configuration protocol. The data structures described 1417 in this document are not specific to the location itself, but 1418 rather provides descriptive information having to do with the 1419 immediate circumstances about the provision of the location (who 1420 the access network is, how to contact that entity, what kind of 1421 service the access network provides, subscriber information, 1422 etc.). This data is similar in nearly every respect to the data 1423 known by service providers in the path of the call. When the 1424 access network provider and service provider are separate 1425 entities, the access network does not participate in the 1426 application layer signaling (and hence cannot add a Call-Info 1427 header field to the SIP message), but may provide location 1428 information in a PIDF-LO object to assist in locating the 1429 caller's device. The element of the PIDF-LO is a 1430 mechanism for the access network provider to supply the 1431 information about the entity or organization that supplied this 1432 location information. For this reason, this document describes a 1433 namespace per RFC 4119 for inclusion in the element 1434 of a PIDF-LO for adding information known to the access network 1435 provider. The access network provider SHOULD provide additional 1436 data within a Provided-By element of a PDIF-LO it returns for 1437 emergency use (e.g., if requested with a HELD "responseTime" 1438 attribute of "emergencyRouting" or "emergencyDispatch" 1439 [RFC5985]). 1441 One or more blocks of data registered in the Emergency Call 1442 Additional Data registry, as defined in Section 10.1, may be included 1443 or referenced in the SIP signaling (using the Call-Info header field) 1444 or in the element of a PIDF-LO. Every block must be 1445 one of the types in the registry. Since the data of an emergency 1446 call may come from multiple sources, the data itself needs 1447 information describing the source. Consequently, each entity adding 1448 additional data MUST supply the "Data Provider" block. All other 1449 blocks are optional, but each entity SHOULD supply any blocks where 1450 it has at least some of the information in the block. 1452 5.1. Transmitting Blocks using the Call-Info Header 1454 A URI to a block MAY be inserted in a SIP request or response method 1455 (most often INVITE or MESSAGE) with a Call-Info header field 1456 containing a purpose value starting with 'EmergencyCallData' and the 1457 type of data available at the URI. The type of data is denoted by 1458 including the root of the MIME type (not including the 1459 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1460 separator. For example, when referencing a block with MIME type 1461 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1462 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1463 "Call-Info" header field for this would be: 1465 Call-Info: https://www.example.com/23sedde3; 1466 purpose="EmergencyCallData.ProviderInfo" 1468 A Call-info header with a purpose value starting with 1469 'EmergencyCallData' MUST only be sent on an emergency call, which can 1470 be ascertained by the presence of an emergency service urn in a Route 1471 header of a SIP message. 1473 If the data is provided by reference, an HTTPS URI MUST be included 1474 and consequently Transport Layer Security (TLS) protection is applied 1475 for protecting the retrieval of the information. 1477 The data may also be supplied by value in a SIP message. In this 1478 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1479 referencing the MIME body part. 1481 More than one Call-Info header with a purpose value starting with 1482 'EmergencyCallData' can be expected, but at least one MUST be 1483 provided. The device MUST provide one if it knows no service 1484 provider is in the path of the call. The device MAY insert one if it 1485 uses a service provider. Any service provider in the path of the 1486 call MUST insert its own. For example, a device, a telematics 1487 service provider in the call path, as well as the mobile carrier 1488 handling the call will each provide one. There may be circumstances 1489 where there is a service provider who is unaware that the call is an 1490 emergency call and cannot reasonably be expected to determine that it 1491 is an emergency call. In that case, that service provider is not 1492 expected to provide EmergencyCallData. 1494 5.2. Transmitting Blocks by Reference using the Provided-By Element 1496 The 'EmergencyCallDataReference' element is used to transmit an 1497 additional data block by reference within a 'Provided-By' element of 1498 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1499 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1500 type of data block referenced. The value of 'ref' is an HTTPS URL 1501 that resolves to a data structure with information about the call. 1502 The value of 'purpose' is the same as used in a 'Call-Info' header 1503 field (as specified in Section 5.1). 1505 For example, to reference a block with MIME type 'application/ 1506 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1507 to 'EmergencyCallData.ProviderInfo'. An example 1508 'EmergencyCallDataReference' element for this would be: 1510 1513 5.3. Transmitting Blocks by Value using the Provided-By Element 1515 It is RECOMMENDED that access networks supply the data specified in 1516 this document by reference, but they MAY provide the data by value. 1518 The 'EmergencyCallDataValue' element is used to transmit an 1519 additional data block by value within a 'Provided-By' element of a 1520 PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: 1521 'purpose' to indicate the type of data block contained. The value of 1522 'purpose' is the same as used in a 'Call-Info' header field (as 1523 specified in Section 5, and in Section 5.1). The same XML structure 1524 as would be contained in the corresponding MIME type body part is 1525 placed inside the 'EmergencyCallDataValue' element. 1527 For example: 1529 1531 flurbit735@es.example.com 1532 1533 1536 1538 This is an example text. 1539 1540 1542 1544 Test 1545 NENA 1546 Access Network Provider 1547 1548 sip:15555550987@burf.example.com;user=phone 1549 1550 1551 1553 Example Provided-By by Value. 1555 5.4. The Content-Disposition Parameter 1557 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1558 It updates and clarifies handling originally defined in RFC 3261 1559 [RFC3261] based on implementation experience. While RFC 3261 did not 1560 mandate support for 'multipart' message bodies, 'multipart/mixed' 1561 MIME bodies are used by many extensions (including this document) 1562 today. For example, adding a PIDF-LO, SDP, and additional data in 1563 body of a SIP message requires a 'multipart' message body. 1565 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1566 parameter for the Content-Disposition header field. These RFCs 1567 describe how a UAS reacts if it receives a message body whose content 1568 type or disposition type it does not understand. If the 'handling' 1569 parameter has the value "optional", the UAS ignores the message body. 1570 If the 'handling' parameter has the value "required", the UAS returns 1571 a 415 (Unsupported Media Type) response. The 'by-reference' 1572 disposition type allows a SIP message to contain a reference to the 1573 body part, and the SIP UA processes the body part according to the 1574 reference. This is the case for the Call-info header containing a 1575 Content Indirection (CID) URL. 1577 As an example, a SIP message indicates the Content-Disposition 1578 parameter in the body of the SIP message as shown in Figure 10. 1580 Content-Type: application/sdp 1582 ...Omit Content-Disposition here; defaults are ok 1583 ...SDP goes in here 1585 --boundary1 1587 Content-Type: application/pidf+xml 1588 Content-ID: 1589 Content-Disposition: by-reference;handling=optional 1591 ...PIDF-LO goes in here 1593 --boundary1-- 1595 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1596 Content-ID: <1234567890@atlanta.example.com> 1597 Content-Disposition: by-reference; handling=optional 1599 ...Data provider information data goes in here 1601 --boundary1-- 1603 Figure 10: Example for use of the Content-Disposition Parameter in 1604 SIP. 1606 6. Examples 1608 This section illustrates a longer and more complex example, as shown 1609 in Figure 11. In this example additional data is added by the end 1610 device, included by the VoIP provider (via the PIDF-LO), and provided 1611 by the access network provider. 1613 O +----+ [=============] [==============] 1614 /|\ | UA | [ Access ] [ VoIP ] 1615 | +----+ [ Network ] [ Provider ] 1616 / \ [ Provider ] [ example.org ] 1617 [ ] [ ] 1618 (1) [ ] (2) [ ] 1619 Emergency Call [ ] Emergency Call [ ] 1620 ------------------------------------------------------------> ] 1621 +Device Info [ ] +Device Info [ ] 1622 +Data Provider Info [ ^ ] +Data Provider Info [ | ] 1623 +Location URI [===.=========] +Location URI [=====|========] 1624 . | 1625 . | 1626 +Location . [================] | 1627 +Owner/Subscriber Info . [ ] (3) | 1628 +Device Info . (4) [ <---------------+ 1629 +Data Provider Info #3 .............> ] Emergency Call 1630 [ ] +Device Info 1631 [ PSAP ] +Data Provider Info #2 1632 [ ] +Location URI 1633 [================] 1635 Legend: 1637 --- Emergency Call Setup Procedure 1638 ... Location Retrieval/Response 1640 Figure 11: Additional Data Example Flow 1642 The example scenario starts with the end device itself adding device 1643 information, owner/subscriber information, a location URI, and data 1644 provider information to the outgoing emergency call setup message 1645 (see step #1 in Figure 11). The SIP INVITE example is shown in 1646 Figure 12. 1648 INVITE urn:service:sos SIP/2.0 1649 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1650 Max-Forwards: 70 1651 To: 1652 From: Hannes Tschofenig ;tag=9fxced76sl 1653 Call-ID: 3848276298220188511@example.com 1654 Call-Info: ;purpose=icon, 1655 ;purpose=info, 1656 1657 ;purpose=EmergencyCallData.ProviderInfo, 1658 1659 ;purpose=EmergencyCallData.DeviceInfo 1660 Geolocation: 1661 Geolocation-Routing: yes 1662 Accept: application/sdp, application/pidf+xml, 1663 application/EmergencyCallData.ProviderInfo+xml 1664 CSeq: 31862 INVITE 1665 Contact: 1666 Content-Type: multipart/mixed; boundary=boundary1 1668 Content-Length: ... 1670 --boundary1 1672 Content-Type: application/sdp 1674 ...SDP goes here 1676 --boundary1-- 1678 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1679 Content-ID: <0123456789@atlanta.example.com> 1680 Content-Disposition: by-reference;handling=optional 1681 1683 1686 d4b3072df09876543@[93.184.216.119] 1687 1688 laptop 1689 00-0d-4b-30-72-df 1691 1693 --boundary1-- 1695 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1696 Content-ID: <1234567890@atlanta.example.com> 1697 Content-Disposition: by-reference;handling=optional 1698 1699 1702 12345 1703 d4b3072df09876543@[93.184.216.119] 1704 1705 Hannes Tschofenig 1706 1707 Other 1708 tel:+1-555-555-0123 1709 EN 1710 1712 1713 Hannes Tschofenig 1714 1715 Hannes 1716 Tschofenig 1717 1718 1719 Dipl. Ing. 1720 1721 --0203 1722 1723 20090808T1430-0500 1724 1725 M 1726 1727 1 1728 1729 de 1730 1731 1732 2 1733 1734 en 1735 1736 1737 1738 work 1739 1743 1744 1745 1746 Linnoitustie 6 1747 Espoo 1748 Uusimaa 1749 02600 1750 Finland 1751 1752 1753 1754 1755 work 1756 voice 1757 1758 1759 tel:+358 50 4871445 1760 1761 1762 work 1763 1764 hannes.tschofenig@nsn.com 1765 1766 1767 work 1768 1769 geo:60.210796,24.812924 1770 1771 1772 1773 home 1774 1775 https://www.example.com/key.asc 1776 1777 1778 Finland/Helsinki 1779 1780 home 1781 1782 http://example.com/hannes.tschofenig 1783 1784 1785 1786 1787 --boundary1-- 1789 Figure 12: End Device sending SIP INVITE with Additional Data. 1791 In this example, information available to the access network provider 1792 is included in the call setup message only indirectly via the use of 1793 the location reference. The PSAP has to retrieve it via a separate 1794 look-up step. Since the access network provider and the VoIP service 1795 provider are two independent entities in this scenario, the access 1796 network provider is not involved in application layer exchanges; the 1797 SIP INVITE transits the access network transparently, as illustrated 1798 in steps #1 and #2. The access network does not alter the SIP 1799 INVITE. 1801 The VoIP service provider receives the message and determines based 1802 on the Service URN that the incoming request is an emergency call. 1803 It performs typical emergency services related tasks, including 1804 location-based routing, and adds additional data, namely service and 1805 subscriber information as well as data provider information #2, to 1806 the outgoing message. For the example we assume a VoIP service 1807 provider that deploys a back-to-back user agent allowing additional 1808 data to be included in the body of the SIP message (rather than per 1809 reference in the header), which allows us to illustrate the use of 1810 multiple data provider info blocks. The resulting message is shown 1811 in Figure 13. The SIP INVITE is sent to the PSAP in step #3. 1813 INVITE sips:psap@example.org SIP/2.0 1814 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1815 Max-Forwards: 70 1816 To: 1817 From: Hannes Tschofenig ;tag=9fxced76sl 1818 Call-ID: 3848276298220188511@example.com 1819 Call-Info: ;purpose=icon, 1820 ;purpose=info, 1821 1822 ;purpose=EmergencyCallData.ProviderInfo 1823 1824 ;purpose=EmergencyCallData.DeviceInfo 1825 Call-Info: 1826 ;purpose=EmergencyCallData.ServiceInfo 1827 Call-Info: 1828 ;purpose=EmergencyCallData.ProviderInfo 1829 Geolocation: 1830 Geolocation-Routing: yes 1831 Accept: application/sdp, application/pidf+xml, 1832 application/EmergencyCallData.ProviderInfo+xml 1833 CSeq: 31862 INVITE 1834 Contact: 1835 Content-Type: multipart/mixed; boundary=boundary1 1837 Content-Length: ... 1839 --boundary1 1840 Content-Type: application/sdp 1842 ...SDP goes here 1844 --boundary1-- 1846 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1847 Content-ID: <0123456789@atlanta.example.com> 1848 Content-Disposition: by-reference;handling=optional 1849 1851 1854 d4b3072df09876543@[93.184.216.119] 1855 1856 laptop 1857 00-0d-4b-30-72-df 1859 1861 --boundary1-- 1863 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1864 Content-ID: <1234567890@atlanta.example.com> 1865 Content-Disposition: by-reference;handling=optional 1866 1867 1870 d4b3072df09876543@[93.184.216.119] 1871 1872 Hannes Tschofenig 1873 1874 Other 1875 tel:+1-555-555-0123 1876 EN 1877 1879 1880 Hannes Tschofenig 1881 1882 Hannes 1883 Tschofenig 1884 1885 1886 Dipl. Ing. 1887 1888 --0203 1889 1890 20090808T1430-0500 1891 1892 M 1893 1894 1 1895 1896 de 1897 1898 1899 2 1900 1901 en 1902 1903 1904 1905 work 1906 1910 1911 1912 1913 Linnoitustie 6 1914 Espoo 1915 Uusimaa 1916 02600 1917 Finland 1918 1919 1920 1921 1922 work 1923 voice 1924 1925 1926 tel:+358 50 4871445 1927 1928 1929 work 1930 1931 hannes.tschofenig@nsn.com 1932 1933 1934 work 1935 1936 geo:60.210796,24.812924 1937 1938 1939 1940 home 1941 1942 https://www.example.com/key.asc 1943 1944 1945 Finland/Helsinki 1946 1947 home 1948 1949 http://example.com/hannes.tschofenig 1950 1951 1952 1953 1955 --boundary1-- 1957 Content-Type: application/EmergencyCallData.ServiceInfo+xml 1958 Content-ID: 1959 Content-Disposition: by-reference;handling=optional 1960 1961 1964 string0987654321@example.org 1965 1966 Residence 1967 VOIP 1968 Unknown 1969 1971 --boundary1-- 1973 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1974 Content-ID: 1975 Content-Disposition: by-reference;handling=optional 1976 1977 1980 string0987654321@example.org 1981 1982 Example VoIP Provider 1983 1985 urn:nena:companyid:ID123 1986 NENA 1987 Service Provider 1988 sip:voip-provider@example.com 1989 EN 1990 1992 1993 John Doe 1994 1995 John 1996 Doe 1997 1998 1999 2000 2001 --0203 2002 2003 20090808T1430-0500 2004 2005 M 2006 2007 1 2008 2009 en 2010 2011 2012 work 2013 2014 Example VoIP Provider 2015 2016 2017 2018 work 2019 2022 2023 2024 2025 Downing Street 10 2026 London 2027 2028 SW1A 2AA 2029 UK 2030 2031 2032 2033 2034 work 2035 voice 2036 2037 2038 sips:john.doe@example.com 2039 2040 2041 work 2042 2043 john.doe@example.com 2044 2045 2046 work 2047 2048 geo:51.503396, 0.127640 2049 2050 Europe/London 2051 2052 home 2053 2054 http://www.example.com/john.doe 2055 2056 2057 2058 2060 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2062 Finally, the PSAP requests location information from the access 2063 network provider. The response is shown in Figure 14. Along with 2064 the location information, additional data is provided in the 2065 element of the PIDF-LO. This request and response is 2066 step #4. 2068 2069 2074 2075 2076 2077 2079 AU 2080 NSW 2081 Wollongong 2082 North Wollongong 2083 Flinders 2084 Street 2085 Campbell Street 2086 Gilligan's Island 2087 Corner 2088 Video Rental Store 2089 2500 2090 Westerns and Classics 2091 store 2092 Private Box 15 2093 2094 2095 2096 true 2097 2098 2013-12-10T20:00:00Z 2099 2100 2101 802.11 2103 2106 2109 2110 2112 88QV4FpfZ976T@example.com 2113 2114 University of Example 2115 2116 urn:nena:companyid:uoi 2117 NENA 2118 Other 2119 tel:+1 555-824-5222 2120 EN 2121 2123 2125 88QV4FpfZ976T@example.com 2126 2127 This is an example text. 2129 2131 2132 2133 2134 mac:00-0d-4b-30-72-df 2135 2013-07-09T20:57:29Z 2136 2137 2139 Figure 14: Access Network Provider returning PIDF-LO with Additional 2140 Data. 2142 7. XML Schemas 2144 This section defines the XML schemas of the five data blocks. 2145 Additionally, the Provided-By schema is specified. 2147 7.1. EmergencyCallData.ProviderInfo XML Schema 2149 2150 2160 2163 2165 2166 2167 2168 2169 2171 2175 2178 2179 2180 2181 2182 2183 2185 2186 2187 2190 2193 2196 2199 2202 2205 2208 2212 2215 2218 2220 2221 2223 2225 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2227 7.2. EmergencyCallData.ServiceInfo XML Schema 2229 2230 2238 2241 2243 2244 2245 2248 2251 2254 2257 2259 2260 2262 2264 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2266 7.3. EmergencyCallData.DeviceInfo XML Schema 2268 2269 2276 2279 2281 2282 2283 2286 2289 2292 2295 2297 2298 2299 2300 2303 2304 2305 2306 2308 2311 2314 2316 2318 2320 2322 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2324 7.4. EmergencyCallData.SubscriberInfo XML Schema 2326 2327 2336 2339 2341 2343 2344 2345 2346 2349 2352 2354 2355 2356 2357 2359 2361 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2363 7.5. EmergencyCallData.Comment XML Schema 2364 2365 2373 2376 2378 2379 2380 2383 2387 2389 2390 2392 2393 2394 2395 2396 2397 2398 2400 2402 Figure 19: EmergencyCallData.Comment XML Schema. 2404 7.6. Provided-By XML Schema 2406 This section defines the Provided-By schema. 2408 2409 2422 2423 2424 2425 2426 2428 2430 2431 2432 2435 2439 2443 2446 2448 2450 2452 2453 2454 2455 2456 2458 2459 2461 2463 2464 2465 2467 2469 2470 2471 2474 2477 2480 2483 2487 2490 2491 2493 2495 Figure 20: Provided-By XML Schema. 2497 8. Security Considerations 2499 The data structures described in this document contain information 2500 usually considered private. When information is provided by value, 2501 entities that are a party to the SIP signaling (such as proxy servers 2502 and back-to-back user agents) will have access to it and need to 2503 protect it against inappropriate disclosure. An entity that is able 2504 to eavesdrop on the SIP signaling will also have access. Some media 2505 (such as in the clear Wi-Fi) is more vulnerable than others (such as 2506 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that 2507 protect against eavesdropping (such as Transport Layer Security 2508 (TLS)) SHOULD be preferentially used whenever feasible. When 2509 information is provided by reference, HTTPS is specified for 2510 dereferencing, and the provider of the information is REQUIRED to 2511 validate the credentials of the requester. While the creation of a 2512 public key infrastructure (PKI) that has global scope may be 2513 difficult, the alternatives to creating devices and services that can 2514 provide critical information securely are more daunting. The 2515 provider of the information MAY enforce any policy it wishes to use, 2516 but PSAPs and responder agencies SHOULD deploy a PKI so that 2517 providers of additional data can check the certificate of the client 2518 and decide the appropriate policy to enforce based on that 2519 certificate. 2521 Ideally, the PSAP and emergency responders will be given credentials 2522 signed by an authority trusted by the data provider. In most 2523 circumstances, nationally recognized credentials would be sufficient, 2524 and if the emergency services arranges a PKI, data providers could be 2525 provisioned with the root CA public key for a given nation. Some 2526 nations are developing a PKI for this, and related, purposes. Since 2527 calls could be made from devices where the device and/or the service 2528 provider(s) are not local to the emergency services authorities, 2529 globally recognized credentials are useful. This might be 2530 accomplished by extending the notion of the "forest guide" described 2531 in [RFC5582] to allow the forest guide to provide the credential of 2532 the PKI root for areas for which it has coverage information, but 2533 standards for such a mechanism are not yet available. In its 2534 absence, the data provider will need to obtain by out of band means 2535 the root CA credentials for any areas to which it is willing to 2536 provide additional data. With the credential of the root CA for a 2537 national emergency services PKI, the data provider server can 2538 validate the credentials of an entity requesting additional data by 2539 reference. 2541 The data provider also needs a credential that can be verified by the 2542 emergency services to know that it is receiving data from an 2543 authorized server. The emergency services authorities could provide 2544 credentials, distinguishable from credentials provided to emergency 2545 responders and PSAPs, which could be used to validate data providers. 2546 Such credentials would have to be acceptable to any PSAP or responder 2547 that could receive a call with additional data supplied by that 2548 provider. This would be extensible to global credential validation 2549 using the forest guide as mentioned above. In the absence of such 2550 credentials, the emergency services authorities could maintain a list 2551 of local data providers' credentials as provided to them out of band. 2552 At a minimum, the emergency services authorities could obtain a 2553 credential from the DNS entry of the domain in the Additional Data 2554 URI to at least validate that the server is known to the domain 2555 providing the URI. 2557 Data provided by devices by reference have similar credential 2558 validation issues as for service providers, and the solutions are the 2559 same. 2561 Much of the information supplied by service providers and devices is 2562 private and confidential; service providers and devices generally go 2563 to lengths to protect this information; disclosing it in the context 2564 of an emergency call is a trade-off to protect the greater interest 2565 of the customer in an emergency. 2567 Neither service providers nor devices will supply private information 2568 unless the call is recognized as an emergency call. In cellular 2569 telephony systems (such as those using 3GPP IMS), there are different 2570 procedures for an originating device to place an emergency versus a 2571 normal call. If a call that is really an emergency call is initiated 2572 as a normal call and the cellular service provider recognizes this, 2573 3GPP IMS permits the service provider to either accept the call 2574 anyway or reject it with a specific code that instructs the device to 2575 retry the call as an emergency call. Service providers SHOULD choose 2576 the latter, because otherwise the device will not have included the 2577 information specified in this document (since the device didn't 2578 recognize the call as being an emergency call). 2580 9. Privacy Considerations 2581 This document enables functionality for conveying additional 2582 information about the caller and the caller's device and service to 2583 the callee. Some of this information is personal data and therefore 2584 privacy concerns arise. An explicit privacy indicator for 2585 information directly relating to the caller's identity is defined and 2586 use is mandatory. However, observance of this request for privacy 2587 and what information it relates to is determined by the destination 2588 jurisdiction. 2590 There are a number of privacy concerns with non-emergency real-time 2591 communication services that are also applicable to emergency calling. 2592 Data protection regulation world-wide has, however, decided to create 2593 exceptions for emergency services since the drawbacks of disclosing 2594 personal data are outweighed by the benefit for the emergency caller. 2595 Hence, the data protection rights of individuals are commonly waived 2596 for emergency situations. There are, however, still various 2597 countries that offer some degree of anonymity for the caller towards 2598 PSAP call takers. 2600 The functionality defined in this document, however, far exceeds the 2601 amount of information sharing found in the legacy POTS system. For 2602 this reason there are additional privacy threats to consider, which 2603 are described in more detail in [RFC6973]. 2605 Stored Data Compromise: There is an increased risk of stored data 2606 compromise since additional data is collected and stored in 2607 databases. Without adequate measures to secure stored data from 2608 unauthorized or inappropriate access at access network providers, 2609 service providers, end devices, as well as PSAPs, individuals are 2610 exposed to potential financial, reputational, or physical harm. 2612 Misattribution: If the personal data collected and conveyed is 2613 incorrect or inaccurate then this may lead to misattribution. 2614 Misattribution occurs when data or communications related to one 2615 individual are attributed to another. 2617 Identification: By the nature of the additional data and its 2618 capability to provide much richer information about the caller, 2619 the call, and the location, the calling party is identified in a 2620 much better way. Some users may feel uncomfortable with this 2621 degree of information sharing even in emergency services 2622 situations. 2624 Secondary Use: There is a risk of secondary use, which is the use of 2625 collected information about an individual without the individual's 2626 consent for a purpose different from that for which the 2627 information was collected. The stated purpose of the additional 2628 data is for emergency services purposes but theoretically the same 2629 information could be used for any other call as well. 2630 Additionally, parties involved in the emergency call may retain 2631 the obtained information and may re-use it for other, non- 2632 emergency services purposes. 2634 Disclosure: When the data defined in this document is not properly 2635 protected (while in transit with traditional communication 2636 security techniques, and while stored using access control 2637 mechanisms) there is the risk of disclosure, which is the 2638 revelation of private information about an individual. 2640 To mitigate these privacy risks the following countermeasures can be 2641 taken: 2643 In regions where callers can elect to suppress certain personally 2644 identifying information, network or PSAP functionality can inspect 2645 privacy flags within the SIP headers to determine what information 2646 may be passed, stored, or displayed to comply with local policy or 2647 law. RFC 3325 [RFC3325] defines the "id" priv-value token. The 2648 presence of this privacy type in a Privacy header field indicates 2649 that the user would like the network asserted identity to be kept 2650 private with respect to SIP entities outside the trust domain with 2651 which the user authenticated, including the PSAP. 2653 This document defines various data structures that contain privacy- 2654 sensitive data. For example, identifiers for the device (e.g., 2655 serial number, MAC address) or account/SIM (e.g., IMSI), contact 2656 information for the user, location of the caller. Local regulations 2657 may govern what data must be provided in emergency calls, but in 2658 general, the emergency call system is aided by the information 2659 described in this document. There is a tradeoff between the privacy 2660 considerations and the utility of the data. For protection, this 2661 specification requires all retrieval of data passed by reference to 2662 be protected against eavesdropping and alteration via communication 2663 security techniques (namely TLS). Furthermore, security safeguards 2664 are required to prevent unauthorized access to stored data. Various 2665 security incidents over at least the past few decades have shown that 2666 data breaches are not uncommon and are often caused by lack of proper 2667 access control frameworks, software bugs (such as buffer overflows), 2668 or missing input parsing (such as SQL injection attacks). The risks 2669 of data breaches is increased with the obligation for emergency 2670 services to retain emergency call related data for extended periods 2671 (e.g., several years are the norm). 2673 Finally, it is also worth highlighting the nature of the SIP 2674 communication architecture, which introduces additional complications 2675 for privacy. Some forms of data can be sent by value in the SIP 2676 signaling or by reference (a URL in the SIP signaling). When data is 2677 sent by value, all intermediaries have access to the data. As such, 2678 these intermediaries may also introduce additional privacy risk. 2679 Therefore, in situations where the conveyed information is privacy- 2680 sensitive and intermediaries are involved, transmitting by reference 2681 might be appropriate, assuming the source of the data can operate a 2682 sufficient dereferencing infrastructure and that proper access 2683 control policies are available for distinguishing the different 2684 entities dereferencing the reference. Without access control 2685 policies any party in possession of the reference is able to resolve 2686 the reference and to obtain the data, including intermediaries. 2688 10. IANA Considerations 2690 10.1. Registry creation 2692 This document creates a new registry called 'Emergency Call 2693 Additional Data'. The following sub-registries are created for this 2694 registry. 2696 10.1.1. Provider ID Series Registry 2698 This document creates a new sub-registry called 'Additional Call Data 2699 Provider ID Series'. As defined in [RFC5226], this registry operates 2700 under "Expert Review" rules. The expert should determine that the 2701 entity requesting a new value is a legitimate issuer of service 2702 provider IDs suitable for use in Additional Call Data. 2704 Private entities issuing and using internally-generated IDs are 2705 encouraged to register and use a unique identifier. This guarantees 2706 that IDs issued and used by the entity are globally unique and 2707 distinguishable. 2709 The content of this registry includes: 2711 Name: The identifier which will be used in the 'ProviderIDSeries' 2712 element. 2714 Source: The full name of the organization issuing the identifiers. 2716 URL: A URL to the organization for further information. 2718 The initial set of values is listed in Figure 21. 2720 +-----------+--------------------------+----------------------+ 2721 | Name | Source | URL | 2722 +-----------+--------------------------+----------------------+ 2723 | NENA | National Emergency | http://www.nena.org | 2724 | | Number Association | | 2725 | EENA | European Emergency | http://www.eena.org | 2726 | | Number Association | | 2727 | domain | (The ID is a fully- | (not applicable) | 2728 | | qualified domain name) | | 2729 +-----------+--------------------------+----------------------+ 2731 Figure 21: Provider ID Series Registry. 2733 10.1.2. Service Environment Registry 2735 This document creates a new sub-registry called 'Additional Call 2736 Service Environment'. As defined in [RFC5226], this registry 2737 operates under "Expert Review" rules. The expert should determine 2738 that the entity requesting a new value is relevant for this service 2739 element, and that the new value is distinct from existing values, and 2740 its use is unambiguous. 2742 The content of this registry includes: 2744 Token: The value to be used in the element. 2746 Description: A short description of the value. 2748 The initial set of values is listed in Figure 22. 2750 +-----------+--------------------------+ 2751 | Token | Description | 2752 +-----------+--------------------------+ 2753 | Business | Business service | 2754 | Residence | Residential service | 2755 | unknown | Type of service unknown | 2756 | | (e.g., anonymous pre- | 2757 | | paid service) | 2758 +-----------+--------------------------+ 2760 Figure 22: Service Environment Registry. 2762 10.1.3. Service Type Registry 2764 This document creates a new sub-registry called 'Additional Call 2765 Service Type'. As defined in [RFC5226], this registry operates under 2766 "Expert Review" rules. The expert should determine that the entity 2767 requesting a new value is relevant for this service element and that 2768 the requested value is clearly distinct from other values so that 2769 there is no ambiguity as to when the value is to be used or which 2770 value is to be used. 2772 The content of this registry includes: 2774 Name: The value to be used in the element. 2776 Description: A short description of the value. 2778 The initial set of values is listed in Figure 3. 2780 10.1.4. Service Mobility Registry 2782 This document creates a new sub-registry called 'Additional Call 2783 Service Mobility'. As defined in [RFC5226], this registry operates 2784 under "Expert Review" rules. The expert should determine that the 2785 entity requesting a new value is relevant for this service element 2786 and that the requested value is clearly distinct from other values so 2787 that there is no ambiguity as to when the value is to be used or 2788 which value is to be used. 2790 The content of this registry includes: 2792 Token: The value used in the element. 2794 Description: A short description of the value. 2796 The initial set of values is listed in Figure 23. 2798 +-----------+----------------------------+ 2799 | Token | Description | 2800 +-----------+----------------------------+ 2801 | Mobile | The device is able to | 2802 | | move at any time | 2803 | Fixed | The device is not expected | 2804 | | to move unless the service | 2805 | | is relocated | 2806 | Nomadic | The device is not expected | 2807 | | to change its point of | 2808 | | attachment while on a call | 2809 | Unknown | No information is known | 2810 | | about the service mobility | 2811 | | environment for the device | 2812 +-----------+----------------------------+ 2814 Figure 23: Service Environment Registry. 2816 10.1.5. Service Provider Type Registry 2817 This document creates a new sub-registry called 'Service Provider 2818 Type'. As defined in [RFC5226], this registry operates under "Expert 2819 Review". The expert should determine that the proposed new value is 2820 distinct from existing values and appropriate for use in the 2821 TypeOfServicerProvider element 2823 The content of this registry includes: 2825 Tokenproviderid: The value used in the 'TypeOfProvider' element. 2827 Description: A short description of the type of service provider. 2829 The initial set of values is defined in Figure 1. 2831 10.1.6. Service Delivered Registry 2833 This document creates a new sub-registry called 'Service Delivered'. 2834 As defined in [RFC5226], this registry operates under "Expert Review" 2835 rules. The expert should consider whether the proposed service is 2836 unique from existing services and the definition of the service will 2837 be clear to implementors and PSAPs/responders. 2839 The content of this registry includes: 2841 Name: The value used in the 'ServiceType' element. 2843 Description: Short description identifying the nature of the 2844 service. 2846 The initial set of values are defined in Figure 3. 2848 10.1.7. Device Classification Registry 2850 This document creates a new sub-registry called 'Device 2851 Classification'. As defined in [RFC5226], this registry operates 2852 under "Expert Review" rules. The expert should consider whether the 2853 proposed class is unique from existing classes and the definition of 2854 the class will be clear to implementors and PSAPs/responders. 2856 The content of this registry includes: 2858 Token: Value used in the 'DeviceClassification' element. 2860 Description: Short description identifying the device type. 2862 The initial set of values are defined in Figure 5. 2864 10.1.8. Device ID Type Type Registry 2866 This document creates a new sub-registry called 'Additional Call Data 2867 Device ID Type'. As defined in [RFC5226], this registry operates 2868 under "Expert Review" rules. The expert should ascertain that the 2869 proposed type is well understood, and provides the information useful 2870 to PSAPs and responders to uniquely identify a device. 2872 The content of this registry includes: 2874 Token: The value to be placed in the 'TypeOfDeviceID' element. 2876 Description: Short description identifying the type of the device 2877 ID. 2879 The initial set of values are defined in Figure 6. 2881 10.1.9. Device/Service Data Type Registry 2883 This document creates a new sub-registry called 'Device/Service Data 2884 Type Registry'. As defined in [RFC5226], this registry operates 2885 under "Expert Review" and "Specification Required" rules. The expert 2886 should ascertain that the proposed type is well understood, and 2887 provides information useful to PSAPs and responders. The 2888 specification must contain a complete description of the data, and a 2889 precise format specification suitable to allow interoperable 2890 implementations. 2892 The content of this registry includes: 2894 Token: The value to be placed in the element. 2896 Description: Short description identifying the the data. 2898 Specification: Citation for the specification of the data. 2900 The initial set of values are listed in Figure 24. 2902 +----------+----------------------------------------+----------------+ 2903 | Token | Description | Specification | 2904 +----------+----------------------------------------+----------------+ 2905 | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2906 +----------+----------------------------------------+----------------+ 2908 Figure 24: Device/Service Data Type Registry. 2910 10.1.10. Emergency Call Data Types Registry 2911 This document creates a new sub-registry called 'Emergency Call Data 2912 Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. 2913 As defined in [RFC5226], this registry operates under "Expert Review" 2914 and "Specification Required" rules. The expert is responsible for 2915 verifying that the document contains a complete and clear 2916 specification and the proposed functionality does not obviously 2917 duplicate existing functionality. 2919 The content of this registry includes: 2921 Token: The root of the data's MIME subtype (not including the 2922 'EmergencyCallData' prefix and any suffix such as '+xml') 2924 Reference: The document that describes the data object 2926 Note that the values from this registry are part of the 2927 'EmergencyCallData' compound value; when used as a value of the 2928 'purpose' parameter of the Call-Info header, the values listed in 2929 this registry are prefixed by 'EmergencyCallData.' per the the 2930 'EmergencyCallData' registation Section 10.2. 2932 The initial set of values are listed in Figure 25. 2934 +----------------+------------+ 2935 | Token | Reference | 2936 +----------------+------------+ 2937 | ProviderInfo | [This RFC] | 2938 | ServiceInfo | [This RFC] | 2939 | DeviceInfo | [This RFC] | 2940 | SubscriberInfo | [This RFC] | 2941 | Comment | [This RFC] | 2942 +----------------+------------+ 2944 Figure 25: Additional Data Blocks Registry. 2946 10.2. 'EmergencyCallData' Purpose Parameter Value 2948 This document defines the 'EmergencyCallData' value for the "purpose" 2949 parameter of the Call-Info header field. The Call-Info header and 2950 the corresponding registry for the 'purpose' parameter was 2951 established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' 2952 is a compound value; when used as a value of the 'purpose' parameter 2953 of the Call-Info header, 'EmergencyCallData' is immediately followed 2954 by a dot ('.') and a value from the 'Emergency Call Data Types' 2955 registry Section 10.1.10. 2957 Header Parameter New 2958 Field Name Value Reference 2959 ---------- --------- ----------------- --------- 2960 Call-Info purpose EmergencyCallData [This RFC] 2962 10.3. URN Sub-Namespace Registration for provided-by Registry Entry 2964 This section registers the namespace specified in Section 10.5.1 in 2965 the provided-by registry established by RFC 4119, for usage within 2966 the element of a PIDF-LO. 2968 The schema for the provided-by element used by this document is 2969 specified in Section 7.6. 2971 10.4. MIME Registrations 2973 10.4.1. MIME Content-type Registration for 'application/ 2974 EmergencyCallData.ProviderInfo+xml' 2976 This specification requests the registration of a new MIME type 2977 according to the procedures of RFC 6838 [RFC6838] and guidelines in 2978 RFC 7303 [RFC7303]. 2980 MIME media type name: application 2982 MIME subtype name: EmergencyCallData.ProviderInfo+xml 2984 Mandatory parameters: none 2986 Optional parameters: charset (indicates the character encoding of 2987 the contents) 2989 Encoding considerations: Uses XML, which can contain 8-bit 2990 characters, depending on the character encoding. See Section 3.2 2991 of RFC 7303 [RFC7303]. 2993 Security considerations: This content type is designed to carry 2994 the data provider information, which is a sub-category of 2995 additional data about an emergency call. Since this data may 2996 contain personal information, appropriate precautions might be 2997 needed to limit unauthorized access, inappropriate disclosure, and 2998 eavesdropping of personal information. Please refer to Section 8 2999 and Section 9 for more information. 3001 Interoperability considerations: None 3002 Published specification: [TBD: This specification] 3004 Applications which use this media type: Emergency Services 3006 Additional information: 3008 Magic Number: None 3010 File Extension: .xml 3012 Macintosh file type code: 'TEXT' 3014 Person and email address for further information: Hannes 3015 Tschofenig, Hannes.Tschofenig@gmx.net 3017 Intended usage: LIMITED USE 3019 Author: This specification is a work item of the IETF ECRIT 3020 working group, with mailing list address . 3022 Change controller: The IESG 3024 10.4.2. MIME Content-type Registration for 'application/ 3025 EmergencyCallData.ServiceInfo+xml' 3027 This specification requests the registration of a new MIME type 3028 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3029 RFC 7303 [RFC7303]. 3031 MIME media type name: application 3033 MIME subtype name: EmergencyCallData.ServiceInfo+xml 3035 Mandatory parameters: none 3037 Optional parameters: charset (indicates the character encoding of 3038 the contents) 3040 Encoding considerations: Uses XML, which can contain 8-bit 3041 characters, depending on the character encoding. See Section 3.2 3042 of RFC 7303 [RFC7303]. 3044 Security considerations: This content type is designed to carry 3045 the service information, which is a sub-category of additional 3046 data about an emergency call. Since this data may contain 3047 personal information, appropriate precautions may be needed to 3048 limit unauthorized access, inappropriate disclosure, and 3049 eavesdropping of personal information. Please refer to Section 8 3050 and Section 9 for more information. 3052 Interoperability considerations: None 3054 Published specification: [TBD: This specification] 3056 Applications which use this media type: Emergency Services 3058 Additional information: 3060 Magic Number: None 3062 File Extension: .xml 3064 Macintosh file type code: 'TEXT' 3066 Person and email address for further information: Hannes 3067 Tschofenig, Hannes.Tschofenig@gmx.net 3069 Intended usage: LIMITED USE 3071 Author: This specification is a work item of the IETF ECRIT 3072 working group, with mailing list address . 3074 Change controller: The IESG 3076 10.4.3. MIME Content-type Registration for 'application/ 3077 EmergencyCallData.DeviceInfo+xml' 3079 This specification requests the registration of a new MIME type 3080 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3081 RFC 7303 [RFC7303]. 3083 MIME media type name: application 3085 MIME subtype name: EmergencyCallData.DeviceInfo+xml 3087 Mandatory parameters: none 3089 Optional parameters: charset (indicates the character encoding of 3090 the contents) 3091 Encoding considerations: Uses XML, which can contain 8-bit 3092 characters, depending on the character encoding. See Section 3.2 3093 of RFC 7303 [RFC7303]. 3095 Security considerations: This content type is designed to carry 3096 device information, which is a sub-category of additional data 3097 about an emergency call. Since this data contains personal 3098 information, appropriate precautions need to be taken to limit 3099 unauthorized access, inappropriate disclosure to third parties, 3100 and eavesdropping of this information. Please refer to Section 8 3101 and Section 9 for more information. 3103 Interoperability considerations: None 3105 Published specification: [TBD: This specification] 3107 Applications which use this media type: Emergency Services 3109 Additional information: 3111 Magic Number: None 3113 File Extension: .xml 3115 Macintosh file type code: 'TEXT' 3117 Person and email address for further information: Hannes 3118 Tschofenig, Hannes.Tschofenig@gmx.net 3120 Intended usage: LIMITED USE 3122 Author: This specification is a work item of the IETF ECRIT 3123 working group, with mailing list address . 3125 Change controller: The IESG 3127 10.4.4. MIME Content-type Registration for 'application/ 3128 EmergencyCallData.SubscriberInfo+xml' 3130 This specification requests the registration of a new MIME type 3131 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3132 RFC 7303 [RFC7303]. 3134 MIME media type name: application 3136 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 3138 Mandatory parameters: none 3139 Optional parameters: charset (indicates the character encoding of 3140 the contents) 3142 Encoding considerations: Uses XML, which can contain 8-bit 3143 characters, depending on the character encoding. See Section 3.2 3144 of RFC 7303 [RFC7303]. 3146 Security considerations: This content type is designed to carry 3147 owner/subscriber information, which is a sub-category of 3148 additional data about an emergency call. Since this data contains 3149 personal information, appropriate precautions need to be taken to 3150 limit unauthorized access, inappropriate disclosure to third 3151 parties, and eavesdropping of this information. Please refer to 3152 Section 8 and Section 9 for more information. 3154 Interoperability considerations: None 3156 Published specification: [TBD: This specification] 3158 Applications which use this media type: Emergency Services 3160 Additional information: 3162 Magic Number: None 3164 File Extension: .xml 3166 Macintosh file type code: 'TEXT' 3168 Person and email address for further information: Hannes 3169 Tschofenig, Hannes.Tschofenig@gmx.net 3171 Intended usage: LIMITED USE 3173 Author: This specification is a work item of the IETF ECRIT 3174 working group, with mailing list address . 3176 Change controller: The IESG 3178 10.4.5. MIME Content-type Registration for 'application/ 3179 EmergencyCallData.Comment+xml' 3181 This specification requests the registration of a new MIME type 3182 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3183 RFC 7303 [RFC7303]. 3185 MIME media type name: application 3186 MIME subtype name: EmergencyCallData.Comment+xml 3188 Mandatory parameters: none 3190 Optional parameters: charset (indicates the character encoding of 3191 the contents) 3193 Encoding considerations: Uses XML, which can contain 8-bit 3194 characters, depending on the character encoding. See Section 3.2 3195 of RFC 7303 [RFC7303]. 3197 Security considerations: This content type is designed to carry a 3198 comment, which is a sub-category of additional data about an 3199 emergency call. This data may contain personal information. 3200 Appropriate precautions may be needed to limit unauthorized 3201 access, inappropriate disclosure to third parties, and 3202 eavesdropping of this information. Please refer to Section 8 and 3203 Section 9 for more information. 3205 Interoperability considerations: None 3207 Published specification: [TBD: This specification] 3209 Applications which use this media type: Emergency Services 3211 Additional information: 3213 Magic Number: None 3215 File Extension: .xml 3217 Macintosh file type code: 'TEXT' 3219 Person and email address for further information: Hannes 3220 Tschofenig, Hannes.Tschofenig@gmx.net 3222 Intended usage: LIMITED USE 3224 Author: This specification is a work item of the IETF ECRIT 3225 working group, with mailing list address . 3227 Change controller: The IESG 3229 10.5. URN Sub-Namespace Registration 3231 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3233 This section registers a new XML namespace, as per the guidelines in 3234 RFC 3688 [RFC3688]. 3236 URI: urn:ietf:params:xml:ns:EmergencyCallData 3238 Registrant Contact: IETF, ECRIT working group, , as 3239 delegated by the IESG . 3241 XML: 3243 BEGIN 3244 3245 3247 3248 3249 3251 Namespace for Additional Emergency Call Data 3252 3253 3254

Namespace for Additional Data related to an Emergency Call

3255

See [TBD: This document].

3256 3257 3258 END 3260 10.5.2. Registration for 3261 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3263 This section registers a new XML namespace, as per the guidelines in 3264 RFC 3688 [RFC3688]. 3266 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3268 Registrant Contact: IETF, ECRIT working group, , as 3269 delegated by the IESG . 3271 XML: 3273 BEGIN 3274 3275 3277 3278 3279 3281 Namespace for Additional Emergency Call Data: 3282 Data Provider Information 3283 3284 3285

Namespace for Additional Data related to an Emergency Call

3286

Data Provider Information

3287

See [TBD: This document].

3288 3289 3290 END 3292 10.5.3. Registration for 3293 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3295 This section registers a new XML namespace, as per the guidelines in 3296 RFC 3688 [RFC3688]. 3298 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3300 Registrant Contact: IETF, ECRIT working group, , as 3301 delegated by the IESG . 3303 XML: 3305 BEGIN 3306 3307 3309 3310 3311 3313 Namespace for Additional Emergency Call Data: 3314 Service Information 3315 3316 3317

Namespace for Additional Data related to an Emergency Call

3318

Service Information

3319

See [TBD: This document].

3320 3321 3322 END 3324 10.5.4. Registration for 3325 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3327 This section registers a new XML namespace, as per the guidelines in 3328 RFC 3688 [RFC3688]. 3330 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3332 Registrant Contact: IETF, ECRIT working group, , as 3333 delegated by the IESG . 3335 XML: 3337 BEGIN 3338 3339 3341 3342 3343 3345 Namespace for Additional Emergency Call Data: 3346 Device Information 3347 3348 3349

Namespace for Additional Data related to an Emergency Call

3350

Device Information

3351

See [TBD: This document].

3352 3353 3354 END 3356 10.5.5. Registration for 3357 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3359 This section registers a new XML namespace, as per the guidelines in 3360 RFC 3688 [RFC3688]. 3362 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3363 Registrant Contact: IETF, ECRIT working group, , as 3364 delegated by the IESG . 3366 XML: 3368 BEGIN 3369 3370 3372 3373 3374 3376 Namespace for Additional Emergency Call Data: 3377 Owner/Subscriber Information 3378 3379 3380

Namespace for Additional Data related to an Emergency Call

3381

Owner/Subscriber Information

3382

See [TBD: This document].

3383 3384 3385 END 3387 10.5.6. Registration for 3388 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3390 This section registers a new XML namespace, as per the guidelines in 3391 RFC 3688 [RFC3688]. 3393 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3395 Registrant Contact: IETF, ECRIT working group, , as 3396 delegated by the IESG . 3398 XML: 3400 BEGIN 3401 3402 3404 3405 3406 3409 Namespace for Additional Emergency Call Data:Comment 3410 3411 3412

Namespace for Additional Data related to an Emergency Call

3413

Comment

3414

See [TBD: This document].

3415 3416 3417 END 3419 10.6. Schema Registrations 3421 This specification registers five schemas, as per the guidelines in 3422 RFC 3688 [RFC3688]. 3424 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3426 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3427 delegated by the IESG (iesg@ietf.org). 3429 XML: The XML schema can be found in Figure 15. 3431 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3433 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3434 delegated by the IESG (iesg@ietf.org). 3436 XML: The XML schema can be found in Figure 16. 3438 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3440 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3441 delegated by the IESG (iesg@ietf.org). 3443 XML: The XML schema can be found in Figure 17. 3445 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3447 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3448 delegated by the IESG (iesg@ietf.org). 3450 XML: The XML schema can be found in Section 7.4. 3452 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3454 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3455 delegated by the IESG (iesg@ietf.org). 3457 XML: The XML schema can be found in Section 7.5. 3459 10.7. VCard Parameter Value Registration 3461 This document registers a new value in the vCARD Parameter Values 3462 registry as defined by [RFC6350] with the following template: 3464 Value: main 3466 Purpose: The main telephone number, typically of an enterprise, as 3467 opposed to a direct dial number of an individual employee 3469 Conformance: This value can be used with the "TYPE" parameter 3470 applied on the "TEL" property. 3472 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3473 00 3475 11. Acknowledgments 3477 This work was originally started in NENA and has benefitted from a 3478 large number of participants in NENA standardization efforts, 3479 originally in the Long Term Definition Working Group, the Data 3480 Technical Committee and most recently the Additional Data working 3481 group. The authors are grateful for the initial work and extended 3482 comments provided by many NENA participants, including Delaine 3483 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3484 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3485 and Robert (Bob) Sherry. 3487 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3488 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 3489 comments. Guy Caron deserves special mention for his detailed review 3490 comments. 3492 12. References 3494 12.1. Normative References 3496 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 3497 Extensions (MIME) Part One: Format of Internet Message 3498 Bodies", RFC 2045, November 1996. 3500 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3501 Requirement Levels", BCP 14, RFC 2119, March 1997. 3503 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3504 Locators", RFC 2392, August 1998. 3506 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3507 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3508 and QSIG Objects", RFC 3204, December 2001. 3510 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3511 A., Peterson, J., Sparks, R., Handley, M., and E. 3512 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3513 June 2002. 3515 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3516 Extensions to the Session Initiation Protocol (SIP) for 3517 Asserted Identity within Trusted Networks", RFC 3325, 3518 November 2002. 3520 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3521 Extensions (MIME) Parameter", RFC 3459, January 2003. 3523 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3524 January 2004. 3526 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3527 Format", RFC 4119, December 2005. 3529 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3530 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3531 May 2008. 3533 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 3534 October 2008. 3536 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3537 Initiation Protocol (SIP)", RFC 5621, September 2009. 3539 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3540 August 2011. 3542 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3543 6351, August 2011. 3545 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3546 Specifications and Registration Procedures", BCP 13, RFC 3547 6838, January 2013. 3549 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 3550 July 2014. 3552 12.2. Informational References 3554 [I-D.gellens-mmusic-negotiating-human-language] 3555 Randy, R., "Negotiating Human Language in Real-Time 3556 Communications", draft-gellens-mmusic-negotiating-human- 3557 language-02 (work in progress), February 2014. 3559 [I-D.ietf-ecrit-psap-callback] 3560 Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3561 Patel, "Public Safety Answering Point (PSAP) Callback", 3562 draft-ietf-ecrit-psap-callback-13 (work in progress), 3563 October 2013. 3565 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3566 "Indicating User Agent Capabilities in the Session 3567 Initiation Protocol (SIP)", RFC 3840, August 2004. 3569 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3570 3966, December 2004. 3572 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3573 Emergency Context Resolution with Internet Technologies", 3574 RFC 5012, January 2008. 3576 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3577 Format for Presence Information Data Format Location 3578 Object (PIDF-LO)", RFC 5139, February 2008. 3580 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3581 Presence Information Data Format Location Object (PIDF-LO) 3582 Usage Clarification, Considerations, and Recommendations", 3583 RFC 5491, March 2009. 3585 [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and 3586 Framework", RFC 5582, September 2009. 3588 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3589 Thomson, "Dynamic Extensions to the Presence Information 3590 Data Format Location Object (PIDF-LO)", RFC 5962, 3591 September 2010. 3593 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3594 5985, September 2010. 3596 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3597 "Framework for Emergency Calling Using Internet 3598 Multimedia", RFC 6443, December 2011. 3600 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3601 R. George, "Specifying Civic Address Extensions in the 3602 Presence Information Data Format Location Object (PIDF- 3603 LO)", RFC 6848, January 2013. 3605 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3606 Communications Services in Support of Emergency Calling", 3607 BCP 181, RFC 6881, March 2013. 3609 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3610 Morris, J., Hansen, M., and R. Smith, "Privacy 3611 Considerations for Internet Protocols", RFC 6973, July 3612 2013. 3614 [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3615 Thomson, "Relative Location Representation", RFC 7035, 3616 October 2013. 3618 [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3619 Patel, "Public Safety Answering Point (PSAP) Callback", 3620 RFC 7090, April 2014. 3622 Appendix A. XML Schema for vCard/xCard 3624 This section contains the vCard/xCard XML schema version of the Relax 3625 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3626 XML schemas defined in this document. The schema in RFC 6351 3627 [RFC6351] is the normative source and this section is informative 3628 only. 3630 3631 3635 3641 3642 3643 vCard Format Specification 3644 3645 3646 3647 3648 3649 3650 3651 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3666 3667 3668 3670 3671 3672 3673 3674 3676 3677 3678 3680 3681 3682 3683 3684 3686 3687 3688 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3733 3734 3735 3736 3740 3741 3742 Section 5: Parameters 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3794 3795 3796 3797 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 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 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 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 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 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 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 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4667 4668 4669 4670 4671 4672 4673 4675 4676 4677 4678 4679 4680 4681 4683 4684 4685 4687 4689 4690 4691 4693 4694 4695 4696 4698 Authors' Addresses 4700 Brian Rosen 4701 NeuStar 4702 470 Conrad Dr. 4703 Mars, PA 16046 4704 US 4706 Phone: +1 724 382 1051 4707 Email: br@brianrosen.net 4708 Hannes Tschofenig 4709 (no affiliation) 4711 Email: Hannes.Tschofenig@gmx.net 4712 URI: http://www.tschofenig.priv.at 4714 Roger Marshall 4715 TeleCommunication Systems, Inc. 4716 2401 Elliott Avenue 4717 Seattle, WA 98121 4718 US 4720 Phone: +1 206 792 2424 4721 Email: rmarshall@telecomsys.com 4722 URI: http://www.telecomsys.com 4724 Randall Gellens 4725 Qualcomm Technologies, Inc. 4726 5775 Morehouse Drive 4727 San Diego, CA 92121 4728 US 4730 Email: rg+ietf@qti.qualcomm.com 4732 James Winterbottom 4733 (no affiliation) 4734 AU 4736 Email: a.james.winterbottom@gmail.com