idnits 2.17.1 draft-ietf-ecrit-additional-data-19.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 2314 has weird spacing: '...element name=...' == Line 2815 has weird spacing: '...ll-Info pur...' -- The document date (February 11, 2014) is 3698 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 2815, but not defined == Unused Reference: 'RFC5985' is defined on line 3430, but no explicit reference was found in the text ** Obsolete normative reference: RFC 822 (Obsoleted by RFC 2822) ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 6 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT B. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track H. Tschofenig 5 Expires: August 15, 2014 Nokia Solutions and Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 12 February 11, 2014 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-19.txt 17 Abstract 19 When an emergency call is sent to a Public Safety Answering Point 20 (PSAP), the device that sends it, as well as any application service 21 provider in the path of the call, or access network provider through 22 which the call originated may have information about the call, the 23 caller or the location which the PSAP may be able to use. This 24 document describes data structures and a mechanism to convey such 25 data to the PSAP. The mechanism uses a Uniform Resource Identifier 26 (URI), which may point to either an external resource or an object in 27 the body of the SIP message. The mechanism thus allows the data to 28 be passed by reference (when the URI points to an external resource) 29 or by value (when it points into the body of the message). This 30 follows the tradition of prior emergency services standardization 31 work where data can be conveyed by value within the call signaling 32 (i.e., in body of the SIP message) and also by reference. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on August 15, 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 . . . . . . . . . . . . . . . 12 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 Delivered by Provider to End User . . . . . . 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 . . . 22 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 . . . . . . . . . . 24 100 3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25 101 3.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 25 102 3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28 103 3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28 104 3.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 28 105 4. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 28 106 4.1. Transmitting Blocks using the Call-Info Header . . . . . 30 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 . . . . . . . . . . . . 32 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 . . . . . . . . . . . . . . . . . . . 52 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 . 68 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 . . . . . . . . . . . . . . . . . . 70 162 9.7. VCard Parameter Value Registration . . . . . . . . . . . 71 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 they MUST be present in the data structure. 279 'Conditional': means they MUST be present if the specified 280 condition(s) is met. They MAY be present if the condition(s) is 281 not met. 283 'Optional': means they 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 |Service Provider | Calling or Origination telecom SP | 442 |Subcontractor | A contractor to another SP | 443 |Telematics Provider | A sensor based SP, especially | 444 | | vehicle based | 445 |Language Translation Provider | A spoken language translation SP | 446 |Emergency Service Provider | An emergency service provider | 447 | | conveying information to another | 448 | | emergency service provider. | 449 |Emergency Modality Translation| An emergency call specific | 450 | | modality translation service | 451 | | e.g., for sign language | 452 |Relay Provider | A interpretation SP, for example, | 453 | | video relay for sign language | 454 | | interpreting | 455 |Other | Any other type of service provider | 456 +------------------------------+------------------------------------+ 458 Figure 1: Type of Data Provider ID Registry. 460 Reason for Need: Identifies the category of data provider. 462 How Used by Call Taker: This information may be helpful when 463 deciding whom to contact when further information is needed. 465 3.1.5. Data Provider Contact URI 467 Data Element: Data Provider Contact URI 469 Use: Required 471 XML Element: 473 Description: When provided by a service provider or an access 474 network provider, this information MUST be a URI to a 24/7 support 475 organization tasked to provide PSAP support for this emergency 476 call. If the call is from a device, this SHOULD be the contact 477 information of the owner of the device. If a telephone number is 478 the contact address then it MUST be a tel URI. If it is provided 479 as a SIP URI then it MUST be in the form of 480 sip:telephonenumber@serviceprovider:user=phone. Note that this 481 contact information is not used by PSAPs for callbacks (a call 482 from a PSAP directly related to a recently terminated emergency 483 call, placed by the PSAP using a SIP Priority header field set to 484 "psap-callback", as described in [I-D.ietf-ecrit-psap-callback]). 486 Reason for Need: Additional data providers may need to be contacted 487 in error cases or other unusual circumstances. 489 How Used by Call Taker: To contact the supplier of the additional 490 data for assistance in handling the call. 492 3.1.6. Data Provider Languages(s) Supported 494 Data Element: Data Provider Language(s) supported 496 Use: Required. 498 XML Element: 500 Description: The language used by the entity at the Data Provider 501 Contact URI, as an alpha 2-character code as defined in ISO 502 639-1:2002 Codes for the representation of names of languages -- 503 Part 1: Alpha-2 code Multiple instances of this element may occur. 504 Order is significant; preferred language should appear first. The 505 content MUST reflect the languages supported at the contact URI. 507 Note that the 'language' media feature tag, defined in RFC 3840 508 [RFC3840] and the more extensive language negotiation mechanism 509 proposed with [I-D.gellens-negotiating-human-language] are 510 independent of this data provider language indication. 512 Reason for Need: This information indicates if the emergency service 513 authority can directly communicate with the service provider or if 514 an interpreter will be needed. 516 How Used by Call Taker: If call taker cannot speak language(s) 517 supported by the service provider, a translation service will need 518 to be added to the conversation. Alternatively, other persons at 519 the PSAP, besides the call taker, might be consulted for help 520 (depending on the urgency and the type of interaction). 522 3.1.7. xCard of Data Provider 524 Data Element: xCard of Data Provider 526 Use: Optional 528 XML Element: 529 Description: There are many fields in the xCard and the creator of 530 the data structure is encouraged to provide as much information as 531 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 532 minimum. N SHOULD contain the name of the support group or device 533 owner as appropriate. If more than one TEL property is provided, 534 a parameter from the vCard Property Value registry MUST be 535 specified on each TEL. For encoding of the xCard this 536 specification uses the XML-based encoding specified in [RFC6351], 537 referred to in this document as "xCard" 539 Reason for Need: Information needed to determine additional contact 540 information. 542 How Used by Call Taker: Assists call taker by providing additional 543 contact information that may not be included in the SIP invite or 544 the PIDF-LO. 546 3.1.8. Subcontractor Principal 548 Data Element: Subcontractor Principal 550 Use: Conditional. This data is required if the Data Provider type 551 is subcontractor. 553 XML Element: 555 Description: Some providers outsource their obligations to handle 556 aspects of emergency services to specialized providers. If the 557 data provider is a subcontractor to another provider this element 558 contains the DataProviderString of the service provider to 559 indicate which provider the subcontractor is working for. 561 Reason for Need: Identify the entity the subcontractor works for. 563 How Used by Call Taker: Allows the call taker to understand what the 564 relationship between data providers and the service providers in 565 the path of the call are. 567 3.1.9. Subcontractor Priority 569 Data Element: Subcontractor Priority 571 Use: Conditional. This element is required if the Data Provider 572 type is set to "Subcontractor". 574 XML Element: 575 Description: If the subcontractor has to be contacted first then 576 this element MUST have the value "sub". If the provider the 577 subcontractor is working for has to be contacted first then this 578 element MUST have the value "main". 580 Reason for Need: Inform the call taker whom to contact first, if 581 support is needed. 583 How Used by Call Taker: To decide which entity to contact first if 584 assistance is needed. 586 3.1.10. ProviderInfo Example 588 589 592 12345 593 string0987654321@example.org 594 595 Example VoIP Provider 596 597 urn:nena:companyid:ID123 598 NENA 599 Service Provider 600 sip:voip-provider@example.com 601 EN 602 604 605 Hannes Tschofenig 606 607 Hannes 608 Tschofenig 609 610 611 Dipl. Ing. 612 613 --0203 614 615 20090808T1430-0500 616 617 M 618 619 1 620 621 de 623 624 625 2 626 627 en 628 629 630 work 631 632 Example VoIP Provider 633 634 635 636 work 637 641 642 643 644 Linnoitustie 6 645 Espoo 646 Uusimaa 647 02600 648 Finland 649 650 651 652 653 work 654 voice 655 656 657 tel:+358 50 4871445 658 659 660 work 661 662 hannes.tschofenig@nsn.com 663 664 665 work 666 667 geo:60.210796,24.812924 668 669 670 home 671 672 673 http://www.tschofenig.priv.at/key.asc 674 675 676 Finland/Helsinki 677 678 home 679 680 http://www.tschofenig.priv.at 681 682 683 684 686 Figure 2: EmergencyCallData.ProviderInfo Example. 688 3.2. Service Information 690 This block describes the service that the service provider provides 691 to the caller. It SHOULD be included by all SPs in the path of the 692 call. The mime subtype is "application/ 693 EmergencyCallData.ServiceInfo+xml". 695 3.2.1. Service Environment 697 Data Element: Service Environment 699 Use: Required 701 XML Element: 703 Description: This element defines whether a call is from a business 704 or residence caller. Currently, the only valid entries are 705 'Business' or 'Residence'. New values can be defined via the 706 registry created in Figure 22. 708 Reason for Need: To assist in determining equipment and manpower 709 requirements. 711 How Used by Call Taker: Information may be used to assist in 712 determining equipment and manpower requirements for emergency 713 responders. As the information is not always available, and the 714 registry is not all encompassing, this is at best advisory 715 information, but since it mimics a similar capability in some 716 current emergency calling systems, it is known to be valuable. 717 The service provider uses its best information (such as a rate 718 plan, facilities used to deliver service or service description) 719 to determine the information and is not responsible for 720 determining the actual characteristics of the location where the 721 call originates from. 723 3.2.2. Service Delivered by Provider to End User 725 Data Element: Service Delivered by Provider to End User 727 Use: Required 729 XML Element: 731 Description: This defines the type of service the end user has 732 subscribed to. The implied mobility of this service cannot be 733 relied upon. A registry with an initial set of values is defined 734 in Figure 3. 736 +--------+----------------------------------------+ 737 | Name | Description | 738 +--------+----------------------------------------+ 739 | Wrless | Wireless Telephone Service: Includes | 740 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 741 | | LTE (Long Term Evolution) | 742 | Coin | Fixed Public Pay/Coin telephones: Any | 743 | | coin or credit card operated device | 744 | 1way | One way outbound service | 745 | Prison | Inmate call/service | 746 | Temp | Soft dialtone/quick service/warm | 747 | | disconnect/suspended | 748 | MLTS | Multi-line telephone system: Includes | 749 | | all PBX, Centrex, key systems, | 750 | | Shared Tenant Service | 751 | SenseU | Sensor, unattended: Includes devices | 752 | | that generate DATA ONLY. This is | 753 | | one-way information exchange and | 754 | | there will be no other form of | 755 | | communication | 756 | SenseA | Sensor, attended: Includes devices | 757 | | that are supported by a monitoring | 758 | | service provider or automatically | 759 | | open a two-way communication path | 760 | POTS | Wireline: Plain Old Telephone Service | 761 | VOIP | VoIP Telephone Service: A type of | 762 | | service that offers communication | 763 | | over internet protocol, such as Fixed| 764 | | Nomadic, Mobile, ... | 765 | Remote | Off premise extension | 766 | Relay | Relay Service: a type of service where | 767 | | there is a human 3rd party agent who | 768 | | provides some kind of additional | 769 | | assistance to the caller. Includes | 770 | | sign language relay and telematics | 771 | | services which provide a service | 772 | | assistant on the call. | 773 +--------+----------------------------------------+ 775 Figure 3: Service Delivered by Provider to End User Registry. 777 More than one value MAY be returned. For example, a VoIP inmate 778 telephone service is a reasonable combination. 780 Reason for Need: Knowing the type of service may assist the PSAP 781 with the handling of the call. 783 How Used by Call Taker: Call takers often use this information to 784 determine what kinds of questions to ask callers, and how much to 785 rely on supportive information. An emergency call from a prison 786 is treated differently that a call from a sensor device. As the 787 information is not always available, and the registry is not all 788 encompassing, this is at best advisory information, but since it 789 mimics a similar capability in some current emergency calling 790 systems, it is known to be valuable. 792 3.2.3. Service Mobility Environment 794 Data Element: Service Mobility Environment 796 Use: Required 798 XML Element: 800 Description: This provides the service providers view of the 801 mobility of the caller. As the service provider may not know the 802 characteristics of the actual access network used, the value not 803 be relied upon. A registry will reflect the following initial 804 valid entries: 806 * Mobile: the device should be able to move at any time 808 * Fixed: the device is not expected to move unless the service is 809 relocated 811 * Nomadic: the device is not expected to change its point of 812 attachment while on a call 814 * Unknown: no information is known about the service mobility 815 environment for the device 817 Reason for Need: Knowing the service provider's belief of mobility 818 may assist the PSAP with the handling of the call. 820 How Used by Call Taker: To determine whether to assume the location 821 of the caller might change. 823 3.2.4. EmergencyCallData.ServiceInfo Example 825 826 829 string0987654321@example.org 830 831 12345 832 Business 833 MLTS 834 Fixed 835 837 Figure 4: EmergencyCallData.ServiceInfo Example. 839 3.3. Device Information 841 This block provides information about the device used to place the 842 call. It should be provided by any service provider that knows what 843 device is being used, and by the device itself. The mime subtype is 844 "application/EmergencyCallData.DeviceInfo+xml". 846 3.3.1. Device Classification 848 Data Element: Device Classification 850 Use: Optional 852 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 | Mobile | Mobile handset | 873 | ATA | analog terminal adapter | 874 |Satphone| Satellite phone | 875 | FSense | Stationary computing device (alarm | 876 | | system, data sensor) | 877 | Guard | Guardian devices | 878 | Desktop| Desktop PC | 879 | Laptop | Laptop computing device | 880 | Tablet | Tablet computing device | 881 | Alarm | Alarm system | 882 | MSense | Mobile Data sensor | 883 | Beacon | Personal beacons (spot) | 884 | Auto | Auto telematics | 885 | Truck | Truck telematics | 886 | Farm | Farm equipment telematics | 887 | Marine | Marine telematics | 888 | PDA | Personal digital assistant | 889 | PND | Personal navigation device) | 890 | SmrtPhn| Smart phone | 891 | Itab | Internet tablet | 892 | Game | Gaming console | 893 | Video | Video phone | 894 | Text | Other text device | 895 |SoftPhn | Soft phone or soft client software | 896 | NA | Not Available | 897 +--------+----------------------------------------+ 899 Figure 5: Device Classification Registry. 901 Reason for Need: The device classification implies the capability of 902 the calling device and assists in identifying the meaning of the 903 emergency call location information that is being presented. For 904 example, does the device require human intervention to initiate a 905 call or is this call the result of programmed instructions? Does 906 the calling device have the ability to update location or 907 condition changes? Is this device interactive or a one-way 908 reporting device? 910 How Used by Call Taker: May assist with location of caller. For 911 example, a cordless handset may be outside or next door. May 912 provide the calltaker some context about the caller, the 913 capabilities of the device used for the call or the environment 914 the device is being used in. 916 3.3.2. Device Manufacturer 918 Data Element: Device Manufacturer 920 Use: Optional 922 XML Element: 924 Description: The plain language name of the manufacturer of the 925 device. 927 Reason for Need: Used by PSAP management for post-mortem 928 investigation/resolution. 930 How Used by Call Taker: Probably not used by the calltaker, but by 931 PSAP management. 933 3.3.3. Device Model Number 935 Data Element: Device Model Number 937 Use: Optional 939 XML Element: 941 Description: Model number of the device. 943 Reason for Need: Used by PSAP management for after action 944 investigation/resolution. 946 How Used by Call Taker: Probably not used by the calltaker, but by 947 PSAP management. 949 3.3.4. Unique Device Identifier 951 Data Element: Unique Device Identifier 953 Use: Optional 955 XML Element: 957 XML Attribute: 958 Description: A string that identifies the specific device making the 959 call or creating an event. 961 The attribute identifies the type of device 962 identifier. A registry with an initial set of values can be seen 963 in Figure 6. 965 +--------+----------------------------------------+ 966 | Token | Description | 967 +--------+----------------------------------------+ 968 | MEID | Mobile Equipment Identifier (CDMA) | 969 | ESN | Electronic Serial Number(GSM) | 970 | MAC | Media Access Control Address (IEEE) | 971 | WiMAX | Device Certificate Unique ID | 972 | IMEI | International Mobile Equipment ID (GSM)| 973 | UDI | Unique Device Identifier | 974 | RFID | Radio Frequency Identification | 975 | SN | Manufacturer Serial Number | 976 +--------+----------------------------------------+ 978 Figure 6: Registry with Device Identifier Types. 980 Reason for Need: Uniquely identifies the device (independent of any 981 signaling identifiers present in the call signaling stream). 983 How Used by Call Taker: Probably not used by the call taker; may be 984 used by PSAP management during an investigation. 986 Example: 12345 988 3.3.5. Device/Service Specific Additional Data Structure 990 Data Element: Device/service specific additional data structure 992 Use: Optional 994 XML Element: 996 Description: A URI representing additional data whose schema is 997 specific to the device or service which created it. (For example, 998 a medical device or medical device monitoring service may have a 999 defined set of medical data.) The URI, when dereferenced, MUST 1000 yield a data structure defined by the Device/service specific 1001 additional data type value. Different data may be created by each 1002 classification; e.g., a medical device created data set. 1004 Reason for Need: Provides device/service specific data that may be 1005 used by the call taker and/or responders. 1007 How Used by Call Taker: Provide information to guide call takers to 1008 select appropriate responders, give appropriate pre-arrival 1009 instructions to callers, and advise responders of what to be 1010 prepared for. May be used by responders to guide assistance 1011 provided. 1013 3.3.6. Device/Service Specific Additional Data Structure Type 1015 Data Element: Type of device/service specific additional data 1016 structure 1018 Use: Conditional. MUST be provided when device/service specific 1019 additional URI is provided 1021 XML Element: 1023 Description: Value from a registry defined by this document to 1024 describe the type of data that can be retrieved from the device/ 1025 service specific additional data structure. Initial values are: 1027 * IEEE 1512 1029 * VEDS 1031 IEEE 1512 is the USDoT model for traffic incidents and VEDS 1032 provides data elements needed for an efficient emergency response 1033 to vehicular emergency incidents. 1035 Reason for Need: This data element allows identification of 1036 externally defined schemas, which may have additional data that 1037 may assist in emergency response. 1039 How Used by Call Taker: This data element allows the end user 1040 (calltaker or first responder) to know what type of additional 1041 data may be available to aid in providing the needed emergency 1042 services. 1044 Note: Information which is specific to a location or a caller 1045 (person) should not be placed in this section. 1047 3.3.7. Issues with getting new types of data into use 1049 This document describes two mechanisms which allow extension of the 1050 kind of data provided with an emergency call: define a new block or 1051 define a new service specific additional data URL for the DeviceInfo 1052 block. While defining new data types and getting a new device or 1053 application to send the new data may be easy, getting PSAPs and 1054 responders to actually retrieve the data and use it will be 1055 difficult. New mechanism providers should understand that acquiring 1056 and using new forms of data usually require software upgrades at the 1057 PSAP and/or responders, as well as training of call takers and 1058 responders in how to interpret and use the information. Legal and 1059 operational review may also be needed. Overwhelming a call taker or 1060 responder with too much information is highly discouraged. Thus, the 1061 barrier to supporting new data is quite high. 1063 The mechanisms this document describes are meant to encourage 1064 development of widely supported, common data formats for classes of 1065 devices. If all manufacturers of a class of device use the same 1066 format, and the data can be shown to improve outcomes, then PSAPs and 1067 responders may be encouraged to upgrade their systems and train their 1068 staff to use the data. Variations, however well intentioned, are 1069 unlikely to be supported. 1071 Implementers should consider that data from sensor-based devices in 1072 some cases may not be useful to call takers or PSAPs (and privacy or 1073 other considerations may preclude the PSAP from touching the data), 1074 but may be of use to responders. Some standards being developed by 1075 other organizations to carry data from the PSAP to responders are 1076 designed to carry all additional data supplied in the call that 1077 conform to this document, even if the PSAP does not fetch or 1078 interpret the data. This allows responders to get the data even if 1079 the PSAP does not. 1081 3.3.8. Choosing between defining a new type of block or new type of 1082 device/service specific additional data 1084 For devices that have device or service specific data, there are two 1085 choices to carry it. A new block can be defined, or the device/ 1086 service specific additional data URL the DeviceInfo block can be used 1087 and a new type for it defined . The data passed would likely be the 1088 same in both cases. Considerations for choosing which mechanism to 1089 register under include: 1091 Applicability: Information which will be carried by many kinds of 1092 devices or services are more appropriately defined as separate 1093 blocks. 1095 Privacy: Information which may contain private data may be better 1096 sent in the DeviceInfo block, rather than a new block so that 1097 implementations are not tempted to send the data by value, and 1098 thus having more exposure to the data than forcing the data to be 1099 retrieved via the URL in DeviceInfo. 1101 Size: Information which may be very may be better sent in the 1102 DeviceInfo block, rather than a new block so that implementations 1103 are not tempted to send the data by value. Conversely, data which 1104 is small may best be sent in a separate block so that it can be 1105 sent by value 1107 Availability of a server: Providing the data via the device block 1108 requires a server be made available to retrieve the data. 1109 Providing the data via new block allows it to be sent by value 1110 (CID). 1112 3.3.9. EmergencyCallData.DeviceInfo Example 1114 1115 1118 string0987654321@example.org 1119 1120 12345 1121 Fixed phone 1122 Nokia 1123 Lumia 800 1124 35788104 1125 1126 1128 Figure 7: EmergencyCallData.DeviceInfo Example. 1130 3.4. Owner/Subscriber Information 1132 This block describes the owner of the device (if provided by the 1133 device) or the subscriber information, if provided by a service 1134 provider. The contact location is not necessarily the location of 1135 the caller or incident, but is rather the nominal contact address. 1136 The mime subtype is "application/EmergencyCallData.Subscriber+xml". 1138 In some jurisdictions some or all parts of the subscriber-specific 1139 information are subject to privacy constraints. These constraints 1140 vary but dictate what information and be displayed and logged. A 1141 general privacy indicator expressing a desire for privacy is 1142 provided. The interpretation of how this is applied is left to the 1143 receiving jurisdiction as the custodians of the local regulatory 1144 requirements. 1146 3.4.1. Subscriber Data Privacy Indicator 1148 Attribute: privacyRequested, boolean. 1150 Use: Conditional. This attribute MUST be provided if the owner/ 1151 subscriber information block is not empty. 1153 Description: The subscriber data privacy indicator specifically 1154 expresses the subscriber's desire for privacy. In some 1155 jurisdictions subscriber services can have a specific "Type of 1156 Service" which prohibits information, such as the name of the 1157 subscriber, from being displayed. This attribute should be used 1158 to explicitly indicate whether the subscriber service includes 1159 such constraints. 1161 Reason for Need: Some jurisdictions require subscriber privacy to be 1162 observed. 1164 How Used by Call Taker: Where privacy is indicated the call taker 1165 may not have access to some aspects of the subscriber information. 1167 3.4.2. xCard for Subscriber's Data 1169 Data Element: xCARD for Subscriber's Data 1171 Use: Conditional. Subscriber data is provided unless it is not 1172 available. Some services, for example prepaid phones, non- 1173 initialized phones, etc., do not have information about the 1174 subscriber. 1176 XML Element: 1178 Description: Information known by the service provider or device 1179 about the subscriber; e.g., Name, Address, Individual Telephone 1180 Number, Main Telephone Number and any other data. N, ORG (if 1181 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1182 than one TEL property is provided, a parameter from the vCard 1183 Property Value registry MUST be specified on each TEL. 1185 Reason for Need: When the caller is unable to provide information, 1186 this data may be used to obtain it 1188 How Used by Call Taker: Obtaining critical information about the 1189 caller and possibly the location when it is not able to be 1190 obtained otherwise. 1192 3.4.3. EmergencyCallData.SubscriberInfo Example 1194 1195 1199 string0987654321@example.org 1200 1201 1202 1203 1204 Simon Perreault 1205 1206 Perreault 1207 Simon 1208 1209 1210 ing. jr 1211 M.Sc. 1212 1213 --0203 1214 1215 20090808T1430-0500 1216 1217 M 1218 1219 1 1220 1221 fr 1222 1223 1224 2 1225 1226 en 1227 1228 1229 work 1230 1231 Viagenie 1232 1233 1234 1235 work 1236 1240 1241 1242 1243 2875 boul. Laurier, suite D2-630 1244 Quebec 1245 QC 1246 G1V 2M2 1247 Canada 1248 1249 1250 1251 1252 work 1253 voice 1254 1255 1256 tel:+1-418-656-9254;ext=102 1257 1258 1259 1260 1261 work 1262 text 1263 voice 1264 cell 1265 video 1266 1267 1268 tel:+1-418-262-6501 1269 1270 1271 work 1272 1273 simon.perreault@viagenie.ca 1274 1275 1276 work 1277 1278 geo:46.766336,-71.28955 1279 1280 1281 work 1282 1283 1284 http://www.viagenie.ca/simon.perreault/simon.asc 1285 1286 1287 America/Montreal 1288 1289 home 1290 1291 http://nomis80.org 1292 1294 1295 1296 1297 1299 Figure 8: EmergencyCallData.SubscriberInfo Example. 1301 3.5. Comment 1303 This block provides a mechanism for the data provider to supply 1304 extra, human readable information to the PSAP. It is not intended 1305 for a general purpose extension mechanism nor does it aim to provide 1306 machine-reable content. The mime subtype is "application/ 1307 EmergencyCallData.Comment+xml" 1309 3.5.1. Comment 1311 Data Element: EmergencyCallData.Comment 1313 Use: Optional 1315 XML Element: 1317 Description: Human readable text providing additional information to 1318 the PSAP staff. 1320 Reason for Need: Explanatory information for values in the data 1321 structure 1323 How Used by Call Taker: To interpret the data provided 1325 3.5.2. EmergencyCallData.Comment Example 1327 1328 1331 string0987654321@example.org 1332 1333 This is an example text. 1334 1336 Figure 9: EmergencyCallData.Comment Example. 1338 4. Data Transport Mechanisms 1339 This section defines how to convey additional data to an emergency 1340 service provider. Two different means are specified: the first uses 1341 the call signaling; the second uses the element of a 1342 PIDF-LO [RFC4119]. 1344 1. First, the ability to embed a Uniform Resource Identifier (URI) 1345 in an existing SIP header field, the Call-Info header, is 1346 defined. The URI points to the additional data structure. The 1347 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1348 document adds a new compound token starting with the value 1349 'EmergencyCallData' for the Call-Info "purpose" parameter. If 1350 the "purpose" parameter is set to a value starting with 1351 'EmergencyCallData', then the Call-Info header contains either an 1352 HTTPS URL pointing to an external resource or a CID (content 1353 indirection) URI that allows the data structure to be placed in 1354 the body of the SIP message. The "purpose" parameter also 1355 indicates the kind of data (by its MIME type) that is available 1356 at the URI. As the data is conveyed using a URI in the SIP 1357 signaling, the data itself may reside on an external resource, or 1358 may be contained within the body of the SIP message. When the 1359 URI refers to data at an external resource, the data is said to 1360 be passed by reference. When the URI refers to data contained 1361 within the body of the SIP message, the data is said to be passed 1362 by value. A PSAP or emergency responder is able to examine the 1363 type of data provided and selectively inspect the data it is 1364 interested in, while forwarding all of it (the values or 1365 references) to downstream entities. To be conveyed in a SIP 1366 body, additional data about a call is defined as a series of MIME 1367 objects. Each block defined in this document is an XML data 1368 structure identified by its MIME type. (Blocks defined by others 1369 may be encoded in XML or not, as identified by their MIME 1370 registration.) As usual, whenever more than one MIME part is 1371 included in the body of a message, MIME-multipart (i.e., 1372 'multipart/mixed') encloses them all. This document defines a 1373 set of XML schemas and MIME types used for each block defined 1374 here. When additional data is passed by value in the SIP 1375 signaling, each CID URL points to one block in the body. 1376 Multiple URIs are used within a Call-Info header field (or 1377 multiple Call-Info header fields) to point to multiple blocks. 1378 When additional data is provided by reference (in SIP signaling 1379 or Provided-By), each HTTPS URL references one block; the data is 1380 retrieved with an HTTPS GET operation, which returns one of the 1381 blocks as an object (the blocks defined here are returned as XML 1382 objects). 1384 2. Second, the ability to embed additional data structures in the 1385 element of a PIDF-LO [RFC4119] is defined. Besides 1386 a service provider in the call path, the access network provider 1387 may also have similar information that may be valuable to the 1388 PSAP. The access network provider may provide location in the 1389 form of a PIDF-LO from a location server via a location 1390 configuration protocol. The data structures described in this 1391 document are not specific to the location itself, but rather 1392 provides descriptive information having to do with the immediate 1393 circumstances about the provision of the location (who the access 1394 network is, how to contact that entity, what kind of service the 1395 access network provides, subscriber information, etc.). This 1396 data is similar in nearly every respect to the data known by 1397 service providers in the path of the call. When the access 1398 network provider and service provider are separate entities, the 1399 access network does not participate in the application layer 1400 signaling (and hence cannot add a Call-Info header field to the 1401 SIP message), but may provide location information to assist in 1402 locating the caller's device. The element of the 1403 PIDF-LO is a mechanism for the access network provider to supply 1404 the information about the entity or organization that supplied 1405 this location information. For this reason, this document 1406 describes a namespace per RFC 4119 for inclusion in the 1407 element of a PIDF-LO for adding information known 1408 to the access network provider. 1410 One or more blocks of data registered in the Emergency Call 1411 Additional Data registry, as defined in Section 9.1, may be included 1412 or referenced in the SIP signaling (using the Call-Info header field) 1413 or in the element of a PIDF-LO. Every block must be 1414 one of the types in the registry. Since the data of an emergency 1415 call may come from multiple sources, the data itself needs 1416 information describing the source. Consequently, each entity adding 1417 additional data MUST supply the "Data Provider" block. All other 1418 blocks are optional, but each entity SHOULD supply any blocks where 1419 it has at least some of the information in the block. 1421 4.1. Transmitting Blocks using the Call-Info Header 1423 A URI to a block MAY be inserted in a SIP request or response method 1424 (most often INVITE or MESSAGE) with a Call-Info header field 1425 containing a purpose value starting with 'EmergencyCallData' and the 1426 type of data available at the URI. The type of data is denoted by 1427 including the root of the MIME type (not including the 1428 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 1429 separator. For example, when referencing a block with MIME type 1430 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 1431 parameter is set to 'EmergencyCallData.ProviderInfo'. An example 1432 "Call-Info" header field for this would be: 1434 Call-Info: https://www.example.com/23sedde3; 1435 purpose="EmergencyCallData.ProviderInfo" 1437 A Call-info header with a purpose value starting with 1438 'EmergencyCallData' MUST only be sent on an emergency call, which can 1439 be ascertained by the presence of an emergency service urn in a Route 1440 header of a SIP message. 1442 If the data is provided by reference, an HTTPS URI MUST be included 1443 and consequently Transport Layer Security (TLS) protection is applied 1444 for protecting the retrieval of the information. 1446 The data may also be supplied by value in a SIP message. In this 1447 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1448 referencing the MIME body part. 1450 More than one Call-Info header with a purpose value starting with 1451 'EmergencyCallData' can be expected, but at least one MUST be 1452 provided. The device MUST provide one if it knows no service 1453 provider is in the path of the call. The device MAY insert one if it 1454 uses a service provider. Any service provider in the path of the 1455 call MUST insert its own. For example, a device, a telematics 1456 service provider in the call path, as well as the mobile carrier 1457 handling the call will each provide one. There may be circumstances 1458 where there is a service provider who is unaware that the call is an 1459 emergency call and cannot reasonably be expected to determine that it 1460 is an emergency call. In that case, that service provider is not 1461 expected to provide EmergencyCallData. 1463 4.2. Transmitting Blocks by Reference using the Provided-By Element 1465 The 'EmergencyCallDataReference' element is used to transmit an 1466 additional data block by reference within a 'Provided-By' element of 1467 a PIDF-LO. The 'EmergencyCallDataReference' element has two 1468 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1469 type of data block referenced. The value of 'ref' is an HTTPS URL 1470 that resolves to a data structure with information about the call. 1471 The value of 'purpose' is the same as used in a 'Call-Info' header 1472 field (as specified in Section 4.1). 1474 For example, to reference a block with MIME type 'application/ 1475 EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set 1476 to 'EmergencyCallData.ProviderInfo'. An example 1477 'EmergencyCallDataReference' element for this would be: 1479 1482 4.3. Transmitting Blocks by Value using the Provided-By Element 1484 It is RECOMMENDED that access networks supply the data specified in 1485 this document by reference, but they MAY provide the data by value. 1487 The 'EmergencyCallDataValue' element is used to transmit an 1488 additional data block by value within a 'Provided-By' element of a 1489 PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: 1490 'purpose' to indicate the type of data block contained. The value of 1491 'purpose' is the same as used in a 'Call-Info' header field (as 1492 specified in Section 4.1, and in Section 4.1). The same XML 1493 structure as would be contained in the corresponding MIME type body 1494 part is placed inside the 'EmergencyCallDataValue' element. 1496 For example: 1498 1500 1501 1503 1505 This is an example text. 1506 1507 1508 1509 1511 Test 1512 NENA 1513 Access Infrastructure Provider 1514 1515 sip:15555550987@burf.example.com;user=phone 1516 1517 1518 1520 Example Provided-By by Value. 1522 4.4. The Content-Disposition Parameter 1524 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1525 It updates and clarifies handling originally defined in RFC 3261 1526 [RFC3261] based on implementation experience. While RFC 3261 did not 1527 mandate support for 'multipart' message bodies, 'multipart/mixed' 1528 MIME bodies are used by many extensions (including this document) 1529 today. For example, adding a PIDF-LO, SDP, and additional data in 1530 body of a SIP message requires a 'multipart' message body. 1532 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1533 parameter for the Content-Disposition header field. These RFCs 1534 describe how a UAS reacts if it receives a message body whose content 1535 type or disposition type it does not understand. If the 'handling' 1536 parameter has the value "optional", the UAS ignores the message body. 1537 If the 'handling' parameter has the value "required", the UAS returns 1538 a 415 (Unsupported Media Type) response. The 'by-reference' 1539 disposition type allows a SIP message to contain a reference to the 1540 body part, and the SIP UA processes the body part according to the 1541 reference. This is the case for the Call-info header containing a 1542 Content Indirection (CID) URL. 1544 As an example, a SIP message indicates the Content-Disposition 1545 parameter in the body of the SIP message as shown in Figure 10. 1547 Content-Type: application/sdp 1549 ...Omit Content-Disposition here; defaults are ok 1550 ...SDP goes in here 1552 --boundary1 1554 Content-Type: application/pidf+xml 1555 Content-ID: 1556 Content-Disposition: by-reference;handling=optional 1558 ...PIDF-LO goes in here 1560 --boundary1-- 1562 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1563 Content-ID: <1234567890@atlanta.example.com> 1564 Content-Disposition: by-reference; handling=optional 1566 ...Data provider information data goes in here 1568 --boundary1-- 1570 Figure 10: Example for use of the Content-Disposition Parameter in 1571 SIP. 1573 5. Examples 1575 This section illustrates a longer and more complex example, as shown 1576 in Figure 11. In this example additional data is added by the end 1577 device, included by the VoIP provider (via the PIDF-LO), and provided 1578 by the access network provider. 1580 [================] (1) [================] 1581 [ O +----+ ] Emergency Call [ ] 1582 [ /|\ | UA |-------------------------------> ] 1583 [ | +----+ ] +Device Info [ ] 1584 [ / \ ] +Data Provider Info [ ] 1585 [ ] +Location URI [ ] 1586 [ Access Network ] [ ] 1587 [ Provider ] [ VoIP Provider ] 1588 [ ] [ example.org ] 1589 [ ^ ] [ ] 1590 [=======.========] [============|===] 1591 . | 1592 . | 1593 . [================] | 1594 . [ ] (2) | 1595 . (3) [ <--------------+ 1596 ....................> PSAP ] Emergency Call 1597 Location [ ] +Device Info 1598 +Owner/Subscriber Info [ ] +Data Provider Info #2 1599 +Device Info [ ] +Location URI 1600 +Data Provider Info #3 [================] 1602 Legend: 1604 --- Emergency Call Setup Procedure 1605 ... Location Retrieval/Response 1607 Figure 11: Additional Data Example Flow 1609 The example scenario starts with the end device itself adding device 1610 information, owner/subscriber information, a location URI, and data 1611 provider information to the outgoing emergency call setup message 1612 (see step #1 in Figure 11). The SIP INVITE example is shown in 1613 Figure 12. 1615 INVITE urn:service:sos SIP/2.0 1616 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1617 Max-Forwards: 70 1618 To: 1619 From: Hannes Tschofenig ;tag=9fxced76sl 1620 Call-ID: 3848276298220188511@example.com 1621 Call-Info: ;purpose=icon, 1622 ;purpose=info, 1623 1624 ;purpose=EmergencyCallData.ProviderInfo, 1625 1626 ;purpose=EmergencyCallData.DeviceInfo 1627 Geolocation: 1628 Geolocation-Routing: yes 1629 Accept: application/sdp, application/pidf+xml, 1630 application/EmergencyCallData.ProviderInfo+xml 1631 CSeq: 31862 INVITE 1632 Contact: 1633 Content-Type: multipart/mixed; boundary=boundary1 1635 Content-Length: ... 1637 --boundary1 1639 Content-Type: application/sdp 1641 ...SDP goes here 1643 --boundary1-- 1645 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1646 Content-ID: <0123456789@atlanta.example.com> 1647 Content-Disposition: by-reference;handling=optional 1648 1650 1653 string0987654321@example.org 1654 1655 SoftPhn 1656 00-0d-4b-30-72-df 1658 1660 --boundary1-- 1662 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1663 Content-ID: <1234567890@atlanta.example.com> 1664 Content-Disposition: by-reference;handling=optional 1665 1666 1669 12345 1670 string0987654321@example.org 1671 1672 Hannes Tschofenig 1673 1674 Other 1675 sip:hannes@example.com 1676 EN 1677 1679 1680 Hannes Tschofenig 1681 1682 Hannes 1683 Tschofenig 1684 1685 1686 Dipl. Ing. 1687 1688 --0203 1689 1690 20090808T1430-0500 1691 1692 M 1693 1694 1 1695 1696 de 1697 1698 1699 2 1700 1701 en 1702 1703 1704 1705 work 1706 1710 1711 1712 1713 Linnoitustie 6 1714 Espoo 1715 Uusimaa 1716 02600 1717 Finland 1718 1719 1720 1721 1722 work 1723 voice 1724 1725 1726 tel:+358 50 4871445 1727 1728 1729 work 1730 1731 hannes.tschofenig@nsn.com 1732 1733 1734 work 1735 1736 geo:60.210796,24.812924 1737 1738 1739 1740 home 1741 1742 https://www.example.com/key.asc 1743 1744 1745 Finland/Helsinki 1746 1747 home 1748 1749 http://example.com/hannes.tschofenig 1750 1751 1752 1753 1754 --boundary1-- 1756 Figure 12: End Device sending SIP INVITE with Additional Data. 1758 In this example, information available to the access network operator 1759 is included in the call setup message only indirectly via the use of 1760 the location reference. The PSAP has to retrieve it via a separate 1761 look-up step. Since the access network provider and the VoIP service 1762 provider are two independent entities in this scenario, the access 1763 network operator is not involved in application layer exchanges; the 1764 SIP INVITE transits the access network transparently, as illustrated 1765 in step #1. No change to the SIP INVITE is applied. 1767 When the VoIP service provider receives the message and determines 1768 based on the Service URN that the incoming request is an emergency 1769 call. It performs the typical emergency services related tasks, 1770 including location-based routing, and adds additional data, namely 1771 service and subscriber information, to the outgoing message. For the 1772 example we assume a VoIP service provider that deploys a back-to-back 1773 user agent allowing additional data to be included in the body of the 1774 SIP message (rather than per reference in the header), which allows 1775 us to illustrate the use of multiple data provider info blocks. The 1776 resulting message is shown in Figure 13. 1778 INVITE sips:psap@example.org SIP/2.0 1779 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1780 Max-Forwards: 70 1781 To: 1782 From: Hannes Tschofenig ;tag=9fxced76sl 1783 Call-ID: 3848276298220188511@example.com 1784 Call-Info: ;purpose=icon, 1785 ;purpose=info, 1786 1787 ;purpose=EmergencyCallData.ProviderInfo 1788 1789 ;purpose=EmergencyCallData.DeviceInfo 1790 Call-Info: 1791 ;purpose=EmergencyCallData.ServiceInfo 1792 Call-Info: 1793 ;purpose=EmergencyCallData.ProviderInfo 1794 Geolocation: 1795 Geolocation-Routing: yes 1796 Accept: application/sdp, application/pidf+xml, 1797 application/EmergencyCallData.ProviderInfo+xml 1798 CSeq: 31862 INVITE 1799 Contact: 1800 Content-Type: multipart/mixed; boundary=boundary1 1802 Content-Length: ... 1804 --boundary1 1806 Content-Type: application/sdp 1807 ...SDP goes here 1809 --boundary1-- 1811 Content-Type: application/EmergencyCallData.DeviceInfo+xml 1812 Content-ID: <0123456789@atlanta.example.com> 1813 Content-Disposition: by-reference;handling=optional 1814 1816 1819 string0987654321@example.org 1820 1821 SoftPhn 1822 00-0d-4b-30-72-df 1824 1826 --boundary1-- 1828 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1829 Content-ID: <1234567890@atlanta.example.com> 1830 Content-Disposition: by-reference;handling=optional 1831 1832 1835 string0987654321@example.org 1836 1837 Hannes Tschofenig 1838 1839 Other 1840 sip:hannes@example.com 1841 EN 1842 1844 1845 Hannes Tschofenig 1846 1847 Hannes 1848 Tschofenig 1849 1850 1851 Dipl. Ing. 1852 1853 --0203 1854 1855 20090808T1430-0500 1856 1857 M 1858 1859 1 1860 1861 de 1862 1863 1864 2 1865 1866 en 1867 1868 1869 1870 work 1871 1875 1876 1877 1878 Linnoitustie 6 1879 Espoo 1880 Uusimaa 1881 02600 1882 Finland 1883 1884 1885 1886 1887 work 1888 voice 1889 1890 1891 tel:+358 50 4871445 1892 1893 1894 work 1895 1896 hannes.tschofenig@nsn.com 1897 1898 1899 work 1900 1901 geo:60.210796,24.812924 1902 1903 1904 1905 home 1906 1907 https://www.example.com/key.asc 1908 1909 1910 Finland/Helsinki 1911 1912 home 1913 1914 http://example.com/hannes.tschofenig 1915 1916 1917 1918 1920 --boundary1-- 1922 Content-Type: application/EmergencyCallData.ServiceInfo+xml 1923 Content-ID: 1924 Content-Disposition: by-reference;handling=optional 1925 1926 1929 string0987654321@example.org 1930 1931 Residence 1932 VOIP 1933 Unknown 1934 1936 --boundary1-- 1938 Content-Type: application/EmergencyCallData.ProviderInfo+xml 1939 Content-ID: 1940 Content-Disposition: by-reference;handling=optional 1941 1942 1945 string0987654321@example.org 1946 1947 Example VoIP Provider 1948 1949 urn:nena:companyid:ID123 1950 NENA 1951 Service Provider 1952 sip:voip-provider@example.com 1953 EN 1954 1956 1957 John Doe 1958 1959 John 1960 Doe 1961 1962 1963 1964 1965 --0203 1966 1967 20090808T1430-0500 1968 1969 M 1970 1971 1 1972 1973 en 1974 1975 1976 work 1977 1978 Example VoIP Provider 1979 1980 1981 1982 work 1983 1986 1987 1988 1989 Downing Street 10 1990 London 1991 1992 SW1A 2AA 1993 UK 1994 1995 1996 1997 1998 work 1999 voice 2000 2001 2002 sips:john.doe@example.com 2003 2004 2005 work 2006 2007 john.doe@example.com 2008 2009 2010 work 2011 2012 geo:51.503396, 0.127640 2013 2014 Europe/London 2015 2016 home 2017 2018 http://www.example.com/john.doe 2019 2020 2021 2022 2024 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 2026 Finally, the PSAP requests location information from the access 2027 network operator. The response is shown in Figure 14. Along with 2028 the location information additional data is provided in the 2029 element of the PIDF-LO. 2031 2032 2037 2038 2039 2040 2042 AU 2043 NSW 2044 Wollongong 2045 North Wollongong 2046 Flinders 2047 Street 2048 Campbell Street 2049 Gilligan's Island 2050 Corner 2051 Video Rental Store 2052 2500 2053 Westerns and Classics 2054 store 2055 Private Box 15 2056 2057 2058 2059 true 2060 2061 2013-12-10T20:00:00Z 2062 2063 2064 802.11 2066 2069 2072 2073 2075 string0987654321@example.org 2076 2077 University of California, Irvine 2078 2079 urn:nena:companyid:uci 2080 NENA 2081 Other 2082 tel:+1 9498245222 2083 EN 2084 2086 2088 string0987654321@example.org 2089 2090 This is an example text. 2091 2093 2095 2096 2097 mac:00-0d-4b-30-72-df 2098 2013-07-09T20:57:29Z 2099 2100 2102 Figure 14: Access Network Provider returning PIDF-LO with Additional 2103 Data. 2105 6. XML Schemas 2107 This section defines the XML schemas of the five data blocks. 2108 Additionally, the Provided-By schema is specified. 2110 6.1. EmergencyCallData.ProviderInfo XML Schema 2112 2113 2123 2126 2128 2129 2130 2131 2132 2134 2138 2141 2142 2143 2144 2145 2146 2148 2149 2150 2153 2156 2159 2162 2165 2168 2171 2175 2178 2181 2183 2184 2186 2188 Figure 15: EmergencyCallData.ProviderInfo XML Schema. 2190 6.2. EmergencyCallData.ServiceInfo XML Schema 2192 2193 2201 2204 2206 2207 2208 2211 2214 2217 2220 2223 2225 2226 2228 2230 Figure 16: EmergencyCallData.ServiceInfo XML Schema. 2232 6.3. EmergencyCallData.DeviceInfo XML Schema 2234 2235 2242 2245 2247 2248 2249 2252 2255 2258 2261 2263 2264 2265 2266 2269 2270 2271 2272 2274 2277 2280 2282 2283 2285 2287 Figure 17: EmergencyCallData.DeviceInfo XML Schema. 2289 6.4. EmergencyCallData.SubscriberInfo XML Schema 2291 2292 2301 2304 2306 2308 2309 2310 2311 2314 2317 2319 2320 2321 2322 2324 2326 Figure 18: EmergencyCallData.SubscriberInfo XML Schema. 2328 6.5. EmergencyCallData.Comment XML Schema 2330 2331 2339 2342 2344 2345 2346 2349 2353 2355 2356 2358 2359 2360 2361 2362 2363 2364 2366 2368 Figure 19: EmergencyCallData.Comment XML Schema. 2370 6.6. Provided-By XML Schema 2372 This section defines the Provided-By schema. 2374 2375 2388 2389 2390 2391 2392 2394 2396 2397 2398 2401 2405 2409 2412 2414 2416 2417 2418 2419 2420 2421 2423 2424 2426 2428 2429 2430 2432 2434 2435 2436 2439 2442 2445 2448 2452 2455 2456 2458 2460 Figure 20: Provided-By XML Schema. 2462 7. Security Considerations 2463 The information in this data structure will usually be considered 2464 private. HTTPS is specified to require the provider of the 2465 information to validate the credentials of the requester. While the 2466 creation of a public key infrastructure (PKI) that has global scope 2467 may be difficult, the alternatives to creating devices and services 2468 that can provide critical information securely are more daunting. 2469 The provider may enforce any policy it wishes to use, but PSAPs and 2470 responder agencies should deploy a PKI so that providers of 2471 additional data can check the certificate of the client and decide 2472 the appropriate policy to enforce based on that certificate. 2474 Ideally, the PSAP and emergency responders will be given credentials 2475 signed by an authority trusted by the data provider. In most 2476 circumstances, nationally recognized credentials would be sufficient, 2477 and if the emergency services arranges a PKI, data providers could be 2478 provisioned with the root CA public key for a given nation. Some 2479 nations are developing a PKI for this, and related, purposes. Since 2480 calls could be made from devices where the device and/or the service 2481 provider(s) are not local to the emergency authorities, globally 2482 recognized credentials are useful. This might be accomplished by 2483 extending the notion of the "forest guide" described in [RFC5222] to 2484 allow the forest guide to provide the credential of the PKI root for 2485 areas that it has coverage information for, but standards for such a 2486 mechanism are not yet available. In its absence, the data provider 2487 will need to obtain the root CA credentials for any areas it is 2488 willing to provide additional data by out of band means. With the 2489 credential of the root CA for a national emergency services PKI, the 2490 data provider server can validate the credentials of an entity 2491 requesting additional data by reference. 2493 The data provider also needs a credential that can be verified by the 2494 emergency services to know that it is receiving data from the right 2495 server. The emergency authorities could provide credentials, 2496 distinguishable from credentials it provides to emergency responders 2497 and PSAPs, which could be used to validate data providers. Such 2498 credentials would have to be acceptable to any PSAP or responder that 2499 could receive a call with additional data supplied by that provider. 2500 This would be extensible to global credential validation using the 2501 forest guide as above. In the absence of such credentials, the 2502 emergency authorities could maintain a list of local data providers' 2503 credentials provided to it out of band. At a minimum, the emergency 2504 authorities could obtain a credential from the DNS entry of the 2505 domain in the Additional Data URI to at least validate that the 2506 server is known to the domain providing the URI. 2508 Data provided by devices by reference have similar credential 2509 validation issues to service providers, and the solutions are the 2510 same. 2512 8. Privacy Considerations 2514 This document enables functionality for conveying additional 2515 information about the caller to the callee. Some of this information 2516 is personal data and therefore privacy concerns arise. An explicit 2517 privacy indicator for information directly relating to the callers 2518 identity is defined and use is mandatory. However, observance of 2519 this request for privacy and what information it relates to is 2520 controlled by the destination jurisdiction. 2522 There are a number of privacy concerns with regular real-time 2523 communication services that are also applicable to emergency calling. 2524 Data protection regulation world-wide has, however, decided to create 2525 exceptions for emergency services since the drawbacks of disclosing 2526 personal data in comparison to the benefit for the emergency caller 2527 are often towards the latter. Hence, the data protection rights of 2528 individuals are often waived for emergency situations. There are, 2529 however, still various countries that offer some degree of anonymity 2530 for the caller towards PSAP call takers. 2532 The functionality defined in this document, however, far exceeds the 2533 amount of information sharing found in the Plain old telephone system 2534 (POTS). For this reason there are additional privacy threats to 2535 consider, which are described in more detail in [RFC6973]. 2537 Stored Data Compromise: First, there is an increased risk of stored 2538 data compromise since additional data is collected and stored in 2539 databases. Without adequate measures to secure stored data from 2540 unauthorized or inappropriate access at access network operators, 2541 service providers, end devices, as well as PSAPs individuals are 2542 exposed to potential financial, reputational, or physical harm. 2544 Misattribution: If the personal data collected and conveyed is 2545 incorrect or inaccurate then this may lead to misattribution. 2546 Misattribution occurs when data or communications related to one 2547 individual are attributed to another. 2549 Identification: By the nature of the additional data and its 2550 capability to provide much richer information about the caller, 2551 the call, and the location the calling party is identified in a 2552 much better way. Some users may feel uncomfortable with this 2553 degree of information sharing even in emergency services 2554 situations. 2556 Secondary Use: Furthermore, there is the risk of secondary use. 2557 Secondary use is the use of collected information about an 2558 individual without the individual's consent for a purpose 2559 different from that for which the information was collected. The 2560 stated purpose of the additional data is for emergency services 2561 purposes but theoretically the same information could be used for 2562 any other call as well. Additionally, parties involved in the 2563 emergency call may retain the obtained information and may re-use 2564 it for other, non-emergency services purposes. 2566 Disclosure: When the data defined in this document is not properly 2567 security (while in transit with traditional communication security 2568 techniques, and while at rest using access control mechanisms) 2569 there is the risk of disclosure, which is the revelation of 2570 information about an individual that affects the way others judge 2571 the individual. 2573 To mitigate these privacy risks the following countermeasures can be 2574 taken. 2576 In regions where callers can elect to suppress certain personally 2577 identifying information, the network or PSAP functionality can 2578 inspect privacy flags within the SIP headers to determine what 2579 information may be passed, stored, or displayed to comply with local 2580 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2581 The presence of this privacy type in a Privacy header field indicates 2582 that the user would like the network asserted identity to be kept 2583 private with respect to SIP entities outside the trust domain with 2584 which the user authenticated, including the PSAP. 2586 This document defines various data structures that constitutes 2587 personal data. Local regulations may govern what data must be 2588 provided in emergency calls, but in general, the emergency call 2589 system is often aided by the kinds of information described in this 2590 document. There is a tradeoff between the privacy considerations and 2591 the utility of the data. For adequate protection this specification 2592 requires all data exchanges to be secured via communication security 2593 techniques (namely TLS) against eavesdropping and inception. 2594 Furthermore, security safeguards are required to prevent unauthorized 2595 access to data at rest. Various security incidents over the last 10 2596 years have shown data breaches are not not uncommon and are often 2597 caused by lack of proper access control frameworks, software bugs 2598 (buffer overflows), or missing input parsing (SQL injection attacks). 2599 The risks of data breaches is increased with the obligation for 2600 emergency services to retain emergency call related data for extended 2601 periods, e.g., several years are the norm. 2603 Finally, it is also worth to highlight the nature of the SIP 2604 communication architecture, which introduces additional complications 2605 for privacy. Some forms of data can be sent by value in the SIP 2606 signaling or by value (URL in SIP signaling). When data is sent by 2607 value, all intermediaries have access to the data. As such, these 2608 intermediaries may also introduce additional privacy risk. 2609 Therefore, in situations where the conveyed information raises 2610 privacy concerns and intermediaries are involved transmitting a 2611 reference is more appropriate (assuming proper access control 2612 policies are available for distinguishing the different entities 2613 dereferencing the reference). Without access control policies any 2614 party in possession of the reference is able to resolve the reference 2615 and to obtain the data, including intermediaries. 2617 9. IANA Considerations 2619 9.1. Registry creation 2621 This document creates a new registry called 'Emergency Call 2622 Additional Data'. The following sub-registries are created for this 2623 registry. 2625 9.1.1. Provider ID Series Registry 2627 This document creates a new sub-registry called 'Additional Call Data 2628 Provider ID Series'. As defined in [RFC5226], this registry operates 2629 under "Expert Review" rules. The expert should determine that the 2630 entity requesting a new value is a legitimate issuer of service 2631 provider IDs suitable for use in Additional Call Data. 2633 The content of this registry includes: 2635 Name: The identifier which will be used in the ProviderIDSeries 2636 element 2638 Source: The full name of the organization issuing the identifiers 2640 URL: A URL to the organization for further information 2642 The initial set of values is listed in Figure 21. 2644 +-----------+--------------------------+----------------------+ 2645 | Name | Source | URL | 2646 +-----------+--------------------------+----------------------+ 2647 | NENA | National Emergency | http://www.nena.org | 2648 | | Number Association | | 2649 | EENA | European Emergency | http://www.eena.org | 2650 | | Number Association | | 2651 +-----------+--------------------------+----------------------+ 2653 Figure 21: Provider ID Series Registry. 2655 9.1.2. Service Environment Registry 2657 This document creates a new sub-registry called 'Additional Call 2658 Service Environment'. As defined in [RFC5226], this registry 2659 operates under "Expert Review" rules. The expert should determine 2660 that the entity requesting a new value is relevant for this service 2661 element. 2663 The content of this registry includes: 2665 Token: The value to be used in element. 2667 Description: A short description of the token. 2669 The initial set of values is listed in Figure 22. 2671 +-----------+--------------------------+ 2672 | Token | Description | 2673 +-----------+--------------------------+ 2674 | Business | [[This RFC]] | 2675 | Residence | [[This RFC]] | 2676 +-----------+--------------------------+ 2678 Figure 22: Service Environment Registry. 2680 9.1.3. Service Provider Type Registry 2682 This document creates a new sub-registry called 'Service Provider 2683 Type'. As defined in [RFC5226], this registry operates under "Expert 2684 Review". The expert should determine that the proposed new value is 2685 distinct from existing values and appropriate for use in the 2686 TypeOfServicerProvider element 2688 The content of this registry includes: 2690 Name: The value to be used in TypeOfServiceProvider. 2692 Description: A short description of the type of service provider 2694 The initial set of values is defined in Figure 1. 2696 9.1.4. Service Delivered Registry 2698 This document creates a new sub-registry called 'Service Delivered'. 2699 As defined in [RFC5226], this registry operates under "Expert Review" 2700 rules. The expert should consider whether the proposed service is 2701 unique from existing services and the definition of the service will 2702 be clear to implementors and PSAPS/responders. 2704 The content of this registry includes: 2706 Name: Enumeration token of the service. 2708 Description: Short description identifying the service. 2710 The initial set of values are defined in Figure 3. 2712 9.1.5. Device Classification Registry 2714 This document creates a new sub-registry called 'Device 2715 Classification'. As defined in [RFC5226], this registry operates 2716 under "Expert Review" rules. The expert should consider whether the 2717 proposed class is unique from existing classes and the definition of 2718 the class will be clear to implementors and PSAPS/responders. 2720 The content of this registry includes: 2722 Name: Enumeration token of the device classification. 2724 Description: Short description identifying the device type. 2726 The initial set of values are defined in Figure 5. 2728 9.1.6. Device ID Type Type Registry 2730 This document creates a new sub-registry called 'Additional Call Data 2731 Device ID Type'. As defined in [RFC5226], this registry operates 2732 under "Expert Review" rules. The expert should ascertain that the 2733 proposed type is well understood, and provides the information useful 2734 to PSAPs and responders to uniquely identify a device. 2736 The content of this registry includes: 2738 Name: Enumeration token of the device id type. 2740 Description: Short description identifying type of device id. 2742 The initial set of values are defined in Figure 6. 2744 9.1.7. Device/Service Data Type Registry 2746 This document creates a new sub-registry called 'Device/Service Data 2747 Type Registry'. As defined in [RFC5226], this registry operates 2748 under "Expert Review" and "Specification Required" rules. The expert 2749 should ascertain that the proposed type is well understood, and 2750 provides information useful to PSAPs and responders. The 2751 specification must contain a complete description of the data, and a 2752 precise format specification suitable to allow interoperable 2753 implementations. 2755 The content of this registry includes: 2757 Name: Enumeration token of the data type. 2759 Description: Short description identifying the the data. 2761 Specification: Citation for the specification of the data. 2763 The initial set of values are listed in Figure 23. 2765 +---------+----------------------------------------+----------------+ 2766 | Token | Description | Specification | 2767 +---------+----------------------------------------+----------------+ 2768 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2769 +---------+----------------------------------------+----------------+ 2770 | VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS | 2771 +---------+----------------------------------------+----------------+ 2773 Figure 23: Device/Service Data Type Registry. 2775 9.1.8. Additional Data Blocks Registry 2777 This document creates a new sub-registry called 'Additional Data 2778 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2779 As defined in [RFC5226], this registry operates under "Expert Review" 2780 and "Specification Required" rules. The expert is responsible for 2781 verifying that the document contains a complete and clear 2782 specification and the proposed functionality does not obviously 2783 duplicate existing functionality. 2785 The content of this registry includes: 2787 Name: Element Name of enclosing block. 2789 Reference: The document that describes the block 2791 The initial set of values are listed in Figure 24. 2793 +--------------+------------+ 2794 | Token | Reference | 2795 +--------------+------------+ 2796 | ProviderInfo | [This RFC] | 2797 | ServiceInfo | [This RFC] | 2798 | DeviceInfo | [This RFC] | 2799 | Subscriber | [This RFC] | 2800 | Comment | [This RFC] | 2801 +--------------+------------+ 2803 Figure 24: Additional Data Blocks Registry. 2805 9.2. 'EmergencyCallData' Purpose Parameter Value 2807 This document defines the 'EmergencyCallData' value for the "purpose" 2808 parameter of the Call-Info header field. The Call-Info header and 2809 the corresponding registry for the 'purpose' parameter was 2810 established with RFC 3261 [RFC3261]. 2812 Header Parameter New 2813 Field Name Value Reference 2814 ---------- --------- ----------------- --------- 2815 Call-Info purpose EmergencyCallData [This RFC] 2817 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2819 This section registers the namespace specified in Section 9.5.1 in 2820 the provided-by registry established by RFC 4119, for usage within 2821 the element of a PIDF-LO. 2823 The schema for the provided-by schema used by this document is 2824 specified in Section 6.6. 2826 9.4. MIME Registrations 2828 9.4.1. MIME Content-type Registration for 'application/ 2829 EmergencyCallData.ProviderInfo+xml' 2831 This specification requests the registration of a new MIME type 2832 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2833 RFC 3023 [RFC3023]. 2835 MIME media type name: application 2837 MIME subtype name: EmergencyCallData.ProviderInfo+xml 2839 Mandatory parameters: none 2841 Optional parameters: charset Indicates the character encoding of 2842 enclosed XML. 2844 Encoding considerations: Uses XML, which can employ 8-bit 2845 characters, depending on the character encoding used. See 2846 Section 3.2 of RFC 3023 [RFC3023]. 2848 Security considerations: This content type is designed to carry 2849 the data provider information, which is a sub-category of 2850 additional data about an emergency call. Since this data contains 2851 personal information appropriate precautions have to be taken to 2852 limit unauthorized access, inappropriate disclosure to third 2853 parties, and eavesdropping of this information. Please refer to 2854 Section 7 and Section 8 for more information. 2856 Interoperability considerations: None 2858 Published specification: [TBD: This specification] 2860 Applications which use this media type: Emergency Services 2862 Additional information: Magic Number: None File Extension: .xml 2863 Macintosh file type code: 'TEXT' 2865 Person and email address for further information: Hannes 2866 Tschofenig, Hannes.Tschofenig@gmx.net 2868 Intended usage: LIMITED USE 2870 Author: This specification is a work item of the IETF ECRIT 2871 working group, with mailing list address . 2873 Change controller: The IESG 2875 9.4.2. MIME Content-type Registration for 'application/ 2876 EmergencyCallData.ServiceInfo+xml' 2878 This specification requests the registration of a new MIME type 2879 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2880 RFC 3023 [RFC3023]. 2882 MIME media type name: application 2884 MIME subtype name: EmergencyCallData.ServiceInfo+xml 2886 Mandatory parameters: none 2888 Optional parameters: charset Indicates the character encoding of 2889 enclosed XML. 2891 Encoding considerations: Uses XML, which can employ 8-bit 2892 characters, depending on the character encoding used. See 2893 Section 3.2 of RFC 3023 [RFC3023]. 2895 Security considerations: This content type is designed to carry 2896 the service information, which is a sub-category of additional 2897 data about an emergency call. Since this data contains personal 2898 information appropriate precautions have to be taken to limit 2899 unauthorized access, inappropriate disclosure to third parties, 2900 and eavesdropping of this information. Please refer to Section 7 2901 and Section 8 for more information. 2903 Interoperability considerations: None 2905 Published specification: [TBD: This specification] 2907 Applications which use this media type: Emergency Services 2909 Additional information: Magic Number: None File Extension: .xml 2910 Macintosh file type code: 'TEXT' 2912 Person and email address for further information: Hannes 2913 Tschofenig, Hannes.Tschofenig@gmx.net 2915 Intended usage: LIMITED USE 2917 Author: This specification is a work item of the IETF ECRIT 2918 working group, with mailing list address . 2920 Change controller: The IESG 2922 9.4.3. MIME Content-type Registration for 'application/ 2923 EmergencyCallData.DeviceInfo+xml' 2925 This specification requests the registration of a new MIME type 2926 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2927 RFC 3023 [RFC3023]. 2929 MIME media type name: application 2931 MIME subtype name: EmergencyCallData.DeviceInfo+xml 2933 Mandatory parameters: none 2935 Optional parameters: charset Indicates the character encoding of 2936 enclosed XML. 2938 Encoding considerations: Uses XML, which can employ 8-bit 2939 characters, depending on the character encoding used. See 2940 Section 3.2 of RFC 3023 [RFC3023]. 2942 Security considerations: This content type is designed to carry 2943 the device information information, which is a sub-category of 2944 additional data about an emergency call. Since this data contains 2945 personal information appropriate precautions have to be taken to 2946 limit unauthorized access, inappropriate disclosure to third 2947 parties, and eavesdropping of this information. Please refer to 2948 Section 7 and Section 8 for more information. 2950 Interoperability considerations: None 2952 Published specification: [TBD: This specification] 2954 Applications which use this media type: Emergency Services 2956 Additional information: Magic Number: None File Extension: .xml 2957 Macintosh file type code: 'TEXT' 2959 Person and email address for further information: Hannes 2960 Tschofenig, Hannes.Tschofenig@gmx.net 2962 Intended usage: LIMITED USE 2964 Author: This specification is a work item of the IETF ECRIT 2965 working group, with mailing list address . 2967 Change controller: The IESG 2969 9.4.4. MIME Content-type Registration for 'application/ 2970 EmergencyCallData.SubscriberInfo+xml' 2972 This specification requests the registration of a new MIME type 2973 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2974 RFC 3023 [RFC3023]. 2976 MIME media type name: application 2978 MIME subtype name: EmergencyCallData.SubscriberInfo+xml 2980 Mandatory parameters: none 2982 Optional parameters: charset Indicates the character encoding of 2983 enclosed XML. 2985 Encoding considerations: Uses XML, which can employ 8-bit 2986 characters, depending on the character encoding used. See 2987 Section 3.2 of RFC 3023 [RFC3023]. 2989 Security considerations: This content type is designed to carry 2990 owner/subscriber information, which is a sub-category of 2991 additional data about an emergency call. Since this data contains 2992 personal information appropriate precautions have to be taken to 2993 limit unauthorized access, inappropriate disclosure to third 2994 parties, and eavesdropping of this information. Please refer to 2995 Section 7 and Section 8 for more information. 2997 Interoperability considerations: None 2999 Published specification: [TBD: This specification] 3001 Applications which use this media type: Emergency Services 3003 Additional information: Magic Number: None File Extension: .xml 3004 Macintosh file type code: 'TEXT' 3006 Person and email address for further information: Hannes 3007 Tschofenig, Hannes.Tschofenig@gmx.net 3009 Intended usage: LIMITED USE 3011 Author: This specification is a work item of the IETF ECRIT 3012 working group, with mailing list address . 3014 Change controller: The IESG 3016 9.4.5. MIME Content-type Registration for 'application/ 3017 EmergencyCallData.Comment+xml' 3019 This specification requests the registration of a new MIME type 3020 according to the procedures of RFC 4288 [RFC4288] and guidelines in 3021 RFC 3023 [RFC3023]. 3023 MIME media type name: application 3025 MIME subtype name: EmergencyCallData.Comment+xml 3027 Mandatory parameters: none 3029 Optional parameters: charset Indicates the character encoding of 3030 enclosed XML. 3032 Encoding considerations: Uses XML, which can employ 8-bit 3033 characters, depending on the character encoding used. See 3034 Section 3.2 of RFC 3023 [RFC3023]. 3036 Security considerations: This content type is designed to carry a 3037 comment, which is a sub-category of additional data about an 3038 emergency call. This data may contain personal information. 3039 Appropriate precautions may have to be taken to limit unauthorized 3040 access, inappropriate disclosure to third parties, and 3041 eavesdropping of this information. Please refer to Section 7 and 3042 Section 8 for more information. 3044 Interoperability considerations: None 3046 Published specification: [TBD: This specification] 3048 Applications which use this media type: Emergency Services 3050 Additional information: Magic Number: None File Extension: .xml 3051 Macintosh file type code: 'TEXT' 3053 Person and email address for further information: Hannes 3054 Tschofenig, Hannes.Tschofenig@gmx.net 3056 Intended usage: LIMITED USE 3058 Author: This specification is a work item of the IETF ECRIT 3059 working group, with mailing list address . 3061 Change controller: The IESG 3063 9.5. URN Sub-Namespace Registration 3065 9.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 3067 This section registers a new XML namespace, as per the guidelines in 3068 RFC 3688 [RFC3688]. 3070 URI: urn:ietf:params:xml:ns:EmergencyCallData 3072 Registrant Contact: IETF, ECRIT working group, , as 3073 delegated by the IESG . 3075 XML: 3077 BEGIN 3078 3079 3081 3082 3083 3085 Namespace for Additional Emergency Call Data 3086 3087 3088

Namespace for Additional Data related to an Emergency Call

3089

See [TBD: This document].

3090 3091 3092 END 3094 9.5.2. Registration for 3095 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3097 This section registers a new XML namespace, as per the guidelines in 3098 RFC 3688 [RFC3688]. 3100 URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 3102 Registrant Contact: IETF, ECRIT working group, , as 3103 delegated by the IESG . 3105 XML: 3107 BEGIN 3108 3109 3111 3112 3113 3115 Namespace for Additional Emergency Call Data: 3116 Data Provider Information 3117 3118 3119

Namespace for Additional Data related to an Emergency Call

3120

Data Provider Information

3121

See [TBD: This document].

3122 3123 3124 END 3126 9.5.3. Registration for 3127 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3129 This section registers a new XML namespace, as per the guidelines in 3130 RFC 3688 [RFC3688]. 3132 URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 3134 Registrant Contact: IETF, ECRIT working group, , as 3135 delegated by the IESG . 3137 XML: 3139 BEGIN 3140 3141 3143 3144 3145 3147 Namespace for Additional Emergency Call Data: 3148 Service Information 3149 3150 3151

Namespace for Additional Data related to an Emergency Call

3152

Service Information

3154

See [TBD: This document].

3155 3156 3157 END 3159 9.5.4. Registration for 3160 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3162 This section registers a new XML namespace, as per the guidelines in 3163 RFC 3688 [RFC3688]. 3165 URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 3167 Registrant Contact: IETF, ECRIT working group, , as 3168 delegated by the IESG . 3170 XML: 3172 BEGIN 3173 3174 3176 3177 3178 3180 Namespace for Additional Emergency Call Data: 3181 Device Information 3182 3183 3184

Namespace for Additional Data related to an Emergency Call

3185

Device Information

3186

See [TBD: This document].

3187 3188 3189 END 3191 9.5.5. Registration for 3192 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3194 This section registers a new XML namespace, as per the guidelines in 3195 RFC 3688 [RFC3688]. 3197 URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 3198 Registrant Contact: IETF, ECRIT working group, , as 3199 delegated by the IESG . 3201 XML: 3203 BEGIN 3204 3205 3207 3208 3209 3211 Namespace for Additional Emergency Call Data: 3212 Owner/Subscriber Information 3213 3214 3215

Namespace for Additional Data related to an Emergency Call

3216

Owner/Subscriber Information

3217

See [TBD: This document].

3218 3219 3220 END 3222 9.5.6. Registration for 3223 urn:ietf:params:xml:ns:EmergencyCallData:Comment 3225 This section registers a new XML namespace, as per the guidelines in 3226 RFC 3688 [RFC3688]. 3228 URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment 3230 Registrant Contact: IETF, ECRIT working group, , as 3231 delegated by the IESG . 3233 XML: 3235 BEGIN 3236 3237 3239 3240 3241 3244 Namespace for Additional Emergency Call Data:Comment 3245 3246 3247

Namespace for Additional Data related to an Emergency Call

3248

Comment

3249

See [TBD: This document].

3250 3251 3252 END 3254 9.6. Schema Registrations 3256 This specification registers five schemas, as per the guidelines in 3257 RFC 3688 [RFC3688]. 3259 URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo 3261 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3262 delegated by the IESG (iesg@ietf.org). 3264 XML: The XML schema can be found in Figure 15. 3266 URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo 3268 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3269 delegated by the IESG (iesg@ietf.org). 3271 XML: The XML schema can be found in Figure 16. 3273 URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo 3275 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3276 delegated by the IESG (iesg@ietf.org). 3278 XML: The XML schema can be found in Figure 17. 3280 URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo 3282 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3283 delegated by the IESG (iesg@ietf.org). 3285 XML: The XML schema can be found in Section 6.4. 3287 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3289 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3290 delegated by the IESG (iesg@ietf.org). 3292 XML: The XML schema can be found in Section 6.5. 3294 9.7. VCard Parameter Value Registration 3296 This document registers a new value in the vCARD Parameter Values 3297 registry as defined by [RFC6350] with the following template: 3299 Value: main 3301 Purpose: The main telephone number, typically of an enterprise, as 3302 opposed to a direct dial number of an individual employee 3304 Conformance: This value can be used with the "TYPE" parameter 3305 applied on the "TEL" property. 3307 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3308 00 3310 10. Acknowledgments 3312 This work was originally started in NENA and has benefitted from a 3313 large number of participants in NENA standardization efforts, 3314 originally in the Long Term Definition Working Group, the Data 3315 Technical Committee and most recently the Additional Data working 3316 group. The authors are grateful for the initial work and extended 3317 comments provided by many NENA participants, including Delaine 3318 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3319 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3320 and Robert (Bob) Sherry. 3322 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3323 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 3324 comments. 3326 11. References 3328 11.1. Normative References 3330 [RFC0822] Crocker, D., "Standard for the format of ARPA Internet 3331 text messages", STD 11, RFC 822, August 1982. 3333 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 3334 Extensions (MIME) Part One: Format of Internet Message 3335 Bodies", RFC 2045, November 1996. 3337 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3338 Requirement Levels", BCP 14, RFC 2119, March 1997. 3340 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3341 Locators", RFC 2392, August 1998. 3343 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 3344 Types", RFC 3023, January 2001. 3346 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3347 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3348 and QSIG Objects", RFC 3204, December 2001. 3350 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3351 A., Peterson, J., Sparks, R., Handley, M., and E. 3352 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3353 June 2002. 3355 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3356 Extensions to the Session Initiation Protocol (SIP) for 3357 Asserted Identity within Trusted Networks", RFC 3325, 3358 November 2002. 3360 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3361 Extensions (MIME) Parameter", RFC 3459, January 2003. 3363 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3364 January 2004. 3366 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3367 Format", RFC 4119, December 2005. 3369 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 3370 Registration Procedures", RFC 4288, December 2005. 3372 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3373 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3374 May 2008. 3376 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3377 Initiation Protocol (SIP)", RFC 5621, September 2009. 3379 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3380 August 2011. 3382 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3383 6351, August 2011. 3385 11.2. Informational References 3387 [I-D.gellens-negotiating-human-language] 3388 Randy, R., "Negotiating Human Language Using SDP", draft- 3389 gellens-negotiating-human-language-02 (work in progress), 3390 February 2013. 3392 [I-D.ietf-ecrit-psap-callback] 3393 Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3394 Patel, "Public Safety Answering Point (PSAP) Callback", 3395 draft-ietf-ecrit-psap-callback-13 (work in progress), 3396 October 2013. 3398 [I-D.ietf-geopriv-relative-location] 3399 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3400 Thomson, "Relative Location Representation", draft-ietf- 3401 geopriv-relative-location-08 (work in progress), September 3402 2013. 3404 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3405 "Indicating User Agent Capabilities in the Session 3406 Initiation Protocol (SIP)", RFC 3840, August 2004. 3408 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3409 Emergency Context Resolution with Internet Technologies", 3410 RFC 5012, January 2008. 3412 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3413 Format for Presence Information Data Format Location 3414 Object (PIDF-LO)", RFC 5139, February 2008. 3416 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 3417 Tschofenig, "LoST: A Location-to-Service Translation 3418 Protocol", RFC 5222, August 2008. 3420 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3421 Presence Information Data Format Location Object (PIDF-LO) 3422 Usage Clarification, Considerations, and Recommendations", 3423 RFC 5491, March 2009. 3425 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3426 Thomson, "Dynamic Extensions to the Presence Information 3427 Data Format Location Object (PIDF-LO)", RFC 5962, 3428 September 2010. 3430 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3431 5985, September 2010. 3433 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3434 "Framework for Emergency Calling Using Internet 3435 Multimedia", RFC 6443, December 2011. 3437 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3438 R. George, "Specifying Civic Address Extensions in the 3439 Presence Information Data Format Location Object (PIDF- 3440 LO)", RFC 6848, January 2013. 3442 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3443 Communications Services in Support of Emergency Calling", 3444 BCP 181, RFC 6881, March 2013. 3446 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3447 Morris, J., Hansen, M., and R. Smith, "Privacy 3448 Considerations for Internet Protocols", RFC 6973, July 3449 2013. 3451 Appendix A. XML Schema for vCard/xCard 3453 This section contains the vCard/xCard XML schema version of the Relax 3454 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3455 XML schemas defined in this document. The schema in RFC 6351 3456 [RFC6351] is the normative source and this section is informative 3457 only. 3459 3460 3464 3470 3471 3472 vCard Format Specification 3473 3474 3475 3476 3477 3478 3479 3480 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3495 3496 3497 3499 3500 3501 3502 3503 3505 3506 3507 3509 3510 3511 3512 3513 3515 3516 3517 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3562 3563 3564 3565 3569 3570 3571 Section 5: Parameters 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3725 3726 3727 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 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 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 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4185 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 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 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334 4335 4336 4337 4338 4339 4340 4341 4342 4343 4344 4345 4346 4347 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367 4368 4369 4370 4371 4372 4373 4374 4375 4376 4377 4378 4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 4391 4392 4393 4394 4395 4396 4397 4398 4399 4400 4401 4402 4403 4404 4405 4406 4407 4408 4409 4410 4411 4412 4413 4414 4415 4416 4417 4418 4419 4420 4421 4422 4423 4424 4425 4426 4427 4428 4429 4430 4431 4432 4433 4434 4435 4436 4437 4438 4439 4440 4441 4442 4443 4444 4445 4446 4447 4448 4449 4451 4452 4453 4454 4455 4456 4457 4458 4459 4460 4461 4462 4463 4464 4465 4466 4467 4468 4469 4470 4471 4472 4473 4474 4475 4476 4477 4478 4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492 4493 4494 4495 4496 4498 4499 4500 4501 4502 4503 4504 4506 4507 4508 4509 4510 4511 4512 4514 4515 4516 4518 4520 4521 4522 4524 4525 4526 4527 4529 Authors' Addresses 4531 Brian Rosen 4532 NeuStar 4533 470 Conrad Dr. 4534 Mars, PA 16046 4535 US 4537 Phone: +1 724 382 1051 4538 Email: br@brianrosen.net 4539 Hannes Tschofenig 4540 Nokia Solutions and Networks 4541 Linnoitustie 6 4542 Espoo 02600 4543 Finland 4545 Phone: +358 (50) 4871445 4546 Email: Hannes.Tschofenig@gmx.net 4547 URI: http://www.tschofenig.priv.at 4549 Roger Marshall 4550 TeleCommunication Systems, Inc. 4551 2401 Elliott Avenue 4552 Seattle, WA 98121 4553 US 4555 Phone: +1 206 792 2424 4556 Email: rmarshall@telecomsys.com 4557 URI: http://www.telecomsys.com 4559 Randall Gellens 4560 Qualcomm Technologies, Inc. 4561 5775 Morehouse Drive 4562 San Diego, CA 92121 4563 US 4565 Email: rg+ietf@qti.qualcomm.com 4567 James Winterbottom 4568 AU 4570 Email: a.james.winterbottom@gmail.com