File: rfc7852.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (6325 lines) | stat: -rw-r--r-- 299,078 bytes
parent folder | download | duplicates (2)
<pre>Internet Engineering Task Force (IETF)                        R. Gellens
Request for Comments: 7852
Updates: <a href="./rfc6443">6443</a>, <a href="./rfc6881">6881</a>                                             B. Rosen
Category: Standards Track                                        NeuStar
ISSN: 2070-1721                                            H. Tschofenig

                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                         J. Winterbottom
                                             Winterb Consulting Services
                                                               July 2016


              <span class="h1">Additional Data Related to an Emergency Call</span>

Abstract

   When an emergency call is sent to a Public Safety Answering Point
   (PSAP), the originating device, the access network provider to which
   the device is connected, and all service providers in the path of the
   call have information about the call, the caller, or the location,
   which is helpful for the PSAP to have in handling the emergency.
   This document describes data structures and mechanisms to convey such
   data to the PSAP.  The intent is that every emergency call carry as
   much of the information described here as possible using the
   mechanisms described here.

   The mechanisms permit the data to be conveyed by reference (as an
   external resource) or by value (within the body of a SIP message or a
   location object).  This follows the tradition of prior emergency
   services standardization work where data can be conveyed by value
   within the call signaling (i.e., in the body of the SIP message) or
   by reference.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc7852">http://www.rfc-editor.org/info/rfc7852</a>.




<span class="grey">Gellens, et al.              Standards Track                    [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-4">4</a>
   <a href="#section-2">2</a>.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-6">6</a>
   <a href="#section-3">3</a>.  Document Scope  . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-7">7</a>
   <a href="#section-4">4</a>.  Data Structures . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-7">7</a>
    <a href="#section-4.1">4.1</a>.  Data Provider Information. . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
     <a href="#section-4.1.1">4.1.1</a>.  Data Provider String  . . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
     4.1.2.  Data Provider ID .  . . . . . . . . . . . . . . . . . .   <a href="#page-9">9</a>
     <a href="#section-4.1.3">4.1.3</a>.  Data Provider ID Series . . . . . . . . . . . . . . . .  <a href="#page-10">10</a>
     <a href="#section-4.1.4">4.1.4</a>.  Type of Data Provider . . . . . . . . . . . . . . . . .  <a href="#page-11">11</a>
     <a href="#section-4.1.5">4.1.5</a>.  Data Provider Contact URI . . . . . . . . . . . . . . .  <a href="#page-12">12</a>
     <a href="#section-4.1.6">4.1.6</a>.  Data Provider Language(s) Supported . . . . . . . . . .  <a href="#page-13">13</a>
     <a href="#section-4.1.7">4.1.7</a>.  xCard of Data Provider  . . . . . . . . . . . . . . . .  <a href="#page-14">14</a>
     <a href="#section-4.1.8">4.1.8</a>.  Subcontractor Principal . . . . . . . . . . . . . . . .  <a href="#page-14">14</a>
     <a href="#section-4.1.9">4.1.9</a>.  Subcontractor Priority  . . . . . . . . . . . . . . . .  <a href="#page-15">15</a>
     <a href="#section-4.1.10">4.1.10</a>. ProviderInfo Example  . . . . . . . . . . . . . . . . .  <a href="#page-15">15</a>
    <a href="#section-4.2">4.2</a>.  Service Information  . . . . . . . . . . . . . . . . . . .  <a href="#page-18">18</a>
     <a href="#section-4.2.1">4.2.1</a>.  Service Environment . . . . . . . . . . . . . . . . . .  <a href="#page-18">18</a>
     <a href="#section-4.2.2">4.2.2</a>.  Service Type  . . . . . . . . . . . . . . . . . . . . .  <a href="#page-19">19</a>
     4.2.3.  Service Mobility Environment .  . . . . . . . . . . . .  <a href="#page-21">21</a>
     <a href="#section-4.2.4">4.2.4</a>.  EmergencyCallData.ServiceInfo Example . . . . . . . . .  <a href="#page-22">22</a>
    <a href="#section-4.3">4.3</a>.  Device Information . . . . . . . . . . . . . . . . . . . .  <a href="#page-22">22</a>
     <a href="#section-4.3.1">4.3.1</a>.  Device Classification . . . . . . . . . . . . . . . . .  <a href="#page-22">22</a>
     <a href="#section-4.3.2">4.3.2</a>.  Device Manufacturer . . . . . . . . . . . . . . . . . .  <a href="#page-23">23</a>
     <a href="#section-4.3.3">4.3.3</a>.  Device Model Number . . . . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
     <a href="#section-4.3.4">4.3.4</a>.  Unique Device Identifier  . . . . . . . . . . . . . . .  <a href="#page-24">24</a>
     <a href="#section-4.3.5">4.3.5</a>.  Device/Service-Specific Additional Data Structure . . .  <a href="#page-25">25</a>
     4.3.6.  Device/Service-Specific Additional Data Structure Type   26
     <a href="#section-4.3.7">4.3.7</a>.  EmergencyCallData.DeviceInfo Example  . . . . . . . . .  <a href="#page-27">27</a>
    <a href="#section-4.4">4.4</a>.  Owner/Subscriber Information . . . . . . . . . . . . . . .  <a href="#page-27">27</a>
     <a href="#section-4.4.1">4.4.1</a>.  Subscriber Data Privacy Indicator . . . . . . . . . . .  <a href="#page-27">27</a>
     <a href="#section-4.4.2">4.4.2</a>.  xCard for Subscriber's Data . . . . . . . . . . . . . .  <a href="#page-28">28</a>



<span class="grey">Gellens, et al.              Standards Track                    [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


     <a href="#section-4.4.3">4.4.3</a>.  EmergencyCallData.SubscriberInfo Example  . . . . . . .  <a href="#page-29">29</a>
    <a href="#section-4.5">4.5</a>.  Comment  . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-31">31</a>
     <a href="#section-4.5.1">4.5.1</a>.  Comment . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-31">31</a>
     <a href="#section-4.5.2">4.5.2</a>.  EmergencyCallData.Comment Example . . . . . . . . . . .  <a href="#page-32">32</a>
   <a href="#section-5">5</a>.  Issues with Getting New Types of Data into Use  . . . . . . .  <a href="#page-32">32</a>
    5.1.  Choosing between Defining a New Type of Block or a New
          Type of Device/Service-Specific Additional Data  . . . . .  <a href="#page-33">33</a>
   <a href="#section-6">6</a>.  Data Transport Mechanisms . . . . . . . . . . . . . . . . . .  <a href="#page-33">33</a>
    <a href="#section-6.1">6.1</a>.  Transmitting Blocks Using Call-Info  . . . . . . . . . . .  <a href="#page-36">36</a>
    6.2.  Transmitting Blocks by Reference Using the &lt;provided-by&gt;
          Element  . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-37">37</a>
    6.3.  Transmitting Blocks by Value Using the &lt;provided-by&gt;
          Element  . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-38">38</a>
    <a href="#section-6.4">6.4</a>.  The Content-Disposition Parameter  . . . . . . . . . . . .  <a href="#page-39">39</a>
   <a href="#section-7">7</a>.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-41">41</a>
   <a href="#section-8">8</a>.  XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-53">53</a>
    <a href="#section-8.1">8.1</a>.  EmergencyCallData.ProviderInfo XML Schema  . . . . . . . .  <a href="#page-54">54</a>
    <a href="#section-8.2">8.2</a>.  EmergencyCallData.ServiceInfo XML Schema . . . . . . . . .  <a href="#page-56">56</a>
    <a href="#section-8.3">8.3</a>.  EmergencyCallData.DeviceInfo XML Schema  . . . . . . . . .  <a href="#page-57">57</a>
    <a href="#section-8.4">8.4</a>.  EmergencyCallData.SubscriberInfo XML Schema  . . . . . . .  <a href="#page-59">59</a>
    <a href="#section-8.5">8.5</a>.  EmergencyCallData.Comment XML Schema . . . . . . . . . . .  <a href="#page-60">60</a>
    <a href="#section-8.6">8.6</a>.  provided-by XML Schema . . . . . . . . . . . . . . . . . .  <a href="#page-61">61</a>
   <a href="#section-9">9</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .  <a href="#page-62">62</a>
   <a href="#section-10">10</a>. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  <a href="#page-64">64</a>
   <a href="#section-11">11</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  <a href="#page-67">67</a>
    <a href="#section-11.1">11.1</a>.  Emergency Call Additional Data Registry . . . . . . . . .  <a href="#page-67">67</a>
     <a href="#section-11.1.1">11.1.1</a>.  Provider ID Series Registry  . . . . . . . . . . . . .  <a href="#page-67">67</a>
     <a href="#section-11.1.2">11.1.2</a>.  Service Environment Registry . . . . . . . . . . . . .  <a href="#page-68">68</a>
     <a href="#section-11.1.3">11.1.3</a>.  Service Type Registry  . . . . . . . . . . . . . . . .  <a href="#page-68">68</a>
     <a href="#section-11.1.4">11.1.4</a>.  Service Mobility Registry  . . . . . . . . . . . . . .  <a href="#page-68">68</a>
     <a href="#section-11.1.5">11.1.5</a>.  Type of Provider Registry  . . . . . . . . . . . . . .  <a href="#page-69">69</a>
     <a href="#section-11.1.6">11.1.6</a>.  Device Classification Registry . . . . . . . . . . . .  <a href="#page-69">69</a>
     <a href="#section-11.1.7">11.1.7</a>.  Device ID Type Registry  . . . . . . . . . . . . . . .  <a href="#page-69">69</a>
     <a href="#section-11.1.8">11.1.8</a>.  Device/Service Data Type Registry  . . . . . . . . . .  <a href="#page-70">70</a>
     <a href="#section-11.1.9">11.1.9</a>.  Emergency Call Data Types Registry . . . . . . . . . .  <a href="#page-70">70</a>
    <a href="#section-11.2">11.2</a>.  'EmergencyCallData' Purpose Parameter Value . . . . . . .  <a href="#page-72">72</a>
    11.3.  URN Sub-Namespace Registration for &lt;provided-by&gt;
           Registry Entry  . . . . . . . . . . . . . . . . . . . . .  <a href="#page-72">72</a>
    <a href="#section-11.4">11.4</a>.  MIME Registrations  . . . . . . . . . . . . . . . . . . .  <a href="#page-72">72</a>
     11.4.1.  MIME Content-Type Registration for
              'application/EmergencyCallData.ProviderInfo+xml' . . .  <a href="#page-72">72</a>
     11.4.2.  MIME Content-Type Registration for
              'application/EmergencyCallData.ServiceInfo+xml'  . . .  <a href="#page-73">73</a>
     11.4.3.  MIME Content-Type Registration for
              'application/EmergencyCallData.DeviceInfo+xml' . . . .  <a href="#page-74">74</a>
     11.4.4.  MIME Content-Type Registration for
              'application/EmergencyCallData.SubscriberInfo+xml' . .  <a href="#page-75">75</a>




<span class="grey">Gellens, et al.              Standards Track                    [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


     11.4.5.  MIME Content-Type Registration for
              'application/EmergencyCallData.Comment+xml'  . . . . .  <a href="#page-76">76</a>
    <a href="#section-11.5">11.5</a>.  URN Sub-Namespace Registration  . . . . . . . . . . . . .  <a href="#page-78">78</a>
     11.5.1.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData . . . . . . .  <a href="#page-78">78</a>
     11.5.2.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo . 78
     11.5.3.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo  . 79
     11.5.4.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo . . <a href="#page-80">80</a>
     11.5.5.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo 81
     11.5.6.  Registration for
              urn:ietf:params:xml:ns:EmergencyCallData:Comment . . .  <a href="#page-81">81</a>
    <a href="#section-11.6">11.6</a>.  Schema Registrations  . . . . . . . . . . . . . . . . . .  <a href="#page-82">82</a>
    <a href="#section-11.7">11.7</a>.  vCard Parameter Value Registration  . . . . . . . . . . .  <a href="#page-83">83</a>
   <a href="#section-12">12</a>. References  . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-84">84</a>
    <a href="#section-12.1">12.1</a>.  Normative References  . . . . . . . . . . . . . . . . . .  <a href="#page-84">84</a>
    <a href="#section-12.2">12.2</a>.  Informative References  . . . . . . . . . . . . . . . . .  <a href="#page-85">85</a>
   <a href="#appendix-A">Appendix A</a>.  XML Schema for vCard/xCard . . . . . . . . . . . . .  <a href="#page-89">89</a>
   <a href="#appendix-B">Appendix B</a>.  XML Validation . . . . . . . . . . . . . . . . . . . <a href="#page-111">111</a>
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-112">112</a>
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-113">113</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   When an IP-based emergency call is initiated, a rich set of data from
   multiple data sources is conveyed to the Public Safety Answering
   Point (PSAP).  This data includes information about the calling party
   identity, the multimedia capabilities of the device, the request for
   emergency services, location information, and metadata about the
   sources of the data.  In addition, the device, the access network
   provider, and any service provider in the call path has even more
   information that is useful for a PSAP when handling an emergency.

   This document extends the basic set of data communicated with an
   emergency call based on the Session Initiation Protocol (SIP), as
   described in <a href="./rfc6443">RFC 6443</a> [<a href="./rfc6443" title="&quot;Framework for Emergency Calling Using Internet Multimedia&quot;">RFC6443</a>] and <a href="./rfc6881">RFC 6881</a> [<a href="./rfc6881" title="&quot;Best Current Practice for Communications Services in Support of Emergency Calling&quot;">RFC6881</a>], in order to
   carry additional data that is useful to an entity or call taker
   handling the call.  This data is "additional" to the basic
   information found in the emergency call signaling used.  The intent
   is that every emergency call carry as much of the information
   described here as possible using the mechanisms described here.







<span class="grey">Gellens, et al.              Standards Track                    [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   This document defines three categories of this additional data that
   can be transmitted with an emergency call:

   Data Associated with a Location:  Primary location data is conveyed
      in the Presence Information Data Format Location Object (PIDF-LO)
      data structure as defined in <a href="./rfc4119">RFC 4119</a> [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>] and extended by
      <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>] and <a href="./rfc6848">RFC 6848</a> [<a href="./rfc6848" title="&quot;Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF- LO)&quot;">RFC6848</a>] (for civic location
      information), <a href="./rfc5491">RFC 5491</a> [<a href="./rfc5491" title="&quot;GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and Recommendations&quot;">RFC5491</a>] and <a href="./rfc5962">RFC 5962</a> [<a href="./rfc5962" title="&quot;Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5962</a>] (for
      geodetic location information), and <a href="./rfc7035">RFC 7035</a> [<a href="./rfc7035" title="&quot;Relative Location Representation&quot;">RFC7035</a>] (for
      relative location).  This primary location data identifies the
      location or estimated location of the caller.  However, there
      might exist additional, secondary data that is specific to the
      location, such as floor plans, tenant and building owner contact
      data, heating, ventilation, and air conditioning (HVAC) status,
      etc.  Such secondary location data is not included in the location
      data structure but can be transmitted using the mechanisms defined
      in this document.  Although this document does not define any
      structures for such data, future documents can do so following the
      procedures defined here.

   Data Associated with a Call:  While some information is carried in
      the call setup procedure itself (as part of the SIP headers as
      well as in the body of the SIP message), there is additional data
      known by the device making the call, the access network to which
      the device is connected, and service providers along the path of
      the call.  This information includes service provider contact
      information, subscriber identity and contact information, the type
      of service the service provider and the access network provide,
      what type of device is being used, etc.  Some data is broadly
      applicable, while other data is dependent on the type of device or
      service.  For example, a medical monitoring device might have
      sensor data.  The data structures defined in this document (Data
      Provider Information, Device Information, and Owner/Subscriber
      Information) all fall into the category of "Data Associated with a
      Call".  Note that the owner/subscriber information includes the
      subscriber's vCard, which might contain personal information such
      as birthday, anniversary, etc., but the data block itself is still
      considered to be about the call, not the caller.

   Data Associated with a Caller:  This is personal data about a caller,
      such as medical information and emergency contact data.  Although
      this document does not define any structures within this category,
      future documents can do so following the procedures defined here.

   While this document defines data structures only within the category
   of Data Associated with a Call, by establishing the overall framework
   of Additional Data, along with general mechanisms for transport of
   such data, extension points, and procedures for future extensions, it



<span class="grey">Gellens, et al.              Standards Track                    [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   minimizes the work needed to carry data in the other categories.
   Other specifications can make use of the facilities provided here.

   For interoperability, there needs to be a common way for the
   information conveyed to a PSAP to be encoded and identified.
   Identification allows emergency services authorities to know during
   call processing which types of data are present and to determine if
   they wish to access it.  A common encoding allows the data to be
   successfully accessed.

   This document defines an extensible set of data structures, and
   mechanisms to transmit this data either by value or by reference,
   either in the SIP call signaling or in the PIDF-LO.  The data
   structures are usable by other communication systems and transports
   as well.  The data structures are defined in <a href="#section-4">Section 4</a>, and the
   transport mechanisms (using SIP and HTTPS) are defined in <a href="#section-6">Section 6</a>.

   Each data structure described in this document is encoded as a
   "block" of information.  Each block is an XML structure with an
   associated Multipurpose Internet Mail Extensions (MIME) media type
   for identification within transport such as SIP and HTTPS.  The set
   of blocks is extensible.  Registries are defined to identify the
   block types that can be used and to allow blocks to be included in
   emergency call signaling.

   Much of the information supplied by service providers and devices is
   private and confidential.  Service providers and devices generally go
   to lengths to protect this information; disclosing it in the context
   of an emergency call is a trade-off to protect the greater interest
   of the customer in an emergency.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Terminology</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

   This document also uses terminology from [<a href="./rfc5012" title="&quot;Requirements for Emergency Context Resolution with Internet Technologies&quot;">RFC5012</a>].  We use the term
   "service provider" to refer to an Application Service Provider (ASP).
   A Voice Service Provider (VSP) is a special type of ASP.  With the
   term "Access Network Provider", we refer to the Internet Access
   Provider (IAP) and the Internet Service Provider (ISP) without
   further distinguishing these two entities, since the difference
   between the two is not relevant for this document.  Note that the
   roles of an ASP and access network provider might be provided by a
   single company.  An Emergency Services Provider is an entity directly
   involved in providing emergency services.  This includes PSAPs,




<span class="grey">Gellens, et al.              Standards Track                    [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   dispatch, police, fire, emergency medical, other responders, and
   other similar agencies.

   Within each data block definition (see <a href="#section-4">Section 4</a>), the values for the
   'Use:' label are specified as one of the following:

   'Required':  means it MUST be present in the data structure.

   'Conditional':  means it MUST be present if the specified
      condition(s) is met.  It MAY be present if the condition(s) is not
      met.

   'Optional':  means it MAY be present.

   vCard [<a href="./rfc6350" title="&quot;vCard Format Specification&quot;">RFC6350</a>] is a data format for representing and exchanging a
   variety of information about individuals and other entities.  For
   applications that use XML, the format defined in vCard is not
   immediately applicable.  For this reason, an XML-based encoding of
   the information elements defined in the vCard specification has been
   defined, and the name of that specification is xCard [<a href="./rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>].
   Since the term vCard is more familiar to most readers, we use the
   terms xCard and vCard interchangeably.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Document Scope</span>

   The scope of this document is explicitly limited to emergency calls.
   The data structures defined here are not appropriate to be conveyed
   in non-emergency calls because they carry sensitive and private data.
   However, in certain private-use situations between a specialized
   service provider (such as a vehicle telematics service provider) and
   dedicated equipment (such as in a vehicle) where the endpoints have a
   preexisting relationship and privacy issues are addressed within the
   relationship, the mechanisms and data structures defined here can be
   used with communications within the limited context of the
   preexisting relationship.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Data Structures</span>

   This section defines the following five data structures, each as a
   data block.  For each block, we define the MIME media type and the
   XML encoding.  The five data structures are:

   'Data Provider':  This block supplies name and contact information
      for the entity that created the data.  <a href="#section-4.1">Section 4.1</a> provides the
      details.

   'Service Information':  This block supplies information about the
      service.  The description can be found in <a href="#section-4.2">Section 4.2</a>.



<span class="grey">Gellens, et al.              Standards Track                    [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   'Device Information':  This block supplies information about the
      device placing the call.  Device information can be found in
      <a href="#section-4.3">Section 4.3</a>.

   'Owner/Subscriber':  This block supplies information about the owner
      of the device or about the subscriber.  Details can be found in
      <a href="#section-4.4">Section 4.4</a>.

   'Comment':  This block provides a way to supply free form human-
      readable text to the PSAP or emergency responders.  This simple
      structure is defined in <a href="#section-4.5">Section 4.5</a>.

   Each block contains a mandatory &lt;DataProviderReference&gt; element.  The
   purpose of the &lt;DataProviderReference&gt; element is to associate all
   blocks added by the same data provider as a unit.  The
   &lt;DataProviderReference&gt; element associates the data provider block to
   each of the other blocks added as a unit.  Consequently, when a data
   provider adds additional data to an emergency call (such as device
   information), it MUST add information about itself (via the data
   provider block), and the blocks added contain the same value in the
   &lt;DataProviderReference&gt; element.  All blocks added by a single entity
   at the same time MUST have the same &lt;DataProviderReference&gt; value.
   (In certain situations, the same provider might process a call more
   than once, likely in different roles, and in such cases, each time it
   processes the call, it adds a new set of blocks with a new
   &lt;DataProviderReference&gt; value.)  The value of the
   &lt;DataProviderReference&gt; element has the same syntax and properties
   (specifically, world-uniqueness) as the value of the 'Message-ID'
   message body header field specified in <a href="./rfc5322">RFC 5322</a> [<a href="./rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>] except that
   the &lt;DataProviderReference&gt; element is not enclosed in brackets (the
   '&lt;' and '&gt;' symbols are omitted).  In other words, the value of a
   &lt;DataProviderReference&gt; element is syntactically a msg-id as
   specified in <a href="./rfc5322">RFC 5322</a> [<a href="./rfc5322" title="&quot;Internet Message Format&quot;">RFC5322</a>].

   Each block is added to the "Additional Data Blocks" registry created
   in <a href="#section-11.1.9">Section 11.1.9</a> and categorized as providing data about the caller.
   New blocks added to the registry in the future MUST also be
   categorized per the description of the three categories in <a href="#section-1">Section 1</a>.
   See Sections <a href="#section-5">5</a> and <a href="#section-5.1">5.1</a> for additional considerations when adding new
   blocks or types of data.

   Note that the xCard format is reused in some of the data structures
   to provide contact information.  In an xCard, there is no way to
   specify a 'main' telephone number (that is, a primary or main contact
   number, typically of an enterprise, as opposed to a direct-dial
   number of an individual).  These numbers are useful to emergency
   responders who are called to a large enterprise.  This document adds
   a new parameter value called 'main-number' to the 'TYPE' parameter of



<span class="grey">Gellens, et al.              Standards Track                    [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   the 'tel' property.  It can be used in any xCard in an emergency call
   additional data block.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Data Provider Information</span>

   This block is intended to be supplied by any service provider in the
   path of the call, or the access network provider, and the device.  It
   includes identification and contact information.  This block MUST be
   supplied by any entity that provides any other block; it SHOULD be
   supplied by every service provider in the call path and by the access
   network provider if those entities do not add any other blocks.
   Devices SHOULD use this block to provide identifying information.
   The MIME media type is 'application/
   EmergencyCallData.ProviderInfo+xml'.  An access network provider
   SHOULD provide this block either by value or by reference in the
   &lt;provided-by&gt; element of a PIDF-LO.

<span class="h4"><a class="selflink" id="section-4.1.1" href="#section-4.1.1">4.1.1</a>.  Data Provider String</span>

   Data Element:  Data Provider String

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.

   XML Element:  &lt;DataProviderString&gt;

   Description:  This is a plaintext string suitable for displaying the
      name of the service provider that supplied the data structure.  If
      the device creates the structure, it SHOULD use the value of the
      contact header field in the SIP INVITE.

   Reason for Need:  Inform the call taker of the identity of the entity
      providing the data.

   How Used by Call Taker:  Allows the call taker to interpret the data
      in this structure.  The source of the information often influences
      how the information is used, believed, or verified.

<span class="h4"><a class="selflink" id="section-4.1.2" href="#section-4.1.2">4.1.2</a>.  Data Provider ID</span>

   Data Element:  Data Provider ID

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.  This data MUST be provided by all
      entities other than the originating device in order to uniquely
      identify the service provider or access provider.

   XML Element:  &lt;ProviderID&gt;



<span class="grey">Gellens, et al.              Standards Track                    [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   Description:  A jurisdiction-specific code for, or the fully
      qualified domain name of, the access network provider or service
      provider shown in the &lt;DataProvidedBy&gt; element that created the
      structure.  NOTE: The value SHOULD be assigned by an organization
      appropriate for the jurisdiction.  In the United States, if the
      provider is registered with NENA, the provider's NENA Company ID
      MUST appear here.  Additional information can be found at the
      National Emergency Number Association (NENA) Company Identifier
      Program &lt;<a href="http://www.nena.org/?page=cid2014">http://www.nena.org/?page=cid2014</a>&gt; or the NENA Company ID
      &lt;<a href="http://www.nena.org/?page=CompanyID">http://www.nena.org/?page=CompanyID</a>&gt;.  The NENA Company ID MUST
      be in the form of a URI in the following format:
      urn:nena:companyid:&lt;NENA Company ID&gt;.  If the organization does
      not have an identifier registered with a jurisdiction-specific
      emergency services registrar (such as NENA), then the value MAY be
      the fully qualified domain name of the service provider or access
      provider.  The device MAY use its IP address or fully qualified
      domain name (and set the 'Data Provider ID Series' element to
      'domain').

   Reason for Need:  Inform the call taker of the identity of the entity
      providing the data.

   How Used by Call Taker:  Where jurisdictions have lists of providers,
      the Data Provider ID provides useful information about the data
      source.  The Data Provider ID uniquely identifies the source of
      the data, which might be needed especially during unusual
      circumstances and for routine logging.

<span class="h4"><a class="selflink" id="section-4.1.3" href="#section-4.1.3">4.1.3</a>.  Data Provider ID Series</span>

   Data Element:  Data Provider ID Series

   Use:  Conditional.  Optional for blocks supplied by the originating
      device; mandatory otherwise.

   XML Element:  &lt;ProviderIDSeries&gt;

   Description:  Identifies the issuer of the &lt;ProviderID&gt;.  The
      "Provider ID Series" registry created in <a href="#section-11.1.1">Section 11.1.1</a> initially
      contains the entries shown in Figure 1.

   Reason for Need:  Identifies how to interpret the Data Provider ID.
      The combination of ProviderIDSeries and ProviderID MUST be
      globally unique.

   How Used by Call Taker:  Determines which provider ID registry to
      consult for more information.




<span class="grey">Gellens, et al.              Standards Track                   [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      +-----------+--------------------------+----------------------+
      | Name      | Source                   | URL                  |
      +-----------+--------------------------+----------------------+
      | NENA      | National Emergency       | <a href="http://www.nena.org">http://www.nena.org</a>  |
      |           | Number Association       |                      |
      |           |                          |                      |
      | EENA      | European Emergency       | <a href="http://www.eena.org">http://www.eena.org</a>  |
      |           | Number Association       |                      |
      |           |                          |                      |
      | domain    | (The ID is a fully       | (not applicable)     |
      |           | qualified domain name)   |                      |
      +-----------+--------------------------+----------------------+

                   Figure 1: Provider ID Series Registry

<span class="h4"><a class="selflink" id="section-4.1.4" href="#section-4.1.4">4.1.4</a>.  Type of Data Provider</span>

   Data Element:  Type of Data Provider

   Use:  Required

   XML Element:  &lt;TypeOfProvider&gt;

   Description:  Identifies the type of data provider supplying the
      data.  The registry containing all valid values is created in
      <a href="#section-11.1.5">Section 11.1.5</a>, and the initial set of values is shown in
      Figure 2.

   Reason for Need:  Identifies the category of data provider.

   How Used by Call Taker:  This information can be helpful when
      deciding whom to contact when further information is needed.



















<span class="grey">Gellens, et al.              Standards Track                   [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   +------------------------------+------------------------------------+
   | Token                        | Description                        |
   +------------------------------+------------------------------------+
   |Client                        | Originating client/device          |
   |                              |                                    |
   |Access Network Provider       | Access network service provider    |
   |                              |                                    |
   |Telecom Provider              | Telecom service provider (including|
   |                              |    native and over-the-top VoIP    |
   |                              |    services)                       |
   |                              |                                    |
   |Telematics Provider           | A sensor-based service provider,   |
   |                              |    especially vehicle based        |
   |                              |                                    |
   |Language Translation Provider | A spoken language translation      |
   |                              |    service                         |
   |                              |                                    |
   |Emergency Service Provider    | An emergency service provider      |
   |                              |    conveying information to another|
   |                              |    emergency service provider      |
   |                              |                                    |
   |Emergency Modality Translation| An emergency-call-specific         |
   |                              |    modality translation service,   |
   |                              |    e.g., for sign language         |
   |                              |                                    |
   |Relay Provider                | An interpretation service, e.g.,   |
   |                              |    video relay for sign language   |
   |                              |    interpretation                  |
   |                              |                                    |
   |Other                         | Any other type of service provider |
   +------------------------------+------------------------------------+

                 Figure 2: Type of Data Provider Registry

<span class="h4"><a class="selflink" id="section-4.1.5" href="#section-4.1.5">4.1.5</a>.  Data Provider Contact URI</span>

   Data Element:  Data Provider Contact URI

   Use:  Required

   XML Element:  &lt;ContactURI&gt;

   Description:  When provided by a service provider or an access
      network provider, this information is expected to be a URI to a
      24/7 support organization tasked to provide PSAP support for this
      emergency call.  When provided by a device, this MUST be the
      contact information of the user or owner of the device.  (Ideally,
      this is the contact information of the device user, but when the



<span class="grey">Gellens, et al.              Standards Track                   [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      owner and user are separate (e.g., the device owner is an
      organization), this MAY be the contact information of the owner.)
      The Data Provider Contact URI SHOULD be a tel URI [<a href="./rfc3966" title="&quot;The tel URI for Telephone Numbers&quot;">RFC3966</a>] in
      E.164 format and fully specified with a country code.  If a tel
      URI is not available, a generic SIP URI is acceptable.  Note that
      this contact information is not used by PSAPs for callbacks (a
      call from a PSAP directly related to a recently terminated
      emergency call, placed by the PSAP using a SIP Priority header
      field set to 'psap-callback', as described in [<a href="./rfc7090" title="&quot;Public Safety Answering Point (PSAP) Callback&quot;">RFC7090</a>]).

   Reason for Need:  Additional data providers might need to be
      contacted in error cases or other unusual circumstances.

   How Used by Call Taker:  To contact the supplier of the additional
      data for assistance in handling the call.

<span class="h4"><a class="selflink" id="section-4.1.6" href="#section-4.1.6">4.1.6</a>.  Data Provider Language(s) Supported</span>

   Data Element:  Data Provider Language(s) supported

   Use:  Required

   XML Element:  &lt;Language&gt;

   Description:  This field encodes the language used by the entity at
      the Data Provider Contact URI.  The content of this field consists
      of a single token from the Language Subtag Registry, which can be
      found at [<a href="#ref-LanguageSubtagRegistry">LanguageSubtagRegistry</a>], and is defined in [<a href="./rfc5646" title="&quot;Tags for Identifying Languages&quot;">RFC5646</a>].
      Multiple instances of this element MAY occur, but the order is
      significant and the preferred language SHOULD appear first.  The
      content MUST reflect the languages supported at the contact URI.

      (Note that this field informs the PSAP of the language(s) used by
      the data provider.  If the PSAP needs to contact the data
      provider, it can be helpful to know in advance the language(s)
      used by the data provider.  If the PSAP uses a communication
      protocol to reach the data provider, that protocol might have
      language facilities of its own (such as the 'language' media
      feature tag, defined in <a href="./rfc3840">RFC 3840</a> [<a href="./rfc3840" title="&quot;Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)&quot;">RFC3840</a>], and the more extensive
      language negotiation mechanism proposed in [<a href="#ref-HUMAN-LANG">HUMAN-LANG</a>]), and if
      so, those are independent of this field.)

   Reason for Need:  This information indicates if the emergency service
      authority can directly communicate with the service provider or if
      an interpreter will be needed.






<span class="grey">Gellens, et al.              Standards Track                   [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   How Used by Call Taker:  If the call taker cannot speak any language
      supported by the service provider, a translation service will need
      to be added to the conversation.  Alternatively, other persons at
      the PSAP, besides the call taker, might be consulted for help
      (depending on the urgency and the type of interaction).

<span class="h4"><a class="selflink" id="section-4.1.7" href="#section-4.1.7">4.1.7</a>.  xCard of Data Provider</span>

   Data Element:  xCard of Data Provider

   Use:  Optional

   XML Element:  &lt;DataProviderContact&gt;

   Description:  Per [<a href="./rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>], the xCard structure is represented
      within a &lt;vcard&gt; element.  Although multiple &lt;vcard&gt; elements can
      be contained in a structure, only one &lt;vcard&gt; element SHOULD be
      provided.  If more than one appears, the first SHOULD be used.
      There are many fields in the xCard, and the creator of the data
      structure is encouraged to provide all available information.  N,
      ORG, ADR, TEL, and EMAIL are suggested at a minimum.  N SHOULD
      contain the name of the support group or device owner as
      appropriate.  If more than one TEL property is provided, a
      parameter from the "vCard Property Values" registry SHOULD be
      specified for each TEL.  For encoding of the vCard, this
      specification uses the XML-based encoding specified in [<a href="./rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>],
      which is referred to in this document as 'xCard'.

   Reason for Need:  Information needed to determine additional contact
      information.

   How Used by Call Taker:  Assists the call taker by providing
      additional contact information aside from what is included in the
      SIP INVITE or the PIDF-LO.

<span class="h4"><a class="selflink" id="section-4.1.8" href="#section-4.1.8">4.1.8</a>.  Subcontractor Principal</span>

   When the entity providing the data is a subcontractor, the Data
   Provider Type is set to that of the primary service provider, and
   this entry is supplied to provide information regarding the
   subcontracting entity.

   Data Element:  Subcontractor Principal

   Use:  Conditional.  This data is required if the entity providing the
      data is a subcontractor.

   XML Element:  &lt;SubcontractorPrincipal&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   Description:  Some providers outsource their obligations to handle
      aspects of emergency services to specialized providers.  If the
      data provider is a subcontractor to another provider, this element
      contains the DataProviderString of the service provider to
      indicate which provider the subcontractor is working for.

   Reason for Need:  Identify the entity the subcontractor works for.

   How Used by Call Taker:  Allows the call taker to understand what the
      relationship is between data providers and the service providers
      in the path of the call.

<span class="h4"><a class="selflink" id="section-4.1.9" href="#section-4.1.9">4.1.9</a>.  Subcontractor Priority</span>

   Data Element:  Subcontractor Priority

   Use:  Conditional.  This data is required if the entity providing the
      data is a subcontractor.

   XML Element:  &lt;SubcontractorPriority&gt;

   Description:  If the subcontractor is supposed to be contacted first,
      then this element MUST have the value 'sub'.  If the provider the
      subcontractor is working for is supposed to be contacted first,
      then this element MUST have the value 'main'.

   Reason for Need:  Inform the call taker whom to contact first, if
      support is needed.

   How Used by Call Taker:  To decide which entity to contact first if
      assistance is needed.

<span class="h4"><a class="selflink" id="section-4.1.10" href="#section-4.1.10">4.1.10</a>.  ProviderInfo Example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;ad:EmergencyCallData.ProviderInfo
       xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
       &lt;ad:DataProviderReference&gt;string0987654321@example.org
       &lt;/ad:DataProviderReference&gt;
       &lt;ad:DataProviderString&gt;Example VoIP Provider
       &lt;/ad:DataProviderString&gt;
       &lt;ad:ProviderID&gt;urn:nena:companyid:ID123&lt;/ad:ProviderID&gt;
       &lt;ad:ProviderIDSeries&gt;NENA&lt;/ad:ProviderIDSeries&gt;
       &lt;ad:TypeOfProvider&gt;Telecom Provider&lt;/ad:TypeOfProvider&gt;
       &lt;ad:ContactURI&gt;tel:+1-201-555-0123&lt;/ad:ContactURI&gt;
       &lt;ad:Language&gt;en&lt;/ad:Language&gt;
       &lt;ad:DataProviderContact
           xmlns="urn:ietf:params:xml:ns:vcard-4.0"&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                   &lt;vcard&gt;
                       &lt;fn&gt;&lt;text&gt;Hannes Tschofenig&lt;/text&gt;&lt;/fn&gt;
                       &lt;n&gt;
                           &lt;surname&gt;Hannes&lt;/surname&gt;
                           &lt;given&gt;Tschofenig&lt;/given&gt;
                           &lt;additional/&gt;
                           &lt;prefix/&gt;
                           &lt;suffix&gt;Dipl. Ing.&lt;/suffix&gt;
                       &lt;/n&gt;
                       &lt;bday&gt;&lt;date&gt;--0203&lt;/date&gt;&lt;/bday&gt;
                       &lt;anniversary&gt;
                           &lt;date-time&gt;20090808T1430-0500&lt;/date-time&gt;
                       &lt;/anniversary&gt;
                       &lt;gender&gt;&lt;sex&gt;M&lt;/sex&gt;&lt;/gender&gt;
                       &lt;lang&gt;
                           &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;1&lt;/integer&gt;&lt;/pref&gt;
                           &lt;/parameters&gt;
                           &lt;language-tag&gt;de&lt;/language-tag&gt;
                       &lt;/lang&gt;
                       &lt;lang&gt;
                           &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;2&lt;/integer&gt;&lt;/pref&gt;
                           &lt;/parameters&gt;
                           &lt;language-tag&gt;en&lt;/language-tag&gt;
                       &lt;/lang&gt;
                       &lt;org&gt;
                           &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;text&gt;Example VoIP Provider&lt;/text&gt;
                       &lt;/org&gt;
                       &lt;adr&gt;
                           &lt;parameters&gt;
                               &lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                               &lt;label&gt;&lt;text&gt;Hannes Tschofenig
                                   Linnoitustie 6
                                   Espoo , Finland
                                   02600&lt;/text&gt;&lt;/label&gt;
                           &lt;/parameters&gt;
                           &lt;pobox/&gt;
                           &lt;ext/&gt;
                           &lt;street&gt;Linnoitustie 6&lt;/street&gt;
                           &lt;locality&gt;Espoo&lt;/locality&gt;
                           &lt;region&gt;Uusimaa&lt;/region&gt;
                           &lt;code&gt;02600&lt;/code&gt;
                           &lt;country&gt;Finland&lt;/country&gt;
                       &lt;/adr&gt;
                       &lt;tel&gt;
                           &lt;parameters&gt;
                               &lt;type&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                                   &lt;text&gt;work&lt;/text&gt;
                                   &lt;text&gt;voice&lt;/text&gt;
                               &lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;uri&gt;tel:+358 50 4871445&lt;/uri&gt;
                       &lt;/tel&gt;
                       &lt;tel&gt;
                           &lt;parameters&gt;
                               &lt;type&gt;
                                   &lt;text&gt;work&lt;/text&gt;
                                   &lt;text&gt;main-number&lt;/text&gt;
                                   &lt;text&gt;voice&lt;/text&gt;
                               &lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;uri&gt;tel:+358 50 5050505&lt;/uri&gt;
                       &lt;/tel&gt;
                       &lt;email&gt;
                           &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;text&gt;hannes.tschofenig@nsn.com&lt;/text&gt;
                       &lt;/email&gt;
                       &lt;geo&gt;
                           &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;uri&gt;geo:60.210796,24.812924&lt;/uri&gt;
                       &lt;/geo&gt;
                       &lt;key&gt;
                           &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;uri&gt;
                             http://www.example.com/key.asc
                           &lt;/uri&gt;
                       &lt;/key&gt;
                       &lt;tz&gt;&lt;text&gt;Finland/Helsinki&lt;/text&gt;&lt;/tz&gt;
                       &lt;url&gt;
                           &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                           &lt;/parameters&gt;
                           &lt;uri&gt;http://www.tschofenig.priv.at&lt;/uri&gt;
                       &lt;/url&gt;
                   &lt;/vcard&gt;
       &lt;/ad:DataProviderContact&gt;
   &lt;/ad:EmergencyCallData.ProviderInfo&gt;

             Figure 3: EmergencyCallData.ProviderInfo Example







<span class="grey">Gellens, et al.              Standards Track                   [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Service Information</span>

   This block describes the service that the service provider provides
   to the caller.  It SHOULD be included by all service providers in the
   path of the call.  The MIME media type is 'application/
   EmergencyCallData.ServiceInfo+xml'.

<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>.  Service Environment</span>

   Data Element:  Service Environment

   Use:  Conditional.  Required unless the 'ServiceType' value is
      'wireless'.

   XML Element:  &lt;ServiceEnvironment&gt;

   Description:  This element indicates whether a call is from a
      business or residence.  Currently, the only valid entries are
      'Business', 'Residence', and 'Unknown', as shown in Figure 4.  New
      values can be defined via the registry created in <a href="#section-11.1.2">Section 11.1.2</a>.

   Reason for Need:  To provide context and a hint when determining
      equipment and manpower requirements.

   How Used by Call Taker:  Information can be used to provide context
      and a hint to assist in determining equipment and manpower
      requirements for emergency responders.  This is non-authoritative;
      there are situations where the service provider does not know the
      type of service (e.g., anonymous prepaid service).  The type of
      service does not necessarily reflect the nature of the premises
      (e.g., a business line installed in a residence or cellular
      service).  The registry does not contain all possible values for
      all situations.  Hence, this is at best advisory information, but
      since it mimics a similar capability in some current emergency
      calling systems (e.g., a field in the Automatic Location
      Information (ALI) used with legacy North American wireline
      systems), it is known to be valuable to PSAPs.  The service
      provider uses its best information (such as a rate plan,
      facilities used to deliver service, or a service description) to
      determine the information and is not responsible for determining
      the actual characteristics of the location from which the call
      originated.  Because the usefulness is unknown (and less clear)
      for cellular, this element is OPTIONAL for commercial mobile radio
      services (e.g., cellular) and REQUIRED otherwise.







<span class="grey">Gellens, et al.              Standards Track                   [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                  +-----------+--------------------------+
                  | Token     | Description              |
                  +-----------+--------------------------+
                  | Business  | Business service         |
                  |           |                          |
                  | Residence | Residential service      |
                  |           |                          |
                  | Unknown   | Type of service unknown  |
                  |           |    (e.g., anonymous pre- |
                  |           |    paid service)         |
                  +-----------+--------------------------+

                  Figure 4: Service Environment Registry

<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>.  Service Type</span>

   Data Element:  Service Delivered by Provider to End User

   Use:  Required

   XML Element:  &lt;ServiceType&gt;

   Description:  This defines the type of service over which the call is
      placed (similar to the Class of Service delivered with legacy
      emergency calls in some regions).  The implied mobility of this
      service cannot be relied upon.  A registry is created in
      <a href="#section-11.1.3">Section 11.1.3</a>.  The initial set of values is shown in Figure 5.
      More than one value MAY be returned.  For example, a VoIP inmate
      telephone service is a reasonable combination.

   Reason for Need:  Knowing the type of service can assist the PSAP in
      the handling of the call.

   How Used by Call Taker:  Call takers often use this information to
      determine what kinds of questions to ask callers and how much to
      rely on supportive information.  As the information is not always
      available, and the registry is not all encompassing, this is at
      best advisory information, but since it mimics a similar
      capability in some legacy emergency calling systems, it is known
      to be valuable.

      +--------------+------------------------------------------+
      | Name         | Description                              |
      +--------------+------------------------------------------+
      | wireless     | Wireless Telephone Service: Includes     |
      |              |   CDMA, GSM, Wi-Fi, WiMAX, and LTE       |
      |              |   (but not satellite)                    |
      |              |                                          |



<span class="grey">Gellens, et al.              Standards Track                   [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      | coin         | Fixed public pay/coin telephones: Any    |
      |              |   device operated by coin or credit card |
      |              |                                          |
      | one-way      | One-way outbound service                 |
      |              |                                          |
      | temp         | Soft dial tone/quick service/warm        |
      |              |   disconnect/suspended                   |
      |              |                                          |
      | MLTS-hosted  | Hosted multi-line telephone system       |
      |              |   such as Centrex                        |
      |              |                                          |
      | MLTS-local   | Local multi-line telephone system,       |
      |              |   including all PBXs, key systems, and   |
      |              |   Shared Tenant Services                 |
      |              |                                          |
      | sensor-      | These are devices that generate DATA     |
      |   unattended |   ONLY.  This is a one-way information   |
      |              |   transmit without interactive media.    |
      |              |                                          |
      | sensor-      | Devices that are supported by a          |
      |   attended   |   monitoring service provider or that    |
      |              |   are capable of supporting interactive  |
      |              |   media                                  |
      |              |                                          |
      | POTS         | Wireline: Plain Old Telephone Service    |
      |              |                                          |
      | OTT          | An over-the-top service that provides    |
      |              |   communication over arbitrary Internet  |
      |              |   access (fixed, nomadic, mobile)        |
      |              |                                          |
      | digital      | Wireline non-OTT digital phone service   |
      |              |                                          |
      | OPX          | Off-premise extension                    |
      |              |                                          |
      | relay        | A service where a human third-party      |
      |              |   agent provides additional assistance.  |
      |              |   This includes sign language relay/     |
      |              |   interpretation, telematics services    |
      |              |   that provide a human on the call,      |
      |              |   and similar services.                  |
      +--------------+------------------------------------------+

       Figure 5: Service Delivered by Provider to End User Registry

   The initial set of values has been collected from sources of
   currently used systems, including [<a href="#ref-NENA-02-010">NENA-02-010</a>], [<a href="#ref-nc911" title="&quot;Wireless 911 for Telecommunicators&quot;">nc911</a>], [<a href="#ref-NANP" title="&quot;ANI II Digits Assignments&quot;">NANP</a>], and
   [<a href="#ref-LERG" title="&quot;LERG Routing Guide&quot;">LERG</a>].




<span class="grey">Gellens, et al.              Standards Track                   [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>.  Service Mobility Environment</span>

   Data Element:  Service Mobility Environment

   Use:  Required

   XML Element:  &lt;ServiceMobility&gt;

   Description:  This provides the service provider's view of the
      mobility of the caller's device.  As the service provider might
      not know the characteristics of the actual device or access
      network used, the value should be treated as advisory and not be
      relied upon.  A registry is created in <a href="#section-11.1.4">Section 11.1.4</a> with the
      initial valid entries shown in Figure 6.

   Reason for Need:  Knowing the service provider's belief of mobility
      can assist the PSAP with the handling of the call.

   How Used by Call Taker:  To determine whether to assume the location
      of the caller might change.

                  +-----------+----------------------------+
                  | Token     | Description                |
                  +-----------+----------------------------+
                  | Mobile    | The device is able to move |
                  |           |   at any time              |
                  |           |                            |
                  | Fixed     | The device is not expected |
                  |           |   to move unless the       |
                  |           |   service is relocated     |
                  |           |                            |
                  | Nomadic   | The device is not expected |
                  |           |   to change its point of   |
                  |           |   attachment while on a    |
                  |           |   call                     |
                  |           |                            |
                  | Unknown   | No information is known    |
                  |           |   about the service        |
                  |           |   mobility environment for |
                  |           |   the device               |
                  +-----------+----------------------------+

                    Figure 6: Service Mobility Registry








<span class="grey">Gellens, et al.              Standards Track                   [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>.  EmergencyCallData.ServiceInfo Example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;svc:EmergencyCallData.ServiceInfo
       xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"&gt;
       &lt;svc:DataProviderReference&gt;2468.IBOC.MLTS.1359@example.org
       &lt;/svc:DataProviderReference&gt;
       &lt;svc:ServiceEnvironment&gt;Business&lt;/svc:ServiceEnvironment&gt;
       &lt;svc:ServiceType&gt;MLTS-hosted&lt;/svc:ServiceType&gt;
       &lt;svc:ServiceMobility&gt;Fixed&lt;/svc:ServiceMobility&gt;
   &lt;/svc:EmergencyCallData.ServiceInfo&gt;

              Figure 7: EmergencyCallData.ServiceInfo Example

<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>.  Device Information</span>

   This block provides information about the device used to place the
   call.  It SHOULD be provided by any service provider that knows what
   device is being used and by the device itself.  The MIME media type
   is 'application/EmergencyCallData.DeviceInfo+xml'.

<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>.  Device Classification</span>

   Data Element:  Device Classification

   Use:  Optional

   XML Element:  &lt;DeviceClassification&gt;

   Description:  This data element defines the kind of device making the
      emergency call.  If the device provides the data structure, the
      device information SHOULD be provided.  If the service provider
      provides the structure and it knows what the device is, the
      service provider SHOULD provide the device information.  Often the
      carrier does not know what the device is.  It is possible to
      receive two Device Information blocks: one provided by the device
      and one from the service provider.  This information describes the
      device, not how it is being used.  This data element defines the
      kind of device making the emergency call.  A registry is created
      in <a href="#section-11.1.6">Section 11.1.6</a> with the initial set of values as shown in
      Figure 8.

   Reason for Need:  The device classification implies the capability of
      the calling device and assists in identifying the meaning of the
      emergency call location information that is being presented.  For
      example, does the device require human intervention to initiate a
      call, or is this call the result of programmed instructions?  Does
      the calling device have the ability to update location or



<span class="grey">Gellens, et al.              Standards Track                   [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      condition changes?  Is this device interactive or a one-way
      reporting device?

   How Used by Call Taker:  Can provide the call taker context regarding
      the caller, the capabilities of the calling device, or the
      environment in which the device is being used and can assist in
      understanding the location information and capabilities of the
      calling device.  For example, a cordless handset might be outside
      or next door.

      +---------------+----------------------------------------+
      | Token         |  Description                           |
      +---------------+----------------------------------------+
      |cordless       | Cordless handset                       |
      |fixed          | Fixed phone                            |
      |satellite      | Satellite phone                        |
      |sensor-fixed   | Fixed (non-mobile) sensor/alarm device |
      |desktop        | Soft client on desktop PC              |
      |laptop         | Soft client on laptop-type device      |
      |tablet         | Soft client on tablet-type device      |
      |alarm-monitored| Alarm system                           |
      |sensor-mobile  | Mobile sensor device                   |
      |aircraft       | Aircraft telematics device             |
      |automobile     | Automobile/cycle/off-road telematics   |
      |truck          | Truck/construction telematics          |
      |farm           | Farm equipment telematics              |
      |marine         | Marine telematics                      |
      |personal       | Personal telematics device             |
      |feature-phone  | Cellular feature phone (not smartphone)|
      |smart-phone    | Cellular smartphone (native)           |
      |smart-phone-app| Soft client app on smartphone          |
      |unknown-device | Soft client on unknown device type     |
      |game           | Gaming console                         |
      |text-only      | Other text device                      |
      |NA             | Not Available                          |
      +---------------+----------------------------------------+

          Figure 8: Device Classification Registry Initial Values

<span class="h4"><a class="selflink" id="section-4.3.2" href="#section-4.3.2">4.3.2</a>.  Device Manufacturer</span>

   Data Element:  Device Manufacturer

   Use:  Optional

   XML Element:  &lt;DeviceMfgr&gt;





<span class="grey">Gellens, et al.              Standards Track                   [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   Description:  The plain language name of the manufacturer of the
      device.

   Reason for Need:  Used by PSAP management for post-mortem
      investigation/resolution.

   How Used by Call Taker:  Probably not used by the call taker but by
      PSAP management.

<span class="h4"><a class="selflink" id="section-4.3.3" href="#section-4.3.3">4.3.3</a>.  Device Model Number</span>

   Data Element:  Device Model Number

   Use:  Optional

   XML Element:  &lt;DeviceModelNr&gt;

   Description:  Model number of the device.

   Reason for Need:  Used by PSAP management for after-action
      investigation/resolution.

   How Used by Call Taker:  Probably not used by the call taker but by
      PSAP management.

<span class="h4"><a class="selflink" id="section-4.3.4" href="#section-4.3.4">4.3.4</a>.  Unique Device Identifier</span>

   Data Element:  Unique Device Identifier

   Use:  Optional

   XML Element:  &lt;UniqueDeviceID&gt;

   XML Attribute:  &lt;TypeOfDeviceID&gt;

   Description:  A string that identifies the specific device (or the
      device's current Subscriber Identification Module (SIM)) making
      the call or creating an event.  Note that more than one
      &lt;UniqueDeviceID&gt; can be present to supply more than one of the
      identifying values.

      The &lt;TypeOfDeviceID&gt; attribute identifies the type of device
      identifier.  A registry is created in <a href="#section-11.1.7">Section 11.1.7</a> with an
      initial set of values shown in Figure 9.







<span class="grey">Gellens, et al.              Standards Track                   [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   Reason for Need:  Uniquely identifies the device (or, in the case of
      International Mobile Subscriber Identity (IMSI), a SIM),
      independent of any signaling identifiers present in the call
      signaling stream.

   How Used by Call Taker:  Probably not used by the call taker; might
      be used by PSAP management during an investigation.  (For example,
      if a PSAP experiences repeated false/accidental calls and there is
      no callback number or it isn't usable, the PSAP might need to try
      to track down the device using various means, e.g., contacting
      service providers in the area.)  In the case of handsets without
      current service, it might be possible to determine who last had
      service.  Another example might be a disconnected call where the
      call taker believes there is a need for assistance but was not
      able to obtain a location or other information.

   Example:  &lt;UniqueDeviceID TypeOfDeviceID="SN"&gt;12345&lt;/UniqueDeviceID&gt;

      +--------+------------------------------------------+
      | Token  | Description                              |
      +--------+------------------------------------------+
      | MEID   | Mobile Equipment Identifier  (CDMA)      |
      | ESN    | Electronic Serial Number (GSM)           |
      | MAC    | Media Access Control Address (IEEE)      |
      | WiMAX  | Device Certificate Unique ID             |
      | IMEI   | International Mobile Equipment ID (GSM)  |
      | IMSI   | International Mobile Subscriber ID (GSM) |
      | UDI    | Unique Device Identifier                 |
      | RFID   | Radio Frequency Identification           |
      | SN     | Manufacturer Serial Number               |
      +--------+------------------------------------------+

               Figure 9: Registry of Device Identifier Types

<span class="h4"><a class="selflink" id="section-4.3.5" href="#section-4.3.5">4.3.5</a>.  Device/Service-Specific Additional Data Structure</span>

   Data Element:  Device/service-specific additional data structure

   Use:  Optional

   XML Element:  &lt;DeviceSpecificData&gt;

   Description:  A URI representing additional data whose schema is
      specific to the device or service that created it.  (For example,
      a medical device or medical device monitoring service might have a
      defined set of medical data.)  The URI, when dereferenced, MUST
      yield a data structure defined by the device/service-specific




<span class="grey">Gellens, et al.              Standards Track                   [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      additional data type value.  Different data can be created by each
      classification, e.g., a data set created by a medical device.

   Reason for Need:  Provides device/service-specific data that can be
      used by the call taker and/or responders.

   How Used by Call Taker:  Provide information to guide call takers to
      select appropriate responders, give appropriate pre-arrival
      instructions to callers, and advise responders of what to be
      prepared for.  May be used by responders to guide assistance
      provided.

<span class="h4"><a class="selflink" id="section-4.3.6" href="#section-4.3.6">4.3.6</a>.  Device/Service-Specific Additional Data Structure Type</span>

   Data Element:  Type of device/service-specific additional data
      structure

   Use:  Conditional.  MUST be provided when a device/service-specific
      additional data URI is provided.

   XML Element:  &lt;DeviceSpecificType&gt;

   Description:  A value from the registry defined in <a href="#section-11.1.8">Section 11.1.8</a> to
      describe the type of data located at the device/service-specific
      additional data structure.  The initial values shown in Figure 10
      currently only include IEEE 1512, which is the United States
      Department of Transportation (USDoT) model for traffic incidents.

   Reason for Need:  This data element allows identification of
      externally defined schemas, which might have additional data that
      can assist in emergency response.

   How Used by Call Taker:  This data element allows the end user (call
      taker or first responder) to know what type of additional data is
      available to aid in providing the needed emergency services.

   Note:  This mechanism is not appropriate for information specific to
      a location or a caller (person).

   +---------+---------------------------+--------------------------+
   |  Token  |       Description         |       Specification      |
   +---------+---------------------------+--------------------------+
   |IEEE1512 |Common Incident Management |       IEEE 1512-2006     |
   |         |  Message Set (USDoT model |                          |
   |         |  for traffic incidents)   |                          |
   +---------+---------------------------+--------------------------+

               Figure 10: Device/Service Data Type Registry



<span class="grey">Gellens, et al.              Standards Track                   [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   The IEEE 1512-2006 specifications can be found at [<a href="#ref-IEEE-1512-2006">IEEE-1512-2006</a>].

<span class="h4"><a class="selflink" id="section-4.3.7" href="#section-4.3.7">4.3.7</a>.  EmergencyCallData.DeviceInfo Example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;dev:EmergencyCallData.DeviceInfo
       xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"&gt;
       &lt;dev:DataProviderReference&gt;d4b3072df.201409182208075@example.org
       &lt;/dev:DataProviderReference&gt;
       &lt;dev:DeviceClassification&gt;fixed&lt;/dev:DeviceClassification&gt;
       &lt;dev:DeviceMfgr&gt;Nokia&lt;/dev:DeviceMfgr&gt;
       &lt;dev:DeviceModelNr&gt;Lumia 800&lt;/dev:DeviceModelNr&gt;
       &lt;dev:UniqueDeviceID TypeOfDeviceID="IMEI"&gt;35788104
       &lt;/dev:UniqueDeviceID&gt;
   &lt;/dev:EmergencyCallData.DeviceInfo&gt;

              Figure 11: EmergencyCallData.DeviceInfo Example

<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>.  Owner/Subscriber Information</span>

   This block describes the owner of the device (if provided by the
   device) or the subscriber information (if provided by a service
   provider).  The contact location is not necessarily the location of
   the caller or incident but is rather the nominal contact address.
   The MIME media type is 'application/
   EmergencyCallData.SubscriberInfo+xml'.

   In some jurisdictions, some or all parts of the subscriber-specific
   information are subject to privacy constraints.  These constraints
   vary but dictate which information can be displayed and logged.  A
   general privacy indicator expressing a desire for privacy by the
   subscriber is provided.  The interpretation of how this is applied is
   left to the receiving jurisdiction as the custodians of the local
   regulatory requirements.  This matches an equivalent privacy flag
   provided in some legacy emergency call systems.

<span class="h4"><a class="selflink" id="section-4.4.1" href="#section-4.4.1">4.4.1</a>.  Subscriber Data Privacy Indicator</span>

   Attribute:  'privacyRequested', Boolean.

   Use:  Conditional.  This attribute MUST be provided if the owner/
      subscriber information block is not empty.

   Description:  The subscriber data privacy indicator specifically
      expresses the subscriber's desire for privacy.  In some
      jurisdictions, subscriber services can have a specific "Type of
      Service" that prohibits information, such as the name of the
      subscriber, from being displayed.  This attribute is provided to



<span class="grey">Gellens, et al.              Standards Track                   [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      explicitly indicate whether the subscriber service includes such
      constraints.  The interpretation of this indicator is left to each
      jurisdiction (in keeping with the semantics of the privacy
      indicator provided in some legacy emergency call systems).
      Because the interpretation of this indicator varies based on local
      regulations, this document cannot describe the exact semantics nor
      indicate which fields are affected (the application of this
      indicator might affect the display of data contained in any of the
      blocks).

   Reason for Need:  Some jurisdictions require subscriber privacy to be
      observed when processing emergency calls.

   How Used by Call Taker:  Where privacy is indicated, the call taker
      might not have access to some aspects of the subscriber
      information.

<span class="h4"><a class="selflink" id="section-4.4.2" href="#section-4.4.2">4.4.2</a>.  xCard for Subscriber's Data</span>

   Data Element:  xCard for Subscriber's Data

   Use:  Conditional.  Subscriber data MUST be provided unless it is not
      available.  Some services, such as prepaid phones, non-initialized
      phones, etc., do not have information about the subscriber.

   XML Element:  &lt;SubscriberData&gt;

   Description:  Information known by the service provider or device
      about the subscriber, e.g., Name, Address, Individual Telephone
      Number, Main Telephone Number, and any other data.  &lt;n&gt;, &lt;org&gt; (if
      appropriate), &lt;adr&gt;, &lt;tel&gt;, and &lt;email&gt; are suggested at a
      minimum.  If more than one &lt;tel&gt; property is provided, a parameter
      from the "vCard Property Values" registry MUST be specified on
      each &lt;tel&gt;.  While some data (such as &lt;anniversary&gt;) might not
      seem obviously relevant for emergency services, any data is
      potentially useful in some emergency circumstances.

   Reason for Need:  When the caller is unable to provide information,
      this data can be used to obtain it.

   How Used by Call Taker:  Obtaining critical information about the
      caller and possibly the location when it is not able to be
      obtained otherwise.  While the location here is not necessarily
      that of a caller, in some circumstances it can be helpful in
      locating the caller when other means have failed.






<span class="grey">Gellens, et al.              Standards Track                   [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h4"><a class="selflink" id="section-4.4.3" href="#section-4.4.3">4.4.3</a>.  EmergencyCallData.SubscriberInfo Example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;sub:EmergencyCallData.SubscriberInfo
        xmlns:sub=
            "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
        privacyRequested="false"&gt;
       &lt;sub:DataProviderReference&gt;FEABFECD901@example.org
       &lt;/sub:DataProviderReference&gt;
       &lt;sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0"&gt;
            &lt;vcard&gt;
                   &lt;fn&gt;&lt;text&gt;Simon Perreault&lt;/text&gt;&lt;/fn&gt;
                   &lt;n&gt;
                       &lt;surname&gt;Perreault&lt;/surname&gt;
                       &lt;given&gt;Simon&lt;/given&gt;
                       &lt;additional/&gt;
                       &lt;prefix/&gt;
                       &lt;suffix&gt;ing. jr&lt;/suffix&gt;
                       &lt;suffix&gt;M.Sc.&lt;/suffix&gt;
                   &lt;/n&gt;
                   &lt;bday&gt;&lt;date&gt;--0203&lt;/date&gt;&lt;/bday&gt;
                   &lt;anniversary&gt;
                       &lt;date-time&gt;20090808T1430-0500&lt;/date-time&gt;
                   &lt;/anniversary&gt;
                   &lt;gender&gt;&lt;sex&gt;M&lt;/sex&gt;&lt;/gender&gt;
                   &lt;lang&gt;
                       &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;1&lt;/integer&gt;&lt;/pref&gt;
                       &lt;/parameters&gt;
                       &lt;language-tag&gt;fr&lt;/language-tag&gt;
                   &lt;/lang&gt;
                   &lt;lang&gt;
                       &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;2&lt;/integer&gt;&lt;/pref&gt;
                       &lt;/parameters&gt;
                       &lt;language-tag&gt;en&lt;/language-tag&gt;
                   &lt;/lang&gt;
                   &lt;org&gt;
                       &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;text&gt;Viagenie&lt;/text&gt;
                   &lt;/org&gt;
                   &lt;adr&gt;
                       &lt;parameters&gt;
                           &lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                           &lt;label&gt;&lt;text&gt;Simon Perreault
                               2875 boul. Laurier, suite D2-630
                               Quebec, QC, Canada
                               G1V 2M2&lt;/text&gt;&lt;/label&gt;
                       &lt;/parameters&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                       &lt;pobox/&gt;
                       &lt;ext/&gt;
                       &lt;street&gt;2875 boul. Laurier,
                               suite D2-630&lt;/street&gt;
                       &lt;locality&gt;Quebec&lt;/locality&gt;
                       &lt;region&gt;QC&lt;/region&gt;
                       &lt;code&gt;G1V 2M2&lt;/code&gt;
                       &lt;country&gt;Canada&lt;/country&gt;
                   &lt;/adr&gt;
                   &lt;tel&gt;
                       &lt;parameters&gt;
                           &lt;type&gt;
                               &lt;text&gt;work&lt;/text&gt;
                               &lt;text&gt;voice&lt;/text&gt;
                           &lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;uri&gt;tel:+1-418-656-9254;ext=102&lt;/uri&gt;
                   &lt;/tel&gt;
                   &lt;tel&gt;
                       &lt;parameters&gt;
                           &lt;type&gt;
                               &lt;text&gt;work&lt;/text&gt;
                               &lt;text&gt;voice&lt;/text&gt;
                               &lt;text&gt;main-number&lt;/text&gt;
                           &lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;uri&gt;tel:+1-418-555-0000&lt;/uri&gt;
                   &lt;/tel&gt;
                   &lt;tel&gt;
                       &lt;parameters&gt;
                           &lt;type&gt;
                               &lt;text&gt;work&lt;/text&gt;
                               &lt;text&gt;text&lt;/text&gt;
                               &lt;text&gt;voice&lt;/text&gt;
                               &lt;text&gt;cell&lt;/text&gt;
                               &lt;text&gt;video&lt;/text&gt;
                           &lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;uri&gt;tel:+1-418-262-6501&lt;/uri&gt;
                   &lt;/tel&gt;
                   &lt;email&gt;
                       &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;text&gt;simon.perreault@viagenie.ca&lt;/text&gt;
                   &lt;/email&gt;
                   &lt;geo&gt;
                       &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                       &lt;/parameters&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                       &lt;uri&gt;geo:46.766336,-71.28955&lt;/uri&gt;
                   &lt;/geo&gt;
                   &lt;key&gt;
                       &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;uri&gt;
                       <a href="http://www.viagenie.ca/simon.perreault/simon.asc">http://www.viagenie.ca/simon.perreault/simon.asc</a>
                       &lt;/uri&gt;
                   &lt;/key&gt;
                   &lt;tz&gt;&lt;text&gt;America/Montreal&lt;/text&gt;&lt;/tz&gt;
                   &lt;url&gt;
                       &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                       &lt;/parameters&gt;
                       &lt;uri&gt;http://nomis80.org&lt;/uri&gt;
                   &lt;/url&gt;
           &lt;/vcard&gt;
       &lt;/sub:SubscriberData&gt;
   &lt;/sub:EmergencyCallData.SubscriberInfo&gt;

            Figure 12: EmergencyCallData.SubscriberInfo Example

<span class="h3"><a class="selflink" id="section-4.5" href="#section-4.5">4.5</a>.  Comment</span>

   This block provides a mechanism for the data provider to supply
   extra, human-readable information to the PSAP.  It is not intended
   for a general purpose extension mechanism nor does it aim to provide
   machine-readable content.  The MIME media type is 'application/
   EmergencyCallData.Comment+xml'.

<span class="h4"><a class="selflink" id="section-4.5.1" href="#section-4.5.1">4.5.1</a>.  Comment</span>

   Data Element:  EmergencyCallData.Comment

   Use:  Optional

   XML Element:  &lt;Comment&gt;

   Description:  Human-readable text providing additional information to
      the PSAP staff.

   Reason for Need:  Explanatory information for values in the data
      structure.

   How Used by Call Taker:  To interpret the data provided.







<span class="grey">Gellens, et al.              Standards Track                   [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h4"><a class="selflink" id="section-4.5.2" href="#section-4.5.2">4.5.2</a>.  EmergencyCallData.Comment Example</span>

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;com:EmergencyCallData.Comment
        xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"&gt;
      &lt;com:DataProviderReference&gt;string0987654321@example.org
      &lt;/com:DataProviderReference&gt;
      &lt;com:Comment xml:lang="en"&gt;This is an example text.&lt;/com:Comment&gt;
   &lt;/com:EmergencyCallData.Comment&gt;

               Figure 13: EmergencyCallData.Comment Example

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Issues with Getting New Types of Data into Use</span>

   This document describes two mechanisms that allow extension of the
   kind of data provided with an emergency call: define a new block or
   define a new device/service-specific additional data URL for the
   DeviceInfo block (<a href="#section-4.3.5">Section 4.3.5</a>).  While defining new data types and
   getting a new device or application to send the new data might be
   easy, getting PSAPs and responders to actually retrieve the data and
   use it will be difficult.  New mechanism providers should understand
   that acquiring and using new forms of data usually require software
   upgrades at the PSAP and/or responders, as well as training of call
   takers and responders in how to interpret and use the information.
   Legal and operational review might also be needed.  Overwhelming a
   call taker or responder with too much information is highly
   discouraged.  Thus, the barrier to supporting new data is quite high.

   The mechanisms this document describes are meant to encourage
   development of widely supported, common data formats for classes of
   devices.  If all manufacturers of a class of device use the same
   format, and the data can be shown to improve outcomes, then PSAPs and
   responders can be encouraged to upgrade their systems and train their
   staff to use the data.  Variations, however well intentioned, are
   unlikely to be supported.

   Implementors should consider that data from sensor-based devices in
   some cases might not be useful to call takers or PSAPs (and privacy,
   liability, or other considerations might preclude the PSAP from
   accessing or handling the data) but might be of use to responders.
   Each data item provided with the call in conformance with this
   document can be accessed by responders or other entities in the
   emergency services, whether or not the data is accessed by the PSAP.








<span class="grey">Gellens, et al.              Standards Track                   [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Choosing between Defining a New Type of Block or a New Type of</span>
<span class="h3">      Device/Service-Specific Additional Data</span>

   For devices that have device- or service-specific data, there are two
   choices to carry it.  A new block can be defined, or the device/
   service-specific additional data URL in the DeviceInfo block can be
   used and a new type defined for it.  The data passed would likely be
   the same in either case.  Considerations for choosing the mechanism
   under which to register include:

   Applicability:  Information that will be supported by many kinds of
      devices or services are more appropriately defined as separate
      blocks.

   Privacy:  Information sent as a device/service-specific additional
      data URL in the DeviceInfo block is by reference (not by value),
      which inherently provides some additional privacy protection
      (since the requester needs to supply a certificate which is
      verified by the supplier).

   Size:  Information that can be very large might be better sent in the
      DeviceInfo block, rather than in a new block, so that
      implementations are unable to send the data by value.  Conversely,
      data that is small might best be sent in a separate block so that
      it can be sent by value.

   Availability of a server:  Providing the data via the DeviceInfo
      block requires that a server be available from which to retrieve
      the data.  Providing the data via a new block allows it to be sent
      by value.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Data Transport Mechanisms</span>

   This section defines how to convey additional data to an emergency
   service provider.  Two different means are specified: the first uses
   call signaling; the second uses the &lt;provided-by&gt; element of a PIDF-
   LO [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>].

   1.  First, the ability to embed a Uniform Resource Identifier (URI)
       in an existing SIP header field, the Call-Info header field, is
       defined.  The URI points to the additional data structure.  The
       Call-Info header field is specified in <a href="./rfc3261#section-20.9">Section&nbsp;20.9 of [RFC3261]</a>.

       This document adds a new compound token starting with the value
       'EmergencyCallData' for the Call-Info 'purpose' parameter.  If
       the 'purpose' parameter is set to a value starting with
       'EmergencyCallData', then the Call-Info header field contains
       either an HTTPS URL pointing to an external resource or a Content



<span class="grey">Gellens, et al.              Standards Track                   [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


       Indirection (CID) URI that allows the data structure to be placed
       in the body of the SIP message.  The 'purpose' parameter also
       indicates the kind of data (by its MIME media subtype) that is
       available at the URI.

       As the data is conveyed using a URI in the SIP signaling, the
       data itself can reside on an external resource or can be
       contained within the body of the SIP message.  When the URI
       refers to data at an external resource, the data is said to be
       passed by reference.  When the URI refers to data contained
       within the body of the SIP message, the data is said to be passed
       by value.  A PSAP or emergency responder is able to examine the
       type of data provided and selectively access the data it is
       interested in, while forwarding all of it (the values or
       references) to downstream entities.

       To be conveyed in a SIP body, additional data about a call is
       defined as a series of MIME objects (also referred to as a
       "block" of data).  Each block defined in this document is an XML
       data structure identified by its MIME media type.  (Blocks
       defined by others can be encoded in XML or not, as identified by
       their MIME registration.)  As usual, whenever more than one MIME
       part is included in the body of a message, MIME multipart (i.e.,
       'multipart/mixed') encloses them all.

       This document defines a set of XML schemas and MIME media types
       used for each block defined here.  When additional data is passed
       by value in the SIP signaling, each CID URL points to one block
       in the body.  Multiple URIs are used within a Call-Info header
       field (or multiple Call-Info header fields) to point to multiple
       blocks.  When additional data is provided by reference (in SIP
       signaling or the &lt;provided-by&gt; element of a PIDF-LO), each HTTPS
       URL references one block; the data is retrieved with an HTTPS GET
       operation, which returns the block as an object (the blocks
       defined here are returned as XML objects).

   2.  Second, the ability to embed additional data structures in the
       &lt;provided-by&gt; element of a PIDF-LO [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>] is defined.

       In addition to service providers in the call path, the access
       network provider generally has similar information that can be
       valuable to the PSAP.  When the access network provider and
       service provider are separate entities, the access network does
       not participate in the application-layer signaling (and hence
       cannot add a Call-Info header field to the SIP message) but can
       provide location information in a PIDF-LO.  When the access
       network provider supplies location information in the form of a
       PIDF-LO from a location server via a location configuration



<span class="grey">Gellens, et al.              Standards Track                   [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


       protocol, it has the ability to add the data structures defined
       in this document (or references to them) within the PIDF-LO.

       The data in these data structures is not specific to the location
       itself, but rather provides descriptive information having to do
       with the immediate circumstances about the provider's provision
       of the location (e.g., the identity of the access network
       provider, how to contact that entity, what kind of service the
       access network provides, subscriber information, etc.).  This
       data is similar in nearly every respect to the data known by
       service providers in the path of the call.  The &lt;provided-by&gt;
       element of the PIDF-LO is a mechanism for the access network
       provider to supply the information.  This document describes a
       namespace per [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>] for inclusion in the &lt;provided-by&gt;
       element of a PIDF-LO for adding information known to the access
       network provider.  The access network provider SHOULD provide
       additional data within a &lt;provided-by&gt; element of a PIDF-LO it
       returns for emergency use (e.g., if requested with an HTTP-
       Enabled Location Delivery (HELD) 'responseTime' attribute of
       'emergencyRouting' or 'emergencyDispatch' [<a href="./rfc5985" title="&quot;HTTP-Enabled Location Delivery (HELD)&quot;">RFC5985</a>]).

   One or more blocks of data registered in the "Emergency Call
   Additional Data" registry, as defined in <a href="#section-11.1.9">Section 11.1.9</a>, can be
   included or referenced in the SIP signaling (using the Call-Info
   header field) or in the &lt;provided-by&gt; element of a PIDF-LO.  For
   interoperability, only blocks in the registry are permitted to be
   sent using the mechanisms specified in this document.  Since multiple
   entities are expected to provide sets of data, the data itself needs
   information describing the source.  Consequently, each entity adding
   additional data MUST supply a 'Data Provider' block.  All other
   blocks are optional, but each entity SHOULD supply all blocks where
   it has at least some of the information in the block.

   Note that, as with any mechanism, failures are possible.  For
   example, a block (provided by value or by reference) might not be the
   type indicated by the 'purpose' parameter, or might be badly formed,
   etc.  The general principle that applies to emergency calls is that
   it is more important for the call to go through than for everything
   to be correct.  Thus, most PSAPs will process a call if at all
   possible, even if data is missing or other failures occur.











<span class="grey">Gellens, et al.              Standards Track                   [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Transmitting Blocks Using Call-Info</span>

   A URI to a block MAY be inserted in any SIP request or response
   method (most often INVITE or MESSAGE), using a Call-Info header field
   containing a 'purpose' value starting with 'EmergencyCallData', a dot
   ('.'), and the type of data available at the URI.  The type of data
   is denoted by including the root of the MIME media subtype (the
   'EmergencyCallData' prefix is not repeated), omitting any suffix such
   as '+xml'.  For example, when referencing a block with MIME media
   type 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose'
   parameter is set to 'EmergencyCallData.ProviderInfo'.  An example
   Call-Info header field for this would be:

   Call-Info:  https://www.example.com/23sedde3;
       purpose="EmergencyCallData.ProviderInfo"

   A Call-Info header field with a 'purpose' value starting with
   'EmergencyCallData' only has meaning in the context of an emergency
   call (as ascertained by the presence of an emergency service URN in a
   Request-URI header field of a SIP message), test emergency calls
   (using an appropriate service URN), and some private-use calls where
   the endpoints have a preexisting relationship and privacy concerns do
   not apply because of the relationship; use in other contexts is
   undefined and is likely to unnecessarily expose confidential data.

   If the data is provided by reference, an HTTPS URI MUST be included,
   and consequently, Transport Layer Security (TLS) protection is used
   during the retrieval of the information.

   The data can also be supplied by value in any SIP request or response
   method that is permitted to contain a body (i.e., not a BYE request)
   [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>].  In this case, CID [<a href="./rfc2392" title="&quot;Content-ID and Message-ID Uniform Resource Locators&quot;">RFC2392</a>] is used, with the CID URL
   referencing the MIME body part containing the data.  Note that
   [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] forbids proxies from altering message bodies, so entities
   in the call path that add blocks by value need to do so using an
   appropriate SIP entity (e.g., a back-to-back user agent).

   Transmitting data by value is especially useful in certain cases,
   such as when the data exists in or is generated by the originating
   device but is not intended for very large data blocks.  Additional
   security and privacy considerations apply to data transmitted by
   value, as discussed in Sections <a href="#section-9">9</a> and <a href="#section-10">10</a>, respectively.

   More than one Call-Info header field with a 'purpose' value starting
   with 'EmergencyCallData' can be expected, but at least one MUST be
   provided.  The device MUST provide one unless it knows that a service
   provider is in the path of the call.  The device MAY insert one if it
   uses a service provider.  Each service provider in the path of an



<span class="grey">Gellens, et al.              Standards Track                   [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   emergency call MUST insert its own.  For example, a device, a
   telematics service provider in the call path, as well as the mobile
   carrier handling the call will each provide one.  There might be
   circumstances where there is a service provider who is unaware that
   the call is an emergency call and cannot reasonably be expected to
   determine that it is an emergency call.  In that case, that service
   provider is not expected to provide EmergencyCallData.

   When blocks are transmitted by value, the 'purpose' parameter in a
   Call-Info header field identifies the data, and the CID URL points to
   the data block in the body (which has a matching Content-ID body part
   header field).  When a data block is carried in a signed or encrypted
   body part, the enclosing multipart (e.g., 'multipart/signed' or
   'multipart/encrypted') has the same Content-ID as the data part.
   This allows an entity to identify and access the data blocks it is
   interested in without having to dive deeply into the message
   structure or decrypt parts it is not interested in.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Transmitting Blocks by Reference Using the &lt;provided-by&gt; Element</span>

   The &lt;EmergencyCallDataReference&gt; element is used to transmit an
   additional data block by reference within a &lt;provided-by&gt; element of
   a PIDF-LO.  The &lt;EmergencyCallDataReference&gt; element has two
   attributes: 'ref' to specify the URL and 'purpose' to indicate the
   type of data block referenced.  The value of 'ref' is an HTTPS URL
   that resolves to a data structure with information about the call.
   The value of 'purpose' is the same as used in a Call-Info header
   field (as specified in <a href="#section-6.1">Section 6.1</a>).

   For example, to reference a block with MIME media type 'application/
   EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set
   to 'EmergencyCallData.ProviderInfo'.  An example
   &lt;EmergencyCallDataReference&gt; element for this would be:

      &lt;EmergencyCallDataReference ref="https://www.example.com/23sedde3"
      purpose="EmergencyCallData.ProviderInfo"/&gt;

   The &lt;EmergencyCallDataReference&gt; element transmits one data block;
   multiple data blocks are transmitted by using multiple
   &lt;EmergencyCallDataReference&gt; elements.  Multiple
   &lt;EmergencyCallDataReference&gt; elements MAY be included as child
   elements inside the &lt;provided-by&gt; element.









<span class="grey">Gellens, et al.              Standards Track                   [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   The following is a simplified example:

   &lt;provided-by&gt;
           &lt;EmergencyCallDataReference
                    purpose="EmergencyCallData.ServiceInfo"
                    ref="https://example.com/ref2" /&gt;

           &lt;EmergencyCallDataReference
                    purpose="EmergencyCallData.ProviderInfo"
                    ref="https://example.com/ref3" /&gt;

           &lt;EmergencyCallDataReference
                    purpose="EmergencyCallData.Comment"
                    ref="https://example.com/ref4" /&gt;
   &lt;/provided-by&gt;

                    Example &lt;provided-by&gt; by Reference

   For an example in context, Figure 18 shows a PIDF-LO example with an
   &lt;EmergencyCallDataReference&gt; element pointing to an
   EmergencyCallData.ServiceInfo data block with the URL in the 'ref'
   attribute and the 'purpose' attribute set to
   'EmergencyCallData.ServiceInfo'.

<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>.  Transmitting Blocks by Value Using the &lt;provided-by&gt; Element</span>

   It is RECOMMENDED that access networks supply the data specified in
   this document by reference, because PIDF-LOs can be fetched by a
   client or other entity and stored locally, so providing the data by
   value risks exposing private information to a larger audience.

   The &lt;EmergencyCallDataValue&gt; element is used to transmit one or more
   additional data blocks by value within a &lt;provided-by&gt; element of a
   PIDF-LO.  Each block being transmitted is placed (as a child element)
   inside the &lt;EmergencyCallDataValue&gt; element.  (The same XML structure
   as would be contained in the corresponding MIME media type body part
   is placed inside the &lt;EmergencyCallDataValue&gt; element.)  Multiple
   &lt;EmergencyCallDataValue&gt; elements MAY be included as child elements
   in the &lt;provided-by&gt; element.












<span class="grey">Gellens, et al.              Standards Track                   [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   The following is a simplified example:

   &lt;provided-by&gt;

           &lt;EmergencyCallDataValue&gt;

             &lt;EmergencyCallData.ProviderInfo
                xmlns=
                "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
                &lt;DataProviderReference&gt;flurbit735@es.example.com
                  &lt;/DataProviderReference&gt;
                &lt;DataProviderString&gt;Access Network Examples, Inc.
                  &lt;/DataProviderString&gt;
                &lt;ProviderID&gt;urn:nena:companyid:Test&lt;/ProviderID&gt;
                &lt;ProviderIDSeries&gt;NENA&lt;/ProviderIDSeries&gt;
                &lt;TypeOfProvider&gt;Access Network Provider
                  &lt;/TypeOfProvider&gt;
                &lt;ContactURI&gt;tel:+1-555-555-0897&lt;/ContactURI&gt;
                &lt;Language&gt;en&lt;/Language&gt;
              &lt;/EmergencyCallData.ProviderInfo&gt;

              &lt;EmergencyCallData.Comment
                 xmlns=
                 "urn:ietf:params:xml:ns:EmergencyCallData:Comment"&gt;
                 &lt;DataProviderReference&gt;flurbit735@es.example.com
                   &lt;/DataProviderReference&gt;
                 &lt;Comment xml:lang="en"&gt;This is an example text.
                   &lt;/Comment&gt;
              &lt;/EmergencyCallData.Comment&gt;

           &lt;/EmergencyCallDataValue&gt;

   &lt;/provided-by&gt;

                      Example &lt;provided-by&gt; by Value

   For an example in context, Figure 18 shows a PIDF-LO example that
   contains a &lt;provided-by&gt; element with the
   &lt;EmergencyCallData.ProviderInfo&gt; and the &lt;EmergencyCallData.Comment&gt;
   elements as child elements of an &lt;EmergencyCallDataValue&gt; element.

<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>.  The Content-Disposition Parameter</span>

   <a href="./rfc5621">RFC 5621</a> [<a href="./rfc5621" title="&quot;Message Body Handling in the Session Initiation Protocol (SIP)&quot;">RFC5621</a>] discusses the handling of message bodies in SIP.
   It updates and clarifies handling originally defined in <a href="./rfc3261">RFC 3261</a>
   [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>] based on implementation experience.  While <a href="./rfc3261">RFC 3261</a> did not
   mandate support for 'multipart' message bodies, 'multipart/mixed'
   MIME bodies are used by many extensions (including this document)



<span class="grey">Gellens, et al.              Standards Track                   [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   today.  For example, adding a PIDF-LO, a Session Description Protocol
   (SDP), and additional data in the body of a SIP message requires a
   'multipart' message body.

   <a href="./rfc3204">RFC 3204</a> [<a href="./rfc3204" title="&quot;MIME media types for ISUP and QSIG Objects&quot;">RFC3204</a>] and <a href="./rfc3459">RFC 3459</a> [<a href="./rfc3459" title="&quot;Critical Content Multi-purpose Internet Mail Extensions (MIME) Parameter&quot;">RFC3459</a>] define the 'handling'
   parameter for the Content-Disposition header field.  These RFCs
   describe how a User Agent Server (UAS) reacts if it receives a
   message body whose content type or disposition type it does not
   understand.  If the 'handling' parameter has the value 'optional',
   the UAS ignores the message body.  If the 'handling' parameter has
   the value 'required', the UAS returns a 415 (Unsupported Media Type)
   response.  The 'by-reference' disposition type of <a href="./rfc5621">RFC 5621</a> [<a href="./rfc5621" title="&quot;Message Body Handling in the Session Initiation Protocol (SIP)&quot;">RFC5621</a>]
   allows a SIP message to contain a reference to the body part, and the
   SIP User Agent (UA) processes the body part according to the
   reference.  This is the case for a Call-Info header field containing
   a CID URL.

   As an example, a SIP message indicates the 'Content-Disposition'
   parameter in the body of the SIP message as shown in Figure 14.

         Content-Type: application/sdp
         ...Omit Content-Disposition here; defaults are ok

         ...SDP goes in here

         --boundary1
         Content-Type: application/pidf+xml
         Content-ID: &lt;target123@atlanta.example.com&gt;
         Content-Disposition: by-reference;handling=optional

         ...PIDF-LO goes in here

         --boundary1
         Content-Type: application/EmergencyCallData.ProviderInfo+xml
         Content-ID: &lt;1234567890@atlanta.example.com&gt;
         Content-Disposition: by-reference; handling=optional

         ...Data provider information data goes in here

         --boundary1--

      Figure 14: Example for Use of the Content-Disposition Parameter
                                  in SIP








<span class="grey">Gellens, et al.              Standards Track                   [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Examples</span>

   This section illustrates a longer and more complex example, as shown
   in Figure 15.  In this example, additional data is added by the end
   device, included by the VoIP provider, and provided by the access
   network provider (via the PIDF-LO).

     O   +----+      [============]                     [=============]
    /|\  | UA |      [  Access    ]                     [ VoIP        ]
     |   +----+      [  Network   ]                     [ Provider    ]
    / \              [  Provider  ]                     [ example.org ]
                     [            ]                     [             ]
    (1)              [            ] (2)                 [             ]
    Emergency Call   [            ] Emergency Call      [             ]
    ------------------------------------------------------&gt;           ]
    +Device Info     [            ] +Device Info        [             ]
    +Data Prov. Info [       ^    ] +Data Provider Info [    |        ]
    +Location URI    [=======.====] +Location URI       [====|========]
                             .                               |
                             .                               |
      +Location              .      [==============]         |
      +Owner/Subscriber Info .      [              ]   (3)   |
      +Device Info           .  (4) [           &lt;------------+
      +Data Provider Info #3 ..........&gt;           ] Emergency Call
                                    [              ] +Device Info
                                    [     PSAP     ] +Data Prov. Info #2
                                    [              ] +Location URI
                                    [==============]


     Legend:

         --- Emergency Call Setup Procedure
         ... Location Retrieval/Response

                  Figure 15: Additional Data Example Flow















<span class="grey">Gellens, et al.              Standards Track                   [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   The example scenario starts with the end device itself adding device
   information, owner/subscriber information, a location URI, and data
   provider information to the outgoing emergency call setup message
   (see step #1 in Figure 15).  The SIP INVITE example is shown in
   Figure 16.

      INVITE urn:service:sos SIP/2.0
      Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
      Max-Forwards: 70
      To: &lt;urn:service:sos&gt;
      From: Hannes Tschofenig &lt;sips:hannes@example.com&gt;;tag=9fxced76sl
      Call-ID: 3848276298220188511@example.com
      Call-Info: &lt;http://wwww.example.com/hannes/photo.jpg&gt;
                     ;purpose=icon,
        &lt;http://www.example.com/hannes/&gt; ;purpose=info,
        &lt;cid:1234567890@atlanta.example.com&gt;
            ;purpose=EmergencyCallData.ProviderInfo,
        &lt;cid:0123456789@atlanta.example.com&gt;
            ;purpose=EmergencyCallData.DeviceInfo
      Geolocation: &lt;<a href="https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o">https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o</a>&gt;
      Geolocation-Routing: yes
      Accept: application/sdp, application/pidf+xml,
         application/EmergencyCallData.ProviderInfo+xml
      CSeq: 31862 INVITE
      Contact: &lt;sips:hannes@example.com&gt;
      Content-Type: multipart/mixed; boundary=boundary1
      Content-Length: ...

      --boundary1
      Content-Type: application/sdp

      ...SDP goes here

      --boundary1
      Content-Type: application/EmergencyCallData.DeviceInfo+xml
      Content-ID: &lt;0123456789@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;dev:EmergencyCallData.DeviceInfo
           xmlns:dev=
           "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"&gt;
          &lt;dev:DataProviderReference&gt;
               d4b3072df09876543@[93.184.216.119]
               &lt;/dev:DataProviderReference&gt;
          &lt;dev:DeviceClassification&gt;laptop&lt;/dev:DeviceClassification&gt;
          &lt;dev:UniqueDeviceID
               TypeOfDeviceID="MAC"&gt;00-0d-4b-30-72-df



<span class="grey">Gellens, et al.              Standards Track                   [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


               &lt;/dev:UniqueDeviceID&gt;
      &lt;/dev:EmergencyCallData.DeviceInfo&gt;

      --boundary1
      Content-Type: application/EmergencyCallData.ProviderInfo+xml
      Content-ID: &lt;1234567890@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;pi:EmergencyCallData.ProviderInfo
         xmlns:pi=
            "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
      &lt;pi:DataProviderReference&gt;d4b3072df09876543@[93.184.216.119]
         &lt;/pi:DataProviderReference&gt;
      &lt;pi:DataProviderString&gt;Hannes Tschofenig&lt;/pi:DataProviderString&gt;
      &lt;pi:TypeOfProvider&gt;Client&lt;/pi:TypeOfProvider&gt;
      &lt;pi:ContactURI&gt;tel:+1-555-555-0123&lt;/pi:ContactURI&gt;
      &lt;pi:Language&gt;en&lt;/pi:Language&gt;
      &lt;pi:DataProviderContact
         xmlns="urn:ietf:params:xml:ns:vcard-4.0"&gt;
         &lt;vcard&gt;
            &lt;fn&gt;&lt;text&gt;Hannes Tschofenig&lt;/text&gt;&lt;/fn&gt;
            &lt;n&gt;
               &lt;surname&gt;Hannes&lt;/surname&gt;
               &lt;given&gt;Tschofenig&lt;/given&gt;
               &lt;additional/&gt;
               &lt;prefix/&gt;
               &lt;suffix&gt;Dipl. Ing.&lt;/suffix&gt;
            &lt;/n&gt;
            &lt;bday&gt;&lt;date&gt;--0203&lt;/date&gt;&lt;/bday&gt;
            &lt;anniversary&gt;
               &lt;date-time&gt;20090808T1430-0500&lt;/date-time&gt;
            &lt;/anniversary&gt;
            &lt;gender&gt;&lt;sex&gt;M&lt;/sex&gt;&lt;/gender&gt;
            &lt;lang&gt;
                &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;1&lt;/integer&gt;&lt;/pref&gt;
                &lt;/parameters&gt;
                &lt;language-tag&gt;de&lt;/language-tag&gt;
            &lt;/lang&gt;
            &lt;lang&gt;
               &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;2&lt;/integer&gt;&lt;/pref&gt;
               &lt;/parameters&gt;
               &lt;language-tag&gt;en&lt;/language-tag&gt;
            &lt;/lang&gt;
            &lt;adr&gt;
               &lt;parameters&gt;
                  &lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;label&gt;&lt;text&gt;Hannes Tschofenig



<span class="grey">Gellens, et al.              Standards Track                   [Page 43]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-44" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                     Linnoitustie 6
                     Espoo, Finland
                     02600&lt;/text&gt;&lt;/label&gt;
               &lt;/parameters&gt;
               &lt;pobox/&gt;
               &lt;ext/&gt;
               &lt;street&gt;Linnoitustie 6&lt;/street&gt;
               &lt;locality&gt;Espoo&lt;/locality&gt;
               &lt;region&gt;Uusimaa&lt;/region&gt;
               &lt;code&gt;02600&lt;/code&gt;
               &lt;country&gt;Finland&lt;/country&gt;
            &lt;/adr&gt;
            &lt;adr&gt;
               &lt;parameters&gt;
                  &lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                  &lt;label&gt;&lt;text&gt;Hannes Tschofenig
                     c/o Hotel DuPont
                     42 W 11th St
                     Wilmington, DE 19801
                     USA&lt;/text&gt;&lt;/label&gt;
               &lt;/parameters&gt;
               &lt;pobox/&gt;
               &lt;ext/&gt;
               &lt;street&gt;42 W 11th St&lt;/street&gt;
                  &lt;locality&gt;Wilmington&lt;/locality&gt;
                  &lt;region&gt;DE&lt;/region&gt;
                  &lt;code&gt;19801&lt;/code&gt;
                  &lt;country&gt;USA&lt;/country&gt;
            &lt;/adr&gt;
            &lt;tel&gt;
               &lt;parameters&gt;
                  &lt;type&gt;
                     &lt;text&gt;work&lt;/text&gt;
                     &lt;text&gt;voice&lt;/text&gt;
                  &lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;tel:+358 50 4871445&lt;/uri&gt;
            &lt;/tel&gt;
            &lt;tel&gt;
               &lt;parameters&gt;
                  &lt;type&gt;
                     &lt;text&gt;home&lt;/text&gt;
                     &lt;text&gt;voice&lt;/text&gt;
                  &lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;tel:+1-555-555-0123&lt;/uri&gt;
            &lt;/tel&gt;
            &lt;tel&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 44]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-45" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


               &lt;parameters&gt;
                  &lt;type&gt;
                     &lt;text&gt;work&lt;/text&gt;
                     &lt;text&gt;voice&lt;/text&gt;
                     &lt;text&gt;main-number&lt;/text&gt;
                  &lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;tel:+1-302-594-3100&lt;/uri&gt;
            &lt;/tel&gt;
            &lt;email&gt;
               &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
               &lt;/parameters&gt;
               &lt;text&gt;hannes.tschofenig@nsn.com&lt;/text&gt;
            &lt;/email&gt;
            &lt;geo&gt;
               &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;geo:60.210796,24.812924&lt;/uri&gt;
            &lt;/geo&gt;
            &lt;geo&gt;
               &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;geo:39.746537,-75.548027&lt;/uri&gt;
            &lt;/geo&gt;
            &lt;key&gt;
               &lt;parameters&gt;
                  &lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;https://www.example.com/key.asc&lt;/uri&gt;
            &lt;/key&gt;
            &lt;tz&gt;&lt;text&gt;Finland/Helsinki&lt;/text&gt;&lt;/tz&gt;
            &lt;url&gt;
               &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
               &lt;/parameters&gt;
               &lt;uri&gt;http://example.com/hannes.tschofenig
               &lt;/uri&gt;
            &lt;/url&gt;
         &lt;/vcard&gt;
      &lt;/pi:DataProviderContact&gt;
      &lt;/pi:EmergencyCallData.ProviderInfo&gt;
      --boundary1--

       Figure 16: End Device Sending SIP INVITE with Additional Data

   In this example, information available to the access network provider
   is included in the call setup message only indirectly via the use of
   the location reference.  The PSAP has to retrieve it via a separate
   lookup step.  Since the access network provider and the VoIP service



<span class="grey">Gellens, et al.              Standards Track                   [Page 45]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-46" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   provider are two independent entities in this scenario, the access
   network provider is not involved in application-layer exchanges; the
   SIP INVITE transits the access network transparently, as illustrated
   in steps #1 and #2 (the access network does not alter the SIP
   INVITE).

   The VoIP service provider receives the message and determines, based
   on the service URN, that the incoming request is an emergency call.
   It performs typical emergency-services-related tasks (such as
   location-based routing) and adds additional data, namely service and
   subscriber information as well as data provider information #2, to
   the outgoing message.  For the example, we assume a VoIP service
   provider deploys a back-to-back user agent allowing additional data
   to be included in the body of the SIP message (rather than by
   reference), which allows us to illustrate the use of multiple data
   provider info blocks.  The resulting message is shown in Figure 17.
   The SIP INVITE is sent to the PSAP in step #3.

      INVITE sips:psap@example.org SIP/2.0
      Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
      Max-Forwards: 70
      To: &lt;urn:service:sos&gt;
      From: Hannes Tschofenig &lt;sips:hannes@example.com&gt;;tag=9fxced76sl
      Call-ID: 3848276298220188511@example.com
      Call-Info: &lt;http://wwww.example.com/hannes/photo.jpg&gt;;
         purpose=icon,
         &lt;http://www.example.com/hannes/&gt;; purpose=info,
         &lt;cid:1234567890@atlanta.example.com&gt;;
         purpose=EmergencyCallData.ProviderInfo
         &lt;cid:0123456789@atlanta.example.com&gt;;
         purpose=EmergencyCallData.DeviceInfo
      Call-Info: &lt;cid:bloorpyhex@atlanta.example.com&gt;;
         purpose=EmergencyCallData.ServiceInfo
      Call-Info: &lt;cid:aaabbb@atlanta.example.com&gt;;
         purpose=EmergencyCallData.ProviderInfo
      Geolocation: &lt;<a href="https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o">https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o</a>&gt;
      Geolocation-Routing: yes
      Accept: application/sdp, application/pidf+xml,
         application/EmergencyCallData.ProviderInfo+xml
      CSeq: 31862 INVITE
      Contact: &lt;sips:hannes@example.com&gt;
      Content-Type: multipart/mixed; boundary=boundary1
      Content-Length: ...

      --boundary1
      Content-Type: application/sdp

      ...SDP goes here



<span class="grey">Gellens, et al.              Standards Track                   [Page 46]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-47" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      --boundary1
      Content-Type: application/EmergencyCallData.DeviceInfo+xml
      Content-ID: &lt;0123456789@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;dev:EmergencyCallData.DeviceInfo
         xmlns:dev=
         "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"&gt;
         &lt;dev:DataProviderReference&gt;d4b3072df09876543@[93.184.216.119]
         &lt;/dev:DataProviderReference&gt;
         &lt;dev:DeviceClassification&gt;laptop&lt;/dev:DeviceClassification&gt;
         &lt;dev:UniqueDeviceID
            TypeOfDeviceID="MAC"&gt;00-0d-4b-30-72-df&lt;/dev:UniqueDeviceID&gt;
      &lt;/dev:EmergencyCallData.DeviceInfo&gt;

      --boundary1
      Content-Type: application/EmergencyCallData.ProviderInfo+xml
      Content-ID: &lt;1234567890@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;pi:EmergencyCallData.ProviderInfo
         xmlns:pi=
         "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
         &lt;pi:DataProviderReference&gt;d4b3072df09876543@[93.184.216.119]
         &lt;/pi:DataProviderReference&gt;
         &lt;pi:DataProviderString&gt;Hannes Tschofenig
         &lt;/pi:DataProviderString&gt;
         &lt;pi:TypeOfProvider&gt;Client&lt;/pi:TypeOfProvider&gt;
         &lt;pi:ContactURI&gt;tel:+1-555-555-0123&lt;/pi:ContactURI&gt;
         &lt;pi:Language&gt;en&lt;/pi:Language&gt;
         &lt;pi:DataProviderContact
            xmlns="urn:ietf:params:xml:ns:vcard-4.0"&gt;
            &lt;vcard&gt;
               &lt;fn&gt;&lt;text&gt;Hannes Tschofenig&lt;/text&gt;&lt;/fn&gt;
               &lt;n&gt;
                  &lt;surname&gt;Hannes&lt;/surname&gt;
                  &lt;given&gt;Tschofenig&lt;/given&gt;
                  &lt;additional/&gt;
                  &lt;prefix/&gt;
                  &lt;suffix&gt;Dipl. Ing.&lt;/suffix&gt;
               &lt;/n&gt;
               &lt;bday&gt;&lt;date&gt;--0203&lt;/date&gt;&lt;/bday&gt;
               &lt;anniversary&gt;
                  &lt;date-time&gt;20090808T1430-0500&lt;/date-time&gt;
               &lt;/anniversary&gt;
               &lt;gender&gt;&lt;sex&gt;M&lt;/sex&gt;&lt;/gender&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 47]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-48" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


               &lt;lang&gt;
                  &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;1&lt;/integer&gt;&lt;/pref&gt;
                  &lt;/parameters&gt;
                  &lt;language-tag&gt;de&lt;/language-tag&gt;
               &lt;/lang&gt;
               &lt;lang&gt;
                  &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;2&lt;/integer&gt;&lt;/pref&gt;
                  &lt;/parameters&gt;
                  &lt;language-tag&gt;en&lt;/language-tag&gt;
               &lt;/lang&gt;
               &lt;adr&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                     &lt;label&gt;&lt;text&gt;Hannes Tschofenig
                         Linnoitustie 6
                         Espoo, Finland
                         02600&lt;/text&gt;&lt;/label&gt;
                  &lt;/parameters&gt;
                  &lt;pobox/&gt;
                  &lt;ext/&gt;
                  &lt;street&gt;Linnoitustie 6&lt;/street&gt;
                  &lt;locality&gt;Espoo&lt;/locality&gt;
                  &lt;region&gt;Uusimaa&lt;/region&gt;
                  &lt;code&gt;02600&lt;/code&gt;
                  &lt;country&gt;Finland&lt;/country&gt;
               &lt;/adr&gt;
               &lt;adr&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                     &lt;label&gt;&lt;text&gt;Hannes Tschofenig
                         c/o Hotel DuPont
                         42 W 11th St
                         Wilmington, DE 19801
                         USA&lt;/text&gt;&lt;/label&gt;
                  &lt;/parameters&gt;
                  &lt;pobox/&gt;
                  &lt;ext/&gt;
                  &lt;street&gt;42 W 11th St&lt;/street&gt;
                  &lt;locality&gt;Wilmington&lt;/locality&gt;
                  &lt;region&gt;DE&lt;/region&gt;
                  &lt;code&gt;19801&lt;/code&gt;
                  &lt;country&gt;USA&lt;/country&gt;
               &lt;/adr&gt;
               &lt;tel&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;
                     &lt;text&gt;work&lt;/text&gt;
                     &lt;text&gt;voice&lt;/text&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 48]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-49" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                     &lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;tel:+358 50 4871445&lt;/uri&gt;
               &lt;/tel&gt;
               &lt;tel&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;
                        &lt;text&gt;home&lt;/text&gt;
                        &lt;text&gt;voice&lt;/text&gt;
                     &lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;tel:+1-555-555-0123&lt;/uri&gt;
               &lt;/tel&gt;
               &lt;email&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;text&gt;hannes.tschofenig@nsn.com&lt;/text&gt;
               &lt;/email&gt;
               &lt;geo&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;geo:60.210796,24.812924&lt;/uri&gt;
               &lt;/geo&gt;
               &lt;geo&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;geo:39.746537,-75.548027&lt;/uri&gt;
               &lt;/geo&gt;
               &lt;key&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;https://www.example.com/key.asc&lt;/uri&gt;
               &lt;/key&gt;
               &lt;tz&gt;&lt;text&gt;Finland/Helsinki&lt;/text&gt;&lt;/tz&gt;
               &lt;url&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;http://example.com/hannes.tschofenig&lt;/uri&gt;
               &lt;/url&gt;
            &lt;/vcard&gt;
         &lt;/pi:DataProviderContact&gt;
      &lt;/pi:EmergencyCallData.ProviderInfo&gt;

      --boundary1
      Content-Type: application/EmergencyCallData.ServiceInfo+xml
      Content-ID: &lt;bloorpyhex@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional



<span class="grey">Gellens, et al.              Standards Track                   [Page 49]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-50" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;svc:EmergencyCallData.ServiceInfo
         xmlns:svc=
            "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"&gt;
         &lt;svc:DataProviderReference&gt;string0987654321@example.org
         &lt;/svc:DataProviderReference&gt;
         &lt;svc:ServiceEnvironment&gt;Residence&lt;/svc:ServiceEnvironment&gt;
         &lt;svc:ServiceType&gt;VOIP&lt;/svc:ServiceType&gt;
         &lt;svc:ServiceMobility&gt;Unknown&lt;/svc:ServiceMobility&gt;
      &lt;/svc:EmergencyCallData.ServiceInfo&gt;

      --boundary1
      Content-Type: application/EmergencyCallData.ProviderInfo+xml
      Content-ID: &lt;aaabbb@atlanta.example.com&gt;
      Content-Disposition: by-reference;handling=optional

      &lt;?xml version="1.0" encoding="UTF-8"?&gt;
      &lt;pi:EmergencyCallData.ProviderInfo
         xmlns:pi=
         "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
         &lt;pi:DataProviderReference&gt;string0987654321@example.org
         &lt;/pi:DataProviderReference&gt;
         &lt;pi:DataProviderString&gt;Exemplar VoIP Provider
         &lt;/pi:DataProviderString&gt;
         &lt;pi:ProviderID&gt;urn:nena:companyid:ID123&lt;/pi:ProviderID&gt;
         &lt;pi:ProviderIDSeries&gt;NENA&lt;/pi:ProviderIDSeries&gt;
         &lt;pi:TypeOfProvider&gt;Service Provider&lt;/pi:TypeOfProvider&gt;
         &lt;pi:ContactURI&gt;sip:voip-provider@example.com&lt;/pi:ContactURI&gt;
         &lt;pi:Language&gt;en&lt;/pi:Language&gt;
         &lt;pi:DataProviderContact
            xmlns="urn:ietf:params:xml:ns:vcard-4.0"&gt;
            &lt;vcard&gt;
               &lt;fn&gt;&lt;text&gt;John Doe&lt;/text&gt;&lt;/fn&gt;
               &lt;n&gt;
                  &lt;surname&gt;John&lt;/surname&gt;
                  &lt;given&gt;Doe&lt;/given&gt;
                  &lt;additional/&gt;
                  &lt;prefix/&gt;
                  &lt;suffix/&gt;
               &lt;/n&gt;
               &lt;bday&gt;&lt;date&gt;--0203&lt;/date&gt;&lt;/bday&gt;
               &lt;anniversary&gt;
                  &lt;date-time&gt;20090808T1430-0500&lt;/date-time&gt;
               &lt;/anniversary&gt;
               &lt;gender&gt;&lt;sex&gt;M&lt;/sex&gt;&lt;/gender&gt;
               &lt;lang&gt;
                  &lt;parameters&gt;&lt;pref&gt;&lt;integer&gt;1&lt;/integer&gt;&lt;/pref&gt;
                  &lt;/parameters&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 50]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-51" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                  &lt;language-tag&gt;en&lt;/language-tag&gt;
               &lt;/lang&gt;
               &lt;org&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;text&gt;Exemplar VoIP Provider&lt;/text&gt;
               &lt;/org&gt;
               &lt;adr&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                     &lt;label&gt;&lt;text&gt;John Doe
                         123 Middle Street
                         The Sticks, IA 50055&lt;/text&gt;&lt;/label&gt;
                  &lt;/parameters&gt;
                  &lt;pobox/&gt;
                  &lt;ext/&gt;
                  &lt;street&gt;123 Middle Street&lt;/street&gt;
                  &lt;locality&gt;The Sticks&lt;/locality&gt;
                  &lt;region&gt;IA&lt;/region&gt;
                  &lt;code&gt;50055&lt;/code&gt;
                  &lt;country&gt;USA&lt;/country&gt;
               &lt;/adr&gt;
               &lt;tel&gt;
                  &lt;parameters&gt;
                     &lt;type&gt;
                        &lt;text&gt;work&lt;/text&gt;
                        &lt;text&gt;voice&lt;/text&gt;
                        &lt;text&gt;main-number&lt;/text&gt;
                     &lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;sips:john.doe@example.com&lt;/uri&gt;
               &lt;/tel&gt;
               &lt;email&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;text&gt;john.doe@example.com&lt;/text&gt;
               &lt;/email&gt;
               &lt;geo&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;work&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;geo:41.761838,-92.963268&lt;/uri&gt;
               &lt;/geo&gt;
               &lt;tz&gt;&lt;text&gt;America/Chicago&lt;/text&gt;&lt;/tz&gt;
               &lt;url&gt;
                  &lt;parameters&gt;&lt;type&gt;&lt;text&gt;home&lt;/text&gt;&lt;/type&gt;
                  &lt;/parameters&gt;
                  &lt;uri&gt;http://www.example.com/john.doe&lt;/uri&gt;
               &lt;/url&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 51]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-52" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


            &lt;/vcard&gt;
         &lt;/pi:DataProviderContact&gt;
      &lt;/pi:EmergencyCallData.ProviderInfo&gt;
      --boundary1--

     Figure 17: VoIP Provider Sending SIP INVITE with Additional Data

   Finally, the PSAP requests location information from the access
   network provider.  The response is shown in Figure 18.  Along with
   the location information, additional data is provided in the
   &lt;provided-by&gt; element of the PIDF-LO.  This request and response is
   step #4.

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;presence xmlns="urn:ietf:params:xml:ns:pidf"
   xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
   xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
   xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
   entity="pres:alice@atlanta.example.com"&gt;
      &lt;dm:device id="target123-1"&gt;
      &lt;gp:geopriv&gt;
      &lt;gp:location-info&gt;
         &lt;civicAddress
            xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"&gt;
            &lt;country&gt;US&lt;/country&gt;
            &lt;A1&gt;DE&lt;/A1&gt;
            &lt;A3&gt;Wilmington&lt;/A3&gt;
            &lt;PRD&gt;W&lt;/PRD&gt;
            &lt;RD&gt;11th&lt;/RD&gt;
            &lt;STS&gt;Street&lt;/STS&gt;
            &lt;HNO&gt;42&lt;/HNO&gt;
            &lt;NAM&gt;The Hotel DuPont&lt;/NAM&gt;
            &lt;PC&gt;19801&lt;/PC&gt;
         &lt;/civicAddress&gt;
      &lt;/gp:location-info&gt;
      &lt;gp:usage-rules&gt;
         &lt;gbp:retransmission-allowed&gt;true
         &lt;/gbp:retransmission-allowed&gt;
         &lt;gbp:retention-expiry&gt;2013-12-10T20:00:00Z
         &lt;/gbp:retention-expiry&gt;
      &lt;/gp:usage-rules&gt;
      &lt;gp:method&gt;802.11&lt;/gp:method&gt;

      &lt;gp:provided-by
         xmlns="urn:ietf:params:xml:ns:EmergencyCallData"&gt;






<span class="grey">Gellens, et al.              Standards Track                   [Page 52]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-53" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


         &lt;EmergencyCallDataReference
            purpose="EmergencyCallData.ServiceInfo"
            ref="https://example.com/ref2" /&gt;

         &lt;EmergencyCallDataValue&gt;
            &lt;EmergencyCallData.ProviderInfo
               xmlns=
               "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"&gt;
               &lt;DataProviderReference&gt;88QV4FpfZ976T@example.com
               &lt;/DataProviderReference&gt;
               &lt;DataProviderString&gt;Diamond State Exemplar
               &lt;/DataProviderString&gt;
               &lt;ProviderID&gt;urn:nena:companyid:diamond&lt;/ProviderID&gt;
               &lt;ProviderIDSeries&gt;NENA&lt;/ProviderIDSeries&gt;
               &lt;TypeOfProvider&gt;Access Network Provider&lt;/TypeOfProvider&gt;
               &lt;ContactURI&gt;tel:+1-302-555-0000&lt;/ContactURI&gt;
               &lt;Language&gt;en&lt;/Language&gt;
            &lt;/EmergencyCallData.ProviderInfo&gt;

            &lt;EmergencyCallData.Comment
               xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment"&gt;
               &lt;DataProviderReference&gt;88QV4FpfZ976T@example.com
               &lt;/DataProviderReference&gt;
               &lt;Comment xml:lang="en"&gt;This is an example text.&lt;/Comment&gt;
            &lt;/EmergencyCallData.Comment&gt;

         &lt;/EmergencyCallDataValue&gt;
      &lt;/gp:provided-by&gt;

      &lt;/gp:geopriv&gt;
      &lt;dm:deviceID&gt;mac:00-0d-4b-30-72-df&lt;/dm:deviceID&gt;
      &lt;dm:timestamp&gt;2013-07-09T20:57:29Z&lt;/dm:timestamp&gt;
      &lt;/dm:device&gt;
   &lt;/presence&gt;

           Figure 18: Access Network Provider Returning PIDF-LO
                           with Additional Data

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  XML Schemas</span>

   This section defines the XML schemas of the five data blocks.
   Additionally, the provided-by schema is specified.









<span class="grey">Gellens, et al.              Standards Track                   [Page 53]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-54" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  EmergencyCallData.ProviderInfo XML Schema</span>

   &lt;?xml version="1.0"?&gt;
   &lt;xs:schema
      targetNamespace=
           "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
      xmlns:xml="http://www.w3.org/XML/1998/namespace"
      xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
      elementFormDefault="qualified"
      attributeFormDefault="unqualified"&gt;

      &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
           schemaLocation="http://www.w3.org/2009/01/xml.xsd"/&gt;

       &lt;xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"
           schemaLocation="vcard.xsd"/&gt;

       &lt;xs:element
           name="EmergencyCallData.ProviderInfo"
           type="pi:ProviderInfoType"/&gt;

       &lt;xs:simpleType name="SubcontractorPriorityType"&gt;
          &lt;xs:restriction base="xs:string"&gt;
               &lt;xs:enumeration value="sub"/&gt;
               &lt;xs:enumeration value="main"/&gt;
          &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;

       &lt;xs:complexType name="ProviderInfoType"&gt;
               &lt;xs:sequence&gt;
                   &lt;xs:element name="DataProviderReference"
                       type="xs:token" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:element name="DataProviderString"
                       type="xs:string" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:element name="ProviderID"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="ProviderIDSeries"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="TypeOfProvider"
                       type="xs:token" minOccurs="1" maxOccurs="1"/&gt;





<span class="grey">Gellens, et al.              Standards Track                   [Page 54]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-55" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                   &lt;xs:element name="ContactURI" type="xs:anyURI"
                       minOccurs="1" maxOccurs="1"/&gt;

   &lt;xs:element name="Language" minOccurs="1" maxOccurs="unbounded"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern
   value="([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8})
   (-[a-z]{4})?(-([a-z]{2}|\d{3}))?(-([0-9a-z]{5,8}|
   \d[0-9a-z]{3}))*(-[0-9a-wyz](-[0-9a-z]{2,8})+)*
   (-x(-[0-9a-z]{1,8})+)?|x(-[0-9a-z]{1,8})+|[a-z]{1,3}
   (-[0-9a-z]{2,8}){1,2}"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;

                   &lt;xs:element name="DataProviderContact"
                       minOccurs="0" maxOccurs="1"&gt;
                     &lt;xs:complexType&gt;
                        &lt;xs:sequence&gt;
                          &lt;xs:element minOccurs="0"
                              maxOccurs="unbounded" ref="xc:vcard"/&gt;
                        &lt;/xs:sequence&gt;
                     &lt;/xs:complexType&gt;
                   &lt;/xs:element&gt;

                   &lt;xs:element name="SubcontractorPrincipal"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="SubcontractorPriority"
                       type="pi:SubcontractorPriorityType"
                       minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:any namespace="##other" processContents="lax"
                       minOccurs="0" maxOccurs="unbounded"/&gt;
               &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;

   &lt;/xs:schema&gt;

           Figure 19: EmergencyCallData.ProviderInfo XML Schema










<span class="grey">Gellens, et al.              Standards Track                   [Page 55]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-56" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  EmergencyCallData.ServiceInfo XML Schema</span>

   &lt;?xml version="1.0"?&gt;
   &lt;xs:schema
        targetNamespace=
            "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
        xmlns:xs="http://www.w3.org/2001/XMLSchema"
        xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
        xmlns:xml="http://www.w3.org/XML/1998/namespace"
        elementFormDefault="qualified"
        attributeFormDefault="unqualified"&gt;

        &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
                   schemaLocation="http://www.w3.org/2001/xml.xsd"/&gt;

       &lt;xs:element name="EmergencyCallData.ServiceInfo"
           type="svc:ServiceInfoType"/&gt;

       &lt;xs:complexType name="ServiceInfoType"&gt;
               &lt;xs:sequence&gt;
                  &lt;xs:element name="DataProviderReference"
                      type="xs:token" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:element name="ServiceEnvironment"
                     type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="ServiceType"
                     type="xs:string" minOccurs="1"
                     maxOccurs="unbounded"/&gt;

                   &lt;xs:element name="ServiceMobility"
                     type="xs:string" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:any namespace="##other" processContents="lax"
                      minOccurs="0" maxOccurs="unbounded"/&gt;
               &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;

   &lt;/xs:schema&gt;

            Figure 20: EmergencyCallData.ServiceInfo XML Schema










<span class="grey">Gellens, et al.              Standards Track                   [Page 56]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-57" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>.  EmergencyCallData.DeviceInfo XML Schema</span>

   &lt;?xml version="1.0"?&gt;
   &lt;xs:schema
        targetNamespace=
           "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
        xmlns:xs="http://www.w3.org/2001/XMLSchema"
        xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
        xmlns:xml="http://www.w3.org/XML/1998/namespace"
        elementFormDefault="qualified"
        attributeFormDefault="unqualified"&gt;

        &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
                   schemaLocation="http://www.w3.org/2001/xml.xsd"/&gt;

       &lt;xs:element name="EmergencyCallData.DeviceInfo"
           type="dev:DeviceInfoType"/&gt;

       &lt;xs:complexType name="DeviceInfoType"&gt;
               &lt;xs:sequence&gt;
                  &lt;xs:element name="DataProviderReference"
                       type="xs:token" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:element name="DeviceClassification"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="DeviceMfgr"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="DeviceModelNr"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:element name="UniqueDeviceID" minOccurs="0"
                               maxOccurs="unbounded"&gt;
                     &lt;xs:complexType&gt;
                       &lt;xs:simpleContent&gt;
                         &lt;xs:extension base="xs:string"&gt;
                           &lt;xs:attribute name="TypeOfDeviceID"
                                         type="xs:string"
                                         use="required"/&gt;
                         &lt;/xs:extension&gt;
                       &lt;/xs:simpleContent&gt;
                     &lt;/xs:complexType&gt;
                   &lt;/xs:element&gt;

                   &lt;xs:element name="DeviceSpecificData"
                       type="xs:anyURI" minOccurs="0" maxOccurs="1"/&gt;




<span class="grey">Gellens, et al.              Standards Track                   [Page 57]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-58" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                   &lt;xs:element name="DeviceSpecificType"
                       type="xs:string" minOccurs="0" maxOccurs="1"/&gt;

                   &lt;xs:any namespace="##other" processContents="lax"
                       minOccurs="0" maxOccurs="unbounded"/&gt;
               &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;

   &lt;/xs:schema&gt;

            Figure 21: EmergencyCallData.DeviceInfo XML Schema








































<span class="grey">Gellens, et al.              Standards Track                   [Page 58]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-59" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.4" href="#section-8.4">8.4</a>.  EmergencyCallData.SubscriberInfo XML Schema</span>

   &lt;?xml version="1.0"?&gt;
       &lt;xs:schema
           targetNamespace=
               "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
       xmlns:xs="http://www.w3.org/2001/XMLSchema"
       xmlns:sub=
           "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
       xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
       xmlns:xml="http://www.w3.org/XML/1998/namespace"
       elementFormDefault="qualified"
       attributeFormDefault="unqualified"&gt;

       &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
           schemaLocation="http://www.w3.org/2001/xml.xsd"/&gt;

       &lt;xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"
             schemaLocation="vcard.xsd"/&gt;

       &lt;xs:element name="EmergencyCallData.SubscriberInfo"
           type="sub:SubscriberInfoType"/&gt;

       &lt;xs:complexType name="SubscriberInfoType"&gt;
           &lt;xs:sequence&gt;
               &lt;xs:element name="DataProviderReference" type="xs:token"
                  minOccurs="1" maxOccurs="1"/&gt;
               &lt;xs:element name="SubscriberData"&gt;
                   &lt;xs:complexType&gt;
                       &lt;xs:sequence&gt;
                           &lt;xs:element ref="xc:vcard"
                           maxOccurs="unbounded"/&gt;
                       &lt;/xs:sequence&gt;
                   &lt;/xs:complexType&gt;
               &lt;/xs:element&gt;

               &lt;xs:any namespace="##other" processContents="lax"
                 minOccurs="0" maxOccurs="unbounded"/&gt;

           &lt;/xs:sequence&gt;
           &lt;xs:attribute name="privacyRequested"
              type="xs:boolean" use="required"/&gt;

       &lt;/xs:complexType&gt;
   &lt;/xs:schema&gt;

          Figure 22: EmergencyCallData.SubscriberInfo XML Schema




<span class="grey">Gellens, et al.              Standards Track                   [Page 59]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-60" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.5" href="#section-8.5">8.5</a>.  EmergencyCallData.Comment XML Schema</span>

   &lt;?xml version="1.0"?&gt;
   &lt;xs:schema
        targetNamespace=
           "urn:ietf:params:xml:ns:EmergencyCallData:Comment"
        xmlns:xs="http://www.w3.org/2001/XMLSchema"
        xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
        xmlns:xml="http://www.w3.org/XML/1998/namespace"
        elementFormDefault="qualified"
        attributeFormDefault="unqualified"&gt;

        &lt;xs:import namespace="http://www.w3.org/XML/1998/namespace"
                   schemaLocation="http://www.w3.org/2001/xml.xsd"/&gt;

       &lt;xs:element name="EmergencyCallData.Comment"
           type="com:CommentType"/&gt;

       &lt;xs:complexType name="CommentType"&gt;
               &lt;xs:sequence&gt;
                   &lt;xs:element name="DataProviderReference"
                     type="xs:token" minOccurs="1" maxOccurs="1"/&gt;

                   &lt;xs:element name="Comment"
                       type="com:CommentSubType" minOccurs="0"
                       maxOccurs="unbounded"/&gt;

                   &lt;xs:any namespace="##other" processContents="lax"
                       minOccurs="0" maxOccurs="unbounded"/&gt;
              &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;

       &lt;xs:complexType name="CommentSubType"&gt;
        &lt;xs:simpleContent&gt;
         &lt;xs:extension base="xs:string"&gt;
          &lt;xs:attribute ref="xml:lang"/&gt;
         &lt;/xs:extension&gt;
        &lt;/xs:simpleContent&gt;
       &lt;/xs:complexType&gt;

   &lt;/xs:schema&gt;

              Figure 23: EmergencyCallData.Comment XML Schema








<span class="grey">Gellens, et al.              Standards Track                   [Page 60]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-61" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-8.6" href="#section-8.6">8.6</a>.  provided-by XML Schema</span>

   This section defines the provided-by schema.

&lt;?xml version="1.0"?&gt;
&lt;xs:schema
    targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData"
    xmlns:xml="http://www.w3.org/XML/1998/namespace"
    xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
    xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
    xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
    xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
    xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
    elementFormDefault="qualified"
    attributeFormDefault="unqualified"&gt;

    &lt;xs:import
     namespace="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
     schemaLocation="ProviderInfo.xsd"/&gt;
    &lt;xs:import
     namespace="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
     schemaLocation="ServiceInfo.xsd"/&gt;
    &lt;xs:import
     namespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
     schemaLocation="DeviceInfo.xsd"/&gt;
    &lt;xs:import
     namespace="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
     schemaLocation="SubscriberInfo.xsd"/&gt;
    &lt;xs:import
     namespace="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
     schemaLocation="Comment.xsd"/&gt;
    &lt;xs:element name="EmergencyCallDataReference" type="ad:ByRefType"/&gt;
    &lt;xs:element name="EmergencyCallDataValue"
    type="ad:EmergencyCallDataValueType"/&gt;
    &lt;!-- Additional Data By Reference --&gt;
    &lt;xs:complexType name="ByRefType"&gt;
        &lt;xs:sequence&gt;
            &lt;xs:any namespace="##other" processContents="lax"
            minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;/xs:sequence&gt;
        &lt;xs:attribute name="purpose" type="xs:token" use="required"/&gt;
        &lt;xs:attribute name="ref" type="xs:anyURI" use="required"/&gt;
    &lt;/xs:complexType&gt;
    &lt;!-- Additional Data By Value --&gt;
    &lt;xs:complexType name="EmergencyCallDataValueType"&gt;
      &lt;xs:sequence&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 61]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-62" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


        &lt;xs:element ref="pi:EmergencyCallData.ProviderInfo"
                minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;xs:element ref="svc:EmergencyCallData.ServiceInfo"
                minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;xs:element ref="dev:EmergencyCallData.DeviceInfo"
                minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;xs:element ref="sub:EmergencyCallData.SubscriberInfo"
                minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;xs:element ref="com:EmergencyCallData.Comment"
                minOccurs="0" maxOccurs="unbounded"/&gt;
        &lt;xs:any namespace="##other" processContents="lax"
         minOccurs="0" maxOccurs="unbounded"/&gt;
      &lt;/xs:sequence&gt;
    &lt;/xs:complexType&gt;
&lt;/xs:schema&gt;

                     Figure 24: provided-by XML Schema

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  Security Considerations</span>

   The data structures described in this document contain information
   usually considered private.  When information is provided by value,
   entities that are a party to the SIP signaling (such as proxy servers
   and back-to-back user agents) will have access to it and need to
   protect it against inappropriate disclosure.  An entity that is able
   to eavesdrop on the SIP signaling will also have access.  Some
   Internet access types (such as in-the-clear Wi-Fi) are more
   vulnerable than others (such as 3G or 4G cellular data traffic) to
   eavesdropping.  Mechanisms that protect against eavesdropping (such
   as TLS version 1.2 or later) SHOULD be preferentially used whenever
   feasible.  (This requirement is not a "MUST" because there is an
   existing deployed base of clear-text SIP, and also because, as an
   emergency call, it is more important for the call to go through than
   for it to be protected; for example, the call MUST proceed even if
   the TLS negotiation or certificate verification fails for whatever
   reason.)  When information is provided by reference, TLS mutual
   authentication is REQUIRED.  That is, HTTPS is REQUIRED for
   dereferencing, the requester MUST use a client certificate to
   authenticate the HTTP request, and the provider of the information is
   REQUIRED to validate the credentials provided by the requester.
   While the creation of a public key infrastructure (PKI) that has
   global scope might be difficult, the alternatives to creating devices
   and services that can provide critical information securely are more
   daunting.  The provider of the information MAY enforce any policy it
   wishes to use, but PSAPs and responder agencies are strongly advised
   to deploy a PKI so that providers of additional data can check the
   certificate of the client (the requester) and decide the appropriate
   policy to enforce based on that certificate.



<span class="grey">Gellens, et al.              Standards Track                   [Page 62]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-63" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   TLS MUST be version 1.2 or later.  It is RECOMMENDED to use only
   cipher suites that offer Perfect Forward Secrecy (PFS) and avoid
   Cipher Block Chaining (CBC) and to follow the recommendations in <a href="https://www.rfc-editor.org/bcp/bcp195">BCP</a>
   <a href="https://www.rfc-editor.org/bcp/bcp195">195</a> [<a href="./rfc7525" title="&quot;Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)&quot;">RFC7525</a>].

   Ideally, the PSAP and emergency responders will be given credentials
   signed by an authority trusted by the data provider.  In most
   circumstances, nationally recognized credentials are sufficient; the
   emergency services community within a country can arrange a PKI, data
   providers can be provisioned with the root Certification Authority
   (CA) public key for the country.  Some nations are developing a PKI
   for this and related purposes.  Since calls could be made from
   devices where the device and/or the service provider(s) is not local
   to the emergency services authorities, globally recognized
   credentials are useful.  This might be accomplished by extending the
   notion of the "forest guide" described in [<a href="./rfc5582" title="&quot;Location-to-URL Mapping Architecture and Framework&quot;">RFC5582</a>] to allow the
   forest guide to provide the credential of the PKI root for areas for
   which it has coverage information, but standards for such a mechanism
   are not yet available.  In its absence, the data provider needs to
   obtain by out-of-band means the root CA credentials for any areas to
   which it is willing to provide additional data.  With the credential
   of the root CA for a national emergency services PKI, the data
   provider server can validate the credentials of an entity requesting
   additional data by reference.

   The data provider also needs a credential that can be verified by the
   emergency services to know that it is receiving data from an
   authorized server.  The emergency services authorities could provide
   credentials, distinguishable from credentials provided to emergency
   responders and PSAPs, which could be used to validate data providers.
   Such credentials would have to be acceptable to any PSAP or responder
   that could receive a call with additional data supplied by that
   provider.  This would be extensible to global credential validation
   using the forest guide as mentioned above.  In the absence of such
   credentials, the emergency services authorities could maintain a list
   of local data providers' credentials as provided to them out of band.
   At a minimum, the emergency services authorities could obtain a
   credential from the DNS entry of the domain in the additional data
   URI (e.g., using DNS-Based Authentication of Named Entities (DANE)
   [<a href="./rfc6698" title="&quot;The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA&quot;">RFC6698</a>]) to at least validate that the server is known to the
   domain providing the URI.

   When devices provide data by reference, the credential validation
   issues are similar to when service providers do so, and while the
   solutions are the same, the challenges of doing so for every device
   are obviously more difficult, especially when considering root
   certificate updates, revocation lists, etc.  However, in general,
   devices are not expected to provide data directly by reference, but



<span class="grey">Gellens, et al.              Standards Track                   [Page 63]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-64" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   rather to either provide data by value or upload the data to a server
   that can more reliably make it available and more easily enforce
   security policy.  Devices that do provide data directly by reference,
   which might include fixed-location sensors, will need to be capable
   of handling this.

   Neither service providers nor devices will supply private information
   unless the call is recognized as an emergency call.  In cellular
   telephony systems (such as those using 3GPP IMS), there are different
   procedures for an originating device to place an emergency call
   versus a normal call.  If a call that is really an emergency call is
   initiated as a normal call and the cellular service provider
   recognizes this, 3GPP IMS permits the service provider to either
   accept the call anyway or reject it with a specific code that
   instructs the device to retry the call as an emergency call.  Service
   providers ought to choose the latter, otherwise the device will not
   include the information specified in this document (since the device
   didn't recognize the call as being an emergency call).

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Privacy Considerations</span>

   This document enables functionality for conveying additional
   information about the caller and the caller's device and service to
   the callee.  Some of this information is personal data and therefore
   privacy concerns arise.  An explicit privacy indicator for
   information directly relating to the caller's identity is defined and
   use is mandatory.  However, observance of this request for privacy
   and which information it relates to is determined by the destination
   jurisdiction (which replicates functionality provided in some legacy
   emergency services systems).

   There are a number of privacy concerns with non-emergency real-time
   communication services that are also applicable to emergency calling.
   Data protection regulation worldwide has, however, decided to create
   exceptions for emergency services since the drawbacks of disclosing
   personal data are outweighed by the benefit for the emergency caller.
   Hence, the data protection rights of individuals are commonly waived
   for emergency situations.  There are, however, still various
   countries that offer some degree of anonymity for the caller towards
   PSAP call takers.

   The functionality defined in this document far exceeds the amount of
   information sharing available in the legacy POTS system.  For this
   reason, there are additional privacy threats to consider, which are
   described in more detail in [<a href="./rfc6973" title="&quot;Privacy Considerations for Internet Protocols&quot;">RFC6973</a>].






<span class="grey">Gellens, et al.              Standards Track                   [Page 64]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-65" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   Stored Data Compromise:  There is an increased risk of stored data
      compromise since additional data is collected and stored in
      databases.  Without adequate measures to secure stored data from
      unauthorized or inappropriate access at access network providers,
      service providers, end devices, as well as PSAPs, individuals are
      exposed to potential financial, reputational, or physical harm.

   Misattribution:  If the personal data collected and conveyed is
      incorrect or inaccurate, then this can lead to misattribution.
      Misattribution occurs when data or communications related to one
      individual are attributed to another.

   Identification:  By the nature of the additional data and its
      capability to provide much richer information about the caller,
      the call, and the location, the calling party is identified in a
      much better way.  Some users could feel uncomfortable with this
      degree of information sharing even in emergency services
      situations.

   Secondary Use:  There is a risk of secondary use, which is the use of
      collected information about an individual without the individual's
      consent for a purpose different from that for which the
      information was collected.  The stated purpose of the additional
      data is for emergency services purposes, but theoretically the
      same information could be used for any other call as well.
      Additionally, parties involved in the emergency call could retain
      the obtained information and reuse it for other, non-emergency
      services purposes.  While technical measures are not in place to
      prevent such secondary reuse, policy, legal, regulatory, and other
      non-technical approaches can be effective.

   Disclosure:  When the data defined in this document is not properly
      protected (while in transit with traditional communication
      security techniques and while stored using access control
      mechanisms), there is the risk of disclosure, which is the
      revelation of private information about an individual.

   To mitigate these privacy risks, the following countermeasures can be
   taken:

   In regions where callers can elect to suppress certain personally
   identifying information, network or PSAP functionality can inspect
   privacy flags within the SIP headers to determine what information
   can be passed, stored, or displayed to comply with local policy or
   law.  <a href="./rfc3325">RFC 3325</a> [<a href="./rfc3325" title="&quot;Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks&quot;">RFC3325</a>] defines the 'id' priv-value token.  The
   presence of this privacy type in a Privacy header field indicates





<span class="grey">Gellens, et al.              Standards Track                   [Page 65]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-66" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   that the user would like the network asserted identity to be kept
   private with respect to SIP entities outside the trust domain with
   which the user authenticated, including the PSAP.

   This document defines various data structures that contain privacy-
   sensitive data such as, for example, identifiers for the device
   (e.g., serial number and MAC address) or account/SIM (e.g., IMSI),
   contact information for the user, and location of the caller.  Local
   regulations may govern which data is provided in emergency calls, but
   in general, the emergency call system is aided by the information
   described in this document.  There is a trade-off between the privacy
   considerations and the utility of the data.  For protection, this
   specification requires all retrieval of data passed by reference to
   be protected against eavesdropping and alteration via communication
   security techniques (namely TLS).  Furthermore, security safeguards
   are required to prevent unauthorized access to stored data.  Various
   security incidents over at least the past few decades have shown that
   data breaches are not uncommon and are often caused by lack of proper
   access control frameworks, software bugs (such as buffer overflows),
   or missing input parsing (such as SQL injection attacks).  The risks
   of data breaches have increased with the obligation for emergency
   services to retain emergency-call-related data for extended periods
   (e.g., several years are the norm).

   Finally, it is also worth highlighting the nature of the SIP
   communication architecture, which introduces additional complications
   for privacy.  Some forms of data can be sent by value in the SIP
   signaling or by reference (a URL in the SIP signaling).  When data is
   sent by value, all intermediaries have access to the data.  As such,
   these intermediaries could also introduce additional privacy risk.
   Therefore, in situations where the conveyed information is privacy
   sensitive and intermediaries are involved, transmitting by reference
   might be appropriate, assuming the source of the data can operate a
   sufficient dereferencing infrastructure and that proper access
   control policies are available for distinguishing the different
   entities dereferencing the reference.  Without access control
   policies, any party in possession of the reference is able to resolve
   the reference and to obtain the data, including intermediaries.













<span class="grey">Gellens, et al.              Standards Track                   [Page 66]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-67" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>.  IANA Considerations</span>

<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>.  Emergency Call Additional Data Registry</span>

   This document creates a new registry called 'Emergency Call
   Additional Data' with a number of sub-registries.

   For several of the sub-registries, "Expert Review" is the criteria
   for adding new entries.  As discussed in <a href="#section-5">Section 5</a>, it can be
   counterproductive to register new types of data, and as discussed in
   <a href="#section-10">Section 10</a>, data sent as part of an emergency call can be very
   privacy sensitive.  In some cases, it is anticipated that various
   standards bodies dealing with emergency services might need to
   register new values, and in those cases, text below advises the
   designed expert to verify that the entity requesting the registration
   is relevant (e.g., a recognized emergency-services-related Standards
   Development Organization (SDO)).  In other cases, especially those
   where the trade-off between the potential benefit versus danger of
   new registrations is more conservative (such as <a href="#section-11.1.9">Section 11.1.9</a>),
   "Specification Required" is the criteria, which is a higher hurdle
   and also implicitly includes an "Expert Review".

   The following sub-registries are created for this registry.

<span class="h4"><a class="selflink" id="section-11.1.1" href="#section-11.1.1">11.1.1</a>.  Provider ID Series Registry</span>

   This document creates a new sub-registry called "Provider ID Series".
   As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under "Expert Review"
   rules.  The expert should determine that the entity requesting a new
   value is a legitimate issuer of service provider IDs suitable for use
   in Additional Call Data.

   Private entities issuing or using internally generated IDs are
   encouraged to register here and to ensure that all IDs they issue or
   use are unique.  This guarantees that IDs issued or used by the
   entity are globally unique and distinguishable from other IDs issued
   or used by the same or a different entity.  (Some organizations, such
   as NENA, issue IDs that are unique among all IDs they issue, so an
   entity using a combination of its NENA ID and the fact that it is
   from NENA is globally unique.  Other entities might not have an ID
   issued by an organization such as NENA, so they are permitted to use
   their domain name, but if so, it needs to be unique.)

   The content of this registry includes:

   Name:  An identifier to be used in the 'ProviderIDSeries' element.

   Source:  The full name of the organization issuing the identifiers.



<span class="grey">Gellens, et al.              Standards Track                   [Page 67]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-68" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   URL:  A URL to the organization for further information.

   The initial set of values is listed in Figure 1.

<span class="h4"><a class="selflink" id="section-11.1.2" href="#section-11.1.2">11.1.2</a>.  Service Environment Registry</span>

   This document creates a new sub-registry called "Service
   Environment".  As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under
   "Expert Review" rules.  The expert should determine that the entity
   requesting a new value is relevant for this service element (e.g., a
   recognized emergency-services-related SDO) and that the new value is
   distinct from existing values, and its use is unambiguous.

   The content of this registry includes:

   Token:  The value to be used in the &lt;ServiceEnvironment&gt; element.

   Description:  A short description of the value.

   The initial set of values is listed in Figure 4.

<span class="h4"><a class="selflink" id="section-11.1.3" href="#section-11.1.3">11.1.3</a>.  Service Type Registry</span>

   This document creates a new sub-registry called "Service Type".  As
   defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under "Expert Review"
   rules.  The expert should determine that the entity requesting a new
   value is relevant for this service element (e.g., a recognized
   emergency-services-related SDO) and that the requested value is
   clearly distinct from other values so that there is no ambiguity as
   to when the value is to be used or which value is to be used.

   The content of this registry includes:

   Name:  The value to be used in the &lt;ServiceType&gt; element.

   Description:  A short description of the value.

   The initial set of values is listed in Figure 5.

<span class="h4"><a class="selflink" id="section-11.1.4" href="#section-11.1.4">11.1.4</a>.  Service Mobility Registry</span>

   This document creates a new sub-registry called "Service Mobility".
   As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under "Expert Review"
   rules.  The expert should determine that the entity requesting a new
   value is relevant for this service element (e.g., a recognized
   emergency-services-related SDO) and that the requested value is
   clearly distinct from other values so that there is no ambiguity as
   to when the value is to be used or which value is to be used.



<span class="grey">Gellens, et al.              Standards Track                   [Page 68]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-69" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   The content of this registry includes:

   Token:  The value used in the &lt;ServiceMobility&gt; element.

   Description:  A short description of the value.

   The initial set of values is listed in Figure 6.

<span class="h4"><a class="selflink" id="section-11.1.5" href="#section-11.1.5">11.1.5</a>.  Type of Provider Registry</span>

   This document creates a new sub-registry called "Type of Provider".
   As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under "Expert Review"
   rules.  The expert should determine that the proposed new value is
   distinct from existing values and appropriate for use in the
   &lt;TypeOfServicerProvider&gt; element

   The content of this registry includes:

   Token:  The value used in the &lt;TypeOfProvider&gt; element.

   Description:  A short description of the type of service provider.

   The initial set of values is defined in Figure 2.

<span class="h4"><a class="selflink" id="section-11.1.6" href="#section-11.1.6">11.1.6</a>.  Device Classification Registry</span>

   This document creates a new sub-registry called "Device
   Classification".  As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates
   under "Expert Review" rules.  The expert should consider whether the
   proposed class is unique from existing classes, and the definition of
   the class will be clear to implementors and PSAPs/responders.

   The content of this registry includes:

   Token:  Value used in the &lt;DeviceClassification&gt; element.

   Description:  Short description identifying the device type.

   The initial set of values is defined in Figure 8.

<span class="h4"><a class="selflink" id="section-11.1.7" href="#section-11.1.7">11.1.7</a>.  Device ID Type Registry</span>

   This document creates a new sub-registry called "Device ID Type".  As
   defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under "Expert Review"
   rules.  The expert should ascertain that the proposed type is well
   understood and provides information that PSAPs and responders are
   able to use to uniquely identify a device.  (For example, a biometric




<span class="grey">Gellens, et al.              Standards Track                   [Page 69]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-70" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   fingerprint used to authenticate a device would not normally be used
   by a PSAP or responder to identify a device.)

   The content of this registry includes:

   Token:  The value to be placed in the &lt;TypeOfDeviceID&gt; element.

   Description:  Short description identifying the type of the device
      ID.

   The initial set of values is defined in Figure 9.

<span class="h4"><a class="selflink" id="section-11.1.8" href="#section-11.1.8">11.1.8</a>.  Device/Service Data Type Registry</span>

   This document creates a new sub-registry called "Device/Service Data
   Type".  As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under
   "Specification Required" rules, which include an explicit "Expert
   Review".  The designated expert should ascertain that the proposed
   type is well understood and provides information useful to PSAPs and
   responders.  The specification must contain a complete description of
   the data and a precise format specification suitable to allow
   interoperable implementations.

   The content of this registry includes:

   Token:  The value to be placed in the &lt;DeviceSpecificType&gt; element.

   Description:  Short description identifying the data.

   Specification:  Citation for the specification of the data.

   The initial set of values is listed in Figure 10.

<span class="h4"><a class="selflink" id="section-11.1.9" href="#section-11.1.9">11.1.9</a>.  Emergency Call Data Types Registry</span>

   This document creates a new sub-registry called "Emergency Call Data
   Types".  As defined in [<a href="./rfc5226" title="">RFC5226</a>], this registry operates under
   "Specification Required" rules, which include an explicit "Expert
   Review".  The expert is responsible for verifying that the document
   contains a complete and clear specification, and the proposed
   functionality does not obviously duplicate existing functionality.
   The expert is also responsible for verifying that the block is
   correctly categorized per the description of the categories in
   <a href="#section-1">Section 1</a>.

   The registry contains an entry for every data block that can be sent
   with an emergency call using the mechanisms as specified in this
   document.  Each data block is identified by the 'root' of its MIME



<span class="grey">Gellens, et al.              Standards Track                   [Page 70]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-71" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   media subtype (which is the part after 'EmergencyCallData.').  If the
   MIME media subtype does not start with 'EmergencyCallData.', then it
   cannot be registered here nor used in a Call-Info header field as
   specified in this document.  The subtype MAY exist under any MIME
   media type (although most commonly under 'application/', this is NOT
   REQUIRED); however, to be added to the registry, the 'root' needs to
   be unique regardless of the MIME media type.

   The content of this registry includes:

   Token:  The root of the data's MIME media subtype (not including the
      'EmergencyCallData' prefix and any suffix such as '+xml').

   Data About:  A hint as to if the block is considered descriptive of
      the call, the caller, or the location (or is applicable to more
      than one), which can help PSAPs and other entities determine if
      they wish to process the block.  Note that this is only a hint;
      entities need to consider the block's contents, not just this
      field, when determining if they wish to process the block (which
      is why the field only exists in the registry and is not contained
      within the block).  The value MUST be either 'The Call', 'The
      Caller', 'The Location', or 'Multiple'.  New values are created by
      extending this registry in a subsequent RFC.

   Reference:  The document that describes the data object.

   Note that the tokens in this registry are part of the
   'EmergencyCallData' compound value; when used as a value of the
   'purpose' parameter of a Call-Info header field, the values listed in
   this registry are prefixed by 'EmergencyCallData.' per the
   'EmergencyCallData' registration; see <a href="#section-11.2">Section 11.2</a>.

   The initial set of values is listed in Figure 25.

      +----------------+--------------+------------+
      | Token          |  Data About  | Reference  |
      +----------------+--------------+------------+
      | ProviderInfo   |   The Call   |  <a href="./rfc7852">RFC 7852</a>  |
      | ServiceInfo    |   The Call   |  <a href="./rfc7852">RFC 7852</a>  |
      | DeviceInfo     |   The Call   |  <a href="./rfc7852">RFC 7852</a>  |
      | SubscriberInfo |   The Call   |  <a href="./rfc7852">RFC 7852</a>  |
      | Comment        |   The Call   |  <a href="./rfc7852">RFC 7852</a>  |
      +----------------+--------------+------------+

                Figure 25: Additional Data Blocks Registry






<span class="grey">Gellens, et al.              Standards Track                   [Page 71]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-72" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>.  'EmergencyCallData' Purpose Parameter Value</span>

   This document defines the 'EmergencyCallData' value for the 'purpose'
   parameter of the Call-Info header field [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>].  IANA has added
   this document to the list of references for the 'purpose' value of
   Call-Info in the "Header Field Parameters and Parameter Values" sub-
   registry of the "Session Initiation Protocol (SIP) Parameters"
   registry.  Note that 'EmergencyCallData' is a compound value; when
   used as a value of the 'purpose' parameter of a Call-Info header
   field, 'EmergencyCallData' is immediately followed by a dot ('.') and
   a value from the "Emergency Call Data Types" registry; see
   <a href="#section-11.1.9">Section 11.1.9</a>.

<span class="h3"><a class="selflink" id="section-11.3" href="#section-11.3">11.3</a>.  URN Sub-Namespace Registration for &lt;provided-by&gt; Registry Entry</span>

   This section registers the namespace specified in <a href="#section-11.5.1">Section 11.5.1</a> in
   the provided-by registry established by <a href="./rfc4119">RFC 4119</a>, for usage within
   the &lt;provided-by&gt; element of a PIDF-LO.

   The schema for the &lt;provided-by&gt; element used by this document is
   specified in <a href="#section-8.6">Section 8.6</a>.

<span class="h3"><a class="selflink" id="section-11.4" href="#section-11.4">11.4</a>.  MIME Registrations</span>

<span class="h4"><a class="selflink" id="section-11.4.1" href="#section-11.4.1">11.4.1</a>.  MIME Content-Type Registration for 'application/</span>
<span class="h4">         EmergencyCallData.ProviderInfo+xml'</span>

   This specification requests the registration of a new MIME media type
   according to the procedures of <a href="./rfc6838">RFC 6838</a> [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] and guidelines in
   <a href="./rfc7303">RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Type name: application

      Subtype name: EmergencyCallData.ProviderInfo+xml

      Mandatory parameters: N/A

      Optional parameters: charset (indicates the character encoding of
      the contents)

      Encoding considerations: Uses XML, which can contain 8-bit
      characters, depending on the character encoding.  See <a href="./rfc7303#section-3.2">Section&nbsp;3.2
      of RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Security considerations: This content type is designed to carry
      the data provider information, which is a sub-category of
      additional data about an emergency call.  Since this data can
      contain personal information, appropriate precautions are needed



<span class="grey">Gellens, et al.              Standards Track                   [Page 72]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-73" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      to limit unauthorized access, inappropriate disclosure, and
      eavesdropping of personal information.  Please refer to Sections <a href="#section-9">9</a>
      and 10 for more information.

      Interoperability considerations: N/A

      Published specification: <a href="./rfc7852">RFC 7852</a>

      Applications that use this media type: Emergency Services

      Additional information:

         Magic Number: N/A

         File Extension: .xml

         Macintosh file type code: 'TEXT'

      Person and email address for further information:
      Hannes Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address &lt;ecrit@ietf.org&gt;.

      Change controller: The IESG &lt;iesg@ietf.org&gt;

<span class="h4"><a class="selflink" id="section-11.4.2" href="#section-11.4.2">11.4.2</a>.  MIME Content-Type Registration for 'application/</span>
<span class="h4">         EmergencyCallData.ServiceInfo+xml'</span>

   This specification requests the registration of a new MIME media type
   according to the procedures of <a href="./rfc6838">RFC 6838</a> [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] and guidelines in
   <a href="./rfc7303">RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Type name: application

      Subtype name: EmergencyCallData.ServiceInfo+xml

      Mandatory parameters: N/A

      Optional parameters: charset (indicates the character encoding of
      the contents)

      Encoding considerations: Uses XML, which can contain 8-bit
      characters, depending on the character encoding.  See <a href="./rfc7303#section-3.2">Section&nbsp;3.2
      of RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].




<span class="grey">Gellens, et al.              Standards Track                   [Page 73]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-74" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      Security considerations: This content type is designed to carry
      the service information, which is a sub-category of additional
      data about an emergency call.  Since this data can contain
      personal information, appropriate precautions are needed to limit
      unauthorized access, inappropriate disclosure, and eavesdropping
      of personal information.  Please refer to Sections <a href="#section-9">9</a> and <a href="#section-10">10</a> for
      more information.

      Interoperability considerations: N/A

      Published specification: <a href="./rfc7852">RFC 7852</a>

      Applications that use this media type: Emergency Services

      Additional information:

         Magic Number: N/A

         File Extension: .xml

         Macintosh file type code: 'TEXT'

      Person and email address for further information:
      Hannes Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address &lt;ecrit@ietf.org&gt;.

      Change controller: The IESG &lt;iesg@ietf.org&gt;

<span class="h4"><a class="selflink" id="section-11.4.3" href="#section-11.4.3">11.4.3</a>.  MIME Content-Type Registration for 'application/</span>
<span class="h4">         EmergencyCallData.DeviceInfo+xml'</span>

   This specification requests the registration of a new MIME media type
   according to the procedures of <a href="./rfc6838">RFC 6838</a> [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] and guidelines in
   <a href="./rfc7303">RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Type name: application

      Subtype name: EmergencyCallData.DeviceInfo+xml

      Mandatory parameters: N/A

      Optional parameters: charset (indicates the character encoding of
      the contents)




<span class="grey">Gellens, et al.              Standards Track                   [Page 74]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-75" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      Encoding considerations: Uses XML, which can contain 8-bit
      characters, depending on the character encoding.  See <a href="./rfc7303#section-3.2">Section&nbsp;3.2
      of RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Security considerations: This content type is designed to carry
      device information, which is a sub-category of additional data
      about an emergency call.  Since this data contains personal
      information, appropriate precautions need to be taken to limit
      unauthorized access, inappropriate disclosure to third parties,
      and eavesdropping of this information.  Please refer to Sections <a href="#section-9">9</a>
      and 10 for more information.

      Interoperability considerations: N/A

      Published specification: <a href="./rfc7852">RFC 7852</a>

      Applications that use this media type: Emergency Services

      Additional information:

         Magic Number: N/A

         File Extension: .xml

         Macintosh file type code: 'TEXT'

      Person and email address for further information:
      Hannes Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address &lt;ecrit@ietf.org&gt;.

      Change controller: The IESG &lt;iesg@ietf.org&gt;

<span class="h4"><a class="selflink" id="section-11.4.4" href="#section-11.4.4">11.4.4</a>.  MIME Content-Type Registration for 'application/</span>
<span class="h4">         EmergencyCallData.SubscriberInfo+xml'</span>

   This specification requests the registration of a new MIME media type
   according to the procedures of <a href="./rfc6838">RFC 6838</a> [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] and guidelines in
   <a href="./rfc7303">RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Type name: application

      Subtype name: EmergencyCallData.SubscriberInfo+xml

      Mandatory parameters: N/A



<span class="grey">Gellens, et al.              Standards Track                   [Page 75]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-76" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      Optional parameters: charset (indicates the character encoding of
      the contents)

      Encoding considerations: Uses XML, which can contain 8-bit
      characters, depending on the character encoding.  See <a href="./rfc7303#section-3.2">Section&nbsp;3.2
      of RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Security considerations: This content type is designed to carry
      owner/subscriber information, which is a sub-category of
      additional data about an emergency call.  Since this data contains
      personal information, appropriate precautions need to be taken to
      limit unauthorized access, inappropriate disclosure to third
      parties, and eavesdropping of this information.  Please refer to
      Sections <a href="#section-9">9</a> and <a href="#section-10">10</a> for more information.

      Interoperability considerations: N/A

      Published specification: <a href="./rfc7852">RFC 7852</a>

      Applications that use this media type: Emergency Services

      Additional information:

         Magic Number: N/A

         File Extension: .xml

         Macintosh file type code: 'TEXT'

      Person and email address for further information:
      Hannes Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address &lt;ecrit@ietf.org&gt;.

      Change controller: The IESG &lt;iesg@ietf.org&gt;

<span class="h4"><a class="selflink" id="section-11.4.5" href="#section-11.4.5">11.4.5</a>.  MIME Content-Type Registration for 'application/</span>
<span class="h4">         EmergencyCallData.Comment+xml'</span>

   This specification requests the registration of a new MIME media type
   according to the procedures of <a href="./rfc6838">RFC 6838</a> [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] and guidelines in
   <a href="./rfc7303">RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Type name: application




<span class="grey">Gellens, et al.              Standards Track                   [Page 76]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-77" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      Subtype name: EmergencyCallData.Comment+xml

      Mandatory parameters: N/A

      Optional parameters: charset (indicates the character encoding of
      the contents)

      Encoding considerations: Uses XML, which can contain 8-bit
      characters, depending on the character encoding.  See <a href="./rfc7303#section-3.2">Section&nbsp;3.2
      of RFC 7303</a> [<a href="./rfc7303" title="&quot;XML Media Types&quot;">RFC7303</a>].

      Security considerations: This content type is designed to carry a
      comment, which is a sub-category of additional data about an
      emergency call.  This data can contain personal information.
      Appropriate precautions are needed to limit unauthorized access,
      inappropriate disclosure to third parties, and eavesdropping of
      this information.  Please refer to Sections <a href="#section-9">9</a> and <a href="#section-10">10</a> for more
      information.

      Interoperability considerations: N/A

      Published specification: <a href="./rfc7852">RFC 7852</a>

      Applications that use this media type: Emergency Services

      Additional information:

         Magic Number: N/A

         File Extension: .xml

         Macintosh file type code: 'TEXT'

      Person and email address for further information:
      Hannes Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the IETF ECRIT
      working group, with mailing list address &lt;ecrit@ietf.org&gt;.

      Change controller: The IESG &lt;iesg@ietf.org&gt;









<span class="grey">Gellens, et al.              Standards Track                   [Page 77]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-78" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h3"><a class="selflink" id="section-11.5" href="#section-11.5">11.5</a>.  URN Sub-Namespace Registration</span>

<span class="h4"><a class="selflink" id="section-11.5.1" href="#section-11.5.1">11.5.1</a>.  Registration for urn:ietf:params:xml:ns:EmergencyCallData</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.

   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END

<span class="h4"><a class="selflink" id="section-11.5.2" href="#section-11.5.2">11.5.2</a>.  Registration for</span>
<span class="h4">         urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.








<span class="grey">Gellens, et al.              Standards Track                   [Page 78]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-79" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data:
               Data Provider Information&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
        &lt;h2&gt;Data Provider Information&lt;/h2&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END

<span class="h4"><a class="selflink" id="section-11.5.3" href="#section-11.5.3">11.5.3</a>.  Registration for</span>
<span class="h4">         urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.

   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data:
               Service Information&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 79]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-80" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
        &lt;h2&gt;Service Information&lt;/h2&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END

<span class="h4"><a class="selflink" id="section-11.5.4" href="#section-11.5.4">11.5.4</a>.  Registration for</span>
<span class="h4">         urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.

   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data:
               Device Information&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
        &lt;h2&gt;Device Information&lt;/h2&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END









<span class="grey">Gellens, et al.              Standards Track                   [Page 80]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-81" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h4"><a class="selflink" id="section-11.5.5" href="#section-11.5.5">11.5.5</a>.  Registration for</span>
<span class="h4">         urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.

   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data:
               Owner/Subscriber Information&lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
        &lt;h2&gt; Owner/Subscriber Information&lt;/h2&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END

<span class="h4"><a class="selflink" id="section-11.5.6" href="#section-11.5.6">11.5.6</a>.  Registration for</span>
<span class="h4">         urn:ietf:params:xml:ns:EmergencyCallData:Comment</span>

   This section registers a new XML namespace, as per the guidelines in
   <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

   URI:  urn:ietf:params:xml:ns:EmergencyCallData:Comment

   Registrant Contact:  IETF, ECRIT working group, &lt;ecrit@ietf.org&gt;, as
      delegated by the IESG &lt;iesg@ietf.org&gt;.







<span class="grey">Gellens, et al.              Standards Track                   [Page 81]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-82" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   XML:

      BEGIN
      &lt;?xml version="1.0"?&gt;
      &lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
        "<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>"&gt;
      &lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;
      &lt;head&gt;
        &lt;meta http-equiv="content-type"
              content="text/html;charset=iso-8859-1"/&gt;
        &lt;title&gt;Namespace for Additional Emergency Call Data:Comment
           &lt;/title&gt;
      &lt;/head&gt;
      &lt;body&gt;
        &lt;h1&gt;Namespace for Additional Data Related to an Emergency Call
           &lt;/h1&gt;
        &lt;h2&gt; Comment&lt;/h2&gt;
      &lt;p&gt;See &lt;a href="http://www.rfc-editor.org/rfc/rfc7852.txt"&gt;
         <a href="./rfc7852">RFC 7852</a>&lt;/a&gt;.&lt;/p&gt;
      &lt;/body&gt;
      &lt;/html&gt;
      END

<span class="h3"><a class="selflink" id="section-11.6" href="#section-11.6">11.6</a>.  Schema Registrations</span>

   This specification registers the following schemas, as per the
   guidelines in <a href="./rfc3688">RFC 3688</a> [<a href="./rfc3688" title="&quot;The IETF XML Registry&quot;">RFC3688</a>].

      ID: EmergencyCallData
      URI: urn:ietf:params:xml:schema:EmergencyCallData
      Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in <a href="#section-8.6">Section 8.6</a>.

      ID: EmergencyCallData:ProviderInfo
      URI: urn:ietf:params:xml:schema:EmergencyCallData:ProviderInfo
      Registrant Contact: IETF, ECRIT working group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in Figure 19.

      ID: EmergencyCallData:ServiceInfo
      URI: urn:ietf:params:xml:schema:EmergencyCallData:ServiceInfo
      Registrant Contact: IETF, ECRIT working group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in Figure 20.






<span class="grey">Gellens, et al.              Standards Track                   [Page 82]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-83" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


      ID: EmergencyCallData:DeviceInfo
      URI: urn:ietf:params:xml:schema:EmergencyCallData:DeviceInfo
      Registrant Contact: IETF, ECRIT working group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).

      XML: The XML schema can be found in Figure 21.

      ID: EmergencyCallData:SubscriberInfo
      URI: urn:ietf:params:xml:schema:EmergencyCallData:SubscriberInfo
      Registrant Contact: IETF, ECRIT working group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in <a href="#section-8.4">Section 8.4</a>.

      ID: EmergencyCallData:Comment
      URI: urn:ietf:params:xml:schema:EmergencyCallData:Comment
      Registrant Contact: IETF, ECRIT working group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in <a href="#section-8.5">Section 8.5</a>.

      ID: vcard-4.0
      URI: urn:ietf:params:xml:ns:vcard-4.0
      Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).
      XML: The XML schema can be found in <a href="#appendix-A">Appendix A</a>.

<span class="h3"><a class="selflink" id="section-11.7" href="#section-11.7">11.7</a>.  vCard Parameter Value Registration</span>

   This document registers a new value in the "vCard Parameter Values"
   registry as defined by [<a href="./rfc6350" title="&quot;vCard Format Specification&quot;">RFC6350</a>] with the following template:

   Value:  main-number

   Purpose:  The main telephone number, typically of an enterprise, as
      opposed to a direct-dial number of an individual employee

   Conformance:  This value can be used with the 'TYPE' parameter
      applied on the 'TEL' property

   Example(s):  TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90
      00











<span class="grey">Gellens, et al.              Standards Track                   [Page 83]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-84" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>.  References</span>

<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
              DOI 10.17487/RFC2119, March 1997,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.

   [<a id="ref-RFC2392">RFC2392</a>]  Levinson, E., "Content-ID and Message-ID Uniform Resource
              Locators", <a href="./rfc2392">RFC 2392</a>, DOI 10.17487/RFC2392, August 1998,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2392">http://www.rfc-editor.org/info/rfc2392</a>&gt;.

   [<a id="ref-RFC3204">RFC3204</a>]  Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
              F., Watson, M., and M. Zonoun, "MIME media types for ISUP
              and QSIG Objects", <a href="./rfc3204">RFC 3204</a>, DOI 10.17487/RFC3204,
              December 2001, &lt;<a href="http://www.rfc-editor.org/info/rfc3204">http://www.rfc-editor.org/info/rfc3204</a>&gt;.

   [<a id="ref-RFC3261">RFC3261</a>]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
              DOI 10.17487/RFC3261, June 2002,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3261">http://www.rfc-editor.org/info/rfc3261</a>&gt;.

   [<a id="ref-RFC3459">RFC3459</a>]  Burger, E., "Critical Content Multi-purpose Internet Mail
              Extensions (MIME) Parameter", <a href="./rfc3459">RFC 3459</a>,
              DOI 10.17487/RFC3459, January 2003,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3459">http://www.rfc-editor.org/info/rfc3459</a>&gt;.

   [<a id="ref-RFC3688">RFC3688</a>]  Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
              DOI 10.17487/RFC3688, January 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3688">http://www.rfc-editor.org/info/rfc3688</a>&gt;.

   [<a id="ref-RFC3966">RFC3966</a>]  Schulzrinne, H., "The tel URI for Telephone Numbers",
              <a href="./rfc3966">RFC 3966</a>, DOI 10.17487/RFC3966, December 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3966">http://www.rfc-editor.org/info/rfc3966</a>&gt;.

   [<a id="ref-RFC4119">RFC4119</a>]  Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", <a href="./rfc4119">RFC 4119</a>, DOI 10.17487/RFC4119, December 2005,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4119">http://www.rfc-editor.org/info/rfc4119</a>&gt;.

   [<a id="ref-RFC5226">RFC5226</a>]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
              DOI 10.17487/RFC5226, May 2008,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>&gt;.






<span class="grey">Gellens, et al.              Standards Track                   [Page 84]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-85" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   [<a id="ref-RFC5322">RFC5322</a>]  Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
              DOI 10.17487/RFC5322, October 2008,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5322">http://www.rfc-editor.org/info/rfc5322</a>&gt;.

   [<a id="ref-RFC5621">RFC5621</a>]  Camarillo, G., "Message Body Handling in the Session
              Initiation Protocol (SIP)", <a href="./rfc5621">RFC 5621</a>,
              DOI 10.17487/RFC5621, September 2009,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5621">http://www.rfc-editor.org/info/rfc5621</a>&gt;.

   [<a id="ref-RFC5646">RFC5646</a>]  Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
              Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc5646">RFC 5646</a>, DOI 10.17487/RFC5646,
              September 2009, &lt;<a href="http://www.rfc-editor.org/info/rfc5646">http://www.rfc-editor.org/info/rfc5646</a>&gt;.

   [<a id="ref-RFC6350">RFC6350</a>]  Perreault, S., "vCard Format Specification", <a href="./rfc6350">RFC 6350</a>,
              DOI 10.17487/RFC6350, August 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6350">http://www.rfc-editor.org/info/rfc6350</a>&gt;.

   [<a id="ref-RFC6351">RFC6351</a>]  Perreault, S., "xCard: vCard XML Representation",
              <a href="./rfc6351">RFC 6351</a>, DOI 10.17487/RFC6351, August 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6351">http://www.rfc-editor.org/info/rfc6351</a>&gt;.

   [<a id="ref-RFC6838">RFC6838</a>]  Freed, N., Klensin, J., and T. Hansen, "Media Type
              Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>,
              <a href="./rfc6838">RFC 6838</a>, DOI 10.17487/RFC6838, January 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6838">http://www.rfc-editor.org/info/rfc6838</a>&gt;.

   [<a id="ref-RFC7303">RFC7303</a>]  Thompson, H. and C. Lilley, "XML Media Types", <a href="./rfc7303">RFC 7303</a>,
              DOI 10.17487/RFC7303, July 2014,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7303">http://www.rfc-editor.org/info/rfc7303</a>&gt;.

<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>.  Informative References</span>

   [<a id="ref-ECRIT-WG-wiki">ECRIT-WG-wiki</a>]
              IETF ECRIT WG Wiki, "Additional Data Examples", July 2015,
              &lt;<a href="http://tools.ietf.org/wg/ecrit/trac/attachment/wiki/WikiStart/additional-data-examples.zip">http://tools.ietf.org/wg/ecrit/trac/attachment/wiki/</a>
              <a href="http://tools.ietf.org/wg/ecrit/trac/attachment/wiki/WikiStart/additional-data-examples.zip">WikiStart/additional-data-examples.zip</a>&gt;.

   [<a id="ref-Err3047">Err3047</a>]  RFC Errata, Erratum ID 3047, <a href="./rfc6351">RFC 6351</a>.

   [<a id="ref-HUMAN-LANG">HUMAN-LANG</a>]
              Gellens, R., "Negotiating Human Language in Real-Time
              Communications", Work in Progress, <a href="./draft-ietf-slim-negotiating-human-language-04">draft-ietf-slim-</a>
              <a href="./draft-ietf-slim-negotiating-human-language-04">negotiating-human-language-04</a>, July 2016.

   [<a id="ref-IANA-XML-Schemas">IANA-XML-Schemas</a>]
              IANA, "IETF XML Registry",
              &lt;<a href="http://www.iana.org/assignments/xml-registry">http://www.iana.org/assignments/xml-registry</a>&gt;.




<span class="grey">Gellens, et al.              Standards Track                   [Page 85]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-86" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   [<a id="ref-IEEE-1512-2006">IEEE-1512-2006</a>]
              IEEE, "IEEE Standard for Common Incident Management
              Message Sets for Use by Emergency Management Centers",
              IEEE Std 1512-2006, DOI 10.1109/IEEESTD.2006.224678,
              August 2006, &lt;<a href="https://standards.ieee.org/findstds/standard/1512-2006.html">https://standards.ieee.org/findstds/</a>
              <a href="https://standards.ieee.org/findstds/standard/1512-2006.html">standard/1512-2006.html</a>&gt;.

   [<a id="ref-LanguageSubtagRegistry">LanguageSubtagRegistry</a>]
              IANA, "Language Subtag Registry",
              &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/</a>
              <a href="http://www.iana.org/assignments/language-subtag-registry">language-subtag-registry</a>&gt;.

   [<a id="ref-LERG">LERG</a>]     Telcordia Technologies, Inc., "LERG Routing Guide", ANI
              II Digits Definitions, June 2015.

   [<a id="ref-NANP">NANP</a>]     North American Numbering Plan Administration (NANPA), "ANI
              II Digits Assignments", September 2015,
              &lt;<a href="http://nanpa.com/number_resource_info/ani_ii_assignments.html">http://nanpa.com/number_resource_info/</a>
              <a href="http://nanpa.com/number_resource_info/ani_ii_assignments.html">ani_ii_assignments.html</a>&gt;.

   [<a id="ref-nc911">nc911</a>]    North Carolina 911 Board, "Wireless 911 for
              Telecommunicators", January 2009,
              &lt;<a href="https://www.nc911.nc.gov/pdf/A_TelecommunicatorReference.pdf">https://www.nc911.nc.gov/pdf/</a>
              <a href="https://www.nc911.nc.gov/pdf/A_TelecommunicatorReference.pdf">A_TelecommunicatorReference.pdf</a>&gt;.

   [<a id="ref-NENA-02-010">NENA-02-010</a>]
              National Emergency Number Association (NENA), "NENA
              Standard Data Formats for 9-1-1 Data Exchange &amp; GIS
              Mapping", NENA-02-010, Version 9, December 2010,
              &lt;<a href="http://www.nena.org">http://www.nena.org</a>&gt;.

   [<a id="ref-RFC3325">RFC3325</a>]  Jennings, C., Peterson, J., and M. Watson, "Private
              Extensions to the Session Initiation Protocol (SIP) for
              Asserted Identity within Trusted Networks", <a href="./rfc3325">RFC 3325</a>,
              DOI 10.17487/RFC3325, November 2002,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3325">http://www.rfc-editor.org/info/rfc3325</a>&gt;.

   [<a id="ref-RFC3840">RFC3840</a>]  Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
              "Indicating User Agent Capabilities in the Session
              Initiation Protocol (SIP)", <a href="./rfc3840">RFC 3840</a>,
              DOI 10.17487/RFC3840, August 2004,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3840">http://www.rfc-editor.org/info/rfc3840</a>&gt;.

   [<a id="ref-RFC5012">RFC5012</a>]  Schulzrinne, H. and R. Marshall, Ed., "Requirements for
              Emergency Context Resolution with Internet Technologies",
              <a href="./rfc5012">RFC 5012</a>, DOI 10.17487/RFC5012, January 2008,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5012">http://www.rfc-editor.org/info/rfc5012</a>&gt;.




<span class="grey">Gellens, et al.              Standards Track                   [Page 86]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-87" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   [<a id="ref-RFC5139">RFC5139</a>]  Thomson, M. and J. Winterbottom, "Revised Civic Location
              Format for Presence Information Data Format Location
              Object (PIDF-LO)", <a href="./rfc5139">RFC 5139</a>, DOI 10.17487/RFC5139,
              February 2008, &lt;<a href="http://www.rfc-editor.org/info/rfc5139">http://www.rfc-editor.org/info/rfc5139</a>&gt;.

   [<a id="ref-RFC5491">RFC5491</a>]  Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
              Presence Information Data Format Location Object (PIDF-LO)
              Usage Clarification, Considerations, and Recommendations",
              <a href="./rfc5491">RFC 5491</a>, DOI 10.17487/RFC5491, March 2009,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5491">http://www.rfc-editor.org/info/rfc5491</a>&gt;.

   [<a id="ref-RFC5582">RFC5582</a>]  Schulzrinne, H., "Location-to-URL Mapping Architecture and
              Framework", <a href="./rfc5582">RFC 5582</a>, DOI 10.17487/RFC5582, September
              2009, &lt;<a href="http://www.rfc-editor.org/info/rfc5582">http://www.rfc-editor.org/info/rfc5582</a>&gt;.

   [<a id="ref-RFC5962">RFC5962</a>]  Schulzrinne, H., Singh, V., Tschofenig, H., and M.
              Thomson, "Dynamic Extensions to the Presence Information
              Data Format Location Object (PIDF-LO)", <a href="./rfc5962">RFC 5962</a>,
              DOI 10.17487/RFC5962, September 2010,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5962">http://www.rfc-editor.org/info/rfc5962</a>&gt;.

   [<a id="ref-RFC5985">RFC5985</a>]  Barnes, M., Ed., "HTTP-Enabled Location Delivery (HELD)",
              <a href="./rfc5985">RFC 5985</a>, DOI 10.17487/RFC5985, September 2010,
              &lt;<a href="http://www.rfc-editor.org/info/rfc5985">http://www.rfc-editor.org/info/rfc5985</a>&gt;.

   [<a id="ref-RFC6443">RFC6443</a>]  Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
              "Framework for Emergency Calling Using Internet
              Multimedia", <a href="./rfc6443">RFC 6443</a>, DOI 10.17487/RFC6443, December
              2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6443">http://www.rfc-editor.org/info/rfc6443</a>&gt;.

   [<a id="ref-RFC6698">RFC6698</a>]  Hoffman, P. and J. Schlyter, "The DNS-Based Authentication
              of Named Entities (DANE) Transport Layer Security (TLS)
              Protocol: TLSA", <a href="./rfc6698">RFC 6698</a>, DOI 10.17487/RFC6698, August
              2012, &lt;<a href="http://www.rfc-editor.org/info/rfc6698">http://www.rfc-editor.org/info/rfc6698</a>&gt;.

   [<a id="ref-RFC6848">RFC6848</a>]  Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and
              R. George, "Specifying Civic Address Extensions in the
              Presence Information Data Format Location Object (PIDF-
              LO)", <a href="./rfc6848">RFC 6848</a>, DOI 10.17487/RFC6848, January 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6848">http://www.rfc-editor.org/info/rfc6848</a>&gt;.

   [<a id="ref-RFC6881">RFC6881</a>]  Rosen, B. and J. Polk, "Best Current Practice for
              Communications Services in Support of Emergency Calling",
              <a href="https://www.rfc-editor.org/bcp/bcp181">BCP 181</a>, <a href="./rfc6881">RFC 6881</a>, DOI 10.17487/RFC6881, March 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6881">http://www.rfc-editor.org/info/rfc6881</a>&gt;.






<span class="grey">Gellens, et al.              Standards Track                   [Page 87]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-88" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


   [<a id="ref-RFC6973">RFC6973</a>]  Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
              Morris, J., Hansen, M., and R. Smith, "Privacy
              Considerations for Internet Protocols", <a href="./rfc6973">RFC 6973</a>,
              DOI 10.17487/RFC6973, July 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6973">http://www.rfc-editor.org/info/rfc6973</a>&gt;.

   [<a id="ref-RFC7035">RFC7035</a>]  Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.
              Thomson, "Relative Location Representation", <a href="./rfc7035">RFC 7035</a>,
              DOI 10.17487/RFC7035, October 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7035">http://www.rfc-editor.org/info/rfc7035</a>&gt;.

   [<a id="ref-RFC7090">RFC7090</a>]  Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
              Patel, "Public Safety Answering Point (PSAP) Callback",
              <a href="./rfc7090">RFC 7090</a>, DOI 10.17487/RFC7090, April 2014,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7090">http://www.rfc-editor.org/info/rfc7090</a>&gt;.

   [<a id="ref-RFC7525">RFC7525</a>]  Sheffer, Y., Holz, R., and P. Saint-Andre,
              "Recommendations for Secure Use of Transport Layer
              Security (TLS) and Datagram Transport Layer Security
              (DTLS)", <a href="https://www.rfc-editor.org/bcp/bcp195">BCP 195</a>, <a href="./rfc7525">RFC 7525</a>, DOI 10.17487/RFC7525, May
              2015, &lt;<a href="http://www.rfc-editor.org/info/rfc7525">http://www.rfc-editor.org/info/rfc7525</a>&gt;.






























<span class="grey">Gellens, et al.              Standards Track                   [Page 88]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-89" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  XML Schema for vCard/xCard</span>

   This section contains the vCard/xCard XML schema version of the Relax
   NG schema defined in <a href="./rfc6351">RFC 6351</a> [<a href="./rfc6351" title="&quot;xCard: vCard XML Representation&quot;">RFC6351</a>] for use with the XML schemas
   defined in this document.  In addition to mapping the Relax NG schema
   to an XML schema, this specification applies an erratum raised for
   <a href="./rfc6351">RFC 6351</a> regarding the type definition; see RFC Erratum ID 3047
   [<a href="#ref-Err3047" title="Erratum ID 3047">Err3047</a>].

   &lt;?xml version="1.0" encoding="UTF-8"?&gt;
   &lt;xs:schema
     targetNamespace="urn:ietf:params:xml:ns:vcard-4.0"
     xmlns:xs="http://www.w3.org/2001/XMLSchema"
     xmlns:ns1="urn:ietf:params:xml:ns:vcard-4.0"
     elementFormDefault="qualified"&gt;
     &lt;!--
       3.3
       iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" }
       x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" }
     --&gt;
     &lt;xs:simpleType name="iana-token"&gt;
       &lt;xs:annotation&gt;
         &lt;xs:documentation&gt;<a href="#section-3.3">Section 3.3</a>: vCard Format Specification
         &lt;/xs:documentation&gt;
       &lt;/xs:annotation&gt;
       &lt;xs:restriction base="xs:string"/&gt;
     &lt;/xs:simpleType&gt;
     &lt;xs:simpleType name="x-name"&gt;
       &lt;xs:restriction base="xs:string"/&gt;
     &lt;/xs:simpleType&gt;
     &lt;!--
       4.1
     --&gt;
     &lt;xs:element name="text" type="xs:string"/&gt;
     &lt;xs:group name="value-text-list"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:text" maxOccurs="unbounded"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;!-- 4.2 --&gt;
     &lt;xs:element name="uri" type="xs:anyURI"/&gt;
     &lt;!-- 4.3.1 --&gt;
     &lt;xs:element name="date"
         substitutionGroup="ns1:value-date-and-or-time"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern
              value="\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d"/&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 89]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-90" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 4.3.2 --&gt;
     &lt;xs:element name="time"
         substitutionGroup="ns1:value-date-and-or-time"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern value=
     "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)(Z|[+\-]\d\d(\d\d)?)?"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 4.3.3 --&gt;
     &lt;xs:element name="date-time"
       substitutionGroup="ns1:value-date-and-or-time"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern value=
     "(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?(Z|[+\-]\d\d(\d\d)?)?"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 4.3.4 --&gt;
     &lt;xs:element name="value-date-and-or-time" abstract="true"/&gt;
     &lt;!-- 4.3.5 --&gt;
     &lt;xs:complexType name="value-timestamp"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:timestamp"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:complexType&gt;
     &lt;xs:element name="timestamp"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern value="\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 4.4 --&gt;
     &lt;xs:element name="boolean" type="xs:boolean"/&gt;
     &lt;!-- 4.5 --&gt;
     &lt;xs:element name="integer" type="xs:integer"/&gt;
     &lt;!-- 4.6 --&gt;
     &lt;xs:element name="float" type="xs:float"/&gt;
     &lt;!-- 4.7 --&gt;
     &lt;xs:element name="utc-offset"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 90]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-91" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           &lt;xs:pattern value="[+\-]\d\d(\d\d)?"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 4.8 --&gt;
     &lt;xs:element name="language-tag"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:string"&gt;
           &lt;xs:pattern value=
   "([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8})(-[a-z]{4})?
   (-([a-z]{2}|\d{3}))?(-([0-9a-z]{5,8}|\d[0-9a-z]{3}))*
   (-[0-9a-wyz](-[0-9a-z]{2,8})+)*(-x(-[0-9a-z]{1,8})+)?
   |x(-[0-9a-z]{1,8})+|[a-z]{1,3}(-[0-9a-z]{2,8}){1,2}"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;!--
       5.1
     --&gt;
     &lt;xs:group name="param-language"&gt;
       &lt;xs:annotation&gt;
         &lt;xs:documentation&gt;<a href="#section-5">Section 5</a>: Parameters&lt;/xs:documentation&gt;
       &lt;/xs:annotation&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:language" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="language"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:language-tag"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.2 --&gt;
     &lt;xs:group name="param-pref"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:pref" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="pref"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="integer"&gt;
             &lt;xs:simpleType&gt;
               &lt;xs:restriction base="xs:integer"&gt;
                 &lt;xs:minInclusive value="1"/&gt;
                 &lt;xs:maxInclusive value="100"/&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 91]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-92" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


               &lt;/xs:restriction&gt;
             &lt;/xs:simpleType&gt;
           &lt;/xs:element&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.4 --&gt;
     &lt;xs:group name="param-altid"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:altid" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="altid"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.5 --&gt;
     &lt;xs:group name="param-pid"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:pid" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="pid"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="text" maxOccurs="unbounded"&gt;
             &lt;xs:simpleType&gt;
               &lt;xs:restriction base="xs:string"&gt;
                 &lt;xs:pattern value="\d+(\.\d+)?"/&gt;
               &lt;/xs:restriction&gt;
             &lt;/xs:simpleType&gt;
           &lt;/xs:element&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.6 --&gt;
     &lt;xs:group name="param-type"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:type" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="type"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="text" maxOccurs="unbounded"&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 92]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-93" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


             &lt;xs:simpleType&gt;
               &lt;xs:restriction base="xs:token"&gt;
                 &lt;xs:enumeration value="work"/&gt;
                 &lt;xs:enumeration value="home"/&gt;
               &lt;/xs:restriction&gt;
             &lt;/xs:simpleType&gt;
           &lt;/xs:element&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.7 --&gt;
     &lt;xs:group name="param-mediatype"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:mediatype" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="mediatype"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.8 --&gt;
     &lt;xs:group name="param-calscale"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:calscale" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="calscale"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="text"&gt;
             &lt;xs:simpleType&gt;
               &lt;xs:restriction base="xs:token"&gt;
                 &lt;xs:enumeration value="gregorian"/&gt;
               &lt;/xs:restriction&gt;
             &lt;/xs:simpleType&gt;
           &lt;/xs:element&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.9 --&gt;
     &lt;xs:group name="param-sort-as"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:sort-as" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 93]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-94" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


     &lt;xs:element name="sort-as"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:text" maxOccurs="unbounded"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 5.10 --&gt;
     &lt;xs:group name="param-geo"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element name="geo" minOccurs="0"&gt;
           &lt;xs:complexType&gt;
             &lt;xs:sequence&gt;
               &lt;xs:element ref="ns1:uri"/&gt;
             &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;
         &lt;/xs:element&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;!-- 5.11 --&gt;
     &lt;xs:group name="param-tz"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element name="tz" minOccurs="0"&gt;
           &lt;xs:complexType&gt;
             &lt;xs:choice&gt;
               &lt;xs:element ref="ns1:text"/&gt;
               &lt;xs:element ref="ns1:uri"/&gt;
             &lt;/xs:choice&gt;
           &lt;/xs:complexType&gt;
         &lt;/xs:element&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;!--
       6.1.3
     --&gt;
     &lt;xs:element name="source"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 94]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-95" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.1.4 --&gt;
     &lt;xs:element name="kind"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:annotation&gt;
             &lt;xs:documentation&gt;
               The text value must be one of: individual, group, org,
         location or a ns1:x-name or a ns1:iana-token value
             &lt;/xs:documentation&gt;
           &lt;/xs:annotation&gt;
           &lt;xs:element name="text" type="xs:token"
                 minOccurs="1" maxOccurs="1"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.2.1 --&gt;
     &lt;xs:element name="fn"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.2.2 --&gt;
     &lt;xs:element name="n"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-sort-as"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 95]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-96" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:surname"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:given"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:additional"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:prefix"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:suffix"
             minOccurs="0" maxOccurs="unbounded"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="surname" type="xs:string"/&gt;
     &lt;xs:element name="given" type="xs:string"/&gt;
     &lt;xs:element name="additional" type="xs:string"/&gt;
     &lt;xs:element name="prefix" type="xs:string"/&gt;
     &lt;xs:element name="suffix" type="xs:string"/&gt;
     &lt;!-- 6.2.3 --&gt;
     &lt;xs:element name="nickname"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:group ref="ns1:value-text-list"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.2.4 --&gt;
     &lt;xs:element name="photo"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 96]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-97" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.2.5 --&gt;
     &lt;xs:element name="bday"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-calscale"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:choice&gt;
             &lt;xs:element ref="ns1:value-date-and-or-time"/&gt;
             &lt;xs:element ref="ns1:text"/&gt;
           &lt;/xs:choice&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.2.6 --&gt;
     &lt;xs:element name="anniversary"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-calscale"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:choice&gt;
             &lt;xs:element ref="ns1:value-date-and-or-time"/&gt;
             &lt;xs:element ref="ns1:text"/&gt;
           &lt;/xs:choice&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 97]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-98" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


     &lt;/xs:element&gt;
     &lt;!-- 6.2.7 --&gt;
     &lt;xs:element name="gender"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:sex"/&gt;
           &lt;xs:element ref="ns1:identity" minOccurs="0"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="sex"&gt;
       &lt;xs:simpleType&gt;
         &lt;xs:restriction base="xs:token"&gt;
           &lt;xs:enumeration value=""/&gt;
           &lt;xs:enumeration value="M"/&gt;
           &lt;xs:enumeration value="F"/&gt;
           &lt;xs:enumeration value="O"/&gt;
           &lt;xs:enumeration value="N"/&gt;
           &lt;xs:enumeration value="U"/&gt;
         &lt;/xs:restriction&gt;
       &lt;/xs:simpleType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="identity" type="xs:string"/&gt;
     &lt;!-- 6.3.1 --&gt;
     &lt;xs:group name="param-label"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:label" minOccurs="0"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;xs:element name="label"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="adr"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-geo"/&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 98]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-99" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                 &lt;xs:group ref="ns1:param-tz"/&gt;
                 &lt;xs:group ref="ns1:param-label"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:pobox"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:ext"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:street"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:locality"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:region"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:code"
             minOccurs="0" maxOccurs="unbounded"/&gt;
           &lt;xs:element ref="ns1:country"
             minOccurs="0" maxOccurs="unbounded"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="pobox" type="xs:string"/&gt;
     &lt;xs:element name="ext" type="xs:string"/&gt;
     &lt;xs:element name="street" type="xs:string"/&gt;
     &lt;xs:element name="locality" type="xs:string"/&gt;
     &lt;xs:element name="region" type="xs:string"/&gt;
     &lt;xs:element name="code" type="xs:string"/&gt;
     &lt;xs:element name="country" type="xs:string"/&gt;
     &lt;!-- 6.4.1 --&gt;
     &lt;xs:element name="tel"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"
                   minOccurs="0"/&gt;
                 &lt;xs:group ref="ns1:param-pid"
                   minOccurs="0"/&gt;
                 &lt;xs:group ref="ns1:param-pref"
                   minOccurs="0"/&gt;
                 &lt;xs:element name="type" minOccurs="0"&gt;
                   &lt;xs:complexType&gt;
                     &lt;xs:sequence&gt;
                       &lt;xs:element name="text"
                         type="xs:string"
                         maxOccurs="unbounded"&gt;



<span class="grey">Gellens, et al.              Standards Track                   [Page 99]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-100" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                       &lt;/xs:element&gt;
                     &lt;/xs:sequence&gt;
                   &lt;/xs:complexType&gt;
                 &lt;/xs:element&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:choice&gt;
             &lt;xs:element ref="ns1:text"/&gt;
             &lt;xs:element ref="ns1:uri"/&gt;
           &lt;/xs:choice&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.4.2 --&gt;
     &lt;xs:element name="email"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.4.3 --&gt;
     &lt;xs:element name="impp"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 100]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-101" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.4.4 --&gt;
     &lt;xs:element name="lang"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:language-tag"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.5.1 --&gt;
     &lt;xs:group name="property-tz"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element name="tz"&gt;
           &lt;xs:complexType&gt;
             &lt;xs:sequence&gt;
               &lt;xs:element name="parameters" minOccurs="0"&gt;
                 &lt;xs:complexType&gt;
                   &lt;xs:sequence&gt;
                     &lt;xs:group ref="ns1:param-altid"/&gt;
                     &lt;xs:group ref="ns1:param-pid"/&gt;
                     &lt;xs:group ref="ns1:param-pref"/&gt;
                     &lt;xs:group ref="ns1:param-type"/&gt;
                     &lt;xs:group
                     ref="ns1:param-mediatype"/&gt;
                   &lt;/xs:sequence&gt;
                 &lt;/xs:complexType&gt;
               &lt;/xs:element&gt;
               &lt;xs:choice&gt;
                 &lt;xs:element ref="ns1:text"/&gt;
                 &lt;xs:element ref="ns1:uri"/&gt;
                 &lt;xs:element ref="ns1:utc-offset"/&gt;
               &lt;/xs:choice&gt;
             &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;
         &lt;/xs:element&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 101]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-102" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;!-- 6.5.2 --&gt;
     &lt;xs:group name="property-geo"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element name="geo"&gt;
           &lt;xs:complexType&gt;
             &lt;xs:sequence&gt;
               &lt;xs:element name="parameters" minOccurs="0"&gt;
                 &lt;xs:complexType&gt;
                   &lt;xs:sequence&gt;
                     &lt;xs:group ref="ns1:param-altid"/&gt;
                     &lt;xs:group ref="ns1:param-pid"/&gt;
                     &lt;xs:group ref="ns1:param-pref"/&gt;
                     &lt;xs:group ref="ns1:param-type"/&gt;
                     &lt;xs:group
                     ref="ns1:param-mediatype"/&gt;
                   &lt;/xs:sequence&gt;
                 &lt;/xs:complexType&gt;
               &lt;/xs:element&gt;
               &lt;xs:element ref="ns1:uri"/&gt;
             &lt;/xs:sequence&gt;
           &lt;/xs:complexType&gt;
         &lt;/xs:element&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:group&gt;
     &lt;!-- 6.6.1 --&gt;
     &lt;xs:element name="title"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.6.2 --&gt;
     &lt;xs:element name="role"&gt;
       &lt;xs:complexType&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 102]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-103" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.6.3 --&gt;
     &lt;xs:element name="logo"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.6.4 --&gt;
     &lt;xs:element name="org"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 103]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-104" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                 &lt;xs:group ref="ns1:param-sort-as"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:group ref="ns1:value-text-list"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.6.5 --&gt;
     &lt;xs:element name="member"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.6.6 --&gt;
     &lt;xs:element name="related"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:element name="type" minOccurs="0"&gt;
                   &lt;xs:complexType&gt;
                     &lt;xs:sequence&gt;
                       &lt;xs:element name="text" maxOccurs="unbounded"&gt;
                         &lt;xs:simpleType&gt;
                           &lt;xs:restriction base="xs:token"&gt;
                             &lt;xs:enumeration value="work"/&gt;
                             &lt;xs:enumeration value="home"/&gt;
                             &lt;xs:enumeration value="contact"/&gt;
                             &lt;xs:enumeration value="acquaintance"/&gt;
                             &lt;xs:enumeration value="friend"/&gt;
                             &lt;xs:enumeration value="met"/&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 104]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-105" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                             &lt;xs:enumeration value="co-worker"/&gt;
                             &lt;xs:enumeration value="colleague"/&gt;
                             &lt;xs:enumeration value="co-resident"/&gt;
                             &lt;xs:enumeration value="neighbor"/&gt;
                             &lt;xs:enumeration value="child"/&gt;
                             &lt;xs:enumeration value="parent"/&gt;
                             &lt;xs:enumeration value="sibling"/&gt;
                             &lt;xs:enumeration value="spouse"/&gt;
                             &lt;xs:enumeration value="kin"/&gt;
                             &lt;xs:enumeration value="muse"/&gt;
                             &lt;xs:enumeration value="crush"/&gt;
                             &lt;xs:enumeration value="date"/&gt;
                             &lt;xs:enumeration value="sweetheart"/&gt;
                             &lt;xs:enumeration value="me"/&gt;
                             &lt;xs:enumeration value="agent"/&gt;
                             &lt;xs:enumeration value="emergency"/&gt;
                           &lt;/xs:restriction&gt;
                         &lt;/xs:simpleType&gt;
                       &lt;/xs:element&gt;
                     &lt;/xs:sequence&gt;
                   &lt;/xs:complexType&gt;
                 &lt;/xs:element&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:choice&gt;
             &lt;xs:element ref="ns1:uri"/&gt;
             &lt;xs:element ref="ns1:text"/&gt;
           &lt;/xs:choice&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.1 --&gt;
     &lt;xs:element name="categories"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:group ref="ns1:value-text-list"/&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 105]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-106" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.2 --&gt;
     &lt;xs:element name="note"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.3 --&gt;
     &lt;xs:element name="prodid"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:text"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.4 --&gt;
     &lt;xs:element name="rev" type="ns1:value-timestamp"/&gt;
     &lt;!-- 6.7.5 --&gt;
     &lt;xs:element name="sound"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-language"/&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 106]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-107" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.6 --&gt;
     &lt;xs:element name="uid"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.7.7 --&gt;
     &lt;xs:element name="clientpidmap"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:sourceid"/&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:element name="sourceid" type="xs:positiveInteger"/&gt;
     &lt;!-- 6.7.8 --&gt;
     &lt;xs:element name="url"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.8.1 --&gt;
     &lt;xs:element name="key"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 107]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-108" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:choice&gt;
             &lt;xs:element ref="ns1:uri"/&gt;
             &lt;xs:element ref="ns1:text"/&gt;
           &lt;/xs:choice&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.9.1 --&gt;
     &lt;xs:element name="fburl"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.9.2 --&gt;
     &lt;xs:element name="caladruri"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 108]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-109" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- 6.9.3 --&gt;
     &lt;xs:element name="caluri"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element name="parameters" minOccurs="0"&gt;
             &lt;xs:complexType&gt;
               &lt;xs:sequence&gt;
                 &lt;xs:group ref="ns1:param-altid"/&gt;
                 &lt;xs:group ref="ns1:param-pid"/&gt;
                 &lt;xs:group ref="ns1:param-pref"/&gt;
                 &lt;xs:group ref="ns1:param-type"/&gt;
                 &lt;xs:group ref="ns1:param-mediatype"/&gt;
               &lt;/xs:sequence&gt;
             &lt;/xs:complexType&gt;
           &lt;/xs:element&gt;
           &lt;xs:element ref="ns1:uri"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;!-- Top-level grammar --&gt;
     &lt;xs:group name="property"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:element ref="ns1:adr" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:anniversary" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:bday" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:caladruri" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:caluri" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:categories" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:clientpidmap" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:email" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:fburl" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:fn" minOccurs="1"
           maxOccurs="unbounded"/&gt;
         &lt;xs:group ref="ns1:property-geo" minOccurs="0"



<span class="grey">Gellens, et al.              Standards Track                  [Page 109]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-110" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:impp" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:key" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:kind" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:lang" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:logo" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:member" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:n" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:nickname" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:note" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:org" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:photo" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:prodid" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:related" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:rev" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:role" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:gender" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:sound" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:source" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:tel" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:title" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:group ref="ns1:property-tz" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:element ref="ns1:uid" minOccurs="0"
           maxOccurs="1"/&gt;
         &lt;xs:element ref="ns1:url" minOccurs="0"
           maxOccurs="unbounded"/&gt;
       &lt;/xs:sequence&gt;



<span class="grey">Gellens, et al.              Standards Track                  [Page 110]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-111" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


     &lt;/xs:group&gt;
     &lt;xs:element name="vcards"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:sequence&gt;
           &lt;xs:element ref="ns1:vcard" maxOccurs="unbounded"/&gt;
         &lt;/xs:sequence&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
     &lt;xs:complexType name="vcardType"&gt;
       &lt;xs:sequence&gt;
         &lt;xs:group ref="ns1:property"/&gt;
         &lt;xs:element ref="ns1:group" minOccurs="0"
           maxOccurs="unbounded"/&gt;
         &lt;xs:any namespace="##other" processContents="lax"
           minOccurs="0" maxOccurs="unbounded"/&gt;
       &lt;/xs:sequence&gt;
     &lt;/xs:complexType&gt;
     &lt;xs:element name="vcard" type="ns1:vcardType"/&gt;
     &lt;xs:element name="group"&gt;
       &lt;xs:complexType&gt;
         &lt;xs:group ref="ns1:property"/&gt;
         &lt;xs:attribute name="name" use="required"/&gt;
       &lt;/xs:complexType&gt;
     &lt;/xs:element&gt;
   &lt;/xs:schema&gt;

<span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">Appendix B</a>.  XML Validation</span>

   This document defines a number of XML schemas and contains various
   examples.  Extracting the XML and validating the examples against the
   schemas can be challenging, especially due to the formatting
   limitations introduced by IETF RFCs.  For those readers who copy the
   XML schemas and examples directly from this document, please consider
   that errors might be introduced due to line breaks and extra
   whitespaces in the regular expressions contained in the vCard schema
   in <a href="#appendix-A">Appendix A</a>.  To validate the PIDF-LO from Figure 18, it is also
   necessary to consult the referenced RFCs and copy the schemas
   necessary for successful validation.

   The XML schemas found in this document include a 'SchemaLocation'
   attribute.  Depending on the location of the downloaded schema files,
   you may need to adjust this schema location or configure your XML
   editor to point to the location.

   For the convenience of the reader, the schemas are available at
   [<a href="#ref-IANA-XML-Schemas">IANA-XML-Schemas</a>], and the XML examples are available at the IETF
   ECRIT working group wiki page [<a href="#ref-ECRIT-WG-wiki">ECRIT-WG-wiki</a>].




<span class="grey">Gellens, et al.              Standards Track                  [Page 111]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-112" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


Acknowledgments

   This work was originally started in NENA and has benefited from a
   large number of participants involved in NENA standardization
   efforts, originally in the Long Term Definition working group, the
   Data Technical Committee, and most recently in the Additional Data
   working group.  The authors are grateful for the initial work and
   extended comments provided by many NENA participants, including
   Delaine Arnold, Marc Berryman, Guy Caron, Brian Dupras, Mark
   Fletcher, James Leyerle, Kathy McMahon, Christian Militeau, Ira
   Pyles, Matt Serra, and Robert (Bob) Sherry.  Amursana Khiyod, Robert
   Sherry, Frank Rahoi, Scott Ross, and Tom Klepetka provided valuable
   feedback regarding the vCard/xCard use in this specification.

   We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin
   Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris
   Santer, Archie Cobbs, Magnus Nystrom, Stephen Farrell, Amanda Baber,
   Dan Banks, Andrew Newton, Philip Reichl, and Francis Dupont for their
   review comments.  Alissa Cooper, Guy Caron, Ben Campbell, and Barry
   Leiba deserve special mention for their detailed and extensive review
   comments, which were very helpful and appreciated.






























<span class="grey">Gellens, et al.              Standards Track                  [Page 112]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-113" ></span>
<span class="grey"><a href="./rfc7852">RFC 7852</a>                  Additional Call Data                 July 2016</span>


Authors' Addresses

   Randall Gellens
   San Diego, CA  92121
   United States

   Email: rg+ietf@randy.pensive.org


   Brian Rosen
   NeuStar
   470 Conrad Dr.
   Mars, PA  16046
   United States

   Phone: +1 724 382 1051
   Email: br@brianrosen.net


   Hannes Tschofenig
   Hall in Tirol  6060
   Austria

   Email: Hannes.tschofenig@gmx.net
   URI:   <a href="http://www.tschofenig.priv.at">http://www.tschofenig.priv.at</a>


   Roger Marshall
   TeleCommunication Systems, Inc.
   2401 Elliott Avenue
   Seattle, WA  98121
   United States

   Phone: +1 206 792 2424
   Email: rmarshall@telecomsys.com
   URI:   <a href="http://www.telecomsys.com">http://www.telecomsys.com</a>


   James Winterbottom
   Winterb Consulting Services
   Gwynneville, NSW  2500
   Australia

   Phone: +61 448 266004
   Email: a.james.winterbottom@gmail.com






Gellens, et al.              Standards Track                  [Page 113]
</pre>