idnits 2.17.00 (12 Aug 2021) /tmp/idnits42426/draft-ietf-ecrit-additional-data-08.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 28 instances of too long lines in the document, the longest one being 11 characters in excess of 72. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1933 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 (May 05, 2013) is 3302 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 1933, but not defined == Unused Reference: 'I-D.iab-privacy-considerations' is defined on line 2561, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: draft-iab-privacy-considerations has been published as RFC 6973 Summary: 4 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ECRIT B.R. Rosen 3 Internet-Draft NeuStar 4 Intended status: Standards Track H. Tschofenig 5 Expires: November 06, 2013 Nokia Siemens Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 May 05, 2013 12 Additional Data related to an Emergency Call 13 draft-ietf-ecrit-additional-data-08.txt 15 Abstract 17 When an emergency call is sent to a Public Safety Answering Point 18 (PSAP), the device that sends it, as well as any application service 19 provider in the path of the call, or access network provider through 20 which the call originated may have information about the call or the 21 caller which the PSAP may be able to use. This document describes 22 data structures to convey such data to the PSAP. In addition, data 23 may also be included by reference, via a Uniform Resource Identifier 24 (URI) pointing to data found at an external resource. Consequently, 25 this document follows the tradition of prior emergency services 26 standardization work where data can be conveyed by value within the 27 call signaling (i.e., in body of the SIP message) and also by 28 reference. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on November 06, 2013. 47 Copyright Notice 48 Copyright (c) 2013 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 3. Data Structure Overview . . . . . . . . . . . . . . . . . . . 6 66 4. Transmitting Blocks of Additional Data . . . . . . . . . . . 7 67 4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 8 68 4.2. Transmitting blocks by reference using Provided-By . . . 9 69 4.3. Transmitting blocks by value using Provided-By . . . . . 9 70 5. Data Provider Information . . . . . . . . . . . . . . . . . . 10 71 5.1. Data Provider String . . . . . . . . . . . . . . . . . . 10 72 5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . 11 73 5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 11 74 5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 12 75 5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 13 76 5.6. Data Provider Languages(s) Supported . . . . . . . . . . 13 77 5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . 14 78 5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 15 79 5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . 15 80 5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 16 81 5.11. emergencyCall.ProviderInfo Example . . . . . . . . . . . 17 82 6. Service Information . . . . . . . . . . . . . . . . . . . . . 19 83 6.1. Service Environment . . . . . . . . . . . . . . . . . . . 19 84 6.2. Service Delivered by Provider to End User . . . . . . . . 20 85 6.3. Service Mobility Environment . . . . . . . . . . . . . . 21 86 6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 22 87 6.5. emergencyCall.SvcInfo Example . . . . . . . . . . . . . . 22 88 7. Device Information . . . . . . . . . . . . . . . . . . . . . 23 89 7.1. Device Classification . . . . . . . . . . . . . . . . . . 23 90 7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 25 91 7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 25 92 7.4. Unique Device Identifier . . . . . . . . . . . . . . . . 26 93 7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 26 94 7.6. Device/Service Specific Additional Data Structure . . . . 27 95 7.7. Device/Service Specific Additional Data Structure Type . 28 96 7.8. Choosing between defining a new type of block or new type 97 of device/service specific additional data . . . . . . . 28 98 7.9. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 29 99 7.10. emergencyCall.DevInfo Example . . . . . . . . . . . . . . 30 100 8. Owner/Subscriber Information . . . . . . . . . . . . . . . . 30 101 8.1. xCard for Subscriber's Data . . . . . . . . . . . . . . . 30 102 8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 31 103 8.3. emergencyCall.SubInfo Example . . . . . . . . . . . . . . 32 104 9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 105 9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 34 106 9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . 34 107 9.3. emergencyCall.Comment Example . . . . . . . . . . . . . . 35 108 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 109 11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 36 110 12. Security Considerations . . . . . . . . . . . . . . . . . . . 37 111 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 38 112 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38 113 14.1. Registry creation . . . . . . . . . . . . . . . . . . . 38 114 14.1.1. Additional Call Data Provider ID Series Registry . . 38 115 14.1.2. Additional Call Data Service Provider Type Registry 39 116 14.1.3. Additional Call Data Service Delivered Registry . . 40 117 14.1.4. Additional Call Data Device Classification Registry 41 118 14.1.5. Additional Call Data Device ID Type Type Registry . 42 119 14.1.6. Device/Service Specific Additional Data Type 120 Registry . . . . . . . . . . . . . . . . . . . . . . 42 121 14.1.7. Additional Call Data Blocks Registry . . . . . . . . 43 122 14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . 43 123 14.3. URN Sub-Namespace Registration for provided-by Registry 124 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 44 125 14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 44 126 14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 45 127 14.4.1. MIME Content-type Registration for 128 'application/emergencyCall.ProviderInfo+xml' . . . . 45 129 14.4.2. MIME Content-type Registration for 130 'application/emergencyCall.SvcInfo+xml' . . . . . . 46 131 14.4.3. MIME Content-type Registration for 132 'application/emergencyCall.DevInfo+xml' . . . . . . 47 133 14.4.4. MIME Content-type Registration for 134 'application/emergencyCall.SubInfo+xml' . . . . . . 49 135 14.4.5. MIME Content-type Registration for 136 'application/emergencyCall.Comment+xml' . . . . . . 50 137 14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 51 138 14.5.1. Registration for 139 urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 51 140 14.5.2. Registration for 141 urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 52 142 14.5.3. Registration for 143 urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 52 145 14.5.4. Registration for 146 urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 53 147 14.5.5. Registration for 148 urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 54 149 14.5.6. Registration for 150 urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 55 151 14.6. Schema Registrations . . . . . . . . . . . . . . . . . . 55 152 14.7. VCard Parameter Value Registration . . . . . . . . . . . 56 153 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56 154 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 155 16.1. Normative References . . . . . . . . . . . . . . . . . . 57 156 16.2. Informational References . . . . . . . . . . . . . . . . 57 157 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 58 158 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80 160 1. Introduction 162 When an emergency call is triggered and the Session Initiation 163 Protocol (SIP) is used a rich set of data is conveyed to the Public 164 Safety Answering Point (PSAP) already as part of the call setup, 165 which includes information about the calling party identity, the 166 multimedia capabilities of the device, the emergency service number, 167 etc. The device, as well as any service provider in the path may 168 have even more information that may be useful for a PSAP call taker. 169 This document extends the basic signaling of an emergency call, as 170 described in [RFC6443] and [RFC6881], in order to carry additional 171 data which may be useful to an entity handling the call. This data 172 is "additional" to the basic information found in the emergency call 173 signaling used. 175 Three general categories of such data are defined, namely data about 176 the call, the location and the caller. In more detail, the three 177 types of data exchanged are: 179 Data Associated with a Call: While information is carried in the 180 call setup procedure itself (as part of the SIP headers as well as 181 in the body of the SIP message), there is additional data known by 182 the device making the call, or a service provider in the path of 183 the call. This information may include the identity and contact 184 information of the service provider, subscriber identity and 185 contact information, the type of service the provider offers, what 186 kind of device is being used, etc. Some data is device or service 187 dependent data. For example, a car telematics system or service 188 may have crash information. A medical monitoring device may have 189 sensor data. While the details of the information may vary by 190 device or service, there needs to be a common way to send such 191 data to a PSAP. 193 Data Associated with a Location: Location data is conveyed in the 194 Presence Informatoin Data Format Location Object (PIDF-LO) data 195 structure originally defined in RFC 4119 [RFC4119]. There may be 196 data that is specific to the location not available in the 197 location data structure itself, such as floor plans, tenant and 198 building owner contact data, Heating, Ventilation and Air 199 Conditioning (HVAC) status, etc. 201 Data Associated with a Caller: This is personal data about a caller, 202 such as medical information and emergency contact data. 204 This document only defines data structures relevant to data 205 associated with the call. Other forms of additional data may use 206 this mechanism to carry data, but those blocks are not defined in 207 this document. 209 Data structures are defined for such data, and a means of conveying 210 the data by including a Uniform Resource Identifier (URI) in an 211 existing SIP header field, the Call-Info header, which is specified 212 in Section 20.9 of [RFC3261]. For this purpose a new token, namely 213 'emergencyCallData' is defined to be carried in the "purpose" 214 parameter. If the "purpose" parameter is set to 'emergencyCallData' 215 then the Call-Info header contains a HTTPS URL that resolves to a 216 data structure with information about the call, or is a CID (content 217 indirection) that allows the data structure to be placed in the body 218 of the message. The "purpose" parameter also contains an indication 219 of what kind of data is available at the URI. As such, the 220 additional data may reside on an external database, or may be 221 contained within the body of the SIP message. 223 Section 10 shows a SIP INVITE example containing such a Call-Info 224 header using the purpose parameter. 226 Besides a service provider in the path of a call, the access network 227 provider (which may provide location in the form of a PIDF-LO 228 [RFC4119] from a location server via a location configuration 229 protocol) also has similar information that may be valuable to the 230 PSAP. This information is not specific to the location itsef, but 231 rather provides descriptive information having to do with the 232 immediate circumstances about the provision of the location (who the 233 access network is, how to contact that entity, what kind of service 234 the access network provides, subscriber information, etc.). This 235 data is similar in nearly every respect to the data known by service 236 providers in the path of the call. When the access network provider 237 and service provider are separate entities, the access network does 238 not participate in the application layer signaling (and hence cannot 239 add a Call-Info' header field to the SIP message), but may provide 240 location information to assist in locating the caller's device. The 241 'provided-by' element of the PIDF-LO is a mechanism for the access 242 network to supply the information about the entity or organization 243 that supplied this location information. For this reason, this 244 document describes a namespace per [RFC4119] for inclusion in the 245 "provided-by" element of a PIDF-LO for adding information known to 246 the access network. 248 More technically, the data structure described in this document is 249 represented as one or more "blocks" of information. Each of the 250 blocks is a Multipurpose Internet Mail Extensions (MIME) type, and an 251 extensible set of these types constitute the data set. A registry is 252 defined to list the block types that may be included. 254 2. Terminology 256 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 257 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 258 document are to be interpreted as described in RFC 2119 [RFC2119]. 260 This document also uses terminology from [RFC5012]. We use the term 261 service provider to refer to an Application Service Provider (ASP) or 262 to Voice Service Provider (VSP), which is a specific type of ASP. 263 With the term "Access Network Provider" we refer to the Internet 264 Access Provider (IAP) and the Internet Service Provider (ISP) without 265 further distinguishing these two entities, since the difference 266 between the two is not relevant for this document. Note that the 267 roles of ASP and access network provider may be provided by a single 268 company. 270 In the data block definitions, the "Use:" values are specified as one 271 of: 273 'Mandatory': means they must be present in the data structure. 275 'Conditional': means they must be present unless the specified 276 condition is met, in which case the they may be present. 278 'Optional': means they may be present. 280 3. Data Structure Overview 282 The following section defines an initial set of blocks which may be 283 sent by value or by reference in SIP signaling or within a PIDF-LO. 284 For each block, we define the MIME type, and the XML data structure 285 for the block. The following blocks are defined: 287 'Data Provider': This block supplies name and contact information 288 for the entity that created the data. 290 'Service Information': This block supplies information about the 291 service provided by a service provider. 293 'Device Information': This block supplies information about the 294 device placing the call. 296 'Owner/Subscriber': This block supplies information about the owner 297 of the device or about the subscriber of the application service. 299 'Comment': This block provides a way to supply free form human 300 readable text to the PSAP or emergency responders. 302 PSAPs and emergency responders can examine the type of data provided 303 and selectively retrieve the data each they are interested in, while 304 forwarding all of it (the values or references) to downstream 305 entities. 307 Blocks can be sent by value (the data in the SIP body or PIDF-LO) or 308 by reference (the data is retrieved via HTTPS from an external 309 server). Data may be provided by the device and/or one or more 310 service providers. For example, the device may provide device 311 specific information by value, a telematics service provider may 312 provide its contact data and data derived from the sensor data (e.g., 313 injury prediction) by reference, and an access network provider may 314 provide contact information by value, all in the same SIP INVITE. 316 The access network provider may supply additional data as well, by 317 including the data within a Provided-By element of a PDIF-LO it 318 returns for emergency use (e.g., if requested with a HELD 319 "responseTime" attribute of "emergencyRouting" or "emergencyDispatch" 320 [RFC5985]). Access network providers are expected to normally supply 321 such information by reference (by including an HTTPS URI within the 322 Provided-By element). This document defines a namespace and adds the 323 namespace to the "provided-by" registry defined by PIDF-LO [RFC4119]. 325 4. Transmitting Blocks of Additional Data 327 One or more blocks of data registered in the Emergency Call 328 Additional Data registry, as defined in Section 14.1, may be included 329 or referenced in the SIP signaling (using the Call-Info header field) 330 or in the provided-by element of a PIDF-LO. Each block is a MIME 331 type, and any set of blocks may be included. 333 Additional data about a call is defined as a series of MIME objects, 334 each with an XML data structure contained inside. As usual, whenever 335 more than one MIME part is included in the body of a message, MIME- 336 multipart (i.e., 'multipart/mixed') encloses them all. The sections 337 below define the XML schema and MIME types used for each block. When 338 additional data is passed by value in the SIP signaling, each CID URL 339 points to one block in the body. Multiple URIs are used within a 340 Call-Info header field (or multiple Call-Info header fields) to point 341 to multiple blocks. When additional data is provided by reference 342 (in SIP signaling or Provided-By), each HTTPS URL references one 343 block; the data is retrieved with an HTTP GET operation, which 344 returns one of the blocks as an XML object. 346 A registry of allowed types is created by this document. Every block 347 must be one of the types in the registry. 349 In regions where callers can elect to suppress certain personally 350 identifying information, the network or PSAP functionality can 351 inspect privacy flags within the SIP headers to determine what 352 information may be passed, stored, or displayed to comply with local 353 policy or law. 355 Each entity adding additional data MUST supply the "Data Provider" 356 block. All other blocks are optional, but each entity SHOULD supply 357 any blocks where it has at least some of the information in the 358 block. 360 4.1. Transmitting blocks using Call-Info 362 A URI to a block MAY be inserted in a SIP request or response method 363 (most often INVITE or MESSAGE) with a Call-Info header field 364 containing a purpose of "emergencyCallData" together with the type of 365 data available at the URI. The type of data is denoted by including 366 the root of the MIME type (not including the emergencyCall prefix and 367 the +xml suffix) with a "." separator. For example, when 368 referencing a block with MIME type 'application/ 369 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to 370 'emergencyCallData.ProviderInfo'. An example "Call-Info" header 371 field for this would be: 373 Call-Info: https://www.example.com/23sedde3; 374 purpose="emergencyCallData.ProviderInfo" 376 The Call-info header with purpose='emergencyCallData' MUST only be 377 sent on an emergency call, which can be ascertained by the presence 378 of an emergency service urn in a Route header of a SIP message. 380 If the data is provided by reference, it may be retrieved with an 381 HTTPS GET from the URI. The URI MUST specify an HTTPS scheme, and 382 consequently Transport Layer Security (TLS) protection is applied. 384 The data may also be supplied by value in a SIP message. In this 385 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 386 referencing the MIME body part. 388 More than one Call-Info header with an emergencyCallData purpose can 389 be expected, but at least one MUST be provided. The device MUST 390 provide one if it knows no service provider is in the path of the 391 call. The device MAY insert one if it uses a service provider. Any 392 service provider in the path of the call MUST insert its own. For 393 example, a device, a telematics service provider in the call path, as 394 well as the mobile carrier handling the call will each provide one. 395 There may be circumstances where there is a service provider who is 396 unaware that the call is an emergency call and cannot reasonably be 397 expected to determine that it is an emergency call. In that case, 398 that service provider is not expected to provide emergencyCallData. 400 4.2. Transmitting blocks by reference using Provided-By 402 The 'emergencyCallDataReference' element is used to transmit an 403 additional data block by reference within a 'Provided-By' element of 404 a PIDF-LO. The 'emergencyCallDataReference' element has two 405 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 406 type of data block referenced. The value of 'ref' is an HTTPS URL 407 that resolves to a data structure with information about the call. 408 The value of 'purpose' is the same as used in a 'Call-Info' header 409 field (as specified in section Section 4.1, Transmitting blocks using 410 Call-Info). 412 For example, to reference a block with MIME type 'application/ 413 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to 414 'emergencyCallData.ProviderInfo'. An example 415 'emergencyCallDataReference' element for this would be: 417 420 4.3. Transmitting blocks by value using Provided-By 422 It is RECOMMENDED that access networks supply the data specified in 423 this document by reference, but they MAY provide the data by value. 425 The 'emergencyCallDataValue' element is used to transmit an 426 additional data block by value within a 'Provided-By' element of a 427 PIDF-LO. The 'emergencyCallDataValue' element has one attribute: 428 'purpose' to indicate the type of data block contained. The value of 429 'purpose' is the same as used in a 'Call-Info' header field (as 430 specified in Section 4.1, and in Section 4.1). The same XML 431 structure as would be wrapped in the corresponding MIME type is 432 placed inside the emergencyCallDataValue element. 434 For example: 436 438 440 HooThrooPoo 441 NENA 442 Access Infrastructure Provider 443 444 sip:15555550987@burf.example.com;user=phone 445 446 447 449 Example Provided-By by Value. 451 5. Data Provider Information 453 This block is intended to be provided by any service provider in the 454 path of the call or the access network provider. It includes 455 identification and contact information. This block SHOULD be 456 provided by every service provider in the call path, and by the 457 access network provider. Devices MAY use this block to provide 458 identifying information. The MIME subtype is "application/ 459 emergencyCall.ProviderInfo+xml". 461 5.1. Data Provider String 463 Data Element: Data Provider String 465 Use: Required 467 XML Element: 468 Description: This is a plain language string suitable for displaying 469 the name of the service provider that created the additional data 470 structure. If the device created the structure the value is 471 identical to the contact header in the SIP INVITE. 473 Reason for Need: Inform the call taker of the identity of the entity 474 providing the additional call data structure. 476 How Used by Call Taker: Allows the call taker to interpret the data 477 in this structure. The source of the information often influences 478 how the information is used, believed or verified. 480 5.2. Data Provider ID 482 Data Element: Data Provider ID 484 Use: Conditional. Must be provided if the service provider is 485 located in a jurisdiction that maintains such ids. Devices are 486 not required to provide it. 488 XML Element: 490 Description: A jurisdiction specific code for the provider shown in 491 the element that created the structure of the 492 call. This data SHOULD be provided if the local jurisdiction 493 maintains such an ID list. For example, in North America, this 494 would be a "NENA Company ID". Devices SHOULD NOT use this 495 element. 497 Reason for Need: Inform the call taker of the identity of the entity 498 providing the additional call data structure. 500 How Used by Call Taker: Where jurisdictions have lists of providers 501 the Data Provider ID can be useful. 503 5.3. Data Provider ID Series 505 Data Element: Data Provider ID Series 507 Use: Conditional. If Data Provider ID is provided, Data Provider ID 508 Series is required. 510 XML Element: 512 Description: Identifies the issuer of the the ProviderId. A 513 registry will reflect the following valid entries: 515 * NENA 517 * EENA 519 Reason for Need: Identifies how to interpret the Data Provider ID. 521 How Used by Call Taker: Determines which provider ID registry to 522 consult for more information 524 5.4. Type of Data Provider 526 Data Element: Type of Data Provider ID 528 Use: Conditional. If Data Provider ID is provided, Type of Data 529 Provider ID is required. 531 XML Element: 533 Description: Identifies the type of data provider id being supplied 534 in the ProviderId data element. A registry will reflect the 535 following valid entries: 537 * Access Network Provider 539 * Service Provider 541 * Service Provider Subcontractor 543 * Telematics Provider 545 * Relay Provider 547 * Other 549 Reason for Need: Identifies what kind of data provider this is. 551 How Used by Call Taker: To decide who to contact when further 552 information is needed 554 5.5. Data Provider Contact URI 556 Data Element: Data Provider Contact URI 558 Use: Required 560 XML Element: 562 Description: For a service provider the contact SHOULD be a contact 563 URI. This MUST be a SIP URI. If a telephone number is the 564 contact address it should be provided in the form of 565 sip:telephonenumber@serviceprovider:user=phone. If the call is 566 from a device, this would reflect the contact information of the 567 owner of the device. When provided by a service provider, this 568 would be a URI to a 24/7 support organization tasked to provide 569 PSAP support for this emergency call. 571 Reason for Need: Additional data providers may need to be contacted 572 for error or other unusual circumstances. 574 How Used by Call Taker: To contact the supplier of the additional 575 data for assistance in handling the call. 577 5.6. Data Provider Languages(s) Supported 579 Data Element: Data Provider Language(s) supported 581 Use: Conditional 583 XML Element: 585 Description: The language used by the entity at the Data Provider 586 Contact URI as an alpha 2-character code as defined in ISO 587 639-1:2002 Codes for the representation of names of languages -- 588 Part 1: Alpha-2 code Multiple instances of this element may occur. 589 Order is significant; preferred language should appear first. 590 This data is required if a Data Provider Contact URI is provided. 592 The content must reflect the languages supported at the contact 593 URI. 595 Reason for Need: Information needed to determine if emergency 596 service authority can communicate with the service provider or if 597 an interpreter will be needed. 599 How Used by Call Taker: If call taker cannot speak language(s) 600 supported by the service provider, a translation service will need 601 to be added to the conversation. 603 5.7. xCard of Data Provider 605 Data Element: xCard of Data Provider 607 Use: Optional 609 XML Element: 611 Description: There are many fields in the xCARD and the creator of 612 the data structure is encouraged to provide as much information as 613 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 614 minimum. N should contain name of support group or device owner 615 as appropriate. If more than one TEL property is provided, a 616 parameter from the vCard Property Value registry MUST be specified 617 on each TEL. For encoding of the xCard this specification uses 618 the XML-based encoding specified in [RFC6351]. 620 and is hereinafter referred to as "xCard" 622 Reason for Need: Information needed to determine additional contact 623 information. 625 How Used by Call Taker: Assists call taker by providing additional 626 contact information that may not be included in the SIP invite or 627 the PIDF-LO. 629 5.8. Subcontractor Principal 631 Data Element: Subcontractor Principal 633 XML Element: 635 Description: If the data provider is a subcontractor to another 636 provider such as an access infrastructure provider or telematics 637 provider, this element contains the DataProviderString of the 638 service provider to indicate which provider the subcontractor is 639 working for. This data is required if the Data Provider type is 640 subcontractor. 642 Reason for Need: Identify the entity the subcontractor works for. 644 How Used by Call Taker: Allows the call taker to understand what the 645 relationship between data providers and the service providers in 646 the path of the call are. 648 5.9. Subcontractor Priority 650 Data Element: Subcontractor Priority 652 Use: Required 654 XML Element: 656 Description: If the subcontractor should be contacted first, this 657 element should have a "sub" value. If the access or origination 658 service provider should be contacted first, this element should 659 have a "main" value. This data is required if the Data Provider 660 type is "subcontractor". 662 Reason for Need: Inform the call taker whether the network operator 663 or the subcontractor should be contacted first if support is 664 needed. 666 How Used by Call Taker: To decide which entity to contact first if 667 assistance is needed. 669 5.10. emergencyCall.ProviderInfo XML Schema 671 672 681 684 685 686 687 688 690 691 692 693 695 697 699 701 703 705 709 711 712 713 714 715 Figure 1: emergencyCall.ProviderInfo XML Schema 717 5.11. emergencyCall.ProviderInfo Example 719 720 723 Example VoIP Provider 724 725 ID123 726 NENA 727 Service Provider 728 sip:voip-provider@example.com 729 EN 730 732 733 Hannes Tschofenig 734 735 Hannes 736 Tschofenig 737 738 739 Dipl. Ing. 740 741 --0203 742 743 20090808T1430-0500 744 745 M 746 747 1 748 749 de 750 751 752 2 753 754 en 755 756 757 work 758 759 Example VoIP Provider 760 761 762 763 work 764 768 769 770 771 Linnoitustie 6 772 Espoo 773 Uusimaa 774 02600 775 Finland 776 777 778 779 780 work 781 voice 782 783 784 tel:+358 50 4871445 785 786 787 work 788 789 hannes.tschofenig@nsn.com 790 791 792 work 793 794 geo:60.210796,24.812924 795 796 797 home 798 799 800 http://www.tschofenig.priv.at/key.asc 801 802 803 Finland/Helsinki 804 805 home 806 807 http://www.tschofenig.priv.at 808 809 811 812 814 Figure 2: emergencyCall.ProviderInfo Example 816 6. Service Information 818 This block describes the service that the service provider provides 819 to the caller. It SHOULD be included by all SPs in the path of the 820 call. The mime subtype is "application/emergencyCall.SvcInfo+xml". 822 6.1. Service Environment 824 Data Element: Service Environment 826 Use: Required 828 XML Element: 830 Description: This element defines whether a call is from a business 831 or residence caller. Currently, the only valid entries are 832 'Business' or 'Residence'. 834 Reason for Need: To assist in determining equipment and manpower 835 requirements. 837 How Used by Call Taker: Information may be used to assist in 838 determining equipment and manpower requirements for emergency 839 responders. As the information is not always available, and the 840 registry is not all encompassing, this is at best advisory 841 information, but since it mimics a similar capability in some 842 current emergency calling systems, it is known to be valuable. 843 The service provider uses its best information (such as a rate 844 plan, facilities used to deliver service or service description) 845 to determine the information and is not responsible for 846 determining the actual characteristics of the location where the 847 call originates from. 849 6.2. Service Delivered by Provider to End User 851 Data Element: Service Delivered by Provider to End User 853 Use: Required 855 XML Element: 857 Description: This defines the type of service the end user has 858 subscribed to. The implied mobility of this service can not be 859 relied upon. A registry defined in this document will reflect the 860 following initial valid entries: 862 * Wireless Telephone Service: Includes Satellite, CDMA, GSM, Wi- 863 Fi, WiMAX, UTMS/WCDMA, LTE (Long Term Evolution) 865 * Fixed Public Pay/Coin telephones: Any coin or credit card 866 operated device. 868 * One way outbound service 870 * Inmate call/service 872 * Soft dialtone/quick service/warm disconnect/suspended 874 * Multi-line telephone system (MLTS): Includes all PBX, Centrex, 875 key systems, Shared Tenant Service. 877 * Sensor, unattended: Includes devices that generate DATA ONLY. 878 This is one-way information exchange and there will be no other 879 form of communication. 881 * Sensor, attended: Includes devices that are supported by a 882 monitoring service provider or automatically open a two-way 883 communication path. 885 * Wireline: Plain Old Telephone Service (POTS). 887 * VoIP Telephone Service: A type of service that offers 888 communication over internet protocol, such as Fixed, Nomadic, 889 Mobile, Unknown 891 * Relay Service: a type of service where there is a human 3rd 892 party agent who provides some kind of additional assistance to 893 the caller. Includes sign language relay and telematics 894 services which provide a service assistant on the call. 896 * Remote (off premise extension) 898 There can be more than one value returned. For example, a VoIP 899 inmate telephone service is a reasonable combination. 901 Reason for Need: Knowing the type of service may assist the PSAP 902 with the handling of the call. 904 How Used by Call Taker: Call takers often use this information to 905 determine what kinds of questions to ask callers, and how much to 906 rely on supportive information. An emergency call from a prison 907 is treated differently that a call from a sensor device. As the 908 information is not always available, and the registry is not all 909 encompassing, this is at best advisory information, but since it 910 mimics a similar capability in some current emergency calling 911 systems, it is known to be valuable. 913 6.3. Service Mobility Environment 915 Data Element: Service Mobility Environment 917 Use: Required 919 XML Element: 921 Description: This provides the service providers view of the 922 mobility of the caller. As the service provider may not know the 923 characteristics of the actual access network used, the value not 924 be relied upon. A registry will reflect the following initial 925 valid entries: 927 * Mobile: the device should be able to move at any time 929 * Fixed: the device is not expected to move unless the service is 930 relocated 932 * Nomadic: the device is not expected to change its point of 933 attachment while on a call 935 * Unknown: no information is known about the service mobility 936 environment for the device 938 Reason for Need: Knowing the service provider's belief of mobility 939 may assist the PSAP with the handling of the call. 941 How Used by Call Taker: To determine whether to assume the location 942 of the caller might change. 944 6.4. emergencyCall.SvcInfo XML Schema 946 947 955 958 959 960 961 963 965 967 969 971 972 973 974 976 Figure 3: emergencyCall.SvcInfo XML Schema 978 6.5. emergencyCall.SvcInfo Example 979 980 983 Business 984 MLTS 985 Fixed 986 988 Figure 4: emergencyCall.SvcInfo Example 990 7. Device Information 992 This block provides information about the device used to place the 993 call. It should be provided by any service provider that knows what 994 device is being used, and by the device itself. The mime subtype is 995 "application/emergencyCall.DevInfo+xml". 997 7.1. Device Classification 999 Data Element: Device Classification 1001 Use: Optional 1003 XML Element: 1005 Description: This data element defines the kind of device making the 1006 emergency call. If the device provides the data structure, the 1007 device information SHOULD be provided. If the service provider 1008 provides the structure and it knows what the device is, the 1009 service provider SHOULD provide the device information. Often the 1010 carrier does not know what the device is. It is possible to 1011 receive two Additional Data Associated with a Call data 1012 structures, one created by the device and one created by the 1013 service provider. This information describes the device, not how 1014 it is being used. This data element defines the kind of device 1015 making the emergency call. A registry will reflect the following 1016 valid entries: 1018 * Cordless handset 1020 * Fixed phone 1022 * Mobile handset 1023 * ATA (analog terminal adapter) 1025 * Satellite phone 1027 * Stationary computing device (alarm system, data sensor) 1029 * Guardian devices 1031 * Desktop PC 1033 * Laptop computing device 1035 * Tablet computing device 1037 * Alarm system 1039 * Data sensor 1041 * Personal beacons (spot) 1043 * Auto telematics (indicates VEDS data set) 1045 * Trucking telematics 1047 * Farm equipment telematics 1049 * Marine telematics 1051 * PDA (personal digital assistant) 1053 * PND (personal navigation device) 1055 * Smart phone 1057 * Internet tablet 1059 * Gaming console 1061 * Video phone 1063 * Other text device 1065 * Not Available 1067 Reason for Need: The device classification implies the capability of 1068 the calling device and assists in identifying the meaning of the 1069 emergency call location information that is being presented. For 1070 example, does the device require human intervention to initiate a 1071 call or is this call the result of programmed instructions? Does 1072 the calling device have the ability to update location or 1073 condition changes? Is this device interactive or a one-way 1074 reporting device? 1076 How Used by Call Taker: May assist with location of caller. For 1077 example, a cordless handset may be outside or next door. May 1078 provide calltaker some context about the caller, the capabilities 1079 of the device used for the call or the environment the device is 1080 being used in. 1082 7.2. Device Manufacturer 1084 Data Element: Device Manufacturer 1086 Use: Optional 1088 XML Element: 1090 Description: The plain language name of the manufacturer of the 1091 device. 1093 Reason for Need: Used by PSAP management for post-mortem 1094 investigation/resolution. 1096 How Used by Call Taker: Probably not used by calltaker, but by PSAP 1097 management. 1099 7.3. Device Model Number 1101 Data Element: Device Model Number 1103 Use: Optional 1105 XML Element: 1107 Description: Model number of the device. 1109 Reason for Need: Used by PSAP management for after action 1110 investigation/resolution. 1112 How Used by Call Taker: Probably not used by calltaker, but by PSAP 1113 management. 1115 7.4. Unique Device Identifier 1117 Data Element: Unique Device Identifier 1119 Use: Optional 1121 XML Element: 1123 Description: String that identifies the specific device making the 1124 call or creating an event. 1126 Reason for Need: Uniquely identifies the device as opposed to any 1127 signaling identifiers encountered in the call signaling stream. 1129 How Used by Call Taker: Probably not used by calltaker they would 1130 need to refer to management for investigation. 1132 7.5. Type of Device Identifier 1134 Data Element: Type of Device Identifier 1136 Use: Conditional: must be provided if DeviceID is provided 1138 XML Element: 1140 Description: Identifies the type of device identifier being 1141 generated in the unique device identifier data element. A 1142 registry will reflect the following valid entries: 1144 * MEID (CDMA) 1146 * ESN (Electronic Serial Number -- superseded by MEID) 1147 * MAC (Media Access Control) Address -- IEEE-delegated address of 1148 any of the interfaces of the device with a MAC address (e.g., 1149 Ethernet, WiFi) 1151 * WiMAX device certificate subject unique identifier 1153 * IMEI (International Mobile Equipment Identifier - GSM) 1155 * Unique Device Identifier (UDI) assigned by US FDA for medical 1156 devices 1158 * RFID (Radio Frequency Identification) 1160 * Sensors (types to be identified in a future document version) 1162 * Manufacturer Serial Number 1164 * Other 1166 Reason for Need: Identifies how to interpret the Unique Device 1167 Identifier. 1169 How Used by Call Taker: Additional information that may be used to 1170 assist with call handling. 1172 7.6. Device/Service Specific Additional Data Structure 1174 Data Element: Device/service specific additional data structure 1176 Use: Optional 1178 XML Element: 1180 Description: A URI representing additional data whose schema is 1181 specific to the device or service which created it. An example is 1182 the VEDs structure for a vehicle telematics device. The URI, when 1183 dereferenced, MUST yield a data structure defined by the Device/ 1184 service specific additional data type value. Different data may 1185 be created by each classification; e.g., telematics creates VEDS 1186 data set. 1188 Reason for Need: Provides device/service specific data that may be 1189 used by the call taker and/or responders. 1191 How Used by Call Taker: Provide information to guide call takers to 1192 select appropriate responders, give appropriate pre-arrival 1193 instructions to callers, and advise responders of what to be 1194 prepared for. May be used by responders to guide assistance 1195 provided. 1197 7.7. Device/Service Specific Additional Data Structure Type 1199 Data Element: Type of Device/service specific additional data 1200 structure 1202 Use: Conditional. MUST be provided when Device/service specific 1203 additional URI is provided 1205 XML Element: 1207 Description: Value from a registry defined by this document to 1208 describe the type of data that can be retrieved from the Device/ 1209 service specific additional data structure. Initial values are: 1211 * IEEE 1512 - USDOT Model for traffic incidents 1213 * VEDS 1215 Reason for Need: This data element allows identification of 1216 externally defined schemas, which may have additional data that 1217 may assist in emergency response. 1219 How Used by Call Taker: This data element allows the end user 1220 (calltaker or first responder) to know what type of additional 1221 data may be available to aid in providing the needed emergency 1222 services. 1224 Note: Information which is specific to a location or a caller 1225 (person) should not be placed in this section. 1227 7.8. Choosing between defining a new type of block or new type of 1228 device/service specific additional data 1230 For devices that have device or service specific data, there are two 1231 choices to carry it. A new block can be defined, or the device/ 1232 service specific additional data URL the the DevInfo block can be 1233 used and a new type for it defined . The data passed would likely be 1234 the same in both cases. Considerations for choosing which mechanism 1235 to register under include: 1237 Applicability: Information which will be carried by many kinds of 1238 devices or services are more appropriately defined as separate 1239 blocks. 1241 Privacy: Information which may contain private data may be better 1242 sent in the DevInfo block, rather than a new block so that 1243 implementations are not tempted to send the data by value, and 1244 thus having more exposure to the data than forcing the data to be 1245 retrieved via the URL in DevInfo. 1247 Size: Information which may be very may be better sent in the 1248 DevInfo block, rather than a new block so that implementations are 1249 not tempted to send the data by value. Conversely, data which is 1250 small may best be sent in a separate block so that it can be sent 1251 by value 1253 Availability of a server: Providing the data via the device block 1254 requires a server be made available to retrieve the data. 1255 Providing the data via new block allows it to be sent by value 1256 (CID). 1258 7.9. emergencyCall.DevInfo XML Schema 1260 1261 1269 1272 1273 1274 1275 1278 1280 1282 1284 1286 1288 1290 1292 1293 1294 1295 1297 Figure 5: emergencyCallDevInfo XML Schema 1299 7.10. emergencyCall.DevInfo Example 1301 1302 1305 Fixed phone 1306 Nokia 1307 Lumia 800 1308 35788104 1309 IMEI 1310 1312 Figure 6: emergencyCallDevInfo Example 1314 8. Owner/Subscriber Information 1316 This block describes the owner of the device (if provided by the 1317 device) or the subscriber information, if provided by a service 1318 provider. The contact location is not necessarily the location of 1319 the caller or incident, but is rather the nominal contact address. 1320 The mime subtype is "application/emergencyCall.Subscriber+xml". 1322 8.1. xCard for Subscriber's Data 1324 Data Element: xCARD for Subscriber's Data 1325 Use: Conditional: Some services (e.g., prepaid phones, initialized 1326 phones, etc.) may not have this information. 1328 XML Element: 1330 Description: Information known by the service provider or device 1331 about the subscriber; e.g., Name, Address, Individual Telephone 1332 Number, Main Telephone Number and any other data. N, ORG (if 1333 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1334 than one TEL property is provided, a parameter from the vCard 1335 Property Value registry MUST be specified on each TEL. 1337 Reason for Need: When the caller is unable to provide information, 1338 this data may be used to obtain it 1340 How Used by Call Taker: Obtaining critical information about the 1341 caller and possibly the location when it is not able to be 1342 obtained otherwise. 1344 8.2. emergencyCall.SubInfo XML Schema 1346 1347 1355 1358 1359 1360 1361 1365 1367 1369 1370 1371 1373 Figure 7: emergencyCall.SubInfo XML Schema 1375 8.3. emergencyCall.SubInfo Example 1377 1378 1381 1382 1383 1384 Simon Perreault 1385 1386 Perreault 1387 Simon 1388 1389 1390 ing. jr 1391 M.Sc. 1392 1393 --0203 1394 1395 20090808T1430-0500 1396 1397 M 1398 1399 1 1400 1401 fr 1402 1403 1404 2 1405 1406 en 1407 1408 1409 work 1410 1411 Viagenie 1412 1413 1414 1415 work 1416 1420 1421 1422 1423 2875 boul. Laurier, suite D2-630 1424 Quebec 1425 QC 1426 G1V 2M2 1427 Canada 1428 1429 1430 1431 1432 work 1433 voice 1434 1435 1436 tel:+1-418-656-9254;ext=102 1437 1438 1439 1440 1441 work 1442 text 1443 voice 1444 cell 1445 video 1446 1447 1448 tel:+1-418-262-6501 1449 1450 1451 work 1452 1453 simon.perreault@viagenie.ca 1454 1455 1456 work 1457 1458 geo:46.766336,-71.28955 1459 1460 1461 work 1462 1463 1464 http://www.viagenie.ca/simon.perreault/simon.asc 1465 1466 1467 America/Montreal 1468 1469 home 1470 1471 http://nomis80.org 1472 1473 1474 1475 1476 1478 Figure 8: emergencyCall.SubInfo Example 1480 9. Comment 1482 This block provides a mechanism for the data provider to supply 1483 extra, human readable information to the PSAP. It is not intended 1484 for a general purpose extension mechanism. The mime subtype is 1485 "application/emergencyCall.Comment+xml" 1487 9.1. Comment 1489 Data Element: EmergencyCall.Comment 1491 Use: Optional 1493 XML Element: 1495 Description: Human readable text providing additional information to 1496 the PSAP staff. 1498 Reason for Need: Explanatory information for values in the data 1499 structure 1501 How Used by Call Taker: To interpret the data provided 1503 9.2. emergencyCall.Comment XML Schema 1505 1506 1513 1516 1517 1518 1519 1521 1523 1524 1525 1527 1528 1529 1530 1531 1532 1533 1535 1537 Figure 9: EmergencyCall.Comment XML Schema 1539 9.3. emergencyCall.Comment Example 1541 1542 1545 This is an example text. 1546 1548 Figure 10: EmergencyCall.Comment Example 1550 10. Example 1551 INVITE sips:bob@biloxi.example.com SIP/2.0 1552 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1553 Max-Forwards: 70 1554 To: Bob 1555 From: Alice ;tag=9fxced76sl 1556 Call-ID: 3848276298220188511@atlanta.example.com 1557 Call-Info: ;purpose=icon, 1558 ;purpose=info, 1559 1560 ;purpose=emergencyCallData.ProviderInfo 1561 Geolocation: 1562 Geolocation-Routing: no 1563 Accept: application/sdp, application/pidf+xml, 1564 application/emergencyCallProviderinfo+xml 1565 CSeq: 31862 INVITE 1566 Contact: 1567 Content-Type: multipart/mixed; boundary=boundary1 1569 Content-Length: ... 1571 --boundary1 1573 Content-Type: application/sdp 1575 ...SDP goes here 1577 --boundary1 1579 Content-Type: application/pidf+xml 1580 Content-ID: 1582 \0x2026PIDF-LO goes here 1584 --boundary1-- 1586 Content-Type: application/emergencyCall.ProviderInfo+xml 1587 Content-ID: <1234567890@atlanta.example.com> 1589 ...Additional Data goes here 1591 --boundary1-- 1593 Example: Attaching Additional Data via CID to a SIP INVITE 1595 11. Main Telephone Number 1597 In a xCard, used extensively in this document, there is no way to 1598 specify a "Main" telephone number. These numbers are useful to 1599 emergency responders who are called to a large enterprise. This 1600 document adds a new Property Value to the "tel" property of the TYPE 1601 parameter called "main". It can be used in any xCard in additional 1602 data. 1604 12. Security Considerations 1606 The information in this data structure will usually be considered 1607 private. HTTPS is specified to require the provider of the 1608 information to validate the credentials of the requester. While the 1609 creation of a PKI that has global scope may be difficult, the 1610 alternatives to creating devices and services that can provide 1611 critical information securely are more daunting. The provider may 1612 enforce any policy it wishes to use, but PSAPs and responder agencies 1613 should deploy a PKI so that providers of additional data can check 1614 the certificate of the client and decide the appropriate policy to 1615 enforce based on that certificate. 1617 Ideally, the PSAP and emergency responders will be given credentials 1618 signed by an authority trusted by the data provider. In most 1619 circumstances, nationally recognized credentials would be sufficient, 1620 and if the emergency services arranges a PKI, data providers could be 1621 provisioned with the root CA public key for a given nation. Some 1622 nations are developing a PKI for this, and related, purposes. Since 1623 calls could be made from devices where the device and/or the service 1624 provider(s) are not local to the emergency authorities, globally 1625 recognized credentials are useful. This might be accomplished by 1626 extending the notion of the "forest guide" described in [RFC5222] to 1627 allow the forest guide to provide the credential of the PKI root for 1628 areas that it has coverage information for, but standards for such a 1629 mechanism are not yet available. In its absence, the data provider 1630 will need to obtain the root CA credentials for any areas it is 1631 willing to provide additional data by out of band means. With the 1632 credential of the root CA for a national emergency services PKI, the 1633 data provider server can validate the credentials of an entity 1634 requesting additional data by reference. 1636 The data provider also needs a credential that can be verified by the 1637 emergency services to know that it is receiving data from the right 1638 server. The emergency authorities could provide credentials, 1639 distinguishable from credentials it provides to emergency responders 1640 and PSAPs, which could be used to validate data providers. Such 1641 credentials would have to be acceptable to any PSAP or responder that 1642 could receive a call with additional data supplied by that provider. 1643 This would be extensible to global credential validation using the 1644 forest guide as above. In the absence of such credentials, the 1645 emergency authorities could maintain a list of local data providers' 1646 credentials provided to it out of band. At a minimum, the emergency 1647 authorities could obtain a credential from the DNS entry of the 1648 domain in the Addional Data URI to at least validate that the server 1649 is known to the domain providing the URI. 1651 Data provided by devices by reference have similar credential 1652 validation issues to service providers, and the solutions are the 1653 same. 1655 13. Privacy Considerations 1657 There is much private data in this information. Local regulations 1658 may govern what data must be provided in emergency calls, but in 1659 general, the emergency call system is often aided by the kinds of 1660 information described in this document. There is a tradeoff between 1661 the privacy considerations and the utility of the data. Certainly, 1662 if the data cannot be protected, due to failure to establish (by TLS) 1663 a secure connection to the data provider, data SHOULD NOT be sent 1664 unless specifically required by regulation. 1666 Some forms of data can be sent by value in the SIP signaling or by 1667 value (URL in SIP signaling). When data is sent by value, all 1668 intermediaries have access to the data. If the data is private, 1669 sending by reference is more appropriate. 1671 14. IANA Considerations 1673 14.1. Registry creation 1675 This document creates a new registry called 'Emergency Call 1676 Additional Data'. The following subregistries are created in 1677 Emergency Call Additional Data: 1679 14.1.1. Additional Call Data Provider ID Series Registry 1681 This document creates a new subregistry called 'Additional Call Data 1682 Provider ID Series'. As defined in [RFC5226], this registry operates 1683 under "Expert Review" rules. The expert should determine that the 1684 entity requesting a new value is a legitimate issuer of service 1685 provider IDs suitable for use in Additional Call Data. 1687 The content of this registry includes: 1689 Name: The identifier which will be used in the ProviderIDSeries 1690 element 1692 Source: The full name of the organization issuing the identifiers 1694 URL: A URL to the organization for further information 1695 The values defined are: 1697 +-----------+-----------+--------------+--------------+ 1698 | Name | Source | URL | 1699 +-----------+--------------------------+--------------+ 1700 | NENA | North American Emergency | www.nena.org | 1701 | | Number Association | | 1702 | EENA | European Emergency | www.eena.org | 1703 | | Number Association | | 1704 +-----------+--------------------------+--------------+ 1705 RFC Editor Note: 1706 replace XXXX in the table above with this documents RFC number 1708 14.1.2. Additional Call Data Service Provider Type Registry 1710 This document creates a new subregistry called 'Service Provider 1711 Type'. As defined in [RFC5226], this registry operates under "Expert 1712 Review". The expert should determine that the proposed new value is 1713 distinct from existing values and appropriate for use in the 1714 TypeOfServicerProvider element 1716 The content of this registry includes: 1718 Name: Value to be used in TypeOfServiceProvider. 1720 Description: A short description of the type of service provider 1722 The values defined are: 1724 +------------------------------+------------------------------------+ 1725 | Name | Description | 1726 +------------------------------+------------------------------------+ 1727 |Access Infrastructure Provider| Access network service provider | 1728 |Service Provider | Calling or Origination telecom SP | 1729 |Service Provider Subcontractor| A contractor to another kind of SP | 1730 |Telematics Provider | A sensor based SP, especially | 1731 | | vehicle based | 1732 |Relay Provider | A interpretation SP, for example, | 1733 | | video relay for sign language | 1734 | | interpretors | 1735 |Other | Any other type of service provider | 1736 +------------------------------+------------------------------------+ 1737 RFC Editor Note: 1738 replace XXXX in the table above with this documents RFC number 1740 14.1.3. Additional Call Data Service Delivered Registry 1742 This document creates a new registry called 'Additional Call Data 1743 Service Delivered'. As defined in [RFC5226], this registry operates 1744 under "Expert Review" rules. The expert should consider whether the 1745 proposed service is unique from existing services and the definition 1746 of the service will be clear to implementors and PSAPS/responders. 1748 The content of this registry includes: 1750 Name: enumeration token of the service. 1752 Description: Short description identifying the service. 1754 The values defined are: 1756 +--------+----------------------------------------+ 1757 | Name | Description | 1758 +--------+----------------------------------------+ 1759 | Wrless | Wireless Telephone Service: Includes | 1760 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 1761 | | LTE (Long Term Evolution) | 1762 | Coin | Fixed Public Pay/Coin telephones: Any | 1763 | | coin or credit card operated device | 1764 | 1way | One way outbound service | 1765 | Prison | Inmate call/service | 1766 | Temp | Soft dialtone/quick service/warm | 1767 | | disconnect/suspended | 1768 | MLTS | Multi-line telephone system: Includes | 1769 | | all PBX, Centrex, key systems, | 1770 | | Shared Tenant Service | 1771 | SenseU | Sensor, unattended: Includes devices | 1772 | | that generate DATA ONLY. This is | 1773 | | one-way information exchange and | 1774 | | there will be no other form of | 1775 | | communication | 1776 | SenseA | Sensor, attended: Includes devices | 1777 | | that are supported by a monitoring | 1778 | | service provider or automatically | 1779 | | open a two-way communication path | 1780 | POTS | Wireline: Plain Old Telephone Service | 1781 | VOIP | VoIP Telephone Service: A type of | 1782 | | service that offers communication | 1783 | | over internet protocol, such as Fixed| 1784 | | Nomadic, Mobile, ... | 1785 +--------+----------------------------------------+ 1787 14.1.4. Additional Call Data Device Classification Registry 1789 This document creates a new registry called 'Additional Call Data 1790 Device Classification'. As defined in [RFC5226], this registry 1791 operates under "Expert Review" rules. The expert should consider 1792 whether the proposed class is unique from existing classes and the 1793 definition of the class will be clear to implementors and PSAPS/ 1794 responders. 1796 The content of this registry includes: 1798 Name: enumeration token of the device classification. 1800 Description: Short description identifying the device type. 1802 The values defined are: 1804 +--------+----------------------------------------+ 1805 | Name | Description | 1806 +--------+----------------------------------------+ 1807 |Cordless| Cordless handset | 1808 | Fixed | Fixed phone | 1809 | Mobile | Mobile handset | 1810 | ATA | analog terminal adapter | 1811 |Satphone| Satellite phone | 1812 | FSense | Stationary computing device (alarm | 1813 | | system, data sensor) | 1814 | Guard | Guardian devices | 1815 | Desktop| Desktop PC | 1816 | Laptop | Laptop computing device | 1817 | Tablet | Tablet computing device | 1818 | Alarm | Alarm system | 1819 | MSense | Mobile Data sensor | 1820 | Beacon | Personal beacons (spot) | 1821 | Auto | Auto telematics | 1822 | Truck | Truck telematics | 1823 | Farm | Farm equipment telematics | 1824 | Marine | Marine telematics | 1825 | PDA | Personal digital assistant | 1826 | PND | Personal navigation device) | 1827 | SmrtPhn| Smart phone | 1828 | Itab | Internet tablet | 1829 | Game | Gaming console | 1830 | Video | Video phone | 1831 | Text | Other text device | 1832 | NA | Not Available | 1833 +--------+----------------------------------------+ 1835 14.1.5. Additional Call Data Device ID Type Type Registry 1837 This document creates a new registry called 'Additional Call Data 1838 Device ID Type'. As defined in [RFC5226], this registry operates 1839 under "Expert Review" rules. The expert should ascertain that the 1840 proposed type is well understood, and provides the information useful 1841 to PSAPs and responders to uniquely identify a device. 1843 The content of this registry includes: 1845 Name: enumeration token of the device id type. 1847 Description: Short description identifying type of device id. 1849 The values defined are: 1851 +--------+----------------------------------------+ 1852 | Name | Description | 1853 +--------+----------------------------------------+ 1854 | MEID | Mobile Equipment Identifier (CDMA) | 1855 | ESN | Electronic Serial Number(GSM) | 1856 | MAC | Media Access Control Address (IEEE) | 1857 | WiMAX | device certificate unique id | 1858 | IMEI | International Mobile Equipment ID (GSM)| 1859 | UDI | Unique Device Identifier (medical) | 1860 | RFID | Radio Frequency Identification | 1861 | SN | Manufacturer Serial Number | 1862 +--------+----------------------------------------+ 1864 14.1.6. Device/Service Specific Additional Data Type Registry 1866 This document creates a new registry called 'Device/Service Specific 1867 Additional Data Type Registry'. As defined in [RFC5226], this 1868 registry operates under "Expert Review" and "Specification Required" 1869 rules. The expert should ascertain that the proposed type is well 1870 understood, and provides information useful to PSAPs and responders. 1871 The specification must contain a complete description of the data, 1872 and a precise format specification suitable to allow interoperable 1873 implementations. 1875 The content of this registry includes: 1877 Name: enumeration token of the data type. 1879 Description: Short description identifying the the data. 1881 Specification: Citation for the specification of the data. 1883 The values defined are: 1885 +---------+----------------------------------------+----------------+ 1886 | Name | description | specification | 1887 +---------+-------+--------------------------------+----------------+ 1888 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 1889 +---------+----------------------------------------+----------------+ 1890 | VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS | 1891 +---------+----------------------------------------+----------------+ 1893 14.1.7. Additional Call Data Blocks Registry 1895 This document creates a new subregistry called 'Additional Call Data 1896 Blocks' in the purpose registry established by RFC 261. As defined 1897 in [RFC5226], this registry operates under "Expert Review" and 1898 "Specification Required" rules. The expert is responsible for 1899 verifying that the document contains a complete and clear 1900 specification of the block and the block does not obviously duplicate 1901 existing blocks. 1903 The content of this registry includes: 1905 Name: Element Name of enclosing block. 1907 Reference: The document that describes the block 1909 The values defined are: 1911 +-------------+-----------+ 1912 | Name | Reference | 1913 +-------------+-----------+ 1914 |ProviderInfo | RFCXXXX | 1915 | SvcInfo | RFCXXXX | 1916 | DevInfo | RFCXXXX | 1917 | Subscriber | RFCXXXX | 1918 | Comment | RFCXXXX | 1919 +-------------+-----------+ 1920 RFC Editor Note: 1921 replace XXXX in the table above with this documents RFC number 1923 14.2. 'emergencyCallData' Purpose Parameter Value 1925 This document defines the 'emergencyCall' value for the "purpose" 1926 parameter of the Call-Info header field. The Call-Info header and 1927 the corresponding registry for the 'purpose' parameter was 1928 established with RFC 3261 [RFC3261]. 1930 Header Parameter New 1931 Field Name Value Reference 1932 ---------- --------- ----------------- --------- 1933 Call-Info purpose emergencyCall [This RFC] 1935 14.3. URN Sub-Namespace Registration for provided-by Registry Entry 1937 This section registers the namespace specified in Section 14.5.1 in 1938 the provided-by registry established by RFC 4119, for usage within 1939 the 'provided-by' element of a PIDF-LO. 1941 14.3.1. Provided-By XML Schema 1943 1944 1953 1956 1957 1958 1959 1960 1962 1963 1964 1965 1967 1969 1970 1971 1973 1974 1976 1977 1979 Figure 11: Provided-By XML Schema 1981 14.4. MIME Registrations 1983 14.4.1. MIME Content-type Registration for 'application/ 1984 emergencyCall.ProviderInfo+xml' 1986 This specification requests the registration of a new MIME type 1987 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1988 RFC 3023 [RFC3023]. 1990 MIME media type name: application 1992 MIME subtype name: emergencyCall.ProviderInfo+xml 1994 Mandatory parameters: none 1996 Optional parameters: charset 1998 Indicates the character encoding of enclosed XML. 2000 Encoding considerations: 2002 Uses XML, which can employ 8-bit characters, depending on the 2003 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 2005 Security considerations: 2007 This content type is designed to carry the data provider 2008 information, which is a sub-category of additional data about an 2009 emergency call. 2011 Since this data contains personal information appropriate 2012 precautions have to be taken to limit unauthorized access, 2013 inappropriate disclosure to third parties, and eavesdropping of 2014 this information. Please refer to Section 12 and Section 13 for 2015 more information. 2017 Interoperability considerations: None 2019 Published specification: [TBD: This specification] 2020 Applications which use this media type: Emergency Services 2022 Additional information: 2024 Magic Number: None 2026 File Extension: .xml 2028 Macintosh file type code: 'TEXT' 2030 Person and email address for further information: Hannes 2031 Tschofenig, Hannes.Tschofenig@gmx.net 2033 Intended usage: LIMITED USE 2035 Author: This specification is a work item of the IETF ECRIT 2036 working group, with mailing list address . 2038 Change controller: The IESG 2040 14.4.2. MIME Content-type Registration for 'application/ 2041 emergencyCall.SvcInfo+xml' 2043 This specification requests the registration of a new MIME type 2044 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2045 RFC 3023 [RFC3023]. 2047 MIME media type name: application 2049 MIME subtype name: emergencyCall.SvcInfo+xml 2051 Mandatory parameters: none 2053 Optional parameters: charset 2055 Indicates the character encoding of enclosed XML. 2057 Encoding considerations: 2059 Uses XML, which can employ 8-bit characters, depending on the 2060 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 2062 Security considerations: 2064 This content type is designed to carry the service information, 2065 which is a sub-category of additional data about an emergency 2066 call. 2068 Since this data contains personal information appropriate 2069 precautions have to be taken to limit unauthorized access, 2070 inappropriate disclosure to third parties, and eavesdropping of 2071 this information. Please refer to Section 12 and Section 13 for 2072 more information. 2074 Interoperability considerations: None 2076 Published specification: [TBD: This specification] 2078 Applications which use this media type: Emergency Services 2080 Additional information: 2082 Magic Number: None 2084 File Extension: .xml 2086 Macintosh file type code: 'TEXT' 2088 Person and email address for further information: Hannes 2089 Tschofenig, Hannes.Tschofenig@gmx.net 2091 Intended usage: LIMITED USE 2093 Author: This specification is a work item of the IETF ECRIT 2094 working group, with mailing list address . 2096 Change controller: The IESG 2098 14.4.3. MIME Content-type Registration for 'application/ 2099 emergencyCall.DevInfo+xml' 2101 This specification requests the registration of a new MIME type 2102 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2103 RFC 3023 [RFC3023]. 2105 MIME media type name: application 2107 MIME subtype name: emergencyCall.DevInfo+xml 2109 Mandatory parameters: none 2111 Optional parameters: charset 2113 Indicates the character encoding of enclosed XML. 2115 Encoding considerations: 2117 Uses XML, which can employ 8-bit characters, depending on the 2118 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 2120 Security considerations: 2122 This content type is designed to carry the device information 2123 information, which is a sub-category of additional data about an 2124 emergency call. 2126 Since this data contains personal information appropriate 2127 precautions have to be taken to limit unauthorized access, 2128 inappropriate disclosure to third parties, and eavesdropping of 2129 this information. Please refer to Section 12 and Section 13 for 2130 more information. 2132 Interoperability considerations: None 2134 Published specification: [TBD: This specification] 2136 Applications which use this media type: Emergency Services 2138 Additional information: 2140 Magic Number: None 2142 File Extension: .xml 2144 Macintosh file type code: 'TEXT' 2146 Person and email address for further information: Hannes 2147 Tschofenig, Hannes.Tschofenig@gmx.net 2149 Intended usage: LIMITED USE 2151 Author: This specification is a work item of the IETF ECRIT 2152 working group, with mailing list address . 2154 Change controller: The IESG 2156 14.4.4. MIME Content-type Registration for 'application/ 2157 emergencyCall.SubInfo+xml' 2159 This specification requests the registration of a new MIME type 2160 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2161 RFC 3023 [RFC3023]. 2163 MIME media type name: application 2165 MIME subtype name: emergencyCall.SubInfo+xml 2167 Mandatory parameters: none 2169 Optional parameters: charset 2171 Indicates the character encoding of enclosed XML. 2173 Encoding considerations: 2175 Uses XML, which can employ 8-bit characters, depending on the 2176 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 2178 Security considerations: 2180 This content type is designed to carry owner/subscriber 2181 information, which is a sub-category of additional data about an 2182 emergency call. 2184 Since this data contains personal information appropriate 2185 precautions have to be taken to limit unauthorized access, 2186 inappropriate disclosure to third parties, and eavesdropping of 2187 this information. Please refer to Section 12 and Section 13 for 2188 more information. 2190 Interoperability considerations: None 2192 Published specification: [TBD: This specification] 2194 Applications which use this media type: Emergency Services 2196 Additional information: 2198 Magic Number: None 2200 File Extension: .xml 2202 Macintosh file type code: 'TEXT' 2203 Person and email address for further information: Hannes 2204 Tschofenig, Hannes.Tschofenig@gmx.net 2206 Intended usage: LIMITED USE 2208 Author: This specification is a work item of the IETF ECRIT 2209 working group, with mailing list address . 2211 Change controller: The IESG 2213 14.4.5. MIME Content-type Registration for 'application/ 2214 emergencyCall.Comment+xml' 2216 This specification requests the registration of a new MIME type 2217 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2218 RFC 3023 [RFC3023]. 2220 MIME media type name: application 2222 MIME subtype name: emergencyCall.Comment+xml 2224 Mandatory parameters: none 2226 Optional parameters: charset 2228 Indicates the character encoding of enclosed XML. 2230 Encoding considerations: 2232 Uses XML, which can employ 8-bit characters, depending on the 2233 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 2235 Security considerations: 2237 This content type is designed to carry a comment, which is a sub- 2238 category of additional data about an emergency call. 2240 This data may contain personal information. Appropriate 2241 precautions may have to be taken to limit unauthorized access, 2242 inappropriate disclosure to third parties, and eavesdropping of 2243 this information. Please refer to Section 12 and Section 13 for 2244 more information. 2246 Interoperability considerations: None 2248 Published specification: [TBD: This specification] 2250 Applications which use this media type: Emergency Services 2251 Additional information: 2253 Magic Number: None 2255 File Extension: .xml 2257 Macintosh file type code: 'TEXT' 2259 Person and email address for further information: Hannes 2260 Tschofenig, Hannes.Tschofenig@gmx.net 2262 Intended usage: LIMITED USE 2264 Author: This specification is a work item of the IETF ECRIT 2265 working group, with mailing list address . 2267 Change controller: The IESG 2269 14.5. URN Sub-Namespace Registration 2271 14.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData 2273 This section registers a new XML namespace, as per the guidelines in 2274 RFC 3688 [RFC3688]. 2276 URI: urn:ietf:params:xml:ns:emergencyCallAddlData 2278 Registrant Contact: IETF, ECRIT working group, , as 2279 delegated by the IESG . 2281 XML: 2283 BEGIN 2284 2285 2287 2288 2289 2291 Namespace for Additional Emergency Call Data 2292 2293 2294

Namespace for Additional Data related to an Emergency Call

2295

See [TBD: This document].

2296 2297 2298 END 2300 14.5.2. Registration for 2301 urn:ietf:params:xml:ns:emergencyCallProviderInfo 2303 This section registers a new XML namespace, as per the guidelines in 2304 RFC 3688 [RFC3688]. 2306 URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo 2308 Registrant Contact: IETF, ECRIT working group, , as 2309 delegated by the IESG . 2311 XML: 2313 BEGIN 2314 2315 2317 2318 2319 2321 Namespace for Additional Emergency Call Data: 2322 Data Provider Information 2323 2324 2325

Namespace for Additional Data related to an Emergency Call

2326

Data Provider Information

2327

See [TBD: This document].

2328 2329 2330 END 2332 14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2334 This section registers a new XML namespace, as per the guidelines in 2335 RFC 3688 [RFC3688]. 2337 URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2338 Registrant Contact: IETF, ECRIT working group, , as 2339 delegated by the IESG . 2341 XML: 2343 BEGIN 2344 2345 2347 2348 2349 2351 Namespace for Additional Emergency Call Data: 2352 Service Information 2353 2354 2355

Namespace for Additional Data related to an Emergency Call

2356

Service Information

2357

See [TBD: This document].

2358 2359 2360 END 2362 14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo 2364 This section registers a new XML namespace, as per the guidelines in 2365 RFC 3688 [RFC3688]. 2367 URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo 2369 Registrant Contact: IETF, ECRIT working group, , as 2370 delegated by the IESG . 2372 XML: 2374 BEGIN 2375 2376 2378 2379 2380 2383 Namespace for Additional Emergency Call Data: 2384 Device Information 2385 2386 2387

Namespace for Additional Data related to an Emergency Call

2388

Device Information

2389

See [TBD: This document].

2390 2391 2392 END 2394 14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo 2396 This section registers a new XML namespace, as per the guidelines in 2397 RFC 3688 [RFC3688]. 2399 URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo 2401 Registrant Contact: IETF, ECRIT working group, , as 2402 delegated by the IESG . 2404 XML: 2406 BEGIN 2407 2408 2410 2411 2412 2414 Namespace for Additional Emergency Call Data: 2415 Owner/Subscriber Information 2416 2417 2418

Namespace for Additional Data related to an Emergency Call

2419

Owner/Subscriber Information

2420

See [TBD: This document].

2421 2422 2423 END 2425 14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment 2427 This section registers a new XML namespace, as per the guidelines in 2428 RFC 3688 [RFC3688]. 2430 URI: urn:ietf:params:xml:ns:emergencyCall.Comment 2432 Registrant Contact: IETF, ECRIT working group, , as 2433 delegated by the IESG . 2435 XML: 2437 BEGIN 2438 2439 2441 2442 2443 2445 Namespace for Additional Emergency Call Data:Comment 2446 2447 2448

Namespace for Additional Data related to an Emergency Call

2449

Comment

2450

See [TBD: This document].

2451 2452 2453 END 2455 14.6. Schema Registrations 2457 This specification registers five schemas, as per the guidelines in 2458 RFC 3688 [RFC3688]. 2460 URI: urn:ietf:params:xml:schema:additional- 2461 data:emergencyCallProviderInfo 2463 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2464 delegated by the IESG (iesg@ietf.org). 2466 XML: The XML schema can be found in Figure 1. 2468 URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo 2469 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 2470 delegated by the IESG (iesg@ietf.org). 2472 XML: The XML schema can be found in Figure 3. 2474 URI: urn:ietf:params:xml:schema:additional- 2475 data:emergencyCallDevInfo 2477 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2478 delegated by the IESG (iesg@ietf.org). 2480 XML: The XML schema can be found in Figure 5. 2482 URI: urn:ietf:params:xml:schema:additional- 2483 data:emergencyCall.SubInfo 2485 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2486 delegated by the IESG (iesg@ietf.org). 2488 XML: The XML schema can be found in Section 8.2. 2490 URI: urn:ietf:params:xml:schema:additional- 2491 data:emergencyCall.Comment 2493 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2494 delegated by the IESG (iesg@ietf.org). 2496 XML: The XML schema can be found in Section 9.2. 2498 14.7. VCard Parameter Value Registration 2500 This document registers a new value in the vCARD Parameter Values 2501 registry as defined by [RFC6350] with the following template: 2503 Value: main 2505 Purpose: The main telephone number, typically of an enterprise, as 2506 opposed to a direct dial number of an individual employee 2508 Conformance: This value can be used with the "TYPE" parameter 2509 applied on the "TEL" property. 2511 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 2512 00 2514 15. Acknowledgments 2515 This work was originally started in NENA and has benefitted from a 2516 large number of participants in NENA standardization efforts, 2517 originally in the Long Term Definition Working Group, the Data 2518 Technical Committee and most recently the Additional Data working 2519 group. The authors are grateful for the initial work and extended 2520 comments provided by the many NENA participants. 2522 16. References 2524 16.1. Normative References 2526 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2527 Requirement Levels", BCP 14, RFC 2119, March 1997. 2529 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 2530 Locators", RFC 2392, August 1998. 2532 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 2533 Types", RFC 3023, January 2001. 2535 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2536 A., Peterson, J., Sparks, R., Handley, M., and E. 2537 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2538 June 2002. 2540 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2541 January 2004. 2543 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 2544 Format", RFC 4119, December 2005. 2546 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 2547 Registration Procedures", RFC 4288, December 2005. 2549 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2550 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2551 May 2008. 2553 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 2554 August 2011. 2556 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 2557 6351, August 2011. 2559 16.2. Informational References 2561 [I-D.iab-privacy-considerations] 2562 Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 2563 Morris, J., Hansen, M., and R. Smith, "Privacy 2564 Considerations for Internet Protocols", draft-iab-privacy- 2565 considerations-03 (work in progress), July 2012. 2567 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 2568 Emergency Context Resolution with Internet Technologies", 2569 RFC 5012, January 2008. 2571 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 2572 Tschofenig, "LoST: A Location-to-Service Translation 2573 Protocol", RFC 5222, August 2008. 2575 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 2576 5985, September 2010. 2578 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 2579 "Framework for Emergency Calling Using Internet 2580 Multimedia", RFC 6443, December 2011. 2582 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 2583 Communications Services in Support of Emergency Calling", 2584 BCP 181, RFC 6881, March 2013. 2586 Appendix A. XML Schema for vCard/xCard 2588 This section contains the vCard/xCard XML schema version of the Relax 2589 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 2590 XML schemas defined in this document. The schema in RFC 6351 2591 [RFC6351] is the normative source and this section is informative 2592 only. 2594 2595 2599 2605 2606 2607 vCard Format Specification 2608 2610 2611 2612 2613 2614 2615 2616 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2631 2632 2633 2635 2636 2637 2638 2639 2641 2642 2643 2645 2646 2647 2648 2649 2651 2652 2653 2656 2657 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2699 2700 2701 2702 2706 2707 2708 Section 5: Parameters 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 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 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 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 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 3635 3636 3637 3638 3639 3640 3641 3643 3644 3645 3646 3647 3648 3649 3651 3652 3653 3655 3657 3658 3659 3661 3662 3663 3664 3666 Authors' Addresses 3667 Brian Rosen 3668 NeuStar 3669 470 Conrad Dr. 3670 Mars, PA 16046 3671 US 3673 Phone: +1 724 382 1051 3674 Email: br@brianrosen.net 3676 Hannes Tschofenig 3677 Nokia Siemens Networks 3678 Linnoitustie 6 3679 Espoo 02600 3680 Finland 3682 Phone: +358 (50) 4871445 3683 Email: Hannes.Tschofenig@gmx.net 3684 URI: http://www.tschofenig.priv.at 3686 Roger Marshall 3687 TeleCommunication Systems, Inc. 3688 2401 Elliott Avenue 3689 Seattle, WA 98121 3690 US 3692 Phone: +1 206 792 2424 3693 Email: rmarshall@telecomsys.com 3694 URI: http://www.telecomsys.com 3696 Randall Gellens 3697 Qualcomm Technologies, Inc. 3698 5775 Morehouse Drive 3699 San Diego, CA 92121 3700 US 3702 Email: rg+ietf@qti.qualcomm.com