idnits 2.17.00 (12 Aug 2021) /tmp/idnits40995/draft-ietf-ecrit-additional-data-13.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 1820 has weird spacing: '...element name=...' == Line 2289 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 2289, but not defined == Unused Reference: 'RFC5985' is defined on line 2881, 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-13.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 . . . . . . . . . . . . . . . . . . . . . . . 27 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 . . . . . . . . . . . . . . . . . . . . . . . . . 36 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 . . . . . . . . . . . . . . . . . . . . 46 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 . . . . . . . . . . . . . 47 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 . . . . . . . . . . 48 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 . . . . 57 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 . . . . . . . . . . . . . . . . . . 59 159 9.7. VCard Parameter Value Registration . . . . . . . . . . . 60 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 provides useful information about the data 367 source. 369 3.1.3. Data Provider ID Series 371 Data Element: Data Provider ID Series 373 Use: Conditional. If Data Provider ID is provided, Data Provider ID 374 Series is required. 376 XML Element: 378 Description: Identifies the issuer of the ProviderId. A registry 379 will reflect the following valid entries: 381 * NENA 383 * EENA 385 Reason for Need: Identifies how to interpret the Data Provider ID. 387 How Used by Call Taker: Determines which provider ID registry to 388 consult for more information 390 3.1.4. Type of Data Provider 392 Data Element: Type of Data Provider ID 394 Use: Conditional. If Data Provider ID is provided, Type of Data 395 Provider ID is required. 397 XML Element: 399 Description: Identifies the type of data provider id being supplied 400 in the ProviderId data element. A registry with an initial set of 401 values is shown in Figure 1. 403 +------------------------------+------------------------------------+ 404 | Token | Description | 405 +------------------------------+------------------------------------+ 406 |Access Network Provider | Access network service provider | 407 |Service Provider | Calling or Origination telecom SP | 408 |Service Provider Subcontractor| A contractor to another kind of SP | 409 |Telematics Provider | A sensor based SP, especially | 410 | | vehicle based | 411 |Language Translation Provider | A spoken language translation SP | 412 |Emergency Service Provider | An emergency service provider | 413 | | conveying information to another | 414 | | emergency service provider. | 415 |Emergency Modality Translation| An emergency call specific | 416 | | modality translation service | 417 | | e.g., for sign language | 418 |Relay Provider | A interpretation SP, for example, | 419 | | video relay for sign language | 420 | | interpreting | 421 |Other | Any other type of service provider | 422 +------------------------------+------------------------------------+ 424 Figure 1: Type of Data Provider ID Registry. 426 Reason for Need: Identifies what kind of data provider this is. 428 How Used by Call Taker: To decide who to contact when further 429 information is needed 431 3.1.5. Data Provider Contact URI 432 Data Element: Data Provider Contact URI 434 Use: Required 436 XML Element: 438 Description: When provided by a service provider or an access 439 provider, this information MUST be a URI to a 24/7 support 440 organization tasked to provide PSAP support for this emergency 441 call. If the call is from a device, this would reflect the 442 contact information of the owner of the device. If a telephone 443 number is the contact address then it MUST be tel URI. If it is 444 provided as a SIP URI then it MUST be in the form of 445 sip:telephonenumber@serviceprovider:user=phone. 447 Reason for Need: Additional data providers may need to be contacted 448 for error or other unusual circumstances. 450 How Used by Call Taker: To contact the supplier of the additional 451 data for assistance in handling the call. 453 3.1.6. Data Provider Languages(s) Supported 455 Data Element: Data Provider Language(s) supported 457 Use: Conditional 459 XML Element: 461 Description: The language used by the entity at the Data Provider 462 Contact URI as an alpha 2-character code as defined in ISO 463 639-1:2002 Codes for the representation of names of languages -- 464 Part 1: Alpha-2 code Multiple instances of this element may occur. 465 Order is significant; preferred language should appear first. 466 This data is required if a Data Provider Contact URI is provided. 467 The content must reflect the languages supported at the contact 468 URI. 470 Reason for Need: Information needed to determine if emergency 471 service authority can communicate with the service provider or if 472 an interpreter will be needed. 474 How Used by Call Taker: If call taker cannot speak language(s) 475 supported by the service provider, a translation service will need 476 to be added to the conversation. 478 3.1.7. xCard of Data Provider 479 Data Element: xCard of Data Provider 481 Use: Optional 483 XML Element: 485 Description: There are many fields in the xCard and the creator of 486 the data structure is encouraged to provide as much information as 487 they have available. N, ORG, ADR, TEL, EMAIL are suggested at a 488 minimum. N should contain name of support group or device owner 489 as appropriate. If more than one TEL property is provided, a 490 parameter from the vCard Property Value registry MUST be specified 491 on each TEL. For encoding of the xCard this specification uses 492 the XML-based encoding specified in [RFC6351]. and is hereinafter 493 referred to as "xCard" 495 Reason for Need: Information needed to determine additional contact 496 information. 498 How Used by Call Taker: Assists call taker by providing additional 499 contact information that may not be included in the SIP invite or 500 the PIDF-LO. 502 3.1.8. Subcontractor Principal 504 Data Element: Subcontractor Principal 506 Use: Conditional. This data is required if the Data Provider type 507 is subcontractor. 509 XML Element: 511 Description: If the data provider is a subcontractor to another 512 provider, such as an access infrastructure provider or telematics 513 provider, this element contains the DataProviderString of the 514 service provider to indicate which provider the subcontractor is 515 working for. 517 Reason for Need: Identify the entity the subcontractor works for. 519 How Used by Call Taker: Allows the call taker to understand what the 520 relationship between data providers and the service providers in 521 the path of the call are. 523 3.1.9. Subcontractor Priority 525 Data Element: Subcontractor Priority 526 Use: Conditional 528 XML Element: 530 Description: If the subcontractor should be contacted first, this 531 element should have a "sub" value. If the access or origination 532 service provider should be contacted first, this element should 533 have a "main" value. This data is required if the Data Provider 534 type is "subcontractor". 536 Reason for Need: Inform the call taker whether the network operator 537 or the subcontractor should be contacted first if support is 538 needed. 540 How Used by Call Taker: To decide which entity to contact first if 541 assistance is needed. 543 3.1.10. emergencyCall.ProviderInfo Example 545 546 549 Example VoIP Provider 550 551 urn:nena:companyid:ID123 552 NENA 553 Service Provider 554 sip:voip-provider@example.com 555 EN 556 558 559 Hannes Tschofenig 560 561 Hannes 562 Tschofenig 563 564 565 Dipl. Ing. 566 567 --0203 568 569 20090808T1430-0500 570 571 M 572 573 1 574 575 de 576 577 578 2 579 580 en 581 582 583 work 584 585 Example VoIP Provider 586 587 588 589 work 590 594 595 596 597 Linnoitustie 6 598 Espoo 599 Uusimaa 600 02600 601 Finland 602 603 604 605 606 work 607 voice 608 609 610 tel:+358 50 4871445 611 612 613 work 614 615 hannes.tschofenig@nsn.com 616 617 618 work 619 620 geo:60.210796,24.812924 622 623 624 home 625 626 627 http://www.tschofenig.priv.at/key.asc 628 629 630 Finland/Helsinki 631 632 home 633 634 http://www.tschofenig.priv.at 635 636 637 638 640 Figure 2: emergencyCall.ProviderInfo Example. 642 3.2. Service Information 644 This block describes the service that the service provider provides 645 to the caller. It SHOULD be included by all SPs in the path of the 646 call. The mime subtype is "application/emergencyCall.SvcInfo+xml". 648 3.2.1. Service Environment 650 Data Element: Service Environment 652 Use: Required 654 XML Element: 656 Description: This element defines whether a call is from a business 657 or residence caller. Currently, the only valid entries are 658 'Business' or 'Residence'. 660 Reason for Need: To assist in determining equipment and manpower 661 requirements. 663 How Used by Call Taker: Information may be used to assist in 664 determining equipment and manpower requirements for emergency 665 responders. As the information is not always available, and the 666 registry is not all encompassing, this is at best advisory 667 information, but since it mimics a similar capability in some 668 current emergency calling systems, it is known to be valuable. 669 The service provider uses its best information (such as a rate 670 plan, facilities used to deliver service or service description) 671 to determine the information and is not responsible for 672 determining the actual characteristics of the location where the 673 call originates from. 675 3.2.2. Service Delivered by Provider to End User 677 Data Element: Service Delivered by Provider to End User 679 Use: Required 681 XML Element: 683 Description: This defines the type of service the end user has 684 subscribed to. The implied mobility of this service cannot be 685 relied upon. A registry with an initial set of values is defined 686 in Figure 3. 688 +--------+----------------------------------------+ 689 | Name | Description | 690 +--------+----------------------------------------+ 691 | Wrless | Wireless Telephone Service: Includes | 692 | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | 693 | | LTE (Long Term Evolution) | 694 | Coin | Fixed Public Pay/Coin telephones: Any | 695 | | coin or credit card operated device | 696 | 1way | One way outbound service | 697 | Prison | Inmate call/service | 698 | Temp | Soft dialtone/quick service/warm | 699 | | disconnect/suspended | 700 | MLTS | Multi-line telephone system: Includes | 701 | | all PBX, Centrex, key systems, | 702 | | Shared Tenant Service | 703 | SenseU | Sensor, unattended: Includes devices | 704 | | that generate DATA ONLY. This is | 705 | | one-way information exchange and | 706 | | there will be no other form of | 707 | | communication | 708 | SenseA | Sensor, attended: Includes devices | 709 | | that are supported by a monitoring | 710 | | service provider or automatically | 711 | | open a two-way communication path | 712 | POTS | Wireline: Plain Old Telephone Service | 713 | VOIP | VoIP Telephone Service: A type of | 714 | | service that offers communication | 715 | | over internet protocol, such as Fixed| 716 | | Nomadic, Mobile, ... | 717 | Remote | Off premise extension | 718 | Relay | Relay Service: a type of service where | 719 | | there is a human 3rd party agent who | 720 | | provides some kind of additional | 721 | | assistance to the caller. Includes | 722 | | sign language relay and telematics | 723 | | services which provide a service | 724 | | assistant on the call. | 725 +--------+----------------------------------------+ 727 Figure 3: Service Delivered by Provider to End User Registry. 729 More than one value MAY be returned. For example, a VoIP inmate 730 telephone service is a reasonable combination. 732 Reason for Need: Knowing the type of service may assist the PSAP 733 with the handling of the call. 735 How Used by Call Taker: Call takers often use this information to 736 determine what kinds of questions to ask callers, and how much to 737 rely on supportive information. An emergency call from a prison 738 is treated differently that a call from a sensor device. As the 739 information is not always available, and the registry is not all 740 encompassing, this is at best advisory information, but since it 741 mimics a similar capability in some current emergency calling 742 systems, it is known to be valuable. 744 3.2.3. Service Mobility Environment 746 Data Element: Service Mobility Environment 748 Use: Required 750 XML Element: 752 Description: This provides the service providers view of the 753 mobility of the caller. As the service provider may not know the 754 characteristics of the actual access network used, the value not 755 be relied upon. A registry will reflect the following initial 756 valid entries: 758 * Mobile: the device should be able to move at any time 760 * Fixed: the device is not expected to move unless the service is 761 relocated 763 * Nomadic: the device is not expected to change its point of 764 attachment while on a call 766 * Unknown: no information is known about the service mobility 767 environment for the device 769 Reason for Need: Knowing the service provider's belief of mobility 770 may assist the PSAP with the handling of the call. 772 How Used by Call Taker: To determine whether to assume the location 773 of the caller might change. 775 3.2.4. emergencyCall.SvcInfo Example 777 778 781 Business 782 MLTS 783 Fixed 784 786 Figure 4: emergencyCall.SvcInfo Example. 788 3.3. Device Information 790 This block provides information about the device used to place the 791 call. It should be provided by any service provider that knows what 792 device is being used, and by the device itself. The mime subtype is 793 "application/emergencyCall.DevInfo+xml". 795 3.3.1. Device Classification 797 Data Element: Device Classification 799 Use: Optional 801 XML Element: 803 Description: This data element defines the kind of device making the 804 emergency call. If the device provides the data structure, the 805 device information SHOULD be provided. If the service provider 806 provides the structure and it knows what the device is, the 807 service provider SHOULD provide the device information. Often the 808 carrier does not know what the device is. It is possible to 809 receive two Additional Data Associated with a Call data 810 structures, one created by the device and one created by the 811 service provider. This information describes the device, not how 812 it is being used. This data element defines the kind of device 813 making the emergency call. The registry with the initial set of 814 values is shown in Figure 5. 816 +--------+----------------------------------------+ 817 | Token | Description | 818 +--------+----------------------------------------+ 819 |Cordless| Cordless handset | 820 | Fixed | Fixed phone | 821 | Mobile | Mobile handset | 822 | ATA | analog terminal adapter | 823 |Satphone| Satellite phone | 824 | FSense | Stationary computing device (alarm | 825 | | system, data sensor) | 826 | Guard | Guardian devices | 827 | Desktop| Desktop PC | 828 | Laptop | Laptop computing device | 829 | Tablet | Tablet computing device | 830 | Alarm | Alarm system | 831 | MSense | Mobile Data sensor | 832 | Beacon | Personal beacons (spot) | 833 | Auto | Auto telematics | 834 | Truck | Truck telematics | 835 | Farm | Farm equipment telematics | 836 | Marine | Marine telematics | 837 | PDA | Personal digital assistant | 838 | PND | Personal navigation device) | 839 | SmrtPhn| Smart phone | 840 | Itab | Internet tablet | 841 | Game | Gaming console | 842 | Video | Video phone | 843 | Text | Other text device | 844 |SoftPhn | Soft phone or soft client software | 845 | NA | Not Available | 846 +--------+----------------------------------------+ 848 Figure 5: Device Classification Registry. 850 Reason for Need: The device classification implies the capability of 851 the calling device and assists in identifying the meaning of the 852 emergency call location information that is being presented. For 853 example, does the device require human intervention to initiate a 854 call or is this call the result of programmed instructions? Does 855 the calling device have the ability to update location or 856 condition changes? Is this device interactive or a one-way 857 reporting device? 859 How Used by Call Taker: May assist with location of caller. For 860 example, a cordless handset may be outside or next door. May 861 provide the calltaker some context about the caller, the 862 capabilities of the device used for the call or the environment 863 the device is being used in. 865 3.3.2. Device Manufacturer 867 Data Element: Device Manufacturer 869 Use: Optional 871 XML Element: 873 Description: The plain language name of the manufacturer of the 874 device. 876 Reason for Need: Used by PSAP management for post-mortem 877 investigation/resolution. 879 How Used by Call Taker: Probably not used by the calltaker, but by 880 PSAP management. 882 3.3.3. Device Model Number 884 Data Element: Device Model Number 886 Use: Optional 888 XML Element: 890 Description: Model number of the device. 892 Reason for Need: Used by PSAP management for after action 893 investigation/resolution. 895 How Used by Call Taker: Probably not used by the calltaker, but by 896 PSAP management. 898 3.3.4. Unique Device Identifier 900 Data Element: Unique Device Identifier 902 Use: Optional 904 XML Element: 906 Description: String that identifies the specific device making the 907 call or creating an event. 909 Reason for Need: Uniquely identifies the device as opposed to any 910 signaling identifiers encountered in the call signaling stream. 912 How Used by Call Taker: Probably not used by the calltaker; they 913 would need to refer to management for investigation. 915 3.3.5. Type of Device Identifier 917 Data Element: Type of Device Identifier 919 Use: Conditional: must be provided if the DeviceID is provided 921 XML Element: 923 Description: Identifies the type of device identifier being 924 generated in the unique device identifier data element. A 925 registry with an initial set of values can be seen in Figure 6. 927 +--------+----------------------------------------+ 928 | Token | Description | 929 +--------+----------------------------------------+ 930 | MEID | Mobile Equipment Identifier (CDMA) | 931 | ESN | Electronic Serial Number(GSM) | 932 | MAC | Media Access Control Address (IEEE) | 933 | WiMAX | Device Certificate Unique ID | 934 | IMEI | International Mobile Equipment ID (GSM)| 935 | UDI | Unique Device Identifier | 936 | RFID | Radio Frequency Identification | 937 | SN | Manufacturer Serial Number | 938 +--------+----------------------------------------+ 940 Figure 6: Registry with Device Identifier Types. 942 Reason for Need: Identifies how to interpret the Unique Device 943 Identifier. 945 How Used by Call Taker: Additional information that may be used to 946 assist with call handling. 948 3.3.6. Device/Service Specific Additional Data Structure 950 Data Element: Device/service specific additional data structure 952 Use: Optional 954 XML Element: 955 Description: A URI representing additional data whose schema is 956 specific to the device or service which created it. An example is 957 the VEDs structure for a vehicle telematics device. The URI, when 958 dereferenced, MUST yield a data structure defined by the Device/ 959 service specific additional data type value. Different data may 960 be created by each classification; e.g., telematics creates VEDS 961 data set. 963 Reason for Need: Provides device/service specific data that may be 964 used by the call taker and/or responders. 966 How Used by Call Taker: Provide information to guide call takers to 967 select appropriate responders, give appropriate pre-arrival 968 instructions to callers, and advise responders of what to be 969 prepared for. May be used by responders to guide assistance 970 provided. 972 3.3.7. Device/Service Specific Additional Data Structure Type 974 Data Element: Type of device/service specific additional data 975 structure 977 Use: Conditional. MUST be provided when device/service specific 978 additional URI is provided 980 XML Element: 982 Description: Value from a registry defined by this document to 983 describe the type of data that can be retrieved from the device/ 984 service specific additional data structure. Initial values are: 986 * IEEE 1512 988 * VEDS 990 IEEE 1512 is the USDoT model for traffic incidents and Vehicular 991 Emergency Data Set (VEDS) provides data elements needed for an 992 efficient emergency response to vehicular emergency incidents. 994 Reason for Need: This data element allows identification of 995 externally defined schemas, which may have additional data that 996 may assist in emergency response. 998 How Used by Call Taker: This data element allows the end user 999 (calltaker or first responder) to know what type of additional 1000 data may be available to aid in providing the needed emergency 1001 services. 1003 Note: Information which is specific to a location or a caller 1004 (person) should not be placed in this section. 1006 3.3.8. Choosing between defining a new type of block or new type of 1007 device/service specific additional data 1009 For devices that have device or service specific data, there are two 1010 choices to carry it. A new block can be defined, or the device/ 1011 service specific additional data URL the DevInfo block can be used 1012 and a new type for it defined . The data passed would likely be the 1013 same in both cases. Considerations for choosing which mechanism to 1014 register under include: 1016 Applicability: Information which will be carried by many kinds of 1017 devices or services are more appropriately defined as separate 1018 blocks. 1020 Privacy: Information which may contain private data may be better 1021 sent in the DevInfo block, rather than a new block so that 1022 implementations are not tempted to send the data by value, and 1023 thus having more exposure to the data than forcing the data to be 1024 retrieved via the URL in DevInfo. 1026 Size: Information which may be very may be better sent in the 1027 DevInfo block, rather than a new block so that implementations are 1028 not tempted to send the data by value. Conversely, data which is 1029 small may best be sent in a separate block so that it can be sent 1030 by value 1032 Availability of a server: Providing the data via the device block 1033 requires a server be made available to retrieve the data. 1034 Providing the data via new block allows it to be sent by value 1035 (CID). 1037 3.3.9. emergencyCall.DevInfo Example 1038 1039 1042 Fixed phone 1043 Nokia 1044 Lumia 800 1045 35788104 1046 IMEI 1047 1049 Figure 7: emergencyCallDevInfo Example. 1051 3.4. Owner/Subscriber Information 1053 This block describes the owner of the device (if provided by the 1054 device) or the subscriber information, if provided by a service 1055 provider. The contact location is not necessarily the location of 1056 the caller or incident, but is rather the nominal contact address. 1057 The mime subtype is "application/emergencyCall.Subscriber+xml". 1059 In some jurisdictions some or all parts of the subscriber-specific 1060 information are subject to privacy constraints. These constraints 1061 vary but dictate what information and be displayed and logged. A 1062 general privacy indicator expressing a desire for privacy is 1063 provided. The interpretation of how this is applied is left to the 1064 receiving jurisdiction as the custodians of the local regulatory 1065 requirements. 1067 3.4.1. Subscriber Data Privacy Indicator 1069 Attribute: privacyRequested, boolean. 1071 Use: Conditional. This attribute MUST be provided if the owner/ 1072 subscriber information block is not empty. 1074 Description: The subscriber data privacy indicator specifically 1075 expresses the subscriber's desire for privacy. In some 1076 jurisdictions subscriber services can have a specific "Type of 1077 Service" which prohibits information, such as the name of the 1078 subscriber, from being displayed. This attribute should be used 1079 to explicitly indicate whether the subscriber service includes 1080 such constraints. 1082 Reason for Need: Some jurisdictions require subscriber privacy to be 1083 observed. 1085 How Used by Call Taker: Where privacy is indicated the call taker 1086 may not have access to some aspects of the subscriber information. 1088 3.4.2. xCard for Subscriber's Data 1090 Data Element: xCARD for Subscriber's Data 1092 Use: Conditional. Subscriber data is provided unless it is not 1093 available. Some services, for example prepaid phones, non- 1094 initialized phones, etc., do not have information about the 1095 subscriber. 1097 XML Element: 1099 Description: Information known by the service provider or device 1100 about the subscriber; e.g., Name, Address, Individual Telephone 1101 Number, Main Telephone Number and any other data. N, ORG (if 1102 appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more 1103 than one TEL property is provided, a parameter from the vCard 1104 Property Value registry MUST be specified on each TEL. 1106 Reason for Need: When the caller is unable to provide information, 1107 this data may be used to obtain it 1109 How Used by Call Taker: Obtaining critical information about the 1110 caller and possibly the location when it is not able to be 1111 obtained otherwise. 1113 3.4.3. emergencyCall.SubInfo Example 1115 1116 1120 1121 1122 1123 Simon Perreault 1124 1125 Perreault 1126 Simon 1127 1128 1129 ing. jr 1130 M.Sc. 1131 1132 --0203 1133 1134 20090808T1430-0500 1135 1136 M 1137 1138 1 1139 1140 fr 1141 1142 1143 2 1144 1145 en 1146 1147 1148 work 1149 1150 Viagenie 1151 1152 1153 1154 work 1155 1159 1160 1161 1162 2875 boul. Laurier, suite D2-630 1163 Quebec 1164 QC 1165 G1V 2M2 1166 Canada 1167 1168 1169 1170 1171 work 1172 voice 1173 1174 1175 tel:+1-418-656-9254;ext=102 1176 1177 1178 1179 1180 work 1181 text 1182 voice 1183 cell 1184 video 1185 1186 1187 tel:+1-418-262-6501 1188 1189 1190 work 1191 1192 simon.perreault@viagenie.ca 1193 1194 1195 work 1196 1197 geo:46.766336,-71.28955 1198 1199 1200 work 1201 1202 1203 http://www.viagenie.ca/simon.perreault/simon.asc 1204 1205 1206 America/Montreal 1207 1208 home 1209 1210 http://nomis80.org 1211 1212 1213 1214 1215 1217 Figure 8: emergencyCall.SubInfo Example. 1219 3.5. Comment 1221 This block provides a mechanism for the data provider to supply 1222 extra, human readable information to the PSAP. It is not intended 1223 for a general purpose extension mechanism nor does it aim to provide 1224 machine-reable content. The mime subtype is "application/ 1225 emergencyCall.Comment+xml" 1227 3.5.1. Comment 1229 Data Element: EmergencyCall.Comment 1231 Use: Optional 1233 XML Element: 1235 Description: Human readable text providing additional information to 1236 the PSAP staff. 1238 Reason for Need: Explanatory information for values in the data 1239 structure 1241 How Used by Call Taker: To interpret the data provided 1243 3.5.2. emergencyCall.Comment Example 1245 1246 1249 This is an example text. 1250 1252 Figure 9: EmergencyCall.Comment Example. 1254 4. Transport 1256 This section defines how to convey additional data to an emergency 1257 service provider. Two different means are specified: the first uses 1258 the call signaling; the second uses the element of a 1259 PIDF-LO [RFC4119]. 1261 1. First, the ability to embed a Uniform Resource Identifier (URI) 1262 in an existing SIP header field, the Call-Info header, is 1263 defined. The URI points to the additional data structure. The 1264 Call-Info header is specified in Section 20.9 of [RFC3261]. This 1265 document adds a new compound token starting with the value 1266 'emergencyCallData' for the Call-Info "purpose" parameter. If 1267 the "purpose" parameter is set to a value starting with 1268 'emergencyCallData', then the Call-Info header contains either an 1269 HTTPS URL pointing to an external resource or a CID (content 1270 indirection) URI that allows the data structure to be placed in 1271 the body of the SIP message. The "purpose" parameter also 1272 indicates the kind of data (by its MIME type) that is available 1273 at the URI. As the data is conveyed using a URI in the SIP 1274 signaling, the data itself may reside on an external resource, or 1275 may be contained within the body of the SIP message. When the 1276 URI refers to data at an external resource, the data is said to 1277 be passed by reference. When the URI refers to data contained 1278 within the body of the SIP message, the data is said to be passed 1279 by value. A PSAP or emergency responder is able to examine the 1280 type of data provided and selectively inspect the data it is 1281 interested in, while forwarding all of it (the values or 1282 references) to downstream entities. To be conveyed in a SIP 1283 body, additional data about a call is defined as a series of MIME 1284 objects. Each block defined in this document is an XML data 1285 structure identified by its MIME type. (Blocks defined by others 1286 may be encoded in XML or not, as identified by their MIME 1287 registration.) As usual, whenever more than one MIME part is 1288 included in the body of a message, MIME-multipart (i.e., 1289 'multipart/mixed') encloses them all. This document defines a 1290 set of XML schemas and MIME types used for each block defined 1291 here. When additional data is passed by value in the SIP 1292 signaling, each CID URL points to one block in the body. 1293 Multiple URIs are used within a Call-Info header field (or 1294 multiple Call-Info header fields) to point to multiple blocks. 1295 When additional data is provided by reference (in SIP signaling 1296 or Provided-By), each HTTPS URL references one block; the data is 1297 retrieved with an HTTPS GET operation, which returns one of the 1298 blocks as an object (the blocks defined here are returned as XML 1299 objects). 1301 2. Second, the ability to embed additional data structures in the 1302 element of a PIDF-LO [RFC4119] is defined. Besides 1303 a service provider in the call path, the access network provider 1304 may also have similar information that may be valuable to the 1305 PSAP. The access network provider may provide location in the 1306 form of a PIDF-LO from a location server via a location 1307 configuration protocol. The data structures described in this 1308 document are not specific to the location itself, but rather 1309 provides descriptive information having to do with the immediate 1310 circumstances about the provision of the location (who the access 1311 network is, how to contact that entity, what kind of service the 1312 access network provides, subscriber information, etc.). This 1313 data is similar in nearly every respect to the data known by 1314 service providers in the path of the call. When the access 1315 network provider and service provider are separate entities, the 1316 access network does not participate in the application layer 1317 signaling (and hence cannot add a Call-Info header field to the 1318 SIP message), but may provide location information to assist in 1319 locating the caller's device. The element of the 1320 PIDF-LO is a mechanism for the access network provider to supply 1321 the information about the entity or organization that supplied 1322 this location information. For this reason, this document 1323 describes a namespace per RFC 4119 for inclusion in the 1324 element of a PIDF-LO for adding information known 1325 to the access network provider. 1327 One or more blocks of data registered in the Emergency Call 1328 Additional Data registry, as defined in Section 9.1, may be included 1329 or referenced in the SIP signaling (using the Call-Info header field) 1330 or in the element of a PIDF-LO. Every block must be 1331 one of the types in the registry. Since the data of an emergency 1332 call may come from multiple sources, the data itself needs 1333 information describing the source. Consequently, each entity adding 1334 additional data MUST supply the "Data Provider" block. All other 1335 blocks are optional, but each entity SHOULD supply any blocks where 1336 it has at least some of the information in the block. 1338 4.1. Transmitting Blocks using the Call-Info Header 1340 A URI to a block MAY be inserted in a SIP request or response method 1341 (most often INVITE or MESSAGE) with a Call-Info header field 1342 containing a purpose value starting with 'emergencyCallData' and the 1343 type of data available at the URI. The type of data is denoted by 1344 including the root of the MIME type (not including the 1345 'emergencyCall' prefix and any suffix such as '+xml') with a '.' 1346 separator. For example, when referencing a block with MIME type 1347 'application/emergencyCall.ProviderInfo+xml', the 'purpose' parameter 1348 is set to 'emergencyCallData.ProviderInfo'. An example "Call-Info" 1349 header field for this would be: 1351 Call-Info: https://www.example.com/23sedde3; 1352 purpose="emergencyCallData.ProviderInfo" 1354 A Call-info header with a purpose value starting with 1355 'emergencyCallData' MUST only be sent on an emergency call, which can 1356 be ascertained by the presence of an emergency service urn in a Route 1357 header of a SIP message. 1359 If the data is provided by reference, an HTTPS URI MUST be included 1360 and consequently Transport Layer Security (TLS) protection is applied 1361 for protecting the retrieval of the information. 1363 The data may also be supplied by value in a SIP message. In this 1364 case, Content Indirection (CID) [RFC2392] is used, with the CID URL 1365 referencing the MIME body part. 1367 More than one Call-Info header with a purpose value starting with 1368 'emergencyCallData' can be expected, but at least one MUST be 1369 provided. The device MUST provide one if it knows no service 1370 provider is in the path of the call. The device MAY insert one if it 1371 uses a service provider. Any service provider in the path of the 1372 call MUST insert its own. For example, a device, a telematics 1373 service provider in the call path, as well as the mobile carrier 1374 handling the call will each provide one. There may be circumstances 1375 where there is a service provider who is unaware that the call is an 1376 emergency call and cannot reasonably be expected to determine that it 1377 is an emergency call. In that case, that service provider is not 1378 expected to provide emergencyCallData. 1380 4.2. Transmitting Blocks by Reference using the Provided-By Element 1382 The 'emergencyCallDataReference' element is used to transmit an 1383 additional data block by reference within a 'Provided-By' element of 1384 a PIDF-LO. The 'emergencyCallDataReference' element has two 1385 attributes: 'ref' to specify the URL, and 'purpose' to indicate the 1386 type of data block referenced. The value of 'ref' is an HTTPS URL 1387 that resolves to a data structure with information about the call. 1388 The value of 'purpose' is the same as used in a 'Call-Info' header 1389 field (as specified in Section 4.1). 1391 For example, to reference a block with MIME type 'application/ 1392 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to 1393 'emergencyCallData.ProviderInfo'. An example 1394 'emergencyCallDataReference' element for this would be: 1396 1399 4.3. Transmitting Blocks by Value using the Provided-By Element 1401 It is RECOMMENDED that access networks supply the data specified in 1402 this document by reference, but they MAY provide the data by value. 1404 The 'emergencyCallDataValue' element is used to transmit an 1405 additional data block by value within a 'Provided-By' element of a 1406 PIDF-LO. The 'emergencyCallDataValue' element has one attribute: 1407 'purpose' to indicate the type of data block contained. The value of 1408 'purpose' is the same as used in a 'Call-Info' header field (as 1409 specified in Section 4.1, and in Section 4.1). The same XML 1410 structure as would be contained in the corresponding MIME type body 1411 part is placed inside the 'emergencyCallDataValue' element. 1413 For example: 1415 1417 1418 1420 1422 This is an example text. 1423 1424 1425 1426 1428 Test 1429 NENA 1430 Access Infrastructure Provider 1431 1432 sip:15555550987@burf.example.com;user=phone 1433 1434 1435 1437 Example Provided-By by Value. 1439 4.4. The Content-Disposition Parameter 1441 RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. 1442 It updates and clarifies handling originally defined in RFC 3261 1443 [RFC3261] based on implementation experience. While RFC 3261 did not 1444 mandate support for 'multipart' message bodies 'multipart/mixed' MIME 1445 bodies are, however, used by many extensions (including additional 1446 data) today. For example, adding a PIDF-LO, SDP, and additional data 1447 in body of a SIP message requires a 'multipart' message body. 1449 RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' 1450 parameter for the Content-Disposition header field. These RFCs 1451 describe how a UAS reacts if it receives a message body whose content 1452 type or disposition type it does not understand. If the 'handling' 1453 parameter has the value "optional", the UAS ignores the message body. 1454 If the 'handling' parameter has the value "required", the UAS returns 1455 a 415 (Unsupported Media Type) response. The 'by-reference' 1456 disposition type allows a SIP message to contain a reference to the 1457 body part, and the SIP UA processes the body part according to the 1458 reference. This is the case for the Call-info header containing a 1459 Content Indirection (CID) URL. 1461 As an example, a SIP message indicates the Content-Disposition 1462 parameter in the body of the SIP message as shown in Figure 10. 1464 Content-Type: application/sdp 1466 ...Omit Content-Disposition here; defaults are ok 1467 ...SDP goes here 1469 --boundary1 1471 Content-Type: application/pidf+xml 1472 Content-ID: 1473 Content-Disposition: by-reference;handling=optional 1475 ...PIDF-LO goes here 1477 --boundary1-- 1479 Content-Type: application/emergencyCall.ProviderInfo+xml 1480 Content-ID: <1234567890@atlanta.example.com> 1481 Content-Disposition: by-reference;handling=optional 1483 ...Additional data goes here 1485 --boundary1-- 1487 Figure 10: Example for use of the Content-Disposition Parameter in 1488 SIP. 1490 5. Examples 1492 This section provides three examples of communicating additional 1493 data. In Figure 11 additional data is communicated in a SIP INVITE 1494 per value. In Figure 12 we illustrate how additional data is added 1495 by a SIP proxy per reference. Finally, an example for including 1496 additional data in the element of a PIDF-LO is 1497 illustrated. 1499 INVITE sips:bob@biloxi.example.com SIP/2.0 1500 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1501 Max-Forwards: 70 1502 To: Bob 1503 From: Alice ;tag=9fxced76sl 1504 Call-ID: 3848276298220188511@atlanta.example.com 1505 Call-Info: ;purpose=icon, 1506 ;purpose=info, 1507 1508 ;purpose=emergencyCallData.ProviderInfo 1509 Geolocation: 1510 Geolocation-Routing: no 1511 Accept: application/sdp, application/pidf+xml, 1512 application/emergencyCallProviderinfo+xml 1513 CSeq: 31862 INVITE 1514 Contact: 1515 Content-Type: multipart/mixed; boundary=boundary1 1517 Content-Length: ... 1519 --boundary1 1521 Content-Type: application/sdp 1523 ...SDP goes here 1525 --boundary1 1527 Content-Type: application/pidf+xml 1528 Content-ID: 1529 Content-Disposition: by-reference;handling=optional 1531 ...PIDF-LO goes here 1533 --boundary1-- 1535 Content-Type: application/emergencyCall.ProviderInfo+xml 1536 Content-ID: <1234567890@atlanta.example.com> 1537 Content-Disposition: by-reference;handling=optional 1539 ...Additional data goes here 1541 --boundary1-- 1543 Figure 11: Example: Attaching Additional Data via CID to a SIP 1544 INVITE. 1546 INVITE sips:bob@biloxi.example.com SIP/2.0 1547 Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9 1548 Max-Forwards: 70 1549 To: Bob 1550 From: Alice ;tag=9fxced76sl 1551 Call-ID: 3848276298220188511@atlanta.example.com 1552 Call-Info: ;purpose=icon, 1553 ;purpose=info, 1554 1555 ;purpose=emergencyCallData.ProviderInfo 1556 Geolocation: 1557 Geolocation-Routing: no 1558 Accept: application/sdp, application/pidf+xml, 1559 application/emergencyCallProviderinfo+xml 1560 CSeq: 31862 INVITE 1561 Contact: 1562 Content-Type: multipart/mixed; boundary=boundary1 1564 Content-Length: ... 1566 --boundary1 1568 Content-Type: application/sdp 1570 ...SDP goes here 1572 --boundary1 1574 Content-Type: application/pidf+xml 1575 Content-ID: 1576 Content-Disposition: by-reference;handling=optional 1578 ...PIDF-LO goes here 1580 --boundary1-- 1582 Figure 12: Example: Attaching Additional Data per Reference in a SIP 1583 INVITE. 1585 1586 1591 1592 1593 1594 1596 AU 1597 NSW 1598 Wollongong 1599 North Wollongong 1600 Flinders 1601 Street 1602 Campbell Street 1603 Gilligan's Island 1604 Corner 1605 Video Rental Store 1606 2500 1607 Westerns and Classics 1608 store 1609 Private Box 15 1610 1611 1612 1613 true 1614 1615 2013-07-10T20:00:00Z 1616 1617 1618 802.11 1619 1622 1625 1626 1628 University of California, Irvine 1629 1630 urn:nena:companyid:uci 1631 NENA 1632 Other 1633 tel:+1 9498245222 1634 EN 1635 1637 1639 This is an example text. 1640 1642 1643 1644 1645 mac:1234567890ab 1646 2013-07-09T20:57:29Z 1647 1648 1649 Figure 13: Example: Including Additional Data via the Provided-By 1650 Element in a PIDF-LO. 1652 6. XML Schemas 1654 This section defines the XML schemas of the five data blocks. 1655 Additionally, the Provided-By schema is specified. 1657 6.1. emergencyCall.ProviderInfo XML Schema 1659 1660 1669 1672 1674 1675 1676 1677 1678 1680 1684 1685 1686 1687 1688 1689 1691 1692 1693 1695 1697 1699 1701 1703 1705 1708 1710 1713 1715 1716 1718 1720 Figure 14: emergencyCall.ProviderInfo XML Schema. 1722 6.2. emergencyCall.SvcInfo XML Schema 1724 1725 1732 1735 1737 1738 1739 1741 1744 1746 1749 1751 1752 1754 1756 Figure 15: emergencyCall.SvcInfo XML Schema. 1758 6.3. emergencyCall.DevInfo XML Schema 1760 1761 1768 1771 1773 1774 1775 1777 1779 1781 1783 1785 1787 1790 1792 1793 1795 1797 Figure 16: emergencyCall.DevInfo XML Schema. 1799 6.4. emergencyCall.SubInfo XML Schema 1801 1802 1810 1813 1815 1817 1818 1819 1820 1823 1825 1826 1827 1828 1830 1832 Figure 17: emergencyCall.SubInfo XML Schema. 1834 6.5. emergencyCall.Comment XML Schema 1836 1837 1844 1847 1849 1850 1851 1854 1856 1857 1859 1860 1861 1862 1863 1864 1865 1867 1869 Figure 18: EmergencyCall.Comment XML Schema. 1871 6.6. Provided-By XML Schema 1873 This section defines the Provided-By schema. 1875 1876 1889 1890 1891 1892 1893 1895 1897 1898 1900 1904 1908 1911 1913 1915 1917 1918 1919 1920 1921 1923 1924 1926 1928 1929 1930 1931 1933 1934 1935 1938 1941 1944 1947 1951 1954 1955 1957 1959 Figure 19: Provided-By XML Schema. 1961 7. Security Considerations 1963 The information in this data structure will usually be considered 1964 private. HTTPS is specified to require the provider of the 1965 information to validate the credentials of the requester. While the 1966 creation of a PKI that has global scope may be difficult, the 1967 alternatives to creating devices and services that can provide 1968 critical information securely are more daunting. The provider may 1969 enforce any policy it wishes to use, but PSAPs and responder agencies 1970 should deploy a PKI so that providers of additional data can check 1971 the certificate of the client and decide the appropriate policy to 1972 enforce based on that certificate. 1974 Ideally, the PSAP and emergency responders will be given credentials 1975 signed by an authority trusted by the data provider. In most 1976 circumstances, nationally recognized credentials would be sufficient, 1977 and if the emergency services arranges a PKI, data providers could be 1978 provisioned with the root CA public key for a given nation. Some 1979 nations are developing a PKI for this, and related, purposes. Since 1980 calls could be made from devices where the device and/or the service 1981 provider(s) are not local to the emergency authorities, globally 1982 recognized credentials are useful. This might be accomplished by 1983 extending the notion of the "forest guide" described in [RFC5222] to 1984 allow the forest guide to provide the credential of the PKI root for 1985 areas that it has coverage information for, but standards for such a 1986 mechanism are not yet available. In its absence, the data provider 1987 will need to obtain the root CA credentials for any areas it is 1988 willing to provide additional data by out of band means. With the 1989 credential of the root CA for a national emergency services PKI, the 1990 data provider server can validate the credentials of an entity 1991 requesting additional data by reference. 1993 The data provider also needs a credential that can be verified by the 1994 emergency services to know that it is receiving data from the right 1995 server. The emergency authorities could provide credentials, 1996 distinguishable from credentials it provides to emergency responders 1997 and PSAPs, which could be used to validate data providers. Such 1998 credentials would have to be acceptable to any PSAP or responder that 1999 could receive a call with additional data supplied by that provider. 2000 This would be extensible to global credential validation using the 2001 forest guide as above. In the absence of such credentials, the 2002 emergency authorities could maintain a list of local data providers' 2003 credentials provided to it out of band. At a minimum, the emergency 2004 authorities could obtain a credential from the DNS entry of the 2005 domain in the Additional Data URI to at least validate that the 2006 server is known to the domain providing the URI. 2008 Data provided by devices by reference have similar credential 2009 validation issues to service providers, and the solutions are the 2010 same. 2012 8. Privacy Considerations 2014 This document enables functionality for conveying additional 2015 information about the caller to the callee. Some of this information 2016 is personal data and therefore privacy concerns arise. An explicit 2017 privacy indicator for information directly relating to the callers 2018 identity is defined and use is mandatory. However, observance of 2019 this request for privacy and what information it relates to is 2020 controlled by the destination jurisdiction. 2022 There are a number of privacy concerns with regular real-time 2023 communication services that are also applicable to emergency calling. 2024 Data protection regulation world-wide has, however, decided to create 2025 exceptions for emergency services since the drawbacks of disclosing 2026 personal data in comparison to the benefit for the emergency caller 2027 are often towards the latter. Hence, the data protection rights of 2028 individuals are often waived for emergency situations. There are, 2029 however, still various countries that offer some degree of anonymity 2030 for the caller towards PSAP call takers. 2032 The functionality defined in this document, however, far exceeds the 2033 amount of information sharing found in the Plain old telephone system 2034 (POTS). For this reason there are additional privacy threats to 2035 consider, which are described in more detail in [RFC6973]. 2037 Stored Data Compromise: First, there is an increased risk of stored 2038 data compromise since additional data is collected and stored in 2039 databases. Without adequate measures to secure stored data from 2040 unauthorized or inappropriate access at access network operators, 2041 service providers, end devices, as well as PSAPs individuals are 2042 exposed to potential financial, reputational, or physical harm. 2044 Misattribution: If the personal data collected and conveyed is 2045 incorrect or inaccurate then this may lead to misattribution. 2046 Misattribution occurs when data or communications related to one 2047 individual are attributed to another. 2049 Identification: By the nature of the additional data and its 2050 capability to provide much richer information about the caller, 2051 the call, and the location the calling party is identified in a 2052 much better way. Some users may feel uncomfortable with this 2053 degree of information sharing even in emergency services 2054 situations. 2056 Secondary Use: Furthermore, there is the risk of secondary use. 2057 Secondary use is the use of collected information about an 2058 individual without the individual's consent for a purpose 2059 different from that for which the information was collected. The 2060 stated purpose of the additional data is for emergency services 2061 purposes but theoretically the same information could be used for 2062 any other call as well. Additionally, parties involved in the 2063 emergency call may retain the obtained information and may re-use 2064 it for other, non-emergency services purposes. 2066 Disclosure: When the data defined in this document is not properly 2067 security (while in transit with traditional communication security 2068 techniques, and while at rest using access control mechanisms) 2069 there is the risk of disclosure, which is the revelation of 2070 information about an individual that affects the way others judge 2071 the individual. 2073 To mitigate these privacy risks the following countermeasures can be 2074 taken. 2076 In regions where callers can elect to suppress certain personally 2077 identifying information, the network or PSAP functionality can 2078 inspect privacy flags within the SIP headers to determine what 2079 information may be passed, stored, or displayed to comply with local 2080 policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. 2081 The presence of this privacy type in a Privacy header field indicates 2082 that the user would like the network asserted identity to be kept 2083 private with respect to SIP entities outside the trust domain with 2084 which the user authenticated, including the PSAP. 2086 This document defines various data structures that constitutes 2087 personal data. Local regulations may govern what data must be 2088 provided in emergency calls, but in general, the emergency call 2089 system is often aided by the kinds of information described in this 2090 document. There is a tradeoff between the privacy considerations and 2091 the utility of the data. For adequate protection this specification 2092 requires all data exchanges to be secured via communication security 2093 techniques (namely TLS) against eavesdropping and inception. 2094 Furthermore, security safeguards are required to prevent unauthorized 2095 access to data at rest. Various security incidents over the last 10 2096 years have shown data breaches are not not uncommon and are often 2097 caused by lack of proper access control frameworks, software bugs 2098 (buffer overflows), or missing input parsing (SQL injection attacks). 2099 The risks of data breaches is increased with the obligation for 2100 emergency services to retain emergency call related data for extended 2101 periods, e.g., several years are the norm. 2103 Finally, it is also worth to highlight the nature of the SIP 2104 communication architecture, which introduces additional complications 2105 for privacy. Some forms of data can be sent by value in the SIP 2106 signaling or by value (URL in SIP signaling). When data is sent by 2107 value, all intermediaries have access to the data. As such, these 2108 intermediaries may also introduce additional privacy risk. 2109 Therefore, in situations where the conveyed information raises 2110 privacy concerns and intermediaries are involved transmitting a 2111 reference is more appropriate (assuming proper access control 2112 policies are available for distinguishing the different entities 2113 dereferencing the reference). Without access control policies any 2114 party in possession of the reference is able to resolve the reference 2115 and to obtain the data, including intermediaries. 2117 9. IANA Considerations 2118 9.1. Registry creation 2120 This document creates a new registry called 'Emergency Call 2121 Additional Data'. The following sub-registries are created in 2122 Emergency Call Additional Data: 2124 9.1.1. Provider ID Series Registry 2126 This document creates a new sub-registry called 'Additional Call Data 2127 Provider ID Series'. As defined in [RFC5226], this registry operates 2128 under "Expert Review" rules. The expert should determine that the 2129 entity requesting a new value is a legitimate issuer of service 2130 provider IDs suitable for use in Additional Call Data. 2132 The content of this registry includes: 2134 Name: The identifier which will be used in the ProviderIDSeries 2135 element 2137 Source: The full name of the organization issuing the identifiers 2139 URL: A URL to the organization for further information 2141 The initial set of values is listed in Figure 20. 2143 +-----------+--------------------------+----------------------+ 2144 | Name | Source | URL | 2145 +-----------+--------------------------+----------------------+ 2146 | NENA | National Emergency | http://www.nena.org | 2147 | | Number Association | | 2148 | EENA | European Emergency | http://www.eena.org | 2149 | | Number Association | | 2150 +-----------+--------------------------+----------------------+ 2152 Figure 20: Provider ID Series Registry. 2154 9.1.2. Service Provider Type Registry 2156 This document creates a new sub-registry called 'Service Provider 2157 Type'. As defined in [RFC5226], this registry operates under "Expert 2158 Review". The expert should determine that the proposed new value is 2159 distinct from existing values and appropriate for use in the 2160 TypeOfServicerProvider element 2162 The content of this registry includes: 2164 Name: Value to be used in TypeOfServiceProvider. 2166 Description: A short description of the type of service provider 2168 The initial set of values is defined in Figure 1. 2170 9.1.3. Service Delivered Registry 2172 This document creates a new sub-registry called 'Service Delivered'. 2173 As defined in [RFC5226], this registry operates under "Expert Review" 2174 rules. The expert should consider whether the proposed service is 2175 unique from existing services and the definition of the service will 2176 be clear to implementors and PSAPS/responders. 2178 The content of this registry includes: 2180 Name: Enumeration token of the service. 2182 Description: Short description identifying the service. 2184 The initial set of values are defined in Figure 3. 2186 9.1.4. Device Classification Registry 2188 This document creates a new sub-registry called 'Device 2189 Classification'. As defined in [RFC5226], this registry operates 2190 under "Expert Review" rules. The expert should consider whether the 2191 proposed class is unique from existing classes and the definition of 2192 the class will be clear to implementors and PSAPS/responders. 2194 The content of this registry includes: 2196 Name: Enumeration token of the device classification. 2198 Description: Short description identifying the device type. 2200 The initial set of values are defined in Figure 5. 2202 9.1.5. Device ID Type Type Registry 2204 This document creates a new sub-registry called 'Additional Call Data 2205 Device ID Type'. As defined in [RFC5226], this registry operates 2206 under "Expert Review" rules. The expert should ascertain that the 2207 proposed type is well understood, and provides the information useful 2208 to PSAPs and responders to uniquely identify a device. 2210 The content of this registry includes: 2212 Name: Enumeration token of the device id type. 2214 Description: Short description identifying type of device id. 2216 The initial set of values are defined in Figure 6. 2218 9.1.6. Device/Service Data Type Registry 2220 This document creates a new sub-registry called 'Device/Service Data 2221 Type Registry'. As defined in [RFC5226], this registry operates 2222 under "Expert Review" and "Specification Required" rules. The expert 2223 should ascertain that the proposed type is well understood, and 2224 provides information useful to PSAPs and responders. The 2225 specification must contain a complete description of the data, and a 2226 precise format specification suitable to allow interoperable 2227 implementations. 2229 The content of this registry includes: 2231 Name: Enumeration token of the data type. 2233 Description: Short description identifying the the data. 2235 Specification: Citation for the specification of the data. 2237 The initial set of values are listed in Figure 21. 2239 +---------+----------------------------------------+----------------+ 2240 | Token | Description | Specification | 2241 +---------+----------------------------------------+----------------+ 2242 | IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | 2243 +---------+----------------------------------------+----------------+ 2244 | VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS | 2245 +---------+----------------------------------------+----------------+ 2247 Figure 21: Device/Service Data Type Registry. 2249 9.1.7. Additional Data Blocks Registry 2251 This document creates a new sub-registry called 'Additional Data 2252 Blocks' in the purpose registry established by RFC 3261 [RFC3261]. 2253 As defined in [RFC5226], this registry operates under "Expert Review" 2254 and "Specification Required" rules. The expert is responsible for 2255 verifying that the document contains a complete and clear 2256 specification and the proposed functionality does not obviously 2257 duplicate existing functionality. 2259 The content of this registry includes: 2261 Name: Element Name of enclosing block. 2263 Reference: The document that describes the block 2265 The initial set of values are listed in Figure 22. 2267 +--------------+------------+ 2268 | Token | Reference | 2269 +--------------+------------+ 2270 | ProviderInfo | [This RFC] | 2271 | SvcInfo | [This RFC] | 2272 | DevInfo | [This RFC] | 2273 | Subscriber | [This RFC] | 2274 | Comment | [This RFC] | 2275 +--------------+------------+ 2277 Figure 22: Additional Data Blocks Registry. 2279 9.2. 'emergencyCallData' Purpose Parameter Value 2281 This document defines the 'emergencyCall' value for the "purpose" 2282 parameter of the Call-Info header field. The Call-Info header and 2283 the corresponding registry for the 'purpose' parameter was 2284 established with RFC 3261 [RFC3261]. 2286 Header Parameter New 2287 Field Name Value Reference 2288 ---------- --------- ----------------- --------- 2289 Call-Info purpose emergencyCall [This RFC] 2291 9.3. URN Sub-Namespace Registration for provided-by Registry Entry 2293 This section registers the namespace specified in Section 9.5.1 in 2294 the provided-by registry established by RFC 4119, for usage within 2295 the element of a PIDF-LO. 2297 The schema for the provided-by schema used by this document is 2298 specified in Section 6.6. 2300 9.4. MIME Registrations 2302 9.4.1. MIME Content-type Registration for 'application/ 2303 emergencyCall.ProviderInfo+xml' 2305 This specification requests the registration of a new MIME type 2306 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2307 RFC 3023 [RFC3023]. 2309 MIME media type name: application 2311 MIME subtype name: emergencyCall.ProviderInfo+xml 2313 Mandatory parameters: none 2315 Optional parameters: charset Indicates the character encoding of 2316 enclosed XML. 2318 Encoding considerations: Uses XML, which can employ 8-bit 2319 characters, depending on the character encoding used. See 2320 Section 3.2 of RFC 3023 [RFC3023]. 2322 Security considerations: This content type is designed to carry 2323 the data provider information, which is a sub-category of 2324 additional data about an emergency call. Since this data contains 2325 personal information appropriate precautions have to be taken to 2326 limit unauthorized access, inappropriate disclosure to third 2327 parties, and eavesdropping of this information. Please refer to 2328 Section 7 and Section 8 for more information. 2330 Interoperability considerations: None 2332 Published specification: [TBD: This specification] 2334 Applications which use this media type: Emergency Services 2336 Additional information: Magic Number: None File Extension: .xml 2337 Macintosh file type code: 'TEXT' 2339 Person and email address for further information: Hannes 2340 Tschofenig, Hannes.Tschofenig@gmx.net 2342 Intended usage: LIMITED USE 2344 Author: This specification is a work item of the IETF ECRIT 2345 working group, with mailing list address . 2347 Change controller: The IESG 2349 9.4.2. MIME Content-type Registration for 'application/ 2350 emergencyCall.SvcInfo+xml' 2352 This specification requests the registration of a new MIME type 2353 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2354 RFC 3023 [RFC3023]. 2356 MIME media type name: application 2358 MIME subtype name: emergencyCall.SvcInfo+xml 2360 Mandatory parameters: none 2362 Optional parameters: charset Indicates the character encoding of 2363 enclosed XML. 2365 Encoding considerations: Uses XML, which can employ 8-bit 2366 characters, depending on the character encoding used. See 2367 Section 3.2 of RFC 3023 [RFC3023]. 2369 Security considerations: This content type is designed to carry 2370 the service information, which is a sub-category of additional 2371 data about an emergency call. Since this data contains personal 2372 information appropriate precautions have to be taken to limit 2373 unauthorized access, inappropriate disclosure to third parties, 2374 and eavesdropping of this information. Please refer to Section 7 2375 and Section 8 for more information. 2377 Interoperability considerations: None 2379 Published specification: [TBD: This specification] 2381 Applications which use this media type: Emergency Services 2383 Additional information: Magic Number: None File Extension: .xml 2384 Macintosh file type code: 'TEXT' 2386 Person and email address for further information: Hannes 2387 Tschofenig, Hannes.Tschofenig@gmx.net 2389 Intended usage: LIMITED USE 2391 Author: This specification is a work item of the IETF ECRIT 2392 working group, with mailing list address . 2394 Change controller: The IESG 2396 9.4.3. MIME Content-type Registration for 'application/ 2397 emergencyCall.DevInfo+xml' 2399 This specification requests the registration of a new MIME type 2400 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2401 RFC 3023 [RFC3023]. 2403 MIME media type name: application 2405 MIME subtype name: emergencyCall.DevInfo+xml 2407 Mandatory parameters: none 2409 Optional parameters: charset Indicates the character encoding of 2410 enclosed XML. 2412 Encoding considerations: Uses XML, which can employ 8-bit 2413 characters, depending on the character encoding used. See 2414 Section 3.2 of RFC 3023 [RFC3023]. 2416 Security considerations: This content type is designed to carry 2417 the device information information, which is a sub-category of 2418 additional data about an emergency call. Since this data contains 2419 personal information appropriate precautions have to be taken to 2420 limit unauthorized access, inappropriate disclosure to third 2421 parties, and eavesdropping of this information. Please refer to 2422 Section 7 and Section 8 for more information. 2424 Interoperability considerations: None 2426 Published specification: [TBD: This specification] 2428 Applications which use this media type: Emergency Services 2430 Additional information: Magic Number: None File Extension: .xml 2431 Macintosh file type code: 'TEXT' 2433 Person and email address for further information: Hannes 2434 Tschofenig, Hannes.Tschofenig@gmx.net 2436 Intended usage: LIMITED USE 2438 Author: This specification is a work item of the IETF ECRIT 2439 working group, with mailing list address . 2441 Change controller: The IESG 2443 9.4.4. MIME Content-type Registration for 'application/ 2444 emergencyCall.SubInfo+xml' 2446 This specification requests the registration of a new MIME type 2447 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2448 RFC 3023 [RFC3023]. 2450 MIME media type name: application 2452 MIME subtype name: emergencyCall.SubInfo+xml 2454 Mandatory parameters: none 2456 Optional parameters: charset Indicates the character encoding of 2457 enclosed XML. 2459 Encoding considerations: Uses XML, which can employ 8-bit 2460 characters, depending on the character encoding used. See 2461 Section 3.2 of RFC 3023 [RFC3023]. 2463 Security considerations: This content type is designed to carry 2464 owner/subscriber information, which is a sub-category of 2465 additional data about an emergency call. Since this data contains 2466 personal information appropriate precautions have to be taken to 2467 limit unauthorized access, inappropriate disclosure to third 2468 parties, and eavesdropping of this information. Please refer to 2469 Section 7 and Section 8 for more information. 2471 Interoperability considerations: None 2473 Published specification: [TBD: This specification] 2475 Applications which use this media type: Emergency Services 2477 Additional information: Magic Number: None File Extension: .xml 2478 Macintosh file type code: 'TEXT' 2480 Person and email address for further information: Hannes 2481 Tschofenig, Hannes.Tschofenig@gmx.net 2483 Intended usage: LIMITED USE 2485 Author: This specification is a work item of the IETF ECRIT 2486 working group, with mailing list address . 2488 Change controller: The IESG 2490 9.4.5. MIME Content-type Registration for 'application/ 2491 emergencyCall.Comment+xml' 2493 This specification requests the registration of a new MIME type 2494 according to the procedures of RFC 4288 [RFC4288] and guidelines in 2495 RFC 3023 [RFC3023]. 2497 MIME media type name: application 2499 MIME subtype name: emergencyCall.Comment+xml 2501 Mandatory parameters: none 2503 Optional parameters: charset Indicates the character encoding of 2504 enclosed XML. 2506 Encoding considerations: Uses XML, which can employ 8-bit 2507 characters, depending on the character encoding used. See 2508 Section 3.2 of RFC 3023 [RFC3023]. 2510 Security considerations: This content type is designed to carry a 2511 comment, which is a sub-category of additional data about an 2512 emergency call. This data may contain personal information. 2513 Appropriate precautions may have to be taken to limit unauthorized 2514 access, inappropriate disclosure to third parties, and 2515 eavesdropping of this information. Please refer to Section 7 and 2516 Section 8 for more information. 2518 Interoperability considerations: None 2520 Published specification: [TBD: This specification] 2522 Applications which use this media type: Emergency Services 2524 Additional information: Magic Number: None File Extension: .xml 2525 Macintosh file type code: 'TEXT' 2527 Person and email address for further information: Hannes 2528 Tschofenig, Hannes.Tschofenig@gmx.net 2530 Intended usage: LIMITED USE 2532 Author: This specification is a work item of the IETF ECRIT 2533 working group, with mailing list address . 2535 Change controller: The IESG 2537 9.5. URN Sub-Namespace Registration 2539 9.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData 2540 This section registers a new XML namespace, as per the guidelines in 2541 RFC 3688 [RFC3688]. 2543 URI: urn:ietf:params:xml:ns:emergencyCallAddlData 2545 Registrant Contact: IETF, ECRIT working group, , as 2546 delegated by the IESG . 2548 XML: 2550 BEGIN 2551 2552 2554 2555 2556 2558 Namespace for Additional Emergency Call Data 2559 2560 2561

Namespace for Additional Data related to an Emergency Call

2562

See [TBD: This document].

2563 2564 2565 END 2567 9.5.2. Registration for 2568 urn:ietf:params:xml:ns:emergencyCallProviderInfo 2570 This section registers a new XML namespace, as per the guidelines in 2571 RFC 3688 [RFC3688]. 2573 URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo 2575 Registrant Contact: IETF, ECRIT working group, , as 2576 delegated by the IESG . 2578 XML: 2580 BEGIN 2581 2582 2585 2586 2587 2589 Namespace for Additional Emergency Call Data: 2590 Data Provider Information 2591 2592 2593

Namespace for Additional Data related to an Emergency Call

2594

Data Provider Information

2595

See [TBD: This document].

2596 2597 2598 END 2600 9.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2602 This section registers a new XML namespace, as per the guidelines in 2603 RFC 3688 [RFC3688]. 2605 URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo 2607 Registrant Contact: IETF, ECRIT working group, , as 2608 delegated by the IESG . 2610 XML: 2612 BEGIN 2613 2614 2616 2617 2618 2620 Namespace for Additional Emergency Call Data: 2621 Service Information 2622 2623 2624

Namespace for Additional Data related to an Emergency Call

2625

Service Information

2626

See [TBD: This document].

2627 2628 2629 END 2631 9.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo 2633 This section registers a new XML namespace, as per the guidelines in 2634 RFC 3688 [RFC3688]. 2636 URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo 2638 Registrant Contact: IETF, ECRIT working group, , as 2639 delegated by the IESG . 2641 XML: 2643 BEGIN 2644 2645 2647 2648 2649 2651 Namespace for Additional Emergency Call Data: 2652 Device Information 2653 2654 2655

Namespace for Additional Data related to an Emergency Call

2656

Device Information

2657

See [TBD: This document].

2658 2659 2660 END 2662 9.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo 2664 This section registers a new XML namespace, as per the guidelines in 2665 RFC 3688 [RFC3688]. 2667 URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo 2669 Registrant Contact: IETF, ECRIT working group, , as 2670 delegated by the IESG . 2672 XML: 2674 BEGIN 2675 2676 2678 2679 2680 2682 Namespace for Additional Emergency Call Data: 2683 Owner/Subscriber Information 2684 2685 2686

Namespace for Additional Data related to an Emergency Call

2687

Owner/Subscriber Information

2688

See [TBD: This document].

2689 2690 2691 END 2693 9.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment 2695 This section registers a new XML namespace, as per the guidelines in 2696 RFC 3688 [RFC3688]. 2698 URI: urn:ietf:params:xml:ns:emergencyCall.Comment 2700 Registrant Contact: IETF, ECRIT working group, , as 2701 delegated by the IESG . 2703 XML: 2705 BEGIN 2706 2707 2709 2710 2711 2713 Namespace for Additional Emergency Call Data:Comment 2714 2715 2716

Namespace for Additional Data related to an Emergency Call

2717

Comment

2718

See [TBD: This document].

2719 2720 2721 END 2723 9.6. Schema Registrations 2725 This specification registers five schemas, as per the guidelines in 2726 RFC 3688 [RFC3688]. 2728 URI: urn:ietf:params:xml:schema:additional- 2729 data:emergencyCallProviderInfo 2731 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2732 delegated by the IESG (iesg@ietf.org). 2734 XML: The XML schema can be found in Figure 14. 2736 URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo 2738 Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as 2739 delegated by the IESG (iesg@ietf.org). 2741 XML: The XML schema can be found in Figure 15. 2743 URI: urn:ietf:params:xml:schema:additional- 2744 data:emergencyCallDevInfo 2746 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2747 delegated by the IESG (iesg@ietf.org). 2749 XML: The XML schema can be found in Figure 16. 2751 URI: urn:ietf:params:xml:schema:additional- 2752 data:emergencyCall.SubInfo 2754 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2755 delegated by the IESG (iesg@ietf.org). 2757 XML: The XML schema can be found in Section 6.4. 2759 URI: urn:ietf:params:xml:schema:additional- 2760 data:emergencyCall.Comment 2762 Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as 2763 delegated by the IESG (iesg@ietf.org). 2765 XML: The XML schema can be found in Section 6.5. 2767 9.7. VCard Parameter Value Registration 2769 This document registers a new value in the vCARD Parameter Values 2770 registry as defined by [RFC6350] with the following template: 2772 Value: main 2774 Purpose: The main telephone number, typically of an enterprise, as 2775 opposed to a direct dial number of an individual employee 2777 Conformance: This value can be used with the "TYPE" parameter 2778 applied on the "TEL" property. 2780 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 2781 00 2783 10. Acknowledgments 2785 This work was originally started in NENA and has benefitted from a 2786 large number of participants in NENA standardization efforts, 2787 originally in the Long Term Definition Working Group, the Data 2788 Technical Committee and most recently the Additional Data working 2789 group. The authors are grateful for the initial work and extended 2790 comments provided by many NENA participants, including Delaine 2791 Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James 2792 Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, 2793 and Robert (Bob) Sherry. 2795 We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin 2796 Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review 2797 comments. 2799 11. References 2801 11.1. Normative References 2803 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2804 Requirement Levels", BCP 14, RFC 2119, March 1997. 2806 [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource 2807 Locators", RFC 2392, August 1998. 2809 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 2810 Types", RFC 3023, January 2001. 2812 [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, 2813 F., Watson, M., and M. Zonoun, "MIME media types for ISUP 2814 and QSIG Objects", RFC 3204, December 2001. 2816 [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, 2817 A., Peterson, J., Sparks, R., Handley, M., and E. 2818 Schooler, "SIP: Session Initiation Protocol", RFC 3261, 2819 June 2002. 2821 [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private 2822 Extensions to the Session Initiation Protocol (SIP) for 2823 Asserted Identity within Trusted Networks", RFC 3325, 2824 November 2002. 2826 [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail 2827 Extensions (MIME) Parameter", RFC 3459, January 2003. 2829 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 2830 January 2004. 2832 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object 2833 Format", RFC 4119, December 2005. 2835 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and 2836 Registration Procedures", RFC 4288, December 2005. 2838 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2839 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 2840 May 2008. 2842 [RFC5621] Camarillo, G., "Message Body Handling in the Session 2843 Initiation Protocol (SIP)", RFC 5621, September 2009. 2845 [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, 2846 August 2011. 2848 [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC 2849 6351, August 2011. 2851 11.2. Informational References 2853 [I-D.ietf-geopriv-relative-location] 2854 Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. 2855 Thomson, "Relative Location Representation", draft-ietf- 2856 geopriv-relative-location-08 (work in progress), September 2857 2013. 2859 [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for 2860 Emergency Context Resolution with Internet Technologies", 2861 RFC 5012, January 2008. 2863 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location 2864 Format for Presence Information Data Format Location 2865 Object (PIDF-LO)", RFC 5139, February 2008. 2867 [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. 2868 Tschofenig, "LoST: A Location-to-Service Translation 2869 Protocol", RFC 5222, August 2008. 2871 [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV 2872 Presence Information Data Format Location Object (PIDF-LO) 2873 Usage Clarification, Considerations, and Recommendations", 2874 RFC 5491, March 2009. 2876 [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. 2877 Thomson, "Dynamic Extensions to the Presence Information 2878 Data Format Location Object (PIDF-LO)", RFC 5962, 2879 September 2010. 2881 [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC 2882 5985, September 2010. 2884 [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, 2885 "Framework for Emergency Calling Using Internet 2886 Multimedia", RFC 6443, December 2011. 2888 [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and 2889 R. George, "Specifying Civic Address Extensions in the 2890 Presence Information Data Format Location Object (PIDF- 2891 LO)", RFC 6848, January 2013. 2893 [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for 2894 Communications Services in Support of Emergency Calling", 2895 BCP 181, RFC 6881, March 2013. 2897 [RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., 2898 Morris, J., Hansen, M., and R. Smith, "Privacy 2899 Considerations for Internet Protocols", RFC 6973, July 2900 2013. 2902 Appendix A. XML Schema for vCard/xCard 2904 This section contains the vCard/xCard XML schema version of the Relax 2905 NG schema defined in RFC 6351 [RFC6351] for simplified use with the 2906 XML schemas defined in this document. The schema in RFC 6351 2907 [RFC6351] is the normative source and this section is informative 2908 only. 2910 2911 2915 2921 2922 2923 vCard Format Specification 2924 2925 2926 2927 2928 2929 2930 2931 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2946 2947 2948 2950 2951 2952 2953 2954 2956 2957 2958 2960 2961 2962 2963 2964 2966 2967 2968 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3013 3014 3015 3016 3020 3021 3022 Section 5: Parameters 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 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 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 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 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 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 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 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 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 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 3950 3951 3952 3953 3954 3955 3956 3958 3959 3960 3961 3962 3963 3964 3966 3967 3968 3970 3972 3973 3974 3976 3977 3978 3979 3981 Authors' Addresses 3983 Brian Rosen 3984 NeuStar 3985 470 Conrad Dr. 3986 Mars, PA 16046 3987 US 3989 Phone: +1 724 382 1051 3990 Email: br@brianrosen.net 3992 Hannes Tschofenig 3993 Nokia Solutions and Networks 3994 Linnoitustie 6 3995 Espoo 02600 3996 Finland 3998 Phone: +358 (50) 4871445 3999 Email: Hannes.Tschofenig@gmx.net 4000 URI: http://www.tschofenig.priv.at 4002 Roger Marshall 4003 TeleCommunication Systems, Inc. 4004 2401 Elliott Avenue 4005 Seattle, WA 98121 4006 US 4008 Phone: +1 206 792 2424 4009 Email: rmarshall@telecomsys.com 4010 URI: http://www.telecomsys.com 4011 Randall Gellens 4012 Qualcomm Technologies, Inc. 4013 5775 Morehouse Drive 4014 San Diego, CA 92121 4015 US 4017 Email: rg+ietf@qti.qualcomm.com 4019 James Winterbottom 4020 AU 4022 Email: a.james.winterbottom@gmail.com