< draft-ietf-ecrit-additional-data-01.txt   draft-ietf-ecrit-additional-data-02.txt >
ECRIT B. Rosen ECRIT B. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: January 13, 2012 Nokia Siemens Networks Expires: May 3, 2012 Nokia Siemens Networks
July 12, 2011 R. Marshall
TeleCommunication Systems, Inc.
October 31, 2011
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-00.txt draft-ietf-ecrit-additional-data-02.txt
Abstract Abstract
When an emergency call is sent to a PSAP, the device that sends it, When an emergency call is sent to a Public Safety Answering Point
as well as any service provider in the path of the call, or access (PSAP), the device that sends it, as well as any service provider in
network may have information about the call which the PSAP may be the path of the call, or access network may have information about
able to use. This document describes an XML data structure that the call which the PSAP may be able to use. This document describes
contains this kind of information in a standardized form. A URI that an XML data structure that contains this kind of information in a
points to the structure can be included in the SIP signaling with the standardized form. A Uniform Resource Identifier (URI) that points
call, or the data may be included in the body of a SIP message. 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 Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 13, 2012. This Internet-Draft will expire on May 3, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Additional Data about a Call . . . . . . . . . . . . . . . . . 5 3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 7
3.1. Data Provider Information Block . . . . . . . . . . . . . 5 4. Data Provider Information . . . . . . . . . . . . . . . . . . 8
3.1.1. Data Provider String . . . . . . . . . . . . . . . . . 6 4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 8
3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . . 6 4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 8
3.1.3. Data Provider Contact URI . . . . . . . . . . . . . . 7 4.3. Data Provider Contact URI . . . . . . . . . . . . . . . . 9
3.1.4. Data Provider Languages(s) supported . . . . . . . . . 7 4.4. Data Provider Languages(s) Supported . . . . . . . . . . . 9
3.1.5. vCARD of Data Provider . . . . . . . . . . . . . . . . 8 4.5. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 10
3.2. Service Information . . . . . . . . . . . . . . . . . . . 9 4.6. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 11
3.2.1. Service Environment . . . . . . . . . . . . . . . . . 9 5. Service Information . . . . . . . . . . . . . . . . . . . . . 12
3.2.2. Service Delivered by Provider to End User . . . . . . 9 5.1. Service Environment . . . . . . . . . . . . . . . . . . . 12
3.3. Device Information . . . . . . . . . . . . . . . . . . . . 10 5.2. Service Delivered by Provider to End User . . . . . . . . 12
3.3.1. Device Classification . . . . . . . . . . . . . . . . 10 5.3. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 13
3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 12 6. Device Information . . . . . . . . . . . . . . . . . . . . . . 15
3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 13 6.1. Device Classification . . . . . . . . . . . . . . . . . . 15
3.3.4. Unique Device Identifier . . . . . . . . . . . . . . . 13 6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 17
3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 14 6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 17
3.3.6. Device/service specific additional data structure . . 15 6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 17
3.4. Regulatory Information . . . . . . . . . . . . . . . . . . 16 6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 18
3.4.1. Telephone Number Privacy Indicator . . . . . . . . . . 16 6.6. Device/Service Specific Additional Data Structure Type . . 19
3.5. Owner/Subscriber Information . . . . . . . . . . . . . . . 17 6.7. Device/Service Specific Additional Data Structure . . . . 20
3.5.1. vCARD for Subscriber's Data . . . . . . . . . . . . . 17 6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 21
4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 18 7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 22
5. Security Considerations . . . . . . . . . . . . . . . . . . . 20 7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 22
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 22
6.1. 'emergencyCallData' Purpose Parameter Value . . . . . . . 21 8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.2. provided-by registry entry . . . . . . . . . . . . . . . . 21 9. Security Considerations . . . . . . . . . . . . . . . . . . . 25
6.3. MIME registrations . . . . . . . . . . . . . . . . . . . . 21 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 26
6.4. URN Sub-Namespace Registration for 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27
urn:ietf:params:xml:ns:additional-data . . . . . . . . . . 21 11.1. 'emergencyCallData' Purpose Parameter Value . . . . . . . 27
6.5. Additional Data Schema Registration . . . . . . . . . . . 22 11.2. URN Sub-Namespace Registration for provided-by
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 Registry Entry . . . . . . . . . . . . . . . . . . . . . . 27
8. Normative References . . . . . . . . . . . . . . . . . . . . . 24 11.3. MIME Registrations . . . . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25 11.3.1. MIME Content-type Registration for
'application/addDataProviderInfo+xml' . . . . . . . . 27
11.3.2. MIME Content-type Registration for
'application/addCallSvcInfo+xml' . . . . . . . . . . 28
11.3.3. MIME Content-type Registration for
'application/addDataDevInfo+xml' . . . . . . . . . . 30
11.3.4. MIME Content-type Registration for
'application/addCallSub+xml' . . . . . . . . . . . . 31
11.4. URN Sub-Namespace Registration . . . . . . . . . . . . . . 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 1. Introduction
When an emergency call is sent to a PSAP, there is a rich set of data As communications devices increasingly utilize the Internet to
in the headers with the call, but the device, as well as any other interconnect and communicate, users will expect to use such devices
service provider in the path may have even more information that to request help. The Internet Protocol suite provides many
would be useful to a PSAP. This information may include the identity advantages but also requires re-thinking of the traditional emergency
and contact information of the service provider, subscriber identity calling architecture. The IETF emergency services architecture, as
and contact information, the type of service the service provider described in [I-D.ietf-ecrit-framework] and
provides, what kind of device the user has, etc. Some kinds of [I-D.ietf-ecrit-phonebcp], offers a much richer communication
devices or services have device or service dependent data. For exchange and thereby better situational awareness for call takers.
example, a car telematics system or service may have crash The richness comes in various forms, including the multi-media
information. A medical monitoring device may have sensor data. communication capabilities (via voice, video, instant messaging, and
While the details of the information may vary by device or service, real-time text), but also via more extensive flow of information.
there needs to be a common way to send such data to a PSAP. 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).
For the call takers this will enable more intelligent decision making In general, there are four types of data exchanged:
and therefore better response in case of an emergency. A pre-
requisite is to offer the technical capabilities to let call takers Data Associated with a Call: A lot of information is carried in the
to gain access to this information stored elsewhere (granted that call setup procedure itself (as part of the SIP headers as well as
they have authorization to access it). 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 useful 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 provider
offers, what kind of device the user has, etc. Some 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.
This document focuses on the data that can be obtained about a call 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, and a mechanism for transporting it in an existing SIP header field,
the Call-Info header. For this purpose a new token, namely the Call-Info header, which is specified in Section 20.9 of
'emergencyCallData' is defined to be carried in the "purpose" [RFC3261]. For this purpose a new token, namely 'emergencyCallData'
parameter. If the "purpose" parameter set to 'emergencyCallData' is defined to be carried in the "purpose" parameter. If the
then the Call-Info contains a HTTPS URL that points to a data "purpose" parameter is set to 'emergencyCallData' then the Call-Info
structure with information about the call or a CID that allows the header contains a HTTPS URL that points to a data structure with
data structure to be placed in the body of the message. In addition, information about the call or a CID that allows the data structure to
this document describes a "provided-by" namespace per [RFC4119] for be placed in the body of the message. Section 8 shows a SIP INVITE
passing information known to the access network 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.
The data is defined as a series of "blocks" that represent a class of 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 information. Each of the blocks is a MIME type, and an extensible
set of these types constitute the data structure. A registry is set of these types constitute the data structure. A registry is
defined to list the block types that may be included. defined to list the block types that may be included.
The data structure contains an element which itself is a URI that has The data structure contains an element which itself is a URI that has
device or service dependent data. Thus the common Additional Data device or service dependent data. Thus the common Additional Data
about a Call defined by this document contains a 'hook', in the form about a Call defined by this document contains a 'hook', in the form
of a URI for a device or service dependent data structure. of a URI, for a device or service dependent data structure.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Additional Data about a Call 3. Call-Info Specification
The Additional Data about a Call is information specific to a call 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 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 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 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 block is a MIME type, and any set of blocks may be included in the
set. set.
Three mechanisms are provided to transport the data set. A URI to Two mechanisms are provided to transport the data set, namely
the data set 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.
The data may be supplied by value in a SIP INVITE or MESSAGE message. 1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE
In this case, Content Indirection [RFC2392] is used, with the CID URL transaction with a Call-Info header containing a purpose of
pointing to the body of the message. "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 More than one Call-Info header with an emergencyCallData purpose can
be expected. The device may insert one, and any intermediary service be expected. The device MAY insert one, and any intermediary service
provider may insert its own. When there are multiple intermediaries provider MAY insert its own. When there are multiple intermediaries,
each intermediary may each insert one. For example, a device may each intermediary MAY each insert one. For example, a device may
provide one, a telematics service provider may provide one and the provide one, a telematics service provider may provide one and the
mobile carrier handling the call may provide one. mobile carrier handling the call may provide one.
The access network may supply Additional Data about a Call. For this Note: The access network MAY supply additional data as well. For
purpose, this document defines a namespace and adds the namespace to this purpose, this document defines a namespace and adds the
the "provided-by" registry defined by [RFC4119] namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].
Additional Data about a Call is defined as a series of blocks. Each Additional data about a call is defined as a series of MIME objects,
block is defined as a mime type, with an XML data structure. MIME- each with an XML data structure contained inside. MIME-multipart is
multipart is used to enclose the set of blocks constituting the used to enclose the XML documents and the sections below define them.
information provided by an entity (service provider or device). The
sections below define the blocks.
3.1. Data Provider Information Block 4. Data Provider Information
This block is intended to be provided by any service provider in the This block is intended to be provided by any service provider in the
path of the call or the access network provider. It includes path of the call or the access network provider. It includes
identification and contact information. This block SHOULD be identification and contact information. This block SHOULD be
provided for every service provider in the path of the call, and the provided for every service provider in the path of the call, and the
access network provider. Devices also use this block to provide access network provider. Devices also use this block to provide
identifying information. The MIME type is "addDataProviderInfo". identifying information. The MIME type is "addDataProviderInfo+xml".
3.1.1. Data Provider String 4.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Required Use: Required
XML Element: <DataProviderString> XML Element: <DataProviderString>
Description: This is a plain language string suitable for displaying Description: This is a plain language string suitable for displaying
the name of the service provider that created the additional data the name of the service provider that created the additional data
structure. If the device created the structure the value is structure. If the device created the structure the value is
identical to the contact header in the SIP Invite. This data is identical to the contact header in the SIP INVITE.
required and should reflect the contact information of the owner
of the device.
Reason for Need: Inform the call taker about the identity of the Reason for Need: Inform the call taker about the identity of the
entity providing the additional call data structure. entity providing the additional call data structure.
How Used by Call Taker: Allows the call taker to interpret 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 in this structure. The source of the information often influences
how the information is used, believed or verified. how the information is used, believed or verified.
3.1.2. Data Provider ID 4.2. Data Provider ID
Data Element: Data Provider ID Data Element: Data Provider ID
Use: Conditional Use: Conditional
XML Element: <ProviderID> XML Element: <ProviderID>
Description: A jurisdiction specific code for the provider shown in Description: A jurisdiction specific code for the provider shown in
the <DataProvidedBy> element that created the structure of the the <DataProvidedBy> element that created the structure of the
call. NOTE: In the US, the NENA Company ID must appear here. call. This data SHOULD be provided if the local jurisdiction
Additional information may be found at maintains such an ID list. For example, in North America, this
http://www.nena.org/nena-company-id. The NENA Company ID shall be would be a "NENA Company ID". Devices would not typically use
in the form of any URI for example: urn:nena:companyid:<NENA this element.
Company ID>. This data is required unless the additional data
structure is provided by the device.
Reason for Need: Inform the call taker about the identity of the Reason for Need: Inform the call taker about the identity of the
entity providing the additional call data structure. entity providing the additional call data structure.
How Used by Call Taker: Where jurisdictions have lists of providers How Used by Call Taker: Where jurisdictions have lists of providers
the Provider Company ID can lead to a wealth of information the Data Provider ID can lead to a wealth of information.
associated with the code.
3.1.3. Data Provider Contact URI 4.3. Data Provider Contact URI
Data Element: Data Provider Contact URI Data Element: Data Provider Contact URI
Use: Required Use: Required
XML Element: <ContactURI> XML Element: <ContractURI>
Description: For a Service Provider the contact SHOULD be a 24x7 Description: For a service provider the contact SHOULD be a contact
contact URI. This must be a SIP URI. If a telephone number is URI. This must be a SIP URI. If a telephone number is the
the contact address it should be provided in the form of contact address it should be provided in the form of
sip:telephonenumber@serviceprovider:user=phone. If the call is sip:telephonenumber@serviceprovider:user=phone. If the call is
from a device, this data is required and should reflect the from a device, this data is required and should reflect the
contact information of the owner of the device. 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 Reason for Need: Additional data providers may need to be contacted
for error or other unusual circumstances. for error or other unusual circumstances.
How Used by Call Taker: To contact the supplier of the additional How Used by Call Taker: To contact the supplier of the additional
data provider structure. data provider structure.
3.1.4. Data Provider Languages(s) supported 4.4. Data Provider Languages(s) Supported
Data Element: Data Provider Language(s) supported Data Element: Data Provider Language(s) supported
Use: Conditional Use: Conditional
XML Element: <Language>
XML Element: <LanguagePreference>
Description: Provided by's alpha 2-character code as defined in ISO Description: Provided by's alpha 2-character code as defined in ISO
639-1:2002 639-1:2002
(http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for (http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for
the representation of names of languages -- Part 1: Alpha-2 code the representation of names of languages -- Part 1: Alpha-2 code
Multiple instances of this element may occur. Order is Multiple instances of this element may occur. Order is
significant; preferred language should appear first. This data is significant; preferred language should appear first. This data is
required unless the message is from a data only device. required if a 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 Reason for Need: Information needed to determine if emergency
can communicate with the Service Provider or if language line will service authority can communicate with the service provider or if
be needed. language line will be needed.
How Used by Call Taker: If call taker cannot speak language(s) How Used by Call Taker: If call taker cannot speak language(s)
supported by the Service Provider, language line will need to be supported by the service provider, at translation service will
added in to conversation. need to be added in to the conversation.
3.1.5. vCARD of Data Provider 4.5. vCARD of Data Provider
Data Element: vCARD of Data Provider Data Element: vCARD of Data Provider
Use: Optional Use: Optional
XML Element: <DataProviderContact> XML Element: <DataProviderContact>
Description: There are many fields in the vCARD. The creator of the Description: There are many fields in the vCARD and the creator of
data structure is encouraged to provide as much information as the data structure is encouraged to provide as much information as
they have available. A minimum of subscriber provided by's name, they have available. For encoding of the vCard this specification
address and general contact number should be provided. uses the XML-based encoding specified in [RFC6351].
Reason for Need: Information needed to determine additional contact Reason for Need: Information needed to determine additional contact
information. information.
How Used by Call Taker: Assists call taker by providing additional How Used by Call Taker: Assists call taker by providing additional
contact information that may not be included in the SIP invite or 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 the PIDF-LO.
taker.
3.2. Service Information 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 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 to the caller. It SHOULD be included by all SPs in the path of the
call. The mime type is "addCallSvcInfo" call. The mime type is "addCallSvcInfo+xml".
3.2.1. Service Environment 5.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
Use: Required Use: Required
XML Element: <SvcEnvironment> XML Element: <SvcEnvironment>
Description: This defines if the call service type is a Business or Description: This element defines whether a call is from a business
Residence caller. Currently, the only valid entries are Business or residence caller. Currently, the only valid entries are
or Residence. 'Business' or 'Residence'.
Reason for Need: To assist in determining equipment and manpower Reason for Need: To assist in determining equipment and manpower
requirements. requirements.
How Used by Call Taker: Information may be used to determine How Used by Call Taker: Information may be used to determine
equipment and manpower requirements for emergency responders. equipment and manpower requirements for emergency responders.
3.2.2. Service Delivered by Provider to End User 5.2. Service Delivered by Provider to End User
Data Element: Service Delivered by Provider to End User Data Element: Service Delivered by Provider to End User
Use: Required Use: Required
XML Element: <SvcDelByProvider> XML Element: <SvcDelByProvider>
Description: This defines the type of service the end user has Description: This defines the type of service the end user has
subscribed to. The implied mobility of this service can not be subscribed to. The implied mobility of this service can not be
relied upon. A registry will reflect the following valid entries: relied upon. A registry will reflect the following initial valid
entries:
* Mobile Telephone Service: Includes Satellite, CDMA, GSM, Wi-Fi, * Mobile Telephone Service: Includes Satellite, CDMA, GSM, Wi-Fi,
WiMAX, LTE (Long Term Evolution) WiMAX, LTE (Long Term Evolution)
* Fixed Public Pay/Coin telephones: Any coin or credit card * Fixed Public Pay/Coin telephones: Any coin or credit card
operated device. operated device.
* One way outbound service * One way outbound service
* Inmate call/service * Inmate call/service
skipping to change at page 10, line 31 skipping to change at page 13, line 31
* Sensor, attended: Includes devices that are supported by a * Sensor, attended: Includes devices that are supported by a
monitoring service provider or automatically open a two-way monitoring service provider or automatically open a two-way
communication path. communication path.
* Wireline: Plain Old Telephone Service (POTS). * Wireline: Plain Old Telephone Service (POTS).
* VoIP Telephone Service: A type of service that offers * VoIP Telephone Service: A type of service that offers
communication over internet protocol, such as Fixed, Nomadic, communication over internet protocol, such as Fixed, Nomadic,
Mobile, Unknown 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 Reason for Need: Knowing the type of service may assist the PSAP
with the handling of the call. with the handling of the call.
How Used by Call Taker: Calltaker may be able to determine if the How Used by Call Taker: Calltakers often use this information to
caller is stationary or mobile and if they will have voice determine what kinds of questions to ask callers, and how much to
communications with the caller or is it a data only event. rely on supportive information. An emergency call from a prison
is treated differently that a call from a sensor device.
3.3. Device Information 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 This block provides information about the device used to place the
call. It should be provided by any service provider that knows what 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 device is being used, and by the device itself. The mime type is
"addDataDevInfo". "addDataDevInfo+xml".
6.1. Device Classification
3.3.1. Device Classification
Data Element: Device Classification Data Element: Device Classification
Use: Optional Use: Optional
XML Element: <DeviceClassification> XML Element: <DeviceClassification>
Description: If the device provides the data structure, the device Description: If the device provides the data structure, the device
information should be provided. If the Service Provider provides information should be provided. If the service provider provides
the structure and it knows what the device is, the Service the structure and it knows what the device is, the service
Provider should provide the device information. Often the carrier provider should provide the device information. Often the carrier
does not know what the device is. It is possible to receive 2 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 data structures, one created by the device and one created by the
Service Provider. Information about the device, not how it is service provider. Information about the device, not how it is
being used. This data element defines the kind of device making being used. This data element defines the kind of device making
the emergency call. A registry will reflect the following valid the emergency call. A registry will reflect the following valid
entries: entries:
* Cordless handset * Cordless handset
* Fixed phone * Fixed phone
* Mobile handset * Mobile handset
skipping to change at page 12, line 37 skipping to change at page 17, line 5
of the calling device. For example, does the device require human of the calling device. For example, does the device require human
intervention to initiate a call or is this call the result of intervention to initiate a call or is this call the result of
programmed instructions. Does the calling device have the ability programmed instructions. Does the calling device have the ability
to rebid for location or condition changes? Is this device to rebid for location or condition changes? Is this device
interactive or a one-way reporting device? interactive or a one-way reporting device?
How Used by Call Taker: May assist with location of caller. For How Used by Call Taker: May assist with location of caller. For
example, a cordless handset may be outside or next door. May example, a cordless handset may be outside or next door. May
provide calltaker some context about the caller. provide calltaker some context about the caller.
3.3.2. Device Manufacturer 6.2. Device Manufacturer
Data Element: Device Manufacturer Data Element: Device Manufacturer
Use: Optional Use: Optional
XML Element: <DeviceMfgr> XML Element: <DeviceMfgr>
Description: Manufacturer is electronically stored on the device.
Different devices may use different conventions to provide their Description: The plain language name of the manufacturer of the
information. We need to know what it represents, so a registry is device.
in order. Need to be able to standardize as much as possible with
a uniform naming convention. A registry will reflect the valid
entries.
Reason for Need: Used by PSAP management for post-mortem Reason for Need: Used by PSAP management for post-mortem
investigation/resolution. investigation/resolution.
How Used by Call Taker: Probably not used by calltaker, but by PSAP How Used by Call Taker: Probably not used by calltaker, but by PSAP
management. management.
3.3.3. Device Model Number 6.3. Device Model Number
Data Element: Device Model Number Data Element: Device Model Number
Use: Optional Use: Optional
XML Element: <DeviceModelNr> XML Element: <DeviceModelNr>
Description: Model number is electronically stored on the device. Description: Model number of the device.
Reason for Need: Used by PSAP management for after action Reason for Need: Used by PSAP management for after action
investigation/resolution. investigation/resolution.
How Used by Call Taker: Probably not used by calltaker, but by PSAP How Used by Call Taker: Probably not used by calltaker, but by PSAP
management. management.
3.3.4. Unique Device Identifier 6.4. Unique Device Identifier
Data Element: Unique Device Identifier Data Element: Unique Device Identifier
Use: Optional Use: Optional
XML Element: <UniqueDeviceID> XML Element: <UniqueDeviceID>
Description: Characters that identify the specific device making the
Description: String that identify the specific device making the
call or creating an event. call or creating an event.
Reason for Need: May be needed when trying to obtain a subpoena to Reason for Need: Uniquely identifies the device as opposed to any
obtain customer information in instances where location info did signaling identifiers encountered in the call signaling stream.
not display or someone is making false emergency calls. May also
be used when working with safe houses that are using non-
initialized phones.
How Used by Call Taker: Probably not used by calltaker they would How Used by Call Taker: Probably not used by calltaker they would
need to refer to management for investigation. need to refer to management for investigation.
3.3.5. Type of Device Identifier 6.5. Type of Device Identifier
Data Element: Type of Device Identifier Data Element: Type of Device Identifier
Use: Optional Use: Optional
XML Element: <TypeOfDeviceID> XML Element: <TypeOfDeviceID>
Description: Identifies the type of device identifier being Description: Identifies the type of device identifier being
generated in the unique device identifier data element. A generated in the unique device identifier data element. A
registry will reflect the following valid entries: registry will reflect the following valid entries:
skipping to change at page 15, line 4 skipping to change at page 19, line 8
* WiMAX has a device certificate * WiMAX has a device certificate
* IMEI (International Mobile Equipment Identifier - GSM) * IMEI (International Mobile Equipment Identifier - GSM)
* Unique Device Identifier (Unique identifier for medical * Unique Device Identifier (Unique identifier for medical
devices) devices)
* RFID (Radio Frequency Identification) * RFID (Radio Frequency Identification)
* Sensors (types to be identified in a future document version) * Sensors (types to be identified in a future document version)
* Manufacturer Serial Number * Manufacturer Serial Number
Reason for Need: Calls from uninitiated devices would give an * Other
identifier that could be associated with erroneous calls --- use
the number to identify what type of capabilities there are. Could Reason for Need: Identifies how to interpret the Unique Device
also use this information to block specific types of calls. Identifier.
How Used by Call Taker: Additional information that may be used to How Used by Call Taker: Additional information that may be used to
assist with call handling. assist with call handling.
3.3.6. Device/service specific additional data structure 6.6. Device/Service Specific Additional Data Structure Type
Data Element: Device/service specific additional data structure Data Element: Type of Device/service specific additional data
structure
Use: Optional Use: Conditional. MUST be provided when Device/service specific
additional URI is provided
XML Element: <devicespecificSchema> XML Element: <devicespecificType>
Description: A URI representing additional data whose schema is Description: Value from a registry defined by this document to
specific to the device or service which created it. An example is describe the type of data that can be retrieved from the Device/
the VEDs structure for a vehicle telematics device. The structure service specific additional data structure. Initial values are:
can be referenced via URI and used in 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 are:
* NPAC * NPAC
* Hazmat International Association of Fire Chiefs * Hazmat International Association of Fire Chiefs
* DHS/EPA E-Plan for HazMat * DHS/EPA E-Plan for HazMat
* NFPA - National Fire Protection Association * NFPA - National Fire Protection Association
* National Alliance for Public Safety GIS (NA-PSG) * National Alliance for Public Safety GIS (NA-PSG)
skipping to change at page 15, line 44 skipping to change at page 20, line 4
* DHS/EPA E-Plan for HazMat * DHS/EPA E-Plan for HazMat
* NFPA - National Fire Protection Association * NFPA - National Fire Protection Association
* National Alliance for Public Safety GIS (NA-PSG) * National Alliance for Public Safety GIS (NA-PSG)
* US DOT Pipeline and Hazardous Materials Safety Administration * US DOT Pipeline and Hazardous Materials Safety Administration
(PHMSA) examples of additional data. (PHMSA) examples of additional data.
* Fire Service Data Model * Fire Service Data Model
* IEEE 1512 - USDOT Model for traffic incidents * IEEE 1512 - USDOT Model for traffic incidents
* Smart Building (NIST) * Smart Building (NIST)
* VEDS * VEDS
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.
Reason for Need: This data element will allow for identification of Reason for Need: This data element will allow for identification of
externally defined schemas, which may have additional data that externally defined schemas, which may have additional data that
will assist in emergency response. will assist in emergency response.
How Used by Call Taker: This data element will allow the end user How Used by Call Taker: This data element will allow the end user
(calltaker or first responder) to know what type of additional (calltaker or first responder) to know what type of additional
data may be available to aid in providing the needed emergency data may be available to aid in providing the needed emergency
services. services.
3.4. Regulatory Information 6.7. Device/Service Specific Additional Data Structure
In some jurisdictions, handling of emergency calls involves Data Element: Device/service specific additional data structure
information known by a service provider that must, by regulation, be
passed to the emergency system. The mime type is "addCallReg".
3.4.1. Telephone Number Privacy Indicator Use: Optional
Data Element: Telephone Number Privacy Indicator XML Element: <devicespecificSchema>
Use: Required 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 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.
XML Element: <TNPrivacyIndicator> Reason for Need: Provides device/service specific data that may be
used by the call taker and/or responders.
Description: Some State regulations require that Non-Published How Used by Call Taker: Provide information to guide call takers to
subscriber name remains private to all including 9-1-1. Where select appropriate responders, give appropriate pre-arrival
this regulation is in place, the end user's name must be overlaid instructions to callers, and advise responders of what to be
with blanks or the verbiage, "Non-Published Number." prepared for. May be used by responders to guide assistance
provided.
Reason for Need: Some State regulations require that Non-Published 6.8. addDataDevInfo XML Schema
subscriber name remains private to all including emergency calls.
Where this regulation is in place, the end user's name must be
overlaid with blanks or the verbiage, "Non-Published Number".
How Used by Call Taker: This is not beneficial to PSAPs; however, <?xml version="1.0"?>
they must follow state regulations. This indicator will allow for <xs:schema
coding that overlays the non-published subscriber name with the targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo"
verbiage "Non-Published Number." 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">
3.5. Owner/Subscriber Information <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 This block describes the owner of the device (if provided by the
device) or the subscriber information, if provided by a service device) or the subscriber information, if provided by a service
provider. The contact location is NOT necessarily the location of provider. The contact location is not necessarily the location of
the caller or incident, but is rather the nominal contact address. the caller or incident, but is rather the nominal contact address.
The mime type is "addCallSub". The mime type is "addCallSub+xml".
3.5.1. vCARD for Subscriber's Data 7.1. vCARD for Subscriber's Data
Data Element: vCARD for Subscriber's Data Data Element: vCARD for Subscriber's Data
Use: Required Use: Required
XML Element: <SubscriberData> XML Element: <SubscriberData>
Description: Information known by the Service Provider about the Description: Information known by the service provider or device
subscriber; i.e., Name, Address, Calling Party Number, Main about the subscriber; i.e., Name, Address, Calling Party Number,
Telephone Number and any other data. If the subscriber is an Main Telephone Number and any other data. If the subscriber is an
enterprise, this is the vCARD of the enterprise and the Company enterprise, this is the vCARD of the enterprise and the Company
Name is used not the Name of the Caller. The telephone number is Name is used not the Name of the Caller. The telephone number is
the main telephone number at the location of the call. The the main telephone number at the location of the call. The
address should be where the call is originating from. address should be where the call is originating from.
Reason for Need: Critical information required for proper call Reason for Need: Critical information required for proper call
handling and dispatching. handling and dispatching.
How Used by Call Taker: Critical information required for proper How Used by Call Taker: Critical information required for proper
call handling and dispatching. call handling and dispatching.
4. XML Schema 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">
NOTE: This section is not yet updated. <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<?xml version="1.0" encoding="UTF-8"?> <xs:element name="addCallSub">
<xsd:schema <xs:complexType>
xmlns:xsd="http://www.w3.org/2001/XMLSchema" <xs:sequence>
xmlns="urn:nena:xml:ns:es:NG:Call" <xs:element name="SubscriberData"
targetNamespace="urn:nena:xml:ns:es:NG:Call" type="vc:vcards" minOccurs="0" maxOccurs="1">
elementFormDefault="qualified" </xs:sequence>
attributeFormDefault="unqualified" version="1.0"> </xs:complexType>
<xsd:include schemaLocation="NGTypeLib.xsd"/> </xs:element>
<xsd:element name="DataAssociatedWithCall"> </xs:schema>
<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 Figure 4: addCallSub XML Schema
5. Security Considerations 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 a SIP INVITE
9. Security Considerations
The information in this data structure will usually be considered The information in this data structure will usually be considered
private. HTTPS is specified to require the provider of the private. HTTPS is specified to require the provider of the
information to validate the credentials of the requester. While the information to validate the credentials of the requester. While the
creation of a PKI that has global scope may be difficult, the creation of a PKI that has global scope may be difficult, the
alternatives to creating devices and services that can provide alternatives to creating devices and services that can provide
critical information securely are more daunting. critical information securely are more daunting.
The Call-info header with purpose='emergencyCallData' MUST only be The Call-info header with purpose='emergencyCallData' MUST only be
sent on an emergency call, which can be ascertained by the presence sent on an emergency call, which can be ascertained by the presence
of an emergency service urn in a Route header of a SIP message. of an emergency service urn in a Route header of a SIP message.
<how recipient validates credentials of sender> <how recipient validates credentials of sender>
<how sender validates credentials of recipient> <how sender validates credentials of recipient>
<how sender validates credentials of anyone requesting device <how sender validates credentials of anyone requesting device
dependent data> dependent data>
10. Privacy Considerations
[Editor's Note: The privacy considerations outlined in
[I-D.iab-privacy-considerations] need to be addressed here in a
future version of this document.
There is much private data in this information. Local regulations There is much private data in this information. Local regulations
may govern what data must be provided in emergency calls, but in may govern what data must be provided in emergency calls, but in
general, the emergency call system is often aided by the kinds of general, the emergency call system is often aided by the kinds of
information described in this document. There is a tradeoff between information described in this document. There is a tradeoff between
the privacy considerations and the utility of the data. Certainly, the privacy considerations and the utility of the data. Certainly,
if the data cannot be protected, due to failure of the TLS mechanisms if the data cannot be protected, due to failure of the TLS mechanisms
described here, data not required by regulation SHOULD not be sent. described here, data not required by regulation SHOULD not be sent.
6. IANA Considerations 11. IANA Considerations
6.1. 'emergencyCallData' Purpose Parameter Value [Editor's Note: The IANA section is missing the description of new
registries. A future version of this draft will contain the
necessary information.]
11.1. 'emergencyCallData' Purpose Parameter Value
This document defines the 'emergencyCallData' value for the "purpose" This document defines the 'emergencyCallData' value for the "purpose"
parameter of the Call-Info header field. A reference to this RFC (in parameter of the Call-Info header field. The Call-Info header and
double brackets) has been added to the existing "purpose" Call-Info the corresponding registry for the 'purpose' parameter was
parameter entry in the SIP Parameters registry, which currently looks established with RFC 3261 [RFC3261].
as follows:
Predefined Header Parameter New
Header Field Parameter Name Values Reference Field Name Value Reference
------------- -------------- --------- --------- ---------- --------- ----------------- ---------
Call-Info purpose Yes [RFC3261][RFC5367] Call-Info purpose emergencyCallData [This RFC]
6.2. provided-by registry entry 11.2. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in ??? in the This section registers the namespace specified in ??? in the
provided-by registry established by RFC4119. provided-by registry established by RFC 4119.
TBD 11.3. MIME Registrations
6.3. MIME registrations 11.3.1. MIME Content-type Registration for 'application/
addDataProviderInfo+xml'
TBD This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023].
6.4. URN Sub-Namespace Registration for MIME media type name: application
urn:ietf:params:xml:ns:additional-data
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
character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
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 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 work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>.
Change controller: The 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 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 work item of the 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 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: addDataDevInfo+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 device information
information, which is a sub-category of additional data about an
emergency 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 work item of 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 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: 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
character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
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 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 work item of the 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 This section registers a new XML namespace, as per the guidelines in
[RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:additional-data URI: urn:ietf:params:xml:ns:addDataProviderInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Additional Data Namespace</title> <title>Namespace for Additional Emergency Call Data:
</head> Data Provider Information</title>
<body> </head>
<h1>Namespace for Additional Data </h1> <body>
<h2>urn:ietf:params:xml:ns:additional-data</h2> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<p>See [TBD].</p> <h2>Data Provider Information</h2>
</body> <p>See [TBD: This document].</p>
</html> </body>
END </html>
END
6.5. Additional Data Schema Registration 11.4.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo
This specification registers a schema, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
[RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:schema:additional-data URI: urn:ietf:params:xml:ns:addCallSvcInfo
Registrant Contact: IETF, ECRIT Working Group (geopriv@ietf.org), Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
as delegated by the IESG (iesg@ietf.org). delegated by the IESG <iesg@ietf.org>.
XML: The XML can be found as the sole content of Section 4. XML:
7. Acknowledgments 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 guidelines in
RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:addDataDevInfo
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:
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:addCallSub
This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688].
URI: 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>Namespace for Additional Emergency Call Data:
Owner/Subscriber Information</title>
</head>
<body>
<h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2> Owner/Subscriber Information</h2>
<p>See [TBD: This document].</p>
</body>
</html>
END
11.5. Schema Registrations
This specification registers four schemas, as per the guidelines in
RFC 3688 [RFC3688].
URI:
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 (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 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.
12. Acknowledgments
The authors would like to thank the following persons for their work The authors would like to thank the following persons for their work
in the NENA Data Technical Committee: Delaine Arnold (Data Technical in the NENA Data Technical Committee: Delaine Arnold (Data Technical
Committee Chair), Marc Berryman, Erica Aubut (Data Technical Committee Chair), Marc Berryman, Erica Aubut (Data Technical
Committee Vice-Chair), Susan Sherwood, Ric Atkins, Patty Bluhm, Committee Vice-Chair), Susan Sherwood, Ric Atkins, Patty Bluhm,
Eileen Boroski, David Connel, Maryls Davis, Paul-David de la Rosby, Eileen Boroski, David Connel, Maryls Davis, Paul-David de la Rosby,
Gordon Chinander, David Froneberger, Marilyn Haroutunian, Roger Gordon Chinander, David Froneberger, Marilyn Haroutunian, Roger
Hixson, Rick Jones, Roger Marshall, Tom Muehleisen, Ira Pyles, Carl Hixson, Rick Jones, Roger Marshall, Tom Muehleisen, Ira Pyles, Carl
Reed, Susan Seet, and Skip Walls. The authors would also like to Reed, Susan Seet, and Skip Walls. The authors would also like to
thank Tom Breen, Technical Committee Chair/Liaison; Busam, Technical thank Tom Breen, Technical Committee Chair/Liaison; Busam, Technical
Committee Vice-Chair/Liaison; Pete Eggimann, Operations Committee Committee Vice-Chair/Liaison; Pete Eggimann, Operations Committee
Chair/Liaison; Wendy Lively, Operations Committee Chair/Liaison; Chair/Liaison; Wendy Lively, Operations Committee Chair/Liaison;
Roger Hixson, Technical Director; and Rick Jones, Operations Issues Roger Hixson, Technical Director; and Rick Jones, Operations Issues
Director for their support and assistance. Director for their support and assistance.
8. Normative References [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 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. 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, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. 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 Authors' Addresses
Brian Rosen Brian Rosen
NeuStar NeuStar
470 Conrad Dr. 470 Conrad Dr.
Mars, PA 16046 Mars, PA 16046
US US
Phone: +1 724 382 1051 Phone: +1 724 382 1051
Email: br@brianrosen.net Email: br@brianrosen.net
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at 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
 End of changes. 109 change blocks. 
311 lines changed or deleted 879 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/