idnits 2.17.00 (12 Aug 2021) /tmp/idnits39937/draft-ietf-ecrit-additional-data-21.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 2307 has weird spacing: '...element name=...' == Line 2807 has weird spacing: '...ll-Info pur...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (March 08, 2014) is 2995 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 2807, but not defined == Unused Reference: 'RFC5985' is defined on line 3415, 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) == Outdated reference: draft-ietf-ecrit-psap-callback has been published as RFC 7090 == Outdated reference: draft-ietf-geopriv-relative-location has been published as RFC 7035 Summary: 6 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track H. Tschofenig 5 Expires: September 9, 2014 (no affiliation) 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 11 (no affiliation) 12 March 08, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-21.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 September 9, 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 |automobile | Automobile telematics | 880 |truck | Truck telematics | 881 |farm | Farm equipment telematics | 882 |marine | Marine telematics | 883 |personal | Personal telematics device | 884 |feature-phone | Feature (not smart-) cellular phone | 885 |smart-phone | Smart-phone cellular phone | 886 |game | Gaming console | 887 |text-only | Other text device | 888 |NA | Not Available | 889 +---------------+----------------------------------------+ 891 Figure 5: Device Classification Registry. 893 Reason for Need: The device classification implies the capability of 894 the calling device and assists in identifying the meaning of the 895 emergency call location information that is being presented. For 896 example, does the device require human intervention to initiate a 897 call or is this call the result of programmed instructions? Does 898 the calling device have the ability to update location or 899 condition changes? Is this device interactive or a one-way 900 reporting device? 902 How Used by Call Taker: May assist with location of caller. For 903 example, a cordless handset may be outside or next door. May 904 provide the calltaker some context about the caller, the 905 capabilities of the device used for the call or the environment 906 the device is being used in. 908 3.3.2. Device Manufacturer 910 Data Element: Device Manufacturer 912 Use: Optional 914 XML Element: 916 Description: The plain language name of the manufacturer of the 917 device. 919 Reason for Need: Used by PSAP management for post-mortem 920 investigation/resolution. 922 How Used by Call Taker: Probably not used by the calltaker, but by 923 PSAP management. 925 3.3.3. Device Model Number 927 Data Element: Device Model Number 929 Use: Optional 931 XML Element: 933 Description: Model number of the device. 935 Reason for Need: Used by PSAP management for after action 936 investigation/resolution. 938 How Used by Call Taker: Probably not used by the calltaker, but by 939 PSAP management. 941 3.3.4. Unique Device Identifier 943 Data Element: Unique Device Identifier 945 Use: Optional 947 XML Element: 949 XML Attribute: 950 Description: A string that identifies the specific device (or the 951 device's current SIM) making the call or creating an event. Note 952 that more than one may be present, to supply more 953 than one of the identifying values. 955 The attribute identifies the type of device 956 identifier. A registry with an initial set of values can be seen 957 in Figure 6. 959 +--------+------------------------------------------+ 960 | Token | Description | 961 +--------+------------------------------------------+ 962 | MEID | Mobile Equipment Identifier (CDMA) | 963 | ESN | Electronic Serial Number (GSM) | 964 | MAC | Media Access Control Address (IEEE) | 965 | WiMAX | Device Certificate Unique ID | 966 | IMEI | International Mobile Equipment ID (GSM) | 967 | IMSI | International Mobile Subscriber ID (GSM) | 968 | UDI | Unique Device Identifier | 969 | RFID | Radio Frequency Identification | 970 | SN | Manufacturer Serial Number | 971 +--------+------------------------------------------+ 973 Figure 6: Registry with Device Identifier Types. 975 Reason for Need: Uniquely identifies the device (or, in the case of 976 IMSI, a SIM), independent of any signaling identifiers present in 977 the call signaling stream. 979 How Used by Call Taker: Probably not used by the call taker; may be 980 used by PSAP management during an investigation. 982 Example: 12345 984 3.3.5. Device/Service Specific Additional Data Structure 986 Data Element: Device/service specific additional data structure 988 Use: Optional 990 XML Element: 991 Description: A URI representing additional data whose schema is 992 specific to the device or service which created it. (For example, 993 a medical device or medical device monitoring service may have a 994 defined set of medical data.) The URI, when dereferenced, MUST 995 yield a data structure defined by the Device/service specific 996 additional data type value. Different data may be created by each 997 classification; e.g., a medical device created data set. 999 Reason for Need: Provides device/service specific data that may be 1000 used by the call taker and/or responders. 1002 How Used by Call Taker: Provide information to guide call takers to 1003 select appropriate responders, give appropriate pre-arrival 1004 instructions to callers, and advise responders of what to be 1005 prepared for. May be used by responders to guide assistance 1006 provided. 1008 3.3.6. Device/Service Specific Additional Data Structure Type 1010 Data Element: Type of device/service specific additional data 1011 structure 1013 Use: Conditional. MUST be provided when device/service specific 1014 additional URI is provided 1016 XML Element: 1018 Description: Value from a registry defined by this document to 1019 describe the type of data that can be retrieved from the device/ 1020 service specific additional data structure. Initial values are: 1022 * IEEE 1512 1024 IEEE 1512 is the USDoT model for traffic incidents. 1026 Reason for Need: This data element allows identification of 1027 externally defined schemas, which may have additional data that 1028 may assist in emergency response. 1030 How Used by Call Taker: This data element allows the end user 1031 (calltaker or first responder) to know what type of additional 1032 data may be available to aid in providing the needed emergency 1033 services. 1035 Note: Information which is specific to a location or a caller 1036 (person) should not be placed in this section. 1038 3.3.7. Issues with getting new types of data into use 1040 This document describes two mechanisms which allow extension of the 1041 kind of data provided with an emergency call: define a new block or 1042 define a new service specific additional data URL for the DeviceInfo 1043 block. While defining new data types and getting a new device or 1044 application to send the new data may be easy, getting PSAPs and 1045 responders to actually retrieve the data and use it will be 1046 difficult. New mechanism providers should understand that acquiring 1047 and using new forms of data usually require software upgrades at the 1048 PSAP and/or responders, as well as training of call takers and 1049 responders in how to interpret and use the information. Legal and 1050 operational review may also be needed. Overwhelming a call taker or 1051 responder with too much information is highly discouraged. Thus, the 1052 barrier to supporting new data is quite high. 1054 The mechanisms this document describes are meant to encourage 1055 development of widely supported, common data formats for classes of 1056 devices. If all manufacturers of a class of device use the same 1057 format, and the data can be shown to improve outcomes, then PSAPs and 1058 responders may be encouraged to upgrade their systems and train their 1059 staff to use the data. Variations, however well intentioned, are 1060 unlikely to be supported. 1062 Implementers should consider that data from sensor-based devices in 1063 some cases may not be useful to call takers or PSAPs (and privacy or 1064 other considerations may preclude the PSAP from touching the data), 1065 but may be of use to responders. Some standards being developed by 1066 other organizations to carry data from the PSAP to responders are 1067 designed to carry all additional data supplied in the call that 1068 conform to this document, even if the PSAP does not fetch or 1069 interpret the data. This allows responders to get the data even if 1070 the PSAP does not. 1072 3.3.8. Choosing between defining a new type of block or new type of 1073 device/service specific additional data 1075 For devices that have device or service specific data, there are two 1076 choices to carry it. A new block can be defined, or the device/ 1077 service specific additional data URL the DeviceInfo block can be used 1078 and a new type for it defined . The data passed would likely be the 1079 same in both cases. Considerations for choosing which mechanism to 1080 register under include: 1082 Applicability: Information which will be carried by many kinds of 1083 devices or services are more appropriately defined as separate 1084 blocks. 1086 Privacy: Information which may contain private data may be better 1087 sent in the DeviceInfo block, rather than a new block so that 1088 implementations are not tempted to send the data by value, and 1089 thus having more exposure to the data than forcing the data to be 1090 retrieved via the URL in DeviceInfo. 1092 Size: Information which may be very may be better sent in the 1093 DeviceInfo block, rather than a new block so that implementations 1094 are not tempted to send the data by value. Conversely, data which 1095 is small may best be sent in a separate block so that it can be 1096 sent by value 1098 Availability of a server: Providing the data via the device block 1099 requires a server be made available to retrieve the data. 1100 Providing the data via new block allows it to be sent by value 1101 (CID). 1103 3.3.9. EmergencyCallData.DeviceInfo Example 1105 1106 1109 string0987654321@example.org 1110 1111 12345 1112 Fixed phone 1113 Nokia 1114 Lumia 800 1115 35788104 1116 1117 1119 Figure 7: EmergencyCallData.DeviceInfo Example. 1121 3.4. Owner/Subscriber Information 1123 This block describes the owner of the device (if provided by the 1124 device) or the subscriber information, if provided by a service 1125 provider. The contact location is not necessarily the location of 1126 the caller or incident, but is rather the nominal contact address. 1127 The mime subtype is "application/EmergencyCallData.Subscriber+xml". 1129 In some jurisdictions some or all parts of the subscriber-specific 1130 information are subject to privacy constraints. These constraints 1131 vary but dictate what information and be displayed and logged. A 1132 general privacy indicator expressing a desire for privacy is 1133 provided. The interpretation of how this is applied is left to the 1134 receiving jurisdiction as the custodians of the local regulatory 1135 requirements. 1137 3.4.1. Subscriber Data Privacy Indicator 1139 Attribute: privacyRequested, boolean. 1141 Use: Conditional. This attribute MUST be provided if the owner/ 1142 subscriber information block is not empty. 1144 Description: The subscriber data privacy indicator specifically 1145 expresses the subscriber's desire for privacy. In some 1146 jurisdictions subscriber services can have a specific "Type of 1147 Service" which prohibits information, such as the name of the 1148 subscriber, from being displayed. This attribute should be used 1149 to explicitly indicate whether the subscriber service includes 1150 such constraints. 1152 Reason for Need: Some jurisdictions require subscriber privacy to be 1153 observed. 1155 How Used by Call Taker: Where privacy is indicated the call taker 1156 may not have access to some aspects of the subscriber information. 1158 3.4.2. xCard for Subscriber's Data 1160 Data Element: xCARD for Subscriber's Data 1162 Use: Conditional. Subscriber data is provided unless it is not 1163 available. Some services, for example prepaid phones, non- 1164 initialized phones, etc., do not have information about the 1165 subscriber. 1167 XML Element: 1169 Description: Information known by the service provider or device 1170 about the subscriber; e.g., Name, Address, Individual Telephone 1171 Number, Main Telephone Number and any other data. N, ORG (if 1172 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1173 than one TEL property is provided, a parameter from the vCard 1174 Property Value registry MUST be specified on each TEL. 1176 Reason for Need: When the caller is unable to provide information, 1177 this data may be used to obtain it 1179 How Used by Call Taker: Obtaining critical information about the 1180 caller and possibly the location when it is not able to be 1181 obtained otherwise. 1183 3.4.3. EmergencyCallData.SubscriberInfo Example 1185 1186 1190 string0987654321@example.org 1191 1192 1193 1194 1195 Simon Perreault 1196 1197 Perreault 1198 Simon 1199 1200 1201 ing. jr 1202 M.Sc. 1203 1204 --0203 1205 1206 20090808T1430-0500 1207 1208 M 1209 1210 1 1211 1212 fr 1213 1214 1215 2 1216 1217 en 1218 1219 1220 work 1221 1222 Viagenie 1223 1224 1225 1226 work 1227 1231 1232 1233 1234 2875 boul. Laurier, suite D2-630 1235 Quebec 1236 QC 1237 G1V 2M2 1238 Canada 1239 1240 1241 1242 1243 work 1244 voice 1245 1246 1247 tel:+1-418-656-9254;ext=102 1248 1249 1250 1251 1252 work 1253 text 1254 voice 1255 cell 1256 video 1257 1258 1259 tel:+1-418-262-6501 1260 1261 1262 work 1263 1264 simon.perreault@viagenie.ca 1265 1266 1267 work 1268 1269 geo:46.766336,-71.28955 1270 1271 1272 work 1273 1274 1275 http://www.viagenie.ca/simon.perreault/simon.asc 1276 1277 1278 America/Montreal 1279 1280 home 1281 1282 http://nomis80.org 1283 1284 1285 1286 1287 1289 Figure 8: EmergencyCallData.SubscriberInfo Example. 1291 3.5. Comment 1293 This block provides a mechanism for the data provider to supply 1294 extra, human readable information to the PSAP. It is not intended 1295 for a general purpose extension mechanism nor does it aim to provide 1296 machine-reable content. The mime subtype is "application/ 1297 EmergencyCallData.Comment+xml" 1299 3.5.1. Comment 1301 Data Element: EmergencyCallData.Comment 1303 Use: Optional 1305 XML Element: 1307 Description: Human readable text providing additional information to 1308 the PSAP staff. 1310 Reason for Need: Explanatory information for values in the data 1311 structure 1313 How Used by Call Taker: To interpret the data provided 1315 3.5.2. EmergencyCallData.Comment Example 1317 1318 1322 string0987654321@example.org 1323 1324 This is an example text. 1325 1327 Figure 9: EmergencyCallData.Comment Example. 1329 4. Data Transport Mechanisms 1331 This section defines how to convey additional data to an emergency 1332 service provider. Two different means are specified: the first uses 1333 the call signaling; the second uses the element of a 1334 PIDF-LO [RFC4119]. 1336 1. First, the ability to embed a Uniform Resource Identifier (URI) 1337 in an existing SIP header field, the Call-Info header, is 1338 defined. The URI points to the additional data structure. The 1339 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1340 document adds a new compound token starting with the value 1341 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1342 the "purpose" parameter is set to a value starting with 1343 'EmergencyCallData', then the Call-Info header contains either an 1344 HTTPS URL pointing to an external resource or a CID (content 1345 indirection) URI that allows the data structure to be placed in 1346 the body of the SIP message. The "purpose" parameter also 1347 indicates the kind of data (by its MIME type) that is available 1348 at the URI. As the data is conveyed using a URI in the SIP 1349 signaling, the data itself may reside on an external resource, or 1350 may be contained within the body of the SIP message. When the 1351 URI refers to data at an external resource, the data is said to 1352 be passed by reference. When the URI refers to data contained 1353 within the body of the SIP message, the data is said to be passed 1354 by value. A PSAP or emergency responder is able to examine the 1355 type of data provided and selectively inspect the data it is 1356 interested in, while forwarding all of it (the values or 1357 references) to downstream entities. To be conveyed in a SIP 1358 body, additional data about a call is defined as a series of MIME 1359 objects. Each block defined in this document is an XML data 1360 structure identified by its MIME type. (Blocks defined by others 1361 may be encoded in XML or not, as identified by their MIME 1362 registration.) As usual, whenever more than one MIME part is 1363 included in the body of a message, MIME-multipart (i.e., 1364 'multipart/mixed') encloses them all. This document defines a 1365 set of XML schemas and MIME types used for each block defined 1366 here. When additional data is passed by value in the SIP 1367 signaling, each CID URL points to one block in the body. 1368 Multiple URIs are used within a Call-Info header field (or 1369 multiple Call-Info header fields) to point to multiple blocks. 1371 When additional data is provided by reference (in SIP signaling 1372 or Provided-By), each HTTPS URL references one block; the data is 1373 retrieved with an HTTPS GET operation, which returns one of the 1374 blocks as an object (the blocks defined here are returned as XML 1375 objects). 1377 2. Second, the ability to embed additional data structures in the 1378 element of a PIDF-LO [RFC4119] is defined. Besides 1379 a service provider in the call path, the access network provider 1380 may also have similar information that may be valuable to the 1381 PSAP. The access network provider may provide location in the 1382 form of a PIDF-LO from a location server via a location 1383 configuration protocol. The data structures described in this 1384 document are not specific to the location itself, but rather 1385 provides descriptive information having to do with the immediate 1386 circumstances about the provision of the location (who the access 1387 network is, how to contact that entity, what kind of service the 1388 access network provides, subscriber information, etc.). This 1389 data is similar in nearly every respect to the data known by 1390 service providers in the path of the call. When the access 1391 network provider and service provider are separate entities, the 1392 access network does not participate in the application layer 1393 signaling (and hence cannot add a Call-Info header field to the 1394 SIP message), but may provide location information to assist in 1395 locating the caller's device. The element of the 1396 PIDF-LO is a mechanism for the access network provider to supply 1397 the information about the entity or organization that supplied 1398 this location information. For this reason, this document 1399 describes a namespace per RFC 4119 for inclusion in the 1400 element of a PIDF-LO for adding information known 1401 to the access network provider. 1403 One or more blocks of data registered in the Emergency Call 1404 Additional Data registry, as defined in Section 9.1, may be included 1405 or referenced in the SIP signaling (using the Call-Info header field) 1406 or in the element of a PIDF-LO. Every block must be 1407 one of the types in the registry. Since the data of an emergency 1408 call may come from multiple sources, the data itself needs 1409 information describing the source. Consequently, each entity adding 1410 additional data MUST supply the "Data Provider" block. All other 1411 blocks are optional, but each entity SHOULD supply any blocks where 1412 it has at least some of the information in the block. 1414 4.1. Transmitting Blocks using the Call-Info Header 1416 A URI to a block MAY be inserted in a SIP request or response method 1417 (most often INVITE or MESSAGE) with a Call-Info header field 1418 containing a purpose value starting with 'EmergencyCallData' and the 1419 type of data available at the URI. The type of data is denoted by 1420 including the root of the MIME type (not including the 1421 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1422 separator. For example, when referencing a block with MIME type 1423 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1424 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1425 "Call-Info" header field for this would be: 1427 Call-Info: https://www.example.com/23sedde3; 1428 purpose="EmergencyCallData.ProviderInfo" 1430 A Call-info header with a purpose value starting with 1431 'EmergencyCallData' MUST only be sent on an emergency call, which can 1432 be ascertained by the presence of an emergency service urn in a Route 1433 header of a SIP message. 1435 If the data is provided by reference, an HTTPS URI MUST be included 1436 and consequently Transport Layer Security (TLS) protection is applied 1437 for protecting the retrieval of the information. 1439 The data may also be supplied by value in a SIP message. In this 1440 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1441 referencing the MIME body part. 1443 More than one Call-Info header with a purpose value starting with 1444 'EmergencyCallData' can be expected, but at least one MUST be 1445 provided. The device MUST provide one if it knows no service 1446 provider is in the path of the call. The device MAY insert one if it 1447 uses a service provider. Any service provider in the path of the 1448 call MUST insert its own. For example, a device, a telematics 1449 service provider in the call path, as well as the mobile carrier 1450 handling the call will each provide one. There may be circumstances 1451 where there is a service provider who is unaware that the call is an 1452 emergency call and cannot reasonably be expected to determine that it 1453 is an emergency call. In that case, that service provider is not 1454 expected to provide EmergencyCallData. 1456 4.2. Transmitting Blocks by Reference using the Provided-By Element 1458 The 'EmergencyCallDataReference' element is used to transmit an 1459 additional data block by reference within a 'Provided-By' element of 1460 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1461 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1462 type of data block referenced. The value of 'ref' is an HTTPS URL 1463 that resolves to a data structure with information about the call. 1464 The value of 'purpose' is the same as used in a 'Call-Info' header 1465 field (as specified in Section 4.1). 1467 For example, to reference a block with MIME type 'application/ 1468 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1469 to 'EmergencyCallData.ProviderInfo'. An example 1470 'EmergencyCallDataReference' element for this would be: 1472 1475 4.3. Transmitting Blocks by Value using the Provided-By Element 1477 It is RECOMMENDED that access networks supply the data specified in 1478 this document by reference, but they MAY provide the data by value. 1480 The 'EmergencyCallDataValue' element is used to transmit an 1481 additional data block by value within a 'Provided-By' element of a 1482 PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: 1483 'purpose' to indicate the type of data block contained. The value of 1484 'purpose' is the same as used in a 'Call-Info' header field (as 1485 specified in Section 4.1, and in Section 4.1). The same XML 1486 structure as would be contained in the corresponding MIME type body 1487 part is placed inside the 'EmergencyCallDataValue' element. 1489 For example: 1491 1493 1494 1496 1498 This is an example text. 1499 1500 1501 1502 1504 Test 1505 NENA 1506 Access Infrastructure Provider 1507 1508 sip:15555550987@burf.example.com;user=phone 1509 1510 1511 1513 Example Provided-By by Value. 1515 4.4. The Content-Disposition Parameter 1517 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1518 It updates and clarifies handling originally defined in RFC 3261 1519 [RFC3261] based on implementation experience. While RFC 3261 did not 1520 mandate support for 'multipart' message bodies, 'multipart/mixed' 1521 MIME bodies are used by many extensions (including this document) 1522 today. For example, adding a PIDF-LO, SDP, and additional data in 1523 body of a SIP message requires a 'multipart' message body. 1525 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1526 parameter for the Content-Disposition header field. These RFCs 1527 describe how a UAS reacts if it receives a message body whose content 1528 type or disposition type it does not understand. If the 'handling' 1529 parameter has the value "optional", the UAS ignores the message body. 1530 If the 'handling' parameter has the value "required", the UAS returns 1531 a 415 (Unsupported Media Type) response. The 'by-reference' 1532 disposition type allows a SIP message to contain a reference to the 1533 body part, and the SIP UA processes the body part according to the 1534 reference. This is the case for the Call-info header containing a 1535 Content Indirection (CID) URL. 1537 As an example, a SIP message indicates the Content-Disposition 1538 parameter in the body of the SIP message as shown in Figure 10. 1540 Content-Type: application/sdp 1542 ...Omit Content-Disposition here; defaults are ok 1543 ...SDP goes in here 1545 --boundary1 1547 Content-Type: application/pidf+xml 1548 Content-ID: 1549 Content-Disposition: by-reference;handling=optional 1551 ...PIDF-LO goes in here 1553 --boundary1-- 1554 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1555 Content-ID: <1234567890@atlanta.example.com> 1556 Content-Disposition: by-reference; handling=optional 1558 ...Data provider information data goes in here 1560 --boundary1-- 1562 Figure 10: Example for use of the Content-Disposition Parameter in 1563 SIP. 1565 5. Examples 1567 This section illustrates a longer and more complex example, as shown 1568 in Figure 11. In this example additional data is added by the end 1569 device, included by the VoIP provider (via the PIDF-LO), and provided 1570 by the access network provider. 1572 [================] (1) [================] 1573 [ O +----+ ] Emergency Call [ ] 1574 [ /|\ | UA |-------------------------------> ] 1575 [ | +----+ ] +Device Info [ ] 1576 [ / \ ] +Data Provider Info [ ] 1577 [ ] +Location URI [ ] 1578 [ Access Network ] [ ] 1579 [ Provider ] [ VoIP Provider ] 1580 [ ] [ example.org ] 1581 [ ^ ] [ ] 1582 [=======.========] [============|===] 1583 . | 1584 . | 1585 . [================] | 1586 . [ ] (2) | 1587 . (3) [ <--------------+ 1588 ....................> PSAP ] Emergency Call 1589 Location [ ] +Device Info 1590 +Owner/Subscriber Info [ ] +Data Provider Info #2 1591 +Device Info [ ] +Location URI 1592 +Data Provider Info #3 [================] 1594 Legend: 1596 --- Emergency Call Setup Procedure 1597 ... Location Retrieval/Response 1598 Figure 11: Additional Data Example Flow 1600 The example scenario starts with the end device itself adding device 1601 information, owner/subscriber information, a location URI, and data 1602 provider information to the outgoing emergency call setup message 1603 (see step #1 in Figure 11). The SIP INVITE example is shown in 1604 Figure 12. 1606 INVITE urn:service:sos SIP/2.0 1607 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1608 Max-Forwards: 70 1609 To: 1610 From: Hannes Tschofenig ;tag=9fxced76sl 1611 Call-ID: 3848276298220188511@example.com 1612 Call-Info: ;purpose=icon, 1613 ;purpose=info, 1614 1615 ;purpose=EmergencyCallData.ProviderInfo, 1616 1617 ;purpose=EmergencyCallData.DeviceInfo 1618 Geolocation: 1619 Geolocation-Routing: yes 1620 Accept: application/sdp, application/pidf+xml, 1621 application/EmergencyCallData.ProviderInfo+xml 1622 CSeq: 31862 INVITE 1623 Contact: 1624 Content-Type: multipart/mixed; boundary=boundary1 1626 Content-Length: ... 1628 --boundary1 1630 Content-Type: application/sdp 1632 ...SDP goes here 1634 --boundary1-- 1636 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1637 Content-ID: <0123456789@atlanta.example.com> 1638 Content-Disposition: by-reference;handling=optional 1639 1641 1644 string0987654321@example.org 1645 1646 SoftPhn 1647 00-0d-4b-30-72-df 1649 1651 --boundary1-- 1653 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1654 Content-ID: <1234567890@atlanta.example.com> 1655 Content-Disposition: by-reference;handling=optional 1656 1657 1660 12345 1661 string0987654321@example.org 1662 1663 Hannes Tschofenig 1664 1665 Other 1666 sip:hannes@example.com 1667 EN 1668 1670 1671 Hannes Tschofenig 1672 1673 Hannes 1674 Tschofenig 1675 1676 1677 Dipl. Ing. 1678 1679 --0203 1680 1681 20090808T1430-0500 1682 1683 M 1684 1685 1 1686 1687 de 1688 1689 1690 2 1691 1692 en 1693 1694 1695 1696 work 1697 1701 1702 1703 1704 Linnoitustie 6 1705 Espoo 1706 Uusimaa 1707 02600 1708 Finland 1709 1710 1711 1712 1713 work 1714 voice 1715 1716 1717 tel:+358 50 4871445 1718 1719 1720 work 1721 1722 hannes.tschofenig@nsn.com 1723 1724 1725 work 1726 1727 geo:60.210796,24.812924 1728 1729 1730 1731 home 1732 1733 https://www.example.com/key.asc 1734 1735 1736 Finland/Helsinki 1737 1738 home 1739 1740 http://example.com/hannes.tschofenig 1741 1742 1743 1744 1745 --boundary1-- 1747 Figure 12: End Device sending SIP INVITE with Additional Data. 1749 In this example, information available to the access network operator 1750 is included in the call setup message only indirectly via the use of 1751 the location reference. The PSAP has to retrieve it via a separate 1752 look-up step. Since the access network provider and the VoIP service 1753 provider are two independent entities in this scenario, the access 1754 network operator is not involved in application layer exchanges; the 1755 SIP INVITE transits the access network transparently, as illustrated 1756 in step #1. No change to the SIP INVITE is applied. 1758 When the VoIP service provider receives the message and determines 1759 based on the Service URN that the incoming request is an emergency 1760 call. It performs the typical emergency services related tasks, 1761 including location-based routing, and adds additional data, namely 1762 service and subscriber information, to the outgoing message. For the 1763 example we assume a VoIP service provider that deploys a back-to-back 1764 user agent allowing additional data to be included in the body of the 1765 SIP message (rather than per reference in the header), which allows 1766 us to illustrate the use of multiple data provider info blocks. The 1767 resulting message is shown in Figure 13. 1769 INVITE sips:psap@example.org SIP/2.0 1770 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1771 Max-Forwards: 70 1772 To: 1773 From: Hannes Tschofenig ;tag=9fxced76sl 1774 Call-ID: 3848276298220188511@example.com 1775 Call-Info: ;purpose=icon, 1776 ;purpose=info, 1777 1778 ;purpose=EmergencyCallData.ProviderInfo 1779 1780 ;purpose=EmergencyCallData.DeviceInfo 1781 Call-Info: 1782 ;purpose=EmergencyCallData.ServiceInfo 1783 Call-Info: 1784 ;purpose=EmergencyCallData.ProviderInfo 1785 Geolocation: 1786 Geolocation-Routing: yes 1787 Accept: application/sdp, application/pidf+xml, 1788 application/EmergencyCallData.ProviderInfo+xml 1789 CSeq: 31862 INVITE 1790 Contact: 1791 Content-Type: multipart/mixed; boundary=boundary1 1793 Content-Length: ... 1795 --boundary1 1797 Content-Type: application/sdp 1799 ...SDP goes here 1801 --boundary1-- 1803 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1804 Content-ID: <0123456789@atlanta.example.com> 1805 Content-Disposition: by-reference;handling=optional 1806 1808 1811 string0987654321@example.org 1812 1813 SoftPhn 1814 00-0d-4b-30-72-df 1816 1818 --boundary1-- 1820 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1821 Content-ID: <1234567890@atlanta.example.com> 1822 Content-Disposition: by-reference;handling=optional 1823 1824 1827 string0987654321@example.org 1828 1829 Hannes Tschofenig 1830 1831 Other 1832 sip:hannes@example.com 1833 EN 1834 1836 1837 Hannes Tschofenig 1838 1839 Hannes 1840 Tschofenig 1841 1842 1843 Dipl. Ing. 1844 1845 --0203 1846 1847 20090808T1430-0500 1848 1849 M 1850 1851 1 1852 1853 de 1854 1855 1856 2 1857 1858 en 1859 1860 1861 1862 work 1863 1867 1868 1869 1870 Linnoitustie 6 1871 Espoo 1872 Uusimaa 1873 02600 1874 Finland 1875 1876 1877 1878 1879 work 1880 voice 1881 1882 1883 tel:+358 50 4871445 1884 1885 1886 work 1887 1888 hannes.tschofenig@nsn.com 1889 1890 1891 work 1892 1893 geo:60.210796,24.812924 1894 1895 1896 1897 home 1898 1899 https://www.example.com/key.asc 1900 1901 1902 Finland/Helsinki 1903 1904 home 1905 1906 http://example.com/hannes.tschofenig 1907 1908 1909 1910 1912 --boundary1-- 1914 Content-Type: application/EmergencyCallData.ServiceInfo+xml 1915 Content-ID: 1916 Content-Disposition: by-reference;handling=optional 1917 1918 1921 string0987654321@example.org 1922 1923 Residence 1924 VOIP 1925 Unknown 1926 1928 --boundary1-- 1930 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1931 Content-ID: 1932 Content-Disposition: by-reference;handling=optional 1933 1934 1937 string0987654321@example.org 1938 1939 Example VoIP Provider 1940 1941 urn:nena:companyid:ID123 1942 NENA 1943 Service Provider 1944 sip:voip-provider@example.com 1945 EN 1946 1948 1949 John Doe 1950 1951 John 1952 Doe 1953 1954 1955 1956 1957 --0203 1958 1959 20090808T1430-0500 1960 1961 M 1962 1963 1 1964 1965 en 1966 1967 1968 work 1969 1970 Example VoIP Provider 1971 1972 1973 1974 work 1975 1978 1979 1980 1981 Downing Street 10 1982 London 1983 1984 SW1A 2AA 1985 UK 1986 1987 1988 1989 1990 work 1991 voice 1992 1993 1994 sips:john.doe@example.com 1995 1996 1997 work 1998 1999 john.doe@example.com 2000 2001 2002 work 2003 2004 geo:51.503396, 0.127640 2005 2006 Europe/London 2007 2008 home 2009 2010 http://www.example.com/john.doe 2011 2012 2013 2014 2016 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2018 Finally, the PSAP requests location information from the access 2019 network operator. The response is shown in Figure 14. Along with 2020 the location information additional data is provided in the 2021 element of the PIDF-LO. 2023 2024 2029 2030 2031 2032 2034 AU 2035 NSW 2036 Wollongong 2037 North Wollongong 2038 Flinders 2039 Street 2040 Campbell Street 2041 Gilligan's Island 2042 Corner 2043 Video Rental Store 2044 2500 2045 Westerns and Classics 2046 store 2047 Private Box 15 2048 2049 2050 2051 true 2052 2053 2013-12-10T20:00:00Z 2054 2055 2056 802.11 2058 2061 2064 2065 2067 string0987654321@example.org 2068 2069 University of California, Irvine 2070 2071 urn:nena:companyid:uci 2072 NENA 2073 Other 2074 tel:+1 9498245222 2075 EN 2076 2078 2080 string0987654321@example.org 2081 2082 This is an example text. 2083 2085 2086 2087 2088 mac:00-0d-4b-30-72-df 2089 2013-07-09T20:57:29Z 2090 2091 2093 Figure 14: Access Network Provider returning PIDF-LO with Additional 2094 Data. 2096 6. XML Schemas 2098 This section defines the XML schemas of the five data blocks. 2099 Additionally, the Provided-By schema is specified. 2101 6.1. EmergencyCallData.ProviderInfo XML Schema 2103 2104 2114 2117 2119 2120 2121 2122 2123 2125 2129 2132 2133 2134 2135 2136 2137 2139 2140 2141 2144 2147 2150 2153 2156 2159 2162 2166 2169 2172 2174 2175 2177 2179 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2181 6.2. EmergencyCallData.ServiceInfo XML Schema 2183 2184 2192 2195 2197 2198 2199 2202 2205 2208 2211 2214 2217 2218 2220 2222 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2224 6.3. EmergencyCallData.DeviceInfo XML Schema 2226 2227 2234 2237 2239 2240 2241 2244 2247 2250 2253 2255 2256 2257 2258 2261 2262 2263 2265 2267 2270 2273 2275 2276 2278 2280 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2282 6.4. EmergencyCallData.SubscriberInfo XML Schema 2284 2285 2294 2297 2299 2301 2302 2303 2304 2307 2310 2313 2314 2315 2316 2318 2320 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2322 6.5. EmergencyCallData.Comment XML Schema 2324 2325 2333 2336 2338 2339 2340 2343 2347 2349 2350 2352 2353 2354 2355 2356 2357 2358 2360 2362 Figure 19: EmergencyCallData.Comment XML Schema. 2364 6.6. Provided-By XML Schema 2366 This section defines the Provided-By schema. 2368 2369 2382 2383 2384 2385 2386 2388 2390 2391 2392 2395 2399 2403 2406 2408 2410 2412 2413 2414 2415 2416 2418 2419 2421 2423 2424 2425 2427 2429 2430 2431 2434 2437 2440 2443 2447 2450 2451 2453 2455 Figure 20: Provided-By XML Schema. 2457 7. Security Considerations 2459 The information in this data structure will usually be considered 2460 private. HTTPS is specified to require the provider of the 2461 information to validate the credentials of the requester. While the 2462 creation of a public key infrastructure (PKI) that has global scope 2463 may be difficult, the alternatives to creating devices and services 2464 that can provide critical information securely are more daunting. 2465 The provider may enforce any policy it wishes to use, but PSAPs and 2466 responder agencies should deploy a PKI so that providers of 2467 additional data can check the certificate of the client and decide 2468 the appropriate policy to enforce based on that certificate. 2470 Ideally, the PSAP and emergency responders will be given credentials 2471 signed by an authority trusted by the data provider. In most 2472 circumstances, nationally recognized credentials would be sufficient, 2473 and if the emergency services arranges a PKI, data providers could be 2474 provisioned with the root CA public key for a given nation. Some 2475 nations are developing a PKI for this, and related, purposes. Since 2476 calls could be made from devices where the device and/or the service 2477 provider(s) are not local to the emergency authorities, globally 2478 recognized credentials are useful. This might be accomplished by 2479 extending the notion of the "forest guide" described in [RFC5222] to 2480 allow the forest guide to provide the credential of the PKI root for 2481 areas that it has coverage information for, but standards for such a 2482 mechanism are not yet available. In its absence, the data provider 2483 will need to obtain the root CA credentials for any areas it is 2484 willing to provide additional data by out of band means. With the 2485 credential of the root CA for a national emergency services PKI, the 2486 data provider server can validate the credentials of an entity 2487 requesting additional data by reference. 2489 The data provider also needs a credential that can be verified by the 2490 emergency services to know that it is receiving data from the right 2491 server. The emergency authorities could provide credentials, 2492 distinguishable from credentials it provides to emergency responders 2493 and PSAPs, which could be used to validate data providers. Such 2494 credentials would have to be acceptable to any PSAP or responder that 2495 could receive a call with additional data supplied by that provider. 2496 This would be extensible to global credential validation using the 2497 forest guide as above. In the absence of such credentials, the 2498 emergency authorities could maintain a list of local data providers' 2499 credentials provided to it out of band. At a minimum, the emergency 2500 authorities could obtain a credential from the DNS entry of the 2501 domain in the Additional Data URI to at least validate that the 2502 server is known to the domain providing the URI. 2504 Data provided by devices by reference have similar credential 2505 validation issues to service providers, and the solutions are the 2506 same. 2508 8. Privacy Considerations 2510 This document enables functionality for conveying additional 2511 information about the caller to the callee. Some of this information 2512 is personal data and therefore privacy concerns arise. An explicit 2513 privacy indicator for information directly relating to the callers 2514 identity is defined and use is mandatory. However, observance of 2515 this request for privacy and what information it relates to is 2516 controlled by the destination jurisdiction. 2518 There are a number of privacy concerns with regular real-time 2519 communication services that are also applicable to emergency calling. 2520 Data protection regulation world-wide has, however, decided to create 2521 exceptions for emergency services since the drawbacks of disclosing 2522 personal data in comparison to the benefit for the emergency caller 2523 are often towards the latter. Hence, the data protection rights of 2524 individuals are often waived for emergency situations. There are, 2525 however, still various countries that offer some degree of anonymity 2526 for the caller towards PSAP call takers. 2528 The functionality defined in this document, however, far exceeds the 2529 amount of information sharing found in the Plain old telephone system 2530 (POTS). For this reason there are additional privacy threats to 2531 consider, which are described in more detail in [RFC6973]. 2533 Stored Data Compromise: First, there is an increased risk of stored 2534 data compromise since additional data is collected and stored in 2535 databases. Without adequate measures to secure stored data from 2536 unauthorized or inappropriate access at access network operators, 2537 service providers, end devices, as well as PSAPs individuals are 2538 exposed to potential financial, reputational, or physical harm. 2540 Misattribution: If the personal data collected and conveyed is 2541 incorrect or inaccurate then this may lead to misattribution. 2542 Misattribution occurs when data or communications related to one 2543 individual are attributed to another. 2545 Identification: By the nature of the additional data and its 2546 capability to provide much richer information about the caller, 2547 the call, and the location the calling party is identified in a 2548 much better way. Some users may feel uncomfortable with this 2549 degree of information sharing even in emergency services 2550 situations. 2552 Secondary Use: Furthermore, there is the risk of secondary use. 2553 Secondary use is the use of collected information about an 2554 individual without the individual's consent for a purpose 2555 different from that for which the information was collected. The 2556 stated purpose of the additional data is for emergency services 2557 purposes but theoretically the same information could be used for 2558 any other call as well. Additionally, parties involved in the 2559 emergency call may retain the obtained information and may re-use 2560 it for other, non-emergency services purposes. 2562 Disclosure: When the data defined in this document is not properly 2563 security (while in transit with traditional communication security 2564 techniques, and while at rest using access control mechanisms) 2565 there is the risk of disclosure, which is the revelation of 2566 information about an individual that affects the way others judge 2567 the individual. 2569 To mitigate these privacy risks the following countermeasures can be 2570 taken. 2572 In regions where callers can elect to suppress certain personally 2573 identifying information, the network or PSAP functionality can 2574 inspect privacy flags within the SIP headers to determine what 2575 information may be passed, stored, or displayed to comply with local 2576 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2577 The presence of this privacy type in a Privacy header field indicates 2578 that the user would like the network asserted identity to be kept 2579 private with respect to SIP entities outside the trust domain with 2580 which the user authenticated, including the PSAP. 2582 This document defines various data structures that constitutes 2583 personal data. Local regulations may govern what data must be 2584 provided in emergency calls, but in general, the emergency call 2585 system is often aided by the kinds of information described in this 2586 document. There is a tradeoff between the privacy considerations and 2587 the utility of the data. For adequate protection this specification 2588 requires all data exchanges to be secured via communication security 2589 techniques (namely TLS) against eavesdropping and inception. 2590 Furthermore, security safeguards are required to prevent unauthorized 2591 access to data at rest. Various security incidents over the last 10 2592 years have shown data breaches are not not uncommon and are often 2593 caused by lack of proper access control frameworks, software bugs 2594 (buffer overflows), or missing input parsing (SQL injection attacks). 2595 The risks of data breaches is increased with the obligation for 2596 emergency services to retain emergency call related data for extended 2597 periods, e.g., several years are the norm. 2599 Finally, it is also worth to highlight the nature of the SIP 2600 communication architecture, which introduces additional complications 2601 for privacy. Some forms of data can be sent by value in the SIP 2602 signaling or by value (URL in SIP signaling). When data is sent by 2603 value, all intermediaries have access to the data. As such, these 2604 intermediaries may also introduce additional privacy risk. 2605 Therefore, in situations where the conveyed information raises 2606 privacy concerns and intermediaries are involved transmitting a 2607 reference is more appropriate (assuming proper access control 2608 policies are available for distinguishing the different entities 2609 dereferencing the reference). Without access control policies any 2610 party in possession of the reference is able to resolve the reference 2611 and to obtain the data, including intermediaries. 2613 9. IANA Considerations 2615 9.1. Registry creation 2617 This document creates a new registry called 'Emergency Call 2618 Additional Data'. The following sub-registries are created for this 2619 registry. 2621 9.1.1. Provider ID Series Registry 2623 This document creates a new sub-registry called 'Additional Call Data 2624 Provider ID Series'. As defined in [RFC5226], this registry operates 2625 under "Expert Review" rules. The expert should determine that the 2626 entity requesting a new value is a legitimate issuer of service 2627 provider IDs suitable for use in Additional Call Data. 2629 The content of this registry includes: 2631 Name: The identifier which will be used in the ProviderIDSeries 2632 element 2634 Source: The full name of the organization issuing the identifiers 2636 URL: A URL to the organization for further information 2638 The initial set of values is listed in Figure 21. 2640 +-----------+--------------------------+----------------------+ 2641 | Name | Source | URL | 2642 +-----------+--------------------------+----------------------+ 2643 | NENA | National Emergency | http://www.nena.org | 2644 | | Number Association | | 2645 | EENA | European Emergency | http://www.eena.org | 2646 | | Number Association | | 2647 +-----------+--------------------------+----------------------+ 2649 Figure 21: Provider ID Series Registry. 2651 9.1.2. Service Environment Registry 2653 This document creates a new sub-registry called 'Additional Call 2654 Service Environment'. As defined in [RFC5226], this registry 2655 operates under "Expert Review" rules. The expert should determine 2656 that the entity requesting a new value is relevant for this service 2657 element. 2659 The content of this registry includes: 2661 Token: The value to be used in element. 2663 Description: A short description of the token. 2665 The initial set of values is listed in Figure 22. 2667 +-----------+--------------------------+ 2668 | Token | Description | 2669 +-----------+--------------------------+ 2670 | Business | [[This RFC]] | 2671 | Residence | [[This RFC]] | 2672 +-----------+--------------------------+ 2674 Figure 22: Service Environment Registry. 2676 9.1.3. Service Provider Type Registry 2678 This document creates a new sub-registry called 'Service Provider 2679 Type'. As defined in [RFC5226], this registry operates under "Expert 2680 Review". The expert should determine that the proposed new value is 2681 distinct from existing values and appropriate for use in the 2682 TypeOfServicerProvider element 2684 The content of this registry includes: 2686 Name: The value to be used in TypeOfServiceProvider. 2688 Description: A short description of the type of service provider 2690 The initial set of values is defined in Figure 1. 2692 9.1.4. Service Delivered Registry 2693 This document creates a new sub-registry called 'Service Delivered'. 2694 As defined in [RFC5226], this registry operates under "Expert Review" 2695 rules. The expert should consider whether the proposed service is 2696 unique from existing services and the definition of the service will 2697 be clear to implementors and PSAPS/responders. 2699 The content of this registry includes: 2701 Name: Enumeration token of the service. 2703 Description: Short description identifying the service. 2705 The initial set of values are defined in Figure 3. 2707 9.1.5. Device Classification Registry 2709 This document creates a new sub-registry called 'Device 2710 Classification'. As defined in [RFC5226], this registry operates 2711 under "Expert Review" rules. The expert should consider whether the 2712 proposed class is unique from existing classes and the definition of 2713 the class will be clear to implementors and PSAPS/responders. 2715 The content of this registry includes: 2717 Name: Enumeration token of the device classification. 2719 Description: Short description identifying the device type. 2721 The initial set of values are defined in Figure 5. 2723 9.1.6. Device ID Type Type Registry 2725 This document creates a new sub-registry called 'Additional Call Data 2726 Device ID Type'. As defined in [RFC5226], this registry operates 2727 under "Expert Review" rules. The expert should ascertain that the 2728 proposed type is well understood, and provides the information useful 2729 to PSAPs and responders to uniquely identify a device. 2731 The content of this registry includes: 2733 Name: Enumeration token of the device id type. 2735 Description: Short description identifying type of device id. 2737 The initial set of values are defined in Figure 6. 2739 9.1.7. Device/Service Data Type Registry 2740 This document creates a new sub-registry called 'Device/Service Data 2741 Type Registry'. As defined in [RFC5226], this registry operates 2742 under "Expert Review" and "Specification Required" rules. The expert 2743 should ascertain that the proposed type is well understood, and 2744 provides information useful to PSAPs and responders. The 2745 specification must contain a complete description of the data, and a 2746 precise format specification suitable to allow interoperable 2747 implementations. 2749 The content of this registry includes: 2751 Name: Enumeration token of the data type. 2753 Description: Short description identifying the the data. 2755 Specification: Citation for the specification of the data. 2757 The initial set of values are listed in Figure 23. 2759 +---------+----------------------------------------+----------------+ 2760 | Token | Description | Specification | 2761 +---------+----------------------------------------+----------------+ 2762 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2763 +---------+----------------------------------------+----------------+ 2765 Figure 23: Device/Service Data Type Registry. 2767 9.1.8. Additional Data Blocks Registry 2769 This document creates a new sub-registry called 'Additional Data 2770 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2771 As defined in [RFC5226], this registry operates under "Expert Review" 2772 and "Specification Required" rules. The expert is responsible for 2773 verifying that the document contains a complete and clear 2774 specification and the proposed functionality does not obviously 2775 duplicate existing functionality. 2777 The content of this registry includes: 2779 Name: Element Name of enclosing block. 2781 Reference: The document that describes the block 2783 The initial set of values are listed in Figure 24. 2785 +--------------+------------+ 2786 | Token | Reference | 2787 +--------------+------------+ 2788 | ProviderInfo | [This RFC] | 2789 | ServiceInfo | [This RFC] | 2790 | DeviceInfo | [This RFC] | 2791 | Subscriber | [This RFC] | 2792 | Comment | [This RFC] | 2793 +--------------+------------+ 2795 Figure 24: Additional Data Blocks Registry. 2797 9.2. 'EmergencyCallData' Purpose Parameter Value 2799 This document defines the 'EmergencyCallData' value for the "purpose" 2800 parameter of the Call-Info header field. The Call-Info header and 2801 the corresponding registry for the 'purpose' parameter was 2802 established with RFC 3261 [RFC3261]. 2804 Header Parameter New 2805 Field Name Value Reference 2806 ---------- --------- ----------------- --------- 2807 Call-Info purpose EmergencyCallData [This RFC] 2809 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2811 This section registers the namespace specified in Section 9.5.1 in 2812 the provided-by registry established by RFC 4119, for usage within 2813 the element of a PIDF-LO. 2815 The schema for the provided-by schema used by this document is 2816 specified in Section 6.6. 2818 9.4. MIME Registrations 2820 9.4.1. MIME Content-type Registration for 'application/ 2821 EmergencyCallData.ProviderInfo+xml' 2823 This specification requests the registration of a new MIME type 2824 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2825 RFC 3023 [RFC3023]. 2827 MIME media type name: application 2829 MIME subtype name: EmergencyCallData.ProviderInfo+xml 2831 Mandatory parameters: none 2832 Optional parameters: charset Indicates the character encoding of 2833 enclosed XML. 2835 Encoding considerations: Uses XML, which can employ 8-bit 2836 characters, depending on the character encoding used. See 2837 Section 3.2 of RFC 3023 [RFC3023]. 2839 Security considerations: This content type is designed to carry 2840 the data provider information, which is a sub-category of 2841 additional data about an emergency call. Since this data contains 2842 personal information appropriate precautions have to be taken to 2843 limit unauthorized access, inappropriate disclosure to third 2844 parties, and eavesdropping of this information. Please refer to 2845 Section 7 and Section 8 for more information. 2847 Interoperability considerations: None 2849 Published specification: [TBD: This specification] 2851 Applications which use this media type: Emergency Services 2853 Additional information: Magic Number: None File Extension: .xml 2854 Macintosh file type code: 'TEXT' 2856 Person and email address for further information: Hannes 2857 Tschofenig, Hannes.Tschofenig@gmx.net 2859 Intended usage: LIMITED USE 2861 Author: This specification is a work item of the IETF ECRIT 2862 working group, with mailing list address . 2864 Change controller: The IESG 2866 9.4.2. MIME Content-type Registration for 'application/ 2867 EmergencyCallData.ServiceInfo+xml' 2869 This specification requests the registration of a new MIME type 2870 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2871 RFC 3023 [RFC3023]. 2873 MIME media type name: application 2875 MIME subtype name: EmergencyCallData.ServiceInfo+xml 2877 Mandatory parameters: none 2878 Optional parameters: charset Indicates the character encoding of 2879 enclosed XML. 2881 Encoding considerations: Uses XML, which can employ 8-bit 2882 characters, depending on the character encoding used. See 2883 Section 3.2 of RFC 3023 [RFC3023]. 2885 Security considerations: This content type is designed to carry 2886 the service information, which is a sub-category of additional 2887 data about an emergency call. Since this data contains personal 2888 information appropriate precautions have to be taken to limit 2889 unauthorized access, inappropriate disclosure to third parties, 2890 and eavesdropping of this information. Please refer to Section 7 2891 and Section 8 for more information. 2893 Interoperability considerations: None 2895 Published specification: [TBD: This specification] 2897 Applications which use this media type: Emergency Services 2899 Additional information: Magic Number: None File Extension: .xml 2900 Macintosh file type code: 'TEXT' 2902 Person and email address for further information: Hannes 2903 Tschofenig, Hannes.Tschofenig@gmx.net 2905 Intended usage: LIMITED USE 2907 Author: This specification is a work item of the IETF ECRIT 2908 working group, with mailing list address . 2910 Change controller: The IESG 2912 9.4.3. MIME Content-type Registration for 'application/ 2913 EmergencyCallData.DeviceInfo+xml' 2915 This specification requests the registration of a new MIME type 2916 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2917 RFC 3023 [RFC3023]. 2919 MIME media type name: application 2921 MIME subtype name: EmergencyCallData.DeviceInfo+xml 2923 Mandatory parameters: none 2924 Optional parameters: charset Indicates the character encoding of 2925 enclosed XML. 2927 Encoding considerations: Uses XML, which can employ 8-bit 2928 characters, depending on the character encoding used. See 2929 Section 3.2 of RFC 3023 [RFC3023]. 2931 Security considerations: This content type is designed to carry 2932 the device information information, which is a sub-category of 2933 additional data about an emergency call. Since this data contains 2934 personal information appropriate precautions have to be taken to 2935 limit unauthorized access, inappropriate disclosure to third 2936 parties, and eavesdropping of this information. Please refer to 2937 Section 7 and Section 8 for more information. 2939 Interoperability considerations: None 2941 Published specification: [TBD: This specification] 2943 Applications which use this media type: Emergency Services 2945 Additional information: Magic Number: None File Extension: .xml 2946 Macintosh file type code: 'TEXT' 2948 Person and email address for further information: Hannes 2949 Tschofenig, Hannes.Tschofenig@gmx.net 2951 Intended usage: LIMITED USE 2953 Author: This specification is a work item of the IETF ECRIT 2954 working group, with mailing list address . 2956 Change controller: The IESG 2958 9.4.4. MIME Content-type Registration for 'application/ 2959 EmergencyCallData.SubscriberInfo+xml' 2961 This specification requests the registration of a new MIME type 2962 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2963 RFC 3023 [RFC3023]. 2965 MIME media type name: application 2967 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 2969 Mandatory parameters: none 2970 Optional parameters: charset Indicates the character encoding of 2971 enclosed XML. 2973 Encoding considerations: Uses XML, which can employ 8-bit 2974 characters, depending on the character encoding used. See 2975 Section 3.2 of RFC 3023 [RFC3023]. 2977 Security considerations: This content type is designed to carry 2978 owner/subscriber information, which is a sub-category of 2979 additional data about an emergency call. Since this data contains 2980 personal information appropriate precautions have to be taken to 2981 limit unauthorized access, inappropriate disclosure to third 2982 parties, and eavesdropping of this information. Please refer to 2983 Section 7 and Section 8 for more information. 2985 Interoperability considerations: None 2987 Published specification: [TBD: This specification] 2989 Applications which use this media type: Emergency Services 2991 Additional information: Magic Number: None File Extension: .xml 2992 Macintosh file type code: 'TEXT' 2994 Person and email address for further information: Hannes 2995 Tschofenig, Hannes.Tschofenig@gmx.net 2997 Intended usage: LIMITED USE 2999 Author: This specification is a work item of the IETF ECRIT 3000 working group, with mailing list address . 3002 Change controller: The IESG 3004 9.4.5. MIME Content-type Registration for 'application/ 3005 EmergencyCallData.Comment+xml' 3007 This specification requests the registration of a new MIME type 3008 according to the procedures of RFC 4288 [RFC4288] and guidelines in 3009 RFC 3023 [RFC3023]. 3011 MIME media type name: application 3013 MIME subtype name: EmergencyCallData.Comment+xml 3015 Mandatory parameters: none 3016 Optional parameters: charset Indicates the character encoding of 3017 enclosed XML. 3019 Encoding considerations: Uses XML, which can employ 8-bit 3020 characters, depending on the character encoding used. See 3021 Section 3.2 of RFC 3023 [RFC3023]. 3023 Security considerations: This content type is designed to carry a 3024 comment, which is a sub-category of additional data about an 3025 emergency call. This data may contain personal information. 3026 Appropriate precautions may have to be taken to limit unauthorized 3027 access, inappropriate disclosure to third parties, and 3028 eavesdropping of this information. Please refer to Section 7 and 3029 Section 8 for more information. 3031 Interoperability considerations: None 3033 Published specification: [TBD: This specification] 3035 Applications which use this media type: Emergency Services 3037 Additional information: Magic Number: None File Extension: .xml 3038 Macintosh file type code: 'TEXT' 3040 Person and email address for further information: Hannes 3041 Tschofenig, Hannes.Tschofenig@gmx.net 3043 Intended usage: LIMITED USE 3045 Author: This specification is a work item of the IETF ECRIT 3046 working group, with mailing list address . 3048 Change controller: The IESG 3050 9.5. URN Sub-Namespace Registration 3052 9.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3054 This section registers a new XML namespace, as per the guidelines in 3055 RFC 3688 [RFC3688]. 3057 URI: urn:ietf:params:xml:ns:EmergencyCallData 3059 Registrant Contact: IETF, ECRIT working group, , as 3060 delegated by the IESG . 3062 XML: 3064 BEGIN 3065 3066 3068 3069 3070 3072 Namespace for Additional Emergency Call Data 3073 3074 3075

Namespace for Additional Data related to an Emergency Call

3076

See [TBD: This document].

3077 3078 3079 END 3081 9.5.2. Registration for 3082 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3084 This section registers a new XML namespace, as per the guidelines in 3085 RFC 3688 [RFC3688]. 3087 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3089 Registrant Contact: IETF, ECRIT working group, , as 3090 delegated by the IESG . 3092 XML: 3094 BEGIN 3095 3096 3098 3099 3100 3102 Namespace for Additional Emergency Call Data: 3103 Data Provider Information 3104 3105 3106

Namespace for Additional Data related to an Emergency Call

3107

Data Provider Information

3108

See [TBD: This document].

3109 3110 3111 END 3113 9.5.3. Registration for 3114 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3116 This section registers a new XML namespace, as per the guidelines in 3117 RFC 3688 [RFC3688]. 3119 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3121 Registrant Contact: IETF, ECRIT working group, , as 3122 delegated by the IESG . 3124 XML: 3126 BEGIN 3127 3128 3130 3131 3132 3134 Namespace for Additional Emergency Call Data: 3135 Service Information 3136 3137 3138

Namespace for Additional Data related to an Emergency Call

3139

Service Information

3140

See [TBD: This document].

3141 3142 3143 END 3145 9.5.4. Registration for 3146 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3148 This section registers a new XML namespace, as per the guidelines in 3149 RFC 3688 [RFC3688]. 3151 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3153 Registrant Contact: IETF, ECRIT working group, , as 3154 delegated by the IESG . 3156 XML: 3158 BEGIN 3159 3160 3162 3163 3164 3166 Namespace for Additional Emergency Call Data: 3167 Device Information 3168 3169 3170

Namespace for Additional Data related to an Emergency Call

3171

Device Information

3172

See [TBD: This document].

3173 3174 3175 END 3177 9.5.5. Registration for 3178 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3180 This section registers a new XML namespace, as per the guidelines in 3181 RFC 3688 [RFC3688]. 3183 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3185 Registrant Contact: IETF, ECRIT working group, , as 3186 delegated by the IESG . 3188 XML: 3190 BEGIN 3191 3192 3194 3195 3196 3198 Namespace for Additional Emergency Call Data: 3199 Owner/Subscriber Information 3200 3201 3202

Namespace for Additional Data related to an Emergency Call

3203

Owner/Subscriber Information

3204

See [TBD: This document].

3205 3206 3207 END 3209 9.5.6. Registration for 3210 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3212 This section registers a new XML namespace, as per the guidelines in 3213 RFC 3688 [RFC3688]. 3215 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3217 Registrant Contact: IETF, ECRIT working group, , as 3218 delegated by the IESG . 3220 XML: 3222 BEGIN 3223 3224 3226 3227 3228 3230 Namespace for Additional Emergency Call Data:Comment 3231 3232 3233

Namespace for Additional Data related to an Emergency Call

3234

Comment

3235

See [TBD: This document].

3236 3237 3238 END 3240 9.6. Schema Registrations 3242 This specification registers five schemas, as per the guidelines in 3243 RFC 3688 [RFC3688]. 3245 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3246 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3247 delegated by the IESG (iesg@ietf.org). 3249 XML: The XML schema can be found in Figure 15. 3251 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3253 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3254 delegated by the IESG (iesg@ietf.org). 3256 XML: The XML schema can be found in Figure 16. 3258 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3260 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3261 delegated by the IESG (iesg@ietf.org). 3263 XML: The XML schema can be found in Figure 17. 3265 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3267 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3268 delegated by the IESG (iesg@ietf.org). 3270 XML: The XML schema can be found in Section 6.4. 3272 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3274 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3275 delegated by the IESG (iesg@ietf.org). 3277 XML: The XML schema can be found in Section 6.5. 3279 9.7. VCard Parameter Value Registration 3281 This document registers a new value in the vCARD Parameter Values 3282 registry as defined by [RFC6350] with the following template: 3284 Value: main 3286 Purpose: The main telephone number, typically of an enterprise, as 3287 opposed to a direct dial number of an individual employee 3289 Conformance: This value can be used with the "TYPE" parameter 3290 applied on the "TEL" property. 3292 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3293 00 3295 10. Acknowledgments 3297 This work was originally started in NENA and has benefitted from a 3298 large number of participants in NENA standardization efforts, 3299 originally in the Long Term Definition Working Group, the Data 3300 Technical Committee and most recently the Additional Data working 3301 group. The authors are grateful for the initial work and extended 3302 comments provided by many NENA participants, including Delaine 3303 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3304 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3305 and Robert (Bob) Sherry. 3307 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3308 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 3309 comments. 3311 11. References 3313 11.1. Normative References 3315 [RFC0822] Crocker, D., "Standard for the format of ARPA Internet 3316 text messages", STD 11, RFC 822, August 1982. 3318 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 3319 Extensions (MIME) Part One: Format of Internet Message 3320 Bodies", RFC 2045, November 1996. 3322 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3323 Requirement Levels", BCP 14, RFC 2119, March 1997. 3325 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3326 Locators", RFC 2392, August 1998. 3328 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 3329 Types", RFC 3023, January 2001. 3331 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3332 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3333 and QSIG Objects", RFC 3204, December 2001. 3335 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3336 A., Peterson, J., Sparks, R., Handley, M., and E. 3337 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3338 June 2002. 3340 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3341 Extensions to the Session Initiation Protocol (SIP) for 3342 Asserted Identity within Trusted Networks", RFC 3325, 3343 November 2002. 3345 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3346 Extensions (MIME) Parameter", RFC 3459, January 2003. 3348 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3349 January 2004. 3351 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3352 Format", RFC 4119, December 2005. 3354 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 3355 Registration Procedures", RFC 4288, December 2005. 3357 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3358 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3359 May 2008. 3361 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3362 Initiation Protocol (SIP)", RFC 5621, September 2009. 3364 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3365 August 2011. 3367 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3368 6351, August 2011. 3370 11.2. Informational References 3372 [I-D.gellens-negotiating-human-language] 3373 Randy, R., "Negotiating Human Language Using SDP", draft- 3374 gellens-negotiating-human-language-02 (work in progress), 3375 February 2013. 3377 [I-D.ietf-ecrit-psap-callback] 3378 Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3379 Patel, "Public Safety Answering Point (PSAP) Callback", 3380 draft-ietf-ecrit-psap-callback-13 (work in progress), 3381 October 2013. 3383 [I-D.ietf-geopriv-relative-location] 3384 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3385 Thomson, "Relative Location Representation", draft-ietf- 3386 geopriv-relative-location-08 (work in progress), September 3387 2013. 3389 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3390 "Indicating User Agent Capabilities in the Session 3391 Initiation Protocol (SIP)", RFC 3840, August 2004. 3393 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3394 Emergency Context Resolution with Internet Technologies", 3395 RFC 5012, January 2008. 3397 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3398 Format for Presence Information Data Format Location 3399 Object (PIDF-LO)", RFC 5139, February 2008. 3401 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 3402 Tschofenig, "LoST: A Location-to-Service Translation 3403 Protocol", RFC 5222, August 2008. 3405 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3406 Presence Information Data Format Location Object (PIDF-LO) 3407 Usage Clarification, Considerations, and Recommendations", 3408 RFC 5491, March 2009. 3410 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3411 Thomson, "Dynamic Extensions to the Presence Information 3412 Data Format Location Object (PIDF-LO)", RFC 5962, 3413 September 2010. 3415 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3416 5985, September 2010. 3418 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3419 "Framework for Emergency Calling Using Internet 3420 Multimedia", RFC 6443, December 2011. 3422 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3423 R. George, "Specifying Civic Address Extensions in the 3424 Presence Information Data Format Location Object (PIDF- 3425 LO)", RFC 6848, January 2013. 3427 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3428 Communications Services in Support of Emergency Calling", 3429 BCP 181, RFC 6881, March 2013. 3431 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3432 Morris, J., Hansen, M., and R. Smith, "Privacy 3433 Considerations for Internet Protocols", RFC 6973, July 3434 2013. 3436 Appendix A. XML Schema for vCard/xCard 3438 This section contains the vCard/xCard XML schema version of the Relax 3439 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3440 XML schemas defined in this document. The schema in RFC 6351 3441 [RFC6351] is the normative source and this section is informative 3442 only. 3444 3445 3449 3455 3456 3457 vCard Format Specification 3458 3459 3460 3461 3462 3463 3464 3465 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3480 3481 3482 3484 3485 3486 3487 3488 3490 3491 3492 3494 3495 3496 3497 3498 3500 3501 3502 3505 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 3547 3548 3549 3550 3554 3555 3556 Section 5: Parameters 3557 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 3715 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 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 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 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4450 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4479 4480 4481 4482 4483 4484 4485 4487 4488 4489 4490 4491 4492 4493 4495 4496 4497 4499 4501 4502 4503 4505 4506 4507 4508 4510 Authors' Addresses 4512 Brian Rosen 4513 NeuStar 4514 470 Conrad Dr. 4515 Mars, PA 16046 4516 US 4518 Phone: +1 724 382 1051 4519 Email: br@brianrosen.net 4521 Hannes Tschofenig 4522 (no affiliation) 4524 Email: Hannes.Tschofenig@gmx.net 4525 URI: http://www.tschofenig.priv.at 4527 Roger Marshall 4528 TeleCommunication Systems, Inc. 4529 2401 Elliott Avenue 4530 Seattle, WA 98121 4531 US 4533 Phone: +1 206 792 2424 4534 Email: rmarshall@telecomsys.com 4535 URI: http://www.telecomsys.com 4536 Randall Gellens 4537 Qualcomm Technologies, Inc. 4538 5775 Morehouse Drive 4539 San Diego, CA 92121 4540 US 4542 Email: rg+ietf@qti.qualcomm.com 4544 James Winterbottom 4545 (no affiliation) 4546 AU 4548 Email: a.james.winterbottom@gmail.com