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

Namespace for Additional Data related to an Emergency Call 3327

3328

See [TBD: This document].

3329 3330 3331 END 3333 10.5.2. Registration for 3334 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3336 This section registers a new XML namespace, as per the guidelines in 3337 RFC 3688 [RFC3688]. 3339 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3341 Registrant Contact: IETF, ECRIT working group, , as 3342 delegated by the IESG . 3344 XML: 3346 BEGIN 3347 3348 3350 3351 3352 3354 Namespace for Additional Emergency Call Data: 3355 Data Provider Information 3356 3357 3358

Namespace for Additional Data related to an Emergency Call 3359

3360

Data Provider Information

3361

See [TBD: This document].

3362 3363 3364 END 3366 10.5.3. Registration for 3367 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3369 This section registers a new XML namespace, as per the guidelines in 3370 RFC 3688 [RFC3688]. 3372 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3374 Registrant Contact: IETF, ECRIT working group, , as 3375 delegated by the IESG . 3377 XML: 3379 BEGIN 3380 3381 3383 3384 3385 3387 Namespace for Additional Emergency Call Data: 3388 Service Information 3389 3390 3391

Namespace for Additional Data related to an Emergency Call 3392

3393

Service Information

3394

See [TBD: This document].

3395 3396 3397 END 3399 10.5.4. Registration for 3400 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3402 This section registers a new XML namespace, as per the guidelines in 3403 RFC 3688 [RFC3688]. 3405 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3407 Registrant Contact: IETF, ECRIT working group, , as 3408 delegated by the IESG . 3410 XML: 3412 BEGIN 3413 3414 3416 3417 3418 3420 Namespace for Additional Emergency Call Data: 3421 Device Information 3422 3423 3424

Namespace for Additional Data related to an Emergency Call 3425

3426

Device Information

3427

See [TBD: This document].

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

Namespace for Additional Data related to an Emergency Call 3458

3459

Owner/Subscriber Information

3460

See [TBD: This document].

3461 3462 3463 END 3465 10.5.6. Registration for 3466 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3468 This section registers a new XML namespace, as per the guidelines in 3469 RFC 3688 [RFC3688]. 3471 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3473 Registrant Contact: IETF, ECRIT working group, , as 3474 delegated by the IESG . 3476 XML: 3478 BEGIN 3479 3480 3482 3483 3484 3486 Namespace for Additional Emergency Call Data:Comment 3487 3488 3489 3490

Namespace for Additional Data related to an Emergency Call 3491

3492

Comment

3493

See [TBD: This document].

3494 3495 3496 END 3498 10.6. Schema Registrations 3500 This specification registers five schemas, as per the guidelines in 3501 RFC 3688 [RFC3688]. 3503 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3505 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3506 delegated by the IESG (iesg@ietf.org). 3508 XML: The XML schema can be found in Figure 15. 3510 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3512 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3513 delegated by the IESG (iesg@ietf.org). 3515 XML: The XML schema can be found in Figure 16. 3517 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 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 Figure 17. 3524 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3525 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3526 delegated by the IESG (iesg@ietf.org). 3528 XML: The XML schema can be found in Section 7.4. 3530 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3532 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3533 delegated by the IESG (iesg@ietf.org). 3535 XML: The XML schema can be found in Section 7.5. 3537 10.7. VCard Parameter Value Registration 3539 This document registers a new value in the vCARD Parameter Values 3540 registry as defined by [RFC6350] with the following template: 3542 Value: main 3544 Purpose: The main telephone number, typically of an enterprise, as 3545 opposed to a direct dial number of an individual employee 3547 Conformance: This value can be used with the "TYPE" parameter 3548 applied on the "TEL" property. 3550 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3551 00 3553 11. Acknowledgments 3555 This work was originally started in NENA and has benefitted from a 3556 large number of participants in NENA standardization efforts, 3557 originally in the Long Term Definition Working Group, the Data 3558 Technical Committee and most recently the Additional Data working 3559 group. The authors are grateful for the initial work and extended 3560 comments provided by many NENA participants, including Delaine 3561 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3562 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3563 and Robert (Bob) Sherry. Amursana Khiyod, Robert Sherry, Frank 3564 Rahoi, Scott Ross, Tom Klepetka provided valuable feedback regarding 3565 the vCard/xCard use in this specification. 3567 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3568 Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris 3569 Santer, and Archie Cobbs for their review comments. Guy Caron 3570 deserves special mention for his detailed and extensive review 3571 comments. 3573 12. References 3575 12.1. Normative References 3577 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3578 Requirement Levels", BCP 14, RFC 2119, March 1997. 3580 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3581 Locators", RFC 2392, August 1998. 3583 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3584 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3585 and QSIG Objects", RFC 3204, December 2001. 3587 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3588 A., Peterson, J., Sparks, R., Handley, M., and E. 3589 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3590 June 2002. 3592 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3593 Extensions (MIME) Parameter", RFC 3459, January 2003. 3595 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3596 January 2004. 3598 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3599 Format", RFC 4119, December 2005. 3601 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3602 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3603 May 2008. 3605 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 3606 October 2008. 3608 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3609 Initiation Protocol (SIP)", RFC 5621, September 2009. 3611 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3612 August 2011. 3614 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3615 6351, August 2011. 3617 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 3618 Specifications and Registration Procedures", BCP 13, RFC 3619 6838, January 2013. 3621 [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, 3622 July 2014. 3624 12.2. Informational References 3626 [I-D.gellens-slim-negotiating-human-language] 3627 Gellens, R., "Negotiating Human Language in Real-Time 3628 Communications", draft-gellens-slim-negotiating-human- 3629 language (work in progress), October 2014. 3631 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3632 Extensions to the Session Initiation Protocol (SIP) for 3633 Asserted Identity within Trusted Networks", RFC 3325, 3634 November 2002. 3636 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3637 "Indicating User Agent Capabilities in the Session 3638 Initiation Protocol (SIP)", RFC 3840, August 2004. 3640 [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3641 3966, December 2004. 3643 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3644 Emergency Context Resolution with Internet Technologies", 3645 RFC 5012, January 2008. 3647 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3648 Format for Presence Information Data Format Location 3649 Object (PIDF-LO)", RFC 5139, February 2008. 3651 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3652 Presence Information Data Format Location Object (PIDF-LO) 3653 Usage Clarification, Considerations, and Recommendations", 3654 RFC 5491, March 2009. 3656 [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and 3657 Framework", RFC 5582, September 2009. 3659 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3660 Thomson, "Dynamic Extensions to the Presence Information 3661 Data Format Location Object (PIDF-LO)", RFC 5962, 3662 September 2010. 3664 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3665 5985, September 2010. 3667 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3668 "Framework for Emergency Calling Using Internet 3669 Multimedia", RFC 6443, December 2011. 3671 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3672 R. George, "Specifying Civic Address Extensions in the 3673 Presence Information Data Format Location Object (PIDF- 3674 LO)", RFC 6848, January 2013. 3676 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3677 Communications Services in Support of Emergency Calling", 3678 BCP 181, RFC 6881, March 2013. 3680 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3681 Morris, J., Hansen, M., and R. Smith, "Privacy 3682 Considerations for Internet Protocols", RFC 6973, July 3683 2013. 3685 [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3686 Thomson, "Relative Location Representation", RFC 7035, 3687 October 2013. 3689 [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3690 Patel, "Public Safety Answering Point (PSAP) Callback", 3691 RFC 7090, April 2014. 3693 12.3. URIs 3695 [1] http://www.nena.org/?page=cid2014 3697 [2] http://www.nena.org/?page=CompanyID 3699 Appendix A. XML Schema for vCard/xCard 3701 This section contains the vCard/xCard XML schema version of the Relax 3702 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3703 XML schemas defined in this document. The schema in RFC 6351 3704 [RFC6351] is the normative source and this section is informative 3705 only. 3707 3708 3712 3717 3718 3719 vCard Format Specification 3720 3721 3722 3723 3724 3725 3726 3727 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3742 3743 3744 3746 3747 3748 3749 3750 3752 3753 3754 3756 3757 3758 3759 3760 3762 3763 3764 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3810 3811 3812 3813 3817 3818 3819 Section 5: Parameters 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 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 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 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 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 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603 4604 4605 4606 4607 4608 4609 4610 4611 4612 4613 4614 4615 4616 4617 4618 4619 4620 4621 4622 4623 4624 4625 4626 4627 4628 4629 4630 4631 4632 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644 4645 4646 4647 4648 4649 4650 4651 4652 4653 4654 4655 4656 4657 4658 4659 4660 4661 4662 4663 4664 4665 4666 4667 4668 4669 4670 4671 4672 4673 4674 4675 4676 4677 4679 4680 4681 4682 4683 4684 4685 4686 4687 4688 4689 4690 4691 4692 4693 4694 4695 4696 4697 4698 4699 4700 4701 4702 4703 4704 4705 4706 4707 4708 4709 4710 4711 4712 4713 4714 4715 4716 4717 4718 4719 4720 4721 4722 4723 4724 4725 4726 4727 4728 4729 4730 4731 4732 4733 4734 4735 4736 4737 4738 4739 4740 4741 4742 4744 4745 4746 4747 4748 4749 4750 4752 4753 4754 4755 4756 4757 4758 4760 4761 4762 4764 4766 4767 4768 4770 4771 4772 4773 4775 Authors' Addresses 4777 Randall Gellens 4778 Qualcomm Technologies, Inc. 4779 5775 Morehouse Drive 4780 San Diego, CA 92121 4781 US 4783 Email: rg+ietf@qti.qualcomm.com 4785 Brian Rosen 4786 NeuStar 4787 470 Conrad Dr. 4788 Mars, PA 16046 4789 US 4791 Phone: +1 724 382 1051 4792 Email: br@brianrosen.net 4794 Hannes Tschofenig 4795 Hall in Tirol 6060 4796 Austria 4798 Email: Hannes.tschofenig@gmx.net 4799 URI: http://www.tschofenig.priv.at 4801 Roger Marshall 4802 TeleCommunication Systems, Inc. 4803 2401 Elliott Avenue 4804 Seattle, WA 98121 4805 US 4807 Phone: +1 206 792 2424 4808 Email: rmarshall@telecomsys.com 4809 URI: http://www.telecomsys.com 4811 James Winterbottom 4812 AU 4814 Email: a.james.winterbottom@gmail.com