idnits 2.17.00 (12 Aug 2021) /tmp/idnits23208/draft-ietf-ecrit-additional-data-03.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1145 has weird spacing: '...ll-Info pur...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: There is much private data in this information. Local regulations may govern what data must be provided in emergency calls, but in general, the emergency call system is often aided by the kinds of information described in this document. There is a tradeoff between the privacy considerations and the utility of the data. Certainly, if the data cannot be protected, due to failure of the TLS mechanisms described here, data not required by regulation SHOULD not be sent. == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (March 13, 2012) is 3720 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 1145, but not defined ** 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 == Outdated reference: draft-ietf-ecrit-phonebcp has been published as RFC 6881 Summary: 3 errors (**), 0 flaws (~~), 7 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: September 14, 2012 Nokia Siemens Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 March 13, 2012 10 Additional Data related to an Emergency Call 11 draft-ietf-ecrit-additional-data-03.txt 13 Abstract 15 When an emergency call is sent to a Public Safety Answering Point 16 (PSAP), the device that sends it, as well as any service provider in 17 the path of the call, or access network may have information about 18 the call which the PSAP may be able to use. This document describes 19 an XML data structure that contains this kind of information in a 20 standardized form. A Uniform Resource Identifier (URI) that points 21 to the structure can be included in the SIP signaling with the call, 22 or the data may be included in the body of a SIP message. 24 Status of this Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on September 14, 2012. 41 Copyright Notice 43 Copyright (c) 2012 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 60 3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 8 61 4. Data Provider Information . . . . . . . . . . . . . . . . . . 9 62 4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 9 63 4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 9 64 4.3. Type of Data Provider ID . . . . . . . . . . . . . . . . . 10 65 4.4. Data Provider Contact URI . . . . . . . . . . . . . . . . 10 66 4.5. Data Provider Languages(s) Supported . . . . . . . . . . . 11 67 4.6. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 12 68 4.7. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 12 69 5. Service Information . . . . . . . . . . . . . . . . . . . . . 14 70 5.1. Service Environment . . . . . . . . . . . . . . . . . . . 14 71 5.2. Service Delivered by Provider to End User . . . . . . . . 14 72 5.3. Service Mobility Environment . . . . . . . . . . . . . . . 16 73 5.4. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 17 74 6. Device Information . . . . . . . . . . . . . . . . . . . . . . 18 75 6.1. Device Classification . . . . . . . . . . . . . . . . . . 18 76 6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 20 77 6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 20 78 6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 21 79 6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 21 80 6.6. Device/Service Specific Additional Data Structure . . . . 22 81 6.7. Device/Service Specific Additional Data Structure Type . . 23 82 6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 23 83 7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 25 84 7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 25 85 7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 25 86 8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 87 9. Security Considerations . . . . . . . . . . . . . . . . . . . 28 88 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 29 89 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30 90 11.1. Registry creation . . . . . . . . . . . . . . . . . . . . 30 91 11.1.1. Additional Call Data Service Delivered Registry . . . 30 92 11.1.2. Additional Call Data Device Classification 93 Registry . . . . . . . . . . . . . . . . . . . . . . 31 94 11.1.3. Additional Call Data Device ID Type Registry . . . . 32 95 11.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 32 96 11.3. URN Sub-Namespace Registration for provided-by 97 Registry Entry . . . . . . . . . . . . . . . . . . . . . . 32 98 11.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 33 99 11.4.1. MIME Content-type Registration for 100 'application/addDataProviderInfo+xml' . . . . . . . . 33 101 11.4.2. MIME Content-type Registration for 102 'application/addCallSvcInfo+xml' . . . . . . . . . . 34 103 11.4.3. MIME Content-type Registration for 104 'application/addDataDevInfo+xml' . . . . . . . . . . 35 105 11.4.4. MIME Content-type Registration for 106 'application/addCallSub+xml' . . . . . . . . . . . . 36 107 11.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 38 108 11.5.1. Registration for 109 urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 38 110 11.5.2. Registration for 111 urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 38 112 11.5.3. Registration for 113 urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 39 114 11.5.4. Registration for urn:ietf:params:xml:ns:addCallSub . 40 115 11.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 41 116 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43 117 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 118 13.1. Normative References . . . . . . . . . . . . . . . . . . . 44 119 13.2. Informational References . . . . . . . . . . . . . . . . . 44 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 46 122 1. Introduction 124 As communications devices increasingly utilize the Internet to 125 interconnect and communicate, users will expect to use such devices 126 to request help. The Internet Protocol suite provides many 127 advantages but also requires re-thinking of the traditional emergency 128 calling architecture. The IETF emergency services architecture, as 129 described in [RFC6443] and [I-D.ietf-ecrit-phonebcp], offers a much 130 richer communication exchange and thereby better situational 131 awareness for call takers. The richness comes in various forms, 132 including the multi-media communication capabilities (via voice, 133 video, instant messaging, and real-time text), but also via more 134 extensive flow of information. Sharing information between various 135 actors will enable more intelligent decision making and therefore 136 better response in case of an emergency. A pre-requisite is to offer 137 the technical capabilities to let call takers to gain access to this 138 information stored elsewhere (granted that they are authorized to 139 access it). 141 In general, there are four types of data exchanged: 143 Data Associated with a Call: While information is carried in the 144 call setup procedure itself (as part of the SIP headers as well as 145 in the body of the SIP message, there is additional data known by 146 the device making the call, or a service provider in the path of 147 the call including contact data, subscriber data, service data and 148 device data. 150 Data Associated with a Location: Location information is available 151 via the PIDF-LO element, which includes civic and geospatial 152 location, information about the entity that provided the data, 153 information about how the location was obtained (as expressed by 154 the element, see Section 2.2.3 of [RFC4119], and the 155 values registered in 156 http://www.iana.org/assignments/method-tokens/method-tokens.xml), 157 and which entity or organization supplied location information 158 (beyond the domain information that can be inferred from a signing 159 certificate) available via the element. However, 160 there may be data that is specific to the location not available 161 in the PIDF, such as floor plan, tenant and building owner contact 162 data, HVAC status, etc. 164 Data Associated with a Caller: This is personal data about a caller, 165 including medical information and emergency contact data. 167 Data associated with a PSAP: When a PSAP handles a call it develops 168 information about the call, which must be passed to subsequent 169 PSAPs, dispatchers and/or responders. 171 When an emergency call is sent to a PSAP, while there is a rich set 172 of data in the SIP message used for the call setup, the device, as 173 well as any other service provider in the path may have even more 174 information useful for a PSAP. This information may include the 175 identity and contact information of the service provider, subscriber 176 identity and contact information, the type of service the provider 177 offers, what kind of device is being used, etc. Some data is device 178 or service dependent data. For example, a car telematics system or 179 service may have crash information. A medical monitoring device may 180 have sensor data. While the details of the information may vary by 181 device or service, there needs to be a common way to send such data 182 to a PSAP. 184 This document focuses only on the data that can be obtained about a 185 call and a mechanism for transporting it in an existing SIP header 186 field, the Call-Info header, which is specified in Section 20.9 of 187 [RFC3261]. For this purpose a new token, namely 'emergencyCallData' 188 is defined to be carried in the "purpose" parameter. If the 189 "purpose" parameter is set to 'emergencyCallData' then the Call-Info 190 header contains a HTTPS URL that points to a service and data 191 structure with information about the call or is a CID that allows the 192 data structure itself to be placed in the body of the message. 193 Section 8 shows a SIP INVITE example containing such a Call-Info 194 header using the purpose parameter. 196 Besides a service provider in the path of a call, the access network 197 (which in the IETF emergency call architecture provides location in 198 the form of a PIDF-LO [RFC4119]) also has similar information that 199 would be valuable to the PSAP. This information is not specific to 200 the location itsef, but rather would provide descriptive information 201 having to do with the immediate circumstances about the provision of 202 the location (who the access network is, how to contact that entity, 203 what kind of service the access network provides, possibly subscriber 204 data, etc.). This data is similar in nearly every respect with the 205 data known by services providers in the path of the call. For this 206 reason, this document describes a "provided-by" namespace per 207 [RFC4119] for passing information known to the access network. 209 The data is defined as a series of "blocks" that represent a class of 210 information. Each of the blocks is a MIME type, and an extensible 211 set of these types constitute the data structure. A registry is 212 defined to list the block types that may be included. 214 The data structure contains an element which itself is a URI that has 215 device or service dependent data. Thus the common Additional Data 216 about a Call defined by this document contains a 'hook', in the form 217 of a URI, for a device or service dependent data structure. 219 2. Terminology 221 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 222 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 223 document are to be interpreted as described in RFC 2119 [RFC2119]. 225 3. Call-Info Specification 227 The Additional Data about a Call is information specific to a call 228 known by the device that sends it or a service provider in the path 229 of a call or in the access network the call originates in. The 230 Additional Data about a Call is a set of information blocks. Each 231 block is a MIME type, and any set of blocks may be included in the 232 set. 234 Two mechanisms are provided to transport the data set, namely 236 1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE 237 transaction with a Call-Info header containing a purpose of 238 "emergencyCallData". If the data is provided by reference, it 239 may be retrieved with an HTTPS Get from the URI. The URI MUST 240 specify an HTTPS scheme, and TLS protection for the data MUST be 241 negotiated. 243 2. The data may be supplied by value in a SIP INVITE or MESSAGE 244 message. In this case, Content Indirection (CID) [RFC2392] is 245 used, with the CID URL pointing to the body of the message. 247 More than one Call-Info header with an emergencyCallData purpose can 248 be expected, but at least one MUST be provided. The device MUST 249 provide one if no service provider is in the path of the call. The 250 device MAY insert one if it uses a service provider, and any 251 intermediary service provider SHOULD insert its own. When there are 252 multiple intermediaries, each intermediary SHOULD each insert one. 253 For example, a device may provide one, a telematics service provider 254 may provide one and the mobile carrier handling the call may provide 255 one. There may be circumstances where there is a service provider 256 who is unaware that the call is an emergency call and cannot 257 reasonably be expected to determine that it is an emergency call. In 258 that case, that service provider is not expected to provide 259 emergencyCallData. 261 Note: The access network MAY supply additional data as well. For 262 this purpose, this document defines a namespace and adds the 263 namespace to the "provided-by" registry defined by PIDF-LO [RFC4119]. 265 Additional data about a call is defined as a series of MIME objects, 266 each with an XML data structure contained inside. MIME-multipart is 267 used to enclose the XML documents and the sections below define them. 269 4. Data Provider Information 271 This block is intended to be provided by any service provider in the 272 path of the call or the access network provider. It includes 273 identification and contact information. This block SHOULD be 274 provided for every service provider in the path of the call, and the 275 access network provider. Devices also use this block to provide 276 identifying information. The MIME type is "addDataProviderInfo+xml". 278 4.1. Data Provider String 280 Data Element: Data Provider String 282 Use: Required 284 XML Element: 286 Description: This is a plain language string suitable for displaying 287 the name of the service provider that created the additional data 288 structure. If the device created the structure the value is 289 identical to the contact header in the SIP INVITE. 291 Reason for Need: Inform the call taker about the identity of the 292 entity providing the additional call data structure. 294 How Used by Call Taker: Allows the call taker to interpret the data 295 in this structure. The source of the information often influences 296 how the information is used, believed or verified. 298 4.2. Data Provider ID 300 Data Element: Data Provider ID 302 Use: Conditional. Must be provided if the service provider is 303 located in a jurisdiction that maintains such ids. Devices are 304 not required to provide it. 306 XML Element: 307 Description: A jurisdiction specific code for the provider shown in 308 the element that created the structure of the 309 call. This data SHOULD be provided if the local jurisdiction 310 maintains such an ID list. For example, in North America, this 311 would be a "NENA Company ID". Devices would not typically use 312 this element. 314 Reason for Need: Inform the call taker about the identity of the 315 entity providing the additional call data structure. 317 How Used by Call Taker: Where jurisdictions have lists of providers 318 the Data Provider ID can lead to a wealth of information. 320 4.3. Type of Data Provider ID 322 Data Element: Type of Data Provider ID 324 Use: Conditional. If Data Provider ID is provided, Type of Data 325 Provider ID is required. 327 XML Element: 329 Description: Identifies the type of data provider id being supplied 330 in the ProviderId data element. A registry will reflect the 331 following valid entries: 333 * NENA (CDMA) 335 * Other 337 Reason for Need: Identifies how to interpret the Data Provider ID. 339 How Used by Call Taker: Determines which provider ID registry to 340 consult for more information 342 4.4. Data Provider Contact URI 343 Data Element: Data Provider Contact URI 345 Use: Required 347 XML Element: 349 Description: For a service provider the contact SHOULD be a contact 350 URI. This must be a SIP URI. If a telephone number is the 351 contact address it should be provided in the form of 352 sip:telephonenumber@serviceprovider:user=phone. If the call is 353 from a device, this would reflect the contact information of the 354 owner of the device. When provided by a service provider, this 355 would be a URI to a 24/7 support organization tasked to provide 356 PSAP support for this emergency call. 358 Reason for Need: Additional data providers may need to be contacted 359 for error or other unusual circumstances. 361 How Used by Call Taker: To contact the supplier of the additional 362 data for assistance in handling the call. 364 4.5. Data Provider Languages(s) Supported 366 Data Element: Data Provider Language(s) supported 368 Use: Conditional 370 XML Element: 372 Description: Provided by's alpha 2-character code as defined in ISO 373 639-1:2002 374 (http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for 375 the representation of names of languages -- Part 1: Alpha-2 code 376 Multiple instances of this element may occur. Order is 377 significant; preferred language should appear first. This data is 378 required if a Data Provider Contact URI is provided. The content 379 must reflect the languages supported at the contact URI. 381 Reason for Need: Information needed to determine if emergency 382 service authority can communicate with the service provider or if 383 an interpreter will be needed. 385 How Used by Call Taker: If call taker cannot speak language(s) 386 supported by the service provider, a translation service will need 387 to be added to the conversation. 389 4.6. vCARD of Data Provider 391 Data Element: vCARD of Data Provider 393 Use: Optional 395 XML Element: 397 Description: There are many fields in the xCARD and the creator of 398 the data structure is encouraged to provide as much information as 399 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 400 minimum. N should contain name of support group or device owner 401 as appropriate. For encoding of the vCard this specification uses 402 the XML-based encoding specified in [RFC6351]. 404 and is hereinafter referred to as "xCard" 406 Reason for Need: Information needed to determine additional contact 407 information. 409 How Used by Call Taker: Assists call taker by providing additional 410 contact information that may not be included in the SIP invite or 411 the PIDF-LO. 413 4.7. addDataProviderInfo XML Schema 414 415 423 426 427 428 429 430 432 433 434 435 437 439 441 443 445 447 448 449 450 452 Figure 1: addDataProviderInfo XML Schema 454 5. Service Information 456 This block describes the service that the service provider provides 457 to the caller. It SHOULD be included by all SPs in the path of the 458 call. The mime type is "addCallSvcInfo+xml". 460 5.1. Service Environment 462 Data Element: Service Environment 464 Use: Required 466 XML Element: 468 Description: This element defines whether a call is from a business 469 or residence caller. Currently, the only valid entries are 470 'Business' or 'Residence'. 472 Reason for Need: To assist in determining equipment and manpower 473 requirements. 475 How Used by Call Taker: Information may be used to assist in 476 determining equipment and manpower requirements for emergency 477 responders. As the information is not always available, and the 478 registry is not all encompassing, this is at best advisory 479 information, but since it mimics a similar capability in some 480 current emergency calling systems, it is known to be valuable. 481 The service provider uses it's best information (such as a rate 482 plan, facilities used to deliver service or service description) 483 to determine the information and is not responsible for 484 determining the actual characteristics of the location where the 485 call originates from. 487 5.2. Service Delivered by Provider to End User 489 Data Element: Service Delivered by Provider to End User 491 Use: Required 492 XML Element: 494 Description: This defines the type of service the end user has 495 subscribed to. The implied mobility of this service can not be 496 relied upon. A registry will reflect the following initial valid 497 entries: 499 * Wireless Telephone Service: Includes Satellite, CDMA, GSM, 500 Wi-Fi, WiMAX, LTE (Long Term Evolution) 502 * Fixed Public Pay/Coin telephones: Any coin or credit card 503 operated device. 505 * One way outbound service 507 * Inmate call/service 509 * Soft dialtone/quick service/warm disconnect/suspended 511 * Multi-line telephone system (MLTS): Includes all PBX, Centrex, 512 key systems, Shared Tenant Service. 514 * Sensor, unattended: Includes devices that generate DATA ONLY. 515 This is one-way information exchange and there will be no other 516 form of communication. 518 * Sensor, attended: Includes devices that are supported by a 519 monitoring service provider or automatically open a two-way 520 communication path. 522 * Wireline: Plain Old Telephone Service (POTS). 524 * VoIP Telephone Service: A type of service that offers 525 communication over internet protocol, such as Fixed, Nomadic, 526 Mobile, Unknown 528 * Relay Service: a type of service where there is a human 3rd 529 party agent who provides some kind of additional assistance to 530 the caller. Includes sign language relay and telematics 531 services which provide a service assistant on the call. 533 * Remote (off premise extension) 535 There can be more than one value returned. For example, a VoIP 536 prison telephone service is a reasonable combination. 538 Reason for Need: Knowing the type of service may assist the PSAP 539 with the handling of the call. 541 How Used by Call Taker: Call takers often use this information to 542 determine what kinds of questions to ask callers, and how much to 543 rely on supportive information. An emergency call from a prison 544 is treated differently that a call from a sensor device. As the 545 information is not always available, and the registry is not all 546 encompassing, this is at best advisory information, but since it 547 mimics a similar capability in some current emergency calling 548 systems, it is known to be valuable. 550 5.3. Service Mobility Environment 552 Data Element: Service Mobility Environment 554 Use: Required 556 XML Element: 558 Description: This provides the service providers view of the 559 mobility of the caller. As the service provider may not know the 560 characteristics of the actual access network used, the value not 561 be relied upon. A registry will reflect the following initial 562 valid entries: 564 * Mobile: the device should be able to move at any time 566 * Fixed: the device is not expected to move unless the service is 567 relocated 569 * Nomadic: the device is not expected to move while on a call, 570 but may move between calls 572 Reason for Need: Knowing the service provider's belief of mobility 573 may assist the PSAP with the handling of the call. 575 How Used by Call Taker: To determine whether to assume the location 576 of the caller might change. 578 5.4. addCallSvcInfo XML Schema 580 581 588 591 592 593 594 596 598 600 601 602 603 605 Figure 2: addCallSvcInfo XML Schema 607 6. Device Information 609 This block provides information about the device used to place the 610 call. It should be provided by any service provider that knows what 611 device is being used, and by the device itself. The mime type is 612 "addDataDevInfo+xml". 614 6.1. Device Classification 616 Data Element: Device Classification 618 Use: Optional 620 XML Element: 622 Description: This data element defines the kind of device making the 623 emergency call. If the device provides the data structure, the 624 device information should be provided. If the service provider 625 provides the structure and it knows what the device is, the 626 service provider should provide the device information. Often the 627 carrier does not know what the device is. It is possible to 628 receive 2 Additional Data Associated with a Caller data 629 structures, one created by the device and one created by the 630 service provider. This Information describes the about the 631 device, not how it is being used. This data element defines the 632 kind of device making the emergency call. A registry will reflect 633 the following valid entries: 635 * Cordless handset 637 * Fixed phone 639 * Mobile handset 641 * ATA - analog terminal adapter 643 * Satellite phone 645 * Stationary computing device (alarm system, data sensor) 647 * Guardian devices 649 * Desktop PC 650 * Laptop computing device 652 * Tablet computing device 654 * Alarm system 656 * Data sensor 658 * Personal beacons (spot) 660 * Auto telematics (indicates VEDS data set) 662 * Trucking telematics 664 * Farm equipment telematics 666 * Marine telematics 668 * PDA (personal digital assistant) 670 * PND (personal navigation device) 672 * Smart phone 674 * Internet tablet 676 * Gaming console 678 * Video phone 680 * Other text device 682 * Not Available 684 Reason for Need: The device classification describes the capability 685 of the calling device and assists in identifying the meaning of 686 the emergency call location information that is being presented. 687 For example, does the device require human intervention to 688 initiate a call or is this call the result of programmed 689 instructions?. Does the calling device have the ability to update 690 location or condition changes? Is this device interactive or a 691 one-way reporting device? 693 How Used by Call Taker: May assist with location of caller. For 694 example, a cordless handset may be outside or next door. May 695 provide calltaker some context about the caller, the capabilities 696 of the device used for the call or the environment the device is 697 being used in. 699 6.2. Device Manufacturer 701 Data Element: Device Manufacturer 703 Use: Optional 705 XML Element: 707 Description: The plain language name of the manufacturer of the 708 device. 710 Reason for Need: Used by PSAP management for post-mortem 711 investigation/resolution. 713 How Used by Call Taker: Probably not used by calltaker, but by PSAP 714 management. 716 6.3. Device Model Number 718 Data Element: Device Model Number 720 Use: Optional 722 XML Element: 724 Description: Model number of the device. 726 Reason for Need: Used by PSAP management for after action 727 investigation/resolution. 729 How Used by Call Taker: Probably not used by calltaker, but by PSAP 730 management. 732 6.4. Unique Device Identifier 734 Data Element: Unique Device Identifier 736 Use: Optional 738 XML Element: 740 Description: String that identify the specific device making the 741 call or creating an event. 743 Reason for Need: Uniquely identifies the device as opposed to any 744 signaling identifiers encountered in the call signaling stream. 746 How Used by Call Taker: Probably not used by calltaker they would 747 need to refer to management for investigation. 749 6.5. Type of Device Identifier 751 Data Element: Type of Device Identifier 753 Use: Conditional: must be provided if DeviceID is provided 755 XML Element: 757 Description: Identifies the type of device identifier being 758 generated in the unique device identifier data element. A 759 registry will reflect the following valid entries: 761 * MEID (CDMA) 763 * ESN (Electronic Serial Number - superseded by MEID) 765 * MAC (Media Access Control) Address - any IEEE device with an 766 Ethernet, Wi-Fi connection 768 * WiMAX has a device certificate 770 * IMEI (International Mobile Equipment Identifier - GSM) 772 * Unique Device Identifier (Unique identifier for medical 773 devices) 775 * RFID (Radio Frequency Identification) 777 * Sensors (types to be identified in a future document version) 779 * Manufacturer Serial Number 781 * Other 783 Reason for Need: Identifies how to interpret the Unique Device 784 Identifier. 786 How Used by Call Taker: Additional information that may be used to 787 assist with call handling. 789 6.6. Device/Service Specific Additional Data Structure 791 Data Element: Device/service specific additional data structure 793 Use: Optional 795 XML Element: 797 Description: A URI representing additional data whose schema is 798 specific to the device or service which created it. An example is 799 the VEDs structure for a vehicle telematics device. The URI, when 800 dereferenced, MUST yield a data structure defined by the Device/ 801 service specific additional data type value. Different data may 802 be created by each classification; i.e., telematics creates VEDS 803 data set - can be different types of data depending on device. 805 Reason for Need: Provides device/service specific data that may be 806 used by the call taker and/or responders. 808 How Used by Call Taker: Provide information to guide call takers to 809 select appropriate responders, give appropriate pre-arrival 810 instructions to callers, and advise responders of what to be 811 prepared for. May be used by responders to guide assistance 812 provided. 814 6.7. Device/Service Specific Additional Data Structure Type 816 Data Element: Type of Device/service specific additional data 817 structure 819 Use: Conditional. MUST be provided when Device/service specific 820 additional URI is provided 822 XML Element: 824 Description: Value from a registry defined by this document to 825 describe the type of data that can be retrieved from the Device/ 826 service specific additional data structure. Initial values are: 828 * IEEE 1512 - USDOT Model for traffic incidents 830 * VEDS 832 Reason for Need: This data element will allow for identification of 833 externally defined schemas, which may have additional data that 834 will assist in emergency response. 836 How Used by Call Taker: This data element will allow the end user 837 (calltaker or first responder) to know what type of additional 838 data may be available to aid in providing the needed emergency 839 services. 841 Note: Information which is specific to a location or a caller 842 (person) should not be placed in this section. 844 6.8. addDataDevInfo XML Schema 845 846 853 856 857 858 859 861 863 865 867 869 871 873 874 875 876 878 Figure 3: addDataDevInfo XML Schema 880 7. Owner/Subscriber Information 882 This block describes the owner of the device (if provided by the 883 device) or the subscriber information, if provided by a service 884 provider. The contact location is not necessarily the location of 885 the caller or incident, but is rather the nominal contact address. 886 The mime type is "addCallSub+xml". 888 7.1. vCARD for Subscriber's Data 890 Data Element: xCARD for Subscriber's Data 892 Use: Conditional: Some services (e.g. prepaid phones, initialized 893 phones, etc.) may not have this information. 895 XML Element: 897 Description: Information known by the service provider or device 898 about the subscriber; i.e., Name, Address, Individual Telephone 899 Number, Main Telephone Number and any other data. N, ORG (if 900 appropriate), ADR, TEL, EMAIL are suggested at a minimum. 902 Reason for Need: When the caller is unable to provide information, 903 this data may be used to obtain it 905 How Used by Call Taker: Obtaining critical information about the 906 caller and possibly the location when it is not able to be 907 obtained otherwise. 909 7.2. addCallSub XML Schema 910 911 919 922 923 924 925 927 928 929 930 932 Figure 4: addCallSub XML Schema 934 8. Example 936 INVITE sips:bob@biloxi.example.com SIP/2.0 937 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 938 Max-Forwards: 70 939 To: Bob 940 From: Alice ;tag=9fxced76sl 941 Call-ID: 3848276298220188511@atlanta.example.com 942 Call-Info: ;purpose=icon, 943 ;purpose=info, 944 ;purpose=emergencyCallData 945 Geolocation: 946 Geolocation-Routing: no 947 Accept: application/sdp, application/pidf+xml 948 CSeq: 31862 INVITE 949 Contact: 950 Content-Type: multipart/mixed; boundary=boundary1 952 Content-Length: ... 954 --boundary1 956 Content-Type: application/sdp 958 ...SDP goes here 960 --boundary1 962 Content-Type: application/pidf+xml 963 Content-ID: 965 ...PIDF-LO goes here 967 --boundary1-- 969 Content-Type: application/pidf+xml 970 Content-ID: <1234567890@atlanta.example.com> 972 ...Additional Data goes here 974 --boundary1-- 976 Example: Attaching Additional Data via CID to a SIP INVITE 978 9. Security Considerations 980 The information in this data structure will usually be considered 981 private. HTTPS is specified to require the provider of the 982 information to validate the credentials of the requester. While the 983 creation of a PKI that has global scope may be difficult, the 984 alternatives to creating devices and services that can provide 985 critical information securely are more daunting. 987 The Call-info header with purpose='emergencyCallData' MUST only be 988 sent on an emergency call, which can be ascertained by the presence 989 of an emergency service urn in a Route header of a SIP message. 991 993 995 998 10. Privacy Considerations 1000 [Editor's Note: The privacy considerations outlined in 1001 [I-D.iab-privacy-considerations] need to be addressed here in a 1002 future version of this document. 1004 There is much private data in this information. Local regulations 1005 may govern what data must be provided in emergency calls, but in 1006 general, the emergency call system is often aided by the kinds of 1007 information described in this document. There is a tradeoff between 1008 the privacy considerations and the utility of the data. Certainly, 1009 if the data cannot be protected, due to failure of the TLS mechanisms 1010 described here, data not required by regulation SHOULD not be sent. 1012 11. IANA Considerations 1014 11.1. Registry creation 1016 11.1.1. Additional Call Data Service Delivered Registry 1018 This document creates a new registry called 'Additional Call Data 1019 Service Delivered'. As defined in [RFC5226], this registry operates 1020 under "Expert Review" rules. 1022 The content of this registry includes: 1024 Name: enumeration token of the service. 1026 Description: Short description identifying the service. 1028 The values defined are: 1030 +--------+----------------------------------------+ 1031 | Name | description | 1032 +--------+-------+--------------------------------+ 1033 | Wrless | Wireless Telephone Service: Includes | 1034 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 1035 | | LTE (Long Term Evolution) | 1036 | Coin | Fixed Public Pay/Coin telephones: Any | 1037 | | coin or credit card operated device | 1038 | 1way | One way outbound service | 1039 | Prison | Inmate call/service | 1040 | Temp | Soft dialtone/quick service/warm | 1041 | | disconnect/suspended | 1042 | MLTS | Multi-line telephone system: Includes | 1043 | | all PBX, Centrex, key systems, | 1044 | | Shared Tenant Service | 1045 | SenseU | Sensor, unattended: Includes devices | 1046 | | that generate DATA ONLY. This is | 1047 | | one-way information exchange and | 1048 | | there will be no other form of | 1049 | | communication | 1050 | SenseA | Sensor, attended: Includes devices | 1051 | | that are supported by a monitoring | 1052 | | service provider or automatically | 1053 | | open a two-way communication path | 1054 | POTS | Wireline: Plain Old Telephone Service | 1055 | VOIP | VoIP Telephone Service: A type of | 1056 | | service that offers communication | 1057 | | over internet protocol, such as Fixed| 1058 | | Nomadic, Mobile, ... | 1059 +--------+-------+--------------------------------+ 1061 11.1.2. Additional Call Data Device Classification Registry 1063 This document creates a new registry called 'Additional Call Data 1064 Device Classification'. As defined in [RFC5226], this registry 1065 operates under "Expert Review" rules. 1067 The content of this registry includes: 1069 Name: enumeration token of the device classification. 1071 Description: Short description identifying the device type. 1073 The values defined are: 1075 +--------+----------------------------------------+ 1076 | Name | description | 1077 +--------+-------+--------------------------------+ 1078 |Cordless| Cordless handset | 1079 | Fixed | Fixed phone | 1080 | Mobile | Mobile handset | 1081 | ATA | analog terminal adapter | 1082 |Satphone| Satellite phone | 1083 | FSense | Stationary computing device (alarm | 1084 | | system, data sensor) | 1085 | Guard | Guardian devices | 1086 | Desktop| Desktop PC | 1087 | Laptop | Laptop computing device | 1088 | Tablet | Tablet computing device | 1089 | Alarm | Alarm system | 1090 | MSense | Mobile Data sensor | 1091 | Beacon | Personal beacons (spot) | 1092 | Auto | Auto telematics | 1093 | Truck | Truck telematics | 1094 | Farm | Farm equipment telematics | 1095 | Marine | Marine telematics | 1096 | PDA | Personal digital assistant | 1097 | PND | Personal navigation device) | 1098 | SmrtPhn| Smart phone | 1099 | Itab | Internet tablet | 1100 | Game | Gaming console | 1101 | Video | Video phone | 1102 | Text | Other text device | 1103 | NA | Not Available | 1104 +--------+----------------------------------------+ 1106 11.1.3. Additional Call Data Device ID Type Registry 1108 This document creates a new registry called 'Additional Call Data 1109 Device ID Type'. As defined in [RFC5226], this registry operates 1110 under "Expert Review" rules. 1112 The content of this registry includes: 1114 Name: enumeration token of the device id type. 1116 Description: Short description identifying the type of device id. 1118 The values defined are: 1120 +--------+----------------------------------------+ 1121 | Name | description | 1122 +--------+-------+--------------------------------+ 1123 | MEID | Mobile Equipment Identifier (CDMA) | 1124 | ESN | Electronic Serial Number(GSM) | 1125 | MAC | Media Access Control Address (IEEE) | 1126 | WiMAX | device certificate unique id | 1127 | IMEI | International Mobile Equipment ID (GSM)| 1128 | UDI | Unique Device Identifier (medical) | 1129 | RFID | Radio Frequency Identification | 1130 | Sense | Sensors (types to be identified ) | 1131 | SN | Manufacturer Serial Number | 1132 | Other | Other | 1133 +--------+----------------------------------------+ 1135 11.2. 'emergencyCallData' Purpose Parameter Value 1137 This document defines the 'emergencyCallData' value for the "purpose" 1138 parameter of the Call-Info header field. The Call-Info header and 1139 the corresponding registry for the 'purpose' parameter was 1140 established with RFC 3261 [RFC3261]. 1142 Header Parameter New 1143 Field Name Value Reference 1144 ---------- --------- ----------------- --------- 1145 Call-Info purpose emergencyCallData [This RFC] 1147 11.3. URN Sub-Namespace Registration for provided-by Registry Entry 1149 This section registers the namespace specified in ??? in the 1150 provided-by registry established by RFC 4119. 1152 11.4. MIME Registrations 1154 11.4.1. MIME Content-type Registration for 'application/ 1155 addDataProviderInfo+xml' 1157 This specification requests the registration of a new MIME type 1158 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1159 RFC 3023 [RFC3023]. 1161 MIME media type name: application 1163 MIME subtype name: addDataProviderInfo+xml 1165 Mandatory parameters: none 1167 Optional parameters: charset 1169 Indicates the character encoding of enclosed XML. 1171 Encoding considerations: 1173 Uses XML, which can employ 8-bit characters, depending on the 1174 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1176 Security considerations: 1178 This content type is designed to carry the data provider 1179 information, which is a sub-category of additional data about an 1180 emergency call. 1182 Since this data contains personal information appropriate 1183 precautions have to be taken to limit unauthorized access, 1184 inappropriate disclosure to third parties, and eavesdropping of 1185 this information. Please refer to Section 9 and Section 10 for 1186 more information. 1188 Interoperability considerations: None 1190 Published specification: [TBD: This specification] 1192 Applications which use this media type: Emergency Services 1194 Additional information: 1196 Magic Number: None 1198 File Extension: .xml 1199 Macintosh file type code: 'TEXT' 1201 Personal and email address for further information: Hannes 1202 Tschofenig, Hannes.Tschofenig@gmx.net 1204 Intended usage: LIMITED USE 1206 Author: This specification is a work item of the IETF ECRIT 1207 working group, with mailing list address . 1209 Change controller: The IESG 1211 11.4.2. MIME Content-type Registration for 'application/ 1212 addCallSvcInfo+xml' 1214 This specification requests the registration of a new MIME type 1215 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1216 RFC 3023 [RFC3023]. 1218 MIME media type name: application 1220 MIME subtype name: addCallSvcInfo+xml 1222 Mandatory parameters: none 1224 Optional parameters: charset 1226 Indicates the character encoding of enclosed XML. 1228 Encoding considerations: 1230 Uses XML, which can employ 8-bit characters, depending on the 1231 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1233 Security considerations: 1235 This content type is designed to carry the service information, 1236 which is a sub-category of additional data about an emergency 1237 call. 1239 Since this data contains personal information appropriate 1240 precautions have to be taken to limit unauthorized access, 1241 inappropriate disclosure to third parties, and eavesdropping of 1242 this information. Please refer to Section 9 and Section 10 for 1243 more information. 1245 Interoperability considerations: None 1247 Published specification: [TBD: This specification] 1249 Applications which use this media type: Emergency Services 1251 Additional information: 1253 Magic Number: None 1255 File Extension: .xml 1257 Macintosh file type code: 'TEXT' 1259 Personal and email address for further information: Hannes 1260 Tschofenig, Hannes.Tschofenig@gmx.net 1262 Intended usage: LIMITED USE 1264 Author: This specification is a work item of the IETF ECRIT 1265 working group, with mailing list address . 1267 Change controller: The IESG 1269 11.4.3. MIME Content-type Registration for 'application/ 1270 addDataDevInfo+xml' 1272 This specification requests the registration of a new MIME type 1273 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1274 RFC 3023 [RFC3023]. 1276 MIME media type name: application 1278 MIME subtype name: addDataDevInfo+xml 1280 Mandatory parameters: none 1282 Optional parameters: charset 1284 Indicates the character encoding of enclosed XML. 1286 Encoding considerations: 1288 Uses XML, which can employ 8-bit characters, depending on the 1289 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1291 Security considerations: 1293 This content type is designed to carry the device information 1294 information, which is a sub-category of additional data about an 1295 emergency call. 1297 Since this data contains personal information appropriate 1298 precautions have to be taken to limit unauthorized access, 1299 inappropriate disclosure to third parties, and eavesdropping of 1300 this information. Please refer to Section 9 and Section 10 for 1301 more information. 1303 Interoperability considerations: None 1305 Published specification: [TBD: This specification] 1307 Applications which use this media type: Emergency Services 1309 Additional information: 1311 Magic Number: None 1313 File Extension: .xml 1315 Macintosh file type code: 'TEXT' 1317 Personal and email address for further information: Hannes 1318 Tschofenig, Hannes.Tschofenig@gmx.net 1320 Intended usage: LIMITED USE 1322 Author: This specification is a work item of the IETF ECRIT 1323 working group, with mailing list address . 1325 Change controller: The IESG 1327 11.4.4. MIME Content-type Registration for 'application/addCallSub+xml' 1329 This specification requests the registration of a new MIME type 1330 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1331 RFC 3023 [RFC3023]. 1333 MIME media type name: application 1335 MIME subtype name: addCallSub+xml 1336 Mandatory parameters: none 1338 Optional parameters: charset 1340 Indicates the character encoding of enclosed XML. 1342 Encoding considerations: 1344 Uses XML, which can employ 8-bit characters, depending on the 1345 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1347 Security considerations: 1349 This content type is designed to carry owner/subscriber 1350 information, which is a sub-category of additional data about an 1351 emergency call. 1353 Since this data contains personal information appropriate 1354 precautions have to be taken to limit unauthorized access, 1355 inappropriate disclosure to third parties, and eavesdropping of 1356 this information. Please refer to Section 9 and Section 10 for 1357 more information. 1359 Interoperability considerations: None 1361 Published specification: [TBD: This specification] 1363 Applications which use this media type: Emergency Services 1365 Additional information: 1367 Magic Number: None 1369 File Extension: .xml 1371 Macintosh file type code: 'TEXT' 1373 Personal and email address for further information: Hannes 1374 Tschofenig, Hannes.Tschofenig@gmx.net 1376 Intended usage: LIMITED USE 1378 Author: This specification is a work item of the IETF ECRIT 1379 working group, with mailing list address . 1381 Change controller: The IESG 1383 11.5. URN Sub-Namespace Registration 1385 11.5.1. Registration for urn:ietf:params:xml:ns:addDataProviderInfo 1387 This section registers a new XML namespace, as per the guidelines in 1388 RFC 3688 [RFC3688]. 1390 URI: urn:ietf:params:xml:ns:addDataProviderInfo 1392 Registrant Contact: IETF, ECRIT working group, , as 1393 delegated by the IESG . 1395 XML: 1397 BEGIN 1398 1399 1401 1402 1403 1405 Namespace for Additional Emergency Call Data: 1406 Data Provider Information 1407 1408 1409

Namespace for Additional Data related to an Emergency Call

1410

Data Provider Information

1411

See [TBD: This document].

1412 1413 1414 END 1416 11.5.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo 1418 This section registers a new XML namespace, as per the guidelines in 1419 RFC 3688 [RFC3688]. 1421 URI: urn:ietf:params:xml:ns:addCallSvcInfo 1423 Registrant Contact: IETF, ECRIT working group, , as 1424 delegated by the IESG . 1426 XML: 1428 BEGIN 1429 1430 1432 1433 1434 1436 Namespace for Additional Emergency Call Data: 1437 Service Information 1438 1439 1440

Namespace for Additional Data related to an Emergency Call

1441

Service Information

1442

See [TBD: This document].

1443 1444 1445 END 1447 11.5.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo 1449 This section registers a new XML namespace, as per the guidelines in 1450 RFC 3688 [RFC3688]. 1452 URI: urn:ietf:params:xml:ns:addDataDevInfo 1454 Registrant Contact: IETF, ECRIT working group, , as 1455 delegated by the IESG . 1457 XML: 1459 BEGIN 1460 1461 1463 1464 1465 1467 Namespace for Additional Emergency Call Data: 1468 Device Information 1469 1470 1471

Namespace for Additional Data related to an Emergency Call

1472

Device Information

1473

See [TBD: This document].

1474 1475 1476 END 1478 11.5.4. Registration for urn:ietf:params:xml:ns:addCallSub 1480 This section registers a new XML namespace, as per the guidelines in 1481 RFC 3688 [RFC3688]. 1483 URI: urn:ietf:params:xml:ns:addCallSub 1485 Registrant Contact: IETF, ECRIT working group, , as 1486 delegated by the IESG . 1488 XML: 1490 BEGIN 1491 1492 1494 1495 1496 1498 Namespace for Additional Emergency Call Data: 1499 Owner/Subscriber Information 1500 1501 1502

Namespace for Additional Data related to an Emergency Call

1503

Owner/Subscriber Information

1504

See [TBD: This document].

1505 1506 1507 END 1509 11.6. Schema Registrations 1511 This specification registers four schemas, as per the guidelines in 1512 RFC 3688 [RFC3688]. 1514 URI: 1515 urn:ietf:params:xml:schema:additional-data:addDataProviderInfo 1517 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1518 delegated by the IESG (iesg@ietf.org). 1520 XML: The XML schema can be found in Figure 1. 1522 URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo 1524 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 1525 delegated by the IESG (iesg@ietf.org). 1527 XML: The XML schema can be found in Figure 2. 1529 URI: urn:ietf:params:xml:schema:additional-data:addDataDevInfo 1531 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1532 delegated by the IESG (iesg@ietf.org). 1534 XML: The XML schema can be found in Figure 3. 1536 URI: urn:ietf:params:xml:schema:additional-data:addCallSub 1538 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1539 delegated by the IESG (iesg@ietf.org). 1541 XML: The XML schema can be found in Figure 4. 1543 12. Acknowledgments 1545 The authors would like to thank the following persons for their work 1546 in the NENA Data Technical Committee: Delaine Arnold (Data Technical 1547 Committee Chair), Marc Berryman, Erica Aubut (Data Technical 1548 Committee Vice-Chair), Susan Sherwood, Ric Atkins, Patty Bluhm, 1549 Eileen Boroski, David Connel, Maryls Davis, Paul-David de la Rosby, 1550 Gordon Chinander, David Froneberger, Marilyn Haroutunian, Roger 1551 Hixson, Rick Jones, Roger Marshall, Tom Muehleisen, Ira Pyles, Carl 1552 Reed, Susan Seet, and Skip Walls. The authors would also like to 1553 thank Tom Breen, Technical Committee Chair/Liaison; Busam, Technical 1554 Committee Vice-Chair/Liaison; Pete Eggimann, Operations Committee 1555 Chair/Liaison; Wendy Lively, Operations Committee Chair/Liaison; 1556 Roger Hixson, Technical Director; and Rick Jones, Operations Issues 1557 Director for their support and assistance. 1559 [Editor's Note: Add the participants of the NENA Additional Data 1560 Working group lead by Matt Serra.] 1562 13. References 1564 13.1. Normative References 1566 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1567 Requirement Levels", BCP 14, RFC 2119, March 1997. 1569 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 1570 Locators", RFC 2392, August 1998. 1572 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1573 Types", RFC 3023, January 2001. 1575 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 1576 A., Peterson, J., Sparks, R., Handley, M., and E. 1577 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 1578 June 2002. 1580 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1581 January 2004. 1583 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1584 Format", RFC 4119, December 2005. 1586 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1587 Registration Procedures", BCP 13, RFC 4288, December 2005. 1589 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1590 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1591 May 2008. 1593 [RFC6351] Perreault, S., "xCard: vCard XML Representation", 1594 RFC 6351, August 2011. 1596 13.2. Informational References 1598 [I-D.iab-privacy-considerations] 1599 Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., and 1600 J. Morris, "Privacy Considerations for Internet 1601 Protocols", draft-iab-privacy-considerations-02 (work in 1602 progress), March 2012. 1604 [I-D.ietf-ecrit-phonebcp] 1605 Rosen, B. and J. Polk, "Best Current Practice for 1606 Communications Services in support of Emergency Calling", 1607 draft-ietf-ecrit-phonebcp-20 (work in progress), 1608 September 2011. 1610 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1611 "Framework for Emergency Calling Using Internet 1612 Multimedia", RFC 6443, December 2011. 1614 Authors' Addresses 1616 Brian Rosen 1617 NeuStar 1618 470 Conrad Dr. 1619 Mars, PA 16046 1620 US 1622 Phone: +1 724 382 1051 1623 Email: br@brianrosen.net 1625 Hannes Tschofenig 1626 Nokia Siemens Networks 1627 Linnoitustie 6 1628 Espoo 02600 1629 Finland 1631 Phone: +358 (50) 4871445 1632 Email: Hannes.Tschofenig@gmx.net 1633 URI: http://www.tschofenig.priv.at 1635 Roger Marshall 1636 TeleCommunication Systems, Inc. 1637 2401 Elliott Avenue 1638 Seattle, WA 98121 1639 US 1641 Phone: +1 206 792 2424 1642 Email: rmarshall@telecomsys.com 1643 URI: http://www.telecomsys.com