idnits 2.17.00 (12 Aug 2021) /tmp/idnits35719/draft-ietf-ecrit-additional-data-24.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 2400 has weird spacing: '...element name=...' == Line 3025 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 13, 2014) is 2776 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 3686 -- Looks like a reference, but probably isn't: '2' on line 3688 == Missing Reference: 'This RFC' is mentioned on line 3025, but not defined ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT R. Gellens 3 Internet-Draft Qualcomm Technologies, Inc. 4 Intended status: Standards Track B. Rosen 5 Expires: April 16, 2015 NeuStar 6 H. Tschofenig 7 (no affiliation) 8 R. Marshall 9 TeleCommunication Systems, Inc. 10 J. Winterbottom 11 (no affiliation) 12 October 13, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-24.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 16, 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 . . . . . . . . . . . . . . . . . . . 15 83 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16 84 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16 85 4.2.3. Service Mobility Environment . . . . . . . . . . . . 18 86 4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 18 87 4.3. Device Information . . . . . . . . . . . . . . . . . . . 19 88 4.3.1. Device Classification . . . . . . . . . . . . . . . . 19 89 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 21 90 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 21 91 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 21 92 4.3.5. Device/Service Specific Additional Data Structure . . 22 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 . . . 23 96 4.3.8. Choosing between defining a new type of block or new 97 type of device/service specific additional data . . . 24 98 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 25 99 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 25 100 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 25 101 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 26 102 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 26 103 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29 104 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 29 105 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 29 106 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 29 107 5.1. Transmitting Blocks using the Call-Info Header . . . . . 31 108 5.2. Transmitting Blocks by Reference using the Provided-By 109 Element . . . . . . . . . . . . . . . . . . . . . . . . . 32 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 35 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 . . . . . . . . . 50 118 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 51 119 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 52 120 7.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 53 121 8. Security Considerations . . . . . . . . . . . . . . . . . . . 56 122 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 57 123 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60 124 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 60 125 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 60 126 10.1.2. Service Environment Registry . . . . . . . . . . . . 61 127 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 61 128 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 62 129 10.1.5. Service Provider Type Registry . . . . . . . . . . . 62 130 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 63 131 10.1.7. Device Classification Registry . . . . . . . . . . . 63 132 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 63 133 10.1.9. Device/Service Data Type Registry . . . . . . . . . 64 134 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 64 135 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 65 136 10.3. URN Sub-Namespace Registration for provided-by Registry 137 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 65 138 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 66 139 10.4.1. MIME Content-type Registration for 140 'application/EmergencyCallData.ProviderInfo+xml' . . 66 141 10.4.2. MIME Content-type Registration for 142 'application/EmergencyCallData.ServiceInfo+xml' . . 67 143 10.4.3. MIME Content-type Registration for 144 'application/EmergencyCallData.DeviceInfo+xml' . . . 68 145 10.4.4. MIME Content-type Registration for 146 'application/EmergencyCallData.SubscriberInfo+xml' . 69 147 10.4.5. MIME Content-type Registration for 148 'application/EmergencyCallData.Comment+xml' . . . . 70 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 . . . . . . . . . . . . . . . . . . . . . . . . . 72 155 10.5.3. Registration for 156 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 73 157 10.5.4. Registration for 158 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 74 159 10.5.5. Registration for 160 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI 161 nfo . . . . . . . . . . . . . . . . . . . . . . . . 75 162 10.5.6. Registration for 163 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 76 164 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 77 165 10.7. VCard Parameter Value Registration . . . . . . . . . . . 78 166 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78 167 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 79 168 12.1. Normative References . . . . . . . . . . . . . . . . . . 79 169 12.2. Informational References . . . . . . . . . . . . . . . . 80 170 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 81 171 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 81 172 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 104 174 1. Introduction 176 When an IP-based emergency call is initiated, a rich set of data from 177 multiple data sources is conveyed to the Public Safety Answering 178 Point (PSAP). This data includes information about the calling party 179 identity, the multimedia capabilities of the device, the request for 180 emergency services, location information, and meta-data about the 181 sources of the data. The device, the access network provider, and 182 any service provider in the call path may have even more information 183 useful for a PSAP. This document extends the basic set of data 184 communicated with an IP-based emergency call, as described in 185 [RFC6443] and [RFC6881], in order to carry additional data which may 186 be useful to an entity or call taker handling the call. This data is 187 "additional" to the basic information found in the emergency call 188 signaling used. 190 In general, there are three categories of this additional data that 191 may be transmitted with an emergency call: 193 Data Associated with a Location: Primary location data is conveyed 194 in the Presence Information Data Format Location Object (PIDF-LO) 195 data structure as defined in RFC 4119 [RFC4119] and extended by 196 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 197 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 198 geodetic location information), and [RFC7035] (for relative 199 location). This primary location data identifies the location or 200 estimated location of the caller. However, there may exist 201 additional, secondary data which is specific to the location, such 202 as floor plans, tenant and building owner contact data, heating, 203 ventilation and air conditioning (HVAC) status, etc. Such 204 secondary location data is not included in the location data 205 structure but can be transmitted using the mechanisms defined in 206 this document. Although this document does not define any 207 structures for such data, future documents may do so following the 208 procedures defined here. 210 Data Associated with a Call: While some information is carried in 211 the call setup procedure itself (as part of the SIP headers as 212 well as in the body of the SIP message), there is additional data 213 known by the device making the call and/or a service provider 214 along the path of the call. This information may include the 215 service provider contact information, subscriber identity and 216 contact information, the type of service the service provider and 217 the access network provider offer, what type of device is being 218 used, etc. Some data is broadly applicable, while other data is 219 dependent on the type of device or service. For example, a 220 medical monitoring device may have sensor data. The data 221 structures defined in this document (Data Provider Information, 222 Device Information, and Owner/Subscriber Information) all fall 223 into the category of "Data Associated with a Call". 225 Data Associated with a Caller: This is personal data about a caller, 226 such as medical information and emergency contact data. Although 227 this document does not define any structures within this category, 228 future documents may do so following the procedures defined here. 230 While this document defines data structures only within the category 231 of Data Associated with a Call, by establishing the overall framework 232 of Additional Data, along with general mechanisms for transport of 233 such data, extension points and procedures for future extensions, it 234 minimizes the work needed to carry data in the other categories. 235 Other specifications may make use of the facilities provided here. 237 For interoperability, there needs to be a common way for the 238 information conveyed to a PSAP to be encoded and identified. 239 Identification allows emergency services authorities to know during 240 call processing which types of data are present and to determine if 241 they wish to access it. A common encoding allows the data to be 242 successfully accessed. 244 This document defines an extensible set of data structures, and 245 mechanisms to transmit this data either by value or by reference, 246 either in the Session Initiation Protocol (SIP) call signaling or in 247 the Presence Information Data Format Location Object (PIDF-LO). The 248 data structures are usable by other communication systems and 249 transports as well. The data structures are defined in Section 4, 250 and the transport mechanisms (using SIP and HTTPS) are defined in 251 Section 5. 253 Each data structure described in this document is encoded as a 254 "block" of information. Each block is an XML structure with an 255 associated Multipurpose Internet Mail Extensions (MIME) type for 256 identification within transport such as SIP and HTTPS. The set of 257 blocks is extensible. Registries are defined to identify the block 258 types that may be used and to allow blocks to be included in 259 emergency call signaling. 261 2. Terminology 263 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 264 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 265 document are to be interpreted as described in RFC 2119 [RFC2119]. 267 This document also uses terminology from [RFC5012]. We use the term 268 service provider to refer to an Application Service Provider (ASP). 269 A Voice Service Provider (VSP) is a special type of ASP. With the 270 term "Access Network Provider" we refer to the Internet Access 271 Provider (IAP) and the Internet Service Provider (ISP) without 272 further distinguishing these two entities, since the difference 273 between the two is not relevant for this document. Note that the 274 roles of ASP and access network provider may be provided by a single 275 company. An Emergency Services Provider is an entity directly 276 involved in providing emergency services. This includes PSAPs, 277 dispatch, police, fire, emergency medical, other responders, and 278 other similar agencies. 280 Within each data block definition (see Section 4), the values for the 281 "Use:" label are specified as one of the following: 283 'Required': means it MUST be present in the data structure. 285 'Conditional': means it MUST be present if the specified 286 condition(s) is met. It MAY be present if the condition(s) is not 287 met. 289 'Optional': means it MAY be present. 291 vCard is a data format for representing and exchanging a variety of 292 information about individuals and other entities. For applications 293 that use XML the format defined in vCard is not immediately 294 applicable. For this purpose an XML-based encoding of the 295 information elements defined in the vCard specification has been 296 defined and the name of that specification is xCard. Since the term 297 vCard is more familiar to most readers, we use the term xCard and 298 vCard interchangeably. 300 3. Document Scope 302 The scope of this document is explicitly limited to emergency calls. 303 The data structures defined here are not appropriate to be conveyed 304 with non-emergency calls because they carry sensitive and private 305 data. 307 4. Data Structures 309 This section defines the following five data structures, each as a 310 data block. For each block we define the MIME type, and the XML 311 encoding. The five data structures are: 313 'Data Provider': This block supplies name and contact information 314 for the entity that created the data. Section 4.1 provides the 315 details. 317 'Service Information': This block supplies information about the 318 service. The description can be found in Section 4.2. 320 'Device Information': This block supplies information about the 321 device placing the call. Device information can be found in 322 Section 4.3. 324 'Owner/Subscriber': This block supplies information about the owner 325 of the device or about the subscriber. Details can be found in 326 Section 4.4. 328 'Comment': This block provides a way to supply free form human 329 readable text to the PSAP or emergency responders. This simple 330 structure is defined in Section 4.5. 332 Each block contains a mandatory element. The 333 purpose of the element is to associate all 334 blocks added by the same data provider as a unit. The 335 element associates the data provider block to 336 each of the other blocks added as a unit. Consequently, when a data 337 provider adds additional data to an emergency call (such as device 338 information) it MUST add information about itself (via the data 339 provider block) and the blocks added contain the same value in the 340 element. All blocks added by a single entity 341 at the same time MUST have the same value. 342 The value of the element has the same syntax 343 and properties (specifically, world-uniqueness) as the value of the 344 "Message-ID" message body header field specified in RFC 5322 345 [RFC5322] except that the element is not 346 enclosed in brackets (the "<" and ">" symbols are omitted). In other 347 words, the value of a element is 348 syntactically a msg-id as specified in RFC 5322 [RFC5322]. 350 Note that the xCard format is re-used in some of the data structures 351 to provide contact information. In an xCard there is no way to 352 specify a "main" telephone number. These numbers are useful to 353 emergency responders who are called to a large enterprise. This 354 document adds a new property value to the "tel" property of the TYPE 355 parameter called "main". It can be used in any xCard in additional 356 data. 358 4.1. Data Provider Information 360 This block is intended to be supplied by any service provider in the 361 path of the call or the access network provider. It includes 362 identification and contact information. This block SHOULD be 363 supplied by every service provider in the call path, and by the 364 access network provider. Devices MAY use this block to provide 365 identifying information. The MIME subtype is "application/ 366 EmergencyCallData.ProviderInfo+xml". An access network provider 367 SHOULD provide this block either by value or by reference in the 368 Provided-By section of a PIDF-LO 370 4.1.1. Data Provider String 372 Data Element: Data Provider String 374 Use: Required 376 XML Element: 378 Description: This is a plain text string suitable for displaying the 379 name of the service provider that supplied the data structure. If 380 the device creates the structure, it SHOULD use the value of the 381 contact header in the SIP INVITE. 383 Reason for Need: Inform the call taker of the identity of the entity 384 providing the data. 386 How Used by Call Taker: Allows the call taker to interpret the data 387 in this structure. The source of the information often influences 388 how the information is used, believed or verified. 390 4.1.2. Data Provider ID 392 Data Element: Data Provider ID 394 Use: Required. This data MUST be provided in order to uniquely 395 identify the service provider or access provider. 397 XML Element: 399 Description: A jurisdiction-specific code for, or the fully- 400 qualified domain name of, the access network provider or service 401 provider shown in the element that created the 402 structure. NOTE: The value SHOULD be assigned by an organization 403 appropriate for the jurisdiction. In the U.S., the provider's 404 NENA Company ID MUST appear here. Additional information can be 405 found at NENA Company Identifier Program [1] or NENA Company ID 406 [2]. The NENA Company ID MUST be in the form of a URI in the 407 following format: urn:nena:companyid:. The value 408 MAY be the fully-qualified domain name of the service provider or 409 access provider. 411 Reason for Need: Inform the call taker of the identity of the entity 412 providing the data. 414 How Used by Call Taker: Where jurisdictions have lists of providers 415 the Data Provider ID provides useful information about the data 416 source. The Data Provider ID uniquely identifies the source of 417 the data, which might be needed especially during unusual 418 circumstances and for routine logging. 420 4.1.3. Data Provider ID Series 422 Data Element: Data Provider ID Series 424 Use: Required. 426 XML Element: 428 Description: Identifies the issuer of the . The 429 Provider ID Series Registry (see Section 10.1) initially contains 430 the following valid entries: 432 * NENA 433 * EENA 435 * domain 437 Reason for Need: Identifies how to interpret the Data Provider ID. 438 The combination of ProviderIDSeries and ProviderID MUST be 439 globally unique. 441 How Used by Call Taker: Determines which provider ID registry to 442 consult for more information 444 4.1.4. Type of Data Provider 446 Data Element: Type of Data Provider 448 Use: Required. 450 XML Element: 452 Description: Identifies the type of data provider supplying the 453 data. A registry with an initial set of values is shown in 454 Figure 1 (see also Section 10.1). 456 +------------------------------+------------------------------------+ 457 | Token | Description | 458 +------------------------------+------------------------------------+ 459 |Access Network Provider | Access network service provider | 460 |Telecom Provider | Calling or origination telecom SP | 461 |Telematics Provider | A sensor based service provider, | 462 | | especially vehicle based | 463 |Language Translation Provider | A spoken language translation SP | 464 |Emergency Service Provider | An emergency service provider | 465 | | conveying information to another| 466 | | emergency service provider. | 467 |Emergency Modality Translation| An emergency call specific | 468 | | modality translation service | 469 | | e.g., for sign language | 470 |Relay Provider | A interpretation SP, for example, | 471 | | video relay for sign language | 472 | | interpreting | 473 |Other | Any other type of service provider | 474 +------------------------------+------------------------------------+ 476 Figure 1: Type of Data Provider Registry. 478 Reason for Need: Identifies the category of data provider. 480 How Used by Call Taker: This information may be helpful when 481 deciding whom to contact when further information is needed. 483 4.1.5. Data Provider Contact URI 485 Data Element: Data Provider Contact URI 487 Use: Required 489 XML Element: 491 Description: When provided by a service provider or an access 492 network provider, this information MUST be a URI to a 24/7 support 493 organization tasked to provide PSAP support for this emergency 494 call. If the call is from a device, this SHOULD be the contact 495 information of the owner of the device. The Data Provider Contact 496 URI SHOULD be a TEL URI [RFC3966] in E.164 format fully specified 497 with country code. If a TEL URI is not available, it MAY be a 498 generic SIP URI. Note that this contact information is not used 499 by PSAPs for callbacks (a call from a PSAP directly related to a 500 recently terminated emergency call, placed by the PSAP using a SIP 501 Priority header field set to "psap-callback", as described in 502 [RFC7090]). 504 Reason for Need: Additional data providers may need to be contacted 505 in error cases or other unusual circumstances. 507 How Used by Call Taker: To contact the supplier of the additional 508 data for assistance in handling the call. 510 4.1.6. Data Provider Languages(s) Supported 512 Data Element: Data Provider Language(s) supported 514 Use: Required. 516 XML Element: 518 Description: The language used by the entity at the Data Provider 519 Contact URI, as an alpha 2-character code as defined in ISO 520 639-1:2002 Codes for the representation of names of languages -- 521 Part 1: Alpha-2 code Multiple instances of this element may occur. 522 Order is significant; preferred language should appear first. The 523 content MUST reflect the languages supported at the contact URI. 525 Note that the 'language' media feature tag, defined in RFC 3840 526 [RFC3840] and the more extensive language negotiation mechanism 527 proposed with [I-D.gellens-slim-negotiating-human-language] are 528 independent of this data provider language indication. 530 Reason for Need: This information indicates if the emergency service 531 authority can directly communicate with the service provider or if 532 an interpreter will be needed. 534 How Used by Call Taker: If the call taker cannot speak any language 535 supported by the service provider, a translation service will need 536 to be added to the conversation. Alternatively, other persons at 537 the PSAP, besides the call taker, might be consulted for help 538 (depending on the urgency and the type of interaction). 540 4.1.7. xCard of Data Provider 542 Data Element: xCard of Data Provider 544 Use: Optional 546 XML Element: 548 Description: There are many fields in the xCard and the creator of 549 the data structure is encouraged to provide as much information as 550 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 551 minimum. N SHOULD contain the name of the support group or device 552 owner as appropriate. If more than one TEL property is provided, 553 a parameter from the vCard Property Value registry MUST be 554 specified on each TEL. For encoding of the xCard this 555 specification uses the XML-based encoding specified in [RFC6351], 556 referred to in this document as "xCard" 558 Reason for Need: Information needed to determine additional contact 559 information. 561 How Used by Call Taker: Assists the call taker by providing 562 additional contact information aside from what may be included in 563 the SIP INVITE or the PIDF-LO. 565 4.1.8. Subcontractor Principal 567 When the entity providing the data is a subcontractor, the Data 568 Provider Type is set to that of the primary service provider and this 569 entry is supplied to provide information regarding the subcontracting 570 entity. 572 Data Element: Subcontractor Principal 573 Use: Conditional. This data is required if the entity providing the 574 data is a subcontractor. 576 XML Element: 578 Description: Some providers outsource their obligations to handle 579 aspects of emergency services to specialized providers. If the 580 data provider is a subcontractor to another provider this element 581 contains the DataProviderString of the service provider to 582 indicate which provider the subcontractor is working for. 584 Reason for Need: Identify the entity the subcontractor works for. 586 How Used by Call Taker: Allows the call taker to understand what the 587 relationship between data providers and the service providers in 588 the path of the call are. 590 4.1.9. Subcontractor Priority 592 Data Element: Subcontractor Priority 594 Use: Conditional. This element is required if the Data Provider 595 type is set to "Subcontractor". 597 XML Element: 599 Description: If the subcontractor has to be contacted first then 600 this element MUST have the value "sub". If the provider the 601 subcontractor is working for has to be contacted first then this 602 element MUST have the value "main". 604 Reason for Need: Inform the call taker whom to contact first, if 605 support is needed. 607 How Used by Call Taker: To decide which entity to contact first if 608 assistance is needed. 610 4.1.10. ProviderInfo Example 612 613 616 12345 617 string0987654321@example.org 618 619 Example VoIP Provider 620 621 urn:nena:companyid:ID123 622 NENA 623 Telecom Provider 624 tel:+1-201-555-0123 625 EN 626 628 629 Hannes Tschofenig 630 631 Hannes 632 Tschofenig 633 634 635 Dipl. Ing. 636 637 --0203 638 639 20090808T1430-0500 640 641 M 642 643 1 644 645 de 646 647 648 2 649 650 en 651 652 653 work 654 655 Example VoIP Provider 656 657 658 659 work 660 664 665 666 667 Linnoitustie 6 668 Espoo 669 Uusimaa 670 02600 671 Finland 672 673 674 675 676 work 677 voice 678 679 680 tel:+358 50 4871445 681 682 683 work 684 685 hannes.tschofenig@nsn.com 686 687 688 work 689 690 geo:60.210796,24.812924 691 692 693 home 694 695 696 http://www.tschofenig.priv.at/key.asc 697 698 699 Finland/Helsinki 700 701 home 702 703 http://www.tschofenig.priv.at 704 705 706 707 709 Figure 2: EmergencyCallData.ProviderInfo Example. 711 4.2. Service Information 713 This block describes the service that the service provider provides 714 to the caller. It SHOULD be included by all SPs in the path of the 715 call. The mime subtype is "application/ 716 EmergencyCallData.ServiceInfo+xml". 718 4.2.1. Service Environment 720 Data Element: Service Environment 722 Use: Optional when a 'ServiceType' value is 'wireless'; required 723 otherwise. 725 XML Element: 727 Description: This element defines whether a call is from a business 728 or residence caller. Currently, the only valid entries are 729 'Business', 'Residence', and 'unknown'. New values can be defined 730 via the registry created in Figure 22. 732 Reason for Need: To provide context and a hint when determining 733 equipment and manpower requirements. 735 How Used by Call Taker: Information may be used to provide context 736 and a hint to assist in determining equipment and manpower 737 requirements for emergency responders. Because there are cases 738 where the service provider does not know (such as anonymous pre- 739 paid service), and the type of service does not neccessarily 740 reflect the nature of the premises (for example, a business line 741 installed in a residence, or wireless service), and the registry 742 is not all encompassing, therefore this is at best advisory 743 information, but since it mimics a similar capability in some 744 current emergency calling systems (e.g., a field in the Automatic 745 Location Information (ALI) information used with legacy North 746 American wireline systems), it is known to be valuable. The 747 service provider uses its best information (such as a rate plan, 748 facilities used to deliver service or service description) to 749 determine the information and is not responsible for determining 750 the actual characteristics of the location from which the call 751 originated. Because the usefulness is unknown (and less clear) 752 for wireless, this element is OPTIONAL for wireless and REQUIRED 753 otherwise. 755 4.2.2. Service Type 757 Data Element: Service Delivered by Provider to End User 759 Use: Required 761 XML Element: 762 Description: This defines the type of service over which the call is 763 placed. The implied mobility of this service cannot be relied 764 upon. A registry with an initial set of values is defined in 765 Figure 3. 767 +--------------+----------------------------------------+ 768 | Name | Description | 769 +--------------+----------------------------------------+ 770 | wireless | Wireless Telephone Service: Includes | 771 | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | 772 | | not satellite) | 773 | coin | Fixed public pay/coin telephones: Any | 774 | | coin or credit card operated device | 775 | one-way | One way outbound service | 776 | prison | Inmate call/service | 777 | temp | Soft dial tone/quick service/warm | 778 | | disconnect/suspended | 779 | MLTS-hosted | Hosted multi-line telephone system | 780 | | such as Centrex | 781 | MLTS-local | Local multi-line telephone system, | 782 | | includes all PBX, key systems, | 783 | | Shared Tenant Service | 784 | sensor- | 785 | unattended | These are devices that generate DATA | 786 | | ONLY. This is a one-way information | 787 | | transmit without interactive media | 788 | sensor- | | 789 | attended | Devices that are supported by a | 790 | | monitoring service provider or that | 791 | | are capable of supporting interactive| 792 | | media | 793 | POTS | Wireline: Plain Old Telephone Service | 794 | VOIP | An over-the-top service that provides | 795 | | communication over arbitrary Internet| 796 | | access (fixed, nomadic, mobile) | 797 | remote | Off premise extension | 798 | relay | A service where there is a human third | 799 | | party agent who provides additional | 800 | | assistance. This includes sign | 801 | | language relay and telematics | 802 | | services that provide a human on the | 803 | | call. | 804 +--------------+----------------------------------------+ 806 Figure 3: Service Delivered by Provider to End User Registry. 808 More than one value MAY be returned. For example, a VoIP inmate 809 telephone service is a reasonable combination. 811 Reason for Need: Knowing the type of service may assist the PSAP 812 with the handling of the call. 814 How Used by Call Taker: Call takers often use this information to 815 determine what kinds of questions to ask callers, and how much to 816 rely on supportive information. An emergency call from a prison 817 is treated differently than a call from a sensor device. As the 818 information is not always available, and the registry is not all 819 encompassing, this is at best advisory information, but since it 820 mimics a similar capability in some current emergency calling 821 systems, it is known to be valuable. 823 4.2.3. Service Mobility Environment 825 Data Element: Service Mobility Environment 827 Use: Required 829 XML Element: 831 Description: This provides the service provider's view of the 832 mobility of the caller's device. As the service provider may not 833 know the characteristics of the actual device or access network 834 used, the value MUST NOT be relied upon. The registry specified 835 in Figure 23 reflects the following initial valid entries: 837 * Mobile: the device is able to move at any time 839 * Fixed: the device is not expected to move unless the service is 840 relocated 842 * Nomadic: the device is not expected to change its point of 843 attachment while on a call 845 * Unknown: no information is known about the service mobility 846 environment for the device 848 Reason for Need: Knowing the service provider's belief of mobility 849 may assist the PSAP with the handling of the call. 851 How Used by Call Taker: To determine whether to assume the location 852 of the caller might change. 854 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 1228 FEABFECD901@example.org 1229 1230 1231 1232 1233 Simon Perreault 1234 1235 Perreault 1236 Simon 1237 1238 1239 ing. jr 1240 M.Sc. 1241 1242 --0203 1243 1244 20090808T1430-0500 1245 1246 M 1247 1248 1 1249 1250 fr 1251 1252 1253 2 1254 1255 en 1256 1257 1258 work 1259 1260 Viagenie 1261 1262 1263 1264 work 1265 1269 1270 1271 1272 2875 boul. Laurier, suite D2-630 1273 Quebec 1274 QC 1275 G1V 2M2 1276 Canada 1277 1278 1279 1280 1281 work 1282 voice 1283 1284 1285 tel:+1-418-656-9254;ext=102 1286 1287 1288 1289 1290 work 1291 text 1292 voice 1293 cell 1294 video 1295 1296 1297 tel:+1-418-262-6501 1298 1299 1300 work 1301 1302 simon.perreault@viagenie.ca 1303 1304 1305 work 1306 1307 geo:46.766336,-71.28955 1308 1309 1310 work 1311 1312 1313 http://www.viagenie.ca/simon.perreault/simon.asc 1314 1315 1316 America/Montreal 1317 1318 home 1319 1320 http://nomis80.org 1321 1322 1323 1325 1326 1328 Figure 8: EmergencyCallData.SubscriberInfo Example. 1330 4.5. Comment 1332 This block provides a mechanism for the data provider to supply 1333 extra, human readable information to the PSAP. It is not intended 1334 for a general purpose extension mechanism nor does it aim to provide 1335 machine-readable content. The mime subtype is "application/ 1336 EmergencyCallData.Comment+xml" 1338 4.5.1. Comment 1340 Data Element: EmergencyCallData.Comment 1342 Use: Optional 1344 XML Element: 1346 Description: Human readable text providing additional information to 1347 the PSAP staff. 1349 Reason for Need: Explanatory information for values in the data 1350 structure. 1352 How Used by Call Taker: To interpret the data provided. 1354 4.5.2. EmergencyCallData.Comment Example 1356 1357 1360 string0987654321@example.org 1361 1362 This is an example text. 1363 1365 Figure 9: EmergencyCallData.Comment Example. 1367 5. Data Transport Mechanisms 1369 This section defines how to convey additional data to an emergency 1370 service provider. Two different means are specified: the first uses 1371 the call signaling; the second uses the element of a 1372 PIDF-LO [RFC4119]. 1374 1. First, the ability to embed a Uniform Resource Identifier (URI) 1375 in an existing SIP header field, the Call-Info header, is 1376 defined. The URI points to the additional data structure. The 1377 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1378 document adds a new compound token starting with the value 1379 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1380 the "purpose" parameter is set to a value starting with 1381 'EmergencyCallData', then the Call-Info header contains either an 1382 HTTPS URL pointing to an external resource or a CID (content 1383 indirection) URI that allows the data structure to be placed in 1384 the body of the SIP message. The "purpose" parameter also 1385 indicates the kind of data (by its MIME type) that is available 1386 at the URI. As the data is conveyed using a URI in the SIP 1387 signaling, the data itself may reside on an external resource, or 1388 may be contained within the body of the SIP message. When the 1389 URI refers to data at an external resource, the data is said to 1390 be passed by reference. When the URI refers to data contained 1391 within the body of the SIP message, the data is said to be passed 1392 by value. A PSAP or emergency responder is able to examine the 1393 type of data provided and selectively inspect the data it is 1394 interested in, while forwarding all of it (the values or 1395 references) to downstream entities. To be conveyed in a SIP 1396 body, additional data about a call is defined as a series of MIME 1397 objects. Each block defined in this document is an XML data 1398 structure identified by its MIME type. (Blocks defined by others 1399 may be encoded in XML or not, as identified by their MIME 1400 registration.) As usual, whenever more than one MIME part is 1401 included in the body of a message, MIME-multipart (i.e., 1402 'multipart/mixed') encloses them all. This document defines a 1403 set of XML schemas and MIME types used for each block defined 1404 here. When additional data is passed by value in the SIP 1405 signaling, each CID URL points to one block in the body. 1406 Multiple URIs are used within a Call-Info header field (or 1407 multiple Call-Info header fields) to point to multiple blocks. 1408 When additional data is provided by reference (in SIP signaling 1409 or Provided-By), each HTTPS URL references one block; the data is 1410 retrieved with an HTTPS GET operation, which returns one of the 1411 blocks as an object (the blocks defined here are returned as XML 1412 objects). 1414 2. Second, the ability to embed additional data structures in the 1415 element of a PIDF-LO [RFC4119] is defined. In 1416 addition to service providers in the call path, the access 1417 network provider may also have similar information that may be 1418 valuable to the PSAP. The access network provider MAY provide 1419 location in the form of a PIDF-LO from a location server via a 1420 location configuration protocol. The data structures described 1421 in this document are not specific to the location itself, but 1422 rather provides descriptive information having to do with the 1423 immediate circumstances about the provision of the location (who 1424 the access network is, how to contact that entity, what kind of 1425 service the access network provides, subscriber information, 1426 etc.). This data is similar in nearly every respect to the data 1427 known by service providers in the path of the call. When the 1428 access network provider and service provider are separate 1429 entities, the access network does not participate in the 1430 application layer signaling (and hence cannot add a Call-Info 1431 header field to the SIP message), but may provide location 1432 information in a PIDF-LO object to assist in locating the 1433 caller's device. The element of the PIDF-LO is a 1434 mechanism for the access network provider to supply the 1435 information about the entity or organization that supplied this 1436 location information. For this reason, this document describes a 1437 namespace per RFC 4119 for inclusion in the element 1438 of a PIDF-LO for adding information known to the access network 1439 provider. The access network provider SHOULD provide additional 1440 data within a Provided-By element of a PDIF-LO it returns for 1441 emergency use (e.g., if requested with a HELD "responseTime" 1442 attribute of "emergencyRouting" or "emergencyDispatch" 1443 [RFC5985]). 1445 One or more blocks of data registered in the Emergency Call 1446 Additional Data registry, as defined in Section 10.1, may be included 1447 or referenced in the SIP signaling (using the Call-Info header field) 1448 or in the element of a PIDF-LO. Every block must be 1449 one of the types in the registry. Since the data of an emergency 1450 call may come from multiple sources, the data itself needs 1451 information describing the source. Consequently, each entity adding 1452 additional data MUST supply the "Data Provider" block. All other 1453 blocks are optional, but each entity SHOULD supply any blocks where 1454 it has at least some of the information in the block. 1456 5.1. Transmitting Blocks using the Call-Info Header 1458 A URI to a block MAY be inserted in a SIP request or response method 1459 (most often INVITE or MESSAGE) with a Call-Info header field 1460 containing a purpose value starting with 'EmergencyCallData' and the 1461 type of data available at the URI. The type of data is denoted by 1462 including the root of the MIME type (not including the 1463 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1464 separator. For example, when referencing a block with MIME type 1465 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1466 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1467 "Call-Info" header field for this would be: 1469 Call-Info: https://www.example.com/23sedde3; 1470 purpose="EmergencyCallData.ProviderInfo" 1472 A Call-info header with a purpose value starting with 1473 'EmergencyCallData' MUST only be sent on an emergency call, which can 1474 be ascertained by the presence of an emergency service urn in a Route 1475 header of a SIP message. 1477 If the data is provided by reference, an HTTPS URI MUST be included 1478 and consequently Transport Layer Security (TLS) protection is applied 1479 for protecting the retrieval of the information. 1481 The data may also be supplied by value in a SIP message. In this 1482 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1483 referencing the MIME body part. 1485 More than one Call-Info header with a purpose value starting with 1486 'EmergencyCallData' can be expected, but at least one MUST be 1487 provided. The device MUST provide one if it knows no service 1488 provider is in the path of the call. The device MAY insert one if it 1489 uses a service provider. Any service provider in the path of the 1490 call MUST insert its own. For example, a device, a telematics 1491 service provider in the call path, as well as the mobile carrier 1492 handling the call will each provide one. There may be circumstances 1493 where there is a service provider who is unaware that the call is an 1494 emergency call and cannot reasonably be expected to determine that it 1495 is an emergency call. In that case, that service provider is not 1496 expected to provide EmergencyCallData. 1498 5.2. Transmitting Blocks by Reference using the Provided-By Element 1500 The 'EmergencyCallDataReference' element is used to transmit an 1501 additional data block by reference within a 'Provided-By' element of 1502 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1503 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1504 type of data block referenced. The value of 'ref' is an HTTPS URL 1505 that resolves to a data structure with information about the call. 1506 The value of 'purpose' is the same as used in a 'Call-Info' header 1507 field (as specified in Section 5.1). 1509 For example, to reference a block with MIME type 'application/ 1510 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1511 to 'EmergencyCallData.ProviderInfo'. An example 1512 'EmergencyCallDataReference' element for this would be: 1514 1517 The 'EmergencyCallDataReference' element transmits one additional 1518 data block; multiple additional data blocks may be transmitted by 1519 using multiple 'EmergencyCallDataReference' elements. 1521 For example: 1523 1525 flurbit735@es.example.com 1526 1528 1532 1536 1540 1542 Example Provided-By by Reference. 1544 5.3. Transmitting Blocks by Value using the Provided-By Element 1546 It is RECOMMENDED that access networks supply the data specified in 1547 this document by reference, but they MAY provide the data by value. 1549 The 'EmergencyCallDataValue' element is used to transmit one or more 1550 additional data blocks by value within a 'Provided-By' element of a 1551 PIDF-LO. Each block being transmitted is placed (as a child element) 1552 inside the 'EmergencyCallDataValue' element. (The same XML structure 1553 as would be contained in the corresponding MIME type body part is 1554 placed inside the 'EmergencyCallDataValue' element.) 1556 For example: 1558 1561 1563 1566 flurbit735@es.example.com 1567 1568 Access Network Examples, Inc 1569 1570 urn:nena:companyid:Test 1571 NENA 1572 Access Network Provider 1573 1574 tel:+1 555-555-0897 1575 EN 1576 1578 1581 flurbit735@es.example.com 1582 1583 This is an example text. 1584 1585 1587 1589 1591 Example Provided-By by Value. 1593 5.4. The Content-Disposition Parameter 1595 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1596 It updates and clarifies handling originally defined in RFC 3261 1597 [RFC3261] based on implementation experience. While RFC 3261 did not 1598 mandate support for 'multipart' message bodies, 'multipart/mixed' 1599 MIME bodies are used by many extensions (including this document) 1600 today. For example, adding a PIDF-LO, SDP, and additional data in 1601 body of a SIP message requires a 'multipart' message body. 1603 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1604 parameter for the Content-Disposition header field. These RFCs 1605 describe how a UAS reacts if it receives a message body whose content 1606 type or disposition type it does not understand. If the 'handling' 1607 parameter has the value "optional", the UAS ignores the message body. 1608 If the 'handling' parameter has the value "required", the UAS returns 1609 a 415 (Unsupported Media Type) response. The 'by-reference' 1610 disposition type allows a SIP message to contain a reference to the 1611 body part, and the SIP UA processes the body part according to the 1612 reference. This is the case for the Call-info header containing a 1613 Content Indirection (CID) URL. 1615 As an example, a SIP message indicates the Content-Disposition 1616 parameter in the body of the SIP message as shown in Figure 10. 1618 Content-Type: application/sdp 1620 ...Omit Content-Disposition here; defaults are ok 1621 ...SDP goes in here 1623 --boundary1 1625 Content-Type: application/pidf+xml 1626 Content-ID: 1627 Content-Disposition: by-reference;handling=optional 1629 ...PIDF-LO goes in here 1631 --boundary1-- 1633 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1634 Content-ID: <1234567890@atlanta.example.com> 1635 Content-Disposition: by-reference; handling=optional 1637 ...Data provider information data goes in here 1639 --boundary1-- 1641 Figure 10: Example for use of the Content-Disposition Parameter in 1642 SIP. 1644 6. Examples 1646 This section illustrates a longer and more complex example, as shown 1647 in Figure 11. In this example additional data is added by the end 1648 device, included by the VoIP provider (via the PIDF-LO), and provided 1649 by the access network provider. 1651 O +----+ [============] [=============] 1652 /|\ | UA | [ Access ] [ VoIP ] 1653 | +----+ [ Network ] [ Provider ] 1654 / \ [ Provider ] [ example.org ] 1655 [ ] [ ] 1656 (1) [ ] (2) [ ] 1657 Emergency Call [ ] Emergency Call [ ] 1658 -------------------------------------------------------> ] 1659 +Device Info [ ] +Device Info [ ] 1660 +Data Prov. Info [ ^ ] +Data Provider Info [ | ] 1661 +Location URI [=======.====] +Location URI [==|==========] 1662 . | 1663 . | 1664 +Location . [==============] | 1665 +Owner/Subscriber Info . [ ] (3) | 1666 +Device Info . (4) [ <----------+ 1667 +Data Provider Info #3 ..........> ] Emergency Call 1668 [ ] +Device Info 1669 [ PSAP ] +Data Prov. Info #2 1670 [ ] +Location URI 1671 [==============] 1673 Legend: 1675 --- Emergency Call Setup Procedure 1676 ... Location Retrieval/Response 1678 Figure 11: Additional Data Example Flow 1680 The example scenario starts with the end device itself adding device 1681 information, owner/subscriber information, a location URI, and data 1682 provider information to the outgoing emergency call setup message 1683 (see step #1 in Figure 11). The SIP INVITE example is shown in 1684 Figure 12. 1686 INVITE urn:service:sos SIP/2.0 1687 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1688 Max-Forwards: 70 1689 To: 1690 From: Hannes Tschofenig ;tag=9fxced76sl 1691 Call-ID: 3848276298220188511@example.com 1692 Call-Info: 1693 ;purpose=icon, 1694 ;purpose=info, 1695 1696 ;purpose=EmergencyCallData.ProviderInfo, 1698 1699 ;purpose=EmergencyCallData.DeviceInfo 1700 Geolocation: 1701 Geolocation-Routing: yes 1702 Accept: application/sdp, application/pidf+xml, 1703 application/EmergencyCallData.ProviderInfo+xml 1704 CSeq: 31862 INVITE 1705 Contact: 1706 Content-Type: multipart/mixed; boundary=boundary1 1708 Content-Length: ... 1710 --boundary1 1712 Content-Type: application/sdp 1714 ...SDP goes here 1716 --boundary1-- 1718 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1719 Content-ID: <0123456789@atlanta.example.com> 1720 Content-Disposition: by-reference;handling=optional 1721 1723 1726 d4b3072df09876543@[93.184.216.119] 1727 1728 laptop 1729 00-0d-4b-30-72-df 1731 1733 --boundary1-- 1735 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1736 Content-ID: <1234567890@atlanta.example.com> 1737 Content-Disposition: by-reference;handling=optional 1738 1739 1742 12345 1743 d4b3072df09876543@[93.184.216.119] 1744 1745 Hannes Tschofenig 1746 1747 Other 1748 tel:+1-555-555-0123 1749 EN 1750 1752 1753 Hannes Tschofenig 1754 1755 Hannes 1756 Tschofenig 1757 1758 1759 Dipl. Ing. 1760 1761 --0203 1762 1763 20090808T1430-0500 1764 1765 M 1766 1767 1 1768 1769 de 1770 1771 1772 2 1773 1774 en 1775 1776 1777 1778 work 1779 1783 1784 1785 1786 Linnoitustie 6 1787 Espoo 1788 Uusimaa 1789 02600 1790 Finland 1791 1792 1793 1794 1795 work 1796 voice 1797 1798 1799 tel:+358 50 4871445 1800 1801 1802 work 1803 1804 hannes.tschofenig@nsn.com 1805 1806 1807 work 1808 1809 geo:60.210796,24.812924 1810 1811 1812 1813 home 1814 1815 https://www.example.com/key.asc 1816 1817 1818 Finland/Helsinki 1819 1820 home 1821 1822 http://example.com/hannes.tschofenig 1823 1824 1825 1826 1827 1828 --boundary1-- 1830 Figure 12: End Device sending SIP INVITE with Additional Data. 1832 In this example, information available to the access network provider 1833 is included in the call setup message only indirectly via the use of 1834 the location reference. The PSAP has to retrieve it via a separate 1835 look-up step. Since the access network provider and the VoIP service 1836 provider are two independent entities in this scenario, the access 1837 network provider is not involved in application layer exchanges; the 1838 SIP INVITE transits the access network transparently, as illustrated 1839 in steps #1 and #2. The access network does not alter the SIP 1840 INVITE. 1842 The VoIP service provider receives the message and determines based 1843 on the Service URN that the incoming request is an emergency call. 1844 It performs typical emergency services related tasks, including 1845 location-based routing, and adds additional data, namely service and 1846 subscriber information as well as data provider information #2, to 1847 the outgoing message. For the example we assume a VoIP service 1848 provider that deploys a back-to-back user agent allowing additional 1849 data to be included in the body of the SIP message (rather than per 1850 reference in the header), which allows us to illustrate the use of 1851 multiple data provider info blocks. The resulting message is shown 1852 in Figure 13. The SIP INVITE is sent to the PSAP in step #3. 1854 INVITE sips:psap@example.org SIP/2.0 1855 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1856 Max-Forwards: 70 1857 To: 1858 From: Hannes Tschofenig ;tag=9fxced76sl 1859 Call-ID: 3848276298220188511@example.com 1860 Call-Info: 1861 ;purpose=icon, 1862 ;purpose=info, 1863 1864 ;purpose=EmergencyCallData.ProviderInfo 1865 1866 ;purpose=EmergencyCallData.DeviceInfo 1867 Call-Info: 1868 ;purpose=EmergencyCallData.ServiceInfo 1869 Call-Info: 1870 ;purpose=EmergencyCallData.ProviderInfo 1871 Geolocation: 1872 Geolocation-Routing: yes 1873 Accept: application/sdp, application/pidf+xml, 1874 application/EmergencyCallData.ProviderInfo+xml 1875 CSeq: 31862 INVITE 1876 Contact: 1877 Content-Type: multipart/mixed; boundary=boundary1 1879 Content-Length: ... 1881 --boundary1 1883 Content-Type: application/sdp 1885 ...SDP goes here 1887 --boundary1-- 1888 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1889 Content-ID: <0123456789@atlanta.example.com> 1890 Content-Disposition: by-reference;handling=optional 1891 1893 1896 d4b3072df09876543@[93.184.216.119] 1897 1898 laptop 1899 00-0d-4b-30-72-df 1901 1903 --boundary1-- 1905 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1906 Content-ID: <1234567890@atlanta.example.com> 1907 Content-Disposition: by-reference;handling=optional 1908 1909 1912 d4b3072df09876543@[93.184.216.119] 1913 1914 Hannes Tschofenig 1915 1916 Other 1917 tel:+1-555-555-0123 1918 EN 1919 1921 1922 Hannes Tschofenig 1923 1924 Hannes 1925 Tschofenig 1926 1927 1928 Dipl. Ing. 1929 1930 --0203 1931 1932 20090808T1430-0500 1933 1934 M 1935 1936 1 1937 1938 de 1939 1940 1941 2 1942 1943 en 1944 1945 1946 1947 work 1948 1952 1953 1954 1955 Linnoitustie 6 1956 Espoo 1957 Uusimaa 1958 02600 1959 Finland 1960 1961 1962 1963 1964 work 1965 voice 1966 1967 1968 tel:+358 50 4871445 1969 1970 1971 work 1972 1973 hannes.tschofenig@nsn.com 1974 1975 1976 work 1977 1978 geo:60.210796,24.812924 1979 1980 1981 1982 home 1983 1984 https://www.example.com/key.asc 1985 1986 1987 Finland/Helsinki 1988 1989 home 1990 1991 http://example.com/hannes.tschofenig 1992 1993 1994 1995 1996 1998 --boundary1-- 2000 Content-Type: application/EmergencyCallData.ServiceInfo+xml 2001 Content-ID: 2002 Content-Disposition: by-reference;handling=optional 2003 2004 2007 string0987654321@example.org 2008 2009 Residence 2010 VOIP 2011 Unknown 2012 2014 --boundary1-- 2016 Content-Type: application/EmergencyCallData.ProviderInfo+xml 2017 Content-ID: 2018 Content-Disposition: by-reference;handling=optional 2019 2020 2023 string0987654321@example.org 2024 2025 Example VoIP Provider 2026 2027 urn:nena:companyid:ID123 2028 NENA 2029 Service Provider 2030 sip:voip-provider@example.com 2031 EN 2032 2034 2035 John Doe 2036 2037 John 2038 Doe 2039 2040 2041 2042 2043 --0203 2044 2045 20090808T1430-0500 2046 2047 M 2048 2049 1 2050 2051 en 2052 2053 2054 work 2055 2056 Example VoIP Provider 2057 2058 2059 2060 work 2061 2064 2065 2066 2067 Downing Street 10 2068 London 2069 2070 SW1A 2AA 2071 UK 2072 2073 2074 2075 2076 work 2077 voice 2078 2079 2080 sips:john.doe@example.com 2081 2082 2083 work 2084 2085 john.doe@example.com 2086 2087 2088 work 2089 2090 geo:51.503396, 0.127640 2091 2092 Europe/London 2093 2094 home 2095 2096 http://www.example.com/john.doe 2097 2098 2099 2100 2102 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2104 Finally, the PSAP requests location information from the access 2105 network provider. The response is shown in Figure 14. Along with 2106 the location information, additional data is provided in the 2107 element of the PIDF-LO. This request and response is 2108 step #4. 2110 2111 2116 2117 2118 2119 2121 AU 2122 NSW 2123 Wollongong 2124 North Wollongong 2125 Flinders 2126 Street 2127 Campbell Street 2128 Gilligan's Island 2129 Corner 2130 Video Rental Store 2131 2500 2132 Westerns and Classics 2133 store 2134 Private Box 15 2135 2136 2137 2138 true 2139 2140 2013-12-10T20:00:00Z 2141 2142 2143 802.11 2145 2148 2152 2153 2156 88QV4FpfZ976T@example.com 2157 2158 University of Example 2159 2160 urn:nena:companyid:uoi 2161 NENA 2162 Other 2163 tel:+1 555-824-5222 2164 EN 2165 2167 2169 88QV4FpfZ976T@example.com 2170 2171 This is an example text. 2172 2174 2176 2177 2178 mac:00-0d-4b-30-72-df 2179 2013-07-09T20:57:29Z 2180 2181 2183 Figure 14: Access Network Provider returning PIDF-LO with Additional 2184 Data. 2186 7. XML Schemas 2188 This section defines the XML schemas of the five data blocks. 2189 Additionally, the Provided-By schema is specified. 2191 7.1. EmergencyCallData.ProviderInfo XML Schema 2193 2194 2204 2207 2209 2210 2211 2212 2213 2215 2219 2222 2223 2224 2225 2226 2227 2229 2230 2231 2234 2237 2240 2243 2246 2249 2252 2256 2259 2263 2265 2266 2268 2269 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2271 7.2. EmergencyCallData.ServiceInfo XML Schema 2273 2274 2283 2286 2289 2290 2291 2294 2297 2301 2304 2306 2307 2309 2311 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2313 7.3. EmergencyCallData.DeviceInfo XML Schema 2315 2316 2325 2328 2331 2332 2333 2336 2339 2342 2345 2347 2348 2349 2350 2353 2354 2355 2356 2358 2361 2364 2366 2367 2369 2371 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2373 7.4. EmergencyCallData.SubscriberInfo XML Schema 2374 2375 2386 2389 2391 2394 2395 2396 2397 2400 2404 2406 2407 2409 2410 2412 2414 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2416 7.5. EmergencyCallData.Comment XML Schema 2417 2418 2427 2430 2433 2434 2435 2438 2442 2444 2445 2447 2448 2449 2450 2451 2452 2453 2455 2457 Figure 19: EmergencyCallData.Comment XML Schema. 2459 7.6. Provided-By XML Schema 2461 This section defines the Provided-By schema. 2463 2464 2479 2481 2483 2485 2487 2490 2492 2493 2494 2497 2501 2505 2508 2510 2511 2513 2514 2515 2516 2517 2519 2520 2522 2524 2525 2526 2528 2530 2531 2532 2535 2538 2541 2544 2548 2551 2552 2554 2556 Figure 20: Provided-By XML Schema. 2558 8. Security Considerations 2560 The data structures described in this document contain information 2561 usually considered private. When information is provided by value, 2562 entities that are a party to the SIP signaling (such as proxy servers 2563 and back-to-back user agents) will have access to it and need to 2564 protect it against inappropriate disclosure. An entity that is able 2565 to eavesdrop on the SIP signaling will also have access. Some media 2566 (such as in the clear Wi-Fi) is more vulnerable than others (such as 2567 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that 2568 protect against eavesdropping (such as Transport Layer Security 2569 (TLS)) SHOULD be preferentially used whenever feasible. When 2570 information is provided by reference, HTTPS is specified for 2571 dereferencing, and the provider of the information is REQUIRED to 2572 validate the credentials of the requester. While the creation of a 2573 public key infrastructure (PKI) that has global scope may be 2574 difficult, the alternatives to creating devices and services that can 2575 provide critical information securely are more daunting. The 2576 provider of the information MAY enforce any policy it wishes to use, 2577 but PSAPs and responder agencies SHOULD deploy a PKI so that 2578 providers of additional data can check the certificate of the client 2579 and decide the appropriate policy to enforce based on that 2580 certificate. 2582 Ideally, the PSAP and emergency responders will be given credentials 2583 signed by an authority trusted by the data provider. In most 2584 circumstances, nationally recognized credentials would be sufficient, 2585 and if the emergency services arranges a PKI, data providers could be 2586 provisioned with the root CA public key for a given nation. Some 2587 nations are developing a PKI for this, and related, purposes. Since 2588 calls could be made from devices where the device and/or the service 2589 provider(s) are not local to the emergency services authorities, 2590 globally recognized credentials are useful. This might be 2591 accomplished by extending the notion of the "forest guide" described 2592 in [RFC5582] to allow the forest guide to provide the credential of 2593 the PKI root for areas for which it has coverage information, but 2594 standards for such a mechanism are not yet available. In its 2595 absence, the data provider will need to obtain by out of band means 2596 the root CA credentials for any areas to which it is willing to 2597 provide additional data. With the credential of the root CA for a 2598 national emergency services PKI, the data provider server can 2599 validate the credentials of an entity requesting additional data by 2600 reference. 2602 The data provider also needs a credential that can be verified by the 2603 emergency services to know that it is receiving data from an 2604 authorized server. The emergency services authorities could provide 2605 credentials, distinguishable from credentials provided to emergency 2606 responders and PSAPs, which could be used to validate data providers. 2607 Such credentials would have to be acceptable to any PSAP or responder 2608 that could receive a call with additional data supplied by that 2609 provider. This would be extensible to global credential validation 2610 using the forest guide as mentioned above. In the absence of such 2611 credentials, the emergency services authorities could maintain a list 2612 of local data providers' credentials as provided to them out of band. 2613 At a minimum, the emergency services authorities could obtain a 2614 credential from the DNS entry of the domain in the Additional Data 2615 URI to at least validate that the server is known to the domain 2616 providing the URI. 2618 Data provided by devices by reference have similar credential 2619 validation issues as for service providers, and the solutions are the 2620 same. 2622 Much of the information supplied by service providers and devices is 2623 private and confidential; service providers and devices generally go 2624 to lengths to protect this information; disclosing it in the context 2625 of an emergency call is a trade-off to protect the greater interest 2626 of the customer in an emergency. 2628 Neither service providers nor devices will supply private information 2629 unless the call is recognized as an emergency call. In cellular 2630 telephony systems (such as those using 3GPP IMS), there are different 2631 procedures for an originating device to place an emergency versus a 2632 normal call. If a call that is really an emergency call is initiated 2633 as a normal call and the cellular service provider recognizes this, 2634 3GPP IMS permits the service provider to either accept the call 2635 anyway or reject it with a specific code that instructs the device to 2636 retry the call as an emergency call. Service providers SHOULD choose 2637 the latter, because otherwise the device will not have included the 2638 information specified in this document (since the device didn't 2639 recognize the call as being an emergency call). 2641 9. Privacy Considerations 2643 This document enables functionality for conveying additional 2644 information about the caller and the caller's device and service to 2645 the callee. Some of this information is personal data and therefore 2646 privacy concerns arise. An explicit privacy indicator for 2647 information directly relating to the caller's identity is defined and 2648 use is mandatory. However, observance of this request for privacy 2649 and what information it relates to is determined by the destination 2650 jurisdiction. 2652 There are a number of privacy concerns with non-emergency real-time 2653 communication services that are also applicable to emergency calling. 2655 Data protection regulation world-wide has, however, decided to create 2656 exceptions for emergency services since the drawbacks of disclosing 2657 personal data are outweighed by the benefit for the emergency caller. 2658 Hence, the data protection rights of individuals are commonly waived 2659 for emergency situations. There are, however, still various 2660 countries that offer some degree of anonymity for the caller towards 2661 PSAP call takers. 2663 The functionality defined in this document, however, far exceeds the 2664 amount of information sharing found in the legacy POTS system. For 2665 this reason there are additional privacy threats to consider, which 2666 are described in more detail in [RFC6973]. 2668 Stored Data Compromise: There is an increased risk of stored data 2669 compromise since additional data is collected and stored in 2670 databases. Without adequate measures to secure stored data from 2671 unauthorized or inappropriate access at access network providers, 2672 service providers, end devices, as well as PSAPs, individuals are 2673 exposed to potential financial, reputational, or physical harm. 2675 Misattribution: If the personal data collected and conveyed is 2676 incorrect or inaccurate then this may lead to misattribution. 2677 Misattribution occurs when data or communications related to one 2678 individual are attributed to another. 2680 Identification: By the nature of the additional data and its 2681 capability to provide much richer information about the caller, 2682 the call, and the location, the calling party is identified in a 2683 much better way. Some users may feel uncomfortable with this 2684 degree of information sharing even in emergency services 2685 situations. 2687 Secondary Use: There is a risk of secondary use, which is the use of 2688 collected information about an individual without the individual's 2689 consent for a purpose different from that for which the 2690 information was collected. The stated purpose of the additional 2691 data is for emergency services purposes but theoretically the same 2692 information could be used for any other call as well. 2693 Additionally, parties involved in the emergency call may retain 2694 the obtained information and may re-use it for other, non- 2695 emergency services purposes. 2697 Disclosure: When the data defined in this document is not properly 2698 protected (while in transit with traditional communication 2699 security techniques, and while stored using access control 2700 mechanisms) there is the risk of disclosure, which is the 2701 revelation of private information about an individual. 2703 To mitigate these privacy risks the following countermeasures can be 2704 taken: 2706 In regions where callers can elect to suppress certain personally 2707 identifying information, network or PSAP functionality can inspect 2708 privacy flags within the SIP headers to determine what information 2709 may be passed, stored, or displayed to comply with local policy or 2710 law. RFC 3325 [RFC3325] defines the "id" priv-value token. The 2711 presence of this privacy type in a Privacy header field indicates 2712 that the user would like the network asserted identity to be kept 2713 private with respect to SIP entities outside the trust domain with 2714 which the user authenticated, including the PSAP. 2716 This document defines various data structures that contain privacy- 2717 sensitive data. For example, identifiers for the device (e.g., 2718 serial number, MAC address) or account/SIM (e.g., IMSI), contact 2719 information for the user, location of the caller. Local regulations 2720 may govern what data must be provided in emergency calls, but in 2721 general, the emergency call system is aided by the information 2722 described in this document. There is a tradeoff between the privacy 2723 considerations and the utility of the data. For protection, this 2724 specification requires all retrieval of data passed by reference to 2725 be protected against eavesdropping and alteration via communication 2726 security techniques (namely TLS). Furthermore, security safeguards 2727 are required to prevent unauthorized access to stored data. Various 2728 security incidents over at least the past few decades have shown that 2729 data breaches are not uncommon and are often caused by lack of proper 2730 access control frameworks, software bugs (such as buffer overflows), 2731 or missing input parsing (such as SQL injection attacks). The risks 2732 of data breaches is increased with the obligation for emergency 2733 services to retain emergency call related data for extended periods 2734 (e.g., several years are the norm). 2736 Finally, it is also worth highlighting the nature of the SIP 2737 communication architecture, which introduces additional complications 2738 for privacy. Some forms of data can be sent by value in the SIP 2739 signaling or by reference (a URL in the SIP signaling). When data is 2740 sent by value, all intermediaries have access to the data. As such, 2741 these intermediaries may also introduce additional privacy risk. 2742 Therefore, in situations where the conveyed information is privacy- 2743 sensitive and intermediaries are involved, transmitting by reference 2744 might be appropriate, assuming the source of the data can operate a 2745 sufficient dereferencing infrastructure and that proper access 2746 control policies are available for distinguishing the different 2747 entities dereferencing the reference. Without access control 2748 policies any party in possession of the reference is able to resolve 2749 the reference and to obtain the data, including intermediaries. 2751 10. IANA Considerations 2753 10.1. Registry creation 2755 This document creates a new registry called 'Emergency Call 2756 Additional Data'. The following sub-registries are created for this 2757 registry. 2759 10.1.1. Provider ID Series Registry 2761 This document creates a new sub-registry called 'Additional Call Data 2762 Provider ID Series'. As defined in [RFC5226], this registry operates 2763 under "Expert Review" rules. The expert should determine that the 2764 entity requesting a new value is a legitimate issuer of service 2765 provider IDs suitable for use in Additional Call Data. 2767 Private entities issuing and using internally-generated IDs are 2768 encouraged to register and use a unique identifier. This guarantees 2769 that IDs issued and used by the entity are globally unique and 2770 distinguishable. 2772 The content of this registry includes: 2774 Name: The identifier which will be used in the 'ProviderIDSeries' 2775 element. 2777 Source: The full name of the organization issuing the identifiers. 2779 URL: A URL to the organization for further information. 2781 The initial set of values is listed in Figure 21. 2783 +-----------+--------------------------+----------------------+ 2784 | Name | Source | URL | 2785 +-----------+--------------------------+----------------------+ 2786 | NENA | National Emergency | http://www.nena.org | 2787 | | Number Association | | 2788 | EENA | European Emergency | http://www.eena.org | 2789 | | Number Association | | 2790 | domain | (The ID is a fully- | (not applicable) | 2791 | | qualified domain name) | | 2792 +-----------+--------------------------+----------------------+ 2794 Figure 21: Provider ID Series Registry. 2796 10.1.2. Service Environment Registry 2798 This document creates a new sub-registry called 'Additional Call 2799 Service Environment'. As defined in [RFC5226], this registry 2800 operates under "Expert Review" rules. The expert should determine 2801 that the entity requesting a new value is relevant for this service 2802 element, and that the new value is distinct from existing values, and 2803 its use is unambiguous. 2805 The content of this registry includes: 2807 Token: The value to be used in the element. 2809 Description: A short description of the value. 2811 The initial set of values is listed in Figure 22. 2813 +-----------+--------------------------+ 2814 | Token | Description | 2815 +-----------+--------------------------+ 2816 | Business | Business service | 2817 | Residence | Residential service | 2818 | unknown | Type of service unknown | 2819 | | (e.g., anonymous pre- | 2820 | | paid service) | 2821 +-----------+--------------------------+ 2823 Figure 22: Service Environment Registry. 2825 10.1.3. Service Type Registry 2827 This document creates a new sub-registry called 'Additional Call 2828 Service Type'. As defined in [RFC5226], this registry operates under 2829 "Expert Review" rules. The expert should determine that the entity 2830 requesting a new value is relevant for this service element and that 2831 the requested value is clearly distinct from other values so that 2832 there is no ambiguity as to when the value is to be used or which 2833 value is to be used. 2835 The content of this registry includes: 2837 Name: The value to be used in the element. 2839 Description: A short description of the value. 2841 The initial set of values is listed in Figure 3. 2843 10.1.4. Service Mobility Registry 2845 This document creates a new sub-registry called 'Additional Call 2846 Service Mobility'. As defined in [RFC5226], this registry operates 2847 under "Expert Review" rules. The expert should determine that the 2848 entity requesting a new value is relevant for this service element 2849 and that the requested value is clearly distinct from other values so 2850 that there is no ambiguity as to when the value is to be used or 2851 which value is to be used. 2853 The content of this registry includes: 2855 Token: The value used in the element. 2857 Description: A short description of the value. 2859 The initial set of values is listed in Figure 23. 2861 +-----------+----------------------------+ 2862 | Token | Description | 2863 +-----------+----------------------------+ 2864 | Mobile | The device is able to | 2865 | | move at any time | 2866 | Fixed | The device is not expected | 2867 | | to move unless the service | 2868 | | is relocated | 2869 | Nomadic | The device is not expected | 2870 | | to change its point of | 2871 | | attachment while on a call | 2872 | Unknown | No information is known | 2873 | | about the service mobility | 2874 | | environment for the device | 2875 +-----------+----------------------------+ 2877 Figure 23: Service Environment Registry. 2879 10.1.5. Service Provider Type Registry 2881 This document creates a new sub-registry called 'Service Provider 2882 Type'. As defined in [RFC5226], this registry operates under "Expert 2883 Review". The expert should determine that the proposed new value is 2884 distinct from existing values and appropriate for use in the 2885 TypeOfServicerProvider element 2887 The content of this registry includes: 2889 Tokenproviderid: The value used in the 'TypeOfProvider' element. 2891 Description: A short description of the type of service provider. 2893 The initial set of values is defined in Figure 1. 2895 10.1.6. Service Delivered Registry 2897 This document creates a new sub-registry called 'Service Delivered'. 2898 As defined in [RFC5226], this registry operates under "Expert Review" 2899 rules. The expert should consider whether the proposed service is 2900 unique from existing services and the definition of the service will 2901 be clear to implementors and PSAPs/responders. 2903 The content of this registry includes: 2905 Name: The value used in the 'ServiceType' element. 2907 Description: Short description identifying the nature of the 2908 service. 2910 The initial set of values are defined in Figure 3. 2912 10.1.7. Device Classification Registry 2914 This document creates a new sub-registry called 'Device 2915 Classification'. As defined in [RFC5226], this registry operates 2916 under "Expert Review" rules. The expert should consider whether the 2917 proposed class is unique from existing classes and the definition of 2918 the class will be clear to implementors and PSAPs/responders. 2920 The content of this registry includes: 2922 Token: Value used in the 'DeviceClassification' element. 2924 Description: Short description identifying the device type. 2926 The initial set of values are defined in Figure 5. 2928 10.1.8. Device ID Type Type Registry 2930 This document creates a new sub-registry called 'Additional Call Data 2931 Device ID Type'. As defined in [RFC5226], this registry operates 2932 under "Expert Review" rules. The expert should ascertain that the 2933 proposed type is well understood, and provides the information useful 2934 to PSAPs and responders to uniquely identify a device. 2936 The content of this registry includes: 2938 Token: The value to be placed in the 'TypeOfDeviceID' element. 2940 Description: Short description identifying the type of the device 2941 ID. 2943 The initial set of values are defined in Figure 6. 2945 10.1.9. Device/Service Data Type Registry 2947 This document creates a new sub-registry called 'Device/Service Data 2948 Type Registry'. As defined in [RFC5226], this registry operates 2949 under "Expert Review" and "Specification Required" rules. The expert 2950 should ascertain that the proposed type is well understood, and 2951 provides information useful to PSAPs and responders. The 2952 specification must contain a complete description of the data, and a 2953 precise format specification suitable to allow interoperable 2954 implementations. 2956 The content of this registry includes: 2958 Token: The value to be placed in the element. 2960 Description: Short description identifying the the data. 2962 Specification: Citation for the specification of the data. 2964 The initial set of values are listed in Figure 24. 2966 +----------+----------------------------------------+---------------+ 2967 | Token | Description | Specification | 2968 +----------+----------------------------------------+---------------+ 2969 | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006| 2970 +----------+----------------------------------------+---------------+ 2972 Figure 24: Device/Service Data Type Registry. 2974 10.1.10. Emergency Call Data Types Registry 2976 This document creates a new sub-registry called 'Emergency Call Data 2977 Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. 2978 As defined in [RFC5226], this registry operates under "Expert Review" 2979 and "Specification Required" rules. The expert is responsible for 2980 verifying that the document contains a complete and clear 2981 specification and the proposed functionality does not obviously 2982 duplicate existing functionality. 2984 The content of this registry includes: 2986 Token: The root of the data's MIME subtype (not including the 2987 'EmergencyCallData' prefix and any suffix such as '+xml') 2989 Reference: The document that describes the data object 2991 Note that the values from this registry are part of the 2992 'EmergencyCallData' compound value; when used as a value of the 2993 'purpose' parameter of the Call-Info header, the values listed in 2994 this registry are prefixed by 'EmergencyCallData.' per the the 2995 'EmergencyCallData' registation Section 10.2. 2997 The initial set of values are listed in Figure 25. 2999 +----------------+------------+ 3000 | Token | Reference | 3001 +----------------+------------+ 3002 | ProviderInfo | [This RFC] | 3003 | ServiceInfo | [This RFC] | 3004 | DeviceInfo | [This RFC] | 3005 | SubscriberInfo | [This RFC] | 3006 | Comment | [This RFC] | 3007 +----------------+------------+ 3009 Figure 25: Additional Data Blocks Registry. 3011 10.2. 'EmergencyCallData' Purpose Parameter Value 3013 This document defines the 'EmergencyCallData' value for the "purpose" 3014 parameter of the Call-Info header field. The Call-Info header and 3015 the corresponding registry for the 'purpose' parameter was 3016 established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' 3017 is a compound value; when used as a value of the 'purpose' parameter 3018 of the Call-Info header, 'EmergencyCallData' is immediately followed 3019 by a dot ('.') and a value from the 'Emergency Call Data Types' 3020 registry Section 10.1.10. 3022 Header Parameter New 3023 Field Name Value Reference 3024 ---------- --------- ----------------- --------- 3025 Call-Info purpose EmergencyCallData [This RFC] 3027 10.3. URN Sub-Namespace Registration for provided-by Registry Entry 3029 This section registers the namespace specified in Section 10.5.1 in 3030 the provided-by registry established by RFC 4119, for usage within 3031 the element of a PIDF-LO. 3033 The schema for the provided-by element used by this document is 3034 specified in Section 7.6. 3036 10.4. MIME Registrations 3038 10.4.1. MIME Content-type Registration for 'application/ 3039 EmergencyCallData.ProviderInfo+xml' 3041 This specification requests the registration of a new MIME type 3042 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3043 RFC 7303 [RFC7303]. 3045 MIME media type name: application 3047 MIME subtype name: EmergencyCallData.ProviderInfo+xml 3049 Mandatory parameters: none 3051 Optional parameters: charset (indicates the character encoding of 3052 the contents) 3054 Encoding considerations: Uses XML, which can contain 8-bit 3055 characters, depending on the character encoding. See Section 3.2 3056 of RFC 7303 [RFC7303]. 3058 Security considerations: This content type is designed to carry 3059 the data provider information, which is a sub-category of 3060 additional data about an emergency call. Since this data may 3061 contain personal information, appropriate precautions might be 3062 needed to limit unauthorized access, inappropriate disclosure, and 3063 eavesdropping of personal information. Please refer to Section 8 3064 and Section 9 for more information. 3066 Interoperability considerations: None 3068 Published specification: [TBD: This specification] 3070 Applications which use this media type: Emergency Services 3072 Additional information: 3074 Magic Number: None 3076 File Extension: .xml 3078 Macintosh file type code: 'TEXT' 3080 Person and email address for further information: Hannes 3081 Tschofenig, Hannes.Tschofenig@gmx.net 3083 Intended usage: LIMITED USE 3085 Author: This specification is a work item of the IETF ECRIT 3086 working group, with mailing list address . 3088 Change controller: The IESG 3090 10.4.2. MIME Content-type Registration for 'application/ 3091 EmergencyCallData.ServiceInfo+xml' 3093 This specification requests the registration of a new MIME type 3094 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3095 RFC 7303 [RFC7303]. 3097 MIME media type name: application 3099 MIME subtype name: EmergencyCallData.ServiceInfo+xml 3101 Mandatory parameters: none 3103 Optional parameters: charset (indicates the character encoding of 3104 the contents) 3106 Encoding considerations: Uses XML, which can contain 8-bit 3107 characters, depending on the character encoding. See Section 3.2 3108 of RFC 7303 [RFC7303]. 3110 Security considerations: This content type is designed to carry 3111 the service information, which is a sub-category of additional 3112 data about an emergency call. Since this data may contain 3113 personal information, appropriate precautions may be needed to 3114 limit unauthorized access, inappropriate disclosure, and 3115 eavesdropping of personal information. Please refer to Section 8 3116 and Section 9 for more information. 3118 Interoperability considerations: None 3120 Published specification: [TBD: This specification] 3122 Applications which use this media type: Emergency Services 3124 Additional information: 3126 Magic Number: None 3127 File Extension: .xml 3129 Macintosh file type code: 'TEXT' 3131 Person and email address for further information: Hannes 3132 Tschofenig, Hannes.Tschofenig@gmx.net 3134 Intended usage: LIMITED USE 3136 Author: This specification is a work item of the IETF ECRIT 3137 working group, with mailing list address . 3139 Change controller: The IESG 3141 10.4.3. MIME Content-type Registration for 'application/ 3142 EmergencyCallData.DeviceInfo+xml' 3144 This specification requests the registration of a new MIME type 3145 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3146 RFC 7303 [RFC7303]. 3148 MIME media type name: application 3150 MIME subtype name: EmergencyCallData.DeviceInfo+xml 3152 Mandatory parameters: none 3154 Optional parameters: charset (indicates the character encoding of 3155 the contents) 3157 Encoding considerations: Uses XML, which can contain 8-bit 3158 characters, depending on the character encoding. See Section 3.2 3159 of RFC 7303 [RFC7303]. 3161 Security considerations: This content type is designed to carry 3162 device information, which is a sub-category of additional data 3163 about an emergency call. Since this data contains personal 3164 information, appropriate precautions need to be taken to limit 3165 unauthorized access, inappropriate disclosure to third parties, 3166 and eavesdropping of this information. Please refer to Section 8 3167 and Section 9 for more information. 3169 Interoperability considerations: None 3171 Published specification: [TBD: This specification] 3173 Applications which use this media type: Emergency Services 3174 Additional information: 3176 Magic Number: None 3178 File Extension: .xml 3180 Macintosh file type code: 'TEXT' 3182 Person and email address for further information: Hannes 3183 Tschofenig, Hannes.Tschofenig@gmx.net 3185 Intended usage: LIMITED USE 3187 Author: This specification is a work item of the IETF ECRIT 3188 working group, with mailing list address . 3190 Change controller: The IESG 3192 10.4.4. MIME Content-type Registration for 'application/ 3193 EmergencyCallData.SubscriberInfo+xml' 3195 This specification requests the registration of a new MIME type 3196 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3197 RFC 7303 [RFC7303]. 3199 MIME media type name: application 3201 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 3203 Mandatory parameters: none 3205 Optional parameters: charset (indicates the character encoding of 3206 the contents) 3208 Encoding considerations: Uses XML, which can contain 8-bit 3209 characters, depending on the character encoding. See Section 3.2 3210 of RFC 7303 [RFC7303]. 3212 Security considerations: This content type is designed to carry 3213 owner/subscriber information, which is a sub-category of 3214 additional data about an emergency call. Since this data contains 3215 personal information, appropriate precautions need to be taken to 3216 limit unauthorized access, inappropriate disclosure to third 3217 parties, and eavesdropping of this information. Please refer to 3218 Section 8 and Section 9 for more information. 3220 Interoperability considerations: None 3221 Published specification: [TBD: This specification] 3223 Applications which use this media type: Emergency Services 3225 Additional information: 3227 Magic Number: None 3229 File Extension: .xml 3231 Macintosh file type code: 'TEXT' 3233 Person and email address for further information: Hannes 3234 Tschofenig, Hannes.Tschofenig@gmx.net 3236 Intended usage: LIMITED USE 3238 Author: This specification is a work item of the IETF ECRIT 3239 working group, with mailing list address . 3241 Change controller: The IESG 3243 10.4.5. MIME Content-type Registration for 'application/ 3244 EmergencyCallData.Comment+xml' 3246 This specification requests the registration of a new MIME type 3247 according to the procedures of RFC 6838 [RFC6838] and guidelines in 3248 RFC 7303 [RFC7303]. 3250 MIME media type name: application 3252 MIME subtype name: EmergencyCallData.Comment+xml 3254 Mandatory parameters: none 3256 Optional parameters: charset (indicates the character encoding of 3257 the contents) 3259 Encoding considerations: Uses XML, which can contain 8-bit 3260 characters, depending on the character encoding. See Section 3.2 3261 of RFC 7303 [RFC7303]. 3263 Security considerations: This content type is designed to carry a 3264 comment, which is a sub-category of additional data about an 3265 emergency call. This data may contain personal information. 3266 Appropriate precautions may be needed to limit unauthorized 3267 access, inappropriate disclosure to third parties, and 3268 eavesdropping of this information. Please refer to Section 8 and 3269 Section 9 for more information. 3271 Interoperability considerations: None 3273 Published specification: [TBD: This specification] 3275 Applications which use this media type: Emergency Services 3277 Additional information: 3279 Magic Number: None 3281 File Extension: .xml 3283 Macintosh file type code: 'TEXT' 3285 Person and email address for further information: Hannes 3286 Tschofenig, Hannes.Tschofenig@gmx.net 3288 Intended usage: LIMITED USE 3290 Author: This specification is a work item of the IETF ECRIT 3291 working group, with mailing list address . 3293 Change controller: The IESG 3295 10.5. URN Sub-Namespace Registration 3297 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3299 This section registers a new XML namespace, as per the guidelines in 3300 RFC 3688 [RFC3688]. 3302 URI: urn:ietf:params:xml:ns:EmergencyCallData 3304 Registrant Contact: IETF, ECRIT working group, , as 3305 delegated by the IESG . 3307 XML: 3309 BEGIN 3310 3311 3313 3314 3315 3317 Namespace for Additional Emergency Call Data 3318 3319 3320

Namespace for Additional Data related to an Emergency Call 3321

3322

See [TBD: This document].

3323 3324 3325 END 3327 10.5.2. Registration for 3328 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3330 This section registers a new XML namespace, as per the guidelines in 3331 RFC 3688 [RFC3688]. 3333 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3335 Registrant Contact: IETF, ECRIT working group, , as 3336 delegated by the IESG . 3338 XML: 3340 BEGIN 3341 3342 3344 3345 3346 3348 Namespace for Additional Emergency Call Data: 3349 Data Provider Information 3350 3351 3352

Namespace for Additional Data related to an Emergency Call 3353

3354

Data Provider Information

3355

See [TBD: This document].

3356 3357 3358 END 3360 10.5.3. Registration for 3361 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3363 This section registers a new XML namespace, as per the guidelines in 3364 RFC 3688 [RFC3688]. 3366 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3368 Registrant Contact: IETF, ECRIT working group, , as 3369 delegated by the IESG . 3371 XML: 3373 BEGIN 3374 3375 3377 3378 3379 3381 Namespace for Additional Emergency Call Data: 3382 Service Information 3383 3384 3385

Namespace for Additional Data related to an Emergency Call 3386

3387

Service Information

3388

See [TBD: This document].

3389 3390 3391 END 3393 10.5.4. Registration for 3394 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3396 This section registers a new XML namespace, as per the guidelines in 3397 RFC 3688 [RFC3688]. 3399 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3401 Registrant Contact: IETF, ECRIT working group, , as 3402 delegated by the IESG . 3404 XML: 3406 BEGIN 3407 3408 3410 3411 3412 3414 Namespace for Additional Emergency Call Data: 3415 Device Information 3416 3417 3418

Namespace for Additional Data related to an Emergency Call 3419

3420

Device Information

3421

See [TBD: This document].

3422 3423 3424 END 3426 10.5.5. Registration for 3427 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3429 This section registers a new XML namespace, as per the guidelines in 3430 RFC 3688 [RFC3688]. 3432 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3434 Registrant Contact: IETF, ECRIT working group, , as 3435 delegated by the IESG . 3437 XML: 3439 BEGIN 3440 3441 3443 3444 3445 3447 Namespace for Additional Emergency Call Data: 3448 Owner/Subscriber Information 3449 3450 3451

Namespace for Additional Data related to an Emergency Call 3452

3453

Owner/Subscriber Information

3454

See [TBD: This document].

3455 3456 3457 END 3459 10.5.6. Registration for 3460 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3462 This section registers a new XML namespace, as per the guidelines in 3463 RFC 3688 [RFC3688]. 3465 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3467 Registrant Contact: IETF, ECRIT working group, , as 3468 delegated by the IESG . 3470 XML: 3472 BEGIN 3473 3474 3476 3477 3478 3480 Namespace for Additional Emergency Call Data:Comment 3481 3482 3483 3484

Namespace for Additional Data related to an Emergency Call 3485

3486

Comment

3487

See [TBD: This document].

3488 3489 3490 END 3492 10.6. Schema Registrations 3494 This specification registers five schemas, as per the guidelines in 3495 RFC 3688 [RFC3688]. 3497 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3499 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3500 delegated by the IESG (iesg@ietf.org). 3502 XML: The XML schema can be found in Figure 15. 3504 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3506 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3507 delegated by the IESG (iesg@ietf.org). 3509 XML: The XML schema can be found in Figure 16. 3511 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3513 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3514 delegated by the IESG (iesg@ietf.org). 3516 XML: The XML schema can be found in Figure 17. 3518 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3519 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3520 delegated by the IESG (iesg@ietf.org). 3522 XML: The XML schema can be found in Section 7.4. 3524 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3526 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3527 delegated by the IESG (iesg@ietf.org). 3529 XML: The XML schema can be found in Section 7.5. 3531 10.7. VCard Parameter Value Registration 3533 This document registers a new value in the vCARD Parameter Values 3534 registry as defined by [RFC6350] with the following template: 3536 Value: main 3538 Purpose: The main telephone number, typically of an enterprise, as 3539 opposed to a direct dial number of an individual employee 3541 Conformance: This value can be used with the "TYPE" parameter 3542 applied on the "TEL" property. 3544 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3545 00 3547 11. Acknowledgments 3549 This work was originally started in NENA and has benefitted from a 3550 large number of participants in NENA standardization efforts, 3551 originally in the Long Term Definition Working Group, the Data 3552 Technical Committee and most recently the Additional Data working 3553 group. The authors are grateful for the initial work and extended 3554 comments provided by many NENA participants, including Delaine 3555 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3556 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3557 and Robert (Bob) Sherry. 3559 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3560 Thomson, Keith Drage, Laura Liess, Chris Santer, and Barbara Stark 3561 for their review comments. Guy Caron deserves special mention for 3562 his detailed and extensive review comments. 3564 12. References 3566 12.1. Normative References 3568 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3569 Requirement Levels", BCP 14, RFC 2119, March 1997. 3571 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3572 Locators", RFC 2392, August 1998. 3574 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3575 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3576 and QSIG Objects", RFC 3204, December 2001. 3578 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3579 A., Peterson, J., Sparks, R., Handley, M., and E. 3580 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3581 June 2002. 3583 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3584 Extensions to the Session Initiation Protocol (SIP) for 3585 Asserted Identity within Trusted Networks", RFC 3325, 3586 November 2002. 3588 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3589 Extensions (MIME) Parameter", RFC 3459, January 2003. 3591 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3592 January 2004. 3594 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3595 Format", RFC 4119, December 2005. 3597 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3598 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3599 May 2008. 3601 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 3602 October 2008. 3604 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3605 Initiation Protocol (SIP)", RFC 5621, September 2009. 3607 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3608 August 2011. 3610 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3611 6351, August 2011. 3613 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3614 Specifications and Registration Procedures", BCP 13, RFC 3615 6838, January 2013. 3617 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 3618 July 2014. 3620 12.2. Informational References 3622 [I-D.gellens-slim-negotiating-human-language] 3623 Gellens, R., "Negotiating Human Language in Real-Time 3624 Communications", draft-gellens-slim-negotiating-human- 3625 language (work in progress), October 2014. 3627 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3628 "Indicating User Agent Capabilities in the Session 3629 Initiation Protocol (SIP)", RFC 3840, August 2004. 3631 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3632 3966, December 2004. 3634 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3635 Emergency Context Resolution with Internet Technologies", 3636 RFC 5012, January 2008. 3638 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3639 Format for Presence Information Data Format Location 3640 Object (PIDF-LO)", RFC 5139, February 2008. 3642 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3643 Presence Information Data Format Location Object (PIDF-LO) 3644 Usage Clarification, Considerations, and Recommendations", 3645 RFC 5491, March 2009. 3647 [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and 3648 Framework", RFC 5582, September 2009. 3650 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3651 Thomson, "Dynamic Extensions to the Presence Information 3652 Data Format Location Object (PIDF-LO)", RFC 5962, 3653 September 2010. 3655 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3656 5985, September 2010. 3658 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3659 "Framework for Emergency Calling Using Internet 3660 Multimedia", RFC 6443, December 2011. 3662 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3663 R. George, "Specifying Civic Address Extensions in the 3664 Presence Information Data Format Location Object (PIDF- 3665 LO)", RFC 6848, January 2013. 3667 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3668 Communications Services in Support of Emergency Calling", 3669 BCP 181, RFC 6881, March 2013. 3671 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3672 Morris, J., Hansen, M., and R. Smith, "Privacy 3673 Considerations for Internet Protocols", RFC 6973, July 3674 2013. 3676 [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3677 Thomson, "Relative Location Representation", RFC 7035, 3678 October 2013. 3680 [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3681 Patel, "Public Safety Answering Point (PSAP) Callback", 3682 RFC 7090, April 2014. 3684 12.3. URIs 3686 [1] http://www.nena.org/?page=cid2014 3688 [2] http://www.nena.org/?page=CompanyID 3690 Appendix A. XML Schema for vCard/xCard 3692 This section contains the vCard/xCard XML schema version of the Relax 3693 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3694 XML schemas defined in this document. The schema in RFC 6351 3695 [RFC6351] is the normative source and this section is informative 3696 only. 3698 3699 3703 3709 3710 3711 vCard Format Specification 3712 3713 3714 3715 3716 3717 3718 3719 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3734 3735 3736 3738 3739 3740 3741 3742 3744 3745 3746 3748 3749 3750 3751 3752 3754 3755 3756 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 3793 3794 3795 3801 3802 3803 3804 3807 3808 3809 Section 5: Parameters 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 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 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 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 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 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 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 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528 4529 4530 4531 4532 4533 4534 4535 4536 4537 4538 4539 4540 4541 4542 4543 4544 4545 4546 4547 4548 4549 4550 4551 4552 4553 4554 4555 4556 4557 4558 4559 4560 4561 4562 4563 4564 4565 4566 4567 4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4675 4676 4677 4678 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4735 4736 4737 4738 4739 4740 4741 4743 4744 4745 4746 4747 4748 4749 4751 4752 4753 4755 4757 4758 4759 4761 4762 4763 4764 4766 Authors' Addresses 4768 Randall Gellens 4769 Qualcomm Technologies, Inc. 4770 5775 Morehouse Drive 4771 San Diego, CA 92121 4772 US 4774 Email: rg+ietf@qti.qualcomm.com 4776 Brian Rosen 4777 NeuStar 4778 470 Conrad Dr. 4779 Mars, PA 16046 4780 US 4782 Phone: +1 724 382 1051 4783 Email: br@brianrosen.net 4785 Hannes Tschofenig 4786 (no affiliation) 4788 Email: Hannes.Tschofenig@gmx.net 4789 URI: http://www.tschofenig.priv.at 4791 Roger Marshall 4792 TeleCommunication Systems, Inc. 4793 2401 Elliott Avenue 4794 Seattle, WA 98121 4795 US 4797 Phone: +1 206 792 2424 4798 Email: rmarshall@telecomsys.com 4799 URI: http://www.telecomsys.com 4801 James Winterbottom 4802 (no affiliation) 4803 AU 4805 Email: a.james.winterbottom@gmail.com