ECRIT                                                           B. Rosen
Internet-Draft                                                   NeuStar
Intended status: Standards Track                           H. Tschofenig
Expires: January 13, May 3, 2012                              Nokia Siemens Networks
                                                           July 12,
                                                             R. Marshall
                                         TeleCommunication Systems, Inc.
                                                        October 31, 2011

              Additional Data related to an Emergency Call
                draft-ietf-ecrit-additional-data-00.txt
                draft-ietf-ecrit-additional-data-02.txt

Abstract

   When an emergency call is sent to a PSAP, Public Safety Answering Point
   (PSAP), the device that sends it, as well as any service provider in
   the path of the call, or access network may have information about
   the call which the PSAP may be able to use.  This document describes
   an XML data structure that contains this kind of information in a
   standardized form.  A URI Uniform Resource Identifier (URI) that points
   to the structure can be included in the SIP signaling with the call,
   or the data may be included in the body of a SIP message.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 13, May 3, 2012.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4  6
   3.  Additional Data about a Call  Call-Info Specification  . . . . . . . . . . . . . . . . . . .  5
     3.1.  7
   4.  Data Provider Information Block  . . . . . . . . . . . . .  5
       3.1.1. . . . . .  8
     4.1.  Data Provider String . . . . . . . . . . . . . . . . .  6
       3.1.2. . .  8
     4.2.  Data Provider ID . . . . . . . . . . . . . . . . . . .  6
       3.1.3. . .  8
     4.3.  Data Provider Contact URI  . . . . . . . . . . . . . .  7
       3.1.4. . .  9
     4.4.  Data Provider Languages(s) supported Supported . . . . . . . . .  7
       3.1.5. . .  9
     4.5.  vCARD of Data Provider . . . . . . . . . . . . . . . .  8
     3.2. . . 10
     4.6.  addDataProviderInfo XML Schema . . . . . . . . . . . . . . 11
   5.  Service Information  . . . . . . . . . . . . . . . . . . .  9
       3.2.1. . . 12
     5.1.  Service Environment  . . . . . . . . . . . . . . . . .  9
       3.2.2. . . 12
     5.2.  Service Delivered by Provider to End User  . . . . . .  9
     3.3. . . 12
     5.3.  addCallSvcInfo XML Schema  . . . . . . . . . . . . . . . . 13
   6.  Device Information . . . . . . . . . . . . . . . . . . . . 10
       3.3.1. . . 15
     6.1.  Device Classification  . . . . . . . . . . . . . . . . 10
       3.3.2. . . 15
     6.2.  Device Manufacturer  . . . . . . . . . . . . . . . . . 12
       3.3.3. . . 17
     6.3.  Device Model Number  . . . . . . . . . . . . . . . . . 13
       3.3.4. . . 17
     6.4.  Unique Device Identifier . . . . . . . . . . . . . . . 13
       3.3.5. . . 17
     6.5.  Type of Device Identifier  . . . . . . . . . . . . . . 14
       3.3.6.  Device/service specific additional data structure  . . 15
     3.4.  Regulatory Information . . . . . . 18
     6.6.  Device/Service Specific Additional Data Structure Type . . 19
     6.7.  Device/Service Specific Additional Data Structure  . . . . 20
     6.8.  addDataDevInfo XML Schema  . . . . . . 16
       3.4.1.  Telephone Number Privacy Indicator . . . . . . . . . . 16
     3.5. 21
   7.  Owner/Subscriber Information . . . . . . . . . . . . . . . 17
       3.5.1. . . 22
     7.1.  vCARD for Subscriber's Data  . . . . . . . . . . . . . 17
   4. . . 22
     7.2.  addCallSub XML Schema  . . . . . . . . . . . . . . . . . . 22
   8.  Example  . . . . . . . . 18
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . 20
   6.  IANA 24
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25
   10. Privacy Considerations . . 21
     6.1.  'emergencyCallData' Purpose Parameter Value . . . . . . . 21
     6.2.  provided-by registry entry . . . . . . . . . . . 26
   11. IANA Considerations  . . . . . 21
     6.3.  MIME registrations . . . . . . . . . . . . . . . . 27
     11.1. 'emergencyCallData' Purpose Parameter Value  . . . . 21
     6.4. . . . 27
     11.2. URN Sub-Namespace Registration for
           urn:ietf:params:xml:ns:additional-data provided-by
           Registry Entry . . . . . . . . . . 21
     6.5.  Additional Data Schema Registration . . . . . . . . . . . 22
   7.  Acknowledgments . 27
     11.3. MIME Registrations . . . . . . . . . . . . . . . . . . . . 27
       11.3.1.  MIME Content-type Registration for
                'application/addDataProviderInfo+xml' . . 23
   8.  Normative References . . . . . . 27
       11.3.2.  MIME Content-type Registration for
                'application/addCallSvcInfo+xml'  . . . . . . . . . . 28

       11.3.3.  MIME Content-type Registration for
                'application/addDataDevInfo+xml'  . . . . . 24
   Authors' Addresses . . . . . 30
       11.3.4.  MIME Content-type Registration for
                'application/addCallSub+xml'  . . . . . . . . . . . . 31
     11.4. URN Sub-Namespace Registration . . . . . . . 25

1.  Introduction

   When an emergency call is sent to a PSAP, there is a rich set of data
   in the headers with . . . . . . . 32
       11.4.1.  Registration for
                urn:ietf:params:xml:ns:addDataProviderInfo  . . . . . 32
       11.4.2.  Registration for
                urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 33
       11.4.3.  Registration for
                urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 34
       11.4.4.  Registration for urn:ietf:params:xml:ns:addCallSub  . 35
     11.5. Schema Registrations . . . . . . . . . . . . . . . . . . . 36
   12. Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 38
   13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
     13.1. Normative References . . . . . . . . . . . . . . . . . . . 39
     13.2. Informational References . . . . . . . . . . . . . . . . . 39
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41

1.  Introduction

   As communications devices increasingly utilize the Internet to
   interconnect and communicate, users will expect to use such devices
   to request help.  The Internet Protocol suite provides many
   advantages but also requires re-thinking of the traditional emergency
   calling architecture.  The IETF emergency services architecture, as
   described in [I-D.ietf-ecrit-framework] and
   [I-D.ietf-ecrit-phonebcp], offers a much richer communication
   exchange and thereby better situational awareness for call takers.
   The richness comes in various forms, including the multi-media
   communication capabilities (via voice, video, instant messaging, and
   real-time text), but also via more extensive flow of information.
   Sharing information between various actors will enable more
   intelligent decision making and therefore better response in case of
   an emergency.  A pre-requisite is to offer the technical capabilities
   to let call takers to gain access to this information stored
   elsewhere (granted that they are authorized to access it).

   In general, there are four types of data exchanged:

   Data Associated with a Call:  A lot of 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, e.g., for example supported
      capabilities of the device).  This also includes information about
      the emergency caller's identity.

   Data Associated with a Location:  Location information is available
      via the PIDF-LO element, which includes civic and geospatial
      location, information about the entity that provided the data,
      information about how the location was obtained (as expressed by
      the <method> element, see Section 2.2.3 of [RFC4119], and the
      values registered in
      http://www.iana.org/assignments/method-tokens/method-tokens.xml),
      and which entity or organization supplied location information
      (beyond the domain information that can be inferred from a signing
      certificate) available via the <provided-by> element.

   Data Associated with a Caller:  This is personal data about a caller,
      including medical information.

   Data associated with a PSAP:  When a PSAP handles a call it develops
      information about the call, which must be passed to subsequent
      PSAPs, dispatchers and/or responders.

   When an emergency call is sent to a PSAP, there is a rich set of data
   in the SIP message used for the call setup, but the device, as well
   as any other service provider in the path may have even more
   information that
   would be useful to for a PSAP.  This information may include the
   identity and contact information of the service provider, subscriber
   identity and contact information, the type of service the service provider
   provides,
   offers, what kind of device the user has, etc.  Some kinds of
   devices or services have data is device
   or service dependent data.  For example, a car telematics system or
   service may have crash information.  A medical monitoring device may
   have sensor data.  While the details of the information may vary by
   device or service, there needs to be a common way to send such data to a PSAP.

   For the call takers this will enable more intelligent decision making
   and therefore better response in case of an emergency.  A pre-
   requisite is to offer the technical capabilities to let call takers
   to gain access a common way to this information stored elsewhere (granted that
   they have authorization send such data
   to access it). a PSAP.

   This document focuses on the data that can be obtained about a call
   and a mechanism for transporting it in an existing SIP header field,
   the Call-Info header. header, which is specified in Section 20.9 of
   [RFC3261].  For this purpose a new token, namely 'emergencyCallData'
   is defined to be carried in the "purpose" parameter.  If the
   "purpose" parameter is set to 'emergencyCallData' then the Call-Info
   header contains a HTTPS URL that points to a data structure with
   information about the call or a CID that allows the data structure to
   be placed in the body of the message.  In addition,  Section 8 shows a SIP INVITE
   example containing such a Call-Info header.

   Besides a service provider in the path of a call, the access network
   (which in the IETF emergency call architecture provides location in
   the form of a PIDF-LO [RFC4119]) also has similar information that
   would be valuable to the PSAP.  This information is not specific to
   the location itsef, but rather to the immmediate circumstances about
   the provision of the location (who the access network is, how to
   contact that entity, what kind of service the access network
   provides, possibly subscriber data, etc.).  This data is in nearly
   every respect similar to the data known by services providers in the
   path of the call.  For this reason, this document describes a
   "provided-by" namespace per [RFC4119] for passing information known
   to the access network network.

   The data is defined as a series of "blocks" that represent a class of
   information.  Each of the blocks is a MIME type, and an extensible
   set of these types constitute the data structure.  A registry is
   defined to list the block types that may be included.

   The data structure contains an element which itself is a URI that has
   device or service dependent data.  Thus the common Additional Data
   about a Call defined by this document contains a 'hook', in the form
   of a URI URI, for a device or service dependent data structure.

2.  Terminology

   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 RFC 2119 [RFC2119].

3.  Additional Data about a Call  Call-Info Specification

   The Additional Data about a Call is information specific to a call
   known by the device that sends it or a service provider in the path
   of a call or in the access network the call originates in.  The
   Additional Data about a Call is a set of information blocks.  Each
   block is a MIME type, and any set of blocks may be included in the
   set.

   Three

   Two mechanisms are provided to transport the data set. set, namely

   1.  A URI to the data set may MAY be inserted in a SIP INVITE or MESSAGE
       transaction with a Call-Info header containing a purpose of
       "emergenyCallData".  If the data is provided by reference, it may
       be retrieved with an HTTPS Get from the URI.  The URI MUST
       specify an HTTPS scheme, and TLS protection for the data MUST be
       negotiated.

   2.  The data may be supplied by value in a SIP INVITE or MESSAGE
       message.  In this case, Content Indirection (CID) [RFC2392] is
       used, with the CID URL pointing to the body of the message.

   More than one Call-Info header with an emergencyCallData purpose can
   be expected.  The device may MAY insert one, and any intermediary service
   provider may MAY insert its own.  When there are multiple intermediaries intermediaries,
   each intermediary may MAY each insert one.  For example, a device may
   provide one, a telematics service provider may provide one and the
   mobile carrier handling the call may provide one.

   Note: The access network may MAY supply Additional Data about a Call. additional data as well.  For
   this purpose, this document defines a namespace and adds the
   namespace to the "provided-by" registry defined by [RFC4119] PIDF-LO [RFC4119].

   Additional Data data about a Call call is defined as a series of blocks.  Each
   block is defined as a mime type, MIME objects,
   each with an XML data structure.  MIME-
   multipart structure contained inside.  MIME-multipart is
   used to enclose the set of blocks constituting XML documents and the
   information provided by an entity (service provider or device).  The sections below define the blocks.

3.1. them.

4.  Data Provider Information Block

   This block is intended to be provided by any service provider in the
   path of the call or the access network provider.  It includes
   identification and contact information.  This block SHOULD be
   provided for every service provider in the path of the call, and the
   access network provider.  Devices also use this block to provide
   identifying information.  The MIME type is "addDataProviderInfo".

3.1.1. "addDataProviderInfo+xml".

4.1.  Data Provider String

   Data Element:  Data Provider String

   Use:  Required

   XML Element:  <DataProviderString>

   Description:  This is a plain language string suitable for displaying
      the name of the service provider that created the additional data
      structure.  If the device created the structure the value is
      identical to the contact header in the SIP Invite.  This data is
      required and should reflect the contact information of the owner
      of the device. INVITE.

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

   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.

3.1.2.

4.2.  Data Provider ID

   Data Element:  Data Provider ID

   Use:  Conditional

   XML Element:  <ProviderID>

   Description:  A jurisdiction specific code for the provider shown in
      the <DataProvidedBy> element that created the structure of the
      call.  NOTE: In the US, the NENA Company ID must appear here.
      Additional information may be found at
      http://www.nena.org/nena-company-id.  The NENA Company ID shall be
      in the form of any URI for example: urn:nena:companyid:<NENA
      Company ID>.  This data is required unless the additional data
      structure is SHOULD be provided by if the device. local jurisdiction
      maintains such an ID list.  For example, in North America, this
      would be a "NENA Company ID".  Devices would not typically use
      this element.

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

   How Used by Call Taker:  Where jurisdictions have lists of providers
      the Data Provider Company ID can lead to a wealth of information
      associated with the code.

3.1.3. information.

4.3.  Data Provider Contact URI

   Data Element:  Data Provider Contact URI

   Use:  Required

   XML Element:  <ContactURI>  <ContractURI>

   Description:  For a Service Provider service provider the contact SHOULD be a 24x7 contact
      URI.  This must be a SIP URI.  If a telephone number is the
      contact address it should be provided in the form of
      sip:telephonenumber@serviceprovider:user=phone.  If the call is
      from a device, this data is required and should reflect the
      contact information of the owner of the device.  This should be a
      URI to a 24/7 support organization tasked to provide PSAP support
      for this emergency call.

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

   How Used by Call Taker:  To contact the supplier of the additional
      data provider structure.

3.1.4.

4.4.  Data Provider Languages(s) supported Supported

   Data Element:  Data Provider Language(s) supported

   Use:  Conditional
   XML Element:  <LanguagePreference>  <Language>

   Description:  Provided by's alpha 2-character code as defined in ISO
      639-1:2002
      (http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for
      the representation of names of languages -- Part 1: Alpha-2 code
      Multiple instances of this element may occur.  Order is
      significant; preferred language should appear first.  This data is
      required unless the message is from if a data only device. Data Provider Contact URI is provided.  The content
      must reflect the languages supported at the contact URI.

   Reason for Need:  Information needed to determine if 9-1-1 Authority emergency
      service authority can communicate with the Service Provider service provider or if
      language line will be needed.

   How Used by Call Taker:  If call taker cannot speak language(s)
      supported by the Service Provider, language line service provider, at translation service will
      need to be added in to the conversation.

3.1.5.

4.5.  vCARD of Data Provider

   Data Element:  vCARD of Data Provider

   Use:  Optional

   XML Element:  <DataProviderContact>

   Description:  There are many fields in the vCARD.  The vCARD and the creator of
      the data structure is encouraged to provide as much information as
      they have available.  A minimum  For encoding of subscriber provided by's name,
      address and general contact number should be provided. the vCard this specification
      uses the XML-based encoding specified in [RFC6351].

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

   How Used by Call Taker:  Assists call taker by providing additional
      contact information that may not be included in the SIP invite or
      the PIDF-LO.  Can display a picture of the caller to the call
      taker.

3.2.

4.6.  addDataProviderInfo XML Schema

 <?xml version="1.0"?>
 <xs:schema
      targetNamespace="urn:ietf:params:xml:ns:addDataProviderInfo"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:ad="urn:ietf:params:xml:ns:addDataProviderInfo"
      xmlns:xml="http://www.w3.org/XML/1998/namespace"
      xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"
      elementFormDefault="qualified" attributeFormDefault="unqualified">

      <xs:import namespace="http://www.w3.org/XML/1998/namespace"
                 schemaLocation="http://www.w3.org/2001/xml.xsd"/>

      <xs:simpleType name="iso3166a2">
        <xs:restriction base="xs:token">
          <xs:pattern value="[A-Z]{2}"/>
        </xs:restriction>
      </xs:simpleType>

     <xs:element name="DataAssociatedWithCall">
         <xs:complexType>
             <xs:sequence>
                 <xs:element name="DataProviderString"
                     type="xs:string" minOccurs="1" maxOccurs="1"/>
                 <xs:element name="DataProviderString"
                     type="xs:string" minOccurs="1" maxOccurs="1"/>
                 <xs:element name="ContactURI" type="xs:anyURI"
                     minOccurs="1" maxOccurs="1"/>
                 <xs:element name="Language" type="ad:iso3166a2"
                     minOccurs="0" maxOccurs="unbounded" />
                 <xs:element name="DataProviderContact"
                     type="vc:vcards" minOccurs="0" maxOccurs="1">
             </xs:sequence>
         </xs:complexType>
     </xs:element>
 </xs:schema>

                 Figure 1: addDataProviderInfo XML Schema

5.  Service Information

   This block describes the service that the service provider provides
   to the caller.  It SHOULD be included by all SPs in the path of the
   call.  The mime type is "addCallSvcInfo"

3.2.1. "addCallSvcInfo+xml".

5.1.  Service Environment

   Data Element:  Service Environment

   Use:  Required

   XML Element:  <SvcEnvironment>

   Description:  This element defines if the whether a call service type is from a Business business
      or
      Residence residence caller.  Currently, the only valid entries are Business
      'Business' or Residence. 'Residence'.

   Reason for Need:  To assist in determining equipment and manpower
      requirements.

   How Used by Call Taker:  Information may be used to determine
      equipment and manpower requirements for emergency responders.

3.2.2.

5.2.  Service Delivered by Provider to End User

   Data Element:  Service Delivered by Provider to End User

   Use:  Required

   XML Element:  <SvcDelByProvider>

   Description:  This defines the type of service the end user has
      subscribed to.  The implied mobility of this service can not be
      relied upon.  A registry will reflect the following initial valid
      entries:

      *  Mobile Telephone Service: Includes Satellite, CDMA, GSM, Wi-Fi,
         WiMAX, LTE (Long Term Evolution)

      *  Fixed Public Pay/Coin telephones: Any coin or credit card
         operated device.

      *  One way outbound service

      *  Inmate call/service

      *  Soft dialtone/quick service/warm disconnect/suspended

      *  Multi-line telephone system (MLTS): Includes all PBX, Centrex,
         key systems, Shared Tenant Service.

      *  Sensor, unattended: Includes devices that generate DATA ONLY.
         This is one-way information exchange and there will be no other
         form of communication.

      *  Sensor, attended: Includes devices that are supported by a
         monitoring service provider or automatically open a two-way
         communication path.

      *  Wireline: Plain Old Telephone Service (POTS).

      *  VoIP Telephone Service: A type of service that offers
         communication over internet protocol, such as Fixed, Nomadic,
         Mobile, Unknown

      There can be more than one value returned.  For example, a VoIP
      prison telephone service is a reasonable conbination.

   Reason for Need:  Knowing the type of service may assist the PSAP
      with the handling of the call.

   How Used by Call Taker:  Calltaker may be able  Calltakers often use this information to
      determine if the
      caller is stationary or mobile what kinds of questions to ask callers, and if they will have voice
      communications with the caller or how much to
      rely on supportive information.  An emergency call from a prison
      is it treated differently that a data only event.

3.3. call from a sensor device.

5.3.  addCallSvcInfo XML Schema
 <?xml version="1.0"?>
 <xs:schema
      targetNamespace="urn:ietf:params:xml:ns:addCallSvcInfo"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:svc="urn:ietf:params:xml:ns:addCallSvcInfo"
      xmlns:xml="http://www.w3.org/XML/1998/namespace"
      elementFormDefault="qualified" attributeFormDefault="unqualified">

      <xs:import namespace="http://www.w3.org/XML/1998/namespace"
                 schemaLocation="http://www.w3.org/2001/xml.xsd"/>

     <xs:element name="addCallSvcInfo">
         <xs:complexType>
             <xs:sequence>
                 <xs:element name="SvcEnvironment"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="SvcDelByProvider"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
             </xs:sequence>
         </xs:complexType>
     </xs:element>
 </xs:schema>

                    Figure 2: addCallSvcInfo XML Schema

6.  Device Information

   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 type is
   "addDataDevInfo".

3.3.1.
   "addDataDevInfo+xml".

6.1.  Device Classification

   Data Element:  Device Classification

   Use:  Optional

   XML Element:  <DeviceClassification>

   Description:  If the device provides the data structure, the device
      information should be provided.  If the Service Provider service provider provides
      the structure and it knows what the device is, the Service
      Provider service
      provider should provide the device information.  Often the carrier
      does not know what the device is.  It is possible to receive 2
      data structures, one created by the device and one created by the
      Service Provider.
      service provider.  Information about the device, not how it is
      being used.  This data element defines the kind of device making
      the emergency call.  A registry will reflect the following valid
      entries:

      *  Cordless handset

      *  Fixed phone

      *  Mobile handset

      *  ATA - analog terminal adapter

      *  Satellite phone

      *  Stationary computing device (alarm system, data sensor)

      *  Guardian devices

      *  Desktop PC

      *  Laptop computing device
      *  Tablet computing device

      *  Alarm system

      *  Data sensor

      *  Personal beacons (spot)

      *  Auto telematics (indicates VEDS data set)

      *  Trucking telematics

      *  Farm equipment telematics

      *  Marine telematics

      *  PDA (personal digital assistant)

      *  PND (personal navigation device)

      *  Smart phone

      *  Internet tablet

      *  Gaming console

      *  Video phone

      *  Other text device

      *  Not Available

   Reason for Need:  The device classification describes the capability
      of the calling device.  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 rebid for location or condition changes?  Is this device
      interactive or a one-way reporting device?

   How Used by Call Taker:  May assist with location of caller.  For
      example, a cordless handset may be outside or next door.  May
      provide calltaker some context about the caller.

3.3.2.  Device Manufacturer

   Data Element:  Device Manufacturer

   Use:  Optional

   XML Element:  <DeviceMfgr>
   Description:  Manufacturer is electronically stored on the device.
      Different devices may use different conventions to provide their
      information.  We need to know what it represents, so a registry is
      in order.  Need to be able to standardize as much as possible with
      a uniform naming convention.  A registry will reflect some context about the valid
      entries. caller.

6.2.  Device Manufacturer

   Data Element:  Device Manufacturer

   Use:  Optional

   XML Element:  <DeviceMfgr>

   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 calltaker, but by PSAP
      management.

3.3.3.

6.3.  Device Model Number

   Data Element:  Device Model Number

   Use:  Optional

   XML Element:  <DeviceModelNr>

   Description:  Model number is electronically stored on of the device.

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

   How Used by Call Taker:  Probably not used by calltaker, but by PSAP
      management.

3.3.4.

6.4.  Unique Device Identifier
   Data Element:  Unique Device Identifier

   Use:  Optional

   XML Element:  <UniqueDeviceID>

   Description:  Characters  String that identify the specific device making the
      call or creating an event.

   Reason for Need:  May be needed when trying to obtain a subpoena  Uniquely identifies the device as opposed to
      obtain customer information any
      signaling identifiers encountered in instances where location info did
      not display or someone is making false emergency calls.  May also
      be used when working with safe houses that are using non-
      initialized phones. the call signaling stream.

   How Used by Call Taker:  Probably not used by calltaker they would
      need to refer to management for investigation.

3.3.5.

6.5.  Type of Device Identifier

   Data Element:  Type of Device Identifier

   Use:  Optional

   XML Element:  <TypeOfDeviceID>

   Description:  Identifies the type of device identifier being
      generated in the unique device identifier data element.  A
      registry will reflect the following valid entries:

      *  MEID (CDMA)

      *  ESN (Electronic Serial Number - superseded by MEID)

      *  MAC (Media Access Control) Address - any IEEE device with an
         Ethernet, Wi-Fi connection

      *  WiMAX has a device certificate

      *  IMEI (International Mobile Equipment Identifier - GSM)

      *  Unique Device Identifier (Unique identifier for medical
         devices)

      *  RFID (Radio Frequency Identification)

      *  Sensors (types to be identified in a future document version)

      *  Manufacturer Serial Number

      *  Other

   Reason for Need:  Calls from uninitiated devices would give an
      identifier that could be associated with erroneous calls --- use
      the number to identify what type of capabilities there are.  Could
      also use this information  Identifies how to block specific types of calls. interpret the Unique Device
      Identifier.

   How Used by Call Taker:  Additional information that may be used to
      assist with call handling.

3.3.6.  Device/service specific additional data structure

6.6.  Device/Service Specific Additional Data Structure Type

   Data Element:  Type of Device/service specific additional data
      structure

   Use:  Optional  Conditional.  MUST be provided when Device/service specific
      additional URI is provided

   XML Element:  <devicespecificSchema>  <devicespecificType>

   Description:  A URI representing additional data whose schema is
      specific  Value from a registry defined by this document to
      describe the device or service which created it.  An example is
      the VEDs structure for a vehicle telematics device.  The structure type of data that can be referenced via URI and used in retrieved from the policy routing function
      business rules/policies or for access by call takers or
      responders.  Non-NENA XML schemas must be registered.  Some
      possible sources Device/
      service specific additional data structure.  Initial values are:

      *  NPAC

      *  Hazmat International Association of Fire Chiefs

      *  DHS/EPA E-Plan for HazMat

      *  NFPA - National Fire Protection Association

      *  National Alliance for Public Safety GIS (NA-PSG)

      *  US DOT Pipeline and Hazardous Materials Safety Administration
         (PHMSA) examples of additional data.

      *  Fire Service data.

      *  Fire Service Data Model
      *  IEEE 1512 - USDOT Model for traffic incidents

      *  Smart Building (NIST)

      *  VEDS

   Reason for Need:  This data element will allow for identification of
      externally defined schemas, which may have additional data that
      will assist in emergency response.

   How Used by Call Taker:  This data element will allow the end user
      (calltaker or first responder) to know what type of additional
      data may be available to aid in providing the needed emergency
      services.

6.7.  Device/Service Specific Additional Data Model

      *  IEEE 1512 - USDOT Model Structure

   Data Element:  Device/service specific additional data structure

   Use:  Optional

   XML Element:  <devicespecificSchema>

   Description:  A URI representing additional data whose schema is
      specific to the device or service which created it.  An example is
      the VEDs structure for traffic incidents
      *  Smart Building (NIST)

      *  VEDS a vehicle telematics device.  The URI, when
      dereferenced, MUST yield a data structure defined by the Device/
      service specific additional data type value.  Different data may
      be created by each classification; i.e., telematics creates VEDS
      data set - can be different types of data depending on device.
      May want to describe type of data for each
      device. data for each device.

   Reason for Need:  Provides device/service specific data that may 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.

6.8.  addDataDevInfo XML Schema

 <?xml version="1.0"?>
 <xs:schema
      targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:svc="urn:ietf:params:xml:ns:addDataDevInfo"
      xmlns:xml="http://www.w3.org/XML/1998/namespace"
      elementFormDefault="qualified" attributeFormDefault="unqualified">

      <xs:import namespace="http://www.w3.org/XML/1998/namespace"
                 schemaLocation="http://www.w3.org/2001/xml.xsd"/>

     <xs:element name="addCallSvcInfo">
         <xs:complexType>
             <xs:sequence>
                 <xs:element name="DeviceClassification"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="DeviceMfgr"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="DeviceModelNr"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="UniqueDeviceID"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="TypeOfDeviceID"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                <xsd:element name="devicespecificType"
                     type="xs:string" minOccurs="0" maxOccurs="1"/>
                 <xsd:element name="devicespecificSchema"
                     type="xsd:anyURI" minOccurs="0" maxOccurs="1"/>
             </xs:sequence>
         </xs:complexType>
     </xs:element>
 </xs:schema>

                    Figure 3: addDataDevInfo XML Schema

7.  Owner/Subscriber Information

   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 type is "addCallSub+xml".

7.1.  vCARD for Subscriber's Data

   Data Element:  vCARD for Subscriber's Data

   Use:  Required

   XML Element:  <SubscriberData>

   Description:  Information known by the service provider or device
      about the subscriber; i.e., Name, Address, Calling Party Number,
      Main Telephone Number and any other data.  If the subscriber is an
      enterprise, this is the vCARD of the enterprise and the Company
      Name is used not the Name of the Caller.  The telephone number is
      the main telephone number at the location of the call.  The
      address should be where the call is originating from.

   Reason for Need:  This data element will allow  Critical information required for identification of
      externally defined schemas, which may have additional data that
      will assist in emergency response. proper call
      handling and dispatching.

   How Used by Call Taker:  This data element will allow the end user
      (calltaker or first responder)  Critical information required for proper
      call handling and dispatching.

7.2.  addCallSub XML Schema
 <?xml version="1.0"?>
 <xs:schema
      targetNamespace="urn:ietf:params:xml:ns:addCallSub"
      xmlns:xs="http://www.w3.org/2001/XMLSchema"
      xmlns:sub="urn:ietf:params:xml:ns:addCallSub"
      xmlns:xml="http://www.w3.org/XML/1998/namespace"
      xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"
      elementFormDefault="qualified" attributeFormDefault="unqualified">

      <xs:import namespace="http://www.w3.org/XML/1998/namespace"
                 schemaLocation="http://www.w3.org/2001/xml.xsd"/>

     <xs:element name="addCallSub">
         <xs:complexType>
             <xs:sequence>
                 <xs:element name="SubscriberData"
                     type="vc:vcards" minOccurs="0" maxOccurs="1">
             </xs:sequence>
         </xs:complexType>
     </xs:element>
 </xs:schema>

                      Figure 4: addCallSub XML Schema

8.  Example

     INVITE sips:bob@biloxi.example.com SIP/2.0
     Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
     Max-Forwards: 70
     To: Bob <sips:bob@biloxi.example.com>
     From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
     Call-ID: 3848276298220188511@atlanta.example.com
     Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
       <http://www.example.com/alice/> ;purpose=info,
       <cid:1234567890@atlanta.example.com> ;purpose=emergencyCallData
     Geolocation: <cid:target123@atlanta.example.com>
     Geolocation-Routing: no
     Accept: application/sdp, application/pidf+xml
     CSeq: 31862 INVITE
     Contact: <sips:alice@atlanta.example.com>
     Content-Type: multipart/mixed; boundary=boundary1

     Content-Length: ...

     --boundary1

     Content-Type: application/sdp

     ...SDP goes here

     --boundary1

     Content-Type: application/pidf+xml
     Content-ID: <target123@atlanta.example.com>

     ...PIDF-LO goes here

     --boundary1--

     Content-Type: application/pidf+xml
     Content-ID: <1234567890@atlanta.example.com>

     ...Additional Data goes here

     --boundary1--

        Example: Attaching Additional Data via CID to know what type of additional a SIP INVITE

9.  Security Considerations

   The information in this data may structure will usually be available considered
   private.  HTTPS is specified to aid in providing require the needed emergency
      services.

3.4.  Regulatory Information

   In some jurisdictions, handling provider of emergency calls involves the
   information known by to validate the credentials of the requester.  While the
   creation of a service provider PKI that must, by regulation, has global scope may be
   passed difficult, the
   alternatives to creating devices and services that can provide
   critical information securely are more daunting.

   The Call-info header with purpose='emergencyCallData' MUST only be
   sent on an emergency call, which can be ascertained by the presence
   of an emergency system.  The mime type is "addCallReg".

3.4.1.  Telephone Number Privacy Indicator

   Data Element:  Telephone Number service urn in a Route header of a SIP message.

   <how recipient validates credentials of sender>

   <how sender validates credentials of recipient>

   <how sender validates credentials of anyone requesting device
   dependent data>

10.  Privacy Indicator

   Use:  Required

   XML Element:  <TNPrivacyIndicator>

   Description:  Some State regulations require that Non-Published
      subscriber name remains private Considerations

   [Editor's Note: The privacy considerations outlined in
   [I-D.iab-privacy-considerations] need to all including 9-1-1.  Where be addressed here in a
   future version of this regulation document.

   There is much private data in place, the end user's name this information.  Local regulations
   may govern what data must be overlaid
      with blanks or the verbiage, "Non-Published Number."

   Reason for Need:  Some State regulations require that Non-Published
      subscriber name remains private to all including provided in emergency calls.
      Where this regulation is calls, but in place, the end user's name must be
      overlaid with blanks or
   general, the verbiage, "Non-Published Number".

   How Used by Call Taker:  This emergency call system is not beneficial to PSAPs; however,
      they must follow state regulations.  This indicator will allow for
      coding that overlays often aided by the non-published subscriber name with kinds of
   information described in this document.  There is a tradeoff between
   the
      verbiage "Non-Published Number."

3.5.  Owner/Subscriber Information

   This block describes privacy considerations and the owner utility of the device (if provided by data.  Certainly,
   if the
   device) or data cannot be protected, due to failure of the subscriber information, if provided TLS mechanisms
   described here, data not required by a service
   provider. regulation SHOULD not be sent.

11.  IANA Considerations

   [Editor's Note: The contact location IANA section is NOT necessarily missing the location description of new
   registries.  A future version of this draft will contain the caller or incident, but is rather
   necessary information.]

11.1.  'emergencyCallData' Purpose Parameter Value

   This document defines the nominal contact address.
   The mime type is "addCallSub".

3.5.1.  vCARD for Subscriber's Data

   Data Element:  vCARD 'emergencyCallData' value for Subscriber's Data

   Use:  Required

   XML Element:  <SubscriberData>

   Description:  Information known by the Service Provider about "purpose"
   parameter of the
      subscriber; i.e., Name, Address, Calling Party Number, Main
      Telephone Number Call-Info header field.  The Call-Info header and any other data.  If
   the subscriber is an
      enterprise, this is corresponding registry for the 'purpose' parameter was
   established with RFC 3261 [RFC3261].

      Header       Parameter   New
      Field        Name        Value               Reference
      ----------   ---------   -----------------   ---------
      Call-Info    purpose     emergencyCallData   [This RFC]

11.2.  URN Sub-Namespace Registration for provided-by Registry Entry

   This section registers the namespace specified in ??? in the vCARD
   provided-by registry established by RFC 4119.

11.3.  MIME Registrations

11.3.1.  MIME Content-type Registration for 'application/
         addDataProviderInfo+xml'

   This specification requests the registration of a new MIME type
   according to the enterprise procedures of RFC 4288 [RFC4288] and guidelines in
   RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: addDataProviderInfo+xml

      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of enclosed XML.

      Encoding considerations:

      Uses XML, which can employ 8-bit characters, depending on the Company
      Name is used not the Name
      character encoding used.  See Section 3.2 of the Caller.  The telephone number RFC 3023 [RFC3023].

      Security considerations:

      This content type is designed to carry the main telephone number at the location data provider
      information, which is a sub-category of the additional data about an
      emergency call.  The
      address should be where the call is originating from.

   Reason for Need:  Critical

      Since this data contains personal information required for proper call
      handling appropriate
      precautions have to be taken to limit unauthorized access,
      inappropriate disclosure to third parties, and dispatching.

   How Used by Call Taker:  Critical information required eavesdropping of
      this information.  Please refer to Section 9 and Section 10 for proper
      call handling
      more information.

      Interoperability considerations: None

      Published specification: [TBD: This specification]

      Applications which use this media type: Emergency Services

      Additional information:

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'

      Personal and dispatching.

4.  XML Schema

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

      Intended usage: LIMITED USE

      Author: This section specification is not yet updated.

   <?xml version="1.0" encoding="UTF-8"?>
   <xsd:schema
       xmlns:xsd="http://www.w3.org/2001/XMLSchema"
       xmlns="urn:nena:xml:ns:es:NG:Call"
       targetNamespace="urn:nena:xml:ns:es:NG:Call"
       elementFormDefault="qualified"
       attributeFormDefault="unqualified" version="1.0">
       <xsd:include schemaLocation="NGTypeLib.xsd"/>
       <xsd:element name="DataAssociatedWithCall">
           <xsd:complexType>
               <xsd:sequence>
                   <xsd:element name="DataProvidedBy"
                       type="sourceProviderType" minOccurs="0"/>
                   <xsd:element ref="CallerDataURL" minOccurs="0"/>
                   <xsd:element ref="ServiceEnvironment"/>
                   <xsd:element ref="ServiceDeliveredByProvider"/>
                   <xsd:element ref="DeviceClassification"/>
                   <xsd:element ref="DeviceManufacturer"/>
                   <xsd:element name="DeviceModel" type="xsd:token"/>
                   <xsd:element name="DeviceID" type="xsd:token"/>
                   <xsd:element ref="DeviceIDType"/>
                   <xsd:element name="DeviceSpecificSchema"
                       type="ExtensionType" minOccurs="0"/>
                   <xsd:element ref="PrivacyIndicator"/>
                   <xsd:element ref="SubscribervCARD"/>
               </xsd:sequence>
           </xsd:complexType>
       </xsd:element>
       <xsd:element name="CallerDataURL" type="xsd:anyURI">
       </xsd:element>
       <xsd:element name="ServiceDeliveredByProvider" type="xsd:token">
       </xsd:element>
       <xsd:element name="DeviceClassification" type="xsd:token">
       </xsd:element>
       <xsd:element name="DeviceManufacturer" type="xsd:token">
       </xsd:element>
       <xsd:element name="DeviceIDType" type="xsd:token">
       </xsd:element>
       <xsd:element name="PrivacyIndicator" type="privacyIndicatorType">
       </xsd:element>
       <xsd:simpleType name="privacyIndicatorType">
           <xsd:restriction base="xsd:token">
               <xsd:enumeration value="Published"/>
               <xsd:enumeration value="Non-Published"/>
           </xsd:restriction>
       </xsd:simpleType>
       <xsd:element name="SubscribervCARD" type="vCARDType">
       </xsd:element>
   </xsd:schema>

                           Figure 1: XML Schema

5.  Security Considerations a work item of the IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The information IESG <ietf@ietf.org>

11.3.2.  MIME Content-type Registration for 'application/
         addCallSvcInfo+xml'

   This specification requests the registration of a new MIME type
   according to the procedures of RFC 4288 [RFC4288] and guidelines in
   RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: addCallSvcInfo+xml
      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of enclosed XML.

      Encoding considerations:

      Uses XML, which can employ 8-bit characters, depending on the
      character encoding used.  See Section 3.2 of RFC 3023 [RFC3023].

      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 structure will usually contains personal information appropriate
      precautions have to be considered
   private.  HTTPS is specified taken to require the provider limit unauthorized access,
      inappropriate disclosure to third parties, and eavesdropping of the
   information
      this information.  Please refer to validate the credentials Section 9 and Section 10 for
      more information.

      Interoperability considerations: None

      Published specification: [TBD: This specification]

      Applications which use this media type: Emergency Services

      Additional information:

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'

      Personal 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 requester.  While IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The IESG <ietf@ietf.org>

11.3.3.  MIME Content-type Registration for 'application/
         addDataDevInfo+xml'

   This specification requests the
   creation registration of a PKI that has global scope may be difficult, the
   alternatives new MIME type
   according to creating devices the procedures of RFC 4288 [RFC4288] and services that can provide
   critical information securely are more daunting.

   The Call-info header with purpose='emergencyCallData' MUST only be
   sent on an emergency call, guidelines in
   RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: addDataDevInfo+xml

      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of enclosed XML.

      Encoding considerations:

      Uses XML, which can be ascertained by employ 8-bit characters, depending on the presence
      character encoding used.  See Section 3.2 of RFC 3023 [RFC3023].

      Security considerations:

      This content type is designed to carry the device information
      information, which is a sub-category of additional data about an
      emergency service urn in a Route header call.

      Since this data contains personal information appropriate
      precautions have to be taken to limit unauthorized access,
      inappropriate disclosure to third parties, and eavesdropping of
      this information.  Please refer to Section 9 and Section 10 for
      more information.

      Interoperability considerations: None

      Published specification: [TBD: This specification]

      Applications which use this media type: Emergency Services

      Additional information:

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'
      Personal and email address for further information: Hannes
      Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a SIP message.

   <how recipient validates credentials work item of sender>

   <how sender validates credentials the IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The IESG <ietf@ietf.org>

11.3.4.  MIME Content-type Registration for 'application/addCallSub+xml'

   This specification requests the registration of recipient>

   <how sender validates credentials a new MIME type
   according to the procedures of anyone requesting device
   dependent data>

   There is much private data in this information.  Local regulations
   may govern what data must be provided in emergency calls, but RFC 4288 [RFC4288] and guidelines in
   general, the emergency call system is often aided by
   RFC 3023 [RFC3023].

      MIME media type name: application

      MIME subtype name: addCallSub+xml

      Mandatory parameters: none

      Optional parameters: charset

      Indicates the character encoding of enclosed XML.

      Encoding considerations:

      Uses XML, which can employ 8-bit characters, depending on the kinds
      character encoding used.  See Section 3.2 of
   information described in this document.  There RFC 3023 [RFC3023].

      Security considerations:

      This content type is designed to carry owner/subscriber
      information, which is a tradeoff between
   the privacy considerations and the utility sub-category of the data.  Certainly,
   if the additional data cannot about an
      emergency call.

      Since this data contains personal information appropriate
      precautions have to be protected, due taken to failure limit unauthorized access,
      inappropriate disclosure to third parties, and eavesdropping of the TLS mechanisms
   described here, data not required by regulation SHOULD not be sent.

6.  IANA Considerations

6.1.  'emergencyCallData' Purpose Parameter Value
      this information.  Please refer to Section 9 and Section 10 for
      more information.

      Interoperability considerations: None

      Published specification: [TBD: This document defines the 'emergencyCallData' value specification]
      Applications which use this media type: Emergency Services

      Additional information:

      Magic Number: None

      File Extension: .xml

      Macintosh file type code: 'TEXT'

      Personal and email address for the "purpose"
   parameter further information: Hannes
      Tschofenig, Hannes.Tschofenig@gmx.net

      Intended usage: LIMITED USE

      Author: This specification is a work item of the Call-Info header field.  A reference to this IETF ECRIT
      working group, with mailing list address <ecrit@ietf.org>.

      Change controller: The IESG <ietf@ietf.org>

11.4.  URN Sub-Namespace Registration

11.4.1.  Registration for urn:ietf:params:xml:ns:addDataProviderInfo

   This section registers a new XML namespace, as per the guidelines in
   RFC (in
   double brackets) has been added 3688 [RFC3688].

   URI:  urn:ietf:params:xml:ns:addDataProviderInfo

   Registrant Contact:  IETF, ECRIT working group, <ecrit@ietf.org>, as
      delegated by the IESG <iesg@ietf.org>.

   XML:

   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
     "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
           content="text/html;charset=iso-8859-1"/>
     <title>Namespace for Additional Emergency Call Data:
            Data Provider Information</title>
   </head>
   <body>
     <h1>Namespace for Additional Data related to an Emergency Call</h1>
     <h2>Data Provider Information</h2>
   <p>See [TBD: This document].</p>
   </body>
   </html>
   END

11.4.2.  Registration for urn:ietf:params:xml:ns:addCallSvcInfo

   This section registers a new XML namespace, as per the existing "purpose" Call-Info
   parameter entry guidelines in the SIP Parameters registry, which currently looks
   RFC 3688 [RFC3688].

   URI:  urn:ietf:params:xml:ns:addCallSvcInfo

   Registrant Contact:  IETF, ECRIT working group, <ecrit@ietf.org>, as follows:

                                       Predefined
      Header Field    Parameter Name     Values     Reference
      -------------   --------------   ---------   ---------
      Call-Info         purpose           Yes      [RFC3261][RFC5367]

6.2.  provided-by registry entry
      delegated by the IESG <iesg@ietf.org>.

   XML:

   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
     "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
           content="text/html;charset=iso-8859-1"/>
     <title>Namespace for Additional Emergency Call Data:
            Service Information</title>
   </head>
   <body>
     <h1>Namespace for Additional Data related to an Emergency Call</h1>
     <h2>Service Information</h2>
   <p>See [TBD: This document].</p>
   </body>
   </html>
   END

11.4.3.  Registration for urn:ietf:params:xml:ns:addDataDevInfo

   This section registers a new XML namespace, as per the namespace specified in ??? guidelines in the
   provided-by registry established
   RFC 3688 [RFC3688].

   URI:  urn:ietf:params:xml:ns:addDataDevInfo

   Registrant Contact:  IETF, ECRIT working group, <ecrit@ietf.org>, as
      delegated by RFC4119.

   TBD

6.3.  MIME registrations

   TBD

6.4.  URN Sub-Namespace the IESG <iesg@ietf.org>.

   XML:

   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
     "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
           content="text/html;charset=iso-8859-1"/>
     <title>Namespace for Additional Emergency Call Data:
            Device Information</title>
   </head>
   <body>
     <h1>Namespace for Additional Data related to an Emergency Call</h1>
     <h2>Device Information</h2>
   <p>See [TBD: This document].</p>
   </body>
   </html>
   END

11.4.4.  Registration for
      urn:ietf:params:xml:ns:additional-data urn:ietf:params:xml:ns:addCallSub

   This section registers a new XML namespace, as per the guidelines in
   RFC 3688 [RFC3688].

   URI:  urn:ietf:params:xml:ns:additional-data  urn:ietf:params:xml:ns:addCallSub

   Registrant Contact:  IETF, ECRIT working group, <ecrit@ietf.org>, as
      delegated by the IESG <iesg@ietf.org>.

   XML:

   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
     "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
           content="text/html;charset=iso-8859-1"/>
        <title>Additional Data Namespace</title>
     <title>Namespace for Additional Emergency Call Data:
            Owner/Subscriber Information</title>
   </head>
   <body>
     <h1>Namespace for Additional Data </h1>
        <h2>urn:ietf:params:xml:ns:additional-data</h2> related to an Emergency Call</h1>
     <h2> Owner/Subscriber Information</h2>
   <p>See [TBD].</p> [TBD: This document].</p>
   </body>
   </html>
   END

6.5.  Additional Data

11.5.  Schema Registration Registrations

   This specification registers a schema, four schemas, as per the guidelines in
   RFC 3688 [RFC3688].

      URI: urn:ietf:params:xml:schema:additional-data
      urn:ietf:params:xml:schema:additional-data:addDataProviderInfo

      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 1.

      URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo

      Registrant Contact: IETF, ECRIT Working Group (geopriv@ietf.org), (ectit@ietf.org), as
      delegated by the IESG (iesg@ietf.org).

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

      URI: urn:ietf:params:xml:schema:additional-data:addDataDevInfo

      Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
      delegated by the sole content of Section IESG (iesg@ietf.org).

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

      URI: urn:ietf:params:xml:schema:additional-data:addCallSub

      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 4.

7.

12.  Acknowledgments

   The authors would like to thank the following persons for their work
   in the NENA Data Technical Committee: Delaine Arnold (Data Technical
   Committee Chair), Marc Berryman, Erica Aubut (Data Technical
   Committee Vice-Chair), Susan Sherwood, Ric Atkins, Patty Bluhm,
   Eileen Boroski, David Connel, Maryls Davis, Paul-David de la Rosby,
   Gordon Chinander, David Froneberger, Marilyn Haroutunian, Roger
   Hixson, Rick Jones, Roger Marshall, Tom Muehleisen, Ira Pyles, Carl
   Reed, Susan Seet, and Skip Walls.  The authors would also like to
   thank Tom Breen, Technical Committee Chair/Liaison; Busam, Technical
   Committee Vice-Chair/Liaison; Pete Eggimann, Operations Committee
   Chair/Liaison; Wendy Lively, Operations Committee Chair/Liaison;
   Roger Hixson, Technical Director; and Rick Jones, Operations Issues
   Director for their support and assistance.

8.

   [Editor's Note: Add the participants of the NENA Additional Data
   Working group lead by Matt Serra.]

13.  References

13.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2392]  Levinson, E., "Content-ID and Message-ID Uniform Resource
              Locators", RFC 2392, August 1998.

   [RFC3023]  Murata, M., St. Laurent, S., and D. Kohn, "XML Media
              Types", RFC 3023, January 2001.

   [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", RFC 3261,
              June 2002.

   [RFC3688]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
              January 2004.

   [RFC4119]  Peterson, J., "A Presence-based GEOPRIV Location Object
              Format", RFC 4119, December 2005.

   [RFC4288]  Freed, N. and J. Klensin, "Media Type Specifications and
              Registration Procedures", BCP 13, RFC 4288, December 2005.

   [RFC6351]  Perreault, S., "xCard: vCard XML Representation",
              RFC 6351, August 2011.

13.2.  Informational References

   [I-D.iab-privacy-considerations]
              Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., and
              J. Morris, "Privacy Considerations for Internet
              Protocols", draft-iab-privacy-considerations-01 (work in
              progress), October 2011.

   [I-D.ietf-ecrit-framework]
              Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
              "Framework for Emergency Calling using Internet
              Multimedia", draft-ietf-ecrit-framework-13 (work in
              progress), September 2011.

   [I-D.ietf-ecrit-phonebcp]
              Rosen, B. and J. Polk, "Best Current Practice for
              Communications Services in support of Emergency Calling",
              draft-ietf-ecrit-phonebcp-20 (work in progress),
              September 2011.

Authors' Addresses

   Brian Rosen
   NeuStar
   470 Conrad Dr.
   Mars, PA  16046
   US

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

   Hannes Tschofenig
   Nokia Siemens Networks
   Linnoitustie 6
   Espoo  02600
   Finland

   Phone: +358 (50) 4871445
   Email: Hannes.Tschofenig@gmx.net
   URI:   http://www.tschofenig.priv.at

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

   Phone: +1 206 792 2424
   Email: rmarshall@telecomsys.com
   URI:   http://www.telecomsys.com