idnits 2.17.00 (12 Aug 2021) /tmp/idnits21691/draft-ietf-ecrit-additional-data-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 27 instances of too long lines in the document, the longest one being 16 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1813 has weird spacing: '...element name=...' == Line 2282 has weird spacing: '...ll-Info pur...' == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (October 16, 2013) is 3138 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 2282, but not defined == Unused Reference: 'RFC5985' is defined on line 2866, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) ** Downref: Normative reference to an Informational RFC: RFC 3325 ** Obsolete normative reference: RFC 4288 (Obsoleted by RFC 6838) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: draft-ietf-geopriv-relative-location has been published as RFC 7035 Summary: 5 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: April 19, 2014 Nokia Solutions and Networks 6 R. Marshall 7 TeleCommunication Systems, Inc. 8 R. Gellens 9 Qualcomm Technologies, Inc. 10 J. Winterbottom 12 October 16, 2013 14 Additional Data related to an Emergency Call 15 draft-ietf-ecrit-additional-data-12.txt 17 Abstract 19 When an emergency call is sent to a Public Safety Answering Point 20 (PSAP), the device that sends it, as well as any application service 21 provider in the path of the call, or access network provider through 22 which the call originated may have information about the call, the 23 caller or the location which the PSAP may be able to use. This 24 document describes data structures and a mechanism to convey such 25 data to the PSAP. The mechanism uses a Uniform Resource Identifier 26 (URI), which may point to either an external resource or an object in 27 the body of the SIP message. The mechanism thus allows the data to 28 be passed by reference (when the URI points to an external resource) 29 or by value (when it points into the body of the message). This 30 follows the tradition of prior emergency services standardization 31 work where data can be conveyed by value within the call signaling 32 (i.e., in body of the SIP message) and also by reference. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on April 19, 2014. 50 Copyright Notice 52 Copyright (c) 2013 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6 70 3.1. Data Provider Information . . . . . . . . . . . . . . . . 7 71 3.1.1. Data Provider String . . . . . . . . . . . . . . . . 7 72 3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8 73 3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8 74 3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9 75 3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 9 76 3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10 77 3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 10 78 3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 11 79 3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 11 80 3.1.10. emergencyCall.ProviderInfo Example . . . . . . . . . 12 81 3.2. Service Information . . . . . . . . . . . . . . . . . . . 14 82 3.2.1. Service Environment . . . . . . . . . . . . . . . . . 14 83 3.2.2. Service Delivered by Provider to End User . . . . . . 15 84 3.2.3. Service Mobility Environment . . . . . . . . . . . . 16 85 3.2.4. emergencyCall.SvcInfo Example . . . . . . . . . . . . 17 86 3.3. Device Information . . . . . . . . . . . . . . . . . . . 17 87 3.3.1. Device Classification . . . . . . . . . . . . . . . . 17 88 3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 19 89 3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 19 90 3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 19 91 3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 20 92 3.3.6. Device/Service Specific Additional Data Structure . . 20 93 3.3.7. Device/Service Specific Additional Data Structure 94 Type . . . . . . . . . . . . . . . . . . . . . . . . 21 95 3.3.8. Choosing between defining a new type of block or new 96 type of device/service specific additional data . . . 22 97 3.3.9. emergencyCall.DevInfo Example . . . . . . . . . . . . 22 98 3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 23 99 3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 23 100 3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 24 101 3.4.3. emergencyCall.SubInfo Example . . . . . . . . . . . . 24 102 3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 26 103 3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 26 104 3.5.2. emergencyCall.Comment Example . . . . . . . . . . . . 27 105 4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 27 106 4.1. Transmitting Blocks using the Call-Info Header . . . . . 29 107 4.2. Transmitting Blocks by Reference using the Provided-By 108 Element . . . . . . . . . . . . . . . . . . . . . . . . . 30 109 4.3. Transmitting Blocks by Value using the Provided-By 110 Element . . . . . . . . . . . . . . . . . . . . . . . . . 30 111 4.4. The Content-Disposition Parameter . . . . . . . . . . . . 31 112 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 32 113 6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 35 114 6.1. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 36 115 6.2. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 37 116 6.3. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 38 117 6.4. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 39 118 6.5. emergencyCall.Comment XML Schema . . . . . . . . . . . . 39 119 6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 40 120 7. Security Considerations . . . . . . . . . . . . . . . . . . . 42 121 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 43 122 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 123 9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 45 124 9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 46 125 9.1.2. Service Provider Type Registry . . . . . . . . . . . 46 126 9.1.3. Service Delivered Registry . . . . . . . . . . . . . 46 127 9.1.4. Device Classification Registry . . . . . . . . . . . 47 128 9.1.5. Device ID Type Type Registry . . . . . . . . . . . . 47 129 9.1.6. Device/Service Data Type Registry . . . . . . . . . . 47 130 9.1.7. Additional Data Blocks Registry . . . . . . . . . . . 48 131 9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 49 132 9.3. URN Sub-Namespace Registration for provided-by Registry 133 Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 49 134 9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 49 135 9.4.1. MIME Content-type Registration for 136 'application/emergencyCall.ProviderInfo+xml' . . . . 49 137 9.4.2. MIME Content-type Registration for 138 'application/emergencyCall.SvcInfo+xml' . . . . . . . 50 139 9.4.3. MIME Content-type Registration for 140 'application/emergencyCall.DevInfo+xml' . . . . . . . 51 141 9.4.4. MIME Content-type Registration for 142 'application/emergencyCall.SubInfo+xml' . . . . . . . 52 143 9.4.5. MIME Content-type Registration for 144 'application/emergencyCall.Comment+xml' . . . . . . . 53 145 9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 54 146 9.5.1. Registration for 147 urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 54 148 9.5.2. Registration for 149 urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 55 150 9.5.3. Registration for 151 urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 56 152 9.5.4. Registration for 153 urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 56 154 9.5.5. Registration for 155 urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 57 156 9.5.6. Registration for 157 urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 58 158 9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 58 159 9.7. VCard Parameter Value Registration . . . . . . . . . . . 59 160 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 161 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 60 162 11.1. Normative References . . . . . . . . . . . . . . . . . . 60 163 11.2. Informational References . . . . . . . . . . . . . . . . 61 164 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 62 165 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 85 167 1. Introduction 169 When an IP-based emergency call is initiated a rich set of data from 170 multiple data sources is conveyed to the Public Safety Answering 171 Point (PSAP). This data includes information about the calling party 172 identity, the multimedia capabilities of the device, the emergency 173 service number, location information, and meta-data about the sources 174 of the data. The device, the access network provider, and any 175 service provider in the call path may have even more information 176 useful for a PSAP. This document extends the basic set of data 177 communicated with an IP-based emergency call, as described in 178 [RFC6443] and [RFC6881], in order to carry additional data which may 179 be useful to an entity or call taker handling the call. This data is 180 "additional" to the basic information found in the emergency call 181 signaling used. 183 In general, there are three categories of data communicated in an 184 emergency call: 186 Data Associated with a Location: Location data is conveyed in the 187 Presence Information Data Format Location Object (PIDF-LO) data 188 structure originally defined in RFC 4119 [RFC4119] and extended by 189 RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location 190 information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for 191 geodetic location information), and 193 [I-D.ietf-geopriv-relative-location] (for relative location). 194 There may be data that is specific to the location not available 195 in the location data structure itself, such as floor plans, tenant 196 and building owner contact data, heating, ventilation and air 197 conditioning (HVAC) status, etc. 199 Data Associated with a Call: While information is carried in the 200 call setup procedure itself (as part of the SIP headers as well as 201 in the body of the SIP message), there is additional data known by 202 the device making the call, and the service provider along the 203 path of the call. This information may include the service 204 provider contact information, subscriber identity and contact 205 information, the type of service the service provider and the 206 access network provider offer, what kind of device is being used, 207 etc. Some data is device or service dependent data. For example, 208 a car telematics system may have crash information. A medical 209 monitoring device may have sensor data. 211 Data Associated with a Caller: This is personal data about a caller, 212 such as medical information and emergency contact data. 214 This document only defines data structures relevant to data 215 associated with the call but defines extension points for other data 216 to be added via other specifications. 218 For interoperability, there needs to be a common way for the 219 information conveyed to a PSAP to be encoded and identified. 220 Identification allows emergency services authorities to know during 221 call processing which types of data are present and to determine if 222 they wish to access it. A common encoding allows the data to be 223 accessed. 225 This document defines the data structures and a way to communicate 226 the information in several ways. Although current standardization 227 efforts around IP-based emergency services are focused on the Session 228 Initiation Protocol (SIP) and HTTP the data structures in XML format 229 described in this document are usable for other communication systems 230 as well. In Section 3 the data structures are defined and the SIP/ 231 HTTP transport components are defined in Section 4 to offer a clear 232 separation between the two. 234 More technically, the data structure described in this document is 235 represented as one or more "blocks" of information. Each of the 236 blocks is an XML structure with an associated Multipurpose Internet 237 Mail Extensions (MIME) type for encapsulation, and an extensible set 238 of these types constitute the data set. A registry is defined to 239 list the block types that may be included. 241 2. Terminology 243 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 244 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 245 document are to be interpreted as described in RFC 2119 [RFC2119]. 247 This document also uses terminology from [RFC5012]. We use the term 248 service provider to refer to an Application Service Provider (ASP). 249 A Voice Service Provider (VSP) is a special type of ASP. With the 250 term "Access Network Provider" we refer to the Internet Access 251 Provider (IAP) and the Internet Service Provider (ISP) without 252 further distinguishing these two entities, since the difference 253 between the two is not relevant for this document. Note that the 254 roles of ASP and access network provider may be provided by a single 255 company. 257 In the data block definitions, see Section 3, the values for the 258 "Use:" label are specified as one of: 260 'Required': means they MUST be present in the data structure. 262 'Conditional': means they MUST be present if the specified 263 condition(s) is met. They MAY be present if the condition(s) is 264 not met. 266 'Optional': means they MAY be present. 268 vCard is a data format for representing and exchanging a variety of 269 information about individuals and other entities. For applications 270 that use XML the format defined in vCard is not immediately 271 applicable. For this purpose an XML-based encoding of the 272 information elements defined in the vCard specification has been 273 defined and the name of that specification is xCard. Since the term 274 vCard is more familiar to most readers we use the term xCard and 275 vCard interchangeable but it would be accurate to use the term vCard 276 only. 278 3. Data Structures 280 This section defines the following five data structures, each as a 281 data block. For each block we define the MIME type, and the XML data 282 structure. The five data structures are: 284 'Data Provider': This block supplies name and contact information 285 for the entity that created the data. Section 3.1 provides the 286 details. 288 'Service Information': This block supplies information about the 289 service. The description can be found in Section 3.2. 291 'Device Information': This block supplies information about the 292 device placing the call. Device information can be found in 293 Section 3.3. 295 'Owner/Subscriber': This block supplies information about the owner 296 of the device or about the subscriber. Details can be found in 297 Section 3.4. 299 'Comment': This block provides a way to supply free form human 300 readable text to the PSAP or emergency responders. This simple 301 structure is defined in Section 3.5. 303 Note that the xCard format is re-used in some of the data structures 304 to provide contact information. In an xCard there is no way to 305 specify a "main" telephone number. These numbers are useful to 306 emergency responders who are called to a large enterprise. This 307 document adds a new property value to the "tel" property of the TYPE 308 parameter called "main". It can be used in any xCard in additional 309 data. 311 3.1. Data Provider Information 313 This block is intended to be provided by any service provider in the 314 path of the call or the access network provider. It includes 315 identification and contact information. This block SHOULD be 316 provided by every service provider in the call path, and by the 317 access network provider. Devices MAY use this block to provide 318 identifying information. The MIME subtype is "application/ 319 emergencyCall.ProviderInfo+xml". An access network provider SHOULD 320 provide this block either by value or by reference in the Provided-By 321 section of a PIDF-LO 323 3.1.1. Data Provider String 325 Data Element: Data Provider String 327 Use: Required 329 XML Element: 331 Description: This is a plain language string suitable for displaying 332 the name of the service provider that created the additional data 333 structure. If the device created the structure the value is 334 identical to the contact header in the SIP INVITE. 336 Reason for Need: Inform the call taker of the identity of the entity 337 providing the additional call data structure. 339 How Used by Call Taker: Allows the call taker to interpret the data 340 in this structure. The source of the information often influences 341 how the information is used, believed or verified. 343 3.1.2. Data Provider ID 345 Data Element: Data Provider ID 347 Use: Conditional. This data SHOULD be provided if the service 348 provider or access provider is located in a jurisdiction that 349 maintains such ids. For example, in North America, this would be 350 a "NENA Company ID". 352 XML Element: 354 Description: A jurisdiction specific code for the access provider or 355 service provider shown in the element that 356 created the structure of the call. NOTE: In the US, the NENA 357 Company ID must appear here. Additional information can be found 358 at http://www.nena.org/nena-company-id. The NENA Company ID MUST 359 be in the form of a URI in the following format: 360 urn:nena:companyid: 362 Reason for Need: Inform the call taker of the identity of the entity 363 providing the additional call data structure. 365 How Used by Call Taker: Where jurisdictions have lists of providers 366 the Data Provider ID can be useful. 368 3.1.3. Data Provider ID Series 370 Data Element: Data Provider ID Series 372 Use: Conditional. If Data Provider ID is provided, Data Provider ID 373 Series is required. 375 XML Element: 377 Description: Identifies the issuer of the ProviderId. A registry 378 will reflect the following valid entries: 380 * NENA 382 * EENA 384 Reason for Need: Identifies how to interpret the Data Provider ID. 386 How Used by Call Taker: Determines which provider ID registry to 387 consult for more information 389 3.1.4. Type of Data Provider 391 Data Element: Type of Data Provider ID 393 Use: Conditional. If Data Provider ID is provided, Type of Data 394 Provider ID is required. 396 XML Element: 398 Description: Identifies the type of data provider id being supplied 399 in the ProviderId data element. A registry with an initial set of 400 values is shown in Figure 1. 402 +------------------------------+------------------------------------+ 403 | Token | Description | 404 +------------------------------+------------------------------------+ 405 |Access Network Provider | Access network service provider | 406 |Service Provider | Calling or Origination telecom SP | 407 |Service Provider Subcontractor| A contractor to another kind of SP | 408 |Telematics Provider | A sensor based SP, especially | 409 | | vehicle based | 410 |Language Translation Provider | A spoken language translation SP | 411 |Expert Advice Provider | An SP giving expert advice | 412 |Emergency Modality Translation| An emergency call specific | 413 | | modality translation service | 414 | | e.g. for sign language | 415 |Relay Provider | A interpretation SP, for example, | 416 | | video relay for sign language | 417 | | interpreting | 418 |Other | Any other type of service provider | 419 +------------------------------+------------------------------------+ 421 Figure 1: Type of Data Provider ID Registry. 423 Reason for Need: Identifies what kind of data provider this is. 425 How Used by Call Taker: To decide who to contact when further 426 information is needed 428 3.1.5. Data Provider Contact URI 430 Data Element: Data Provider Contact URI 431 Use: Required 433 XML Element: 435 Description: For a service provider or access provider the contact 436 SHOULD be a contact URI. This MUST be either a tel uri or a SIP 437 URI. If a telephone number is the contact address it SHOULD be 438 provided as a tel URI, if it is provided as a SIP URI then it MUST 439 be in the form of sip:telephonenumber@serviceprovider:user=phone. 440 If the call is from a device, this would reflect the contact 441 information of the owner of the device. When provided by a 442 service or access provider, this would be a URI to a 24/7 support 443 organization tasked to provide PSAP support for this emergency 444 call. 446 Reason for Need: Additional data providers may need to be contacted 447 for error or other unusual circumstances. 449 How Used by Call Taker: To contact the supplier of the additional 450 data for assistance in handling the call. 452 3.1.6. Data Provider Languages(s) Supported 454 Data Element: Data Provider Language(s) supported 456 Use: Conditional 458 XML Element: 460 Description: The language used by the entity at the Data Provider 461 Contact URI as an alpha 2-character code as defined in ISO 462 639-1:2002 Codes for the representation of names of languages -- 463 Part 1: Alpha-2 code Multiple instances of this element may occur. 464 Order is significant; preferred language should appear first. 465 This data is required if a Data Provider Contact URI is provided. 466 The content must reflect the languages supported at the contact 467 URI. 469 Reason for Need: Information needed to determine if emergency 470 service authority can communicate with the service provider or if 471 an interpreter will be needed. 473 How Used by Call Taker: If call taker cannot speak language(s) 474 supported by the service provider, a translation service will need 475 to be added to the conversation. 477 3.1.7. xCard of Data Provider 478 Data Element: xCard of Data Provider 480 Use: Optional 482 XML Element: 484 Description: There are many fields in the xCard and the creator of 485 the data structure is encouraged to provide as much information as 486 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 487 minimum. N should contain name of support group or device owner 488 as appropriate. If more than one TEL property is provided, a 489 parameter from the vCard Property Value registry MUST be specified 490 on each TEL. For encoding of the xCard this specification uses 491 the XML-based encoding specified in [RFC6351]. and is hereinafter 492 referred to as "xCard" 494 Reason for Need: Information needed to determine additional contact 495 information. 497 How Used by Call Taker: Assists call taker by providing additional 498 contact information that may not be included in the SIP invite or 499 the PIDF-LO. 501 3.1.8. Subcontractor Principal 503 Data Element: Subcontractor Principal 505 Use: Conditional 507 XML Element: 509 Description: If the data provider is a subcontractor to another 510 provider such as an access infrastructure provider or telematics 511 provider, this element contains the DataProviderString of the 512 service provider to indicate which provider the subcontractor is 513 working for. This data is required if the Data Provider type is 514 subcontractor. 516 Reason for Need: Identify the entity the subcontractor works for. 518 How Used by Call Taker: Allows the call taker to understand what the 519 relationship between data providers and the service providers in 520 the path of the call are. 522 3.1.9. Subcontractor Priority 524 Data Element: Subcontractor Priority 525 Use: Conditional 527 XML Element: 529 Description: If the subcontractor should be contacted first, this 530 element should have a "sub" value. If the access or origination 531 service provider should be contacted first, this element should 532 have a "main" value. This data is required if the Data Provider 533 type is "subcontractor". 535 Reason for Need: Inform the call taker whether the network operator 536 or the subcontractor should be contacted first if support is 537 needed. 539 How Used by Call Taker: To decide which entity to contact first if 540 assistance is needed. 542 3.1.10. emergencyCall.ProviderInfo Example 544 545 548 Example VoIP Provider 549 550 urn:nena:companyid:ID123 551 NENA 552 Service Provider 553 sip:voip-provider@example.com 554 EN 555 557 558 Hannes Tschofenig 559 560 Hannes 561 Tschofenig 562 563 564 Dipl. Ing. 565 566 --0203 567 568 20090808T1430-0500 569 570 M 571 572 1 573 574 de 575 576 577 2 578 579 en 580 581 582 work 583 584 Example VoIP Provider 585 586 587 588 work 589 593 594 595 596 Linnoitustie 6 597 Espoo 598 Uusimaa 599 02600 600 Finland 601 602 603 604 605 work 606 voice 607 608 609 tel:+358 50 4871445 610 611 612 work 613 614 hannes.tschofenig@nsn.com 615 616 617 work 618 619 geo:60.210796,24.812924 621 622 623 home 624 625 626 http://www.tschofenig.priv.at/key.asc 627 628 629 Finland/Helsinki 630 631 home 632 633 http://www.tschofenig.priv.at 634 635 636 637 639 Figure 2: emergencyCall.ProviderInfo Example. 641 3.2. Service Information 643 This block describes the service that the service provider provides 644 to the caller. It SHOULD be included by all SPs in the path of the 645 call. The mime subtype is "application/emergencyCall.SvcInfo+xml". 647 3.2.1. Service Environment 649 Data Element: Service Environment 651 Use: Required 653 XML Element: 655 Description: This element defines whether a call is from a business 656 or residence caller. Currently, the only valid entries are 657 'Business' or 'Residence'. 659 Reason for Need: To assist in determining equipment and manpower 660 requirements. 662 How Used by Call Taker: Information may be used to assist in 663 determining equipment and manpower requirements for emergency 664 responders. As the information is not always available, and the 665 registry is not all encompassing, this is at best advisory 666 information, but since it mimics a similar capability in some 667 current emergency calling systems, it is known to be valuable. 668 The service provider uses its best information (such as a rate 669 plan, facilities used to deliver service or service description) 670 to determine the information and is not responsible for 671 determining the actual characteristics of the location where the 672 call originates from. 674 3.2.2. Service Delivered by Provider to End User 676 Data Element: Service Delivered by Provider to End User 678 Use: Required 680 XML Element: 682 Description: This defines the type of service the end user has 683 subscribed to. The implied mobility of this service cannot be 684 relied upon. A registry with an initial set of values is defined 685 in Figure 3. 687 +--------+----------------------------------------+ 688 | Name | Description | 689 +--------+----------------------------------------+ 690 | Wrless | Wireless Telephone Service: Includes | 691 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 692 | | LTE (Long Term Evolution) | 693 | Coin | Fixed Public Pay/Coin telephones: Any | 694 | | coin or credit card operated device | 695 | 1way | One way outbound service | 696 | Prison | Inmate call/service | 697 | Temp | Soft dialtone/quick service/warm | 698 | | disconnect/suspended | 699 | MLTS | Multi-line telephone system: Includes | 700 | | all PBX, Centrex, key systems, | 701 | | Shared Tenant Service | 702 | SenseU | Sensor, unattended: Includes devices | 703 | | that generate DATA ONLY. This is | 704 | | one-way information exchange and | 705 | | there will be no other form of | 706 | | communication | 707 | SenseA | Sensor, attended: Includes devices | 708 | | that are supported by a monitoring | 709 | | service provider or automatically | 710 | | open a two-way communication path | 711 | POTS | Wireline: Plain Old Telephone Service | 712 | VOIP | VoIP Telephone Service: A type of | 713 | | service that offers communication | 714 | | over internet protocol, such as Fixed| 715 | | Nomadic, Mobile, ... | 716 | Remote | Off premise extension | 717 | Relay | Relay Service: a type of service where | 718 | | there is a human 3rd party agent who | 719 | | provides some kind of additional | 720 | | assistance to the caller. Includes | 721 | | sign language relay and telematics | 722 | | services which provide a service | 723 | | assistant on the call. | 724 +--------+----------------------------------------+ 726 Figure 3: Service Delivered by Provider to End User Registry. 728 More than one value MAY be returned. For example, a VoIP inmate 729 telephone service is a reasonable combination. 731 Reason for Need: Knowing the type of service may assist the PSAP 732 with the handling of the call. 734 How Used by Call Taker: Call takers often use this information to 735 determine what kinds of questions to ask callers, and how much to 736 rely on supportive information. An emergency call from a prison 737 is treated differently that a call from a sensor device. As the 738 information is not always available, and the registry is not all 739 encompassing, this is at best advisory information, but since it 740 mimics a similar capability in some current emergency calling 741 systems, it is known to be valuable. 743 3.2.3. Service Mobility Environment 745 Data Element: Service Mobility Environment 747 Use: Required 749 XML Element: 751 Description: This provides the service providers view of the 752 mobility of the caller. As the service provider may not know the 753 characteristics of the actual access network used, the value not 754 be relied upon. A registry will reflect the following initial 755 valid entries: 757 * Mobile: the device should be able to move at any time 759 * Fixed: the device is not expected to move unless the service is 760 relocated 762 * Nomadic: the device is not expected to change its point of 763 attachment while on a call 765 * Unknown: no information is known about the service mobility 766 environment for the device 768 Reason for Need: Knowing the service provider's belief of mobility 769 may assist the PSAP with the handling of the call. 771 How Used by Call Taker: To determine whether to assume the location 772 of the caller might change. 774 3.2.4. emergencyCall.SvcInfo Example 776 777 780 Business 781 MLTS 782 Fixed 783 785 Figure 4: emergencyCall.SvcInfo Example. 787 3.3. Device Information 789 This block provides information about the device used to place the 790 call. It should be provided by any service provider that knows what 791 device is being used, and by the device itself. The mime subtype is 792 "application/emergencyCall.DevInfo+xml". 794 3.3.1. Device Classification 796 Data Element: Device Classification 798 Use: Optional 800 XML Element: 802 Description: This data element defines the kind of device making the 803 emergency call. If the device provides the data structure, the 804 device information SHOULD be provided. If the service provider 805 provides the structure and it knows what the device is, the 806 service provider SHOULD provide the device information. Often the 807 carrier does not know what the device is. It is possible to 808 receive two Additional Data Associated with a Call data 809 structures, one created by the device and one created by the 810 service provider. This information describes the device, not how 811 it is being used. This data element defines the kind of device 812 making the emergency call. The registry with the initial set of 813 values is shown in Figure 5. 815 +--------+----------------------------------------+ 816 | Token | Description | 817 +--------+----------------------------------------+ 818 |Cordless| Cordless handset | 819 | Fixed | Fixed phone | 820 | Mobile | Mobile handset | 821 | ATA | analog terminal adapter | 822 |Satphone| Satellite phone | 823 | FSense | Stationary computing device (alarm | 824 | | system, data sensor) | 825 | Guard | Guardian devices | 826 | Desktop| Desktop PC | 827 | Laptop | Laptop computing device | 828 | Tablet | Tablet computing device | 829 | Alarm | Alarm system | 830 | MSense | Mobile Data sensor | 831 | Beacon | Personal beacons (spot) | 832 | Auto | Auto telematics | 833 | Truck | Truck telematics | 834 | Farm | Farm equipment telematics | 835 | Marine | Marine telematics | 836 | PDA | Personal digital assistant | 837 | PND | Personal navigation device) | 838 | SmrtPhn| Smart phone | 839 | Itab | Internet tablet | 840 | Game | Gaming console | 841 | Video | Video phone | 842 | Text | Other text device | 843 |SoftPhn | Soft phone or soft client software | 844 | NA | Not Available | 845 +--------+----------------------------------------+ 847 Figure 5: Device Classification Registry. 849 Reason for Need: The device classification implies the capability of 850 the calling device and assists in identifying the meaning of the 851 emergency call location information that is being presented. For 852 example, does the device require human intervention to initiate a 853 call or is this call the result of programmed instructions? Does 854 the calling device have the ability to update location or 855 condition changes? Is this device interactive or a one-way 856 reporting device? 858 How Used by Call Taker: May assist with location of caller. For 859 example, a cordless handset may be outside or next door. May 860 provide the calltaker some context about the caller, the 861 capabilities of the device used for the call or the environment 862 the device is being used in. 864 3.3.2. Device Manufacturer 866 Data Element: Device Manufacturer 868 Use: Optional 870 XML Element: 872 Description: The plain language name of the manufacturer of the 873 device. 875 Reason for Need: Used by PSAP management for post-mortem 876 investigation/resolution. 878 How Used by Call Taker: Probably not used by the calltaker, but by 879 PSAP management. 881 3.3.3. Device Model Number 883 Data Element: Device Model Number 885 Use: Optional 887 XML Element: 889 Description: Model number of the device. 891 Reason for Need: Used by PSAP management for after action 892 investigation/resolution. 894 How Used by Call Taker: Probably not used by the calltaker, but by 895 PSAP management. 897 3.3.4. Unique Device Identifier 899 Data Element: Unique Device Identifier 901 Use: Optional 903 XML Element: 905 Description: String that identifies the specific device making the 906 call or creating an event. 908 Reason for Need: Uniquely identifies the device as opposed to any 909 signaling identifiers encountered in the call signaling stream. 911 How Used by Call Taker: Probably not used by the calltaker they 912 would need to refer to management for investigation. 914 3.3.5. Type of Device Identifier 916 Data Element: Type of Device Identifier 918 Use: Conditional: must be provided if the DeviceID is provided 920 XML Element: 922 Description: Identifies the type of device identifier being 923 generated in the unique device identifier data element. A 924 registry with an initial set of values can be seen in Figure 6. 926 +--------+----------------------------------------+ 927 | Token | Description | 928 +--------+----------------------------------------+ 929 | MEID | Mobile Equipment Identifier (CDMA) | 930 | ESN | Electronic Serial Number(GSM) | 931 | MAC | Media Access Control Address (IEEE) | 932 | WiMAX | Device Certificate Unique ID | 933 | IMEI | International Mobile Equipment ID (GSM)| 934 | UDI | Unique Device Identifier | 935 | RFID | Radio Frequency Identification | 936 | SN | Manufacturer Serial Number | 937 +--------+----------------------------------------+ 939 Figure 6: Registry with Device Identifier Types. 941 Reason for Need: Identifies how to interpret the Unique Device 942 Identifier. 944 How Used by Call Taker: Additional information that may be used to 945 assist with call handling. 947 3.3.6. Device/Service Specific Additional Data Structure 949 Data Element: Device/service specific additional data structure 951 Use: Optional 953 XML Element: 954 Description: A URI representing additional data whose schema is 955 specific to the device or service which created it. An example is 956 the VEDs structure for a vehicle telematics device. The URI, when 957 dereferenced, MUST yield a data structure defined by the Device/ 958 service specific additional data type value. Different data may 959 be created by each classification; e.g., telematics creates VEDS 960 data set. 962 Reason for Need: Provides device/service specific data that may be 963 used by the call taker and/or responders. 965 How Used by Call Taker: Provide information to guide call takers to 966 select appropriate responders, give appropriate pre-arrival 967 instructions to callers, and advise responders of what to be 968 prepared for. May be used by responders to guide assistance 969 provided. 971 3.3.7. Device/Service Specific Additional Data Structure Type 973 Data Element: Type of device/service specific additional data 974 structure 976 Use: Conditional. MUST be provided when device/service specific 977 additional URI is provided 979 XML Element: 981 Description: Value from a registry defined by this document to 982 describe the type of data that can be retrieved from the device/ 983 service specific additional data structure. Initial values are: 985 * IEEE 1512 987 * VEDS 989 IEEE 1512 is the USDoT model for traffic incidents and Vehicular 990 Emergency Data Set (VEDS) provides data elements needed for an 991 efficient emergency response to vehicular emergency incidents. 993 Reason for Need: This data element allows identification of 994 externally defined schemas, which may have additional data that 995 may assist in emergency response. 997 How Used by Call Taker: This data element allows the end user 998 (calltaker or first responder) to know what type of additional 999 data may be available to aid in providing the needed emergency 1000 services. 1002 Note: Information which is specific to a location or a caller 1003 (person) should not be placed in this section. 1005 3.3.8. Choosing between defining a new type of block or new type of 1006 device/service specific additional data 1008 For devices that have device or service specific data, there are two 1009 choices to carry it. A new block can be defined, or the device/ 1010 service specific additional data URL the DevInfo block can be used 1011 and a new type for it defined . The data passed would likely be the 1012 same in both cases. Considerations for choosing which mechanism to 1013 register under include: 1015 Applicability: Information which will be carried by many kinds of 1016 devices or services are more appropriately defined as separate 1017 blocks. 1019 Privacy: Information which may contain private data may be better 1020 sent in the DevInfo block, rather than a new block so that 1021 implementations are not tempted to send the data by value, and 1022 thus having more exposure to the data than forcing the data to be 1023 retrieved via the URL in DevInfo. 1025 Size: Information which may be very may be better sent in the 1026 DevInfo block, rather than a new block so that implementations are 1027 not tempted to send the data by value. Conversely, data which is 1028 small may best be sent in a separate block so that it can be sent 1029 by value 1031 Availability of a server: Providing the data via the device block 1032 requires a server be made available to retrieve the data. 1033 Providing the data via new block allows it to be sent by value 1034 (CID). 1036 3.3.9. emergencyCall.DevInfo Example 1037 1038 1041 Fixed phone 1042 Nokia 1043 Lumia 800 1044 35788104 1045 IMEI 1046 1048 Figure 7: emergencyCallDevInfo Example. 1050 3.4. Owner/Subscriber Information 1052 This block describes the owner of the device (if provided by the 1053 device) or the subscriber information, if provided by a service 1054 provider. The contact location is not necessarily the location of 1055 the caller or incident, but is rather the nominal contact address. 1056 The mime subtype is "application/emergencyCall.Subscriber+xml". 1058 In some jurisdictions some or all parts of the subscriber-specific 1059 information are subject to privacy constraints. These constraints 1060 vary but dictate what information and be displayed and logged. A 1061 general privacy indicator expressing a desire for privacy is 1062 provided. The interpretation of how this is applied is left to the 1063 receiving jurisdiction as the custodians of the local regulatory 1064 requirements. 1066 3.4.1. Subscriber Data Privacy Indicator 1068 Attribute: privacyRequested, boolean. 1070 Use: Mandatory: Specifically expresses the subscriber's desire for 1071 privacy. 1073 Description: In some jurisdictions subscriber services can have a 1074 specific "Type of Service" which prohibits information such as the 1075 name of the subscriber from being displayed. This attribute 1076 should be used to explicitly indicate whether the subscriber 1077 service includes such constraints. 1079 Reason for Need: Some jurisdictions require subscriber privacy to be 1080 observed. 1082 How Used by Call Taker: Where privacy is indicated the call taker 1083 MAY not have access to some aspects of the subscriber information. 1085 3.4.2. xCard for Subscriber's Data 1087 Data Element: xCARD for Subscriber's Data 1089 Use: Conditional: Some services (e.g., prepaid phones, initialized 1090 phones, etc.) may not have this information. 1092 XML Element: 1094 Description: Information known by the service provider or device 1095 about the subscriber; e.g., Name, Address, Individual Telephone 1096 Number, Main Telephone Number and any other data. N, ORG (if 1097 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1098 than one TEL property is provided, a parameter from the vCard 1099 Property Value registry MUST be specified on each TEL. 1101 Reason for Need: When the caller is unable to provide information, 1102 this data may be used to obtain it 1104 How Used by Call Taker: Obtaining critical information about the 1105 caller and possibly the location when it is not able to be 1106 obtained otherwise. 1108 3.4.3. emergencyCall.SubInfo Example 1110 1111 1115 1116 1117 1118 Simon Perreault 1119 1120 Perreault 1121 Simon 1122 1123 1124 ing. jr 1125 M.Sc. 1126 1127 --0203 1128 1129 20090808T1430-0500 1130 1131 M 1132 1133 1 1134 1135 fr 1136 1137 1138 2 1139 1140 en 1141 1142 1143 work 1144 1145 Viagenie 1146 1147 1148 1149 work 1150 1154 1155 1156 1157 2875 boul. Laurier, suite D2-630 1158 Quebec 1159 QC 1160 G1V 2M2 1161 Canada 1162 1163 1164 1165 1166 work 1167 voice 1168 1169 1170 tel:+1-418-656-9254;ext=102 1171 1172 1173 1174 1175 work 1176 text 1177 voice 1178 cell 1179 video 1181 1182 1183 tel:+1-418-262-6501 1184 1185 1186 work 1187 1188 simon.perreault@viagenie.ca 1189 1190 1191 work 1192 1193 geo:46.766336,-71.28955 1194 1195 1196 work 1197 1198 1199 http://www.viagenie.ca/simon.perreault/simon.asc 1200 1201 1202 America/Montreal 1203 1204 home 1205 1206 http://nomis80.org 1207 1208 1209 1210 1211 1213 Figure 8: emergencyCall.SubInfo Example. 1215 3.5. Comment 1217 This block provides a mechanism for the data provider to supply 1218 extra, human readable information to the PSAP. It is not intended 1219 for a general purpose extension mechanism nor does it aim to provide 1220 machine-reable content. The mime subtype is "application/ 1221 emergencyCall.Comment+xml" 1223 3.5.1. Comment 1225 Data Element: EmergencyCall.Comment 1227 Use: Optional 1228 XML Element: 1230 Description: Human readable text providing additional information to 1231 the PSAP staff. 1233 Reason for Need: Explanatory information for values in the data 1234 structure 1236 How Used by Call Taker: To interpret the data provided 1238 3.5.2. emergencyCall.Comment Example 1240 1241 1244 This is an example text. 1245 1247 Figure 9: EmergencyCall.Comment Example. 1249 4. Transport 1251 This section defines how to convey additional data to an emergency 1252 service provider. Two different means are specified: the first uses 1253 the call signaling; the second uses the element of a 1254 PIDF-LO [RFC4119]. 1256 1. First, the ability to embed a Uniform Resource Identifier (URI) 1257 in an existing SIP header field, the Call-Info header, is 1258 defined. The URI points to the additional data structure. The 1259 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1260 document adds a new compound token starting with the value 1261 'emergencyCallData' for the Call-Info "purpose" parameter. If 1262 the "purpose" parameter is set to a value starting with 1263 'emergencyCallData', then the Call-Info header contains either an 1264 HTTPS URL pointing to an external resource or a CID (content 1265 indirection) URI that allows the data structure to be placed in 1266 the body of the SIP message. The "purpose" parameter also 1267 indicates the kind of data (by its MIME type) that is available 1268 at the URI. As the data is conveyed using a URI in the SIP 1269 signaling, the data itself may reside on an external resource, or 1270 may be contained within the body of the SIP message. When the 1271 URI refers to data at an external resource, the data is said to 1272 be passed by reference. When the URI refers to data contained 1273 within the body of the SIP message, the data is said to be passed 1274 by value. A PSAP or emergency responder is able to examine the 1275 type of data provided and selectively inspect the data it is 1276 interested in, while forwarding all of it (the values or 1277 references) to downstream entities. To be conveyed in a SIP 1278 body, additional data about a call is defined as a series of MIME 1279 objects. Each block defined in this document is an XML data 1280 structure identified by its MIME type. (Blocks defined by others 1281 may be encoded in XML or not, as identified by their MIME 1282 registration.) As usual, whenever more than one MIME part is 1283 included in the body of a message, MIME-multipart (i.e., 1284 'multipart/mixed') encloses them all. This document defines a 1285 set of XML schemas and MIME types used for each block defined 1286 here. When additional data is passed by value in the SIP 1287 signaling, each CID URL points to one block in the body. 1288 Multiple URIs are used within a Call-Info header field (or 1289 multiple Call-Info header fields) to point to multiple blocks. 1290 When additional data is provided by reference (in SIP signaling 1291 or Provided-By), each HTTPS URL references one block; the data is 1292 retrieved with an HTTPS GET operation, which returns one of the 1293 blocks as an object (the blocks defined here are returned as XML 1294 objects). 1296 2. Second, the ability to embed additional data structures in the 1297 element of a PIDF-LO [RFC4119] is defined. Besides 1298 a service provider in the call path, the access network provider 1299 may also have similar information that may be valuable to the 1300 PSAP. The access network provider may provide location in the 1301 form of a PIDF-LO from a location server via a location 1302 configuration protocol. The data structures described in this 1303 document are not specific to the location itself, but rather 1304 provides descriptive information having to do with the immediate 1305 circumstances about the provision of the location (who the access 1306 network is, how to contact that entity, what kind of service the 1307 access network provides, subscriber information, etc.). This 1308 data is similar in nearly every respect to the data known by 1309 service providers in the path of the call. When the access 1310 network provider and service provider are separate entities, the 1311 access network does not participate in the application layer 1312 signaling (and hence cannot add a Call-Info header field to the 1313 SIP message), but may provide location information to assist in 1314 locating the caller's device. The element of the 1315 PIDF-LO is a mechanism for the access network provider to supply 1316 the information about the entity or organization that supplied 1317 this location information. For this reason, this document 1318 describes a namespace per RFC 4119 for inclusion in the 1319 element of a PIDF-LO for adding information known 1320 to the access network provider. 1322 One or more blocks of data registered in the Emergency Call 1323 Additional Data registry, as defined in Section 9.1, may be included 1324 or referenced in the SIP signaling (using the Call-Info header field) 1325 or in the element of a PIDF-LO. Every block must be 1326 one of the types in the registry. Since the data of an emergency 1327 call may come from multiple sources, the data itself needs 1328 information describing the source. Consequently, each entity adding 1329 additional data MUST supply the "Data Provider" block. All other 1330 blocks are optional, but each entity SHOULD supply any blocks where 1331 it has at least some of the information in the block. 1333 4.1. Transmitting Blocks using the Call-Info Header 1335 A URI to a block MAY be inserted in a SIP request or response method 1336 (most often INVITE or MESSAGE) with a Call-Info header field 1337 containing a purpose value starting with 'emergencyCallData' and the 1338 type of data available at the URI. The type of data is denoted by 1339 including the root of the MIME type (not including the 1340 'emergencyCall' prefix and any suffix such as '+xml') with a '.' 1341 separator. For example, when referencing a block with MIME type 1342 'application/emergencyCall.ProviderInfo+xml', the 'purpose' parameter 1343 is set to 'emergencyCallData.ProviderInfo'. An example "Call-Info" 1344 header field for this would be: 1346 Call-Info: https://www.example.com/23sedde3; 1347 purpose="emergencyCallData.ProviderInfo" 1349 A Call-info header with a purpose value starting with 1350 'emergencyCallData' MUST only be sent on an emergency call, which can 1351 be ascertained by the presence of an emergency service urn in a Route 1352 header of a SIP message. 1354 If the data is provided by reference, an HTTPS URI MUST be included 1355 and consequently Transport Layer Security (TLS) protection is applied 1356 for protecting the retrieval of the information. 1358 The data may also be supplied by value in a SIP message. In this 1359 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1360 referencing the MIME body part. 1362 More than one Call-Info header with a purpose value starting with 1363 'emergencyCallData' can be expected, but at least one MUST be 1364 provided. The device MUST provide one if it knows no service 1365 provider is in the path of the call. The device MAY insert one if it 1366 uses a service provider. Any service provider in the path of the 1367 call MUST insert its own. For example, a device, a telematics 1368 service provider in the call path, as well as the mobile carrier 1369 handling the call will each provide one. There may be circumstances 1370 where there is a service provider who is unaware that the call is an 1371 emergency call and cannot reasonably be expected to determine that it 1372 is an emergency call. In that case, that service provider is not 1373 expected to provide emergencyCallData. 1375 4.2. Transmitting Blocks by Reference using the Provided-By Element 1377 The 'emergencyCallDataReference' element is used to transmit an 1378 additional data block by reference within a 'Provided-By' element of 1379 a PIDF-LO. The 'emergencyCallDataReference' element has two 1380 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1381 type of data block referenced. The value of 'ref' is an HTTPS URL 1382 that resolves to a data structure with information about the call. 1383 The value of 'purpose' is the same as used in a 'Call-Info' header 1384 field (as specified in Section 4.1). 1386 For example, to reference a block with MIME type 'application/ 1387 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to 1388 'emergencyCallData.ProviderInfo'. An example 1389 'emergencyCallDataReference' element for this would be: 1391 1394 4.3. Transmitting Blocks by Value using the Provided-By Element 1396 It is RECOMMENDED that access networks supply the data specified in 1397 this document by reference, but they MAY provide the data by value. 1399 The 'emergencyCallDataValue' element is used to transmit an 1400 additional data block by value within a 'Provided-By' element of a 1401 PIDF-LO. The 'emergencyCallDataValue' element has one attribute: 1402 'purpose' to indicate the type of data block contained. The value of 1403 'purpose' is the same as used in a 'Call-Info' header field (as 1404 specified in Section 4.1, and in Section 4.1). The same XML 1405 structure as would be contained in the corresponding MIME type body 1406 part is placed inside the 'emergencyCallDataValue' element. 1408 For example: 1410 1412 1413 1415 1417 This is an example text. 1418 1419 1420 1421 1423 Test 1424 NENA 1425 Access Infrastructure Provider 1426 1427 sip:15555550987@burf.example.com;user=phone 1428 1429 1430 1432 Example Provided-By by Value. 1434 4.4. The Content-Disposition Parameter 1436 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1437 It updates and clarifies handling originally defined in RFC 3261 1438 [RFC3261] based on implementation experience. While RFC 3261 did not 1439 mandate support for 'multipart' message bodies 'multipart/mixed' MIME 1440 bodies are, however, used by many extensions (including additional 1441 data) today. For example, adding a PIDF-LO, SDP, and additional data 1442 in body of a SIP message requires a 'multipart' message body. 1444 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1445 parameter for the Content-Disposition header field. These RFCs 1446 describe how a UAS reacts if it receives a message body whose content 1447 type or disposition type it does not understand. If the 'handling' 1448 parameter has the value "optional", the UAS ignores the message body. 1449 If the 'handling' parameter has the value "required", the UAS returns 1450 a 415 (Unsupported Media Type) response. The 'by-reference' 1451 disposition type allows a SIP message to contain a reference to the 1452 body part, and the SIP UA processes the body part according to the 1453 reference. This is the case for the Call-info header containing a 1454 Content Indirection (CID) URL. 1456 As an example, a SIP message indicates the Content-Disposition 1457 parameter in the body of the SIP message as shown in Figure 10. 1459 Content-Type: application/sdp 1461 ...Omit Content-Disposition here; defaults are ok 1462 ...SDP goes here 1463 --boundary1 1465 Content-Type: application/pidf+xml 1466 Content-ID: 1467 Content-Disposition: by-reference;handling=optional 1469 ...PIDF-LO goes here 1471 --boundary1-- 1473 Content-Type: application/emergencyCall.ProviderInfo+xml 1474 Content-ID: <1234567890@atlanta.example.com> 1475 Content-Disposition: by-reference;handling=optional 1477 ...Additional data goes here 1479 --boundary1-- 1481 Figure 10: Example for use of the Content-Disposition Parameter in 1482 SIP. 1484 5. Examples 1486 This section provides three examples of communicating additional 1487 data. In Figure 11 additional data is communicated in a SIP INVITE 1488 per value. In Figure 12 we illustrate how additional data is added 1489 by a SIP proxy per reference. Finally, an example for including 1490 additional data in the element of a PIDF-LO is 1491 illustrated. 1493 INVITE sips:bob@biloxi.example.com SIP/2.0 1494 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1495 Max-Forwards: 70 1496 To: Bob 1497 From: Alice ;tag=9fxced76sl 1498 Call-ID: 3848276298220188511@atlanta.example.com 1499 Call-Info: ;purpose=icon, 1500 ;purpose=info, 1501 1502 ;purpose=emergencyCallData.ProviderInfo 1503 Geolocation: 1504 Geolocation-Routing: no 1505 Accept: application/sdp, application/pidf+xml, 1506 application/emergencyCallProviderinfo+xml 1507 CSeq: 31862 INVITE 1508 Contact: 1509 Content-Type: multipart/mixed; boundary=boundary1 1511 Content-Length: ... 1513 --boundary1 1515 Content-Type: application/sdp 1517 ...SDP goes here 1519 --boundary1 1521 Content-Type: application/pidf+xml 1522 Content-ID: 1523 Content-Disposition: by-reference;handling=optional 1525 ...PIDF-LO goes here 1527 --boundary1-- 1529 Content-Type: application/emergencyCall.ProviderInfo+xml 1530 Content-ID: <1234567890@atlanta.example.com> 1531 Content-Disposition: by-reference;handling=optional 1533 ...Additional data goes here 1535 --boundary1-- 1537 Figure 11: Example: Attaching Additional Data via CID to a SIP 1538 INVITE. 1540 INVITE sips:bob@biloxi.example.com SIP/2.0 1541 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1542 Max-Forwards: 70 1543 To: Bob 1544 From: Alice ;tag=9fxced76sl 1545 Call-ID: 3848276298220188511@atlanta.example.com 1546 Call-Info: ;purpose=icon, 1547 ;purpose=info, 1548 1549 ;purpose=emergencyCallData.ProviderInfo 1550 Geolocation: 1551 Geolocation-Routing: no 1552 Accept: application/sdp, application/pidf+xml, 1553 application/emergencyCallProviderinfo+xml 1554 CSeq: 31862 INVITE 1555 Contact: 1556 Content-Type: multipart/mixed; boundary=boundary1 1558 Content-Length: ... 1560 --boundary1 1562 Content-Type: application/sdp 1564 ...SDP goes here 1566 --boundary1 1568 Content-Type: application/pidf+xml 1569 Content-ID: 1570 Content-Disposition: by-reference;handling=optional 1572 ...PIDF-LO goes here 1574 --boundary1-- 1576 Figure 12: Example: Attaching Additional Data per Reference in a SIP 1577 INVITE. 1579 1580 1585 1586 1587 1588 1590 AU 1591 NSW 1592 Wollongong 1593 North Wollongong 1594 Flinders 1595 Street 1596 Campbell Street 1597 Gilligan's Island 1598 Corner 1599 Video Rental Store 1600 2500 1601 Westerns and Classics 1602 store 1603 Private Box 15 1604 1605 1606 1607 true 1608 1609 2013-07-10T20:00:00Z 1610 1611 1612 802.11 1613 1616 1619 1620 1622 University of California, Irvine 1623 1624 urn:nena:companyid:uci 1625 NENA 1626 Other 1627 tel:+1 9498245222 1628 EN 1629 1631 1633 This is an example text. 1634 1636 1637 1638 1639 mac:1234567890ab 1640 2013-07-09T20:57:29Z 1641 1642 1644 Figure 13: Example: Including Additional Data via the Provided-By 1645 Element in a PIDF-LO. 1647 6. XML Schemas 1648 This section defines the XML schemas of the five data blocks. 1649 Additionally, the Provided-By schema is specified. 1651 6.1. emergencyCall.ProviderInfo XML Schema 1653 1654 1663 1666 1668 1669 1670 1671 1672 1674 1678 1679 1680 1681 1682 1683 1685 1686 1687 1689 1691 1693 1696 1698 1700 1703 1705 1708 1710 1711 1713 1715 Figure 14: emergencyCall.ProviderInfo XML Schema. 1717 6.2. emergencyCall.SvcInfo XML Schema 1719 1720 1727 1730 1732 1733 1734 1736 1738 1740 1743 1745 1746 1748 1750 Figure 15: emergencyCall.SvcInfo XML Schema. 1752 6.3. emergencyCall.DevInfo XML Schema 1754 1755 1762 1765 1767 1768 1769 1771 1773 1775 1777 1779 1781 1784 1786 1787 1789 1790 Figure 16: emergencyCall.DevInfo XML Schema. 1792 6.4. emergencyCall.SubInfo XML Schema 1794 1795 1803 1806 1808 1810 1811 1812 1813 1816 1818 1819 1820 1821 1823 1825 Figure 17: emergencyCall.SubInfo XML Schema. 1827 6.5. emergencyCall.Comment XML Schema 1829 1830 1836 1839 1841 1842 1843 1846 1848 1849 1851 1852 1853 1854 1855 1856 1857 1859 1861 Figure 18: EmergencyCall.Comment XML Schema. 1863 6.6. Provided-By XML Schema 1865 This section defines the Provided-By schema. 1867 1868 1881 1882 1883 1884 1885 1887 1889 1890 1892 1896 1900 1903 1905 1907 1909 1910 1911 1912 1913 1915 1916 1918 1920 1921 1922 1924 1926 1927 1928 1932 1935 1938 1941 1945 1948 1949 1951 1953 Figure 19: Provided-By XML Schema. 1955 7. Security Considerations 1957 The information in this data structure will usually be considered 1958 private. HTTPS is specified to require the provider of the 1959 information to validate the credentials of the requester. While the 1960 creation of a PKI that has global scope may be difficult, the 1961 alternatives to creating devices and services that can provide 1962 critical information securely are more daunting. The provider may 1963 enforce any policy it wishes to use, but PSAPs and responder agencies 1964 should deploy a PKI so that providers of additional data can check 1965 the certificate of the client and decide the appropriate policy to 1966 enforce based on that certificate. 1968 Ideally, the PSAP and emergency responders will be given credentials 1969 signed by an authority trusted by the data provider. In most 1970 circumstances, nationally recognized credentials would be sufficient, 1971 and if the emergency services arranges a PKI, data providers could be 1972 provisioned with the root CA public key for a given nation. Some 1973 nations are developing a PKI for this, and related, purposes. Since 1974 calls could be made from devices where the device and/or the service 1975 provider(s) are not local to the emergency authorities, globally 1976 recognized credentials are useful. This might be accomplished by 1977 extending the notion of the "forest guide" described in [RFC5222] to 1978 allow the forest guide to provide the credential of the PKI root for 1979 areas that it has coverage information for, but standards for such a 1980 mechanism are not yet available. In its absence, the data provider 1981 will need to obtain the root CA credentials for any areas it is 1982 willing to provide additional data by out of band means. With the 1983 credential of the root CA for a national emergency services PKI, the 1984 data provider server can validate the credentials of an entity 1985 requesting additional data by reference. 1987 The data provider also needs a credential that can be verified by the 1988 emergency services to know that it is receiving data from the right 1989 server. The emergency authorities could provide credentials, 1990 distinguishable from credentials it provides to emergency responders 1991 and PSAPs, which could be used to validate data providers. Such 1992 credentials would have to be acceptable to any PSAP or responder that 1993 could receive a call with additional data supplied by that provider. 1994 This would be extensible to global credential validation using the 1995 forest guide as above. In the absence of such credentials, the 1996 emergency authorities could maintain a list of local data providers' 1997 credentials provided to it out of band. At a minimum, the emergency 1998 authorities could obtain a credential from the DNS entry of the 1999 domain in the Additional Data URI to at least validate that the 2000 server is known to the domain providing the URI. 2002 Data provided by devices by reference have similar credential 2003 validation issues to service providers, and the solutions are the 2004 same. 2006 8. Privacy Considerations 2008 This document enables functionality for conveying additional 2009 information about the caller to the callee. Some of this information 2010 is personal data and therefore privacy concerns arise. An explicit 2011 privacy indicator for information directly relating to the callers 2012 identity is defined and use is mandatory. However, observance of 2013 this request for privacy and what information it relates to is 2014 controlled by the destination jurisdiction. 2016 There are a number of privacy concerns with regular real-time 2017 communication services that are also applicable to emergency calling. 2018 Data protection regulation world-wide has, however, decided to create 2019 exceptions for emergency services since the drawbacks of disclosing 2020 personal data in comparison to the benefit for the emergency caller 2021 are often towards the latter. Hence, the data protection rights of 2022 individuals are often waived for emergency situations. There are, 2023 however, still various countries that offer some degree of anonymity 2024 for the caller towards PSAP call takers. 2026 The functionality defined in this document, however, far exceeds the 2027 amount of information sharing found in the Plain old telephone system 2028 (POTS). For this reason there are additional privacy threats to 2029 consider, which are described in more detail in [RFC6973]. 2031 Stored Data Compromise: First, there is an increased risk of stored 2032 data compromise since additional data is collected and stored in 2033 databases. Without adequate measures to secure stored data from 2034 unauthorized or inappropriate access at access network operators, 2035 service providers, end devices, as well as PSAPs individuals are 2036 exposed to potential financial, reputational, or physical harm. 2038 Misattribution: If the personal data collected and conveyed is 2039 incorrect or inaccurate then this may lead to misattribution. 2040 Misattribution occurs when data or communications related to one 2041 individual are attributed to another. 2043 Identification: By the nature of the additional data and its 2044 capability to provide much richer information about the caller, 2045 the call, and the location the calling party is identified in a 2046 much better way. Some users may feel uncomfortable with this 2047 degree of information sharing even in emergency services 2048 situations. 2050 Secondary Use: Furthermore, there is the risk of secondary use. 2051 Secondary use is the use of collected information about an 2052 individual without the individual's consent for a purpose 2053 different from that for which the information was collected. The 2054 stated purpose of the additional data is for emergency services 2055 purposes but theoretically the same information could be used for 2056 any other call as well. Additionally, parties involved in the 2057 emergency call may retain the obtained information and may re-use 2058 it for other, non-emergency services purposes. 2060 Disclosure: When the data defined in this document is not properly 2061 security (while in transit with traditional communication security 2062 techniques, and while at rest using access control mechanisms) 2063 there is the risk of disclosure, which is the revelation of 2064 information about an individual that affects the way others judge 2065 the individual. 2067 To mitigate these privacy risks the following countermeasures can be 2068 taken. 2070 In regions where callers can elect to suppress certain personally 2071 identifying information, the network or PSAP functionality can 2072 inspect privacy flags within the SIP headers to determine what 2073 information may be passed, stored, or displayed to comply with local 2074 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2075 The presence of this privacy type in a Privacy header field indicates 2076 that the user would like the network asserted identity to be kept 2077 private with respect to SIP entities outside the trust domain with 2078 which the user authenticated, including the PSAP. 2080 This document defines various data structures that constitutes 2081 personal data. Local regulations may govern what data must be 2082 provided in emergency calls, but in general, the emergency call 2083 system is often aided by the kinds of information described in this 2084 document. There is a tradeoff between the privacy considerations and 2085 the utility of the data. For adequate protection this specification 2086 requires all data exchanges to be secured via communication security 2087 techniques (namely TLS) against eavesdropping and inception. 2088 Furthermore, security safeguards are required to prevent unauthorized 2089 access to data at rest. Various security incidents over the last 10 2090 years have shown data breaches are not not uncommon and are often 2091 caused by lack of proper access control frameworks, software bugs 2092 (buffer overflows), or missing input parsing (SQL injection attacks). 2093 The risks of data breaches is increased with the obligation for 2094 emergency services to retain emergency call related data for extended 2095 periods, e.g., several years are the norm. 2097 Finally, it is also worth to highlight the nature of the SIP 2098 communication architecture, which introduces additional complications 2099 for privacy. Some forms of data can be sent by value in the SIP 2100 signaling or by value (URL in SIP signaling). When data is sent by 2101 value, all intermediaries have access to the data. As such, these 2102 intermediaries may also introduce additional privacy risk. 2103 Therefore, in situations where the conveyed information raises 2104 privacy concerns and intermediaries are involved transmitting a 2105 reference is more appropriate (assuming proper access control 2106 policies are available for distinguishing the different entities 2107 dereferencing the reference). Without access control policies any 2108 party in possession of the reference is able to resolve the reference 2109 and to obtain the data, including intermediaries. 2111 9. IANA Considerations 2113 9.1. Registry creation 2115 This document creates a new registry called 'Emergency Call 2116 Additional Data'. The following sub-registries are created in 2117 Emergency Call Additional Data: 2119 9.1.1. Provider ID Series Registry 2121 This document creates a new sub-registry called 'Additional Call Data 2122 Provider ID Series'. As defined in [RFC5226], this registry operates 2123 under "Expert Review" rules. The expert should determine that the 2124 entity requesting a new value is a legitimate issuer of service 2125 provider IDs suitable for use in Additional Call Data. 2127 The content of this registry includes: 2129 Name: The identifier which will be used in the ProviderIDSeries 2130 element 2132 Source: The full name of the organization issuing the identifiers 2134 URL: A URL to the organization for further information 2136 The initial set of values is listed in Figure 20. 2138 +-----------+--------------------------+----------------------+ 2139 | Name | Source | URL | 2140 +-----------+--------------------------+----------------------+ 2141 | NENA | National Emergency | http://www.nena.org | 2142 | | Number Association | | 2143 | EENA | European Emergency | http://www.eena.org | 2144 | | Number Association | | 2145 +-----------+--------------------------+----------------------+ 2147 Figure 20: Provider ID Series Registry. 2149 9.1.2. Service Provider Type Registry 2151 This document creates a new sub-registry called 'Service Provider 2152 Type'. As defined in [RFC5226], this registry operates under "Expert 2153 Review". The expert should determine that the proposed new value is 2154 distinct from existing values and appropriate for use in the 2155 TypeOfServicerProvider element 2157 The content of this registry includes: 2159 Name: Value to be used in TypeOfServiceProvider. 2161 Description: A short description of the type of service provider 2163 The initial set of values is defined in Figure 1. 2165 9.1.3. Service Delivered Registry 2166 This document creates a new sub-registry called 'Service Delivered'. 2167 As defined in [RFC5226], this registry operates under "Expert Review" 2168 rules. The expert should consider whether the proposed service is 2169 unique from existing services and the definition of the service will 2170 be clear to implementors and PSAPS/responders. 2172 The content of this registry includes: 2174 Name: Enumeration token of the service. 2176 Description: Short description identifying the service. 2178 The initial set of values are defined in Figure 3. 2180 9.1.4. Device Classification Registry 2182 This document creates a new sub-registry called 'Device 2183 Classification'. As defined in [RFC5226], this registry operates 2184 under "Expert Review" rules. The expert should consider whether the 2185 proposed class is unique from existing classes and the definition of 2186 the class will be clear to implementors and PSAPS/responders. 2188 The content of this registry includes: 2190 Name: Enumeration token of the device classification. 2192 Description: Short description identifying the device type. 2194 The initial set of values are defined in Figure 5. 2196 9.1.5. Device ID Type Type Registry 2198 This document creates a new sub-registry called 'Additional Call Data 2199 Device ID Type'. As defined in [RFC5226], this registry operates 2200 under "Expert Review" rules. The expert should ascertain that the 2201 proposed type is well understood, and provides the information useful 2202 to PSAPs and responders to uniquely identify a device. 2204 The content of this registry includes: 2206 Name: Enumeration token of the device id type. 2208 Description: Short description identifying type of device id. 2210 The initial set of values are defined in Figure 6. 2212 9.1.6. Device/Service Data Type Registry 2213 This document creates a new sub-registry called 'Device/Service Data 2214 Type Registry'. As defined in [RFC5226], this registry operates 2215 under "Expert Review" and "Specification Required" rules. The expert 2216 should ascertain that the proposed type is well understood, and 2217 provides information useful to PSAPs and responders. The 2218 specification must contain a complete description of the data, and a 2219 precise format specification suitable to allow interoperable 2220 implementations. 2222 The content of this registry includes: 2224 Name: Enumeration token of the data type. 2226 Description: Short description identifying the the data. 2228 Specification: Citation for the specification of the data. 2230 The initial set of values are listed in Figure 21. 2232 +---------+----------------------------------------+----------------+ 2233 | Token | Description | Specification | 2234 +---------+----------------------------------------+----------------+ 2235 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2236 +---------+----------------------------------------+----------------+ 2237 | VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS | 2238 +---------+----------------------------------------+----------------+ 2240 Figure 21: Device/Service Data Type Registry. 2242 9.1.7. Additional Data Blocks Registry 2244 This document creates a new sub-registry called 'Additional Data 2245 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2246 As defined in [RFC5226], this registry operates under "Expert Review" 2247 and "Specification Required" rules. The expert is responsible for 2248 verifying that the document contains a complete and clear 2249 specification and the proposed functionality does not obviously 2250 duplicate existing functionality. 2252 The content of this registry includes: 2254 Name: Element Name of enclosing block. 2256 Reference: The document that describes the block 2258 The initial set of values are listed in Figure 22. 2260 +--------------+------------+ 2261 | Token | Reference | 2262 +--------------+------------+ 2263 | ProviderInfo | [This RFC] | 2264 | SvcInfo | [This RFC] | 2265 | DevInfo | [This RFC] | 2266 | Subscriber | [This RFC] | 2267 | Comment | [This RFC] | 2268 +--------------+------------+ 2270 Figure 22: Additional Data Blocks Registry. 2272 9.2. 'emergencyCallData' Purpose Parameter Value 2274 This document defines the 'emergencyCall' value for the "purpose" 2275 parameter of the Call-Info header field. The Call-Info header and 2276 the corresponding registry for the 'purpose' parameter was 2277 established with RFC 3261 [RFC3261]. 2279 Header Parameter New 2280 Field Name Value Reference 2281 ---------- --------- ----------------- --------- 2282 Call-Info purpose emergencyCall [This RFC] 2284 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2286 This section registers the namespace specified in Section 9.5.1 in 2287 the provided-by registry established by RFC 4119, for usage within 2288 the element of a PIDF-LO. 2290 The schema for the provided-by schema used by this document is 2291 specified in Section 6.6. 2293 9.4. MIME Registrations 2295 9.4.1. MIME Content-type Registration for 'application/ 2296 emergencyCall.ProviderInfo+xml' 2298 This specification requests the registration of a new MIME type 2299 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2300 RFC 3023 [RFC3023]. 2302 MIME media type name: application 2303 MIME subtype name: emergencyCall.ProviderInfo+xml 2305 Mandatory parameters: none 2307 Optional parameters: charset Indicates the character encoding of 2308 enclosed XML. 2310 Encoding considerations: Uses XML, which can employ 8-bit 2311 characters, depending on the character encoding used. See 2312 Section 3.2 of RFC 3023 [RFC3023]. 2314 Security considerations: This content type is designed to carry 2315 the data provider information, which is a sub-category of 2316 additional data about an emergency call. Since this data contains 2317 personal information appropriate precautions have to be taken to 2318 limit unauthorized access, inappropriate disclosure to third 2319 parties, and eavesdropping of this information. Please refer to 2320 Section 7 and Section 8 for more information. 2322 Interoperability considerations: None 2324 Published specification: [TBD: This specification] 2326 Applications which use this media type: Emergency Services 2328 Additional information: Magic Number: None File Extension: .xml 2329 Macintosh file type code: 'TEXT' 2331 Person and email address for further information: Hannes 2332 Tschofenig, Hannes.Tschofenig@gmx.net 2334 Intended usage: LIMITED USE 2336 Author: This specification is a work item of the IETF ECRIT 2337 working group, with mailing list address . 2339 Change controller: The IESG 2341 9.4.2. MIME Content-type Registration for 'application/ 2342 emergencyCall.SvcInfo+xml' 2344 This specification requests the registration of a new MIME type 2345 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2346 RFC 3023 [RFC3023]. 2348 MIME media type name: application 2350 MIME subtype name: emergencyCall.SvcInfo+xml 2351 Mandatory parameters: none 2353 Optional parameters: charset Indicates the character encoding of 2354 enclosed XML. 2356 Encoding considerations: Uses XML, which can employ 8-bit 2357 characters, depending on the character encoding used. See 2358 Section 3.2 of RFC 3023 [RFC3023]. 2360 Security considerations: This content type is designed to carry 2361 the service information, which is a sub-category of additional 2362 data about an emergency call. Since this data contains personal 2363 information appropriate precautions have to be taken to limit 2364 unauthorized access, inappropriate disclosure to third parties, 2365 and eavesdropping of this information. Please refer to Section 7 2366 and Section 8 for more information. 2368 Interoperability considerations: None 2370 Published specification: [TBD: This specification] 2372 Applications which use this media type: Emergency Services 2374 Additional information: Magic Number: None File Extension: .xml 2375 Macintosh file type code: 'TEXT' 2377 Person and email address for further information: Hannes 2378 Tschofenig, Hannes.Tschofenig@gmx.net 2380 Intended usage: LIMITED USE 2382 Author: This specification is a work item of the IETF ECRIT 2383 working group, with mailing list address . 2385 Change controller: The IESG 2387 9.4.3. MIME Content-type Registration for 'application/ 2388 emergencyCall.DevInfo+xml' 2390 This specification requests the registration of a new MIME type 2391 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2392 RFC 3023 [RFC3023]. 2394 MIME media type name: application 2396 MIME subtype name: emergencyCall.DevInfo+xml 2398 Mandatory parameters: none 2399 Optional parameters: charset Indicates the character encoding of 2400 enclosed XML. 2402 Encoding considerations: Uses XML, which can employ 8-bit 2403 characters, depending on the character encoding used. See 2404 Section 3.2 of RFC 3023 [RFC3023]. 2406 Security considerations: This content type is designed to carry 2407 the device information information, which is a sub-category of 2408 additional data about an emergency call. Since this data contains 2409 personal information appropriate precautions have to be taken to 2410 limit unauthorized access, inappropriate disclosure to third 2411 parties, and eavesdropping of this information. Please refer to 2412 Section 7 and Section 8 for more information. 2414 Interoperability considerations: None 2416 Published specification: [TBD: This specification] 2418 Applications which use this media type: Emergency Services 2420 Additional information: Magic Number: None File Extension: .xml 2421 Macintosh file type code: 'TEXT' 2423 Person and email address for further information: Hannes 2424 Tschofenig, Hannes.Tschofenig@gmx.net 2426 Intended usage: LIMITED USE 2428 Author: This specification is a work item of the IETF ECRIT 2429 working group, with mailing list address . 2431 Change controller: The IESG 2433 9.4.4. MIME Content-type Registration for 'application/ 2434 emergencyCall.SubInfo+xml' 2436 This specification requests the registration of a new MIME type 2437 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2438 RFC 3023 [RFC3023]. 2440 MIME media type name: application 2442 MIME subtype name: emergencyCall.SubInfo+xml 2444 Mandatory parameters: none 2445 Optional parameters: charset Indicates the character encoding of 2446 enclosed XML. 2448 Encoding considerations: Uses XML, which can employ 8-bit 2449 characters, depending on the character encoding used. See 2450 Section 3.2 of RFC 3023 [RFC3023]. 2452 Security considerations: This content type is designed to carry 2453 owner/subscriber information, which is a sub-category of 2454 additional data about an emergency call. Since this data contains 2455 personal information appropriate precautions have to be taken to 2456 limit unauthorized access, inappropriate disclosure to third 2457 parties, and eavesdropping of this information. Please refer to 2458 Section 7 and Section 8 for more information. 2460 Interoperability considerations: None 2462 Published specification: [TBD: This specification] 2464 Applications which use this media type: Emergency Services 2466 Additional information: Magic Number: None File Extension: .xml 2467 Macintosh file type code: 'TEXT' 2469 Person and email address for further information: Hannes 2470 Tschofenig, Hannes.Tschofenig@gmx.net 2472 Intended usage: LIMITED USE 2474 Author: This specification is a work item of the IETF ECRIT 2475 working group, with mailing list address . 2477 Change controller: The IESG 2479 9.4.5. MIME Content-type Registration for 'application/ 2480 emergencyCall.Comment+xml' 2482 This specification requests the registration of a new MIME type 2483 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2484 RFC 3023 [RFC3023]. 2486 MIME media type name: application 2488 MIME subtype name: emergencyCall.Comment+xml 2490 Mandatory parameters: none 2491 Optional parameters: charset Indicates the character encoding of 2492 enclosed XML. 2494 Encoding considerations: Uses XML, which can employ 8-bit 2495 characters, depending on the character encoding used. See 2496 Section 3.2 of RFC 3023 [RFC3023]. 2498 Security considerations: This content type is designed to carry a 2499 comment, which is a sub-category of additional data about an 2500 emergency call. This data may contain personal information. 2501 Appropriate precautions may have to be taken to limit unauthorized 2502 access, inappropriate disclosure to third parties, and 2503 eavesdropping of this information. Please refer to Section 7 and 2504 Section 8 for more information. 2506 Interoperability considerations: None 2508 Published specification: [TBD: This specification] 2510 Applications which use this media type: Emergency Services 2512 Additional information: Magic Number: None File Extension: .xml 2513 Macintosh file type code: 'TEXT' 2515 Person and email address for further information: Hannes 2516 Tschofenig, Hannes.Tschofenig@gmx.net 2518 Intended usage: LIMITED USE 2520 Author: This specification is a work item of the IETF ECRIT 2521 working group, with mailing list address . 2523 Change controller: The IESG 2525 9.5. URN Sub-Namespace Registration 2527 9.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData 2529 This section registers a new XML namespace, as per the guidelines in 2530 RFC 3688 [RFC3688]. 2532 URI: urn:ietf:params:xml:ns:emergencyCallAddlData 2534 Registrant Contact: IETF, ECRIT working group, , as 2535 delegated by the IESG . 2537 XML: 2539 BEGIN 2540 2541 2543 2544 2545 2547 Namespace for Additional Emergency Call Data 2548 2549 2550

Namespace for Additional Data related to an Emergency Call

2551

See [TBD: This document].

2552 2553 2554 END 2556 9.5.2. Registration for 2557 urn:ietf:params:xml:ns:emergencyCallProviderInfo 2559 This section registers a new XML namespace, as per the guidelines in 2560 RFC 3688 [RFC3688]. 2562 URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo 2564 Registrant Contact: IETF, ECRIT working group, , as 2565 delegated by the IESG . 2567 XML: 2569 BEGIN 2570 2571 2573 2574 2575 2577 Namespace for Additional Emergency Call Data: 2578 Data Provider Information 2579 2580 2581

Namespace for Additional Data related to an Emergency Call

2582

Data Provider Information

2583

See [TBD: This document].

2584 2585 2586 END 2588 9.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2590 This section registers a new XML namespace, as per the guidelines in 2591 RFC 3688 [RFC3688]. 2593 URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2595 Registrant Contact: IETF, ECRIT working group, , as 2596 delegated by the IESG . 2598 XML: 2600 BEGIN 2601 2602 2604 2605 2606 2608 Namespace for Additional Emergency Call Data: 2609 Service Information 2610 2611 2612

Namespace for Additional Data related to an Emergency Call

2613

Service Information

2614

See [TBD: This document].

2615 2616 2617 END 2619 9.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo 2621 This section registers a new XML namespace, as per the guidelines in 2622 RFC 3688 [RFC3688]. 2624 URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo 2625 Registrant Contact: IETF, ECRIT working group, , as 2626 delegated by the IESG . 2628 XML: 2630 BEGIN 2631 2632 2634 2635 2636 2638 Namespace for Additional Emergency Call Data: 2639 Device Information 2640 2641 2642

Namespace for Additional Data related to an Emergency Call

2643

Device Information

2644

See [TBD: This document].

2645 2646 2647 END 2649 9.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo 2651 This section registers a new XML namespace, as per the guidelines in 2652 RFC 3688 [RFC3688]. 2654 URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo 2656 Registrant Contact: IETF, ECRIT working group, , as 2657 delegated by the IESG . 2659 XML: 2661 BEGIN 2662 2663 2665 2666 2667 2670 Namespace for Additional Emergency Call Data: 2671 Owner/Subscriber Information 2672 2673 2674

Namespace for Additional Data related to an Emergency Call

2675

Owner/Subscriber Information

2676

See [TBD: This document].

2677 2678 2679 END 2681 9.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment 2683 This section registers a new XML namespace, as per the guidelines in 2684 RFC 3688 [RFC3688]. 2686 URI: urn:ietf:params:xml:ns:emergencyCall.Comment 2688 Registrant Contact: IETF, ECRIT working group, , as 2689 delegated by the IESG . 2691 XML: 2693 BEGIN 2694 2695 2697 2698 2699 2701 Namespace for Additional Emergency Call Data:Comment 2702 2703 2704

Namespace for Additional Data related to an Emergency Call

2705

Comment

2706

See [TBD: This document].

2707 2708 2709 END 2711 9.6. Schema Registrations 2712 This specification registers five schemas, as per the guidelines in 2713 RFC 3688 [RFC3688]. 2715 URI: urn:ietf:params:xml:schema:additional- 2716 data:emergencyCallProviderInfo 2718 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2719 delegated by the IESG (iesg@ietf.org). 2721 XML: The XML schema can be found in Figure 14. 2723 URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo 2725 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 2726 delegated by the IESG (iesg@ietf.org). 2728 XML: The XML schema can be found in Figure 15. 2730 URI: urn:ietf:params:xml:schema:additional- 2731 data:emergencyCallDevInfo 2733 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2734 delegated by the IESG (iesg@ietf.org). 2736 XML: The XML schema can be found in Figure 16. 2738 URI: urn:ietf:params:xml:schema:additional- 2739 data:emergencyCall.SubInfo 2741 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2742 delegated by the IESG (iesg@ietf.org). 2744 XML: The XML schema can be found in Section 6.4. 2746 URI: urn:ietf:params:xml:schema:additional- 2747 data:emergencyCall.Comment 2749 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2750 delegated by the IESG (iesg@ietf.org). 2752 XML: The XML schema can be found in Section 6.5. 2754 9.7. VCard Parameter Value Registration 2756 This document registers a new value in the vCARD Parameter Values 2757 registry as defined by [RFC6350] with the following template: 2759 Value: main 2760 Purpose: The main telephone number, typically of an enterprise, as 2761 opposed to a direct dial number of an individual employee 2763 Conformance: This value can be used with the "TYPE" parameter 2764 applied on the "TEL" property. 2766 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 2767 00 2769 10. Acknowledgments 2771 This work was originally started in NENA and has benefitted from a 2772 large number of participants in NENA standardization efforts, 2773 originally in the Long Term Definition Working Group, the Data 2774 Technical Committee and most recently the Additional Data working 2775 group. The authors are grateful for the initial work and extended 2776 comments provided by many NENA participants, including Delaine 2777 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 2778 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 2779 and Robert (Bob) Sherry. 2781 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 2782 Thomson, Keith Drage, and Laura Liess for their review comments. 2784 11. References 2786 11.1. Normative References 2788 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2789 Requirement Levels", BCP 14, RFC 2119, March 1997. 2791 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 2792 Locators", RFC 2392, August 1998. 2794 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 2795 Types", RFC 3023, January 2001. 2797 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 2798 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 2799 and QSIG Objects", RFC 3204, December 2001. 2801 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2802 A., Peterson, J., Sparks, R., Handley, M., and E. 2803 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2804 June 2002. 2806 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 2807 Extensions to the Session Initiation Protocol (SIP) for 2808 Asserted Identity within Trusted Networks", RFC 3325, 2809 November 2002. 2811 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 2812 Extensions (MIME) Parameter", RFC 3459, January 2003. 2814 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2815 January 2004. 2817 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 2818 Format", RFC 4119, December 2005. 2820 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 2821 Registration Procedures", RFC 4288, December 2005. 2823 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2824 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2825 May 2008. 2827 [RFC5621] Camarillo, G., "Message Body Handling in the Session 2828 Initiation Protocol (SIP)", RFC 5621, September 2009. 2830 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 2831 August 2011. 2833 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 2834 6351, August 2011. 2836 11.2. Informational References 2838 [I-D.ietf-geopriv-relative-location] 2839 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 2840 Thomson, "Relative Location Representation", draft-ietf- 2841 geopriv-relative-location-08 (work in progress), September 2842 2013. 2844 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 2845 Emergency Context Resolution with Internet Technologies", 2846 RFC 5012, January 2008. 2848 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 2849 Format for Presence Information Data Format Location 2850 Object (PIDF-LO)", RFC 5139, February 2008. 2852 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 2853 Tschofenig, "LoST: A Location-to-Service Translation 2854 Protocol", RFC 5222, August 2008. 2856 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 2857 Presence Information Data Format Location Object (PIDF-LO) 2858 Usage Clarification, Considerations, and Recommendations", 2859 RFC 5491, March 2009. 2861 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 2862 Thomson, "Dynamic Extensions to the Presence Information 2863 Data Format Location Object (PIDF-LO)", RFC 5962, 2864 September 2010. 2866 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 2867 5985, September 2010. 2869 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 2870 "Framework for Emergency Calling Using Internet 2871 Multimedia", RFC 6443, December 2011. 2873 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 2874 R. George, "Specifying Civic Address Extensions in the 2875 Presence Information Data Format Location Object (PIDF- 2876 LO)", RFC 6848, January 2013. 2878 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 2879 Communications Services in Support of Emergency Calling", 2880 BCP 181, RFC 6881, March 2013. 2882 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 2883 Morris, J., Hansen, M., and R. Smith, "Privacy 2884 Considerations for Internet Protocols", RFC 6973, July 2885 2013. 2887 Appendix A. XML Schema for vCard/xCard 2889 This section contains the vCard/xCard XML schema version of the Relax 2890 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 2891 XML schemas defined in this document. The schema in RFC 6351 2892 [RFC6351] is the normative source and this section is informative 2893 only. 2895 2896 2900 2906 2907 2908 vCard Format Specification 2909 2910 2911 2912 2913 2914 2915 2916 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2931 2932 2933 2935 2936 2937 2938 2939 2941 2942 2943 2945 2946 2947 2948 2949 2951 2952 2953 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2998 3000 3001 3002 3006 3007 3008 Section 5: Parameters 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3934 3935 3936 3937 3938 3939 3940 3942 3943 3944 3945 3946 3947 3948 3950 3951 3952 3954 3956 3957 3958 3960 3961 3962 3963 3965 Authors' Addresses 3967 Brian Rosen 3968 NeuStar 3969 470 Conrad Dr. 3970 Mars, PA 16046 3971 US 3973 Phone: +1 724 382 1051 3974 Email: br@brianrosen.net 3976 Hannes Tschofenig 3977 Nokia Solutions and Networks 3978 Linnoitustie 6 3979 Espoo 02600 3980 Finland 3982 Phone: +358 (50) 4871445 3983 Email: Hannes.Tschofenig@gmx.net 3984 URI: http://www.tschofenig.priv.at 3986 Roger Marshall 3987 TeleCommunication Systems, Inc. 3988 2401 Elliott Avenue 3989 Seattle, WA 98121 3990 US 3992 Phone: +1 206 792 2424 3993 Email: rmarshall@telecomsys.com 3994 URI: http://www.telecomsys.com 3996 Randall Gellens 3997 Qualcomm Technologies, Inc. 3998 5775 Morehouse Drive 3999 San Diego, CA 92121 4000 US 4002 Email: rg+ietf@qti.qualcomm.com 4004 James Winterbottom 4005 AU 4007 Email: a.james.winterbottom@gmail.com