draft-ietf-ecrit-additional-data-02.txt   draft-ietf-ecrit-additional-data-03.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: May 3, 2012 Nokia Siemens Networks Expires: September 14, 2012 Nokia Siemens Networks
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
October 31, 2011 March 13, 2012
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-02.txt draft-ietf-ecrit-additional-data-03.txt
Abstract Abstract
When an emergency call is sent to a Public Safety Answering Point When an emergency call is sent to a Public Safety Answering Point
(PSAP), the device that sends it, as well as any service provider in (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 path of the call, or access network may have information about
the call which the PSAP may be able to use. This document describes 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 an XML data structure that contains this kind of information in a
standardized form. A Uniform Resource Identifier (URI) that points standardized form. A Uniform Resource Identifier (URI) that points
to the structure can be included in the SIP signaling with the call, to the structure can be included in the SIP signaling with the call,
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 May 3, 2012. This Internet-Draft will expire on September 14, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 7 3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 8
4. Data Provider Information . . . . . . . . . . . . . . . . . . 8 4. Data Provider Information . . . . . . . . . . . . . . . . . . 9
4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 8 4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 9
4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 8 4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 9
4.3. Data Provider Contact URI . . . . . . . . . . . . . . . . 9 4.3. Type of Data Provider ID . . . . . . . . . . . . . . . . . 10
4.4. Data Provider Languages(s) Supported . . . . . . . . . . . 9 4.4. Data Provider Contact URI . . . . . . . . . . . . . . . . 10
4.5. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 10 4.5. Data Provider Languages(s) Supported . . . . . . . . . . . 11
4.6. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 11 4.6. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 12
5. Service Information . . . . . . . . . . . . . . . . . . . . . 12 4.7. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 12
5.1. Service Environment . . . . . . . . . . . . . . . . . . . 12 5. Service Information . . . . . . . . . . . . . . . . . . . . . 14
5.2. Service Delivered by Provider to End User . . . . . . . . 12 5.1. Service Environment . . . . . . . . . . . . . . . . . . . 14
5.3. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 13 5.2. Service Delivered by Provider to End User . . . . . . . . 14
6. Device Information . . . . . . . . . . . . . . . . . . . . . . 15 5.3. Service Mobility Environment . . . . . . . . . . . . . . . 16
6.1. Device Classification . . . . . . . . . . . . . . . . . . 15 5.4. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 17
6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 17 6. Device Information . . . . . . . . . . . . . . . . . . . . . . 18
6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 17 6.1. Device Classification . . . . . . . . . . . . . . . . . . 18
6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 17 6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 20
6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 18 6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 20
6.6. Device/Service Specific Additional Data Structure Type . . 19 6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 21
6.7. Device/Service Specific Additional Data Structure . . . . 20 6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 21
6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 21 6.6. Device/Service Specific Additional Data Structure . . . . 22
7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 22 6.7. Device/Service Specific Additional Data Structure Type . . 23
7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 22 6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 23
7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 22 7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 25
8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 25
9. Security Considerations . . . . . . . . . . . . . . . . . . . 25 7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 25
10. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 26 8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 9. Security Considerations . . . . . . . . . . . . . . . . . . . 28
11.1. 'emergencyCallData' Purpose Parameter Value . . . . . . . 27 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 29
11.2. URN Sub-Namespace Registration for provided-by 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
Registry Entry . . . . . . . . . . . . . . . . . . . . . . 27 11.1. Registry creation . . . . . . . . . . . . . . . . . . . . 30
11.3. MIME Registrations . . . . . . . . . . . . . . . . . . . . 27 11.1.1. Additional Call Data Service Delivered Registry . . . 30
11.3.1. MIME Content-type Registration for 11.1.2. Additional Call Data Device Classification
'application/addDataProviderInfo+xml' . . . . . . . . 27 Registry . . . . . . . . . . . . . . . . . . . . . . 31
11.3.2. MIME Content-type Registration for 11.1.3. Additional Call Data Device ID Type Registry . . . . 32
'application/addCallSvcInfo+xml' . . . . . . . . . . 28 11.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 32
11.3. URN Sub-Namespace Registration for provided-by
11.3.3. MIME Content-type Registration for Registry Entry . . . . . . . . . . . . . . . . . . . . . . 32
'application/addDataDevInfo+xml' . . . . . . . . . . 30 11.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 33
11.3.4. MIME Content-type Registration for 11.4.1. MIME Content-type Registration for
'application/addCallSub+xml' . . . . . . . . . . . . 31 'application/addDataProviderInfo+xml' . . . . . . . . 33
11.4. URN Sub-Namespace Registration . . . . . . . . . . . . . . 32 11.4.2. MIME Content-type Registration for
11.4.1. Registration for 'application/addCallSvcInfo+xml' . . . . . . . . . . 34
urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 32 11.4.3. MIME Content-type Registration for
11.4.2. Registration for 'application/addDataDevInfo+xml' . . . . . . . . . . 35
urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 33 11.4.4. MIME Content-type Registration for
11.4.3. Registration for 'application/addCallSub+xml' . . . . . . . . . . . . 36
urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 34 11.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 38
11.4.4. Registration for urn:ietf:params:xml:ns:addCallSub . 35 11.5.1. Registration for
11.5. Schema Registrations . . . . . . . . . . . . . . . . . . . 36 urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 38
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 11.5.2. Registration for
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39 urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 38
13.1. Normative References . . . . . . . . . . . . . . . . . . . 39 11.5.3. Registration for
13.2. Informational References . . . . . . . . . . . . . . . . . 39 urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 41 11.5.4. Registration for urn:ietf:params:xml:ns:addCallSub . 40
11.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 41
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 43
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44
13.1. Normative References . . . . . . . . . . . . . . . . . . . 44
13.2. Informational References . . . . . . . . . . . . . . . . . 44
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 46
1. Introduction 1. Introduction
As communications devices increasingly utilize the Internet to As communications devices increasingly utilize the Internet to
interconnect and communicate, users will expect to use such devices interconnect and communicate, users will expect to use such devices
to request help. The Internet Protocol suite provides many to request help. The Internet Protocol suite provides many
advantages but also requires re-thinking of the traditional emergency advantages but also requires re-thinking of the traditional emergency
calling architecture. The IETF emergency services architecture, as calling architecture. The IETF emergency services architecture, as
described in [I-D.ietf-ecrit-framework] and described in [RFC6443] and [I-D.ietf-ecrit-phonebcp], offers a much
[I-D.ietf-ecrit-phonebcp], offers a much richer communication richer communication exchange and thereby better situational
exchange and thereby better situational awareness for call takers. awareness for call takers. The richness comes in various forms,
The richness comes in various forms, including the multi-media including the multi-media communication capabilities (via voice,
communication capabilities (via voice, video, instant messaging, and video, instant messaging, and real-time text), but also via more
real-time text), but also via more extensive flow of information. extensive flow of information. Sharing information between various
Sharing information between various actors will enable more actors will enable more intelligent decision making and therefore
intelligent decision making and therefore better response in case of better response in case of an emergency. A pre-requisite is to offer
an emergency. A pre-requisite is to offer the technical capabilities the technical capabilities to let call takers to gain access to this
to let call takers to gain access to this information stored information stored elsewhere (granted that they are authorized to
elsewhere (granted that they are authorized to access it). access it).
In general, there are four types of data exchanged: In general, there are four types of data exchanged:
Data Associated with a Call: A lot of information is carried in the Data Associated with a Call: While information is carried in the
call setup procedure itself (as part of the SIP headers as well as 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 in the body of the SIP message, there is additional data known by
capabilities of the device). This also includes information about the device making the call, or a service provider in the path of
the emergency caller's identity. the call including contact data, subscriber data, service data and
device data.
Data Associated with a Location: Location information is available Data Associated with a Location: Location information is available
via the PIDF-LO element, which includes civic and geospatial via the PIDF-LO element, which includes civic and geospatial
location, information about the entity that provided the data, location, information about the entity that provided the data,
information about how the location was obtained (as expressed by information about how the location was obtained (as expressed by
the <method> element, see Section 2.2.3 of [RFC4119], and the the <method> element, see Section 2.2.3 of [RFC4119], and the
values registered in values registered in
http://www.iana.org/assignments/method-tokens/method-tokens.xml), http://www.iana.org/assignments/method-tokens/method-tokens.xml),
and which entity or organization supplied location information and which entity or organization supplied location information
(beyond the domain information that can be inferred from a signing (beyond the domain information that can be inferred from a signing
certificate) available via the <provided-by> element. certificate) available via the <provided-by> element. However,
there may be data that is specific to the location not available
in the PIDF, such as floor plan, tenant and building owner contact
data, HVAC status, etc.
Data Associated with a Caller: This is personal data about a caller, Data Associated with a Caller: This is personal data about a caller,
including medical information. including medical information and emergency contact data.
Data associated with a PSAP: When a PSAP handles a call it develops Data associated with a PSAP: When a PSAP handles a call it develops
information about the call, which must be passed to subsequent information about the call, which must be passed to subsequent
PSAPs, dispatchers and/or responders. PSAPs, dispatchers and/or responders.
When an emergency call is sent to a PSAP, there is a rich set of data When an emergency call is sent to a PSAP, while there is a rich set
in the SIP message used for the call setup, but the device, as well of data in the SIP message used for the call setup, the device, as
as any other service provider in the path may have even more well as any other service provider in the path may have even more
information useful for a PSAP. This information may include the information useful for a PSAP. This information may include the
identity and contact information of the service provider, subscriber identity and contact information of the service provider, subscriber
identity and contact information, the type of service the provider identity and contact information, the type of service the provider
offers, what kind of device the user has, etc. Some data is device offers, what kind of device is being used, etc. Some data is device
or service dependent data. For example, a car telematics system or or service dependent data. For example, a car telematics system or
service may have crash information. A medical monitoring device may service may have crash information. A medical monitoring device may
have sensor data. While the details of the information may vary by 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 device or service, there needs to be a common way to send such data
to a PSAP. to a PSAP.
This document focuses on the data that can be obtained about a call This document focuses only on the data that can be obtained about a
and a mechanism for transporting it in an existing SIP header field, call and a mechanism for transporting it in an existing SIP header
the Call-Info header, which is specified in Section 20.9 of field, the Call-Info header, which is specified in Section 20.9 of
[RFC3261]. For this purpose a new token, namely 'emergencyCallData' [RFC3261]. For this purpose a new token, namely 'emergencyCallData'
is defined to be carried in the "purpose" parameter. If the is defined to be carried in the "purpose" parameter. If the
"purpose" parameter is set to 'emergencyCallData' then the Call-Info "purpose" parameter is set to 'emergencyCallData' then the Call-Info
header contains a HTTPS URL that points to a data structure with header contains a HTTPS URL that points to a service and data
information about the call or a CID that allows the data structure to structure with information about the call or is a CID that allows the
be placed in the body of the message. Section 8 shows a SIP INVITE data structure itself to be placed in the body of the message.
example containing such a Call-Info header. Section 8 shows a SIP INVITE example containing such a Call-Info
header using the purpose parameter.
Besides a service provider in the path of a call, the access network Besides a service provider in the path of a call, the access network
(which in the IETF emergency call architecture provides location in (which in the IETF emergency call architecture provides location in
the form of a PIDF-LO [RFC4119]) also has similar information that the form of a PIDF-LO [RFC4119]) also has similar information that
would be valuable to the PSAP. This information is not specific to would be valuable to the PSAP. This information is not specific to
the location itsef, but rather to the immmediate circumstances about the location itsef, but rather would provide descriptive information
the provision of the location (who the access network is, how to having to do with the immediate circumstances about the provision of
contact that entity, what kind of service the access network the location (who the access network is, how to contact that entity,
provides, possibly subscriber data, etc.). This data is in nearly what kind of service the access network provides, possibly subscriber
every respect similar to the data known by services providers in the data, etc.). This data is similar in nearly every respect with the
path of the call. For this reason, this document describes a data known by services providers in the path of the call. For this
"provided-by" namespace per [RFC4119] for passing information known reason, this document describes a "provided-by" namespace per
to the access network. [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.
skipping to change at page 7, line 18 skipping to change at page 8, line 18
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.
Two mechanisms are provided to transport the data set, namely Two mechanisms are provided to transport the data set, namely
1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE 1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE
transaction with a Call-Info header containing a purpose of transaction with a Call-Info header containing a purpose of
"emergenyCallData". If the data is provided by reference, it may "emergencyCallData". If the data is provided by reference, it
be retrieved with an HTTPS Get from the URI. The URI MUST 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 specify an HTTPS scheme, and TLS protection for the data MUST be
negotiated. negotiated.
2. The data may be supplied by value in a SIP INVITE or MESSAGE 2. The data may be supplied by value in a SIP INVITE or MESSAGE
message. In this case, Content Indirection (CID) [RFC2392] is message. In this case, Content Indirection (CID) [RFC2392] is
used, with the CID URL pointing to the body of the message. 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, but at least one MUST be provided. The device MUST
provider MAY insert its own. When there are multiple intermediaries, provide one if no service provider is in the path of the call. The
each intermediary MAY each insert one. For example, a device may device MAY insert one if it uses a service provider, and any
provide one, a telematics service provider may provide one and the intermediary service provider SHOULD insert its own. When there are
mobile carrier handling the call may provide one. multiple intermediaries, each intermediary SHOULD 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. There may be circumstances where there is a service provider
who is unaware that the call is an emergency call and cannot
reasonably be expected to determine that it is an emergency call. In
that case, that service provider is not expected to provide
emergencyCallData.
Note: The access network MAY supply additional data as well. For Note: The access network MAY supply additional data as well. For
this purpose, this document defines a namespace and adds the this purpose, this document defines a namespace and adds the
namespace to the "provided-by" registry defined by PIDF-LO [RFC4119]. namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].
Additional data about a call is defined as a series of MIME objects, Additional data about a call is defined as a series of MIME objects,
each with an XML data structure contained inside. MIME-multipart is each with an XML data structure contained inside. MIME-multipart is
used to enclose the XML documents and the sections below define them. used to enclose the XML documents and the sections below define them.
4. Data Provider Information 4. Data Provider Information
skipping to change at page 8, line 38 skipping to change at page 9, line 38
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.
4.2. Data Provider ID 4.2. Data Provider ID
Data Element: Data Provider ID Data Element: Data Provider ID
Use: Conditional Use: Conditional. Must be provided if the service provider is
located in a jurisdiction that maintains such ids. Devices are
not required to provide it.
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. This data SHOULD be provided if the local jurisdiction call. This data SHOULD be provided if the local jurisdiction
maintains such an ID list. For example, in North America, this maintains such an ID list. For example, in North America, this
would be a "NENA Company ID". Devices would not typically use would be a "NENA Company ID". Devices would not typically use
this element. this element.
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.
skipping to change at page 9, line 13 skipping to change at page 10, line 17
maintains such an ID list. For example, in North America, this maintains such an ID list. For example, in North America, this
would be a "NENA Company ID". Devices would not typically use would be a "NENA Company ID". Devices would not typically use
this element. this element.
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 Data Provider ID can lead to a wealth of information. the Data Provider ID can lead to a wealth of information.
4.3. Data Provider Contact URI 4.3. Type of Data Provider ID
Data Element: Type of Data Provider ID
Use: Conditional. If Data Provider ID is provided, Type of Data
Provider ID is required.
XML Element: <TypeOfProviderID>
Description: Identifies the type of data provider id being supplied
in the ProviderId data element. A registry will reflect the
following valid entries:
* NENA (CDMA)
* Other
Reason for Need: Identifies how to interpret the Data Provider ID.
How Used by Call Taker: Determines which provider ID registry to
consult for more information
4.4. Data Provider Contact URI
Data Element: Data Provider Contact URI Data Element: Data Provider Contact URI
Use: Required Use: Required
XML Element: <ContractURI> XML Element: <ContactURI>
Description: For a service provider the contact SHOULD be a contact Description: For a service provider the contact SHOULD be a contact
URI. This must be a SIP URI. If a telephone number is the URI. This must be a SIP URI. If a telephone number is 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 would reflect the contact information of the
contact information of the owner of the device. This should be a owner of the device. When provided by a service provider, this
URI to a 24/7 support organization tasked to provide PSAP support would be a URI to a 24/7 support organization tasked to provide
for this emergency call. 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 for assistance in handling the call.
4.4. Data Provider Languages(s) Supported 4.5. 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: <Language>
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 if a Data Provider Contact URI is provided. The content required if a Data Provider Contact URI is provided. The content
must reflect the languages supported at the contact URI. must reflect the languages supported at the contact URI.
skipping to change at page 10, line 17 skipping to change at page 12, line 7
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 if a Data Provider Contact URI is provided. The content required if a Data Provider Contact URI is provided. The content
must reflect the languages supported at the contact URI. must reflect the languages supported at the contact URI.
Reason for Need: Information needed to determine if emergency Reason for Need: Information needed to determine if emergency
service authority can communicate with the service provider or if service authority can communicate with the service provider or if
language line will be needed. an interpreter 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, at translation service will supported by the service provider, a translation service will need
need to be added in to the conversation. to be added to the conversation.
4.5. vCARD of Data Provider 4.6. 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 and the creator of Description: There are many fields in the xCARD and the creator of
the data structure is encouraged to provide as much information as the data structure is encouraged to provide as much information as
they have available. For encoding of the vCard this specification they have available. N, ORG, ADR, TEL, EMAIL are suggested at a
uses the XML-based encoding specified in [RFC6351]. minimum. N should contain name of support group or device owner
as appropriate. For encoding of the vCard this specification uses
the XML-based encoding specified in [RFC6351].
and is hereinafter referred to as "xCard"
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. the PIDF-LO.
4.6. addDataProviderInfo XML Schema 4.7. addDataProviderInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:addDataProviderInfo" targetNamespace="urn:ietf:params:xml:ns:addDataProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:addDataProviderInfo" xmlns:ad="urn:ietf:params:xml:ns:addDataProviderInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:simpleType name="iso3166a2"> <xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/> <xs:pattern value="[A-Z]{2}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:element name="DataAssociatedWithCall"> <xs:element name="addDataProviderInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderString" <xs:element name="DataProviderString"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="DataProviderString" <xs:element name="ProviderID"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI" <xs:element name="TypeOfProvider"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI"
minOccurs="1" maxOccurs="1"/> minOccurs="1" maxOccurs="1"/>
<xs:element name="Language" type="ad:iso3166a2" <xs:element name="Language" type="ad:iso3166a2"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
<xs:element name="DataProviderContact" <xs:element name="DataProviderContact"
type="vc:vcards" minOccurs="0" maxOccurs="1"> type="vc:vcards" minOccurs="0" maxOccurs="1">
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
skipping to change at page 12, line 26 skipping to change at page 14, line 26
XML Element: <SvcEnvironment> XML Element: <SvcEnvironment>
Description: This element defines whether a call is from a business Description: This element defines whether a call is from a business
or residence caller. Currently, the only valid entries are or residence caller. Currently, the only valid entries are
'Business' 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 assist in
equipment and manpower requirements for emergency responders. determining equipment and manpower requirements for emergency
responders. As the information is not always available, and the
registry is not all encompassing, this is at best advisory
information, but since it mimics a similar capability in some
current emergency calling systems, it is known to be valuable.
The service provider uses it's best information (such as a rate
plan, facilities used to deliver service or service description)
to determine the information and is not responsible for
determining the actual characteristics of the location where the
call originates from.
5.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 initial valid relied upon. A registry will reflect the following initial valid
entries: entries:
* Mobile Telephone Service: Includes Satellite, CDMA, GSM, Wi-Fi, * Wireless Telephone Service: Includes Satellite, CDMA, GSM,
WiMAX, LTE (Long Term Evolution) Wi-Fi, 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
* Soft dialtone/quick service/warm disconnect/suspended * Soft dialtone/quick service/warm disconnect/suspended
skipping to change at page 13, line 31 skipping to change at page 15, line 40
* 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
* Relay Service: a type of service where there is a human 3rd
party agent who provides some kind of additional assistance to
the caller. Includes sign language relay and telematics
services which provide a service assistant on the call.
* Remote (off premise extension)
There can be more than one value returned. For example, a VoIP There can be more than one value returned. For example, a VoIP
prison telephone service is a reasonable conbination. prison telephone service is a reasonable combination.
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: Calltakers often use this information to How Used by Call Taker: Call takers often use this information to
determine what kinds of questions to ask callers, and how much to determine what kinds of questions to ask callers, and how much to
rely on supportive information. An emergency call from a prison rely on supportive information. An emergency call from a prison
is treated differently that a call from a sensor device. is treated differently that a call from a sensor device. As the
information is not always available, and the registry is not all
encompassing, this is at best advisory information, but since it
mimics a similar capability in some current emergency calling
systems, it is known to be valuable.
5.3. addCallSvcInfo XML Schema 5.3. Service Mobility Environment
<?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" Data Element: Service Mobility Environment
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="addCallSvcInfo"> Use: Required
<xs:complexType>
<xs:sequence> XML Element: <SvcMobility>
<xs:element name="SvcEnvironment"
type="xs:string" minOccurs="0" maxOccurs="1"/> Description: This provides the service providers view of the
<xs:element name="SvcDelByProvider" mobility of the caller. As the service provider may not know the
type="xs:string" minOccurs="0" maxOccurs="1"/> characteristics of the actual access network used, the value not
</xs:sequence> be relied upon. A registry will reflect the following initial
</xs:complexType> valid entries:
</xs:element>
</xs:schema> * Mobile: the device should be able to move at any time
* Fixed: the device is not expected to move unless the service is
relocated
* Nomadic: the device is not expected to move while on a call,
but may move between calls
Reason for Need: Knowing the service provider's belief of mobility
may assist the PSAP with the handling of the call.
How Used by Call Taker: To determine whether to assume the location
of the caller might change.
5.4. 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="unbounded"/>
<xs:element name="SvcMobility"
type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 2: addCallSvcInfo XML Schema Figure 2: addCallSvcInfo XML Schema
6. Device Information 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+xml". "addDataDevInfo+xml".
6.1. Device Classification 6.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: This data element defines the kind of device making the
information should be provided. If the service provider provides emergency call. If the device provides the data structure, the
the structure and it knows what the device is, the service device information should be provided. If the service provider
provider should provide the device information. Often the carrier provides the structure and it knows what the device is, the
does not know what the device is. It is possible to receive 2 service provider should provide the device information. Often the
data structures, one created by the device and one created by the carrier does not know what the device is. It is possible to
service provider. Information about the device, not how it is receive 2 Additional Data Associated with a Caller data
being used. This data element defines the kind of device making structures, one created by the device and one created by the
the emergency call. A registry will reflect the following valid service provider. This Information describes the about the
entries: 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 * Cordless handset
* Fixed phone * Fixed phone
* Mobile handset * Mobile handset
* ATA - analog terminal adapter * ATA - analog terminal adapter
* Satellite phone * Satellite phone
skipping to change at page 16, line 37 skipping to change at page 19, line 39
* Gaming console * Gaming console
* Video phone * Video phone
* Other text device * Other text device
* Not Available * Not Available
Reason for Need: The device classification describes the capability Reason for Need: The device classification describes the capability
of the calling device. For example, does the device require human of the calling device and assists in identifying the meaning of
intervention to initiate a call or is this call the result of the emergency call location information that is being presented.
programmed instructions. Does the calling device have the ability For example, does the device require human intervention to
to rebid for location or condition changes? Is this device initiate a call or is this call the result of programmed
interactive or a one-way reporting device? instructions?. Does the calling device have the ability to update
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 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, the capabilities
of the device used for the call or the environment the device is
being used in.
6.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: The plain language name of the manufacturer of the Description: The plain language name of the manufacturer of the
skipping to change at page 18, line 23 skipping to change at page 21, line 29
Reason for Need: Uniquely identifies the device as opposed to any Reason for Need: Uniquely identifies the device as opposed to any
signaling identifiers encountered in the call signaling stream. signaling identifiers encountered in the call signaling stream.
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.
6.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: Conditional: must be provided if DeviceID is provided
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:
* MEID (CDMA) * MEID (CDMA)
* ESN (Electronic Serial Number - superseded by MEID) * ESN (Electronic Serial Number - superseded by MEID)
skipping to change at page 19, line 19 skipping to change at page 22, line 26
* Manufacturer Serial Number * Manufacturer Serial Number
* Other * Other
Reason for Need: Identifies how to interpret the Unique Device Reason for Need: Identifies how to interpret the Unique Device
Identifier. 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.
6.6. Device/Service Specific Additional Data Structure Type 6.6. Device/Service Specific Additional Data 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 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.
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.7. Device/Service Specific Additional Data Structure Type
Data Element: Type of Device/service specific additional data Data Element: Type of Device/service specific additional data
structure structure
Use: Conditional. MUST be provided when Device/service specific Use: Conditional. MUST be provided when Device/service specific
additional URI is provided additional URI is provided
XML Element: <devicespecificType> XML Element: <devicespecificType>
Description: Value from a registry defined by this document to Description: Value from a registry defined by this document to
describe the type of data that can be retrieved from the Device/ describe the type of data that can be retrieved from the Device/
service specific additional data structure. Initial values are: 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 Model
* IEEE 1512 - USDOT Model for traffic incidents * IEEE 1512 - USDOT Model for traffic incidents
* Smart Building (NIST)
* VEDS * VEDS
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.
6.7. Device/Service Specific Additional Data Structure Note: Information which is specific to a location or a caller
(person) should not be placed in this section.
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 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.
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 6.8. addDataDevInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo" targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:addDataDevInfo" xmlns:svc="urn:ietf:params:xml:ns:addDataDevInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
skipping to change at page 22, line 15 skipping to change at page 25, line 15
7. Owner/Subscriber Information 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+xml". The mime type is "addCallSub+xml".
7.1. vCARD for Subscriber's Data 7.1. vCARD for Subscriber's Data
Data Element: vCARD for Subscriber's Data Data Element: xCARD for Subscriber's Data
Use: Required Use: Conditional: Some services (e.g. prepaid phones, initialized
phones, etc.) may not have this information.
XML Element: <SubscriberData> XML Element: <SubscriberData>
Description: Information known by the service provider or device Description: Information known by the service provider or device
about the subscriber; i.e., Name, Address, Calling Party Number, about the subscriber; i.e., Name, Address, Individual Telephone
Main Telephone Number and any other data. If the subscriber is an Number, Main Telephone Number and any other data. N, ORG (if
enterprise, this is the vCARD of the enterprise and the Company appropriate), ADR, TEL, EMAIL are suggested at a minimum.
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: Critical information required for proper call Reason for Need: When the caller is unable to provide information,
handling and dispatching. this data may be used to obtain it
How Used by Call Taker: Critical information required for proper How Used by Call Taker: Obtaining critical information about the
call handling and dispatching. caller and possibly the location when it is not able to be
obtained otherwise.
7.2. addCallSub XML Schema 7.2. addCallSub XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:addCallSub" targetNamespace="urn:ietf:params:xml:ns:addCallSub"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:addCallSub" xmlns:sub="urn:ietf:params:xml:ns:addCallSub"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
skipping to change at page 27, line 7 skipping to change at page 30, line 7
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.
11. IANA Considerations 11. IANA Considerations
[Editor's Note: The IANA section is missing the description of new 11.1. Registry creation
registries. A future version of this draft will contain the
necessary information.]
11.1. 'emergencyCallData' Purpose Parameter Value 11.1.1. Additional Call Data Service Delivered Registry
This document creates a new registry called 'Additional Call Data
Service Delivered'. As defined in [RFC5226], this registry operates
under "Expert Review" rules.
The content of this registry includes:
Name: enumeration token of the service.
Description: Short description identifying the service.
The values defined are:
+--------+----------------------------------------+
| Name | description |
+--------+-------+--------------------------------+
| Wrless | Wireless Telephone Service: Includes |
| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
| | LTE (Long Term Evolution) |
| Coin | Fixed Public Pay/Coin telephones: Any |
| | coin or credit card operated device |
| 1way | One way outbound service |
| Prison | Inmate call/service |
| Temp | Soft dialtone/quick service/warm |
| | disconnect/suspended |
| MLTS | Multi-line telephone system: Includes |
| | all PBX, Centrex, key systems, |
| | Shared Tenant Service |
| SenseU | Sensor, unattended: Includes devices |
| | that generate DATA ONLY. This is |
| | one-way information exchange and |
| | there will be no other form of |
| | communication |
| SenseA | Sensor, attended: Includes devices |
| | that are supported by a monitoring |
| | service provider or automatically |
| | open a two-way communication path |
| POTS | Wireline: Plain Old Telephone Service |
| VOIP | VoIP Telephone Service: A type of |
| | service that offers communication |
| | over internet protocol, such as Fixed|
| | Nomadic, Mobile, ... |
+--------+-------+--------------------------------+
11.1.2. Additional Call Data Device Classification Registry
This document creates a new registry called 'Additional Call Data
Device Classification'. As defined in [RFC5226], this registry
operates under "Expert Review" rules.
The content of this registry includes:
Name: enumeration token of the device classification.
Description: Short description identifying the device type.
The values defined are:
+--------+----------------------------------------+
| Name | description |
+--------+-------+--------------------------------+
|Cordless| Cordless handset |
| Fixed | Fixed phone |
| Mobile | Mobile handset |
| ATA | analog terminal adapter |
|Satphone| Satellite phone |
| FSense | Stationary computing device (alarm |
| | system, data sensor) |
| Guard | Guardian devices |
| Desktop| Desktop PC |
| Laptop | Laptop computing device |
| Tablet | Tablet computing device |
| Alarm | Alarm system |
| MSense | Mobile Data sensor |
| Beacon | Personal beacons (spot) |
| Auto | Auto telematics |
| Truck | Truck telematics |
| Farm | Farm equipment telematics |
| Marine | Marine telematics |
| PDA | Personal digital assistant |
| PND | Personal navigation device) |
| SmrtPhn| Smart phone |
| Itab | Internet tablet |
| Game | Gaming console |
| Video | Video phone |
| Text | Other text device |
| NA | Not Available |
+--------+----------------------------------------+
11.1.3. Additional Call Data Device ID Type Registry
This document creates a new registry called 'Additional Call Data
Device ID Type'. As defined in [RFC5226], this registry operates
under "Expert Review" rules.
The content of this registry includes:
Name: enumeration token of the device id type.
Description: Short description identifying the type of device id.
The values defined are:
+--------+----------------------------------------+
| Name | description |
+--------+-------+--------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) |
| ESN | Electronic Serial Number(GSM) |
| MAC | Media Access Control Address (IEEE) |
| WiMAX | device certificate unique id |
| IMEI | International Mobile Equipment ID (GSM)|
| UDI | Unique Device Identifier (medical) |
| RFID | Radio Frequency Identification |
| Sense | Sensors (types to be identified ) |
| SN | Manufacturer Serial Number |
| Other | Other |
+--------+----------------------------------------+
11.2. '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. The Call-Info header and parameter of the Call-Info header field. The Call-Info header and
the corresponding registry for the 'purpose' parameter was the corresponding registry for the 'purpose' parameter was
established with RFC 3261 [RFC3261]. established with RFC 3261 [RFC3261].
Header Parameter New Header Parameter New
Field Name Value Reference Field Name Value Reference
---------- --------- ----------------- --------- ---------- --------- ----------------- ---------
Call-Info purpose emergencyCallData [This RFC] Call-Info purpose emergencyCallData [This RFC]
11.2. URN Sub-Namespace Registration for provided-by Registry Entry 11.3. 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 RFC 4119. provided-by registry established by RFC 4119.
11.3. MIME Registrations 11.4. MIME Registrations
11.3.1. MIME Content-type Registration for 'application/ 11.4.1. MIME Content-type Registration for 'application/
addDataProviderInfo+xml' addDataProviderInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: addDataProviderInfo+xml MIME subtype name: addDataProviderInfo+xml
skipping to change at page 28, line 41 skipping to change at page 34, line 16
Personal and email address for further information: Hannes Personal and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
11.3.2. MIME Content-type Registration for 'application/ 11.4.2. MIME Content-type Registration for 'application/
addCallSvcInfo+xml' addCallSvcInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: addCallSvcInfo+xml MIME subtype name: addCallSvcInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
Encoding considerations: Encoding considerations:
Uses XML, which can employ 8-bit characters, depending on the Uses XML, which can employ 8-bit characters, depending on the
character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 30, line 5 skipping to change at page 35, line 29
Personal and email address for further information: Hannes Personal and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
11.3.3. MIME Content-type Registration for 'application/ 11.4.3. MIME Content-type Registration for 'application/
addDataDevInfo+xml' addDataDevInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: addDataDevInfo+xml MIME subtype name: addDataDevInfo+xml
skipping to change at page 31, line 14 skipping to change at page 36, line 41
Personal and email address for further information: Hannes Personal and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
11.3.4. MIME Content-type Registration for 'application/addCallSub+xml' 11.4.4. MIME Content-type Registration for 'application/addCallSub+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: addCallSub+xml MIME subtype name: addCallSub+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Optional parameters: charset
Indicates the character encoding of enclosed XML. Indicates the character encoding of enclosed XML.
Encoding considerations: Encoding considerations:
Uses XML, which can employ 8-bit characters, depending on the Uses XML, which can employ 8-bit characters, depending on the
character encoding used. See Section 3.2 of RFC 3023 [RFC3023]. character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 32, line 24 skipping to change at page 38, line 5
Personal and email address for further information: Hannes Personal and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
11.4. URN Sub-Namespace Registration 11.5. URN Sub-Namespace Registration
11.4.1. Registration for urn:ietf:params:xml:ns:addDataProviderInfo 11.5.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
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:addDataProviderInfo 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:
skipping to change at page 33, line 24 skipping to change at page 38, line 38
Data Provider Information</title> Data Provider Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Data Provider Information</h2> <h2>Data Provider Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
11.4.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo 11.5.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:addCallSvcInfo URI: urn:ietf:params:xml:ns:addCallSvcInfo
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:
skipping to change at page 34, line 24 skipping to change at page 39, line 26
Service Information</title> Service Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Service Information</h2> <h2>Service Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
11.4.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo 11.5.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:addDataDevInfo URI: urn:ietf:params:xml:ns:addDataDevInfo
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:
skipping to change at page 35, line 24 skipping to change at page 40, line 24
Device Information</title> Device Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Device Information</h2> <h2>Device Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
11.4.4. Registration for urn:ietf:params:xml:ns:addCallSub 11.5.4. Registration for urn:ietf:params:xml:ns:addCallSub
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:addCallSub URI: urn:ietf:params:xml:ns:addCallSub
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:
skipping to change at page 36, line 24 skipping to change at page 41, line 24
Owner/Subscriber Information</title> Owner/Subscriber Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2> Owner/Subscriber Information</h2> <h2> Owner/Subscriber Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
11.5. Schema Registrations 11.6. Schema Registrations
This specification registers four schemas, as per the guidelines in This specification registers four schemas, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: URI:
urn:ietf:params:xml:schema:additional-data:addDataProviderInfo urn:ietf:params:xml:schema:additional-data: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).
skipping to change at page 39, line 32 skipping to change at page 44, line 32
[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 [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", BCP 13, RFC 4288, December 2005. Registration Procedures", BCP 13, RFC 4288, December 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC6351] Perreault, S., "xCard: vCard XML Representation", [RFC6351] Perreault, S., "xCard: vCard XML Representation",
RFC 6351, August 2011. RFC 6351, August 2011.
13.2. Informational References 13.2. Informational References
[I-D.iab-privacy-considerations] [I-D.iab-privacy-considerations]
Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., and Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., and
J. Morris, "Privacy Considerations for Internet J. Morris, "Privacy Considerations for Internet
Protocols", draft-iab-privacy-considerations-01 (work in Protocols", draft-iab-privacy-considerations-02 (work in
progress), October 2011. progress), March 2012.
[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] [I-D.ietf-ecrit-phonebcp]
Rosen, B. and J. Polk, "Best Current Practice for Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in support of Emergency Calling", Communications Services in support of Emergency Calling",
draft-ietf-ecrit-phonebcp-20 (work in progress), draft-ietf-ecrit-phonebcp-20 (work in progress),
September 2011. September 2011.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 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
 End of changes. 78 change blocks. 
253 lines changed or deleted 458 lines changed or added

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