idnits 2.17.1 draft-ietf-ecrit-additional-data-04.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 1253 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. -- The document date (July 16, 2012) is 4299 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 1253, 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: A later version (-09) exists of draft-iab-privacy-considerations-03 Summary: 3 errors (**), 0 flaws (~~), 5 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: January 17, 2013 Nokia Siemens Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 July 16, 2012 10 Additional Data related to an Emergency Call 11 draft-ietf-ecrit-additional-data-04.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 January 17, 2013. 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 . . . . . . . . . . . . . . . . . . 10 62 4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 10 63 4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 10 64 4.3. Type of Data Provider ID . . . . . . . . . . . . . . . . . 11 65 4.4. Data Provider Contact URI . . . . . . . . . . . . . . . . 12 66 4.5. Data Provider Languages(s) Supported . . . . . . . . . . . 12 67 4.6. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 13 68 4.7. Subcontractor Principal . . . . . . . . . . . . . . . . . 13 69 4.8. Subcontractor Priority . . . . . . . . . . . . . . . . . . 14 70 4.9. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 14 71 5. Service Information . . . . . . . . . . . . . . . . . . . . . 16 72 5.1. Service Environment . . . . . . . . . . . . . . . . . . . 16 73 5.2. Service Delivered by Provider to End User . . . . . . . . 16 74 5.3. Service Mobility Environment . . . . . . . . . . . . . . . 18 75 5.4. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 19 76 6. Device Information . . . . . . . . . . . . . . . . . . . . . . 20 77 6.1. Device Classification . . . . . . . . . . . . . . . . . . 20 78 6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 22 79 6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 22 80 6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 23 81 6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 23 82 6.6. Device/Service Specific Additional Data Structure . . . . 24 83 6.7. Device/Service Specific Additional Data Structure Type . . 25 84 6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 25 85 7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 27 86 7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 27 87 7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 27 88 8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 89 9. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 30 90 10. Security Considerations . . . . . . . . . . . . . . . . . . . 31 91 11. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 32 92 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 93 12.1. Registry creation . . . . . . . . . . . . . . . . . . . . 33 94 12.1.1. Additional Call Data Blocks Registry . . . . . . . . 33 95 12.1.2. Additional Call Data Service Delivered Registry . . . 33 96 12.1.3. Additional Call Data Device Classification 97 Registry . . . . . . . . . . . . . . . . . . . . . . 34 98 12.1.4. Additional Call Data Device ID Type Registry . . . . 35 99 12.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 36 100 12.3. URN Sub-Namespace Registration for provided-by 101 Registry Entry . . . . . . . . . . . . . . . . . . . . . . 36 102 12.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 36 103 12.4.1. MIME Content-type Registration for 104 'application/addDataProviderInfo+xml' . . . . . . . . 36 105 12.4.2. MIME Content-type Registration for 106 'application/addCallSvcInfo+xml' . . . . . . . . . . 38 107 12.4.3. MIME Content-type Registration for 108 'application/addDataDevInfo+xml' . . . . . . . . . . 39 109 12.4.4. MIME Content-type Registration for 110 'application/addCallSub+xml' . . . . . . . . . . . . 40 111 12.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 41 112 12.5.1. Registration for 113 urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 41 114 12.5.2. Registration for 115 urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 42 116 12.5.3. Registration for 117 urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 43 118 12.5.4. Registration for urn:ietf:params:xml:ns:addCallSub . 44 119 12.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 45 120 12.7. VCard Parameter Value Registration . . . . . . . . . . . . 46 121 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47 122 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 123 14.1. Normative References . . . . . . . . . . . . . . . . . . . 48 124 14.2. Informational References . . . . . . . . . . . . . . . . . 48 125 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50 127 1. Introduction 129 As communications devices increasingly utilize the Internet to 130 interconnect and communicate, users will expect to use such devices 131 to request help. The Internet Protocol suite provides many 132 advantages but also requires re-thinking of the traditional emergency 133 calling architecture. The IETF emergency services architecture, as 134 described in [RFC6443] and [I-D.ietf-ecrit-phonebcp], offers a much 135 richer communication exchange and thereby better situational 136 awareness for call takers. The richness comes in various forms, 137 including the multi-media communication capabilities (via voice, 138 video, instant messaging, and real-time text), but also via more 139 extensive flow of information. Sharing information between various 140 actors will enable more intelligent decision making and therefore 141 better response in case of an emergency. A pre-requisite is to offer 142 the technical capabilities to let call takers to gain access to this 143 information stored elsewhere (granted that they are authorized to 144 access it). 146 In general, there are four types of data exchanged: 148 Data Associated with a Call: While information is carried in the 149 call setup procedure itself (as part of the SIP headers as well as 150 in the body of the SIP message, there is additional data known by 151 the device making the call, or a service provider in the path of 152 the call including contact data, subscriber data, service data and 153 device data. 155 Data Associated with a Location: Location information is available 156 via the PIDF-LO element, which includes civic and geospatial 157 location, information about the entity that provided the data, 158 information about how the location was obtained (as expressed by 159 the element, see Section 2.2.3 of [RFC4119], and the 160 values registered in 161 http://www.iana.org/assignments/method-tokens/method-tokens.xml), 162 and which entity or organization supplied location information 163 (beyond the domain information that can be inferred from a signing 164 certificate) available via the element. However, 165 there may be data that is specific to the location not available 166 in the PIDF, such as floor plan, tenant and building owner contact 167 data, HVAC status, etc. 169 Data Associated with a Caller: This is personal data about a caller, 170 including medical information and emergency contact data. 172 Data associated with a PSAP: When a PSAP handles a call it develops 173 information about the call, which must be passed to subsequent 174 PSAPs, dispatchers and/or responders. 176 When an emergency call is sent to a PSAP, while there is a rich set 177 of data in the SIP message used for the call setup, the device, as 178 well as any other service provider in the path may have even more 179 information useful for a PSAP. This information may include the 180 identity and contact information of the service provider, subscriber 181 identity and contact information, the type of service the provider 182 offers, what kind of device is being used, etc. Some data is device 183 or service dependent data. For example, a car telematics system or 184 service may have crash information. A medical monitoring device may 185 have sensor data. While the details of the information may vary by 186 device or service, there needs to be a common way to send such data 187 to a PSAP. 189 This document focuses only on the data that can be obtained about a 190 call and a mechanism for transporting it in an existing SIP header 191 field, the Call-Info header, which is specified in Section 20.9 of 192 [RFC3261]. For this purpose a new token, namely 'emergencyCallData' 193 is defined to be carried in the "purpose" parameter. If the 194 "purpose" parameter is set to 'emergencyCallData' then the Call-Info 195 header contains a HTTPS URL that points to a service and data 196 structure with information about the call or is a CID that allows the 197 data structure itself to be placed in the body of the message. 198 Section 8 shows a SIP INVITE example containing such a Call-Info 199 header using the purpose parameter. 201 Besides a service provider in the path of a call, the access network 202 (which in the IETF emergency call architecture provides location in 203 the form of a PIDF-LO [RFC4119]) also has similar information that 204 would be valuable to the PSAP. This information is not specific to 205 the location itsef, but rather would provide descriptive information 206 having to do with the immediate circumstances about the provision of 207 the location (who the access network is, how to contact that entity, 208 what kind of service the access network provides, possibly subscriber 209 data, etc.). This data is similar in nearly every respect with the 210 data known by services providers in the path of the call. For this 211 reason, this document describes a "provided-by" namespace per 212 [RFC4119] for passing information known to the access network. 214 The data is defined as a series of "blocks" that represent a class of 215 information. Each of the blocks is a MIME type, and an extensible 216 set of these types constitute the data structure. A registry is 217 defined to list the block types that may be included. 219 The data structure contains an element which itself is a URI that has 220 device or service dependent data. Thus the common Additional Data 221 about a Call defined by this document contains a 'hook', in the form 222 of a URI, for a device or service dependent data structure. 224 2. Terminology 226 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 227 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 228 document are to be interpreted as described in RFC 2119 [RFC2119]. 230 3. Call-Info Specification 232 The Additional Data about a Call is information specific to a call 233 known by the device that sends it or a service provider in the path 234 of a call or in the access network the call originates in. The 235 Additional Data about a Call is a set of information blocks. Each 236 block is a MIME type, and any set of blocks may be included in the 237 set. 239 Two mechanisms are provided to transport the data set, namely 241 1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE 242 transaction with a Call-Info header containing a purpose of 243 "emergencyCallData". If the data is provided by reference, it 244 may be retrieved with an HTTPS Get from the URI. The URI MUST 245 specify an HTTPS scheme, and TLS protection for the data MUST be 246 negotiated. 248 2. The data may be supplied by value in a SIP INVITE or MESSAGE 249 message. In this case, Content Indirection (CID) [RFC2392] is 250 used, with the CID URL pointing to the body of the message. 252 More than one Call-Info header with an emergencyCallData purpose can 253 be expected, but at least one MUST be provided. The device MUST 254 provide one if no service provider is in the path of the call. The 255 device MAY insert one if it uses a service provider, and any 256 intermediary service provider SHOULD insert its own. When there are 257 multiple intermediaries, each intermediary SHOULD each insert one. 258 For example, a device may provide one, a telematics service provider 259 may provide one and the mobile carrier handling the call may provide 260 one. There may be circumstances where there is a service provider 261 who is unaware that the call is an emergency call and cannot 262 reasonably be expected to determine that it is an emergency call. In 263 that case, that service provider is not expected to provide 264 emergencyCallData. 266 Note: The access network MAY supply additional data as well. For 267 this purpose, this document defines a namespace and adds the 268 namespace to the "provided-by" registry defined by PIDF-LO [RFC4119]. 270 In regions where callers can elect to suppress certain personally 271 identifying information, the network or PSAP functionality can 272 inspect privacy flags within the SIP headers to determine what 273 information may be passed, stored, or displayed to comply with local 274 policy or law. 276 Additional data about a call is defined as a series of MIME objects, 277 each with an XML data structure contained inside. MIME-multipart is 278 used to enclose the XML documents and the sections below define them. 279 When additional data is passed by value, the CID URL points to one of 280 the blocks, and a link is provided in each of the other blocks to 281 link to the next block. When additional data is provided by 282 reference, the data is retrieved with an HTTP Get operation, which 283 returns a multi-part MIME header and a set of MIME blocks threaded 284 with the links. A registry of allowed types is created by this 285 document. Every block MUST be one of the types in the registry. 287 4. Data Provider Information 289 This block is intended to be provided by any service provider in the 290 path of the call or the access network provider. It includes 291 identification and contact information. This block SHOULD be 292 provided for every service provider in the path of the call, and the 293 access network provider. Devices also use this block to provide 294 identifying information. The MIME type is "addDataProviderInfo+xml". 296 4.1. Data Provider String 298 Data Element: Data Provider String 300 Use: Required 302 XML Element: 304 Description: This is a plain language string suitable for displaying 305 the name of the service provider that created the additional data 306 structure. If the device created the structure the value is 307 identical to the contact header in the SIP INVITE. 309 Reason for Need: Inform the call taker about the identity of the 310 entity providing the additional call data structure. 312 How Used by Call Taker: Allows the call taker to interpret the data 313 in this structure. The source of the information often influences 314 how the information is used, believed or verified. 316 4.2. Data Provider ID 318 Data Element: Data Provider ID 320 Use: Conditional. Must be provided if the service provider is 321 located in a jurisdiction that maintains such ids. Devices are 322 not required to provide it. 324 XML Element: 325 Description: A jurisdiction specific code for the provider shown in 326 the element that created the structure of the 327 call. This data SHOULD be provided if the local jurisdiction 328 maintains such an ID list. For example, in North America, this 329 would be a "NENA Company ID". Devices would not typically use 330 this element. 332 Reason for Need: Inform the call taker about the identity of the 333 entity providing the additional call data structure. 335 How Used by Call Taker: Where jurisdictions have lists of providers 336 the Data Provider ID can lead to a wealth of information. 338 4.3. Type of Data Provider ID 340 Data Element: Type of Data Provider ID 342 Use: Conditional. If Data Provider ID is provided, Type of Data 343 Provider ID is required. 345 XML Element: 347 Description: Identifies the type of data provider id being supplied 348 in the ProviderId data element. A registry will reflect the 349 following valid entries: 351 * Access Provider 353 * Origination Network Provider 355 * ServiceProviderSubcontractor 357 * Other 359 Reason for Need: Identifies how to interpret the Data Provider ID. 361 How Used by Call Taker: Determines which provider ID registry to 362 consult for more information 364 4.4. Data Provider Contact URI 366 Data Element: Data Provider Contact URI 368 Use: Required 370 XML Element: 372 Description: For a service provider the contact SHOULD be a contact 373 URI. This must be a SIP URI. If a telephone number is the 374 contact address it should be provided in the form of 375 sip:telephonenumber@serviceprovider:user=phone. If the call is 376 from a device, this would reflect the contact information of the 377 owner of the device. When provided by a service provider, this 378 would be a URI to a 24/7 support organization tasked to provide 379 PSAP support for this emergency call. 381 Reason for Need: Additional data providers may need to be contacted 382 for error or other unusual circumstances. 384 How Used by Call Taker: To contact the supplier of the additional 385 data for assistance in handling the call. 387 4.5. Data Provider Languages(s) Supported 389 Data Element: Data Provider Language(s) supported 391 Use: Conditional 393 XML Element: 395 Description: Provided by's alpha 2-character code as defined in ISO 396 639-1:2002 397 (http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for 398 the representation of names of languages -- Part 1: Alpha-2 code 399 Multiple instances of this element may occur. Order is 400 significant; preferred language should appear first. This data is 401 required if a Data Provider Contact URI is provided. The content 402 must reflect the languages supported at the contact URI. 404 Reason for Need: Information needed to determine if emergency 405 service authority can communicate with the service provider or if 406 an interpreter will be needed. 408 How Used by Call Taker: If call taker cannot speak language(s) 409 supported by the service provider, a translation service will need 410 to be added to the conversation. 412 4.6. vCARD of Data Provider 414 Data Element: vCARD of Data Provider 416 Use: Optional 418 XML Element: 420 Description: There are many fields in the xCARD and the creator of 421 the data structure is encouraged to provide as much information as 422 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 423 minimum. N should contain name of support group or device owner 424 as appropriate. If more than one TEL property is provided, a 425 parameter from the vCard Property Value registry MUST be specified 426 on each TEL. For encoding of the vCard this specification uses 427 the XML-based encoding specified in [RFC6351]. 429 and is hereinafter referred to as "xCard" 431 Reason for Need: Information needed to determine additional contact 432 information. 434 How Used by Call Taker: Assists call taker by providing additional 435 contact information that may not be included in the SIP invite or 436 the PIDF-LO. 438 4.7. Subcontractor Principal 440 Data Element: Subcontractor Principal 442 XML Element: 443 Description: If the data provider is a subcontractor to an access 444 provider or origination network, this element contains the 445 DataProviderString of the access provider or origination network 446 to indicate which provider the subcontractor is working for. This 447 data is required if the Data Provider type is subcontractor. 449 Reason for Need: Identify the entity the subcontractor works for. 451 How Used by Call Taker: Allows the call taker to understand what the 452 relationship between data providers and the service providers in 453 the path of the call are. 455 4.8. Subcontractor Priority 457 Data Element: Subcontractor Priority 459 Use: Required 461 XML Element: 463 Description: If the subcontractor should be contacted first, this 464 element should have a "sub" value. If the access or origination 465 service provider should be contacted first, this element should 466 have a "main" value. This data is required if the Data Provider 467 type is "subcontractor". 469 Reason for Need: Inform the call taker whether the network operator 470 or the subcontractor should be contacted first if support is 471 needed. 473 How Used by Call Taker: To decide which entity to contact first if 474 assistance is needed. 476 4.9. addDataProviderInfo XML Schema 477 478 486 489 490 491 492 493 495 496 497 498 500 502 504 506 508 510 512 513 514 515 517 Figure 1: addDataProviderInfo XML Schema 519 5. Service Information 521 This block describes the service that the service provider provides 522 to the caller. It SHOULD be included by all SPs in the path of the 523 call. The mime type is "addCallSvcInfo+xml". 525 5.1. Service Environment 527 Data Element: Service Environment 529 Use: Required 531 XML Element: 533 Description: This element defines whether a call is from a business 534 or residence caller. Currently, the only valid entries are 535 'Business' or 'Residence'. 537 Reason for Need: To assist in determining equipment and manpower 538 requirements. 540 How Used by Call Taker: Information may be used to assist in 541 determining equipment and manpower requirements for emergency 542 responders. As the information is not always available, and the 543 registry is not all encompassing, this is at best advisory 544 information, but since it mimics a similar capability in some 545 current emergency calling systems, it is known to be valuable. 546 The service provider uses it's best information (such as a rate 547 plan, facilities used to deliver service or service description) 548 to determine the information and is not responsible for 549 determining the actual characteristics of the location where the 550 call originates from. 552 5.2. Service Delivered by Provider to End User 554 Data Element: Service Delivered by Provider to End User 556 Use: Required 557 XML Element: 559 Description: This defines the type of service the end user has 560 subscribed to. The implied mobility of this service can not be 561 relied upon. A registry will reflect the following initial valid 562 entries: 564 * Wireless Telephone Service: Includes Satellite, CDMA, GSM, 565 Wi-Fi, WiMAX, LTE (Long Term Evolution) 567 * Fixed Public Pay/Coin telephones: Any coin or credit card 568 operated device. 570 * One way outbound service 572 * Inmate call/service 574 * Soft dialtone/quick service/warm disconnect/suspended 576 * Multi-line telephone system (MLTS): Includes all PBX, Centrex, 577 key systems, Shared Tenant Service. 579 * Sensor, unattended: Includes devices that generate DATA ONLY. 580 This is one-way information exchange and there will be no other 581 form of communication. 583 * Sensor, attended: Includes devices that are supported by a 584 monitoring service provider or automatically open a two-way 585 communication path. 587 * Wireline: Plain Old Telephone Service (POTS). 589 * VoIP Telephone Service: A type of service that offers 590 communication over internet protocol, such as Fixed, Nomadic, 591 Mobile, Unknown 593 * Relay Service: a type of service where there is a human 3rd 594 party agent who provides some kind of additional assistance to 595 the caller. Includes sign language relay and telematics 596 services which provide a service assistant on the call. 598 * Remote (off premise extension) 600 There can be more than one value returned. For example, a VoIP 601 prison telephone service is a reasonable combination. 603 Reason for Need: Knowing the type of service may assist the PSAP 604 with the handling of the call. 606 How Used by Call Taker: Call takers often use this information to 607 determine what kinds of questions to ask callers, and how much to 608 rely on supportive information. An emergency call from a prison 609 is treated differently that a call from a sensor device. As the 610 information is not always available, and the registry is not all 611 encompassing, this is at best advisory information, but since it 612 mimics a similar capability in some current emergency calling 613 systems, it is known to be valuable. 615 5.3. Service Mobility Environment 617 Data Element: Service Mobility Environment 619 Use: Required 621 XML Element: 623 Description: This provides the service providers view of the 624 mobility of the caller. As the service provider may not know the 625 characteristics of the actual access network used, the value not 626 be relied upon. A registry will reflect the following initial 627 valid entries: 629 * Mobile: the device should be able to move at any time 631 * Fixed: the device is not expected to move unless the service is 632 relocated 634 * Nomadic: the device is not expected to move while on a call, 635 but may move between calls 637 Reason for Need: Knowing the service provider's belief of mobility 638 may assist the PSAP with the handling of the call. 640 How Used by Call Taker: To determine whether to assume the location 641 of the caller might change. 643 5.4. addCallSvcInfo XML Schema 645 646 653 656 657 658 659 661 663 665 667 668 669 670 672 Figure 2: addCallSvcInfo XML Schema 674 6. Device Information 676 This block provides information about the device used to place the 677 call. It should be provided by any service provider that knows what 678 device is being used, and by the device itself. The mime type is 679 "addDataDevInfo+xml". 681 6.1. Device Classification 683 Data Element: Device Classification 685 Use: Optional 687 XML Element: 689 Description: This data element defines the kind of device making the 690 emergency call. If the device provides the data structure, the 691 device information should be provided. If the service provider 692 provides the structure and it knows what the device is, the 693 service provider should provide the device information. Often the 694 carrier does not know what the device is. It is possible to 695 receive 2 Additional Data Associated with a Caller data 696 structures, one created by the device and one created by the 697 service provider. This Information describes the about the 698 device, not how it is being used. This data element defines the 699 kind of device making the emergency call. A registry will reflect 700 the following valid entries: 702 * Cordless handset 704 * Fixed phone 706 * Mobile handset 708 * ATA - analog terminal adapter 710 * Satellite phone 712 * Stationary computing device (alarm system, data sensor) 714 * Guardian devices 716 * Desktop PC 717 * Laptop computing device 719 * Tablet computing device 721 * Alarm system 723 * Data sensor 725 * Personal beacons (spot) 727 * Auto telematics (indicates VEDS data set) 729 * Trucking telematics 731 * Farm equipment telematics 733 * Marine telematics 735 * PDA (personal digital assistant) 737 * PND (personal navigation device) 739 * Smart phone 741 * Internet tablet 743 * Gaming console 745 * Video phone 747 * Other text device 749 * Not Available 751 Reason for Need: The device classification describes the capability 752 of the calling device and assists in identifying the meaning of 753 the emergency call location information that is being presented. 754 For example, does the device require human intervention to 755 initiate a call or is this call the result of programmed 756 instructions?. Does the calling device have the ability to update 757 location or condition changes? Is this device interactive or a 758 one-way reporting device? 760 How Used by Call Taker: May assist with location of caller. For 761 example, a cordless handset may be outside or next door. May 762 provide calltaker some context about the caller, the capabilities 763 of the device used for the call or the environment the device is 764 being used in. 766 6.2. Device Manufacturer 768 Data Element: Device Manufacturer 770 Use: Optional 772 XML Element: 774 Description: The plain language name of the manufacturer of the 775 device. 777 Reason for Need: Used by PSAP management for post-mortem 778 investigation/resolution. 780 How Used by Call Taker: Probably not used by calltaker, but by PSAP 781 management. 783 6.3. Device Model Number 785 Data Element: Device Model Number 787 Use: Optional 789 XML Element: 791 Description: Model number of the device. 793 Reason for Need: Used by PSAP management for after action 794 investigation/resolution. 796 How Used by Call Taker: Probably not used by calltaker, but by PSAP 797 management. 799 6.4. Unique Device Identifier 801 Data Element: Unique Device Identifier 803 Use: Optional 805 XML Element: 807 Description: String that identify the specific device making the 808 call or creating an event. 810 Reason for Need: Uniquely identifies the device as opposed to any 811 signaling identifiers encountered in the call signaling stream. 813 How Used by Call Taker: Probably not used by calltaker they would 814 need to refer to management for investigation. 816 6.5. Type of Device Identifier 818 Data Element: Type of Device Identifier 820 Use: Conditional: must be provided if DeviceID is provided 822 XML Element: 824 Description: Identifies the type of device identifier being 825 generated in the unique device identifier data element. A 826 registry will reflect the following valid entries: 828 * MEID (CDMA) 830 * ESN (Electronic Serial Number - superseded by MEID) 832 * MAC (Media Access Control) Address - any IEEE device with an 833 Ethernet, Wi-Fi connection 835 * WiMAX has a device certificate 837 * IMEI (International Mobile Equipment Identifier - GSM) 839 * Unique Device Identifier (Unique identifier for medical 840 devices) 842 * RFID (Radio Frequency Identification) 844 * Sensors (types to be identified in a future document version) 846 * Manufacturer Serial Number 848 * Other 850 Reason for Need: Identifies how to interpret the Unique Device 851 Identifier. 853 How Used by Call Taker: Additional information that may be used to 854 assist with call handling. 856 6.6. Device/Service Specific Additional Data Structure 858 Data Element: Device/service specific additional data structure 860 Use: Optional 862 XML Element: 864 Description: A URI representing additional data whose schema is 865 specific to the device or service which created it. An example is 866 the VEDs structure for a vehicle telematics device. The URI, when 867 dereferenced, MUST yield a data structure defined by the Device/ 868 service specific additional data type value. Different data may 869 be created by each classification; i.e., telematics creates VEDS 870 data set - can be different types of data depending on device. 872 Reason for Need: Provides device/service specific data that may be 873 used by the call taker and/or responders. 875 How Used by Call Taker: Provide information to guide call takers to 876 select appropriate responders, give appropriate pre-arrival 877 instructions to callers, and advise responders of what to be 878 prepared for. May be used by responders to guide assistance 879 provided. 881 6.7. Device/Service Specific Additional Data Structure Type 883 Data Element: Type of Device/service specific additional data 884 structure 886 Use: Conditional. MUST be provided when Device/service specific 887 additional URI is provided 889 XML Element: 891 Description: Value from a registry defined by this document to 892 describe the type of data that can be retrieved from the Device/ 893 service specific additional data structure. Initial values are: 895 * IEEE 1512 - USDOT Model for traffic incidents 897 * VEDS 899 Reason for Need: This data element will allow for identification of 900 externally defined schemas, which may have additional data that 901 will assist in emergency response. 903 How Used by Call Taker: This data element will allow the end user 904 (calltaker or first responder) to know what type of additional 905 data may be available to aid in providing the needed emergency 906 services. 908 Note: Information which is specific to a location or a caller 909 (person) should not be placed in this section. 911 6.8. addDataDevInfo XML Schema 912 913 920 923 924 925 926 928 930 932 934 936 938 940 942 943 944 945 947 Figure 3: addDataDevInfo XML Schema 949 7. Owner/Subscriber Information 951 This block describes the owner of the device (if provided by the 952 device) or the subscriber information, if provided by a service 953 provider. The contact location is not necessarily the location of 954 the caller or incident, but is rather the nominal contact address. 955 The mime type is "addCallSub+xml". 957 7.1. vCARD for Subscriber's Data 959 Data Element: xCARD for Subscriber's Data 961 Use: Conditional: Some services (e.g. prepaid phones, initialized 962 phones, etc.) may not have this information. 964 XML Element: 966 Description: Information known by the service provider or device 967 about the subscriber; i.e., Name, Address, Individual Telephone 968 Number, Main Telephone Number and any other data. N, ORG (if 969 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 970 than one TEL property is provided, a parameter from the vCard 971 Property Value registry MUST be specified on each TEL. 973 Reason for Need: When the caller is unable to provide information, 974 this data may be used to obtain it 976 How Used by Call Taker: Obtaining critical information about the 977 caller and possibly the location when it is not able to be 978 obtained otherwise. 980 7.2. addCallSub XML Schema 981 982 990 993 994 995 996 998 1000 1001 1002 1003 1005 Figure 4: addCallSub XML Schema 1007 8. Example 1009 INVITE sips:bob@biloxi.example.com SIP/2.0 1010 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1011 Max-Forwards: 70 1012 To: Bob 1013 From: Alice ;tag=9fxced76sl 1014 Call-ID: 3848276298220188511@atlanta.example.com 1015 Call-Info: ;purpose=icon, 1016 ;purpose=info, 1017 ;purpose=emergencyCallData 1018 Geolocation: 1019 Geolocation-Routing: no 1020 Accept: application/sdp, application/pidf+xml, 1021 application/addDataProviderinfo+xml 1022 CSeq: 31862 INVITE 1023 Contact: 1024 Content-Type: multipart/mixed; boundary=boundary1 1026 Content-Length: ... 1028 --boundary1 1030 Content-Type: application/sdp 1032 ...SDP goes here 1034 --boundary1 1036 Content-Type: application/pidf+xml 1037 Content-ID: 1039 ...PIDF-LO goes here 1041 --boundary1-- 1043 Content-Type: application/addDataProviderinfo+xml 1044 Content-ID: <1234567890@atlanta.example.com> 1046 ...Additional Data goes here 1048 --boundary1-- 1050 Example: Attaching Additional Data via CID to a SIP INVITE 1052 9. Main Telephone Number 1054 In a vCard, used extensively in this document, there is no way to 1055 specify a "Main" telephone number. These numbers are useful to 1056 emergency responders who are called to a large enterprise. This 1057 document adds a new Property Value to the "tel" property of the TYPE 1058 parameter called "main". It can be used in any vCard in additional 1059 data. 1061 10. Security Considerations 1063 The information in this data structure will usually be considered 1064 private. HTTPS is specified to require the provider of the 1065 information to validate the credentials of the requester. While the 1066 creation of a PKI that has global scope may be difficult, the 1067 alternatives to creating devices and services that can provide 1068 critical information securely are more daunting. 1070 The Call-info header with purpose='emergencyCallData' MUST only be 1071 sent on an emergency call, which can be ascertained by the presence 1072 of an emergency service urn in a Route header of a SIP message. 1074 1076 1078 1081 11. Privacy Considerations 1083 [Editor's Note: The privacy considerations outlined in 1084 [I-D.iab-privacy-considerations] need to be addressed here in a 1085 future version of this document. 1087 There is much private data in this information. Local regulations 1088 may govern what data must be provided in emergency calls, but in 1089 general, the emergency call system is often aided by the kinds of 1090 information described in this document. There is a tradeoff between 1091 the privacy considerations and the utility of the data. Certainly, 1092 if the data cannot be protected, due to failure of the TLS mechanisms 1093 described here, data not required by regulation SHOULD not be sent. 1095 12. IANA Considerations 1097 12.1. Registry creation 1099 12.1.1. Additional Call Data Blocks Registry 1101 This document creates a new registry called 'Additional Call Data 1102 Blocks'. As defined in [RFC5226], this registry operates under 1103 "Expert Review" and "Specification Required" rules. 1105 The content of this registry includes: 1107 Name: Element Name of enclosing block. 1109 Reference: The document that describes the block 1111 The values defined are: 1113 +---------------------+-----------+ 1114 | Name | Reference | 1115 +---------------------+-----------+ 1116 | addDataProviderInfo | RFCXXXX | 1117 | addCallSvcInfo | RFCXXXX | 1118 | addCallSvcInfo | RFCXXXX | 1119 | addCallSub | RFCXXXX | 1120 +---------------------+-----------+ 1121 RFC Editor Note: 1122 replace XXXX in the table above with this documents RFC number 1124 12.1.2. Additional Call Data Service Delivered Registry 1126 This document creates a new registry called 'Additional Call Data 1127 Service Delivered'. As defined in [RFC5226], this registry operates 1128 under "Expert Review" rules. 1130 The content of this registry includes: 1132 Name: enumeration token of the service. 1134 Description: Short description identifying the service. 1136 The values defined are: 1138 +--------+----------------------------------------+ 1139 | Name | description | 1140 +--------+-------+--------------------------------+ 1141 | Wrless | Wireless Telephone Service: Includes | 1142 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 1143 | | LTE (Long Term Evolution) | 1144 | Coin | Fixed Public Pay/Coin telephones: Any | 1145 | | coin or credit card operated device | 1146 | 1way | One way outbound service | 1147 | Prison | Inmate call/service | 1148 | Temp | Soft dialtone/quick service/warm | 1149 | | disconnect/suspended | 1150 | MLTS | Multi-line telephone system: Includes | 1151 | | all PBX, Centrex, key systems, | 1152 | | Shared Tenant Service | 1153 | SenseU | Sensor, unattended: Includes devices | 1154 | | that generate DATA ONLY. This is | 1155 | | one-way information exchange and | 1156 | | there will be no other form of | 1157 | | communication | 1158 | SenseA | Sensor, attended: Includes devices | 1159 | | that are supported by a monitoring | 1160 | | service provider or automatically | 1161 | | open a two-way communication path | 1162 | POTS | Wireline: Plain Old Telephone Service | 1163 | VOIP | VoIP Telephone Service: A type of | 1164 | | service that offers communication | 1165 | | over internet protocol, such as Fixed| 1166 | | Nomadic, Mobile, ... | 1167 +--------+-------+--------------------------------+ 1169 12.1.3. Additional Call Data Device Classification Registry 1171 This document creates a new registry called 'Additional Call Data 1172 Device Classification'. As defined in [RFC5226], this registry 1173 operates under "Expert Review" rules. 1175 The content of this registry includes: 1177 Name: enumeration token of the device classification. 1179 Description: Short description identifying the device type. 1181 The values defined are: 1183 +--------+----------------------------------------+ 1184 | Name | description | 1185 +--------+-------+--------------------------------+ 1186 |Cordless| Cordless handset | 1187 | Fixed | Fixed phone | 1188 | Mobile | Mobile handset | 1189 | ATA | analog terminal adapter | 1190 |Satphone| Satellite phone | 1191 | FSense | Stationary computing device (alarm | 1192 | | system, data sensor) | 1193 | Guard | Guardian devices | 1194 | Desktop| Desktop PC | 1195 | Laptop | Laptop computing device | 1196 | Tablet | Tablet computing device | 1197 | Alarm | Alarm system | 1198 | MSense | Mobile Data sensor | 1199 | Beacon | Personal beacons (spot) | 1200 | Auto | Auto telematics | 1201 | Truck | Truck telematics | 1202 | Farm | Farm equipment telematics | 1203 | Marine | Marine telematics | 1204 | PDA | Personal digital assistant | 1205 | PND | Personal navigation device) | 1206 | SmrtPhn| Smart phone | 1207 | Itab | Internet tablet | 1208 | Game | Gaming console | 1209 | Video | Video phone | 1210 | Text | Other text device | 1211 | NA | Not Available | 1212 +--------+----------------------------------------+ 1214 12.1.4. Additional Call Data Device ID Type Registry 1216 This document creates a new registry called 'Additional Call Data 1217 Device ID Type'. As defined in [RFC5226], this registry operates 1218 under "Expert Review" rules. 1220 The content of this registry includes: 1222 Name: enumeration token of the device id type. 1224 Description: Short description identifying the type of device id. 1226 The values defined are: 1228 +--------+----------------------------------------+ 1229 | Name | description | 1230 +--------+-------+--------------------------------+ 1231 | MEID | Mobile Equipment Identifier (CDMA) | 1232 | ESN | Electronic Serial Number(GSM) | 1233 | MAC | Media Access Control Address (IEEE) | 1234 | WiMAX | device certificate unique id | 1235 | IMEI | International Mobile Equipment ID (GSM)| 1236 | UDI | Unique Device Identifier (medical) | 1237 | RFID | Radio Frequency Identification | 1238 | Sense | Sensors (types to be identified ) | 1239 | SN | Manufacturer Serial Number | 1240 | Other | Other | 1241 +--------+----------------------------------------+ 1243 12.2. 'emergencyCallData' Purpose Parameter Value 1245 This document defines the 'emergencyCallData' value for the "purpose" 1246 parameter of the Call-Info header field. The Call-Info header and 1247 the corresponding registry for the 'purpose' parameter was 1248 established with RFC 3261 [RFC3261]. 1250 Header Parameter New 1251 Field Name Value Reference 1252 ---------- --------- ----------------- --------- 1253 Call-Info purpose emergencyCallData [This RFC] 1255 12.3. URN Sub-Namespace Registration for provided-by Registry Entry 1257 This section registers the namespace specified in ??? in the 1258 provided-by registry established by RFC 4119. 1260 12.4. MIME Registrations 1262 12.4.1. MIME Content-type Registration for 'application/ 1263 addDataProviderInfo+xml' 1265 This specification requests the registration of a new MIME type 1266 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1267 RFC 3023 [RFC3023]. 1269 MIME media type name: application 1271 MIME subtype name: addDataProviderInfo+xml 1273 Mandatory parameters: none 1274 Optional parameters: charset 1276 Indicates the character encoding of enclosed XML. 1278 Encoding considerations: 1280 Uses XML, which can employ 8-bit characters, depending on the 1281 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1283 Security considerations: 1285 This content type is designed to carry the data provider 1286 information, which is a sub-category of additional data about an 1287 emergency call. 1289 Since this data contains personal information appropriate 1290 precautions have to be taken to limit unauthorized access, 1291 inappropriate disclosure to third parties, and eavesdropping of 1292 this information. Please refer to Section 10 and Section 11 for 1293 more information. 1295 Interoperability considerations: None 1297 Published specification: [TBD: This specification] 1299 Applications which use this media type: Emergency Services 1301 Additional information: 1303 Magic Number: None 1305 File Extension: .xml 1307 Macintosh file type code: 'TEXT' 1309 Personal and email address for further information: Hannes 1310 Tschofenig, Hannes.Tschofenig@gmx.net 1312 Intended usage: LIMITED USE 1314 Author: This specification is a work item of the IETF ECRIT 1315 working group, with mailing list address . 1317 Change controller: The IESG 1319 12.4.2. MIME Content-type Registration for 'application/ 1320 addCallSvcInfo+xml' 1322 This specification requests the registration of a new MIME type 1323 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1324 RFC 3023 [RFC3023]. 1326 MIME media type name: application 1328 MIME subtype name: addCallSvcInfo+xml 1330 Mandatory parameters: none 1332 Optional parameters: charset 1334 Indicates the character encoding of enclosed XML. 1336 Encoding considerations: 1338 Uses XML, which can employ 8-bit characters, depending on the 1339 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1341 Security considerations: 1343 This content type is designed to carry the service information, 1344 which is a sub-category of additional data about an emergency 1345 call. 1347 Since this data contains personal information appropriate 1348 precautions have to be taken to limit unauthorized access, 1349 inappropriate disclosure to third parties, and eavesdropping of 1350 this information. Please refer to Section 10 and Section 11 for 1351 more information. 1353 Interoperability considerations: None 1355 Published specification: [TBD: This specification] 1357 Applications which use this media type: Emergency Services 1359 Additional information: 1361 Magic Number: None 1363 File Extension: .xml 1365 Macintosh file type code: 'TEXT' 1366 Personal and email address for further information: Hannes 1367 Tschofenig, Hannes.Tschofenig@gmx.net 1369 Intended usage: LIMITED USE 1371 Author: This specification is a work item of the IETF ECRIT 1372 working group, with mailing list address . 1374 Change controller: The IESG 1376 12.4.3. MIME Content-type Registration for 'application/ 1377 addDataDevInfo+xml' 1379 This specification requests the registration of a new MIME type 1380 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1381 RFC 3023 [RFC3023]. 1383 MIME media type name: application 1385 MIME subtype name: addDataDevInfo+xml 1387 Mandatory parameters: none 1389 Optional parameters: charset 1391 Indicates the character encoding of enclosed XML. 1393 Encoding considerations: 1395 Uses XML, which can employ 8-bit characters, depending on the 1396 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1398 Security considerations: 1400 This content type is designed to carry the device information 1401 information, which is a sub-category of additional data about an 1402 emergency call. 1404 Since this data contains personal information appropriate 1405 precautions have to be taken to limit unauthorized access, 1406 inappropriate disclosure to third parties, and eavesdropping of 1407 this information. Please refer to Section 10 and Section 11 for 1408 more information. 1410 Interoperability considerations: None 1412 Published specification: [TBD: This specification] 1413 Applications which use this media type: Emergency Services 1415 Additional information: 1417 Magic Number: None 1419 File Extension: .xml 1421 Macintosh file type code: 'TEXT' 1423 Personal and email address for further information: Hannes 1424 Tschofenig, Hannes.Tschofenig@gmx.net 1426 Intended usage: LIMITED USE 1428 Author: This specification is a work item of the IETF ECRIT 1429 working group, with mailing list address . 1431 Change controller: The IESG 1433 12.4.4. MIME Content-type Registration for 'application/addCallSub+xml' 1435 This specification requests the registration of a new MIME type 1436 according to the procedures of RFC 4288 [RFC4288] and guidelines in 1437 RFC 3023 [RFC3023]. 1439 MIME media type name: application 1441 MIME subtype name: addCallSub+xml 1443 Mandatory parameters: none 1445 Optional parameters: charset 1447 Indicates the character encoding of enclosed XML. 1449 Encoding considerations: 1451 Uses XML, which can employ 8-bit characters, depending on the 1452 character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. 1454 Security considerations: 1456 This content type is designed to carry owner/subscriber 1457 information, which is a sub-category of additional data about an 1458 emergency call. 1460 Since this data contains personal information appropriate 1461 precautions have to be taken to limit unauthorized access, 1462 inappropriate disclosure to third parties, and eavesdropping of 1463 this information. Please refer to Section 10 and Section 11 for 1464 more information. 1466 Interoperability considerations: None 1468 Published specification: [TBD: This specification] 1470 Applications which use this media type: Emergency Services 1472 Additional information: 1474 Magic Number: None 1476 File Extension: .xml 1478 Macintosh file type code: 'TEXT' 1480 Personal and email address for further information: Hannes 1481 Tschofenig, Hannes.Tschofenig@gmx.net 1483 Intended usage: LIMITED USE 1485 Author: This specification is a work item of the IETF ECRIT 1486 working group, with mailing list address . 1488 Change controller: The IESG 1490 12.5. URN Sub-Namespace Registration 1492 12.5.1. Registration for urn:ietf:params:xml:ns:addDataProviderInfo 1494 This section registers a new XML namespace, as per the guidelines in 1495 RFC 3688 [RFC3688]. 1497 URI: urn:ietf:params:xml:ns:addDataProviderInfo 1499 Registrant Contact: IETF, ECRIT working group, , as 1500 delegated by the IESG . 1502 XML: 1504 BEGIN 1505 1506 1508 1509 1510 1512 Namespace for Additional Emergency Call Data: 1513 Data Provider Information 1514 1515 1516

Namespace for Additional Data related to an Emergency Call

1517

Data Provider Information

1518

See [TBD: This document].

1519 1520 1521 END 1523 12.5.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo 1525 This section registers a new XML namespace, as per the guidelines in 1526 RFC 3688 [RFC3688]. 1528 URI: urn:ietf:params:xml:ns:addCallSvcInfo 1530 Registrant Contact: IETF, ECRIT working group, , as 1531 delegated by the IESG . 1533 XML: 1535 BEGIN 1536 1537 1539 1540 1541 1543 Namespace for Additional Emergency Call Data: 1544 Service Information 1545 1546 1547

Namespace for Additional Data related to an Emergency Call

1548

Service Information

1549

See [TBD: This document].

1550 1551 1552 END 1554 12.5.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo 1556 This section registers a new XML namespace, as per the guidelines in 1557 RFC 3688 [RFC3688]. 1559 URI: urn:ietf:params:xml:ns:addDataDevInfo 1561 Registrant Contact: IETF, ECRIT working group, , as 1562 delegated by the IESG . 1564 XML: 1566 BEGIN 1567 1568 1570 1571 1572 1574 Namespace for Additional Emergency Call Data: 1575 Device Information 1576 1577 1578

Namespace for Additional Data related to an Emergency Call

1579

Device Information

1580

See [TBD: This document].

1581 1582 1583 END 1585 12.5.4. Registration for urn:ietf:params:xml:ns:addCallSub 1587 This section registers a new XML namespace, as per the guidelines in 1588 RFC 3688 [RFC3688]. 1590 URI: urn:ietf:params:xml:ns:addCallSub 1592 Registrant Contact: IETF, ECRIT working group, , as 1593 delegated by the IESG . 1595 XML: 1597 BEGIN 1598 1599 1601 1602 1603 1605 Namespace for Additional Emergency Call Data: 1606 Owner/Subscriber Information 1607 1608 1609

Namespace for Additional Data related to an Emergency Call

1610

Owner/Subscriber Information

1611

See [TBD: This document].

1612 1613 1614 END 1616 12.6. Schema Registrations 1618 This specification registers four schemas, as per the guidelines in 1619 RFC 3688 [RFC3688]. 1621 URI: 1622 urn:ietf:params:xml:schema:additional-data:addDataProviderInfo 1624 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1625 delegated by the IESG (iesg@ietf.org). 1627 XML: The XML schema can be found in Figure 1. 1629 URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo 1631 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 1632 delegated by the IESG (iesg@ietf.org). 1634 XML: The XML schema can be found in Figure 2. 1636 URI: urn:ietf:params:xml:schema:additional-data:addDataDevInfo 1638 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1639 delegated by the IESG (iesg@ietf.org). 1641 XML: The XML schema can be found in Figure 3. 1643 URI: urn:ietf:params:xml:schema:additional-data:addCallSub 1645 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 1646 delegated by the IESG (iesg@ietf.org). 1648 XML: The XML schema can be found in Figure 4. 1650 12.7. VCard Parameter Value Registration 1652 This document registers a new value in the vCARD Parameter Values 1653 registry as defined by [RFC6350] with the following template: 1655 Value: main 1657 Purpose: The main telephone number, typically of an enterprise, as 1658 opposed to a direct dial number of an individual employee 1660 Conformance: This value can be used with the "TYPE" parameter 1661 applied on the "TEL" property. 1663 Example(s): 1664 TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-9000 1666 13. Acknowledgments 1668 This work was originally started in NENA and has benefitted from a 1669 large number of participants in NENA standardization efforts, 1670 originally in the Long Term Definition Working Group, the Data 1671 Technical Committee and most recently the Additional Data working 1672 group. The authors are grateful for the initial work and extended 1673 comments provided by the many NENA participants. 1675 14. References 1677 14.1. Normative References 1679 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1680 Requirement Levels", BCP 14, RFC 2119, March 1997. 1682 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 1683 Locators", RFC 2392, August 1998. 1685 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 1686 Types", RFC 3023, January 2001. 1688 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 1689 A., Peterson, J., Sparks, R., Handley, M., and E. 1690 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 1691 June 2002. 1693 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1694 January 2004. 1696 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 1697 Format", RFC 4119, December 2005. 1699 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 1700 Registration Procedures", BCP 13, RFC 4288, December 2005. 1702 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1703 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1704 May 2008. 1706 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 1707 August 2011. 1709 [RFC6351] Perreault, S., "xCard: vCard XML Representation", 1710 RFC 6351, August 2011. 1712 14.2. Informational References 1714 [I-D.iab-privacy-considerations] 1715 Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 1716 Morris, J., Hansen, M., and R. Smith, "Privacy 1717 Considerations for Internet Protocols", 1718 draft-iab-privacy-considerations-03 (work in progress), 1719 July 2012. 1721 [I-D.ietf-ecrit-phonebcp] 1722 Rosen, B. and J. Polk, "Best Current Practice for 1723 Communications Services in support of Emergency Calling", 1724 draft-ietf-ecrit-phonebcp-20 (work in progress), 1725 September 2011. 1727 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 1728 "Framework for Emergency Calling Using Internet 1729 Multimedia", RFC 6443, December 2011. 1731 Authors' Addresses 1733 Brian Rosen 1734 NeuStar 1735 470 Conrad Dr. 1736 Mars, PA 16046 1737 US 1739 Phone: +1 724 382 1051 1740 Email: br@brianrosen.net 1742 Hannes Tschofenig 1743 Nokia Siemens Networks 1744 Linnoitustie 6 1745 Espoo 02600 1746 Finland 1748 Phone: +358 (50) 4871445 1749 Email: Hannes.Tschofenig@gmx.net 1750 URI: http://www.tschofenig.priv.at 1752 Roger Marshall 1753 TeleCommunication Systems, Inc. 1754 2401 Elliott Avenue 1755 Seattle, WA 98121 1756 US 1758 Phone: +1 206 792 2424 1759 Email: rmarshall@telecomsys.com 1760 URI: http://www.telecomsys.com