draft-ietf-ecrit-additional-data-00.txt   draft-ietf-ecrit-additional-data-01.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: March 25, 2011 Nokia Siemens Networks Expires: January 13, 2012 Nokia Siemens Networks
September 21, 2010 July 12, 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-00.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 PSAP, the device that sends it,
as well as any service provider in the path of the call may have as well as any service provider in the path of the call, or access
information about the call which the PSAP may be able to use. This network may have information about the call which the PSAP may be
document describes an XML data structure that contains this kind of able to use. This document describes an XML data structure that
information in a standardized form. A URI that points to the contains this kind of information in a standardized form. A URI that
structure can be included in the SIP signaling with the call. points to the structure can be included in the SIP signaling with the
call, or the data may be included in the body of a SIP message.
Status of this Memo 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 March 25, 2011. This Internet-Draft will expire on January 13, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2010 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Additional Data about a Call . . . . . . . . . . . . . . . . . 5 3. Additional Data about a Call . . . . . . . . . . . . . . . . . 5
3.1. Data Provided by . . . . . . . . . . . . . . . . . . . . . 5 3.1. Data Provider Information Block . . . . . . . . . . . . . 5
3.2. Provided by Company ID . . . . . . . . . . . . . . . . . . 6 3.1.1. Data Provider String . . . . . . . . . . . . . . . . . 6
3.3. Provided by Contact URI . . . . . . . . . . . . . . . . . 6 3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . . 6
3.4. Provided by Languages(s) supported . . . . . . . . . . . . 7 3.1.3. Data Provider Contact URI . . . . . . . . . . . . . . 7
3.5. vCARD of Provided By . . . . . . . . . . . . . . . . . . . 7 3.1.4. Data Provider Languages(s) supported . . . . . . . . . 7
3.6. Service Environment . . . . . . . . . . . . . . . . . . . 8 3.1.5. vCARD of Data Provider . . . . . . . . . . . . . . . . 8
3.7. Service Delivered by Provider to End User . . . . . . . . 8 3.2. Service Information . . . . . . . . . . . . . . . . . . . 9
3.8. Device Classification . . . . . . . . . . . . . . . . . . 10 3.2.1. Service Environment . . . . . . . . . . . . . . . . . 9
3.9. Device Manufacturer . . . . . . . . . . . . . . . . . . . 11 3.2.2. Service Delivered by Provider to End User . . . . . . 9
3.10. Device Model Number . . . . . . . . . . . . . . . . . . . 12 3.3. Device Information . . . . . . . . . . . . . . . . . . . . 10
3.11. Unique Device Identifier . . . . . . . . . . . . . . . . . 12 3.3.1. Device Classification . . . . . . . . . . . . . . . . 10
3.12. Type of Device Identifier . . . . . . . . . . . . . . . . 13 3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 12
3.13. Device/service specific additional data structure . . . . 14 3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 13
3.14. Telephone Number Privacy Indicator . . . . . . . . . . . . 15 3.3.4. Unique Device Identifier . . . . . . . . . . . . . . . 13
3.15. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 16 3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 14
4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3.3.6. Device/service specific additional data structure . . 15
5. Security Considerations . . . . . . . . . . . . . . . . . . . 19 3.4. Regulatory Information . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 3.4.1. Telephone Number Privacy Indicator . . . . . . . . . . 16
6.1. 'emergencyCallData' Purpose Parameter Value . . . . . . . 20 3.5. Owner/Subscriber Information . . . . . . . . . . . . . . . 17
6.2. URN Sub-Namespace Registration for 3.5.1. vCARD for Subscriber's Data . . . . . . . . . . . . . 17
urn:ietf:params:xml:ns:additional-data . . . . . . . . . . 20 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 18
6.3. Additional Data Schema Registration . . . . . . . . . . . 21 5. Security Considerations . . . . . . . . . . . . . . . . . . . 20
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
8. Normative References . . . . . . . . . . . . . . . . . . . . . 23 6.1. 'emergencyCallData' Purpose Parameter Value . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2. provided-by registry entry . . . . . . . . . . . . . . . . 21
6.3. MIME registrations . . . . . . . . . . . . . . . . . . . . 21
6.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:additional-data . . . . . . . . . . 21
6.5. Additional Data Schema Registration . . . . . . . . . . . 22
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23
8. Normative References . . . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 25
1. Introduction 1. Introduction
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, there is a rich set of data
in the headers with the call, but the device, as well as any other in the headers with the call, but the device, as well as any other
service provider in the path may have even more information that service provider in the path may have even more information that
would be useful to a PSAP. This information may include the identity would be useful to 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 service provider and contact information, the type of service the service provider
provides, what kind of device the user has, etc. Some kinds of provides, what kind of device the user has, etc. Some kinds of
skipping to change at page 3, line 27 skipping to change at page 3, line 27
While the details of the information may vary by device or service, 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. there needs to be a common way to send such data to a PSAP.
For the call takers this will enable more intelligent decision making For the call takers this will enable more intelligent decision making
and therefore better response in case of an emergency. A pre- and therefore better response in case of an emergency. A pre-
requisite is to offer the technical capabilities to let call takers requisite is to offer the technical capabilities to let call takers
to gain access to this information stored elsewhere (granted that to gain access to this information stored elsewhere (granted that
they have authorization to access it). they have authorization to access it).
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 an existing SIP header field, the Call-Info header, is used for and a mechanism for transporting it in an existing SIP header field,
this purpose by defining a new token, namely 'emergencyCallData' the Call-Info header. For this purpose a new token, namely
carried in the "purpose" parameter. If the "purpose" parameter set 'emergencyCallData' is defined to be carried in the "purpose"
to 'emergencyCallData' then the Call-Info contains a HTTPS URL that parameter. If the "purpose" parameter set to 'emergencyCallData'
points to an XML data structure with information about the call. The then the Call-Info contains a HTTPS URL that points to a data
initial XML data structure was defined by a working group within the structure with information about the call or a CID that allows the
National Emergency Number Association (NENA) and is included in this data structure to be placed in the body of the message. In addition,
document. 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
information. Each of the blocks is a MIME type, and an extensible
set of these types constitute the data structure. A registry is
defined to list the block types that may be included.
The data structure contains an element which itself is a URI that has 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. Additional Data about a Call
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. The Additional Data about a Call is an XML data of a call or in the access network the call originates in. The
structure. An HTTPS URI to that structure may be inserted in a SIP Additional Data about a Call is a set of information blocks. Each
INVITE or MESSAGE transaction with a Call-Info header containing a block is a MIME type, and any set of blocks may be included in the
purpose of "emergenyCallData". The data, which must conform to the set.
schema in Section 4 may be retrieved with an HTTPS Get. HTTPS MUST be
used. Three mechanisms are provided to transport the data set. 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 "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.
In this case, Content Indirection [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.
3.1. Data Provided by The access network may supply Additional Data about a Call. For this
purpose, this document defines a namespace and adds the namespace to
the "provided-by" registry defined by [RFC4119]
Data Element: Data Provided by Additional Data about a Call is defined as a series of blocks. Each
block is defined as a mime type, with an XML data structure. MIME-
multipart is used to enclose the set of blocks constituting the
information provided by an entity (service provider or device). The
sections below define the blocks.
3.1. Data Provider Information Block
This block is intended to be provided by any service provider in the
path of the call or the access network provider. It includes
identification and contact information. This block SHOULD be
provided for every service provider in the path of the call, and the
access network provider. Devices also use this block to provide
identifying information. The MIME type is "addDataProviderInfo".
3.1.1. Data Provider String
Data Element: Data Provider String
Use: Required Use: Required
XML Element: <DataProvidedBy> 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. This data is
required and should reflect the contact information of the owner required and should reflect the contact information of the owner
of the device. 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.2. Provided by Company ID 3.1.2. Data Provider ID
Data Element: Provided by Company ID Data Element: Data Provider ID
Use: Conditional Use: Conditional
XML Element: <ProviderCompanyID> 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. NOTE: In the US, the NENA Company ID must appear here.
Additional information may be found at Additional information may be found at
http://www.nena.org/nena-company-id. The NENA Company ID shall be http://www.nena.org/nena-company-id. The NENA Company ID shall be
in the form of any URI for example: urn:nena:companyid:<NENA in the form of any URI for example: urn:nena:companyid:<NENA
Company ID>. This data is required unless the additional data Company ID>. This data is required unless the additional data
structure is provided by the device. 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 Provider Company ID can lead to a wealth of information
associated with the code. associated with the code.
3.3. Provided by Contact URI 3.1.3. Data Provider Contact URI
Data Element: Provided by 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 24x7 Description: For a Service Provider the contact SHOULD be a 24x7
contact number. If provided by an entity without a 24X7, they contact URI. This must be a SIP URI. If a telephone number is
must provide the provided by contact information. This must be a the contact address it should be provided in the form of
SIP URI. If a telephone number is the contact address it should
be provided in the form of
sip:telephonenumber@serviceprovider:user=phone. If the call is 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.
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.4. Provided by Languages(s) supported 3.1.4. Data Provider Languages(s) supported
Data Element: Provided by Language(s) supported Data Element: Data Provider Language(s) supported
Use: Conditional Use: Conditional
XML Element: <LanguagePreference> 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 unless the message is from a data only device.
Reason for Need: Information needed to determine if 9-1-1 Authority Reason for Need: Information needed to determine if 9-1-1 Authority
can communicate with the Service Provider or if language line will can communicate with the Service Provider or if language line will
skipping to change at page 7, line 35 skipping to change at page 8, line 20
required unless the message is from a data only device. required unless the message is from a data only device.
Reason for Need: Information needed to determine if 9-1-1 Authority Reason for Need: Information needed to determine if 9-1-1 Authority
can communicate with the Service Provider or if language line will can communicate with the Service Provider or if language line will
be needed. 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, language line will need to be
added in to conversation. added in to conversation.
3.5. vCARD of Provided By 3.1.5. vCARD of Data Provider
Data Element: vCARD of Provided By Data Element: vCARD of Data Provider
Use: Optional Use: Optional
XML Element: <ProvidedByContact> XML Element: <DataProviderContact>
Description: There are many fields in the vCARD. The creator of the Description: There are many fields in the vCARD. The creator of the
data structure is encouraged to provide as much information as data structure is encouraged to provide as much information as
they have available. A minimum of subscriber provided by's name, they have available. A minimum of subscriber provided by's name,
address and contact number should be provided. address and general contact number should be provided.
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. Can display a picture of the caller to the call
taker. taker.
3.6. Service Environment 3.2. Service Information
This block describes the service that the service provider provides
to the caller. It SHOULD be included by all SPs in the path of the
call. The mime type is "addCallSvcInfo"
3.2.1. 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 defines if the call service type is a Business or
Residence caller. Currently, the only valid entries are Business Residence caller. Currently, the only valid entries are Business
or Residence. 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.7. Service Delivered by Provider to End User 3.2.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 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
skipping to change at page 10, line 5 skipping to change at page 10, line 38
communication over internet protocol, such as Fixed, Nomadic, communication over internet protocol, such as Fixed, Nomadic,
Mobile, Unknown Mobile, Unknown
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: Calltaker may be able to determine if the
caller is stationary or mobile and if they will have voice caller is stationary or mobile and if they will have voice
communications with the caller or is it a data only event. communications with the caller or is it a data only event.
3.8. Device Classification 3.3. Device Information
This block provides information about the device used to place the
call. It should be provided by any service provider that knows what
device is being used, and by the device itself. The mime type is
"addDataDevInfo".
3.3.1. 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
skipping to change at page 11, line 4 skipping to change at page 11, line 46
* Laptop computing device * Laptop computing device
* Tablet computing device * Tablet computing device
* Alarm system * Alarm system
* Data sensor * Data sensor
* Personal beacons (spot) * Personal beacons (spot)
* Auto telematics (indicates VEDS data set)
* Auto telematics (indicates VEDS data set)
* Trucking telematics * Trucking telematics
* Farm equipment telematics * Farm equipment telematics
* Marine telematics * Marine telematics
* PDA (personal digital assistant) * PDA (personal digital assistant)
* PND (personal navigation device) * PND (personal navigation device)
skipping to change at page 11, line 39 skipping to change at page 12, line 37
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.9. Device Manufacturer 3.3.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. Description: Manufacturer is electronically stored on the device.
Different devices may use different conventions to provide their Different devices may use different conventions to provide their
information. We need to know what it represents, so a registry is information. We need to know what it represents, so a registry is
in order. Need to be able to standardize as much as possible with in order. Need to be able to standardize as much as possible with
a uniform naming convention. A registry will reflect the valid a uniform naming convention. A registry will reflect the valid
entries. 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.10. Device Model Number 3.3.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 is electronically stored on 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.11. Unique Device Identifier 3.3.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: Characters 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: May be needed when trying to obtain a subpoena to
obtain customer information in instances where location info did obtain customer information in instances where location info did
not display or someone is making false emergency calls. May also not display or someone is making false emergency calls. May also
be used when working with safe houses that are using non- be used when working with safe houses that are using non-
initialized phones. 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.12. Type of Device Identifier 3.3.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 14, line 4 skipping to change at page 14, line 43
Ethernet, Wi-Fi connection Ethernet, Wi-Fi connection
* 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 Reason for Need: Calls from uninitiated devices would give an
identifier that could be associated with erroneous calls --- use identifier that could be associated with erroneous calls --- use
the number to identify what type of capabilities there are. Could the number to identify what type of capabilities there are. Could
also use this information to block specific types of calls. also use this information to block specific types of calls.
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.13. Device/service specific additional data structure 3.3.6. Device/service specific additional data structure
Data Element: Device/service specific additional data structure Data Element: Device/service specific additional data structure
Use: Optional Use: Optional
XML Element: <devicespecificSchema> XML Element: <devicespecificSchema>
Description: A URI representing additional data whose schema is Description: A URI representing additional data whose schema is
specific to the device or service which created it. An example is specific to the device or service which created it. An example is
the VEDs structure for a vehicle telematics device. The structure the VEDs structure for a vehicle telematics device. The structure
skipping to change at page 15, line 4 skipping to change at page 15, line 44
* 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., Different data may be created by each classification; i.e.,
telematics creates VEDS data set - can be different types of data telematics creates VEDS data set - can be different types of data
depending on device. May want to describe type of data for each depending on device. May want to describe type of data for each
device. 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.14. Telephone Number Privacy Indicator 3.4. Regulatory Information
In some jurisdictions, handling of emergency calls involves
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
Data Element: Telephone Number Privacy Indicator Data Element: Telephone Number Privacy Indicator
Use: Required Use: Required
XML Element: <TNPrivacyIndicator> XML Element: <TNPrivacyIndicator>
Description: Some State regulations require that Non-Published Description: Some State regulations require that Non-Published
subscriber name remains private to all including 9-1-1. Where subscriber name remains private to all including 9-1-1. Where
this regulation is in place, the end user's name must be overlaid this regulation is in place, the end user's name must be overlaid
skipping to change at page 16, line 10 skipping to change at page 17, line 10
Reason for Need: Some State regulations require that Non-Published Reason for Need: Some State regulations require that Non-Published
subscriber name remains private to all including emergency calls. subscriber name remains private to all including emergency calls.
Where this regulation is in place, the end user's name must be Where this regulation is in place, the end user's name must be
overlaid with blanks or the verbiage, "Non-Published Number". overlaid with blanks or the verbiage, "Non-Published Number".
How Used by Call Taker: This is not beneficial to PSAPs; however, How Used by Call Taker: This is not beneficial to PSAPs; however,
they must follow state regulations. This indicator will allow for they must follow state regulations. This indicator will allow for
coding that overlays the non-published subscriber name with the coding that overlays the non-published subscriber name with the
verbiage "Non-Published Number." verbiage "Non-Published Number."
3.15. vCARD for Subscriber's Data 3.5. Owner/Subscriber Information
This block describes the owner of the device (if provided by the
device) or the subscriber information, if provided by a service
provider. The contact location is NOT necessarily the location of
the caller or incident, but is rather the nominal contact address.
The mime type is "addCallSub".
3.5.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 about the
subscriber; i.e., Name, Address, Calling Party Number, Main subscriber; i.e., Name, Address, Calling Party Number, Main
Telephone Number and any other data. If the subscriber is an Telephone Number and any other data. If the subscriber is an
skipping to change at page 17, line 7 skipping to change at page 18, line 7
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 4. XML Schema
NOTE: This section is not yet updated.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xsd:schema <xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="urn:nena:xml:ns:es:NG:Call" xmlns="urn:nena:xml:ns:es:NG:Call"
targetNamespace="urn:nena:xml:ns:es:NG:Call" targetNamespace="urn:nena:xml:ns:es:NG:Call"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified" version="1.0"> attributeFormDefault="unqualified" version="1.0">
<xsd:include schemaLocation="NGTypeLib.xsd"/> <xsd:include schemaLocation="NGTypeLib.xsd"/>
<xsd:element name="DataAssociatedWithCall"> <xsd:element name="DataAssociatedWithCall">
<xsd:complexType> <xsd:complexType>
skipping to change at page 20, line 5 skipping to change at page 20, line 25
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>
There is much private data in this information. Local regulations
may govern what data must be provided in emergency calls, but in
general, the emergency call system is often aided by the kinds of
information described in this document. There is a tradeoff between
the privacy considerations and the utility of the data. Certainly,
if the data cannot be protected, due to failure of the TLS mechanisms
described here, data not required by regulation SHOULD not be sent.
6. IANA Considerations 6. IANA Considerations
6.1. 'emergencyCallData' Purpose Parameter Value 6.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. A reference to this RFC (in
double brackets) has been added to the existing "purpose" Call-Info double brackets) has been added to the existing "purpose" Call-Info
parameter entry in the SIP Parameters registry, which currently looks parameter entry in the SIP Parameters registry, which currently looks
as follows: as follows:
Predefined Predefined
Header Field Parameter Name Values Reference Header Field Parameter Name Values Reference
------------- -------------- --------- --------- ------------- -------------- --------- ---------
Call-Info purpose Yes [RFC3261][RFC5367] Call-Info purpose Yes [RFC3261][RFC5367]
6.2. URN Sub-Namespace Registration for 6.2. provided-by registry entry
This section registers the namespace specified in ??? in the
provided-by registry established by RFC4119.
TBD
6.3. MIME registrations
TBD
6.4. URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:additional-data urn:ietf:params:xml:ns:additional-data
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]. [RFC3688].
URI: urn:ietf:params:xml:ns:additional-data URI: urn:ietf:params:xml:ns:additional-data
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 21, line 5 skipping to change at page 22, line 23
<title>Additional Data Namespace</title> <title>Additional Data Namespace</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data </h1> <h1>Namespace for Additional Data </h1>
<h2>urn:ietf:params:xml:ns:additional-data</h2> <h2>urn:ietf:params:xml:ns:additional-data</h2>
<p>See [TBD].</p> <p>See [TBD].</p>
</body> </body>
</html> </html>
END END
6.3. Additional Data Schema Registration 6.5. Additional Data Schema Registration
This specification registers a schema, as per the guidelines in This specification registers a schema, as per the guidelines in
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:additional-data URI: urn:ietf:params:xml:schema:additional-data
Registrant Contact: IETF, ECRIT Working Group (geopriv@ietf.org), Registrant Contact: IETF, ECRIT Working Group (geopriv@ietf.org),
as delegated by the IESG (iesg@ietf.org). as delegated by the IESG (iesg@ietf.org).
XML: The XML can be found as the sole content of Section 4. XML: The XML can be found as the sole content of Section 4.
skipping to change at page 23, line 10 skipping to change at page 24, line 10
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 8. 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
Locators", RFC 2392, August 1998.
[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
Format", RFC 4119, December 2005.
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. 52 change blocks. 
86 lines changed or deleted 180 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/