idnits 2.17.00 (12 Aug 2021) /tmp/idnits14224/draft-ietf-ecrit-additional-data-15.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 37 instances of too long lines in the document, the longest one being 16 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 2241 has weird spacing: '...element name=...' == Line 2743 has weird spacing: '...ll-Info pur...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (November 03, 2013) is 3120 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) == Missing Reference: 'This RFC' is mentioned on line 2743, but not defined == Unused Reference: 'RFC5985' is defined on line 3348, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: draft-ietf-ecrit-psap-callback has been published as RFC 7090 == Outdated reference: draft-ietf-geopriv-relative-location has been published as RFC 7035 Summary: 5 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). 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: May 07, 2014 Nokia Solutions and Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 12 November 03, 2013 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-15.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 May 07, 2014. 50 Copyright Notice 52 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . 6 70 3.1. Data Provider Information . . . . . . . . . . . . . . . . 7 71 3.1.1. Data Provider String . . . . . . . . . . . . . . . . 7 72 3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8 73 3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8 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 . . . . . . 15 84 3.2.3. Service Mobility Environment . . . . . . . . . . . . 18 85 3.2.4. emergencyCallData.SvcInfo Example . . . . . . . . . . 18 86 3.3. Device Information . . . . . . . . . . . . . . . . . . . 19 87 3.3.1. Device Classification . . . . . . . . . . . . . . . . 19 88 3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 20 89 3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 21 90 3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 21 91 3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 21 92 3.3.6. Device/Service Specific Additional Data Structure . . 22 93 3.3.7. Device/Service Specific Additional Data Structure 94 Type . . . . . . . . . . . . . . . . . . . . . . . . 23 95 3.3.8. Choosing between defining a new type of block or new 96 type of device/service specific additional data . . . 23 97 3.3.9. emergencyCallData.DevInfo Example . . . . . . . . . . 24 98 3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24 99 3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 25 100 3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25 101 3.4.3. emergencyCallData.SubInfo Example . . . . . . . . . . 26 102 3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28 103 3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28 104 3.5.2. emergencyCallData.Comment Example . . . . . . . . . . 29 105 4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 29 106 4.1. Transmitting Blocks using the Call-Info Header . . . . . 31 107 4.2. Transmitting Blocks by Reference using the Provided-By 108 Element . . . . . . . . . . . . . . . . . . . . . . . . . 31 109 4.3. Transmitting Blocks by Value using the Provided-By 110 Element . . . . . . . . . . . . . . . . . . . . . . . . . 32 111 4.4. The Content-Disposition Parameter . . . . . . . . . . . . 33 112 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34 113 6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45 114 6.1. emergencyCallData.ProviderInfo XML Schema . . . . . . . . 45 115 6.2. emergencyCallData.SvcInfo XML Schema . . . . . . . . . . 47 116 6.3. emergencyCallData.DevInfo XML Schema . . . . . . . . . . 48 117 6.4. emergencyCallData.SubInfo XML Schema . . . . . . . . . . 49 118 6.5. emergencyCallData.Comment XML Schema . . . . . . . . . . 49 119 6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 50 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.SvcInfo+xml' . . . . . 61 140 9.4.3. MIME Content-type Registration for 141 'application/emergencyCallData.DevInfo+xml' . . . . . 62 142 9.4.4. MIME Content-type Registration for 143 'application/emergencyCallData.SubInfo+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:svcinfo . . 67 154 9.5.4. Registration for 155 urn:ietf:params:xml:ns:emergencycalldata:devinfo . . 67 156 9.5.5. Registration for 157 urn:ietf:params:xml:ns:emergencycalldata:subinfo . . 68 158 9.5.6. Registration for 159 urn:ietf:params:xml:ns:emergencycalldata:comment . . 69 160 9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 70 161 9.7. VCard Parameter Value Registration . . . . . . . . . . . 70 162 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71 163 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 71 164 11.1. Normative References . . . . . . . . . . . . . . . . . . 71 165 11.2. Informational References . . . . . . . . . . . . . . . . 72 166 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 74 167 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 169 1. Introduction 171 When an IP-based emergency call is initiated a rich set of data from 172 multiple data sources is conveyed to the Public Safety Answering 173 Point (PSAP). This data includes information about the calling party 174 identity, the multimedia capabilities of the device, the emergency 175 service number, location information, and meta-data about the sources 176 of the data. The device, the access network provider, and any 177 service provider in the call path may have even more information 178 useful for a PSAP. This document extends the basic set of data 179 communicated with an IP-based emergency call, as described in 180 [RFC6443] and [RFC6881], in order to carry additional data which may 181 be useful to an entity or call taker handling the call. This data is 182 "additional" to the basic information found in the emergency call 183 signaling used. 185 In general, there are three categories of data communicated in an 186 emergency call: 188 Data Associated with a Location: Location data is conveyed in the 189 Presence Information Data Format Location Object (PIDF-LO) data 190 structure originally defined in RFC 4119 [RFC4119] and extended by 191 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 192 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 193 geodetic location information), and 194 [I-D.ietf-geopriv-relative-location] (for relative location). 195 There may be data that is specific to the location not available 196 in the location data structure itself, such as floor plans, tenant 197 and building owner contact data, heating, ventilation and air 198 conditioning (HVAC) status, etc. 200 Data Associated with a Call: While information is carried in the 201 call setup procedure itself (as part of the SIP headers as well as 202 in the body of the SIP message), there is additional data known by 203 the device making the call, and the service provider along the 204 path of the call. This information may include the service 205 provider contact information, subscriber identity and contact 206 information, the type of service the service provider and the 207 access network provider offer, what kind of device is being used, 208 etc. Some data is device or service dependent data. For example, 209 a car telematics system may have crash information. A medical 210 monitoring device may have sensor data. 212 Data Associated with a Caller: This is personal data about a caller, 213 such as medical information and emergency contact data. 215 This document only defines data structures relevant to data 216 associated with the call but defines extension points for other data 217 to be added via other specifications. 219 For interoperability, there needs to be a common way for the 220 information conveyed to a PSAP to be encoded and identified. 221 Identification allows emergency services authorities to know during 222 call processing which types of data are present and to determine if 223 they wish to access it. A common encoding allows the data to be 224 accessed. 226 This document defines the data structures and a way to communicate 227 the information in several ways. Although current standardization 228 efforts around IP-based emergency services are focused on the Session 229 Initiation Protocol (SIP) and HTTP the data structures in XML format 230 described in this document are usable for other communication systems 231 as well. In Section 3 the data structures are defined and the SIP/ 232 HTTP transport components are defined in Section 4 to offer a clear 233 separation between the two. 235 More technically, the data structure described in this document is 236 represented as one or more "blocks" of information. Each of the 237 blocks is an XML structure with an associated Multipurpose Internet 238 Mail Extensions (MIME) type for encapsulation, and an extensible set 239 of these types constitute the data set. A registry is defined to 240 list the block types that may be included. 242 2. Terminology 244 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 245 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 246 document are to be interpreted as described in RFC 2119 [RFC2119]. 248 This document also uses terminology from [RFC5012]. We use the term 249 service provider to refer to an Application Service Provider (ASP). 250 A Voice Service Provider (VSP) is a special type of ASP. With the 251 term "Access Network Provider" we refer to the Internet Access 252 Provider (IAP) and the Internet Service Provider (ISP) without 253 further distinguishing these two entities, since the difference 254 between the two is not relevant for this document. Note that the 255 roles of ASP and access network provider may be provided by a single 256 company. 258 In the data block definitions, see Section 3, the values for the 259 "Use:" label are specified as one of: 261 'Required': means they MUST be present in the data structure. 263 'Conditional': means they MUST be present if the specified 264 condition(s) is met. They MAY be present if the condition(s) is 265 not met. 267 'Optional': means they MAY be present. 269 vCard is a data format for representing and exchanging a variety of 270 information about individuals and other entities. For applications 271 that use XML the format defined in vCard is not immediately 272 applicable. For this purpose an XML-based encoding of the 273 information elements defined in the vCard specification has been 274 defined and the name of that specification is xCard. Since the term 275 vCard is more familiar to most readers we use the term xCard and 276 vCard interchangeable but it would be accurate to use the term vCard 277 only. 279 3. Data Structures 281 This section defines the following five data structures, each as a 282 data block. For each block we define the MIME type, and the XML data 283 structure. The five data structures are: 285 'Data Provider': This block supplies name and contact information 286 for the entity that created the data. Section 3.1 provides the 287 details. 289 'Service Information': This block supplies information about the 290 service. The description can be found in Section 3.2. 292 'Device Information': This block supplies information about the 293 device placing the call. Device information can be found in 294 Section 3.3. 296 'Owner/Subscriber': This block supplies information about the owner 297 of the device or about the subscriber. Details can be found in 298 Section 3.4. 300 'Comment': This block provides a way to supply free form human 301 readable text to the PSAP or emergency responders. This simple 302 structure is defined in Section 3.5. 304 Each block contains a mandatory element. The purpose of this 305 element is to associate the data added by a data provider to the 306 data provider block. Consequently, when a data provider adds 307 additional data to an emergency call (such as device information) it 308 MUST add information about itself (via the data provider block) and 309 the two blocks contain the same value in the element, whereby 310 the chosen value for the element MUST be different to any other 311 elements already added by other data providers. 313 Note that the xCard format is re-used in some of the data structures 314 to provide contact information. In an xCard there is no way to 315 specify a "main" telephone number. These numbers are useful to 316 emergency responders who are called to a large enterprise. This 317 document adds a new property value to the "tel" property of the TYPE 318 parameter called "main". It can be used in any xCard in additional 319 data. 321 3.1. Data Provider Information 323 This block is intended to be provided by any service provider in the 324 path of the call or the access network provider. It includes 325 identification and contact information. This block SHOULD be 326 provided by every service provider in the call path, and by the 327 access network provider. Devices MAY use this block to provide 328 identifying information. The MIME subtype is "application/ 329 emergencyCall.ProviderInfo+xml". An access network provider SHOULD 330 provide this block either by value or by reference in the Provided-By 331 section of a PIDF-LO 333 3.1.1. Data Provider String 335 Data Element: Data Provider String 336 Use: Required 338 XML Element: 340 Description: This is a plain language string suitable for displaying 341 the name of the service provider that created the additional data 342 structure. If the device created the structure the value is 343 identical to the contact header in the SIP INVITE. 345 Reason for Need: Inform the call taker of the identity of the entity 346 providing the additional call data structure. 348 How Used by Call Taker: Allows the call taker to interpret the data 349 in this structure. The source of the information often influences 350 how the information is used, believed or verified. 352 3.1.2. Data Provider ID 354 Data Element: Data Provider ID 356 Use: Conditional. This data SHOULD be provided if the service 357 provider or access provider is located in a jurisdiction that 358 maintains such ids. For example, in North America, this would be 359 a "NENA Company ID". 361 XML Element: 363 Description: A jurisdiction specific code for the access provider or 364 service provider shown in the element that 365 created the structure of the call. NOTE: In the US, the NENA 366 Company ID must appear here. Additional information can be found 367 at http://www.nena.org/nena-company-id. The NENA Company ID MUST 368 be in the form of a URI in the following format: 369 urn:nena:companyid: 371 Reason for Need: Inform the call taker of the identity of the entity 372 providing the additional call data structure. 374 How Used by Call Taker: Where jurisdictions have lists of providers 375 the Data Provider ID provides useful information about the data 376 source. 378 3.1.3. Data Provider ID Series 380 Data Element: Data Provider ID Series 382 Use: Conditional. If Data Provider ID is provided, Data Provider ID 383 Series is required. 385 XML Element: 387 Description: Identifies the issuer of the ProviderId. A registry 388 will reflect the following valid entries: 390 * NENA 392 * EENA 394 Reason for Need: Identifies how to interpret the Data Provider ID. 396 How Used by Call Taker: Determines which provider ID registry to 397 consult for more information 399 3.1.4. Type of Data Provider 401 Data Element: Type of Data Provider ID 403 Use: Conditional. If Data Provider ID is provided, Type of Data 404 Provider ID is required. 406 XML Element: 408 Description: Identifies the type of data provider id being supplied 409 in the ProviderId data element. A registry with an initial set of 410 values is shown in Figure 1. 412 +------------------------------+------------------------------------+ 413 | Token | Description | 414 +------------------------------+------------------------------------+ 415 |Access Network Provider | Access network service provider | 416 |Service Provider | Calling or Origination telecom SP | 417 |Subcontractor | A contractor to another SP | 418 |Telematics Provider | A sensor based SP, especially | 419 | | vehicle based | 420 |Language Translation Provider | A spoken language translation SP | 421 |Emergency Service Provider | An emergency service provider | 422 | | conveying information to another | 423 | | emergency service provider. | 424 |Emergency Modality Translation| An emergency call specific | 425 | | modality translation service | 426 | | e.g., for sign language | 427 |Relay Provider | A interpretation SP, for example, | 428 | | video relay for sign language | 429 | | interpreting | 430 |Other | Any other type of service provider | 431 +------------------------------+------------------------------------+ 433 Figure 1: Type of Data Provider ID Registry. 435 Reason for Need: Identifies what kind of data provider this is. 437 How Used by Call Taker: To decide who to contact when further 438 information is needed 440 3.1.5. Data Provider Contact URI 442 Data Element: Data Provider Contact URI 444 Use: Required 446 XML Element: 448 Description: When provided by a service provider or an access 449 provider, this information MUST be a URI to a 24/7 support 450 organization tasked to provide PSAP support for this emergency 451 call. If the call is from a device, this would reflect the 452 contact information of the owner of the device. If a telephone 453 number is the contact address then it MUST be tel URI. If it is 454 provided as a SIP URI then it MUST be in the form of 455 sip:telephonenumber@serviceprovider:user=phone. Note that this 456 contact information is not used by PSAPs for callbacks using a SIP 457 Priority header field with the value set to "psap- callback", as 458 described in [I-D.ietf-ecrit-psap-callback]. 460 Reason for Need: Additional data providers may need to be contacted 461 for error or other unusual circumstances. 463 How Used by Call Taker: To contact the supplier of the additional 464 data for assistance in handling the call. 466 3.1.6. Data Provider Languages(s) Supported 468 Data Element: Data Provider Language(s) supported 470 Use: Required. 472 XML Element: 474 Description: The language used by the entity at the Data Provider 475 Contact URI as an alpha 2-character code as defined in ISO 476 639-1:2002 Codes for the representation of names of languages -- 477 Part 1: Alpha-2 code Multiple instances of this element may occur. 478 Order is significant; preferred language should appear first. The 479 content MUST reflect the languages supported at the contact URI. 481 Note that the 'language' media feature tag, defined in RFC 3840 482 [RFC3840] and the more extensive language negotiation mechanism 483 proposed with [I-D.gellens-negotiating-human-language] are 484 independent of this data provider language indication. 486 Reason for Need: Information needed to determine if emergency 487 service authority can communicate with the service provider or if 488 an interpreter will be needed. 490 How Used by Call Taker: If call taker cannot speak language(s) 491 supported by the service provider, a translation service will need 492 to be added to the conversation. Alternatively, other persons at 493 the PSAP, besides the call taker, might be consulted for help 494 (depending on the urgency and the type of interaction). 496 3.1.7. xCard of Data Provider 498 Data Element: xCard of Data Provider 500 Use: Optional 502 XML Element: 504 Description: There are many fields in the xCard and the creator of 505 the data structure is encouraged to provide as much information as 506 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 507 minimum. N should contain name of support group or device owner 508 as appropriate. If more than one TEL property is provided, a 509 parameter from the vCard Property Value registry MUST be specified 510 on each TEL. For encoding of the xCard this specification uses 511 the XML-based encoding specified in [RFC6351]. and is hereinafter 512 referred to as "xCard" 514 Reason for Need: Information needed to determine additional contact 515 information. 517 How Used by Call Taker: Assists call taker by providing additional 518 contact information that may not be included in the SIP invite or 519 the PIDF-LO. 521 3.1.8. Subcontractor Principal 523 Data Element: Subcontractor Principal 525 Use: Conditional. This data is required if the Data Provider type 526 is subcontractor. 528 XML Element: 530 Description: Some providers outsource their obligations to handle 531 aspects of emergency services to specialized providers. If the 532 data provider is a subcontractor to another provider this element 533 contains the DataProviderString of the service provider to 534 indicate which provider the subcontractor is working for. 536 Reason for Need: Identify the entity the subcontractor works for. 538 How Used by Call Taker: Allows the call taker to understand what the 539 relationship between data providers and the service providers in 540 the path of the call are. 542 3.1.9. Subcontractor Priority 544 Data Element: Subcontractor Priority 546 Use: Conditional. This element is required if the Data Provider 547 type is set to "Subcontractor". 549 XML Element: 551 Description: If the subcontractor has to be contacted first then 552 this element MUST have the value "sub". If the provider the 553 subcontractor is working for has to be contacted first then this 554 element MUST have the value "main". 556 Reason for Need: Inform the call taker whom to contact first, if 557 support is needed. 559 How Used by Call Taker: To decide which entity to contact first if 560 assistance is needed. 562 3.1.10. ProviderInfo Example 564 565 568 12345 569 Example VoIP Provider 570 571 urn:nena:companyid:ID123 572 NENA 573 Service Provider 574 sip:voip-provider@example.com 575 EN 576 578 579 Hannes Tschofenig 580 581 Hannes 582 Tschofenig 583 584 585 Dipl. Ing. 586 587 --0203 588 589 20090808T1430-0500 590 591 M 592 593 1 594 595 de 596 597 598 2 599 600 en 601 602 603 work 604 605 Example VoIP Provider 606 607 608 609 work 610 614 615 616 617 Linnoitustie 6 618 Espoo 619 Uusimaa 620 02600 621 Finland 622 623 624 625 626 work 627 voice 628 629 630 tel:+358 50 4871445 631 632 633 work 634 635 hannes.tschofenig@nsn.com 636 637 638 work 639 640 geo:60.210796,24.812924 641 642 643 home 644 645 646 http://www.tschofenig.priv.at/key.asc 647 648 649 Finland/Helsinki 650 651 home 652 653 http://www.tschofenig.priv.at 654 655 656 657 659 Figure 2: emergencyCall.ProviderInfo Example. 661 3.2. Service Information 663 This block describes the service that the service provider provides 664 to the caller. It SHOULD be included by all SPs in the path of the 665 call. The mime subtype is "application/emergencyCall.SvcInfo+xml". 667 3.2.1. Service Environment 669 Data Element: Service Environment 671 Use: Required 673 XML Element: 675 Description: This element defines whether a call is from a business 676 or residence caller. Currently, the only valid entries are 677 'Business' or 'Residence'. New values can be defined via the 678 registry created in Figure 22. 680 Reason for Need: To assist in determining equipment and manpower 681 requirements. 683 How Used by Call Taker: Information may be used to assist in 684 determining equipment and manpower requirements for emergency 685 responders. As the information is not always available, and the 686 registry is not all encompassing, this is at best advisory 687 information, but since it mimics a similar capability in some 688 current emergency calling systems, it is known to be valuable. 689 The service provider uses its best information (such as a rate 690 plan, facilities used to deliver service or service description) 691 to determine the information and is not responsible for 692 determining the actual characteristics of the location where the 693 call originates from. 695 3.2.2. Service Delivered by Provider to End User 697 Data Element: Service Delivered by Provider to End User 698 Use: Required 700 XML Element: 702 Description: This defines the type of service the end user has 703 subscribed to. The implied mobility of this service cannot be 704 relied upon. A registry with an initial set of values is defined 705 in Figure 3. 707 +--------+----------------------------------------+ 708 | Name | Description | 709 +--------+----------------------------------------+ 710 | Wrless | Wireless Telephone Service: Includes | 711 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 712 | | LTE (Long Term Evolution) | 713 | Coin | Fixed Public Pay/Coin telephones: Any | 714 | | coin or credit card operated device | 715 | 1way | One way outbound service | 716 | Prison | Inmate call/service | 717 | Temp | Soft dialtone/quick service/warm | 718 | | disconnect/suspended | 719 | MLTS | Multi-line telephone system: Includes | 720 | | all PBX, Centrex, key systems, | 721 | | Shared Tenant Service | 722 | SenseU | Sensor, unattended: Includes devices | 723 | | that generate DATA ONLY. This is | 724 | | one-way information exchange and | 725 | | there will be no other form of | 726 | | communication | 727 | SenseA | Sensor, attended: Includes devices | 728 | | that are supported by a monitoring | 729 | | service provider or automatically | 730 | | open a two-way communication path | 731 | POTS | Wireline: Plain Old Telephone Service | 732 | VOIP | VoIP Telephone Service: A type of | 733 | | service that offers communication | 734 | | over internet protocol, such as Fixed| 735 | | Nomadic, Mobile, ... | 736 | Remote | Off premise extension | 737 | Relay | Relay Service: a type of service where | 738 | | there is a human 3rd party agent who | 739 | | provides some kind of additional | 740 | | assistance to the caller. Includes | 741 | | sign language relay and telematics | 742 | | services which provide a service | 743 | | assistant on the call. | 744 +--------+----------------------------------------+ 746 Figure 3: Service Delivered by Provider to End User Registry. 748 More than one value MAY be returned. For example, a VoIP inmate 749 telephone service is a reasonable combination. 751 Reason for Need: Knowing the type of service may assist the PSAP 752 with the handling of the call. 754 How Used by Call Taker: Call takers often use this information to 755 determine what kinds of questions to ask callers, and how much to 756 rely on supportive information. An emergency call from a prison 757 is treated differently that a call from a sensor device. As the 758 information is not always available, and the registry is not all 759 encompassing, this is at best advisory information, but since it 760 mimics a similar capability in some current emergency calling 761 systems, it is known to be valuable. 763 3.2.3. Service Mobility Environment 765 Data Element: Service Mobility Environment 767 Use: Required 769 XML Element: 771 Description: This provides the service providers view of the 772 mobility of the caller. As the service provider may not know the 773 characteristics of the actual access network used, the value not 774 be relied upon. A registry will reflect the following initial 775 valid entries: 777 * Mobile: the device should be able to move at any time 779 * Fixed: the device is not expected to move unless the service is 780 relocated 782 * Nomadic: the device is not expected to change its point of 783 attachment while on a call 785 * Unknown: no information is known about the service mobility 786 environment for the device 788 Reason for Need: Knowing the service provider's belief of mobility 789 may assist the PSAP with the handling of the call. 791 How Used by Call Taker: To determine whether to assume the location 792 of the caller might change. 794 3.2.4. emergencyCallData.SvcInfo Example 796 797 800 12345 801 Business 802 MLTS 803 Fixed 804 806 Figure 4: emergencyCallData.SvcInfo Example. 808 3.3. Device Information 810 This block provides information about the device used to place the 811 call. It should be provided by any service provider that knows what 812 device is being used, and by the device itself. The mime subtype is 813 "application/emergencyCall.DevInfo+xml". 815 3.3.1. Device Classification 817 Data Element: Device Classification 819 Use: Optional 821 XML Element: 823 Description: This data element defines the kind of device making the 824 emergency call. If the device provides the data structure, the 825 device information SHOULD be provided. If the service provider 826 provides the structure and it knows what the device is, the 827 service provider SHOULD provide the device information. Often the 828 carrier does not know what the device is. It is possible to 829 receive two Additional Data Associated with a Call data 830 structures, one created by the device and one created by the 831 service provider. This information describes the device, not how 832 it is being used. This data element defines the kind of device 833 making the emergency call. The registry with the initial set of 834 values is shown in Figure 5. 836 +--------+----------------------------------------+ 837 | Token | Description | 838 +--------+----------------------------------------+ 839 |Cordless| Cordless handset | 840 | Fixed | Fixed phone | 841 | Mobile | Mobile handset | 842 | ATA | analog terminal adapter | 843 |Satphone| Satellite phone | 844 | FSense | Stationary computing device (alarm | 845 | | system, data sensor) | 846 | Guard | Guardian devices | 847 | Desktop| Desktop PC | 848 | Laptop | Laptop computing device | 849 | Tablet | Tablet computing device | 850 | Alarm | Alarm system | 851 | MSense | Mobile Data sensor | 852 | Beacon | Personal beacons (spot) | 853 | Auto | Auto telematics | 854 | Truck | Truck telematics | 855 | Farm | Farm equipment telematics | 856 | Marine | Marine telematics | 857 | PDA | Personal digital assistant | 858 | PND | Personal navigation device) | 859 | SmrtPhn| Smart phone | 860 | Itab | Internet tablet | 861 | Game | Gaming console | 862 | Video | Video phone | 863 | Text | Other text device | 864 |SoftPhn | Soft phone or soft client software | 865 | NA | Not Available | 866 +--------+----------------------------------------+ 868 Figure 5: Device Classification Registry. 870 Reason for Need: The device classification implies the capability of 871 the calling device and assists in identifying the meaning of the 872 emergency call location information that is being presented. For 873 example, does the device require human intervention to initiate a 874 call or is this call the result of programmed instructions? Does 875 the calling device have the ability to update location or 876 condition changes? Is this device interactive or a one-way 877 reporting device? 879 How Used by Call Taker: May assist with location of caller. For 880 example, a cordless handset may be outside or next door. May 881 provide the calltaker some context about the caller, the 882 capabilities of the device used for the call or the environment 883 the device is being used in. 885 3.3.2. Device Manufacturer 887 Data Element: Device Manufacturer 889 Use: Optional 891 XML Element: 893 Description: The plain language name of the manufacturer of the 894 device. 896 Reason for Need: Used by PSAP management for post-mortem 897 investigation/resolution. 899 How Used by Call Taker: Probably not used by the calltaker, but by 900 PSAP management. 902 3.3.3. Device Model Number 904 Data Element: Device Model Number 906 Use: Optional 908 XML Element: 910 Description: Model number of the device. 912 Reason for Need: Used by PSAP management for after action 913 investigation/resolution. 915 How Used by Call Taker: Probably not used by the calltaker, but by 916 PSAP management. 918 3.3.4. Unique Device Identifier 920 Data Element: Unique Device Identifier 922 Use: Optional 924 XML Element: 926 Description: String that identifies the specific device making the 927 call or creating an event. 929 Reason for Need: Uniquely identifies the device as opposed to any 930 signaling identifiers encountered in the call signaling stream. 932 How Used by Call Taker: Probably not used by the calltaker; they 933 would need to refer to management for investigation. 935 3.3.5. Type of Device Identifier 937 Data Element: Type of Device Identifier 939 Use: Conditional: must be provided if the DeviceID is provided 941 XML Element: 942 Description: Identifies the type of device identifier being 943 generated in the unique device identifier data element. A 944 registry with an initial set of values can be seen in Figure 6. 946 +--------+----------------------------------------+ 947 | Token | Description | 948 +--------+----------------------------------------+ 949 | MEID | Mobile Equipment Identifier (CDMA) | 950 | ESN | Electronic Serial Number(GSM) | 951 | MAC | Media Access Control Address (IEEE) | 952 | WiMAX | Device Certificate Unique ID | 953 | IMEI | International Mobile Equipment ID (GSM)| 954 | UDI | Unique Device Identifier | 955 | RFID | Radio Frequency Identification | 956 | SN | Manufacturer Serial Number | 957 +--------+----------------------------------------+ 959 Figure 6: Registry with Device Identifier Types. 961 Reason for Need: Identifies how to interpret the Unique Device 962 Identifier. 964 How Used by Call Taker: Additional information that may be used to 965 assist with call handling. 967 3.3.6. Device/Service Specific Additional Data Structure 969 Data Element: Device/service specific additional data structure 971 Use: Optional 973 XML Element: 975 Description: A URI representing additional data whose schema is 976 specific to the device or service which created it. An example is 977 the Vehicular Emergency Data Set (VEDS) structure for a vehicle 978 telematics device. The URI, when dereferenced, MUST yield a data 979 structure defined by the Device/service specific additional data 980 type value. Different data may be created by each classification; 981 e.g., a telematics created VEDS data set. 983 Reason for Need: Provides device/service specific data that may be 984 used by the call taker and/or responders. 986 How Used by Call Taker: Provide information to guide call takers to 987 select appropriate responders, give appropriate pre-arrival 988 instructions to callers, and advise responders of what to be 989 prepared for. May be used by responders to guide assistance 990 provided. 992 3.3.7. Device/Service Specific Additional Data Structure Type 994 Data Element: Type of device/service specific additional data 995 structure 997 Use: Conditional. MUST be provided when device/service specific 998 additional URI is provided 1000 XML Element: 1002 Description: Value from a registry defined by this document to 1003 describe the type of data that can be retrieved from the device/ 1004 service specific additional data structure. Initial values are: 1006 * IEEE 1512 1008 * VEDS 1010 IEEE 1512 is the USDoT model for traffic incidents and VEDS 1011 provides data elements needed for an efficient emergency response 1012 to vehicular emergency incidents. 1014 Reason for Need: This data element allows identification of 1015 externally defined schemas, which may have additional data that 1016 may assist in emergency response. 1018 How Used by Call Taker: This data element allows the end user 1019 (calltaker or first responder) to know what type of additional 1020 data may be available to aid in providing the needed emergency 1021 services. 1023 Note: Information which is specific to a location or a caller 1024 (person) should not be placed in this section. 1026 3.3.8. Choosing between defining a new type of block or new type of 1027 device/service specific additional data 1029 For devices that have device or service specific data, there are two 1030 choices to carry it. A new block can be defined, or the device/ 1031 service specific additional data URL the DevInfo block can be used 1032 and a new type for it defined . The data passed would likely be the 1033 same in both cases. Considerations for choosing which mechanism to 1034 register under include: 1036 Applicability: Information which will be carried by many kinds of 1037 devices or services are more appropriately defined as separate 1038 blocks. 1040 Privacy: Information which may contain private data may be better 1041 sent in the DevInfo block, rather than a new block so that 1042 implementations are not tempted to send the data by value, and 1043 thus having more exposure to the data than forcing the data to be 1044 retrieved via the URL in DevInfo. 1046 Size: Information which may be very may be better sent in the 1047 DevInfo block, rather than a new block so that implementations are 1048 not tempted to send the data by value. Conversely, data which is 1049 small may best be sent in a separate block so that it can be sent 1050 by value 1052 Availability of a server: Providing the data via the device block 1053 requires a server be made available to retrieve the data. 1054 Providing the data via new block allows it to be sent by value 1055 (CID). 1057 3.3.9. emergencyCallData.DevInfo Example 1059 1060 1063 12345 1064 Fixed phone 1065 Nokia 1066 Lumia 800 1067 35788104 1068 IMEI 1069 1071 Figure 7: emergencyCallData.DevInfo Example. 1073 3.4. Owner/Subscriber Information 1074 This block describes the owner of the device (if provided by the 1075 device) or the subscriber information, if provided by a service 1076 provider. The contact location is not necessarily the location of 1077 the caller or incident, but is rather the nominal contact address. 1078 The mime subtype is "application/emergencyCall.Subscriber+xml". 1080 In some jurisdictions some or all parts of the subscriber-specific 1081 information are subject to privacy constraints. These constraints 1082 vary but dictate what information and be displayed and logged. A 1083 general privacy indicator expressing a desire for privacy is 1084 provided. The interpretation of how this is applied is left to the 1085 receiving jurisdiction as the custodians of the local regulatory 1086 requirements. 1088 3.4.1. Subscriber Data Privacy Indicator 1090 Attribute: privacyRequested, boolean. 1092 Use: Conditional. This attribute MUST be provided if the owner/ 1093 subscriber information block is not empty. 1095 Description: The subscriber data privacy indicator specifically 1096 expresses the subscriber's desire for privacy. In some 1097 jurisdictions subscriber services can have a specific "Type of 1098 Service" which prohibits information, such as the name of the 1099 subscriber, from being displayed. This attribute should be used 1100 to explicitly indicate whether the subscriber service includes 1101 such constraints. 1103 Reason for Need: Some jurisdictions require subscriber privacy to be 1104 observed. 1106 How Used by Call Taker: Where privacy is indicated the call taker 1107 may not have access to some aspects of the subscriber information. 1109 3.4.2. xCard for Subscriber's Data 1111 Data Element: xCARD for Subscriber's Data 1113 Use: Conditional. Subscriber data is provided unless it is not 1114 available. Some services, for example prepaid phones, non- 1115 initialized phones, etc., do not have information about the 1116 subscriber. 1118 XML Element: 1120 Description: Information known by the service provider or device 1121 about the subscriber; e.g., Name, Address, Individual Telephone 1122 Number, Main Telephone Number and any other data. N, ORG (if 1123 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1124 than one TEL property is provided, a parameter from the vCard 1125 Property Value registry MUST be specified on each TEL. 1127 Reason for Need: When the caller is unable to provide information, 1128 this data may be used to obtain it 1130 How Used by Call Taker: Obtaining critical information about the 1131 caller and possibly the location when it is not able to be 1132 obtained otherwise. 1134 3.4.3. emergencyCallData.SubInfo Example 1136 1137 1141 12345 1142 1143 1144 1145 Simon Perreault 1146 1147 Perreault 1148 Simon 1149 1150 1151 ing. jr 1152 M.Sc. 1153 1154 --0203 1155 1156 20090808T1430-0500 1157 1158 M 1159 1160 1 1161 1162 fr 1163 1164 1165 2 1166 1167 en 1168 1169 1170 work 1171 1172 Viagenie 1173 1174 1175 1176 work 1177 1181 1182 1183 1184 2875 boul. Laurier, suite D2-630 1185 Quebec 1186 QC 1187 G1V 2M2 1188 Canada 1189 1190 1191 1192 1193 work 1194 voice 1195 1196 1197 tel:+1-418-656-9254;ext=102 1198 1199 1200 1201 1202 work 1203 text 1204 voice 1205 cell 1206 video 1207 1208 1209 tel:+1-418-262-6501 1210 1211 1212 work 1213 1214 simon.perreault@viagenie.ca 1215 1216 1217 work 1218 1219 geo:46.766336,-71.28955 1220 1221 1222 work 1223 1224 1225 http://www.viagenie.ca/simon.perreault/simon.asc 1226 1227 1228 America/Montreal 1229 1230 home 1231 1232 http://nomis80.org 1233 1234 1235 1236 1237 1239 Figure 8: emergencyCallData.SubInfo Example. 1241 3.5. Comment 1243 This block provides a mechanism for the data provider to supply 1244 extra, human readable information to the PSAP. It is not intended 1245 for a general purpose extension mechanism nor does it aim to provide 1246 machine-reable content. The mime subtype is "application/ 1247 emergencyCall.Comment+xml" 1249 3.5.1. Comment 1251 Data Element: EmergencyCall.Comment 1253 Use: Optional 1255 XML Element: 1257 Description: Human readable text providing additional information to 1258 the PSAP staff. 1260 Reason for Need: Explanatory information for values in the data 1261 structure 1263 How Used by Call Taker: To interpret the data provided 1265 3.5.2. emergencyCallData.Comment Example 1267 1268 1271 12345 1272 This is an example text. 1273 1275 Figure 9: EmergencyCallData.Comment Example. 1277 4. Transport 1279 This section defines how to convey additional data to an emergency 1280 service provider. Two different means are specified: the first uses 1281 the call signaling; the second uses the element of a 1282 PIDF-LO [RFC4119]. 1284 1. First, the ability to embed a Uniform Resource Identifier (URI) 1285 in an existing SIP header field, the Call-Info header, is 1286 defined. The URI points to the additional data structure. The 1287 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1288 document adds a new compound token starting with the value 1289 'emergencyCallData' for the Call-Info "purpose" parameter. If 1290 the "purpose" parameter is set to a value starting with 1291 'emergencyCallData', then the Call-Info header contains either an 1292 HTTPS URL pointing to an external resource or a CID (content 1293 indirection) URI that allows the data structure to be placed in 1294 the body of the SIP message. The "purpose" parameter also 1295 indicates the kind of data (by its MIME type) that is available 1296 at the URI. As the data is conveyed using a URI in the SIP 1297 signaling, the data itself may reside on an external resource, or 1298 may be contained within the body of the SIP message. When the 1299 URI refers to data at an external resource, the data is said to 1300 be passed by reference. When the URI refers to data contained 1301 within the body of the SIP message, the data is said to be passed 1302 by value. A PSAP or emergency responder is able to examine the 1303 type of data provided and selectively inspect the data it is 1304 interested in, while forwarding all of it (the values or 1305 references) to downstream entities. To be conveyed in a SIP 1306 body, additional data about a call is defined as a series of MIME 1307 objects. Each block defined in this document is an XML data 1308 structure identified by its MIME type. (Blocks defined by others 1309 may be encoded in XML or not, as identified by their MIME 1310 registration.) As usual, whenever more than one MIME part is 1311 included in the body of a message, MIME-multipart (i.e., 1312 'multipart/mixed') encloses them all. This document defines a 1313 set of XML schemas and MIME types used for each block defined 1314 here. When additional data is passed by value in the SIP 1315 signaling, each CID URL points to one block in the body. 1316 Multiple URIs are used within a Call-Info header field (or 1317 multiple Call-Info header fields) to point to multiple blocks. 1318 When additional data is provided by reference (in SIP signaling 1319 or Provided-By), each HTTPS URL references one block; the data is 1320 retrieved with an HTTPS GET operation, which returns one of the 1321 blocks as an object (the blocks defined here are returned as XML 1322 objects). 1324 2. Second, the ability to embed additional data structures in the 1325 element of a PIDF-LO [RFC4119] is defined. Besides 1326 a service provider in the call path, the access network provider 1327 may also have similar information that may be valuable to the 1328 PSAP. The access network provider may provide location in the 1329 form of a PIDF-LO from a location server via a location 1330 configuration protocol. The data structures described in this 1331 document are not specific to the location itself, but rather 1332 provides descriptive information having to do with the immediate 1333 circumstances about the provision of the location (who the access 1334 network is, how to contact that entity, what kind of service the 1335 access network provides, subscriber information, etc.). This 1336 data is similar in nearly every respect to the data known by 1337 service providers in the path of the call. When the access 1338 network provider and service provider are separate entities, the 1339 access network does not participate in the application layer 1340 signaling (and hence cannot add a Call-Info header field to the 1341 SIP message), but may provide location information to assist in 1342 locating the caller's device. The element of the 1343 PIDF-LO is a mechanism for the access network provider to supply 1344 the information about the entity or organization that supplied 1345 this location information. For this reason, this document 1346 describes a namespace per RFC 4119 for inclusion in the 1347 element of a PIDF-LO for adding information known 1348 to the access network provider. 1350 One or more blocks of data registered in the Emergency Call 1351 Additional Data registry, as defined in Section 9.1, may be included 1352 or referenced in the SIP signaling (using the Call-Info header field) 1353 or in the element of a PIDF-LO. Every block must be 1354 one of the types in the registry. Since the data of an emergency 1355 call may come from multiple sources, the data itself needs 1356 information describing the source. Consequently, each entity adding 1357 additional data MUST supply the "Data Provider" block. All other 1358 blocks are optional, but each entity SHOULD supply any blocks where 1359 it has at least some of the information in the block. 1361 4.1. Transmitting Blocks using the Call-Info Header 1363 A URI to a block MAY be inserted in a SIP request or response method 1364 (most often INVITE or MESSAGE) with a Call-Info header field 1365 containing a purpose value starting with 'emergencyCallData' and the 1366 type of data available at the URI. The type of data is denoted by 1367 including the root of the MIME type (not including the 1368 'emergencyCall' prefix and any suffix such as '+xml') with a '.' 1369 separator. For example, when referencing a block with MIME type 1370 'application/emergencyCall.ProviderInfo+xml', the 'purpose' parameter 1371 is set to 'emergencyCallData.ProviderInfo'. An example "Call-Info" 1372 header field for this would be: 1374 Call-Info: https://www.example.com/23sedde3; 1375 purpose="emergencyCallData.ProviderInfo" 1377 A Call-info header with a purpose value starting with 1378 'emergencyCallData' MUST only be sent on an emergency call, which can 1379 be ascertained by the presence of an emergency service urn in a Route 1380 header of a SIP message. 1382 If the data is provided by reference, an HTTPS URI MUST be included 1383 and consequently Transport Layer Security (TLS) protection is applied 1384 for protecting the retrieval of the information. 1386 The data may also be supplied by value in a SIP message. In this 1387 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1388 referencing the MIME body part. 1390 More than one Call-Info header with a purpose value starting with 1391 'emergencyCallData' can be expected, but at least one MUST be 1392 provided. The device MUST provide one if it knows no service 1393 provider is in the path of the call. The device MAY insert one if it 1394 uses a service provider. Any service provider in the path of the 1395 call MUST insert its own. For example, a device, a telematics 1396 service provider in the call path, as well as the mobile carrier 1397 handling the call will each provide one. There may be circumstances 1398 where there is a service provider who is unaware that the call is an 1399 emergency call and cannot reasonably be expected to determine that it 1400 is an emergency call. In that case, that service provider is not 1401 expected to provide emergencyCallData. 1403 4.2. Transmitting Blocks by Reference using the Provided-By Element 1405 The 'emergencyCallDataReference' element is used to transmit an 1406 additional data block by reference within a 'Provided-By' element of 1407 a PIDF-LO. The 'emergencyCallDataReference' element has two 1408 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1409 type of data block referenced. The value of 'ref' is an HTTPS URL 1410 that resolves to a data structure with information about the call. 1411 The value of 'purpose' is the same as used in a 'Call-Info' header 1412 field (as specified in Section 4.1). 1414 For example, to reference a block with MIME type 'application/ 1415 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to 1416 'emergencyCallData.ProviderInfo'. An example 1417 'emergencyCallDataReference' element for this would be: 1419 1422 4.3. Transmitting Blocks by Value using the Provided-By Element 1424 It is RECOMMENDED that access networks supply the data specified in 1425 this document by reference, but they MAY provide the data by value. 1427 The 'emergencyCallDataValue' element is used to transmit an 1428 additional data block by value within a 'Provided-By' element of a 1429 PIDF-LO. The 'emergencyCallDataValue' element has one attribute: 1430 'purpose' to indicate the type of data block contained. The value of 1431 'purpose' is the same as used in a 'Call-Info' header field (as 1432 specified in Section 4.1, and in Section 4.1). The same XML 1433 structure as would be contained in the corresponding MIME type body 1434 part is placed inside the 'emergencyCallDataValue' element. 1436 For example: 1438 1440 1441 1443 1445 This is an example text. 1446 1447 1448 1449 1451 Test 1452 NENA 1453 Access Infrastructure Provider 1454 1455 sip:15555550987@burf.example.com;user=phone 1456 1457 1458 1460 Example Provided-By by Value. 1462 4.4. The Content-Disposition Parameter 1464 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1465 It updates and clarifies handling originally defined in RFC 3261 1466 [RFC3261] based on implementation experience. While RFC 3261 did not 1467 mandate support for 'multipart' message bodies 'multipart/mixed' MIME 1468 bodies are, however, used by many extensions (including additional 1469 data) today. For example, adding a PIDF-LO, SDP, and additional data 1470 in body of a SIP message requires a 'multipart' message body. 1472 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1473 parameter for the Content-Disposition header field. These RFCs 1474 describe how a UAS reacts if it receives a message body whose content 1475 type or disposition type it does not understand. If the 'handling' 1476 parameter has the value "optional", the UAS ignores the message body. 1477 If the 'handling' parameter has the value "required", the UAS returns 1478 a 415 (Unsupported Media Type) response. The 'by-reference' 1479 disposition type allows a SIP message to contain a reference to the 1480 body part, and the SIP UA processes the body part according to the 1481 reference. This is the case for the Call-info header containing a 1482 Content Indirection (CID) URL. 1484 As an example, a SIP message indicates the Content-Disposition 1485 parameter in the body of the SIP message as shown in Figure 10. 1487 Content-Type: application/sdp 1489 ...Omit Content-Disposition here; defaults are ok 1490 ...SDP goes in here 1492 --boundary1 1494 Content-Type: application/pidf+xml 1495 Content-ID: 1496 Content-Disposition: by-reference;handling=optional 1498 ...PIDF-LO goes in here 1500 --boundary1-- 1501 Content-Type: application/emergencyCall.ProviderInfo+xml 1502 Content-ID: <1234567890@atlanta.example.com> 1503 Content-Disposition: by-reference;handling=optional 1505 ...Data provider information data goes in here 1507 --boundary1-- 1509 Figure 10: Example for use of the Content-Disposition Parameter in 1510 SIP. 1512 5. Examples 1514 This section illustrates a longer and more complex example, as shown 1515 in Figure 11. In this example additional data is added by the end 1516 device, included by the VoIP provider, and provided by the access 1517 network provider. 1519 O +----+ Emergency Call 1520 /|\ | UA |--+ +Device Info 1521 | +----+ | +Data Provider Info 1522 / \ | +Location URI 1523 | 1524 | (1) 1525 \ 1526 \ 1527 ,-----------. Location 1528 ,' `. +Owner/Subscriber Info 1529 / \ +Device Info 1530 | Access | +Data Provider Info #3 1531 | Network |<..................+ 1532 | Provider | . 1533 \ / . (4) 1534 `. ,' . 1535 '----------' . 1536 | . 1537 | v 1538 | +----------+ 1539 (2)| | | 1540 | | PSAP | 1541 \ | | 1542 \ +----------+ 1543 Emergency Call \ ^ 1544 +Device Info \ | 1545 +Data Provider Info ,-------. | (3) 1546 +Location URI ,' `. - 1547 / VoIP \ ---- 1548 ( Provider )--- 1549 \ example.org / Emergency Call 1550 `. ,' +Device Info 1551 '-------' +Owner/Subscriber Info 1552 +Data Provider Info 1553 ////////////// 1554 +Service Info 1555 +Location URI 1556 +Data Provider Info #2 1558 Legend: 1560 --- Emergency Call Setup Procedure 1561 ... Location Retrieval/Response 1563 Figure 11: Additional Data Example Flow. 1565 The example scenario starts with the end device itself adding device 1566 information, owner/subscriber information, a location URI, and data 1567 provider information to the outgoing emergency call setup message 1568 (see step #1 in Figure 11). The SIP INVITE example is shown in 1569 Figure 12. 1571 INVITE urn:service:sos SIP/2.0 1572 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1573 Max-Forwards: 70 1574 To: 1575 From: Hannes Tschofenig ;tag=9fxced76sl 1576 Call-ID: 3848276298220188511@example.com 1577 Call-Info: ;purpose=icon, 1578 ;purpose=info, 1579 1580 ;purpose=emergencyCallData.ProviderInfo 1581 Geolocation: 1582 Geolocation-Routing: yes 1583 Accept: application/sdp, application/pidf+xml, 1584 application/emergencyCallProviderinfo+xml 1585 CSeq: 31862 INVITE 1586 Contact: 1587 Content-Type: multipart/mixed; boundary=boundary1 1589 Content-Length: ... 1591 --boundary1 1592 Content-Type: application/sdp 1594 ...SDP goes here 1596 --boundary1-- 1598 Content-Type: application/emergencyCallData.DevInfo+xml 1599 Content-ID: <1234567890@atlanta.example.com> 1600 Content-Disposition: by-reference;handling=optional 1601 1603 1606 12345 1607 SoftPhn 1608 00-0d-4b-30-72-df 1609 MAC 1610 1612 --boundary1-- 1614 Content-Type: application/emergencyCallData.ProviderInfo+xml 1615 Content-ID: <1234567890@atlanta.example.com> 1616 Content-Disposition: by-reference;handling=optional 1617 1618 1621 12345 1622 Hannes Tschofenig 1623 1624 Other 1625 sip:hannes@example.com 1626 EN 1627 1629 1630 Hannes Tschofenig 1631 1632 Hannes 1633 Tschofenig 1634 1635 1636 Dipl. Ing. 1637 1638 --0203 1639 1640 20090808T1430-0500 1641 1642 M 1643 1644 1 1645 1646 de 1647 1648 1649 2 1650 1651 en 1652 1653 1654 1655 work 1656 1660 1661 1662 1663 Linnoitustie 6 1664 Espoo 1665 Uusimaa 1666 02600 1667 Finland 1668 1669 1670 1671 1672 work 1673 voice 1674 1675 1676 tel:+358 50 4871445 1677 1678 1679 work 1680 1681 hannes.tschofenig@nsn.com 1682 1683 1684 work 1685 1686 geo:60.210796,24.812924 1688 1689 1690 1691 home 1692 1693 https://www.example.com/key.asc 1694 1695 1696 Finland/Helsinki 1697 1698 home 1699 1700 http://example.com/hannes.tschofenig 1701 1702 1703 1704 1705 --boundary1-- 1707 Figure 12: End Device sending SIP INVITE with Additional Data. 1709 In this example, information available to the access network operator 1710 is included in the call setup message only indirectly via the use of 1711 the location reference. The PSAP has to retrieve it via a separate 1712 look-up step. Since the access network provider and the VoIP service 1713 provider are two independent entities in this scenario the access 1714 network operator is not involved in the processing of application 1715 layer exchanges and forwards the SIP INVITE transparently, as 1716 illustrated in step #1. No change to the SIP INVITE is applied. 1718 When the VoIP service provider receives the message and determines 1719 based on the Service URN that the incoming request is an emergency 1720 call. It performs the typical emergency services related tasks, 1721 including location-based routing, and adds additional data, namely 1722 service and subscriber information, to the outgoing message. For the 1723 example we assume a VoIP service provider that deploys a back-to-back 1724 user agent allowing additional data to be included in the body of the 1725 SIP message (rather than per reference in the header), which allows 1726 us to illustrate the use of multiple data provider info blocks. The 1727 resulting message is shown in Figure 13. 1729 INVITE sips:psap@example.org SIP/2.0 1730 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 1731 Max-Forwards: 70 1732 To: 1733 From: Hannes Tschofenig ;tag=9fxced76sl 1734 Call-ID: 3848276298220188511@example.com 1735 Call-Info: ;purpose=icon, 1736 ;purpose=info, 1737 1738 ;purpose=emergencyCallData.ProviderInfo 1739 Geolocation: 1740 Geolocation-Routing: yes 1741 Accept: application/sdp, application/pidf+xml, 1742 application/emergencyCallData.ProviderInfo+xml 1743 CSeq: 31862 INVITE 1744 Contact: 1745 Content-Type: multipart/mixed; boundary=boundary1 1747 Content-Length: ... 1749 --boundary1 1751 Content-Type: application/sdp 1753 ...SDP goes here 1755 --boundary1-- 1757 Content-Type: application/emergencyCallData.DevInfo+xml 1758 Content-ID: <1234567890@atlanta.example.com> 1759 Content-Disposition: by-reference;handling=optional 1760 1762 1765 12345 1766 SoftPhn 1767 00-0d-4b-30-72-df 1768 MAC 1769 1771 --boundary1-- 1773 Content-Type: application/emergencyCallData.ProviderInfo+xml 1774 Content-ID: <1234567890@atlanta.example.com> 1775 Content-Disposition: by-reference;handling=optional 1776 1777 1780 12345 1781 Hannes Tschofenig 1782 1784 Other 1785 sip:hannes@example.com 1786 EN 1787 1789 1790 Hannes Tschofenig 1791 1792 Hannes 1793 Tschofenig 1794 1795 1796 Dipl. Ing. 1797 1798 --0203 1799 1800 20090808T1430-0500 1801 1802 M 1803 1804 1 1805 1806 de 1807 1808 1809 2 1810 1811 en 1812 1813 1814 1815 work 1816 1820 1821 1822 1823 Linnoitustie 6 1824 Espoo 1825 Uusimaa 1826 02600 1827 Finland 1828 1829 1830 1831 1832 work 1833 voice 1834 1835 1836 tel:+358 50 4871445 1837 1838 1839 work 1840 1841 hannes.tschofenig@nsn.com 1842 1843 1844 work 1845 1846 geo:60.210796,24.812924 1847 1848 1849 1850 home 1851 1852 https://www.example.com/key.asc 1853 1854 1855 Finland/Helsinki 1856 1857 home 1858 1859 http://example.com/hannes.tschofenig 1860 1861 1862 1863 1865 --boundary1-- 1867 Content-Type: application/emergencyCall.SvcInfo+xml 1868 Content-ID: <1234567890@atlanta.example.com> 1869 Content-Disposition: by-reference;handling=optional 1870 1871 1874 abc123 1875 Residence 1876 VOIP 1877 Unknown 1878 1879 --boundary1-- 1881 Content-Type: application/emergencyCallData.ProviderInfo+xml 1882 Content-ID: <1234567890@atlanta.example.com> 1883 Content-Disposition: by-reference;handling=optional 1884 1885 1888 abc123 1889 Example VoIP Provider 1890 1891 urn:nena:companyid:ID123 1892 NENA 1893 Service Provider 1894 sip:voip-provider@example.com 1895 EN 1896 1898 1899 John Doe 1900 1901 John 1902 Doe 1903 1904 1905 1906 1907 --0203 1908 1909 20090808T1430-0500 1910 1911 M 1912 1913 1 1914 1915 en 1916 1917 1918 work 1919 1920 Example VoIP Provider 1921 1922 1923 1924 work 1925 1928 1929 1930 1931 Downing Street 10 1932 London 1933 1934 SW1A 2AA 1935 UK 1936 1937 1938 1939 1940 work 1941 voice 1942 1943 1944 sips:john.doe@example.com 1945 1946 1947 work 1948 1949 john.doe@example.com 1950 1951 1952 work 1953 1954 geo:51.503396, 0.127640 1955 1956 Europe/London 1957 1958 home 1959 1960 http://www.example.com/john.doe 1961 1962 1963 1964 1966 Figure 13: VoIP Provider sending SIP INVITE with Additional Data. 1968 Finally, the PSAP requests location information from the access 1969 network operator. The response is shown in Figure 14. Along with 1970 the location information additional data is provided in the 1971 element of the PIDF-LO. 1973 1974 1979 1980 1981 1982 1984 AU 1985 NSW 1986 Wollongong 1987 North Wollongong 1988 Flinders 1989 Street 1990 Campbell Street 1991 Gilligan's Island 1992 Corner 1993 Video Rental Store 1994 2500 1995 Westerns and Classics 1996 store 1997 Private Box 15 1998 1999 2000 2001 true 2002 2003 2013-12-10T20:00:00Z 2004 2005 2006 802.11 2008 2011 2014 2015 2017 University of California, Irvine 2018 2019 urn:nena:companyid:uci 2020 NENA 2021 Other 2022 tel:+1 9498245222 2023 EN 2024 2026 2028 This is an example text. 2029 2031 2032 2033 2034 mac:00-0d-4b-30-72-df 2035 2013-07-09T20:57:29Z 2036 2037 2039 Figure 14: Access Network Provider returning PIDF-LO with Additional 2040 Data. 2042 6. XML Schemas 2044 This section defines the XML schemas of the five data blocks. 2045 Additionally, the Provided-By schema is specified. 2047 6.1. emergencyCallData.ProviderInfo XML Schema 2049 2050 2060 2063 2065 2066 2067 2069 2070 2072 2076 2077 2078 2079 2080 2081 2083 2084 2085 2088 2091 2094 2097 2100 2103 2106 2110 2113 2116 2118 2119 2121 2123 Figure 15: emergencyCallData.ProviderInfo XML Schema. 2125 6.2. emergencyCallData.SvcInfo XML Schema 2127 2128 2136 2139 2141 2142 2143 2146 2149 2152 2155 2158 2160 2161 2163 2164 Figure 16: emergencyCallData.SvcInfo XML Schema. 2166 6.3. emergencyCallData.DevInfo XML Schema 2168 2169 2176 2179 2181 2182 2183 2186 2189 2192 2195 2198 2201 2204 2207 2209 2210 2212 2214 Figure 17: emergencyCallData.DevInfo XML Schema. 2216 6.4. emergencyCallData.SubInfo XML Schema 2218 2219 2228 2231 2233 2235 2236 2237 2238 2241 2244 2246 2247 2248 2249 2251 2253 Figure 18: emergencyCallData.SubInfo XML Schema. 2255 6.5. emergencyCallData.Comment XML Schema 2257 2258 2266 2269 2271 2272 2273 2276 2280 2282 2283 2285 2286 2287 2288 2289 2290 2291 2293 2295 Figure 19: EmergencyCallData.Comment XML Schema. 2297 6.6. Provided-By XML Schema 2299 This section defines the Provided-By schema. 2301 2302 2315 2316 2317 2318 2319 2321 2323 2324 2325 2328 2332 2336 2339 2341 2343 2345 2346 2347 2348 2349 2351 2352 2354 2356 2357 2358 2360 2362 2363 2364 2367 2370 2373 2376 2380 2383 2384 2386 2388 Figure 20: Provided-By XML Schema. 2390 7. Security Considerations 2391 The information in this data structure will usually be considered 2392 private. HTTPS is specified to require the provider of the 2393 information to validate the credentials of the requester. While the 2394 creation of a public key infrastructure (PKI) that has global scope 2395 may be difficult, the alternatives to creating devices and services 2396 that can provide critical information securely are more daunting. 2397 The provider may enforce any policy it wishes to use, but PSAPs and 2398 responder agencies should deploy a PKI so that providers of 2399 additional data can check the certificate of the client and decide 2400 the appropriate policy to enforce based on that certificate. 2402 Ideally, the PSAP and emergency responders will be given credentials 2403 signed by an authority trusted by the data provider. In most 2404 circumstances, nationally recognized credentials would be sufficient, 2405 and if the emergency services arranges a PKI, data providers could be 2406 provisioned with the root CA public key for a given nation. Some 2407 nations are developing a PKI for this, and related, purposes. Since 2408 calls could be made from devices where the device and/or the service 2409 provider(s) are not local to the emergency authorities, globally 2410 recognized credentials are useful. This might be accomplished by 2411 extending the notion of the "forest guide" described in [RFC5222] to 2412 allow the forest guide to provide the credential of the PKI root for 2413 areas that it has coverage information for, but standards for such a 2414 mechanism are not yet available. In its absence, the data provider 2415 will need to obtain the root CA credentials for any areas it is 2416 willing to provide additional data by out of band means. With the 2417 credential of the root CA for a national emergency services PKI, the 2418 data provider server can validate the credentials of an entity 2419 requesting additional data by reference. 2421 The data provider also needs a credential that can be verified by the 2422 emergency services to know that it is receiving data from the right 2423 server. The emergency authorities could provide credentials, 2424 distinguishable from credentials it provides to emergency responders 2425 and PSAPs, which could be used to validate data providers. Such 2426 credentials would have to be acceptable to any PSAP or responder that 2427 could receive a call with additional data supplied by that provider. 2428 This would be extensible to global credential validation using the 2429 forest guide as above. In the absence of such credentials, the 2430 emergency authorities could maintain a list of local data providers' 2431 credentials provided to it out of band. At a minimum, the emergency 2432 authorities could obtain a credential from the DNS entry of the 2433 domain in the Additional Data URI to at least validate that the 2434 server is known to the domain providing the URI. 2436 Data provided by devices by reference have similar credential 2437 validation issues to service providers, and the solutions are the 2438 same. 2440 8. Privacy Considerations 2442 This document enables functionality for conveying additional 2443 information about the caller to the callee. Some of this information 2444 is personal data and therefore privacy concerns arise. An explicit 2445 privacy indicator for information directly relating to the callers 2446 identity is defined and use is mandatory. However, observance of 2447 this request for privacy and what information it relates to is 2448 controlled by the destination jurisdiction. 2450 There are a number of privacy concerns with regular real-time 2451 communication services that are also applicable to emergency calling. 2452 Data protection regulation world-wide has, however, decided to create 2453 exceptions for emergency services since the drawbacks of disclosing 2454 personal data in comparison to the benefit for the emergency caller 2455 are often towards the latter. Hence, the data protection rights of 2456 individuals are often waived for emergency situations. There are, 2457 however, still various countries that offer some degree of anonymity 2458 for the caller towards PSAP call takers. 2460 The functionality defined in this document, however, far exceeds the 2461 amount of information sharing found in the Plain old telephone system 2462 (POTS). For this reason there are additional privacy threats to 2463 consider, which are described in more detail in [RFC6973]. 2465 Stored Data Compromise: First, there is an increased risk of stored 2466 data compromise since additional data is collected and stored in 2467 databases. Without adequate measures to secure stored data from 2468 unauthorized or inappropriate access at access network operators, 2469 service providers, end devices, as well as PSAPs individuals are 2470 exposed to potential financial, reputational, or physical harm. 2472 Misattribution: If the personal data collected and conveyed is 2473 incorrect or inaccurate then this may lead to misattribution. 2474 Misattribution occurs when data or communications related to one 2475 individual are attributed to another. 2477 Identification: By the nature of the additional data and its 2478 capability to provide much richer information about the caller, 2479 the call, and the location the calling party is identified in a 2480 much better way. Some users may feel uncomfortable with this 2481 degree of information sharing even in emergency services 2482 situations. 2484 Secondary Use: Furthermore, there is the risk of secondary use. 2485 Secondary use is the use of collected information about an 2486 individual without the individual's consent for a purpose 2487 different from that for which the information was collected. The 2488 stated purpose of the additional data is for emergency services 2489 purposes but theoretically the same information could be used for 2490 any other call as well. Additionally, parties involved in the 2491 emergency call may retain the obtained information and may re-use 2492 it for other, non-emergency services purposes. 2494 Disclosure: When the data defined in this document is not properly 2495 security (while in transit with traditional communication security 2496 techniques, and while at rest using access control mechanisms) 2497 there is the risk of disclosure, which is the revelation of 2498 information about an individual that affects the way others judge 2499 the individual. 2501 To mitigate these privacy risks the following countermeasures can be 2502 taken. 2504 In regions where callers can elect to suppress certain personally 2505 identifying information, the network or PSAP functionality can 2506 inspect privacy flags within the SIP headers to determine what 2507 information may be passed, stored, or displayed to comply with local 2508 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2509 The presence of this privacy type in a Privacy header field indicates 2510 that the user would like the network asserted identity to be kept 2511 private with respect to SIP entities outside the trust domain with 2512 which the user authenticated, including the PSAP. 2514 This document defines various data structures that constitutes 2515 personal data. Local regulations may govern what data must be 2516 provided in emergency calls, but in general, the emergency call 2517 system is often aided by the kinds of information described in this 2518 document. There is a tradeoff between the privacy considerations and 2519 the utility of the data. For adequate protection this specification 2520 requires all data exchanges to be secured via communication security 2521 techniques (namely TLS) against eavesdropping and inception. 2522 Furthermore, security safeguards are required to prevent unauthorized 2523 access to data at rest. Various security incidents over the last 10 2524 years have shown data breaches are not not uncommon and are often 2525 caused by lack of proper access control frameworks, software bugs 2526 (buffer overflows), or missing input parsing (SQL injection attacks). 2527 The risks of data breaches is increased with the obligation for 2528 emergency services to retain emergency call related data for extended 2529 periods, e.g., several years are the norm. 2531 Finally, it is also worth to highlight the nature of the SIP 2532 communication architecture, which introduces additional complications 2533 for privacy. Some forms of data can be sent by value in the SIP 2534 signaling or by value (URL in SIP signaling). When data is sent by 2535 value, all intermediaries have access to the data. As such, these 2536 intermediaries may also introduce additional privacy risk. 2537 Therefore, in situations where the conveyed information raises 2538 privacy concerns and intermediaries are involved transmitting a 2539 reference is more appropriate (assuming proper access control 2540 policies are available for distinguishing the different entities 2541 dereferencing the reference). Without access control policies any 2542 party in possession of the reference is able to resolve the reference 2543 and to obtain the data, including intermediaries. 2545 9. IANA Considerations 2547 9.1. Registry creation 2549 This document creates a new registry called 'Emergency Call 2550 Additional Data'. The following sub-registries are created for this 2551 registry. 2553 9.1.1. Provider ID Series Registry 2555 This document creates a new sub-registry called 'Additional Call Data 2556 Provider ID Series'. As defined in [RFC5226], this registry operates 2557 under "Expert Review" rules. The expert should determine that the 2558 entity requesting a new value is a legitimate issuer of service 2559 provider IDs suitable for use in Additional Call Data. 2561 The content of this registry includes: 2563 Name: The identifier which will be used in the ProviderIDSeries 2564 element 2566 Source: The full name of the organization issuing the identifiers 2568 URL: A URL to the organization for further information 2570 The initial set of values is listed in Figure 21. 2572 +-----------+--------------------------+----------------------+ 2573 | Name | Source | URL | 2574 +-----------+--------------------------+----------------------+ 2575 | NENA | National Emergency | http://www.nena.org | 2576 | | Number Association | | 2577 | EENA | European Emergency | http://www.eena.org | 2578 | | Number Association | | 2579 +-----------+--------------------------+----------------------+ 2581 Figure 21: Provider ID Series Registry. 2583 9.1.2. Service Environment Registry 2585 This document creates a new sub-registry called 'Additional Call 2586 Service Environment'. As defined in [RFC5226], this registry 2587 operates under "Expert Review" rules. The expert should determine 2588 that the entity requesting a new value is relevant for this service 2589 element. 2591 The content of this registry includes: 2593 Token: The value to be used in element. 2595 Description: A short description of the token. 2597 The initial set of values is listed in Figure 22. 2599 +-----------+--------------------------+ 2600 | Token | Description | 2601 +-----------+--------------------------+ 2602 | Business | [[This RFC]] | 2603 | Residence | [[This RFC]] | 2604 +-----------+--------------------------+ 2606 Figure 22: Service Environment Registry. 2608 9.1.3. Service Provider Type Registry 2610 This document creates a new sub-registry called 'Service Provider 2611 Type'. As defined in [RFC5226], this registry operates under "Expert 2612 Review". The expert should determine that the proposed new value is 2613 distinct from existing values and appropriate for use in the 2614 TypeOfServicerProvider element 2616 The content of this registry includes: 2618 Name: The value to be used in TypeOfServiceProvider. 2620 Description: A short description of the type of service provider 2622 The initial set of values is defined in Figure 1. 2624 9.1.4. Service Delivered Registry 2626 This document creates a new sub-registry called 'Service Delivered'. 2627 As defined in [RFC5226], this registry operates under "Expert Review" 2628 rules. The expert should consider whether the proposed service is 2629 unique from existing services and the definition of the service will 2630 be clear to implementors and PSAPS/responders. 2632 The content of this registry includes: 2634 Name: Enumeration token of the service. 2636 Description: Short description identifying the service. 2638 The initial set of values are defined in Figure 3. 2640 9.1.5. Device Classification Registry 2642 This document creates a new sub-registry called 'Device 2643 Classification'. As defined in [RFC5226], this registry operates 2644 under "Expert Review" rules. The expert should consider whether the 2645 proposed class is unique from existing classes and the definition of 2646 the class will be clear to implementors and PSAPS/responders. 2648 The content of this registry includes: 2650 Name: Enumeration token of the device classification. 2652 Description: Short description identifying the device type. 2654 The initial set of values are defined in Figure 5. 2656 9.1.6. Device ID Type Type Registry 2658 This document creates a new sub-registry called 'Additional Call Data 2659 Device ID Type'. As defined in [RFC5226], this registry operates 2660 under "Expert Review" rules. The expert should ascertain that the 2661 proposed type is well understood, and provides the information useful 2662 to PSAPs and responders to uniquely identify a device. 2664 The content of this registry includes: 2666 Name: Enumeration token of the device id type. 2668 Description: Short description identifying type of device id. 2670 The initial set of values are defined in Figure 6. 2672 9.1.7. Device/Service Data Type Registry 2674 This document creates a new sub-registry called 'Device/Service Data 2675 Type Registry'. As defined in [RFC5226], this registry operates 2676 under "Expert Review" and "Specification Required" rules. The expert 2677 should ascertain that the proposed type is well understood, and 2678 provides information useful to PSAPs and responders. The 2679 specification must contain a complete description of the data, and a 2680 precise format specification suitable to allow interoperable 2681 implementations. 2683 The content of this registry includes: 2685 Name: Enumeration token of the data type. 2687 Description: Short description identifying the the data. 2689 Specification: Citation for the specification of the data. 2691 The initial set of values are listed in Figure 23. 2693 +---------+----------------------------------------+----------------+ 2694 | Token | Description | Specification | 2695 +---------+----------------------------------------+----------------+ 2696 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2697 +---------+----------------------------------------+----------------+ 2698 | VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS | 2699 +---------+----------------------------------------+----------------+ 2701 Figure 23: Device/Service Data Type Registry. 2703 9.1.8. Additional Data Blocks Registry 2705 This document creates a new sub-registry called 'Additional Data 2706 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2707 As defined in [RFC5226], this registry operates under "Expert Review" 2708 and "Specification Required" rules. The expert is responsible for 2709 verifying that the document contains a complete and clear 2710 specification and the proposed functionality does not obviously 2711 duplicate existing functionality. 2713 The content of this registry includes: 2715 Name: Element Name of enclosing block. 2717 Reference: The document that describes the block 2719 The initial set of values are listed in Figure 24. 2721 +--------------+------------+ 2722 | Token | Reference | 2723 +--------------+------------+ 2724 | ProviderInfo | [This RFC] | 2725 | SvcInfo | [This RFC] | 2726 | DevInfo | [This RFC] | 2727 | Subscriber | [This RFC] | 2728 | Comment | [This RFC] | 2729 +--------------+------------+ 2731 Figure 24: Additional Data Blocks Registry. 2733 9.2. 'emergencyCallData' Purpose Parameter Value 2735 This document defines the 'emergencyCallData' value for the "purpose" 2736 parameter of the Call-Info header field. The Call-Info header and 2737 the corresponding registry for the 'purpose' parameter was 2738 established with RFC 3261 [RFC3261]. 2740 Header Parameter New 2741 Field Name Value Reference 2742 ---------- --------- ----------------- --------- 2743 Call-Info purpose emergencyCallData [This RFC] 2745 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2747 This section registers the namespace specified in Section 9.5.1 in 2748 the provided-by registry established by RFC 4119, for usage within 2749 the element of a PIDF-LO. 2751 The schema for the provided-by schema used by this document is 2752 specified in Section 6.6. 2754 9.4. MIME Registrations 2756 9.4.1. MIME Content-type Registration for 'application/ 2757 emergencyCallData.ProviderInfo+xml' 2759 This specification requests the registration of a new MIME type 2760 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2761 RFC 3023 [RFC3023]. 2763 MIME media type name: application 2765 MIME subtype name: emergencyCallData.ProviderInfo+xml 2767 Mandatory parameters: none 2769 Optional parameters: charset Indicates the character encoding of 2770 enclosed XML. 2772 Encoding considerations: Uses XML, which can employ 8-bit 2773 characters, depending on the character encoding used. See 2774 Section 3.2 of RFC 3023 [RFC3023]. 2776 Security considerations: This content type is designed to carry 2777 the data provider information, which is a sub-category of 2778 additional data about an emergency call. Since this data contains 2779 personal information appropriate precautions have to be taken to 2780 limit unauthorized access, inappropriate disclosure to third 2781 parties, and eavesdropping of this information. Please refer to 2782 Section 7 and Section 8 for more information. 2784 Interoperability considerations: None 2786 Published specification: [TBD: This specification] 2788 Applications which use this media type: Emergency Services 2790 Additional information: Magic Number: None File Extension: .xml 2791 Macintosh file type code: 'TEXT' 2793 Person and email address for further information: Hannes 2794 Tschofenig, Hannes.Tschofenig@gmx.net 2796 Intended usage: LIMITED USE 2798 Author: This specification is a work item of the IETF ECRIT 2799 working group, with mailing list address . 2801 Change controller: The IESG 2803 9.4.2. MIME Content-type Registration for 'application/ 2804 emergencyCallData.SvcInfo+xml' 2806 This specification requests the registration of a new MIME type 2807 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2808 RFC 3023 [RFC3023]. 2810 MIME media type name: application 2812 MIME subtype name: emergencyCallData.SvcInfo+xml 2814 Mandatory parameters: none 2816 Optional parameters: charset Indicates the character encoding of 2817 enclosed XML. 2819 Encoding considerations: Uses XML, which can employ 8-bit 2820 characters, depending on the character encoding used. See 2821 Section 3.2 of RFC 3023 [RFC3023]. 2823 Security considerations: This content type is designed to carry 2824 the service information, which is a sub-category of additional 2825 data about an emergency call. Since this data contains personal 2826 information appropriate precautions have to be taken to limit 2827 unauthorized access, inappropriate disclosure to third parties, 2828 and eavesdropping of this information. Please refer to Section 7 2829 and Section 8 for more information. 2831 Interoperability considerations: None 2833 Published specification: [TBD: This specification] 2835 Applications which use this media type: Emergency Services 2837 Additional information: Magic Number: None File Extension: .xml 2838 Macintosh file type code: 'TEXT' 2840 Person and email address for further information: Hannes 2841 Tschofenig, Hannes.Tschofenig@gmx.net 2843 Intended usage: LIMITED USE 2845 Author: This specification is a work item of the IETF ECRIT 2846 working group, with mailing list address . 2848 Change controller: The IESG 2850 9.4.3. MIME Content-type Registration for 'application/ 2851 emergencyCallData.DevInfo+xml' 2853 This specification requests the registration of a new MIME type 2854 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2855 RFC 3023 [RFC3023]. 2857 MIME media type name: application 2859 MIME subtype name: emergencyCallData.DevInfo+xml 2861 Mandatory parameters: none 2863 Optional parameters: charset Indicates the character encoding of 2864 enclosed XML. 2866 Encoding considerations: Uses XML, which can employ 8-bit 2867 characters, depending on the character encoding used. See 2868 Section 3.2 of RFC 3023 [RFC3023]. 2870 Security considerations: This content type is designed to carry 2871 the device information information, which is a sub-category of 2872 additional data about an emergency call. Since this data contains 2873 personal information appropriate precautions have to be taken to 2874 limit unauthorized access, inappropriate disclosure to third 2875 parties, and eavesdropping of this information. Please refer to 2876 Section 7 and Section 8 for more information. 2878 Interoperability considerations: None 2880 Published specification: [TBD: This specification] 2882 Applications which use this media type: Emergency Services 2884 Additional information: Magic Number: None File Extension: .xml 2885 Macintosh file type code: 'TEXT' 2887 Person and email address for further information: Hannes 2888 Tschofenig, Hannes.Tschofenig@gmx.net 2890 Intended usage: LIMITED USE 2892 Author: This specification is a work item of the IETF ECRIT 2893 working group, with mailing list address . 2895 Change controller: The IESG 2897 9.4.4. MIME Content-type Registration for 'application/ 2898 emergencyCallData.SubInfo+xml' 2900 This specification requests the registration of a new MIME type 2901 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2902 RFC 3023 [RFC3023]. 2904 MIME media type name: application 2906 MIME subtype name: emergencyCallData.SubInfo+xml 2908 Mandatory parameters: none 2910 Optional parameters: charset Indicates the character encoding of 2911 enclosed XML. 2913 Encoding considerations: Uses XML, which can employ 8-bit 2914 characters, depending on the character encoding used. See 2915 Section 3.2 of RFC 3023 [RFC3023]. 2917 Security considerations: This content type is designed to carry 2918 owner/subscriber information, which is a sub-category of 2919 additional data about an emergency call. Since this data contains 2920 personal information appropriate precautions have to be taken to 2921 limit unauthorized access, inappropriate disclosure to third 2922 parties, and eavesdropping of this information. Please refer to 2923 Section 7 and Section 8 for more information. 2925 Interoperability considerations: None 2927 Published specification: [TBD: This specification] 2929 Applications which use this media type: Emergency Services 2931 Additional information: Magic Number: None File Extension: .xml 2932 Macintosh file type code: 'TEXT' 2934 Person and email address for further information: Hannes 2935 Tschofenig, Hannes.Tschofenig@gmx.net 2937 Intended usage: LIMITED USE 2939 Author: This specification is a work item of the IETF ECRIT 2940 working group, with mailing list address . 2942 Change controller: The IESG 2944 9.4.5. MIME Content-type Registration for 'application/ 2945 emergencyCallData.Comment+xml' 2947 This specification requests the registration of a new MIME type 2948 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2949 RFC 3023 [RFC3023]. 2951 MIME media type name: application 2953 MIME subtype name: emergencyCallData.Comment+xml 2955 Mandatory parameters: none 2957 Optional parameters: charset Indicates the character encoding of 2958 enclosed XML. 2960 Encoding considerations: Uses XML, which can employ 8-bit 2961 characters, depending on the character encoding used. See 2962 Section 3.2 of RFC 3023 [RFC3023]. 2964 Security considerations: This content type is designed to carry a 2965 comment, which is a sub-category of additional data about an 2966 emergency call. This data may contain personal information. 2967 Appropriate precautions may have to be taken to limit unauthorized 2968 access, inappropriate disclosure to third parties, and 2969 eavesdropping of this information. Please refer to Section 7 and 2970 Section 8 for more information. 2972 Interoperability considerations: None 2974 Published specification: [TBD: This specification] 2976 Applications which use this media type: Emergency Services 2978 Additional information: Magic Number: None File Extension: .xml 2979 Macintosh file type code: 'TEXT' 2981 Person and email address for further information: Hannes 2982 Tschofenig, Hannes.Tschofenig@gmx.net 2984 Intended usage: LIMITED USE 2986 Author: This specification is a work item of the IETF ECRIT 2987 working group, with mailing list address . 2989 Change controller: The IESG 2991 9.5. URN Sub-Namespace Registration 2993 9.5.1. Registration for urn:ietf:params:xml:ns:emergencycalldata 2995 This section registers a new XML namespace, as per the guidelines in 2996 RFC 3688 [RFC3688]. 2998 URI: urn:ietf:params:xml:ns:emergencycalldata 3000 Registrant Contact: IETF, ECRIT working group, , as 3001 delegated by the IESG . 3003 XML: 3005 BEGIN 3006 3007 3009 3010 3011 3013 Namespace for Additional Emergency Call Data 3014 3015 3016

Namespace for Additional Data related to an Emergency Call

3017

See [TBD: This document].

3018 3019 3020 END 3022 9.5.2. Registration for 3023 urn:ietf:params:xml:ns:emergencycalldata:providerinfo 3025 This section registers a new XML namespace, as per the guidelines in 3026 RFC 3688 [RFC3688]. 3028 URI: urn:ietf:params:xml:ns:emergencycalldata:providerinfo 3030 Registrant Contact: IETF, ECRIT working group, , as 3031 delegated by the IESG . 3033 XML: 3035 BEGIN 3036 3037 3039 3040 3041 3043 Namespace for Additional Emergency Call Data: 3044 Data Provider Information 3045 3046 3047

Namespace for Additional Data related to an Emergency Call

3048

Data Provider Information

3049

See [TBD: This document].

3050 3051 3052 END 3054 9.5.3. Registration for 3055 urn:ietf:params:xml:ns:emergencycalldata:svcinfo 3057 This section registers a new XML namespace, as per the guidelines in 3058 RFC 3688 [RFC3688]. 3060 URI: urn:ietf:params:xml:ns:emergencycalldata:svcinfo 3062 Registrant Contact: IETF, ECRIT working group, , as 3063 delegated by the IESG . 3065 XML: 3067 BEGIN 3068 3069 3071 3072 3073 3075 Namespace for Additional Emergency Call Data: 3076 Service Information 3077 3078 3079

Namespace for Additional Data related to an Emergency Call

3080

Service Information

3081

See [TBD: This document].

3082 3083 3084 END 3086 9.5.4. Registration for 3087 urn:ietf:params:xml:ns:emergencycalldata:devinfo 3089 This section registers a new XML namespace, as per the guidelines in 3090 RFC 3688 [RFC3688]. 3092 URI: urn:ietf:params:xml:ns:emergencycalldata:devinfo 3093 Registrant Contact: IETF, ECRIT working group, , as 3094 delegated by the IESG . 3096 XML: 3098 BEGIN 3099 3100 3102 3103 3104 3106 Namespace for Additional Emergency Call Data: 3107 Device Information 3108 3109 3110

Namespace for Additional Data related to an Emergency Call

3111

Device Information

3112

See [TBD: This document].

3113 3114 3115 END 3117 9.5.5. Registration for 3118 urn:ietf:params:xml:ns:emergencycalldata:subinfo 3120 This section registers a new XML namespace, as per the guidelines in 3121 RFC 3688 [RFC3688]. 3123 URI: urn:ietf:params:xml:ns:emergencycalldata:subinfo 3125 Registrant Contact: IETF, ECRIT working group, , as 3126 delegated by the IESG . 3128 XML: 3130 BEGIN 3131 3132 3134 3135 3136 3138 Namespace for Additional Emergency Call Data: 3139 Owner/Subscriber Information 3140 3141 3142

Namespace for Additional Data related to an Emergency Call

3143

Owner/Subscriber Information

3144

See [TBD: This document].

3145 3146 3147 END 3149 9.5.6. Registration for 3150 urn:ietf:params:xml:ns:emergencycalldata:comment 3152 This section registers a new XML namespace, as per the guidelines in 3153 RFC 3688 [RFC3688]. 3155 URI: urn:ietf:params:xml:ns:emergencycalldata:comment 3157 Registrant Contact: IETF, ECRIT working group, , as 3158 delegated by the IESG . 3160 XML: 3162 BEGIN 3163 3164 3166 3167 3168 3170 Namespace for Additional Emergency Call Data:Comment 3171 3172 3173

Namespace for Additional Data related to an Emergency Call

3174

Comment

3175

See [TBD: This document].

3176 3177 3178 END 3180 9.6. Schema Registrations 3182 This specification registers five schemas, as per the guidelines in 3183 RFC 3688 [RFC3688]. 3185 URI: urn:ietf:params:xml:schema:emergencycalldata:providerinfo 3187 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3188 delegated by the IESG (iesg@ietf.org). 3190 XML: The XML schema can be found in Figure 15. 3192 URI: urn:ietf:params:xml:schema:emergencycalldata:svcinfo 3194 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 3195 delegated by the IESG (iesg@ietf.org). 3197 XML: The XML schema can be found in Figure 16. 3199 URI: urn:ietf:params:xml:schema:emergencycalldata:devinfo 3201 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3202 delegated by the IESG (iesg@ietf.org). 3204 XML: The XML schema can be found in Figure 17. 3206 URI: urn:ietf:params:xml:schema:emergencycalldata:subinfo 3208 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3209 delegated by the IESG (iesg@ietf.org). 3211 XML: The XML schema can be found in Section 6.4. 3213 URI: urn:ietf:params:xml:schema:emergencycalldata:comment 3215 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 3216 delegated by the IESG (iesg@ietf.org). 3218 XML: The XML schema can be found in Section 6.5. 3220 9.7. VCard Parameter Value Registration 3222 This document registers a new value in the vCARD Parameter Values 3223 registry as defined by [RFC6350] with the following template: 3225 Value: main 3226 Purpose: The main telephone number, typically of an enterprise, as 3227 opposed to a direct dial number of an individual employee 3229 Conformance: This value can be used with the "TYPE" parameter 3230 applied on the "TEL" property. 3232 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 3233 00 3235 10. Acknowledgments 3237 This work was originally started in NENA and has benefitted from a 3238 large number of participants in NENA standardization efforts, 3239 originally in the Long Term Definition Working Group, the Data 3240 Technical Committee and most recently the Additional Data working 3241 group. The authors are grateful for the initial work and extended 3242 comments provided by many NENA participants, including Delaine 3243 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 3244 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 3245 and Robert (Bob) Sherry. 3247 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 3248 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 3249 comments. 3251 11. References 3253 11.1. Normative References 3255 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3256 Requirement Levels", BCP 14, RFC 2119, March 1997. 3258 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 3259 Locators", RFC 2392, August 1998. 3261 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 3262 Types", RFC 3023, January 2001. 3264 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 3265 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 3266 and QSIG Objects", RFC 3204, December 2001. 3268 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 3269 A., Peterson, J., Sparks, R., Handley, M., and E. 3270 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 3271 June 2002. 3273 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 3274 Extensions to the Session Initiation Protocol (SIP) for 3275 Asserted Identity within Trusted Networks", RFC 3325, 3276 November 2002. 3278 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 3279 Extensions (MIME) Parameter", RFC 3459, January 2003. 3281 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 3282 January 2004. 3284 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 3285 Format", RFC 4119, December 2005. 3287 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 3288 Registration Procedures", RFC 4288, December 2005. 3290 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3291 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 3292 May 2008. 3294 [RFC5621] Camarillo, G., "Message Body Handling in the Session 3295 Initiation Protocol (SIP)", RFC 5621, September 2009. 3297 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 3298 August 2011. 3300 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 3301 6351, August 2011. 3303 11.2. Informational References 3305 [I-D.gellens-negotiating-human-language] 3306 Randy, R., "Negotiating Human Language Using SDP", draft- 3307 gellens-negotiating-human-language-02 (work in progress), 3308 February 2013. 3310 [I-D.ietf-ecrit-psap-callback] 3311 Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. 3312 Patel, "Public Safety Answering Point (PSAP) Callback", 3313 draft-ietf-ecrit-psap-callback-13 (work in progress), 3314 October 2013. 3316 [I-D.ietf-geopriv-relative-location] 3317 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 3318 Thomson, "Relative Location Representation", draft-ietf- 3319 geopriv-relative-location-08 (work in progress), September 3320 2013. 3322 [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, 3323 "Indicating User Agent Capabilities in the Session 3324 Initiation Protocol (SIP)", RFC 3840, August 2004. 3326 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 3327 Emergency Context Resolution with Internet Technologies", 3328 RFC 5012, January 2008. 3330 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 3331 Format for Presence Information Data Format Location 3332 Object (PIDF-LO)", RFC 5139, February 2008. 3334 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 3335 Tschofenig, "LoST: A Location-to-Service Translation 3336 Protocol", RFC 5222, August 2008. 3338 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 3339 Presence Information Data Format Location Object (PIDF-LO) 3340 Usage Clarification, Considerations, and Recommendations", 3341 RFC 5491, March 2009. 3343 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 3344 Thomson, "Dynamic Extensions to the Presence Information 3345 Data Format Location Object (PIDF-LO)", RFC 5962, 3346 September 2010. 3348 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 3349 5985, September 2010. 3351 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 3352 "Framework for Emergency Calling Using Internet 3353 Multimedia", RFC 6443, December 2011. 3355 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 3356 R. George, "Specifying Civic Address Extensions in the 3357 Presence Information Data Format Location Object (PIDF- 3358 LO)", RFC 6848, January 2013. 3360 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 3361 Communications Services in Support of Emergency Calling", 3362 BCP 181, RFC 6881, March 2013. 3364 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 3365 Morris, J., Hansen, M., and R. Smith, "Privacy 3366 Considerations for Internet Protocols", RFC 6973, July 3367 2013. 3369 Appendix A. XML Schema for vCard/xCard 3371 This section contains the vCard/xCard XML schema version of the Relax 3372 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 3373 XML schemas defined in this document. The schema in RFC 6351 3374 [RFC6351] is the normative source and this section is informative 3375 only. 3377 3378 3382 3388 3389 3390 vCard Format Specification 3391 3392 3393 3394 3395 3396 3397 3398 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3413 3414 3415 3417 3418 3419 3420 3421 3423 3424 3425 3427 3428 3429 3430 3431 3433 3434 3435 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3480 3481 3482 3483 3487 3488 3489 Section 5: Parameters 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 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 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3949 3950 3951 3952 3953 3954 3955 3956 3957 3958 3959 3960 3961 3962 3963 3964 3965 3966 3967 3968 3969 3970 3971 3972 3973 3974 3975 3976 3977 3978 3979 3980 3981 3982 3983 3984 3985 3986 3987 3988 3989 3990 3991 3992 3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003 4004 4005 4006 4007 4008 4009 4010 4011 4012 4013 4014 4015 4016 4017 4018 4019 4020 4021 4022 4023 4024 4025 4026 4027 4028 4029 4030 4031 4032 4033 4034 4035 4036 4037 4038 4039 4040 4041 4042 4043 4044 4045 4046 4047 4048 4049 4050 4051 4052 4053 4054 4055 4056 4057 4058 4059 4060 4061 4062 4063 4064 4065 4066 4067 4068 4069 4070 4071 4072 4073 4074 4075 4076 4077 4078 4079 4080 4081 4082 4083 4084 4085 4086 4087 4089 4090 4091 4092 4093 4094 4095 4096 4097 4098 4099 4100 4101 4102 4103 4104 4105 4106 4107 4108 4109 4110 4111 4112 4113 4114 4115 4116 4117 4118 4119 4120 4121 4122 4123 4124 4125 4126 4127 4128 4129 4130 4131 4132 4133 4134 4135 4136 4137 4138 4139 4140 4141 4142 4143 4144 4145 4146 4147 4148 4149 4150 4151 4152 4153 4154 4155 4156 4157 4158 4159 4160 4161 4162 4163 4164 4165 4166 4167 4168 4169 4170 4171 4172 4173 4174 4175 4176 4177 4178 4179 4180 4181 4182 4183 4184 4186 4187 4188 4189 4190 4191 4192 4193 4194 4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 4285 4286 4287 4288 4289 4290 4291 4292 4293 4294 4295 4296 4297 4298 4299 4300 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311 4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 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 4412 4413 4414 4415 4416 4417 4418 4420 4421 4422 4423 4424 4425 4426 4428 4429 4430 4432 4434 4435 4436 4438 4439 4440 4441 4443 Authors' Addresses 4445 Brian Rosen 4446 NeuStar 4447 470 Conrad Dr. 4448 Mars, PA 16046 4449 US 4451 Phone: +1 724 382 1051 4452 Email: br@brianrosen.net 4454 Hannes Tschofenig 4455 Nokia Solutions and Networks 4456 Linnoitustie 6 4457 Espoo 02600 4458 Finland 4460 Phone: +358 (50) 4871445 4461 Email: Hannes.Tschofenig@gmx.net 4462 URI: http://www.tschofenig.priv.at 4463 Roger Marshall 4464 TeleCommunication Systems, Inc. 4465 2401 Elliott Avenue 4466 Seattle, WA 98121 4467 US 4469 Phone: +1 206 792 2424 4470 Email: rmarshall@telecomsys.com 4471 URI: http://www.telecomsys.com 4473 Randall Gellens 4474 Qualcomm Technologies, Inc. 4475 5775 Morehouse Drive 4476 San Diego, CA 92121 4477 US 4479 Email: rg+ietf@qti.qualcomm.com 4481 James Winterbottom 4482 AU 4484 Email: a.james.winterbottom@gmail.com