idnits 2.17.1 draft-ietf-ecrit-additional-data-22.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 39 instances of too long lines in the document, the longest one being 18 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 2308 has weird spacing: '...element name=...' == Line 2808 has weird spacing: '...ll-Info pur...' -- The document date (April 23, 2014) is 3654 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 392 -- Looks like a reference, but probably isn't: '2' on line 392 == Missing Reference: 'This RFC' is mentioned on line 2808, but not defined == Unused Reference: 'RFC5985' is defined on line 3416, but no explicit reference was found in the text ** Obsolete normative reference: RFC 822 (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track H. Tschofenig 5 Expires: October 25, 2014 (no affiliation) 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 11 (no affiliation) 12 April 23, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-22.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 October 25, 2014. 50 Copyright Notice 52 Copyright (c) 2014 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7 70 3.1. Data Provider Information . . . . . . . . . . . . . . . . 8 71 3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 72 3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8 73 3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9 74 3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9 75 3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10 76 3.1.6. Data Provider Languages(s) Supported . . . . . . . . 11 77 3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11 78 3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12 79 3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13 80 3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13 81 3.2. Service Information . . . . . . . . . . . . . . . . . . . 15 82 3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15 83 3.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16 84 3.2.3. Service Mobility Environment . . . . . . . . . . . . 17 85 3.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 18 86 3.3. Device Information . . . . . . . . . . . . . . . . . . . 18 87 3.3.1. Device Classification . . . . . . . . . . . . . . . . 18 88 3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 20 89 3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 20 90 3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20 91 3.3.5. Device/Service Specific Additional Data Structure . . 21 92 3.3.6. Device/Service Specific Additional Data Structure 93 Type . . . . . . . . . . . . . . . . . . . . . . . . 22 94 3.3.7. Issues with getting new types of data into use . . . 23 95 3.3.8. Choosing between defining a new type of block or new 96 type of device/service specific additional data . . . 23 97 3.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 24 98 3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24 99 3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 25 100 3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25 101 3.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 26 102 3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28 103 3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28 104 3.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 28 105 4. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 29 106 4.1. Transmitting Blocks using the Call-Info Header . . . . . 31 107 4.2. Transmitting Blocks by Reference using the Provided-By 108 Element . . . . . . . . . . . . . . . . . . . . . . . . . 31 109 4.3. Transmitting Blocks by Value using the Provided-By 110 Element . . . . . . . . . . . . . . . . . . . . . . . . . 32 111 4.4. The Content-Disposition Parameter . . . . . . . . . . . . 33 112 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34 113 6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45 114 6.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 45 115 6.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 47 116 6.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 48 117 6.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 49 118 6.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 50 119 6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 51 120 7. Security Considerations . . . . . . . . . . . . . . . . . . . 53 121 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 54 122 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 123 9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 56 124 9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 56 125 9.1.2. Service Environment Registry . . . . . . . . . . . . 57 126 9.1.3. Service Provider Type Registry . . . . . . . . . . . 57 127 9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57 128 9.1.5. Device Classification Registry . . . . . . . . . . . 58 129 9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 58 130 9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58 131 9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 59 132 9.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . . 60 133 9.3. URN Sub-Namespace Registration for provided-by Registry 134 Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 60 135 9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 60 136 9.4.1. MIME Content-type Registration for 137 'application/EmergencyCallData.ProviderInfo+xml' . . 60 138 9.4.2. MIME Content-type Registration for 139 'application/EmergencyCallData.ServiceInfo+xml' . . . 61 140 9.4.3. MIME Content-type Registration for 141 'application/EmergencyCallData.DeviceInfo+xml' . . . 62 142 9.4.4. MIME Content-type Registration for 143 'application/EmergencyCallData.SubscriberInfo+xml' . 63 145 9.4.5. MIME Content-type Registration for 146 'application/EmergencyCallData.Comment+xml' . . . . . 64 147 9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 65 148 9.5.1. Registration for 149 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 65 150 9.5.2. Registration for 151 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 66 152 9.5.3. Registration for 153 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 67 154 9.5.4. Registration for 155 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo . 67 156 9.5.5. Registration for 157 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberIn 158 fo . . . . . . . . . . . . . . . . . . . . . . . . . 68 159 9.5.6. Registration for 160 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 69 161 9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 69 162 9.7. VCard Parameter Value Registration . . . . . . . . . . . 70 163 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71 164 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 71 165 11.1. Normative References . . . . . . . . . . . . . . . . . . 71 166 11.2. Informational References . . . . . . . . . . . . . . . . 72 167 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 74 168 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 170 1. Introduction 172 When an IP-based emergency call is initiated, a rich set of data from 173 multiple data sources is conveyed to the Public Safety Answering 174 Point (PSAP). This data includes information about the calling party 175 identity, the multimedia capabilities of the device, the emergency 176 service number, location information, and meta-data about the sources 177 of the data. The device, the access network provider, and any 178 service provider in the call path may have even more information 179 useful for a PSAP. This document extends the basic set of data 180 communicated with an IP-based emergency call, as described in 181 [RFC6443] and [RFC6881], in order to carry additional data which may 182 be useful to an entity or call taker handling the call. This data is 183 "additional" to the basic information found in the emergency call 184 signaling used. 186 In general, there are three categories of this additional data that 187 may be transmitted with an emergency call: 189 Data Associated with a Location: Primary location data is conveyed 190 in the Presence Information Data Format Location Object (PIDF-LO) 191 data structure as defined in RFC 4119 [RFC4119] and extended by 192 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 193 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 194 geodetic location information), and 195 [I-D.ietf-geopriv-relative-location] (for relative location). 196 This primary location data identifies the location or estimated 197 location of the caller. However, there may exist additional, 198 secondary data which is specific to the location, such as floor 199 plans, tenant and building owner contact data, heating, 200 ventilation and air conditioning (HVAC) status, etc. Such 201 secondary location data is not included in the location data 202 structure but can be transmitted using the mechanisms defined in 203 this document; although this document does not define any 204 structures for such data, future documents may do so following the 205 procedures defined here. 207 Data Associated with a Call: While some information is carried in 208 the call setup procedure itself (as part of the SIP headers as 209 well as in the body of the SIP message), there is additional data 210 known by the device making the call and/or a service provider 211 along the path of the call. This information may include the 212 service provider contact information, subscriber identity and 213 contact information, the type of service the service provider and 214 the access network provider offer, what type of device is being 215 used, etc. Some data is broadly applicable, while other data is 216 dependent on the type of device or service. For example, a 217 medical monitoring device may have sensor data. The data 218 structures defined in this document (Data Provider Information, 219 Device Information, and Owner/Subscriber Information) all fall 220 into this category ("Data Associated with a Call"). 222 Data Associated with a Caller: This is personal data about a caller, 223 such as medical information and emergency contact data. Although 224 this document does not define any structures within this category, 225 future documents may do so following the procedures defined here. 227 While this document defines data structures only within the category 228 of Data Associated with a Call, by establishing the overall framework 229 of Additional Data, along with general mechanisms for transport of 230 such data, extension points and procedures for future extensions, it 231 minimizes the work needed to carry data in the other categories. 232 Other specifications may make use of the facilities provided here. 234 For interoperability, there needs to be a common way for the 235 information conveyed to a PSAP to be encoded and identified. 236 Identification allows emergency services authorities to know during 237 call processing which types of data are present and to determine if 238 they wish to access it. A common encoding allows the data to be 239 successfully accessed. 241 This document defines an extensible set of data structures, and 242 mechanisms to transmit this data either by value or by reference, 243 either in the Session Initiation Protocol (SIP) call signaling or in 244 the Presence Information Data Format Location Object (PIDF-LO). The 245 data structures are usable by other communication systems and 246 transports as well. The data structures are defined in Section 3, 247 and the transport mechanisms (using SIP and HTTPS) are defined in 248 Section 4. 250 Each data structure described in this document is encoded as a 251 "block" of information. Each block is an XML structure with an 252 associated Multipurpose Internet Mail Extensions (MIME) type for 253 identification within transport such as SIP and HTTPS. The set of 254 blocks is extensible. Registries are defined to identify the block 255 types that may be used and to allow blocks to be included in 256 emergency call signaling. 258 2. Terminology 260 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 261 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 262 document are to be interpreted as described in RFC 2119 [RFC2119]. 264 This document also uses terminology from [RFC5012]. We use the term 265 service provider to refer to an Application Service Provider (ASP). 266 A Voice Service Provider (VSP) is a special type of ASP. With the 267 term "Access Network Provider" we refer to the Internet Access 268 Provider (IAP) and the Internet Service Provider (ISP) without 269 further distinguishing these two entities, since the difference 270 between the two is not relevant for this document. Note that the 271 roles of ASP and access network provider may be provided by a single 272 company. 274 Within each data block definition (see Section 3), the values for the 275 "Use:" label are specified as one of the following: 277 'Required': means it MUST be present in the data structure. 279 'Conditional': means it MUST be present if the specified 280 condition(s) is met. It MAY be present if the condition(s) is not 281 met. 283 'Optional': means it MAY be present. 285 vCard is a data format for representing and exchanging a variety of 286 information about individuals and other entities. For applications 287 that use XML the format defined in vCard is not immediately 288 applicable. For this purpose an XML-based encoding of the 289 information elements defined in the vCard specification has been 290 defined and the name of that specification is xCard. Since the term 291 vCard is more familiar to most readers, we use the term xCard and 292 vCard interchangeably. 294 3. Data Structures 296 This section defines the following five data structures, each as a 297 data block. For each block we define the MIME type, and the XML 298 encoding. The five data structures are: 300 'Data Provider': This block supplies name and contact information 301 for the entity that created the data. Section 3.1 provides the 302 details. 304 'Service Information': This block supplies information about the 305 service. The description can be found in Section 3.2. 307 'Device Information': This block supplies information about the 308 device placing the call. Device information can be found in 309 Section 3.3. 311 'Owner/Subscriber': This block supplies information about the owner 312 of the device or about the subscriber. Details can be found in 313 Section 3.4. 315 'Comment': This block provides a way to supply free form human 316 readable text to the PSAP or emergency responders. This simple 317 structure is defined in Section 3.5. 319 Each block contains a mandatory element. The 320 purpose of the element is to associate all 321 blocks added by the same data provider as a unit. The 322 element associates the data provider block to 323 each of the other blocks added as a unit. Consequently, when a data 324 provider adds additional data to an emergency call (such as device 325 information) it MUST add information about itself (via the data 326 provider block) and the blocks added contain the same value in the 327 element. All blocks added by a single entity 328 at the same time MUST have the same value. 329 The value of the element has the same syntax 330 and properties (specifically, world-uniqueness) as the value of the 331 "Content-ID" message body header field specified in RFC 2045 332 [RFC2045] except that the element is not 333 enclosed in brackets (the "<" and ">" symbols are omitted). In other 334 words, the value of an element is 335 syntactically an addr-spec as specified in RFC 822 [RFC0822]. 337 Note that the xCard format is re-used in some of the data structures 338 to provide contact information. In an xCard there is no way to 339 specify a "main" telephone number. These numbers are useful to 340 emergency responders who are called to a large enterprise. This 341 document adds a new property value to the "tel" property of the TYPE 342 parameter called "main". It can be used in any xCard in additional 343 data. 345 3.1. Data Provider Information 347 This block is intended to be supplied by any service provider in the 348 path of the call or the access network provider. It includes 349 identification and contact information. This block SHOULD be 350 supplied by every service provider in the call path, and by the 351 access network provider. Devices MAY use this block to provide 352 identifying information. The MIME subtype is "application/ 353 EmergencyCallData.ProviderInfo+xml". An access network provider 354 SHOULD provide this block either by value or by reference in the 355 Provided-By section of a PIDF-LO 357 3.1.1. Data Provider String 359 Data Element: Data Provider String 361 Use: Required 363 XML Element: 365 Description: This is a plain text string suitable for displaying the 366 name of the service provider that supplied the data structure. If 367 the device creates the structure, it SHOULD use the value of the 368 contact header in the SIP INVITE. 370 Reason for Need: Inform the call taker of the identity of the entity 371 providing the data. 373 How Used by Call Taker: Allows the call taker to interpret the data 374 in this structure. The source of the information often influences 375 how the information is used, believed or verified. 377 3.1.2. Data Provider ID 379 Data Element: Data Provider ID 381 Use: Conditional. This data SHOULD be provided if the service 382 provider or access provider is located in a jurisdiction that 383 maintains such IDs. For example, in North America, this would be 384 a NENA Company ID. 386 XML Element: 388 Description: A jurisdiction-specific code for the access network 389 provider or service provider shown in the element 390 that created the structure. NOTE: In the US, the provider's NENA 391 Company ID MUST appear here. Additional information can be found 392 at NENA Company Identifier Program [1] or NENA Company ID [2]. 393 The NENA Company ID MUST be in the form of a URI in the following 394 format: urn:nena:companyid: 396 Reason for Need: Inform the call taker of the identity of the entity 397 providing the data. 399 How Used by Call Taker: Where jurisdictions have lists of providers 400 the Data Provider ID provides useful information about the data 401 source. 403 3.1.3. Data Provider ID Series 405 Data Element: Data Provider ID Series 407 Use: Conditional. If Data Provider ID is provided, Data Provider ID 408 Series is required. 410 XML Element: 412 Description: Identifies the issuer of the ProviderId. The Provider 413 ID Series Registry (see Section 9.1) initially contains the 414 following valid entries: 416 * NENA 418 * EENA 420 Reason for Need: Identifies how to interpret the Data Provider ID. 422 How Used by Call Taker: Determines which provider ID registry to 423 consult for more information 425 3.1.4. Type of Data Provider 427 Data Element: Type of Data Provider ID 429 Use: Conditional. If Data Provider ID is provided, Type of Data 430 Provider ID is required. 432 XML Element: 433 Description: Identifies the type of data provider ID being supplied 434 in the ProviderID data element. A registry with an initial set of 435 values is shown in Figure 1 (see also Section 9.1). 437 +------------------------------+------------------------------------+ 438 | Token | Description | 439 +------------------------------+------------------------------------+ 440 |Access Network Provider | Access network service provider | 441 |Telecom Provider | Calling or origination telecom SP | 442 |Telematics Provider | A sensor based service provider, | 443 | | especially vehicle based | 444 |Language Translation Provider | A spoken language translation SP | 445 |Emergency Service Provider | An emergency service provider | 446 | | conveying information to another| 447 | | emergency service provider. | 448 |Emergency Modality Translation| An emergency call specific | 449 | | modality translation service | 450 | | e.g., for sign language | 451 |Relay Provider | A interpretation SP, for example, | 452 | | video relay for sign language | 453 | | interpreting | 454 |Other | Any other type of service provider | 455 +------------------------------+------------------------------------+ 457 Figure 1: Type of Data Provider ID Registry. 459 Reason for Need: Identifies the category of data provider. 461 How Used by Call Taker: This information may be helpful when 462 deciding whom to contact when further information is needed. 464 3.1.5. Data Provider Contact URI 466 Data Element: Data Provider Contact URI 468 Use: Required 470 XML Element: 472 Description: When provided by a service provider or an access 473 network provider, this information MUST be a URI to a 24/7 support 474 organization tasked to provide PSAP support for this emergency 475 call. If the call is from a device, this SHOULD be the contact 476 information of the owner of the device. If a telephone number is 477 the contact address then it MUST be a tel URI. If it is provided 478 as a SIP URI then it MUST be in the form of 479 sip:telephonenumber@serviceprovider:user=phone. Note that this 480 contact information is not used by PSAPs for callbacks (a call 481 from a PSAP directly related to a recently terminated emergency 482 call, placed by the PSAP using a SIP Priority header field set to 483 "psap-callback", as described in [I-D.ietf-ecrit-psap-callback]). 485 Reason for Need: Additional data providers may need to be contacted 486 in error cases or other unusual circumstances. 488 How Used by Call Taker: To contact the supplier of the additional 489 data for assistance in handling the call. 491 3.1.6. Data Provider Languages(s) Supported 493 Data Element: Data Provider Language(s) supported 495 Use: Required. 497 XML Element: 499 Description: The language used by the entity at the Data Provider 500 Contact URI, as an alpha 2-character code as defined in ISO 501 639-1:2002 Codes for the representation of names of languages -- 502 Part 1: Alpha-2 code Multiple instances of this element may occur. 503 Order is significant; preferred language should appear first. The 504 content MUST reflect the languages supported at the contact URI. 506 Note that the 'language' media feature tag, defined in RFC 3840 507 [RFC3840] and the more extensive language negotiation mechanism 508 proposed with [I-D.gellens-negotiating-human-language] are 509 independent of this data provider language indication. 511 Reason for Need: This information indicates if the emergency service 512 authority can directly communicate with the service provider or if 513 an interpreter will be needed. 515 How Used by Call Taker: If call taker cannot speak language(s) 516 supported by the service provider, a translation service will need 517 to be added to the conversation. Alternatively, other persons at 518 the PSAP, besides the call taker, might be consulted for help 519 (depending on the urgency and the type of interaction). 521 3.1.7. xCard of Data Provider 523 Data Element: xCard of Data Provider 525 Use: Optional 527 XML Element: 528 Description: There are many fields in the xCard and the creator of 529 the data structure is encouraged to provide as much information as 530 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 531 minimum. N SHOULD contain the name of the support group or device 532 owner as appropriate. If more than one TEL property is provided, 533 a parameter from the vCard Property Value registry MUST be 534 specified on each TEL. For encoding of the xCard this 535 specification uses the XML-based encoding specified in [RFC6351], 536 referred to in this document as "xCard" 538 Reason for Need: Information needed to determine additional contact 539 information. 541 How Used by Call Taker: Assists call taker by providing additional 542 contact information that may not be included in the SIP invite or 543 the PIDF-LO. 545 3.1.8. Subcontractor Principal 547 When the entity providing the data is a subcontractor, the Data 548 Provider Type is set to that of the primary service provider and this 549 entry is supplied to provide information regarding the subcontracting 550 entity. 552 Data Element: Subcontractor Principal 554 Use: Conditional. This data is required if the entity providing the 555 data is a subcontractor. 557 XML Element: 559 Description: Some providers outsource their obligations to handle 560 aspects of emergency services to specialized providers. If the 561 data provider is a subcontractor to another provider this element 562 contains the DataProviderString of the service provider to 563 indicate which provider the subcontractor is working for. 565 Reason for Need: Identify the entity the subcontractor works for. 567 How Used by Call Taker: Allows the call taker to understand what the 568 relationship between data providers and the service providers in 569 the path of the call are. 571 3.1.9. Subcontractor Priority 573 Data Element: Subcontractor Priority 575 Use: Conditional. This element is required if the Data Provider 576 type is set to "Subcontractor". 578 XML Element: 580 Description: If the subcontractor has to be contacted first then 581 this element MUST have the value "sub". If the provider the 582 subcontractor is working for has to be contacted first then this 583 element MUST have the value "main". 585 Reason for Need: Inform the call taker whom to contact first, if 586 support is needed. 588 How Used by Call Taker: To decide which entity to contact first if 589 assistance is needed. 591 3.1.10. ProviderInfo Example 593 594 597 12345 598 string0987654321@example.org 599 600 Example VoIP Provider 601 602 urn:nena:companyid:ID123 603 NENA 604 Service Provider 605 sip:voip-provider@example.com 606 EN 607 609 610 Hannes Tschofenig 611 612 Hannes 613 Tschofenig 614 615 616 Dipl. Ing. 617 618 --0203 619 620 20090808T1430-0500 621 622 M 623 624 1 625 626 de 627 628 629 2 630 631 en 632 633 634 work 635 636 Example VoIP Provider 637 638 639 640 work 641 645 646 647 648 Linnoitustie 6 649 Espoo 650 Uusimaa 651 02600 652 Finland 653 654 655 656 657 work 658 voice 659 660 661 tel:+358 50 4871445 662 663 664 work 665 666 hannes.tschofenig@nsn.com 667 668 669 work 670 671 geo:60.210796,24.812924 672 673 674 home 675 676 677 http://www.tschofenig.priv.at/key.asc 678 679 680 Finland/Helsinki 681 682 home 683 684 http://www.tschofenig.priv.at 685 686 687 688 690 Figure 2: EmergencyCallData.ProviderInfo Example. 692 3.2. Service Information 694 This block describes the service that the service provider provides 695 to the caller. It SHOULD be included by all SPs in the path of the 696 call. The mime subtype is "application/ 697 EmergencyCallData.ServiceInfo+xml". 699 3.2.1. Service Environment 701 Data Element: Service Environment 703 Use: Required 705 XML Element: 707 Description: This element defines whether a call is from a business 708 or residence caller. Currently, the only valid entries are 709 'Business' or 'Residence'. New values can be defined via the 710 registry created in Figure 22. 712 Reason for Need: To assist in determining equipment and manpower 713 requirements. 715 How Used by Call Taker: Information may be used to assist in 716 determining equipment and manpower requirements for emergency 717 responders. As the information is not always available, and the 718 registry is not all encompassing, this is at best advisory 719 information, but since it mimics a similar capability in some 720 current emergency calling systems, it is known to be valuable. 721 The service provider uses its best information (such as a rate 722 plan, facilities used to deliver service or service description) 723 to determine the information and is not responsible for 724 determining the actual characteristics of the location where the 725 call originates from. 727 3.2.2. Service Type 729 Data Element: Service Delivered by Provider to End User 731 Use: Required 733 XML Element: 735 Description: This defines the type of service over which the call is 736 placed. The implied mobility of this service cannot be relied 737 upon. A registry with an initial set of values is defined in 738 Figure 3. 740 +--------------+----------------------------------------+ 741 | Name | Description | 742 +--------------+----------------------------------------+ 743 | wireless | Wireless Telephone Service: Includes | 744 | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | 745 | | not satellite ) | 746 | coin | Fixed public pay/coin telephones: Any | 747 | | coin or credit card operated device | 748 | one-way | One way outbound service | 749 | prison | Inmate call/service | 750 | temp | Soft dialtone/quick service/warm | 751 | | disconnect/suspended | 752 | MLTS | Multi-line telephone system: Includes | 753 | | all PBX, Centrex, key systems, | 754 | | Shared Tenant Service | 755 | sensor- | 756 | unattended | These are devices that generate DATA | 757 | | ONLY. This is a one-way information | 758 | | transmit without interactive media | 759 | sensor- | | 760 | attended | Devices that are supported by a | 761 | | monitoring service provider or that | 762 | | are capable of supporting interactive| 763 | | media | 764 | POTS | Wireline: Plain Old Telephone Service | 765 | VOIP | An over-the-top service that provides | 766 | | communication over arbitrary Internet| 767 | | access (fixed, nomadic, mobile) | 768 | remote | Off premise extension | 769 | relay | A service where there is a human third | 770 | | party agent who provides additional | 771 | | assistance. This includes sign | 772 | | language relay and telematics | 773 | | services that provide a human on the | 774 | | call. | 775 +--------------+----------------------------------------+ 777 Figure 3: Service Delivered by Provider to End User Registry. 779 More than one value MAY be returned. For example, a VoIP inmate 780 telephone service is a reasonable combination. 782 Reason for Need: Knowing the type of service may assist the PSAP 783 with the handling of the call. 785 How Used by Call Taker: Call takers often use this information to 786 determine what kinds of questions to ask callers, and how much to 787 rely on supportive information. An emergency call from a prison 788 is treated differently that a call from a sensor device. As the 789 information is not always available, and the registry is not all 790 encompassing, this is at best advisory information, but since it 791 mimics a similar capability in some current emergency calling 792 systems, it is known to be valuable. 794 3.2.3. Service Mobility Environment 796 Data Element: Service Mobility Environment 798 Use: Required 800 XML Element: 802 Description: This provides the service provider's view of the 803 mobility of the caller. As the service provider may not know the 804 characteristics of the actual device or access network used, the 805 value MUST NOT be relied upon. A registry reflects the following 806 initial valid entries: 808 * Mobile: the device should be able to move at any time 809 * Fixed: the device is not expected to move unless the service is 810 relocated 812 * Nomadic: the device is not expected to change its point of 813 attachment while on a call 815 * Unknown: no information is known about the service mobility 816 environment for the device 818 Reason for Need: Knowing the service provider's belief of mobility 819 may assist the PSAP with the handling of the call. 821 How Used by Call Taker: To determine whether to assume the location 822 of the caller might change. 824 3.2.4. EmergencyCallData.ServiceInfo Example 826 827 830 string0987654321@example.org 831 832 12345 833 Business 834 MLTS 835 Fixed 836 838 Figure 4: EmergencyCallData.ServiceInfo Example. 840 3.3. Device Information 842 This block provides information about the device used to place the 843 call. It should be provided by any service provider that knows what 844 device is being used, and by the device itself. The mime subtype is 845 "application/EmergencyCallData.DeviceInfo+xml". 847 3.3.1. Device Classification 849 Data Element: Device Classification 851 Use: Optional 853 XML Element: 854 Description: This data element defines the kind of device making the 855 emergency call. If the device provides the data structure, the 856 device information SHOULD be provided. If the service provider 857 provides the structure and it knows what the device is, the 858 service provider SHOULD provide the device information. Often the 859 carrier does not know what the device is. It is possible to 860 receive two Additional Data Associated with a Call data 861 structures, one created by the device and one created by the 862 service provider. This information describes the device, not how 863 it is being used. This data element defines the kind of device 864 making the emergency call. The registry with the initial set of 865 values is shown in Figure 5. 867 +---------------+----------------------------------------+ 868 | Token | Description | 869 +---------------+----------------------------------------+ 870 |cordless | Cordless handset | 871 |fixed | Fixed phone | 872 |satellite | Satellite phone | 873 |sensor-fixed | Fixed (non mobile) sensor/alarm device | 874 |desktop | Desktop PC | 875 |laptop | Laptop computing device | 876 |tablet | Tablet computing device | 877 |alarm-monitored| Alarm system | 878 |sensor-mobile | Mobile sensor device | 879 |aircraft | Aircraft telematics device | 880 |automobile | Automobile/cycle/off-road telematics | 881 |truck | Truck/construction telematics | 882 |farm | Farm equipment telematics | 883 |marine | Marine telematics | 884 |personal | Personal telematics device | 885 |feature-phone | Feature (not smart-) cellular phone | 886 |smart-phone | Smart-phone cellular phone | 887 |game | Gaming console | 888 |text-only | Other text device | 889 |NA | Not Available | 890 +---------------+----------------------------------------+ 892 Figure 5: Device Classification Registry. 894 Reason for Need: The device classification implies the capability of 895 the calling device and assists in identifying the meaning of the 896 emergency call location information that is being presented. For 897 example, does the device require human intervention to initiate a 898 call or is this call the result of programmed instructions? Does 899 the calling device have the ability to update location or 900 condition changes? Is this device interactive or a one-way 901 reporting device? 903 How Used by Call Taker: May assist with location of caller. For 904 example, a cordless handset may be outside or next door. May 905 provide the calltaker some context about the caller, the 906 capabilities of the device used for the call or the environment 907 the device is being used in. 909 3.3.2. Device Manufacturer 911 Data Element: Device Manufacturer 913 Use: Optional 915 XML Element: 917 Description: The plain language name of the manufacturer of the 918 device. 920 Reason for Need: Used by PSAP management for post-mortem 921 investigation/resolution. 923 How Used by Call Taker: Probably not used by the calltaker, but by 924 PSAP management. 926 3.3.3. Device Model Number 928 Data Element: Device Model Number 930 Use: Optional 932 XML Element: 934 Description: Model number of the device. 936 Reason for Need: Used by PSAP management for after action 937 investigation/resolution. 939 How Used by Call Taker: Probably not used by the calltaker, but by 940 PSAP management. 942 3.3.4. Unique Device Identifier 944 Data Element: Unique Device Identifier 946 Use: Optional 948 XML Element: 950 XML Attribute: 951 Description: A string that identifies the specific device (or the 952 device's current SIM) making the call or creating an event. Note 953 that more than one may be present, to supply more 954 than one of the identifying values. 956 The attribute identifies the type of device 957 identifier. A registry with an initial set of values can be seen 958 in Figure 6. 960 +--------+------------------------------------------+ 961 | Token | Description | 962 +--------+------------------------------------------+ 963 | MEID | Mobile Equipment Identifier (CDMA) | 964 | ESN | Electronic Serial Number (GSM) | 965 | MAC | Media Access Control Address (IEEE) | 966 | WiMAX | Device Certificate Unique ID | 967 | IMEI | International Mobile Equipment ID (GSM) | 968 | IMSI | International Mobile Subscriber ID (GSM) | 969 | UDI | Unique Device Identifier | 970 | RFID | Radio Frequency Identification | 971 | SN | Manufacturer Serial Number | 972 +--------+------------------------------------------+ 974 Figure 6: Registry with Device Identifier Types. 976 Reason for Need: Uniquely identifies the device (or, in the case of 977 IMSI, a SIM), independent of any signaling identifiers present in 978 the call signaling stream. 980 How Used by Call Taker: Probably not used by the call taker; may be 981 used by PSAP management during an investigation. 983 Example: 12345 985 3.3.5. Device/Service Specific Additional Data Structure 987 Data Element: Device/service specific additional data structure 989 Use: Optional 991 XML Element: 992 Description: A URI representing additional data whose schema is 993 specific to the device or service which created it. (For example, 994 a medical device or medical device monitoring service may have a 995 defined set of medical data.) The URI, when dereferenced, MUST 996 yield a data structure defined by the Device/service specific 997 additional data type value. Different data may be created by each 998 classification; e.g., a medical device created data set. 1000 Reason for Need: Provides device/service specific data that may be 1001 used by the call taker and/or responders. 1003 How Used by Call Taker: Provide information to guide call takers to 1004 select appropriate responders, give appropriate pre-arrival 1005 instructions to callers, and advise responders of what to be 1006 prepared for. May be used by responders to guide assistance 1007 provided. 1009 3.3.6. Device/Service Specific Additional Data Structure Type 1011 Data Element: Type of device/service specific additional data 1012 structure 1014 Use: Conditional. MUST be provided when device/service specific 1015 additional URI is provided 1017 XML Element: 1019 Description: Value from a registry defined by this document to 1020 describe the type of data that can be retrieved from the device/ 1021 service specific additional data structure. Initial values are: 1023 * IEEE 1512 1025 IEEE 1512 is the USDoT model for traffic incidents. 1027 Reason for Need: This data element allows identification of 1028 externally defined schemas, which may have additional data that 1029 may assist in emergency response. 1031 How Used by Call Taker: This data element allows the end user 1032 (calltaker or first responder) to know what type of additional 1033 data may be available to aid in providing the needed emergency 1034 services. 1036 Note: Information which is specific to a location or a caller 1037 (person) should not be placed in this section. 1039 3.3.7. Issues with getting new types of data into use 1041 This document describes two mechanisms which allow extension of the 1042 kind of data provided with an emergency call: define a new block or 1043 define a new service specific additional data URL for the DeviceInfo 1044 block. While defining new data types and getting a new device or 1045 application to send the new data may be easy, getting PSAPs and 1046 responders to actually retrieve the data and use it will be 1047 difficult. New mechanism providers should understand that acquiring 1048 and using new forms of data usually require software upgrades at the 1049 PSAP and/or responders, as well as training of call takers and 1050 responders in how to interpret and use the information. Legal and 1051 operational review may also be needed. Overwhelming a call taker or 1052 responder with too much information is highly discouraged. Thus, the 1053 barrier to supporting new data is quite high. 1055 The mechanisms this document describes are meant to encourage 1056 development of widely supported, common data formats for classes of 1057 devices. If all manufacturers of a class of device use the same 1058 format, and the data can be shown to improve outcomes, then PSAPs and 1059 responders may be encouraged to upgrade their systems and train their 1060 staff to use the data. Variations, however well intentioned, are 1061 unlikely to be supported. 1063 Implementers should consider that data from sensor-based devices in 1064 some cases may not be useful to call takers or PSAPs (and privacy or 1065 other considerations may preclude the PSAP from touching the data), 1066 but may be of use to responders. Some standards being developed by 1067 other organizations to carry data from the PSAP to responders are 1068 designed to carry all additional data supplied in the call that 1069 conform to this document, even if the PSAP does not fetch or 1070 interpret the data. This allows responders to get the data even if 1071 the PSAP does not. 1073 3.3.8. Choosing between defining a new type of block or new type of 1074 device/service specific additional data 1076 For devices that have device or service specific data, there are two 1077 choices to carry it. A new block can be defined, or the device/ 1078 service specific additional data URL the DeviceInfo block can be used 1079 and a new type for it defined . The data passed would likely be the 1080 same in both cases. Considerations for choosing which mechanism to 1081 register under include: 1083 Applicability: Information which will be carried by many kinds of 1084 devices or services are more appropriately defined as separate 1085 blocks. 1087 Privacy: Information which may contain private data may be better 1088 sent in the DeviceInfo block, rather than a new block so that 1089 implementations are not tempted to send the data by value, and 1090 thus having more exposure to the data than forcing the data to be 1091 retrieved via the URL in DeviceInfo. 1093 Size: Information which may be very may be better sent in the 1094 DeviceInfo block, rather than a new block so that implementations 1095 are not tempted to send the data by value. Conversely, data which 1096 is small may best be sent in a separate block so that it can be 1097 sent by value 1099 Availability of a server: Providing the data via the device block 1100 requires a server be made available to retrieve the data. 1101 Providing the data via new block allows it to be sent by value 1102 (CID). 1104 3.3.9. EmergencyCallData.DeviceInfo Example 1106 1107 1110 string0987654321@example.org 1111 1112 12345 1113 Fixed phone 1114 Nokia 1115 Lumia 800 1116 35788104 1117 1118 1120 Figure 7: EmergencyCallData.DeviceInfo Example. 1122 3.4. Owner/Subscriber Information 1124 This block describes the owner of the device (if provided by the 1125 device) or the subscriber information, if provided by a service 1126 provider. The contact location is not necessarily the location of 1127 the caller or incident, but is rather the nominal contact address. 1128 The mime subtype is "application/EmergencyCallData.Subscriber+xml". 1130 In some jurisdictions some or all parts of the subscriber-specific 1131 information are subject to privacy constraints. These constraints 1132 vary but dictate what information and be displayed and logged. A 1133 general privacy indicator expressing a desire for privacy is 1134 provided. The interpretation of how this is applied is left to the 1135 receiving jurisdiction as the custodians of the local regulatory 1136 requirements. 1138 3.4.1. Subscriber Data Privacy Indicator 1140 Attribute: privacyRequested, boolean. 1142 Use: Conditional. This attribute MUST be provided if the owner/ 1143 subscriber information block is not empty. 1145 Description: The subscriber data privacy indicator specifically 1146 expresses the subscriber's desire for privacy. In some 1147 jurisdictions subscriber services can have a specific "Type of 1148 Service" which prohibits information, such as the name of the 1149 subscriber, from being displayed. This attribute should be used 1150 to explicitly indicate whether the subscriber service includes 1151 such constraints. 1153 Reason for Need: Some jurisdictions require subscriber privacy to be 1154 observed. 1156 How Used by Call Taker: Where privacy is indicated the call taker 1157 may not have access to some aspects of the subscriber information. 1159 3.4.2. xCard for Subscriber's Data 1161 Data Element: xCARD for Subscriber's Data 1163 Use: Conditional. Subscriber data is provided unless it is not 1164 available. Some services, for example prepaid phones, non- 1165 initialized phones, etc., do not have information about the 1166 subscriber. 1168 XML Element: 1170 Description: Information known by the service provider or device 1171 about the subscriber; e.g., Name, Address, Individual Telephone 1172 Number, Main Telephone Number and any other data. N, ORG (if 1173 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1174 than one TEL property is provided, a parameter from the vCard 1175 Property Value registry MUST be specified on each TEL. 1177 Reason for Need: When the caller is unable to provide information, 1178 this data may be used to obtain it 1180 How Used by Call Taker: Obtaining critical information about the 1181 caller and possibly the location when it is not able to be 1182 obtained otherwise. 1184 3.4.3. EmergencyCallData.SubscriberInfo Example 1186 1187 1191 string0987654321@example.org 1192 1193 1194 1195 1196 Simon Perreault 1197 1198 Perreault 1199 Simon 1200 1201 1202 ing. jr 1203 M.Sc. 1204 1205 --0203 1206 1207 20090808T1430-0500 1208 1209 M 1210 1211 1 1212 1213 fr 1214 1215 1216 2 1217 1218 en 1219 1220 1221 work 1222 1223 Viagenie 1224 1225 1226 1227 work 1228 1232 1233 1234 1235 2875 boul. Laurier, suite D2-630 1236 Quebec 1237 QC 1238 G1V 2M2 1239 Canada 1240 1241 1242 1243 1244 work 1245 voice 1246 1247 1248 tel:+1-418-656-9254;ext=102 1249 1250 1251 1252 1253 work 1254 text 1255 voice 1256 cell 1257 video 1258 1259 1260 tel:+1-418-262-6501 1261 1262 1263 work 1264 1265 simon.perreault@viagenie.ca 1266 1267 1268 work 1269 1270 geo:46.766336,-71.28955 1271 1272 1273 work 1274 1275 1276 http://www.viagenie.ca/simon.perreault/simon.asc 1277 1278 1279 America/Montreal 1280 1281 home 1282 1283 http://nomis80.org 1284 1285 1286 1287 1288 1290 Figure 8: EmergencyCallData.SubscriberInfo Example. 1292 3.5. Comment 1294 This block provides a mechanism for the data provider to supply 1295 extra, human readable information to the PSAP. It is not intended 1296 for a general purpose extension mechanism nor does it aim to provide 1297 machine-reable content. The mime subtype is "application/ 1298 EmergencyCallData.Comment+xml" 1300 3.5.1. Comment 1302 Data Element: EmergencyCallData.Comment 1304 Use: Optional 1306 XML Element: 1308 Description: Human readable text providing additional information to 1309 the PSAP staff. 1311 Reason for Need: Explanatory information for values in the data 1312 structure 1314 How Used by Call Taker: To interpret the data provided 1316 3.5.2. EmergencyCallData.Comment Example 1318 1319 1323 string0987654321@example.org 1324 1325 This is an example text. 1326 1328 Figure 9: EmergencyCallData.Comment Example. 1330 4. Data Transport Mechanisms 1332 This section defines how to convey additional data to an emergency 1333 service provider. Two different means are specified: the first uses 1334 the call signaling; the second uses the element of a 1335 PIDF-LO [RFC4119]. 1337 1. First, the ability to embed a Uniform Resource Identifier (URI) 1338 in an existing SIP header field, the Call-Info header, is 1339 defined. The URI points to the additional data structure. The 1340 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1341 document adds a new compound token starting with the value 1342 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1343 the "purpose" parameter is set to a value starting with 1344 'EmergencyCallData', then the Call-Info header contains either an 1345 HTTPS URL pointing to an external resource or a CID (content 1346 indirection) URI that allows the data structure to be placed in 1347 the body of the SIP message. The "purpose" parameter also 1348 indicates the kind of data (by its MIME type) that is available 1349 at the URI. As the data is conveyed using a URI in the SIP 1350 signaling, the data itself may reside on an external resource, or 1351 may be contained within the body of the SIP message. When the 1352 URI refers to data at an external resource, the data is said to 1353 be passed by reference. When the URI refers to data contained 1354 within the body of the SIP message, the data is said to be passed 1355 by value. A PSAP or emergency responder is able to examine the 1356 type of data provided and selectively inspect the data it is 1357 interested in, while forwarding all of it (the values or 1358 references) to downstream entities. To be conveyed in a SIP 1359 body, additional data about a call is defined as a series of MIME 1360 objects. Each block defined in this document is an XML data 1361 structure identified by its MIME type. (Blocks defined by others 1362 may be encoded in XML or not, as identified by their MIME 1363 registration.) As usual, whenever more than one MIME part is 1364 included in the body of a message, MIME-multipart (i.e., 1365 'multipart/mixed') encloses them all. This document defines a 1366 set of XML schemas and MIME types used for each block defined 1367 here. When additional data is passed by value in the SIP 1368 signaling, each CID URL points to one block in the body. 1369 Multiple URIs are used within a Call-Info header field (or 1370 multiple Call-Info header fields) to point to multiple blocks. 1372 When additional data is provided by reference (in SIP signaling 1373 or Provided-By), each HTTPS URL references one block; the data is 1374 retrieved with an HTTPS GET operation, which returns one of the 1375 blocks as an object (the blocks defined here are returned as XML 1376 objects). 1378 2. Second, the ability to embed additional data structures in the 1379 element of a PIDF-LO [RFC4119] is defined. Besides 1380 a service provider in the call path, the access network provider 1381 may also have similar information that may be valuable to the 1382 PSAP. The access network provider may provide location in the 1383 form of a PIDF-LO from a location server via a location 1384 configuration protocol. The data structures described in this 1385 document are not specific to the location itself, but rather 1386 provides descriptive information having to do with the immediate 1387 circumstances about the provision of the location (who the access 1388 network is, how to contact that entity, what kind of service the 1389 access network provides, subscriber information, etc.). This 1390 data is similar in nearly every respect to the data known by 1391 service providers in the path of the call. When the access 1392 network provider and service provider are separate entities, the 1393 access network does not participate in the application layer 1394 signaling (and hence cannot add a Call-Info header field to the 1395 SIP message), but may provide location information to assist in 1396 locating the caller's device. The element of the 1397 PIDF-LO is a mechanism for the access network provider to supply 1398 the information about the entity or organization that supplied 1399 this location information. For this reason, this document 1400 describes a namespace per RFC 4119 for inclusion in the 1401 element of a PIDF-LO for adding information known 1402 to the access network provider. 1404 One or more blocks of data registered in the Emergency Call 1405 Additional Data registry, as defined in Section 9.1, may be included 1406 or referenced in the SIP signaling (using the Call-Info header field) 1407 or in the element of a PIDF-LO. Every block must be 1408 one of the types in the registry. Since the data of an emergency 1409 call may come from multiple sources, the data itself needs 1410 information describing the source. Consequently, each entity adding 1411 additional data MUST supply the "Data Provider" block. All other 1412 blocks are optional, but each entity SHOULD supply any blocks where 1413 it has at least some of the information in the block. 1415 4.1. Transmitting Blocks using the Call-Info Header 1417 A URI to a block MAY be inserted in a SIP request or response method 1418 (most often INVITE or MESSAGE) with a Call-Info header field 1419 containing a purpose value starting with 'EmergencyCallData' and the 1420 type of data available at the URI. The type of data is denoted by 1421 including the root of the MIME type (not including the 1422 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1423 separator. For example, when referencing a block with MIME type 1424 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1425 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1426 "Call-Info" header field for this would be: 1428 Call-Info: https://www.example.com/23sedde3; 1429 purpose="EmergencyCallData.ProviderInfo" 1431 A Call-info header with a purpose value starting with 1432 'EmergencyCallData' MUST only be sent on an emergency call, which can 1433 be ascertained by the presence of an emergency service urn in a Route 1434 header of a SIP message. 1436 If the data is provided by reference, an HTTPS URI MUST be included 1437 and consequently Transport Layer Security (TLS) protection is applied 1438 for protecting the retrieval of the information. 1440 The data may also be supplied by value in a SIP message. In this 1441 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1442 referencing the MIME body part. 1444 More than one Call-Info header with a purpose value starting with 1445 'EmergencyCallData' can be expected, but at least one MUST be 1446 provided. The device MUST provide one if it knows no service 1447 provider is in the path of the call. The device MAY insert one if it 1448 uses a service provider. Any service provider in the path of the 1449 call MUST insert its own. For example, a device, a telematics 1450 service provider in the call path, as well as the mobile carrier 1451 handling the call will each provide one. There may be circumstances 1452 where there is a service provider who is unaware that the call is an 1453 emergency call and cannot reasonably be expected to determine that it 1454 is an emergency call. In that case, that service provider is not 1455 expected to provide EmergencyCallData. 1457 4.2. Transmitting Blocks by Reference using the Provided-By Element 1459 The 'EmergencyCallDataReference' element is used to transmit an 1460 additional data block by reference within a 'Provided-By' element of 1461 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1462 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1463 type of data block referenced. The value of 'ref' is an HTTPS URL 1464 that resolves to a data structure with information about the call. 1465 The value of 'purpose' is the same as used in a 'Call-Info' header 1466 field (as specified in Section 4.1). 1468 For example, to reference a block with MIME type 'application/ 1469 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1470 to 'EmergencyCallData.ProviderInfo'. An example 1471 'EmergencyCallDataReference' element for this would be: 1473 1476 4.3. Transmitting Blocks by Value using the Provided-By Element 1478 It is RECOMMENDED that access networks supply the data specified in 1479 this document by reference, but they MAY provide the data by value. 1481 The 'EmergencyCallDataValue' element is used to transmit an 1482 additional data block by value within a 'Provided-By' element of a 1483 PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: 1484 'purpose' to indicate the type of data block contained. The value of 1485 'purpose' is the same as used in a 'Call-Info' header field (as 1486 specified in Section 4.1, and in Section 4.1). The same XML 1487 structure as would be contained in the corresponding MIME type body 1488 part is placed inside the 'EmergencyCallDataValue' element. 1490 For example: 1492 1494 1495 1497 1499 This is an example text. 1500 1501 1502 1503 1505 Test 1506 NENA 1507 Access Infrastructure Provider 1508 1509 sip:15555550987@burf.example.com;user=phone 1510 1511 1512 1514 Example Provided-By by Value. 1516 4.4. The Content-Disposition Parameter 1518 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1519 It updates and clarifies handling originally defined in RFC 3261 1520 [RFC3261] based on implementation experience. While RFC 3261 did not 1521 mandate support for 'multipart' message bodies, 'multipart/mixed' 1522 MIME bodies are used by many extensions (including this document) 1523 today. For example, adding a PIDF-LO, SDP, and additional data in 1524 body of a SIP message requires a 'multipart' message body. 1526 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1527 parameter for the Content-Disposition header field. These RFCs 1528 describe how a UAS reacts if it receives a message body whose content 1529 type or disposition type it does not understand. If the 'handling' 1530 parameter has the value "optional", the UAS ignores the message body. 1531 If the 'handling' parameter has the value "required", the UAS returns 1532 a 415 (Unsupported Media Type) response. The 'by-reference' 1533 disposition type allows a SIP message to contain a reference to the 1534 body part, and the SIP UA processes the body part according to the 1535 reference. This is the case for the Call-info header containing a 1536 Content Indirection (CID) URL. 1538 As an example, a SIP message indicates the Content-Disposition 1539 parameter in the body of the SIP message as shown in Figure 10. 1541 Content-Type: application/sdp 1543 ...Omit Content-Disposition here; defaults are ok 1544 ...SDP goes in here 1546 --boundary1 1548 Content-Type: application/pidf+xml 1549 Content-ID: 1550 Content-Disposition: by-reference;handling=optional 1552 ...PIDF-LO goes in here 1554 --boundary1-- 1555 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1556 Content-ID: <1234567890@atlanta.example.com> 1557 Content-Disposition: by-reference; handling=optional 1559 ...Data provider information data goes in here 1561 --boundary1-- 1563 Figure 10: Example for use of the Content-Disposition Parameter in 1564 SIP. 1566 5. Examples 1568 This section illustrates a longer and more complex example, as shown 1569 in Figure 11. In this example additional data is added by the end 1570 device, included by the VoIP provider (via the PIDF-LO), and provided 1571 by the access network provider. 1573 [================] (1) [================] 1574 [ O +----+ ] Emergency Call [ ] 1575 [ /|\ | UA |-------------------------------> ] 1576 [ | +----+ ] +Device Info [ ] 1577 [ / \ ] +Data Provider Info [ ] 1578 [ ] +Location URI [ ] 1579 [ Access Network ] [ ] 1580 [ Provider ] [ VoIP Provider ] 1581 [ ] [ example.org ] 1582 [ ^ ] [ ] 1583 [=======.========] [============|===] 1584 . | 1585 . | 1586 . [================] | 1587 . [ ] (2) | 1588 . (3) [ <--------------+ 1589 ....................> PSAP ] Emergency Call 1590 Location [ ] +Device Info 1591 +Owner/Subscriber Info [ ] +Data Provider Info #2 1592 +Device Info [ ] +Location URI 1593 +Data Provider Info #3 [================] 1595 Legend: 1597 --- Emergency Call Setup Procedure 1598 ... Location Retrieval/Response 1599 Figure 11: Additional Data Example Flow 1601 The example scenario starts with the end device itself adding device 1602 information, owner/subscriber information, a location URI, and data 1603 provider information to the outgoing emergency call setup message 1604 (see step #1 in Figure 11). The SIP INVITE example is shown in 1605 Figure 12. 1607 INVITE urn:service:sos SIP/2.0 1608 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1609 Max-Forwards: 70 1610 To: 1611 From: Hannes Tschofenig ;tag=9fxced76sl 1612 Call-ID: 3848276298220188511@example.com 1613 Call-Info: ;purpose=icon, 1614 ;purpose=info, 1615 1616 ;purpose=EmergencyCallData.ProviderInfo, 1617 1618 ;purpose=EmergencyCallData.DeviceInfo 1619 Geolocation: 1620 Geolocation-Routing: yes 1621 Accept: application/sdp, application/pidf+xml, 1622 application/EmergencyCallData.ProviderInfo+xml 1623 CSeq: 31862 INVITE 1624 Contact: 1625 Content-Type: multipart/mixed; boundary=boundary1 1627 Content-Length: ... 1629 --boundary1 1631 Content-Type: application/sdp 1633 ...SDP goes here 1635 --boundary1-- 1637 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1638 Content-ID: <0123456789@atlanta.example.com> 1639 Content-Disposition: by-reference;handling=optional 1640 1642 1645 string0987654321@example.org 1646 1647 SoftPhn 1648 00-0d-4b-30-72-df 1650 1652 --boundary1-- 1654 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1655 Content-ID: <1234567890@atlanta.example.com> 1656 Content-Disposition: by-reference;handling=optional 1657 1658 1661 12345 1662 string0987654321@example.org 1663 1664 Hannes Tschofenig 1665 1666 Other 1667 sip:hannes@example.com 1668 EN 1669 1671 1672 Hannes Tschofenig 1673 1674 Hannes 1675 Tschofenig 1676 1677 1678 Dipl. Ing. 1679 1680 --0203 1681 1682 20090808T1430-0500 1683 1684 M 1685 1686 1 1687 1688 de 1689 1690 1691 2 1692 1693 en 1694 1695 1696 1697 work 1698 1702 1703 1704 1705 Linnoitustie 6 1706 Espoo 1707 Uusimaa 1708 02600 1709 Finland 1710 1711 1712 1713 1714 work 1715 voice 1716 1717 1718 tel:+358 50 4871445 1719 1720 1721 work 1722 1723 hannes.tschofenig@nsn.com 1724 1725 1726 work 1727 1728 geo:60.210796,24.812924 1729 1730 1731 1732 home 1733 1734 https://www.example.com/key.asc 1735 1736 1737 Finland/Helsinki 1738 1739 home 1740 1741 http://example.com/hannes.tschofenig 1742 1743 1744 1745 1746 --boundary1-- 1748 Figure 12: End Device sending SIP INVITE with Additional Data. 1750 In this example, information available to the access network operator 1751 is included in the call setup message only indirectly via the use of 1752 the location reference. The PSAP has to retrieve it via a separate 1753 look-up step. Since the access network provider and the VoIP service 1754 provider are two independent entities in this scenario, the access 1755 network operator is not involved in application layer exchanges; the 1756 SIP INVITE transits the access network transparently, as illustrated 1757 in step #1. No change to the SIP INVITE is applied. 1759 When the VoIP service provider receives the message and determines 1760 based on the Service URN that the incoming request is an emergency 1761 call. It performs the typical emergency services related tasks, 1762 including location-based routing, and adds additional data, namely 1763 service and subscriber information, to the outgoing message. For the 1764 example we assume a VoIP service provider that deploys a back-to-back 1765 user agent allowing additional data to be included in the body of the 1766 SIP message (rather than per reference in the header), which allows 1767 us to illustrate the use of multiple data provider info blocks. The 1768 resulting message is shown in Figure 13. 1770 INVITE sips:psap@example.org SIP/2.0 1771 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1772 Max-Forwards: 70 1773 To: 1774 From: Hannes Tschofenig ;tag=9fxced76sl 1775 Call-ID: 3848276298220188511@example.com 1776 Call-Info: ;purpose=icon, 1777 ;purpose=info, 1778 1779 ;purpose=EmergencyCallData.ProviderInfo 1780 1781 ;purpose=EmergencyCallData.DeviceInfo 1782 Call-Info: 1783 ;purpose=EmergencyCallData.ServiceInfo 1784 Call-Info: 1785 ;purpose=EmergencyCallData.ProviderInfo 1786 Geolocation: 1787 Geolocation-Routing: yes 1788 Accept: application/sdp, application/pidf+xml, 1789 application/EmergencyCallData.ProviderInfo+xml 1790 CSeq: 31862 INVITE 1791 Contact: 1792 Content-Type: multipart/mixed; boundary=boundary1 1794 Content-Length: ... 1796 --boundary1 1798 Content-Type: application/sdp 1800 ...SDP goes here 1802 --boundary1-- 1804 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1805 Content-ID: <0123456789@atlanta.example.com> 1806 Content-Disposition: by-reference;handling=optional 1807 1809 1812 string0987654321@example.org 1813 1814 SoftPhn 1815 00-0d-4b-30-72-df 1817 1819 --boundary1-- 1821 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1822 Content-ID: <1234567890@atlanta.example.com> 1823 Content-Disposition: by-reference;handling=optional 1824 1825 1828 string0987654321@example.org 1829 1830 Hannes Tschofenig 1831 1832 Other 1833 sip:hannes@example.com 1834 EN 1835 1837 1838 Hannes Tschofenig 1839 1840 Hannes 1841 Tschofenig 1842 1843 1844 Dipl. Ing. 1845 1846 --0203 1847 1848 20090808T1430-0500 1849 1850 M 1851 1852 1 1853 1854 de 1855 1856 1857 2 1858 1859 en 1860 1861 1862 1863 work 1864 1868 1869 1870 1871 Linnoitustie 6 1872 Espoo 1873 Uusimaa 1874 02600 1875 Finland 1876 1877 1878 1879 1880 work 1881 voice 1882 1883 1884 tel:+358 50 4871445 1885 1886 1887 work 1888 1889 hannes.tschofenig@nsn.com 1890 1891 1892 work 1893 1894 geo:60.210796,24.812924 1895 1896 1897 1898 home 1899 1900 https://www.example.com/key.asc 1901 1902 1903 Finland/Helsinki 1904 1905 home 1906 1907 http://example.com/hannes.tschofenig 1908 1909 1910 1911 1913 --boundary1-- 1915 Content-Type: application/EmergencyCallData.ServiceInfo+xml 1916 Content-ID: 1917 Content-Disposition: by-reference;handling=optional 1918 1919 1922 string0987654321@example.org 1923 1924 Residence 1925 VOIP 1926 Unknown 1927 1929 --boundary1-- 1931 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1932 Content-ID: 1933 Content-Disposition: by-reference;handling=optional 1934 1935 1938 string0987654321@example.org 1939 1940 Example VoIP Provider 1941 1942 urn:nena:companyid:ID123 1943 NENA 1944 Service Provider 1945 sip:voip-provider@example.com 1946 EN 1947 1949 1950 John Doe 1951 1952 John 1953 Doe 1954 1955 1956 1957 1958 --0203 1959 1960 20090808T1430-0500 1961 1962 M 1963 1964 1 1965 1966 en 1967 1968 1969 work 1970 1971 Example VoIP Provider 1972 1973 1974 1975 work 1976 1979 1980 1981 1982 Downing Street 10 1983 London 1984 1985 SW1A 2AA 1986 UK 1987 1988 1989 1990 1991 work 1992 voice 1993 1994 1995 sips:john.doe@example.com 1996 1997 1998 work 1999 2000 john.doe@example.com 2001 2002 2003 work 2004 2005 geo:51.503396, 0.127640 2006 2007 Europe/London 2008 2009 home 2010 2011 http://www.example.com/john.doe 2012 2013 2014 2015 2017 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2019 Finally, the PSAP requests location information from the access 2020 network operator. The response is shown in Figure 14. Along with 2021 the location information additional data is provided in the 2022 element of the PIDF-LO. 2024 2025 2030 2031 2032 2033 2035 AU 2036 NSW 2037 Wollongong 2038 North Wollongong 2039 Flinders 2040 Street 2041 Campbell Street 2042 Gilligan's Island 2043 Corner 2044 Video Rental Store 2045 2500 2046 Westerns and Classics 2047 store 2048 Private Box 15 2049 2050 2051 2052 true 2053 2054 2013-12-10T20:00:00Z 2055 2056 2057 802.11 2059 2062 2065 2066 2068 string0987654321@example.org 2069 2070 University of California, Irvine 2071 2072 urn:nena:companyid:uci 2073 NENA 2074 Other 2075 tel:+1 9498245222 2076 EN 2077 2079 2081 string0987654321@example.org 2082 2083 This is an example text. 2084 2086 2087 2088 2089 mac:00-0d-4b-30-72-df 2090 2013-07-09T20:57:29Z 2091 2092 2094 Figure 14: Access Network Provider returning PIDF-LO with Additional 2095 Data. 2097 6. XML Schemas 2099 This section defines the XML schemas of the five data blocks. 2100 Additionally, the Provided-By schema is specified. 2102 6.1. EmergencyCallData.ProviderInfo XML Schema 2104 2105 2115 2118 2120 2121 2122 2123 2124 2126 2130 2133 2134 2135 2136 2137 2138 2140 2141 2142 2145 2148 2151 2154 2157 2160 2163 2167 2170 2173 2175 2176 2178 2180 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2182 6.2. EmergencyCallData.ServiceInfo XML Schema 2184 2185 2193 2196 2198 2199 2200 2203 2206 2209 2212 2215 2218 2219 2221 2223 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2225 6.3. EmergencyCallData.DeviceInfo XML Schema 2227 2228 2235 2238 2240 2241 2242 2245 2248 2251 2254 2256 2257 2258 2259 2262 2263 2264 2266 2268 2271 2274 2276 2277 2279 2281 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2283 6.4. EmergencyCallData.SubscriberInfo XML Schema 2285 2286 2295 2298 2300 2302 2303 2304 2305 2308 2311 2314 2315 2316 2317 2319 2321 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2323 6.5. EmergencyCallData.Comment XML Schema 2325 2326 2334 2337 2339 2340 2341 2344 2348 2350 2351 2353 2354 2355 2356 2357 2358 2359 2361 2363 Figure 19: EmergencyCallData.Comment XML Schema. 2365 6.6. Provided-By XML Schema 2367 This section defines the Provided-By schema. 2369 2370 2383 2384 2385 2386 2387 2389 2391 2392 2393 2396 2400 2404 2407 2409 2411 2413 2414 2415 2416 2417 2419 2420 2422 2424 2425 2426 2428 2430 2431 2432 2435 2438 2441 2444 2448 2451 2452 2454 2456 Figure 20: Provided-By XML Schema. 2458 7. Security Considerations 2460 The information in this data structure will usually be considered 2461 private. HTTPS is specified to require the provider of the 2462 information to validate the credentials of the requester. While the 2463 creation of a public key infrastructure (PKI) that has global scope 2464 may be difficult, the alternatives to creating devices and services 2465 that can provide critical information securely are more daunting. 2466 The provider may enforce any policy it wishes to use, but PSAPs and 2467 responder agencies should deploy a PKI so that providers of 2468 additional data can check the certificate of the client and decide 2469 the appropriate policy to enforce based on that certificate. 2471 Ideally, the PSAP and emergency responders will be given credentials 2472 signed by an authority trusted by the data provider. In most 2473 circumstances, nationally recognized credentials would be sufficient, 2474 and if the emergency services arranges a PKI, data providers could be 2475 provisioned with the root CA public key for a given nation. Some 2476 nations are developing a PKI for this, and related, purposes. Since 2477 calls could be made from devices where the device and/or the service 2478 provider(s) are not local to the emergency authorities, globally 2479 recognized credentials are useful. This might be accomplished by 2480 extending the notion of the "forest guide" described in [RFC5222] to 2481 allow the forest guide to provide the credential of the PKI root for 2482 areas that it has coverage information for, but standards for such a 2483 mechanism are not yet available. In its absence, the data provider 2484 will need to obtain the root CA credentials for any areas it is 2485 willing to provide additional data by out of band means. With the 2486 credential of the root CA for a national emergency services PKI, the 2487 data provider server can validate the credentials of an entity 2488 requesting additional data by reference. 2490 The data provider also needs a credential that can be verified by the 2491 emergency services to know that it is receiving data from the right 2492 server. The emergency authorities could provide credentials, 2493 distinguishable from credentials it provides to emergency responders 2494 and PSAPs, which could be used to validate data providers. Such 2495 credentials would have to be acceptable to any PSAP or responder that 2496 could receive a call with additional data supplied by that provider. 2497 This would be extensible to global credential validation using the 2498 forest guide as above. In the absence of such credentials, the 2499 emergency authorities could maintain a list of local data providers' 2500 credentials provided to it out of band. At a minimum, the emergency 2501 authorities could obtain a credential from the DNS entry of the 2502 domain in the Additional Data URI to at least validate that the 2503 server is known to the domain providing the URI. 2505 Data provided by devices by reference have similar credential 2506 validation issues to service providers, and the solutions are the 2507 same. 2509 8. Privacy Considerations 2511 This document enables functionality for conveying additional 2512 information about the caller to the callee. Some of this information 2513 is personal data and therefore privacy concerns arise. An explicit 2514 privacy indicator for information directly relating to the callers 2515 identity is defined and use is mandatory. However, observance of 2516 this request for privacy and what information it relates to is 2517 controlled by the destination jurisdiction. 2519 There are a number of privacy concerns with regular real-time 2520 communication services that are also applicable to emergency calling. 2521 Data protection regulation world-wide has, however, decided to create 2522 exceptions for emergency services since the drawbacks of disclosing 2523 personal data in comparison to the benefit for the emergency caller 2524 are often towards the latter. Hence, the data protection rights of 2525 individuals are often waived for emergency situations. There are, 2526 however, still various countries that offer some degree of anonymity 2527 for the caller towards PSAP call takers. 2529 The functionality defined in this document, however, far exceeds the 2530 amount of information sharing found in the Plain old telephone system 2531 (POTS). For this reason there are additional privacy threats to 2532 consider, which are described in more detail in [RFC6973]. 2534 Stored Data Compromise: First, there is an increased risk of stored 2535 data compromise since additional data is collected and stored in 2536 databases. Without adequate measures to secure stored data from 2537 unauthorized or inappropriate access at access network operators, 2538 service providers, end devices, as well as PSAPs individuals are 2539 exposed to potential financial, reputational, or physical harm. 2541 Misattribution: If the personal data collected and conveyed is 2542 incorrect or inaccurate then this may lead to misattribution. 2543 Misattribution occurs when data or communications related to one 2544 individual are attributed to another. 2546 Identification: By the nature of the additional data and its 2547 capability to provide much richer information about the caller, 2548 the call, and the location the calling party is identified in a 2549 much better way. Some users may feel uncomfortable with this 2550 degree of information sharing even in emergency services 2551 situations. 2553 Secondary Use: Furthermore, there is the risk of secondary use. 2554 Secondary use is the use of collected information about an 2555 individual without the individual's consent for a purpose 2556 different from that for which the information was collected. The 2557 stated purpose of the additional data is for emergency services 2558 purposes but theoretically the same information could be used for 2559 any other call as well. Additionally, parties involved in the 2560 emergency call may retain the obtained information and may re-use 2561 it for other, non-emergency services purposes. 2563 Disclosure: When the data defined in this document is not properly 2564 security (while in transit with traditional communication security 2565 techniques, and while at rest using access control mechanisms) 2566 there is the risk of disclosure, which is the revelation of 2567 information about an individual that affects the way others judge 2568 the individual. 2570 To mitigate these privacy risks the following countermeasures can be 2571 taken. 2573 In regions where callers can elect to suppress certain personally 2574 identifying information, the network or PSAP functionality can 2575 inspect privacy flags within the SIP headers to determine what 2576 information may be passed, stored, or displayed to comply with local 2577 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2578 The presence of this privacy type in a Privacy header field indicates 2579 that the user would like the network asserted identity to be kept 2580 private with respect to SIP entities outside the trust domain with 2581 which the user authenticated, including the PSAP. 2583 This document defines various data structures that constitutes 2584 personal data. Local regulations may govern what data must be 2585 provided in emergency calls, but in general, the emergency call 2586 system is often aided by the kinds of information described in this 2587 document. There is a tradeoff between the privacy considerations and 2588 the utility of the data. For adequate protection this specification 2589 requires all data exchanges to be secured via communication security 2590 techniques (namely TLS) against eavesdropping and inception. 2591 Furthermore, security safeguards are required to prevent unauthorized 2592 access to data at rest. Various security incidents over the last 10 2593 years have shown data breaches are not not uncommon and are often 2594 caused by lack of proper access control frameworks, software bugs 2595 (buffer overflows), or missing input parsing (SQL injection attacks). 2596 The risks of data breaches is increased with the obligation for 2597 emergency services to retain emergency call related data for extended 2598 periods, e.g., several years are the norm. 2600 Finally, it is also worth to highlight the nature of the SIP 2601 communication architecture, which introduces additional complications 2602 for privacy. Some forms of data can be sent by value in the SIP 2603 signaling or by value (URL in SIP signaling). When data is sent by 2604 value, all intermediaries have access to the data. As such, these 2605 intermediaries may also introduce additional privacy risk. 2606 Therefore, in situations where the conveyed information raises 2607 privacy concerns and intermediaries are involved transmitting a 2608 reference is more appropriate (assuming proper access control 2609 policies are available for distinguishing the different entities 2610 dereferencing the reference). Without access control policies any 2611 party in possession of the reference is able to resolve the reference 2612 and to obtain the data, including intermediaries. 2614 9. IANA Considerations 2616 9.1. Registry creation 2618 This document creates a new registry called 'Emergency Call 2619 Additional Data'. The following sub-registries are created for this 2620 registry. 2622 9.1.1. Provider ID Series Registry 2624 This document creates a new sub-registry called 'Additional Call Data 2625 Provider ID Series'. As defined in [RFC5226], this registry operates 2626 under "Expert Review" rules. The expert should determine that the 2627 entity requesting a new value is a legitimate issuer of service 2628 provider IDs suitable for use in Additional Call Data. 2630 The content of this registry includes: 2632 Name: The identifier which will be used in the ProviderIDSeries 2633 element 2635 Source: The full name of the organization issuing the identifiers 2637 URL: A URL to the organization for further information 2639 The initial set of values is listed in Figure 21. 2641 +-----------+--------------------------+----------------------+ 2642 | Name | Source | URL | 2643 +-----------+--------------------------+----------------------+ 2644 | NENA | National Emergency | http://www.nena.org | 2645 | | Number Association | | 2646 | EENA | European Emergency | http://www.eena.org | 2647 | | Number Association | | 2648 +-----------+--------------------------+----------------------+ 2650 Figure 21: Provider ID Series Registry. 2652 9.1.2. Service Environment Registry 2654 This document creates a new sub-registry called 'Additional Call 2655 Service Environment'. As defined in [RFC5226], this registry 2656 operates under "Expert Review" rules. The expert should determine 2657 that the entity requesting a new value is relevant for this service 2658 element. 2660 The content of this registry includes: 2662 Token: The value to be used in element. 2664 Description: A short description of the token. 2666 The initial set of values is listed in Figure 22. 2668 +-----------+--------------------------+ 2669 | Token | Description | 2670 +-----------+--------------------------+ 2671 | Business | [[This RFC]] | 2672 | Residence | [[This RFC]] | 2673 +-----------+--------------------------+ 2675 Figure 22: Service Environment Registry. 2677 9.1.3. Service Provider Type Registry 2679 This document creates a new sub-registry called 'Service Provider 2680 Type'. As defined in [RFC5226], this registry operates under "Expert 2681 Review". The expert should determine that the proposed new value is 2682 distinct from existing values and appropriate for use in the 2683 TypeOfServicerProvider element 2685 The content of this registry includes: 2687 Name: The value to be used in TypeOfServiceProvider. 2689 Description: A short description of the type of service provider 2691 The initial set of values is defined in Figure 1. 2693 9.1.4. Service Delivered Registry 2694 This document creates a new sub-registry called 'Service Delivered'. 2695 As defined in [RFC5226], this registry operates under "Expert Review" 2696 rules. The expert should consider whether the proposed service is 2697 unique from existing services and the definition of the service will 2698 be clear to implementors and PSAPS/responders. 2700 The content of this registry includes: 2702 Name: Enumeration token of the service. 2704 Description: Short description identifying the service. 2706 The initial set of values are defined in Figure 3. 2708 9.1.5. Device Classification Registry 2710 This document creates a new sub-registry called 'Device 2711 Classification'. As defined in [RFC5226], this registry operates 2712 under "Expert Review" rules. The expert should consider whether the 2713 proposed class is unique from existing classes and the definition of 2714 the class will be clear to implementors and PSAPS/responders. 2716 The content of this registry includes: 2718 Name: Enumeration token of the device classification. 2720 Description: Short description identifying the device type. 2722 The initial set of values are defined in Figure 5. 2724 9.1.6. Device ID Type Type Registry 2726 This document creates a new sub-registry called 'Additional Call Data 2727 Device ID Type'. As defined in [RFC5226], this registry operates 2728 under "Expert Review" rules. The expert should ascertain that the 2729 proposed type is well understood, and provides the information useful 2730 to PSAPs and responders to uniquely identify a device. 2732 The content of this registry includes: 2734 Name: Enumeration token of the device id type. 2736 Description: Short description identifying type of device id. 2738 The initial set of values are defined in Figure 6. 2740 9.1.7. Device/Service Data Type Registry 2741 This document creates a new sub-registry called 'Device/Service Data 2742 Type Registry'. As defined in [RFC5226], this registry operates 2743 under "Expert Review" and "Specification Required" rules. The expert 2744 should ascertain that the proposed type is well understood, and 2745 provides information useful to PSAPs and responders. The 2746 specification must contain a complete description of the data, and a 2747 precise format specification suitable to allow interoperable 2748 implementations. 2750 The content of this registry includes: 2752 Name: Enumeration token of the data type. 2754 Description: Short description identifying the the data. 2756 Specification: Citation for the specification of the data. 2758 The initial set of values are listed in Figure 23. 2760 +---------+----------------------------------------+----------------+ 2761 | Token | Description | Specification | 2762 +---------+----------------------------------------+----------------+ 2763 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2764 +---------+----------------------------------------+----------------+ 2766 Figure 23: Device/Service Data Type Registry. 2768 9.1.8. Additional Data Blocks Registry 2770 This document creates a new sub-registry called 'Additional Data 2771 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2772 As defined in [RFC5226], this registry operates under "Expert Review" 2773 and "Specification Required" rules. The expert is responsible for 2774 verifying that the document contains a complete and clear 2775 specification and the proposed functionality does not obviously 2776 duplicate existing functionality. 2778 The content of this registry includes: 2780 Name: Element Name of enclosing block. 2782 Reference: The document that describes the block 2784 The initial set of values are listed in Figure 24. 2786 +--------------+------------+ 2787 | Token | Reference | 2788 +--------------+------------+ 2789 | ProviderInfo | [This RFC] | 2790 | ServiceInfo | [This RFC] | 2791 | DeviceInfo | [This RFC] | 2792 | Subscriber | [This RFC] | 2793 | Comment | [This RFC] | 2794 +--------------+------------+ 2796 Figure 24: Additional Data Blocks Registry. 2798 9.2. 'EmergencyCallData' Purpose Parameter Value 2800 This document defines the 'EmergencyCallData' value for the "purpose" 2801 parameter of the Call-Info header field. The Call-Info header and 2802 the corresponding registry for the 'purpose' parameter was 2803 established with RFC 3261 [RFC3261]. 2805 Header Parameter New 2806 Field Name Value Reference 2807 ---------- --------- ----------------- --------- 2808 Call-Info purpose EmergencyCallData [This RFC] 2810 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2812 This section registers the namespace specified in Section 9.5.1 in 2813 the provided-by registry established by RFC 4119, for usage within 2814 the element of a PIDF-LO. 2816 The schema for the provided-by schema used by this document is 2817 specified in Section 6.6. 2819 9.4. MIME Registrations 2821 9.4.1. MIME Content-type Registration for 'application/ 2822 EmergencyCallData.ProviderInfo+xml' 2824 This specification requests the registration of a new MIME type 2825 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2826 RFC 3023 [RFC3023]. 2828 MIME media type name: application 2830 MIME subtype name: EmergencyCallData.ProviderInfo+xml 2832 Mandatory parameters: none 2833 Optional parameters: charset Indicates the character encoding of 2834 enclosed XML. 2836 Encoding considerations: Uses XML, which can employ 8-bit 2837 characters, depending on the character encoding used. See 2838 Section 3.2 of RFC 3023 [RFC3023]. 2840 Security considerations: This content type is designed to carry 2841 the data provider information, which is a sub-category of 2842 additional data about an emergency call. Since this data contains 2843 personal information appropriate precautions have to be taken to 2844 limit unauthorized access, inappropriate disclosure to third 2845 parties, and eavesdropping of this information. Please refer to 2846 Section 7 and Section 8 for more information. 2848 Interoperability considerations: None 2850 Published specification: [TBD: This specification] 2852 Applications which use this media type: Emergency Services 2854 Additional information: Magic Number: None File Extension: .xml 2855 Macintosh file type code: 'TEXT' 2857 Person and email address for further information: Hannes 2858 Tschofenig, Hannes.Tschofenig@gmx.net 2860 Intended usage: LIMITED USE 2862 Author: This specification is a work item of the IETF ECRIT 2863 working group, with mailing list address . 2865 Change controller: The IESG 2867 9.4.2. MIME Content-type Registration for 'application/ 2868 EmergencyCallData.ServiceInfo+xml' 2870 This specification requests the registration of a new MIME type 2871 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2872 RFC 3023 [RFC3023]. 2874 MIME media type name: application 2876 MIME subtype name: EmergencyCallData.ServiceInfo+xml 2878 Mandatory parameters: none 2879 Optional parameters: charset Indicates the character encoding of 2880 enclosed XML. 2882 Encoding considerations: Uses XML, which can employ 8-bit 2883 characters, depending on the character encoding used. See 2884 Section 3.2 of RFC 3023 [RFC3023]. 2886 Security considerations: This content type is designed to carry 2887 the service information, which is a sub-category of additional 2888 data about an emergency call. Since this data contains personal 2889 information appropriate precautions have to be taken to limit 2890 unauthorized access, inappropriate disclosure to third parties, 2891 and eavesdropping of this information. Please refer to Section 7 2892 and Section 8 for more information. 2894 Interoperability considerations: None 2896 Published specification: [TBD: This specification] 2898 Applications which use this media type: Emergency Services 2900 Additional information: Magic Number: None File Extension: .xml 2901 Macintosh file type code: 'TEXT' 2903 Person and email address for further information: Hannes 2904 Tschofenig, Hannes.Tschofenig@gmx.net 2906 Intended usage: LIMITED USE 2908 Author: This specification is a work item of the IETF ECRIT 2909 working group, with mailing list address . 2911 Change controller: The IESG 2913 9.4.3. MIME Content-type Registration for 'application/ 2914 EmergencyCallData.DeviceInfo+xml' 2916 This specification requests the registration of a new MIME type 2917 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2918 RFC 3023 [RFC3023]. 2920 MIME media type name: application 2922 MIME subtype name: EmergencyCallData.DeviceInfo+xml 2924 Mandatory parameters: none 2925 Optional parameters: charset Indicates the character encoding of 2926 enclosed XML. 2928 Encoding considerations: Uses XML, which can employ 8-bit 2929 characters, depending on the character encoding used. See 2930 Section 3.2 of RFC 3023 [RFC3023]. 2932 Security considerations: This content type is designed to carry 2933 the device information information, which is a sub-category of 2934 additional data about an emergency call. Since this data contains 2935 personal information appropriate precautions have to be taken to 2936 limit unauthorized access, inappropriate disclosure to third 2937 parties, and eavesdropping of this information. Please refer to 2938 Section 7 and Section 8 for more information. 2940 Interoperability considerations: None 2942 Published specification: [TBD: This specification] 2944 Applications which use this media type: Emergency Services 2946 Additional information: Magic Number: None File Extension: .xml 2947 Macintosh file type code: 'TEXT' 2949 Person and email address for further information: Hannes 2950 Tschofenig, Hannes.Tschofenig@gmx.net 2952 Intended usage: LIMITED USE 2954 Author: This specification is a work item of the IETF ECRIT 2955 working group, with mailing list address . 2957 Change controller: The IESG 2959 9.4.4. MIME Content-type Registration for 'application/ 2960 EmergencyCallData.SubscriberInfo+xml' 2962 This specification requests the registration of a new MIME type 2963 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2964 RFC 3023 [RFC3023]. 2966 MIME media type name: application 2968 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 2970 Mandatory parameters: none 2971 Optional parameters: charset Indicates the character encoding of 2972 enclosed XML. 2974 Encoding considerations: Uses XML, which can employ 8-bit 2975 characters, depending on the character encoding used. See 2976 Section 3.2 of RFC 3023 [RFC3023]. 2978 Security considerations: This content type is designed to carry 2979 owner/subscriber information, which is a sub-category of 2980 additional data about an emergency call. Since this data contains 2981 personal information appropriate precautions have to be taken to 2982 limit unauthorized access, inappropriate disclosure to third 2983 parties, and eavesdropping of this information. Please refer to 2984 Section 7 and Section 8 for more information. 2986 Interoperability considerations: None 2988 Published specification: [TBD: This specification] 2990 Applications which use this media type: Emergency Services 2992 Additional information: Magic Number: None File Extension: .xml 2993 Macintosh file type code: 'TEXT' 2995 Person and email address for further information: Hannes 2996 Tschofenig, Hannes.Tschofenig@gmx.net 2998 Intended usage: LIMITED USE 3000 Author: This specification is a work item of the IETF ECRIT 3001 working group, with mailing list address . 3003 Change controller: The IESG 3005 9.4.5. MIME Content-type Registration for 'application/ 3006 EmergencyCallData.Comment+xml' 3008 This specification requests the registration of a new MIME type 3009 according to the procedures of RFC 4288 [RFC4288] and guidelines in 3010 RFC 3023 [RFC3023]. 3012 MIME media type name: application 3014 MIME subtype name: EmergencyCallData.Comment+xml 3016 Mandatory parameters: none 3017 Optional parameters: charset Indicates the character encoding of 3018 enclosed XML. 3020 Encoding considerations: Uses XML, which can employ 8-bit 3021 characters, depending on the character encoding used. See 3022 Section 3.2 of RFC 3023 [RFC3023]. 3024 Security considerations: This content type is designed to carry a 3025 comment, which is a sub-category of additional data about an 3026 emergency call. This data may contain personal information. 3027 Appropriate precautions may have to be taken to limit unauthorized 3028 access, inappropriate disclosure to third parties, and 3029 eavesdropping of this information. Please refer to Section 7 and 3030 Section 8 for more information. 3032 Interoperability considerations: None 3034 Published specification: [TBD: This specification] 3036 Applications which use this media type: Emergency Services 3038 Additional information: Magic Number: None File Extension: .xml 3039 Macintosh file type code: 'TEXT' 3041 Person and email address for further information: Hannes 3042 Tschofenig, Hannes.Tschofenig@gmx.net 3044 Intended usage: LIMITED USE 3046 Author: This specification is a work item of the IETF ECRIT 3047 working group, with mailing list address . 3049 Change controller: The IESG 3051 9.5. URN Sub-Namespace Registration 3053 9.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3055 This section registers a new XML namespace, as per the guidelines in 3056 RFC 3688 [RFC3688]. 3058 URI: urn:ietf:params:xml:ns:EmergencyCallData 3060 Registrant Contact: IETF, ECRIT working group, , as 3061 delegated by the IESG . 3063 XML: 3065 BEGIN 3066 3067 3069 3070 3071 3073 Namespace for Additional Emergency Call Data 3074 3075 3076

Namespace for Additional Data related to an Emergency Call

3077

See [TBD: This document].

3078 3079 3080 END 3082 9.5.2. Registration for 3083 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3085 This section registers a new XML namespace, as per the guidelines in 3086 RFC 3688 [RFC3688]. 3088 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3090 Registrant Contact: IETF, ECRIT working group, , as 3091 delegated by the IESG . 3093 XML: 3095 BEGIN 3096 3097 3099 3100 3101 3103 Namespace for Additional Emergency Call Data: 3104 Data Provider Information 3105 3106 3107

Namespace for Additional Data related to an Emergency Call

3108

Data Provider Information

3109

See [TBD: This document].

3110 3111 3112 END 3114 9.5.3. Registration for 3115 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3117 This section registers a new XML namespace, as per the guidelines in 3118 RFC 3688 [RFC3688]. 3120 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3122 Registrant Contact: IETF, ECRIT working group, , as 3123 delegated by the IESG . 3125 XML: 3127 BEGIN 3128 3129 3131 3132 3133 3135 Namespace for Additional Emergency Call Data: 3136 Service Information 3137 3138 3139

Namespace for Additional Data related to an Emergency Call

3140

Service Information

3141

See [TBD: This document].

3142 3143 3144 END 3146 9.5.4. Registration for 3147 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3149 This section registers a new XML namespace, as per the guidelines in 3150 RFC 3688 [RFC3688]. 3152 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3154 Registrant Contact: IETF, ECRIT working group, , as 3155 delegated by the IESG . 3157 XML: 3159 BEGIN 3160 3161 3163 3164 3165 3167 Namespace for Additional Emergency Call Data: 3168 Device Information 3169 3170 3171

Namespace for Additional Data related to an Emergency Call

3172

Device Information

3173

See [TBD: This document].

3174 3175 3176 END 3178 9.5.5. Registration for 3179 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3181 This section registers a new XML namespace, as per the guidelines in 3182 RFC 3688 [RFC3688]. 3184 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3186 Registrant Contact: IETF, ECRIT working group, , as 3187 delegated by the IESG . 3189 XML: 3191 BEGIN 3192 3193 3195 3196 3197 3199 Namespace for Additional Emergency Call Data: 3200 Owner/Subscriber Information 3201 3202 3203

Namespace for Additional Data related to an Emergency Call

3204

Owner/Subscriber Information

3205

See [TBD: This document].

3206 3207 3208 END 3210 9.5.6. Registration for 3211 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3213 This section registers a new XML namespace, as per the guidelines in 3214 RFC 3688 [RFC3688]. 3216 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3218 Registrant Contact: IETF, ECRIT working group, , as 3219 delegated by the IESG . 3221 XML: 3223 BEGIN 3224 3225 3227 3228 3229 3231 Namespace for Additional Emergency Call Data:Comment 3232 3233 3234

Namespace for Additional Data related to an Emergency Call

3235

Comment

3236

See [TBD: This document].

3237 3238 3239 END 3241 9.6. Schema Registrations 3243 This specification registers five schemas, as per the guidelines in 3244 RFC 3688 [RFC3688]. 3246 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3247 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3248 delegated by the IESG (iesg@ietf.org). 3250 XML: The XML schema can be found in Figure 15. 3252 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3254 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3255 delegated by the IESG (iesg@ietf.org). 3257 XML: The XML schema can be found in Figure 16. 3259 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3261 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3262 delegated by the IESG (iesg@ietf.org). 3264 XML: The XML schema can be found in Figure 17. 3266 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3268 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3269 delegated by the IESG (iesg@ietf.org). 3271 XML: The XML schema can be found in Section 6.4. 3273 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3275 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3276 delegated by the IESG (iesg@ietf.org). 3278 XML: The XML schema can be found in Section 6.5. 3280 9.7. VCard Parameter Value Registration 3282 This document registers a new value in the vCARD Parameter Values 3283 registry as defined by [RFC6350] with the following template: 3285 Value: main 3287 Purpose: The main telephone number, typically of an enterprise, as 3288 opposed to a direct dial number of an individual employee 3290 Conformance: This value can be used with the "TYPE" parameter 3291 applied on the "TEL" property. 3293 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3294 00 3296 10. Acknowledgments 3298 This work was originally started in NENA and has benefitted from a 3299 large number of participants in NENA standardization efforts, 3300 originally in the Long Term Definition Working Group, the Data 3301 Technical Committee and most recently the Additional Data working 3302 group. The authors are grateful for the initial work and extended 3303 comments provided by many NENA participants, including Delaine 3304 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3305 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3306 and Robert (Bob) Sherry. 3308 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3309 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 3310 comments. 3312 11. References 3314 11.1. Normative References 3316 [RFC0822] Crocker, D., "Standard for the format of ARPA Internet 3317 text messages", STD 11, RFC 822, August 1982. 3319 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 3320 Extensions (MIME) Part One: Format of Internet Message 3321 Bodies", RFC 2045, November 1996. 3323 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3324 Requirement Levels", BCP 14, RFC 2119, March 1997. 3326 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3327 Locators", RFC 2392, August 1998. 3329 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 3330 Types", RFC 3023, January 2001. 3332 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3333 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3334 and QSIG Objects", RFC 3204, December 2001. 3336 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3337 A., Peterson, J., Sparks, R., Handley, M., and E. 3338 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3339 June 2002. 3341 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3342 Extensions to the Session Initiation Protocol (SIP) for 3343 Asserted Identity within Trusted Networks", RFC 3325, 3344 November 2002. 3346 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3347 Extensions (MIME) Parameter", RFC 3459, January 2003. 3349 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3350 January 2004. 3352 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3353 Format", RFC 4119, December 2005. 3355 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 3356 Registration Procedures", RFC 4288, December 2005. 3358 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3359 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3360 May 2008. 3362 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3363 Initiation Protocol (SIP)", RFC 5621, September 2009. 3365 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3366 August 2011. 3368 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3369 6351, August 2011. 3371 11.2. Informational References 3373 [I-D.gellens-negotiating-human-language] 3374 Randy, R., "Negotiating Human Language Using SDP", draft- 3375 gellens-negotiating-human-language-02 (work in progress), 3376 February 2013. 3378 [I-D.ietf-ecrit-psap-callback] 3379 Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3380 Patel, "Public Safety Answering Point (PSAP) Callback", 3381 draft-ietf-ecrit-psap-callback-13 (work in progress), 3382 October 2013. 3384 [I-D.ietf-geopriv-relative-location] 3385 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3386 Thomson, "Relative Location Representation", draft-ietf- 3387 geopriv-relative-location-08 (work in progress), September 3388 2013. 3390 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3391 "Indicating User Agent Capabilities in the Session 3392 Initiation Protocol (SIP)", RFC 3840, August 2004. 3394 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3395 Emergency Context Resolution with Internet Technologies", 3396 RFC 5012, January 2008. 3398 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3399 Format for Presence Information Data Format Location 3400 Object (PIDF-LO)", RFC 5139, February 2008. 3402 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 3403 Tschofenig, "LoST: A Location-to-Service Translation 3404 Protocol", RFC 5222, August 2008. 3406 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3407 Presence Information Data Format Location Object (PIDF-LO) 3408 Usage Clarification, Considerations, and Recommendations", 3409 RFC 5491, March 2009. 3411 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3412 Thomson, "Dynamic Extensions to the Presence Information 3413 Data Format Location Object (PIDF-LO)", RFC 5962, 3414 September 2010. 3416 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3417 5985, September 2010. 3419 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3420 "Framework for Emergency Calling Using Internet 3421 Multimedia", RFC 6443, December 2011. 3423 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3424 R. George, "Specifying Civic Address Extensions in the 3425 Presence Information Data Format Location Object (PIDF- 3426 LO)", RFC 6848, January 2013. 3428 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3429 Communications Services in Support of Emergency Calling", 3430 BCP 181, RFC 6881, March 2013. 3432 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3433 Morris, J., Hansen, M., and R. Smith, "Privacy 3434 Considerations for Internet Protocols", RFC 6973, July 3435 2013. 3437 Appendix A. XML Schema for vCard/xCard 3439 This section contains the vCard/xCard XML schema version of the Relax 3440 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3441 XML schemas defined in this document. The schema in RFC 6351 3442 [RFC6351] is the normative source and this section is informative 3443 only. 3445 3446 3450 3456 3457 3458 vCard Format Specification 3459 3460 3461 3462 3463 3464 3465 3466 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3481 3482 3483 3485 3486 3487 3488 3489 3491 3492 3493 3495 3496 3497 3498 3499 3501 3502 3503 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3548 3549 3550 3551 3555 3556 3557 Section 5: Parameters 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 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 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4088 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 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 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 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 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 4480 4481 4482 4483 4484 4485 4486 4488 4489 4490 4491 4492 4493 4494 4496 4497 4498 4500 4502 4503 4504 4506 4507 4508 4509 4511 Authors' Addresses 4513 Brian Rosen 4514 NeuStar 4515 470 Conrad Dr. 4516 Mars, PA 16046 4517 US 4519 Phone: +1 724 382 1051 4520 Email: br@brianrosen.net 4522 Hannes Tschofenig 4523 (no affiliation) 4525 Email: Hannes.Tschofenig@gmx.net 4526 URI: http://www.tschofenig.priv.at 4528 Roger Marshall 4529 TeleCommunication Systems, Inc. 4530 2401 Elliott Avenue 4531 Seattle, WA 98121 4532 US 4534 Phone: +1 206 792 2424 4535 Email: rmarshall@telecomsys.com 4536 URI: http://www.telecomsys.com 4537 Randall Gellens 4538 Qualcomm Technologies, Inc. 4539 5775 Morehouse Drive 4540 San Diego, CA 92121 4541 US 4543 Email: rg+ietf@qti.qualcomm.com 4545 James Winterbottom 4546 (no affiliation) 4547 AU 4549 Email: a.james.winterbottom@gmail.com