draft-ietf-ecrit-additional-data-06.txt   draft-ietf-ecrit-additional-data-07.txt 
ECRIT B.R. Rosen ECRIT B. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: August 20, 2013 Nokia Siemens Networks Expires: August 30, 2013 Nokia Siemens Networks
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
R. Gellens R. Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
February 18, 2013 February 26, 2013
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-06.txt draft-ietf-ecrit-additional-data-07.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 through which the call the path of the call, or access network through which the call
originated may have information about the call which the PSAP may be originated may have information about the call which the PSAP may be
able to use. This document describes an XML data structure to able to use. This document describes an XML data structure to
contains such data and a Uniform Resource Identifier (URI) for contains such data and a Uniform Resource Identifier (URI) for
conveying the data to the PSAP. The URI may point to either an conveying the data to the PSAP. The URI may point to either an
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 August 20, 2013. This Internet-Draft will expire on August 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 (http://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Simplified BSD License text to this document. Code Components extracted from this document must
as described in Section 4.e of the Trust Legal Provisions and are include Simplified BSD License text as described in Section 4.e of
provided without warranty as described in the Simplified BSD License. the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8
3. Block Overview . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Block Overview . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Transmitting Blocks of Additional Data . . . . . . . . . . . . 7 4. Transmitting Blocks of Additional Data . . . . . . . . . . . . 10
4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 7 4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 10
4.2. Transmitting blocks by reference using Provided-By . . . . 8 4.2. Transmitting blocks by reference using Provided-By . . . . 11
4.3. Transmitting blocks by value using Provided-By . . . . . . 9 4.3. Transmitting blocks by value using Provided-By . . . . . . 12
5. Data Provider Information . . . . . . . . . . . . . . . . . . 9 5. Data Provider Information . . . . . . . . . . . . . . . . . . 13
5.1. Data Provider String . . . . . . . . . . . . . . . . . . . 9 5.1. Data Provider String . . . . . . . . . . . . . . . . . . . 13
5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 10 5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 13
5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 10 5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 14
5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 11 5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 14
5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 12 5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 15
5.6. Data Provider Languages(s) Supported . . . . . . . . . . . 12 5.6. Data Provider Languages(s) Supported . . . . . . . . . . . 16
5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . . 13 5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . . 16
5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 13 5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 17
5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . . 14 5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . . 18
5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 14 5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 19
6. Service Information . . . . . . . . . . . . . . . . . . . . . 15 6. Service Information . . . . . . . . . . . . . . . . . . . . . 20
6.1. Service Environment . . . . . . . . . . . . . . . . . . . 15 6.1. Service Environment . . . . . . . . . . . . . . . . . . . 20
6.2. Service Delivered by Provider to End User . . . . . . . . 16 6.2. Service Delivered by Provider to End User . . . . . . . . 20
6.3. Service Mobility Environment . . . . . . . . . . . . . . . 17 6.3. Service Mobility Environment . . . . . . . . . . . . . . . 22
6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 18 6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 23
7. Device Information . . . . . . . . . . . . . . . . . . . . . . 18 7. Device Information . . . . . . . . . . . . . . . . . . . . . . 24
7.1. Device Classification . . . . . . . . . . . . . . . . . . 19 7.1. Device Classification . . . . . . . . . . . . . . . . . . 24
7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 20 7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 26
7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 21 7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 26
7.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 21 7.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 27
7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 22 7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 27
7.6. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . . 22 7.6. Device/Service Specific Additional Data Structure . . . . 28
8. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 23 7.7. Device/Service Specific Additional Data Structure Type . . 29
8.1. xCard for Subscriber\0x2019s Data . . . . . . . . . . . . 23 7.8. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . . 30
8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . . 24 8. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 31
9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.1. xCard for Subscriber\\0x2019s Data . . . . . . . . . . . . 31
9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 24 8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . . 32
9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . . 25 9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 33
11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 26 9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . . 34
12. Security Considerations . . . . . . . . . . . . . . . . . . . 26 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 27 11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 36
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 12. Security Considerations . . . . . . . . . . . . . . . . . . . 37
14.1. Registry creation . . . . . . . . . . . . . . . . . . . . 28 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 39
14.1.1. Additional Call Data Blocks Registry . . . . . . . . 28 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40
14.1.2. Additional Call Data Service Provider Type Registry . 28 14.1. Registry creation . . . . . . . . . . . . . . . . . . . . 40
14.1.3. Additional Call Data Service Delivered Registry . . . 29 14.1.1. Additional Call Data Blocks Registry . . . . . . . . 40
14.1.4. Additional Call Data Device Classification Registry . 30 14.1.2. Additional Call Data Service Provider Type
14.1.5. Additional Call Data Device ID Type Registry . . . . 31 Registry . . . . . . . . . . . . . . . . . . . . . . 40
14.1.6. Additional Call Data Blocks Registry . . . . . . . . 32 14.1.3. Additional Call Data Service Delivered Registry . . . 41
14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 32 14.1.4. Additional Call Data Device Classification
14.3. URN Sub-Namespace Registration for provided-by Registry Registry . . . . . . . . . . . . . . . . . . . . . . 42
Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 33 14.1.5. Additional Call Data Device ID Type Registry . . . . 43
14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 33 14.1.6. Additional Call Data Blocks Registry . . . . . . . . 44
14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 33 14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 44
14.3. URN Sub-Namespace Registration for provided-by
Registry Entry . . . . . . . . . . . . . . . . . . . . . . 45
14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 46
14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 46
14.4.1. MIME Content-type Registration for 14.4.1. MIME Content-type Registration for
'application/emergencyCall.ProviderInfo+xml' . . . . 34 'application/emergencyCall.ProviderInfo+xml' . . . . 46
14.4.2. MIME Content-type Registration for 14.4.2. MIME Content-type Registration for
'application/emergencyCall.SvcInfo+xml' . . . . . . . 35 'application/emergencyCall.SvcInfo+xml' . . . . . . . 48
14.4.3. MIME Content-type Registration for 14.4.3. MIME Content-type Registration for
'application/emergencyCall.DevInfo+xml' . . . . . . . 36 'application/emergencyCall.DevInfo+xml' . . . . . . . 49
14.4.4. MIME Content-type Registration for 14.4.4. MIME Content-type Registration for
'application/emergencyCall.SubInfo+xml' . . . . . . . 37 'application/emergencyCall.SubInfo+xml' . . . . . . . 50
14.4.5. MIME Content-type Registration for 14.4.5. MIME Content-type Registration for
'application/emergencyCall.Comment+xml' . . . . . . . 38 'application/emergencyCall.Comment+xml' . . . . . . . 51
14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 39 14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 53
14.5.1. Registration for 14.5.1. Registration for
urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 39 urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 53
14.5.2. Registration for 14.5.2. Registration for
urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 40 urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 53
14.5.3. Registration for 14.5.3. Registration for
urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 40 urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 54
14.5.4. Registration for 14.5.4. Registration for
urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 41 urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 55
14.5.5. Registration for 14.5.5. Registration for
urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 42 urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 56
14.5.6. Registration for 14.5.6. Registration for
urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 42 urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 57
14.6. Schema Registrations . . . . . . . . . . . . . . . . . . 43 14.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 58
14.7. VCard Parameter Value Registration . . . . . . . . . . . 44 14.7. VCard Parameter Value Registration . . . . . . . . . . . . 59
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 44 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 61
16.1. Normative References . . . . . . . . . . . . . . . . . . 44 16.1. Normative References . . . . . . . . . . . . . . . . . . . 61
16.2. Informational References . . . . . . . . . . . . . . . . 45 16.2. Informational References . . . . . . . . . . . . . . . . . 61
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 45 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 63
1. Introduction 1. Introduction
This document extends the basic signaling of an emergency call as This document extends the basic signaling of an emergency call as
described in [RFC6443] and [I-D.ietf-ecrit-phonebcp] in order to described in [RFC6443] and [I-D.ietf-ecrit-phonebcp] in order to
carry additional data which may be useful to an entity handling the carry additional data which may be useful to an entity handling the
call. This data is "additional" to the basic signaling used in call. This data is "additional" to the basic signaling used in
processing the call. processing the call.
Three general categories of such data are defined, for the caller, Three general categories of such data are defined, for the caller,
the location, the call, and the PSAP. An XML data structure is the location and the call. An XML data structure is defined for such
defined for such data, and a means of conveying the data by including data, and a means of conveying the data by including a Uniform
a Uniform Resource Identifier (URI) in the SIP signaling which Resource Identifier (URI) in the SIP signaling which resolves to the
resolves to the data. The data itself may reside on an external data. The data itself may reside on an external resource, or may be
resource, or may be contained within the BODY of the SIP message. contained within the BODY of the SIP message.
In general, there are three types of data exchanged: In general, there are three types of data exchanged:
Data Associated with a Call: While information is carried in the call Data Associated with a Call: While information is carried in the
setup procedure itself (as part of the SIP headers as well as in call setup procedure itself (as part of the SIP headers as well as
the body of the SIP message), there is additional data known by in the body of the SIP message), there is additional data known by
the device making the call, or a service provider in the path of the device making the call, or a service provider in the path of
the call. This information may include the identity and contact the call. This information may include the identity and contact
information of the service provider, subscriber identity and information of the service provider, subscriber identity and
contact information, the type of service the provider offers, what contact information, the type of service the provider offers, what
kind of device is being used, etc. Some data is device or service kind of device is being used, etc. Some data is device or service
dependent data. For example, a car telematics system or service dependent data. For example, a car telematics system or service
may have crash information. A medical monitoring device may have may have crash information. A medical monitoring device may have
sensor data. While the details of the information may vary by sensor data. While the details of the information may vary by
device or service, there needs to be a common way to send such device or service, there needs to be a common way to send such
data to a PSAP. data to a PSAP.
Data Associated with a Location: There may be data that is specific Data Associated with a Location: There may be data that is specific
to the location not available in the location data structure to the location not available in the location data structure
(PIDF-LO [RFC4119]) itself, such as floor plan, tenant and (PIDF-LO [RFC4119]) itself, such as floor plan, tenant and
building owner contact data, HVAC status, etc. 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,
such as medical information and emergency contact data. such as medical information and emergency contact data.
When an emergency call is sent to a PSAP, while there is a rich set When an emergency call is sent to a PSAP, while there is a rich set
of data in the SIP message used for the call setup, the device, as of data in the SIP message used for the call setup, the device, as
well as any service provider in the path may have even more well as any service provider in the path may have even more
information that may be useful for a PSAP. information that may be useful for a PSAP.
This document focuses on additional data associated with an emergent This document focuses on additional data associated with an emergency
call and a mechanism for transporting it in an existing SIP header call and a mechanism for transporting it in an existing SIP header
field, 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 resolves to a data structure with header contains a HTTPS URL that resolves to a data structure with
information about the call, or is a CID that allows the data information about the call, or is a CID that allows the data
structure itself to be placed in the body of the message. Section 10 structure itself to be placed in the body of the message. Section 10
shows a SIP INVITE example containing such a Call-Info header using shows a SIP INVITE example containing such a Call-Info header using
the purpose parameter. The "purpose" parameter also contains an the purpose parameter. The "purpose" parameter also contains an
indication of what kind of data is available at the URI. indication of what kind of data is available at the URI.
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
may be valuable to the PSAP. This information is not specific to the may be valuable to the PSAP. This information is not specific to the
location itsef, but rather provides descriptive information having to location itsef, but rather provides descriptive information having to
do with the immediate circumstances about the provision of the do with the immediate circumstances about the provision of the
location (who the access network is, how to contact that entity, what location (who the access network is, how to contact that entity, what
kind of service the access network provides, possibly subscriber kind of service the access network provides, possibly subscriber
skipping to change at page 6, line 10 skipping to change at page 8, line 14
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].
In the data block definitions, the "Use:" values are specified as one In the data block definitions, the "Use:" values are specified as one
of: of:
Mandatory which means they MUST be present in the data structure. Mandatory which means they MUST be present in the data structure.
Conditional which means they MUST be present unless the specified Conditional which means they MUST be present unless the specified
condition is met, in which case the they MAY be present. condition is met, in which case the they MAY be present.
Optional which means they MAY be present. Optional which means they MAY be present.
3. Block Overview 3. Block Overview
The following section defines an initial set of blocks which may be The following section defines an initial set of blocks which may be
sent by value or by reference in SIP signaling or within a PIDF-LO. sent by value or by reference in SIP signaling or within a PIDF-LO.
For each block, we define the MIME type, and the XML data structure For each block, we define the MIME type, and the XML data structure
for the block. Blocks are defined for: for the block. Blocks are defined for:
Data Provider which supplies name and contact information for the Data Provider which supplies name and contact information for the
entity that created the data. entity that created the data.
Service Information which supplies information about the service Service Information which supplies information about the service
provided by a service provider. provided by a service provider.
Device Information which supplies information about the device Device Information which supplies information about the device
placing the call. placing the call.
Owner/Subscriber which supplies information about the owner of the Owner/Subscriber which supplies information about the owner of the
device or the subscriber to the service provider. device or the subscriber to the service provider.
Comment which provides a way to supply free form human readable text Comment which provides a way to supply free form human readable text
to the PSAP or emergency responders. to the PSAP or emergency responders.
PSAPs and emergency responders can examine the type of data provided PSAPs and emergency responders can examine the type of data provided
and selectively retrieve the data each is interested in, while and selectively retrieve the data each is interested in, while
forwarding all of it (the values or references) to downstream forwarding all of it (the values or references) to downstream
entities. entities.
Blocks can be sent by value (the data in the SIP body or PIDF-LO) or Blocks can be sent by value (the data in the SIP body or PIDF-LO) or
by reference (the data is retrieved via HTTPS from an external by reference (the data is retrieved via HTTPS from an external
server). Data may be provided by the device and/or one or more server). Data may be provided by the device and/or one or more
skipping to change at page 8, line 4 skipping to change at page 10, line 41
inspect privacy flags within the SIP headers to determine what inspect privacy flags within the SIP headers to determine what
information may be passed, stored, or displayed to comply with local information may be passed, stored, or displayed to comply with local
policy or law. policy or law.
Each entity adding Additional Information MUST supply the "Data Each entity adding Additional Information MUST supply the "Data
Provider" block. All other blocks are optional, but each entity Provider" block. All other blocks are optional, but each entity
SHOULD supply any blocks where it has at least some of the SHOULD supply any blocks where it has at least some of the
information in the block. information in the block.
4.1. Transmitting blocks using Call-Info 4.1. Transmitting blocks using Call-Info
A URI to a block MAY be inserted in a SIP request or response method A URI to a block MAY be inserted in a SIP request or response method
(most often INVITE or MESSAGE) with a Call-Info header field (most often INVITE or MESSAGE) with a Call-Info header field
containing a purpose of "emergencyCallData" together with the type of containing a purpose of "emergencyCallData" together with the type of
data available at the URI. The type of data is denoted by including data available at the URI. The type of data is denoted by including
the root of the MIME type (not including the emergencyCall prefix and the root of the MIME type (not including the emergencyCall prefix and
the +xml suffix) with a "." separator. For example, when the +xml suffix) with a "." separator. For example, when referencing
referencing a block with MIME type 'application/ a block with MIME type 'application/emergencyCall.ProviderInfo+xml',
emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to the 'purpose' parameter is set to 'emergencyCallData.ProviderInfo'.
'emergencyCallData.ProviderInfo'. An example "Call-Info" header An example "Call-Info" header field for this would be:
field for this would be:
Call-Info: https:23sedde3@example.com; Call-Info: https:23sedde3@example.com;
purpose="emergencyCallData.ProviderInfo" purpose="emergencyCallData.ProviderInfo"
The Call-info header with purpose='emergencyCallData' MUST only be The Call-info header with purpose='emergencyCallData' MUST only be
sent on an emergency call, which can be ascertained by the presence sent on an emergency call, which can be ascertained by the presence
of an emergency service urn in a Route header of a SIP message. of an emergency service urn in a Route header of a SIP message.
If the data is provided by reference, it may be retrieved with an 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 HTTPS Get from the URI. The URI MUST specify an HTTPS scheme, and
TLS protection for the data MUST be negotiated. TLS protection for the data MUST be negotiated.
skipping to change at page 9, line 43 skipping to change at page 12, line 35
"emergencyCallData.ProviderInfo"> "emergencyCallData.ProviderInfo">
<ProviderID>HooThrooPoo</ProviderID> <ProviderID>HooThrooPoo</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProviderID>Access Infrastructure Provider <TypeOfProviderID>Access Infrastructure Provider
</TypeOfProviderID> </TypeOfProviderID>
<ContactURI>sip:15555550987@burf.example.com:user=phone <ContactURI>sip:15555550987@burf.example.com:user=phone
</ContactURI> </ContactURI>
</emergencyCallDataValue> </emergencyCallDataValue>
</provided-by> </provided-by>
Example Provided-By by value
5. Data Provider Information 5. Data Provider Information
This block is intended to be provided by any service provider in the This block is intended to be provided by any service provider in the
path of the call or the access network provider. It includes path of the call or the access network provider. It includes
identification and contact information. This block SHOULD be identification and contact information. This block SHOULD be
provided for every service provider in the path of the call, and the provided for every service provider in the path of the call, and the
access network provider. Devices MAY use this block to provide access network provider. Devices MAY use this block to provide
identifying information. The MIME subtype is "application/ identifying information. The MIME subtype is "application/
emergencyCall.ProviderInfo+xml". emergencyCall.ProviderInfo+xml".
5.1. Data Provider String 5.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Required
XML Element: <DataProviderString> Use: Required
Description: This is a plain language string suitable for displaying XML Element: <DataProviderString>
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. identical to the contact header in the SIP INVITE.
Reason for Need: Inform the call taker of the identity of the entity Reason for Need: Inform the call taker of the identity of the entity
providing the additional call data structure. 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.
5.2. Data Provider ID 5.2. Data Provider ID
Data Element: Data Provider ID Data Element: Data Provider ID
Use: Conditional. Must be provided if the service provider is Use: Conditional. Must be provided if the service provider is
located in a jurisdiction that maintains such ids. Devices are located in a jurisdiction that maintains such ids. Devices are
not required to provide it. 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 SHOULD NOT use this would be a "NENA Company ID". Devices SHOULD NOT use this
element. element.
Reason for Need: Inform the call taker of the identity of the entity Reason for Need: Inform the call taker of the identity of the entity
providing the additional call data structure. 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 be useful. the Data Provider ID can be useful.
5.3. Data Provider ID Series 5.3. Data Provider ID Series
Data Element: Data Provider ID Series Data Element: Data Provider ID Series
Use: Conditional. If Data Provider ID is provided, Data Provider ID Use: Conditional. If Data Provider ID is provided, Data Provider ID
Series is required. Series is required.
XML Element: <ProviderIDSeries> XML Element: <ProviderIDSeries>
Description: Identifies the issuer of the the ProviderId. A registry Description: Identifies the issuer of the the ProviderId. A
will reflect the following valid entries: registry will reflect the following valid entries:
* NENA * NENA
* EENA * EENA
Reason for Need: Identifies how to interpret the Data Provider ID. Reason for Need: Identifies how to interpret the Data Provider ID.
How Used by Call Taker: Determines which provider ID registry to How Used by Call Taker: Determines which provider ID registry to
consult for more information consult for more information
5.4. Type of Data Provider 5.4. Type of Data Provider
Data Element: Type of Data Provider ID Data Element: Type of Data Provider ID
Use: Conditional. If Data Provider ID is provided, Type of Data
Use: Conditional. If Data Provider ID is provided, Type of Data
Provider ID is required. Provider ID is required.
XML Element: <TypeOfProviderID> XML Element: <TypeOfProviderID>
Description: Identifies the type of data provider id being supplied Description: Identifies the type of data provider id being supplied
in the ProviderId data element. A registry will reflect the in the ProviderId data element. A registry will reflect the
following valid entries: following valid entries:
* Access Infrastructure Provider * Access Infrastructure Provider
* Service Provider * Service Provider
* Service Provider Subcontractor * Service Provider Subcontractor
* Telematics Provider * Telematics Provider
* Relay Provider * Relay Provider
* Other * Other
Reason for Need: Identifies what kind of data provider this is. Reason for Need: Identifies what kind of data provider this is.
How Used by Call Taker: To decide who to contact when further How Used by Call Taker: To decide who to contact when further
information is needed information is needed
5.5. Data Provider Contact URI 5.5. Data Provider Contact URI
Data Element: Data Provider Contact URI Data Element: Data Provider Contact URI
Use: Required Use: Required
XML Element: <ContactURI> XML Element: <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 contact URI. This MUST be a SIP URI. If a telephone number is the
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 would reflect the contact information of the from a device, this would reflect the contact information of the
owner of the device. When provided by a service provider, this owner of the device. When provided by a service provider, this
would be a URI to a 24/7 support organization tasked to provide would be a URI to a 24/7 support organization tasked to provide
PSAP support 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 for assistance in handling the call. data for assistance in handling the call.
5.6. Data Provider Languages(s) Supported 5.6. 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: The language used by the entity at the Data Provider
Contact URI as an alpha 2-character code as defined in ISO
639-1:2002 (http://www.iso.org/iso/
catalogue_detail?csnumber=22109) Codes for the representation of
names of languages -- Part 1: Alpha-2 code Multiple instances of
this element may occur. Order is significant; preferred language
should appear first. This data is required if a Data Provider
Contact URI is provided. The content must reflect the languages
supported at the contact URI.
Reason for Need: Information needed to determine if emergency service Description: The language used by the entity at the Data Provider
authority can communicate with the service provider or if an Contact URI as an alpha 2-character code as defined in ISO 639-
interpreter will be needed. 1:2002 (http://www.iso.org/iso/catalogue_detail?csnumber=22109)
Codes for the representation of names of languages -- Part 1:
Alpha-2 code Multiple instances of this element may occur. Order
is significant; preferred language should appear first. This data
is required if a Data Provider Contact URI is provided. The
content must reflect the languages supported at the contact URI.
How Used by Call Taker: If call taker cannot speak language(s) Reason for Need: Information needed to determine if emergency
service authority can communicate with the service provider or if
an interpreter will be needed.
How Used by Call Taker: If call taker cannot speak language(s)
supported by the service provider, a translation service will need supported by the service provider, a translation service will need
to be added to the conversation. to be added to the conversation.
5.7. xCard of Data Provider 5.7. xCard of Data Provider
Data Element: xCard of Data Provider Data Element: xCard of Data Provider
Use: Optional
Use: Optional
XML Element: <DataProviderContact> XML Element: <DataProviderContact>
Description: There are many fields in the xCARD 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. N, ORG, ADR, TEL, EMAIL are suggested at a they have available. N, ORG, ADR, TEL, EMAIL are suggested at a
minimum. N should contain name of support group or device owner minimum. N should contain name of support group or device owner
as appropriate. If more than one TEL property is provided, a as appropriate. If more than one TEL property is provided, a
parameter from the vCard Property Value registry MUST be specified parameter from the vCard Property Value registry MUST be specified
on each TEL. For encoding of the xCard this specification uses on each TEL. For encoding of the xCard this specification uses
the XML-based encoding specified in [RFC6351]. the XML-based encoding specified in [RFC6351].
and is hereinafter referred to as "xCard" 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.
5.8. Subcontractor Principal 5.8. Subcontractor Principal
Data Element: Subcontractor Principal Data Element: Subcontractor Principal
XML Element: <SubcontratorPrincipal>
Description: If the data provider is a subcontractor to another XML Element: <SubcontratorPrincipal>
Description: If the data provider is a subcontractor to another
provider such as an access infrastructure provider or telematics provider such as an access infrastructure provider or telematics
provider, this element contains the DataProviderString of the provider, this element contains the DataProviderString of the
service provider to indicate which provider the subcontractor is service provider to indicate which provider the subcontractor is
working for. This data is required if the Data Provider type is working for. This data is required if the Data Provider type is
subcontractor. subcontractor.
Reason for Need: Identify the entity the subcontractor works for. Reason for Need: Identify the entity the subcontractor works for.
How Used by Call Taker: Allows the call taker to understand what the How Used by Call Taker: Allows the call taker to understand what the
relationship between data providers and the service providers in relationship between data providers and the service providers in
the path of the call are. the path of the call are.
5.9. Subcontractor Priority 5.9. Subcontractor Priority
Data Element: Subcontractor Priority Data Element: Subcontractor Priority
Use: Required Use: Required
XML Element: <SubcontractorPriority> XML Element: <SubcontractorPriority>
Description: If the subcontractor should be contacted first, this Description: If the subcontractor should be contacted first, this
element should have a "sub" value. If the access or origination element should have a "sub" value. If the access or origination
service provider should be contacted first, this element should service provider should be contacted first, this element should
have a "main" value. This data is required if the Data Provider have a "main" value. This data is required if the Data Provider
type is "subcontractor". type is "subcontractor".
Reason for Need: Inform the call taker whether the network operator Reason for Need: Inform the call taker whether the network operator
or the subcontractor should be contacted first if support is or the subcontractor should be contacted first if support is
needed. needed.
How Used by Call Taker: To decide which entity to contact first if How Used by Call Taker: To decide which entity to contact first if
assistance is needed. assistance is needed.
5.10. emergencyCall.ProviderInfo XML Schema 5.10. emergencyCall.ProviderInfo XML Schema
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <?xml version="1.0"?>
schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:simpleType name="iso3166a2"> <xs:import namespace="http://www.w3.org/XML/1998/namespace"
<xs:restriction base="xs:token"> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:pattern value="[A-Z]{2}"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="emergencyCall.ProviderInfo"> <xs:simpleType name="iso3166a2">
<xs:complexType> <xs:restriction base="xs:token">
<xs:sequence> <xs:pattern value="[A-Z]{2}"/>
<xs:element name="DataProviderString" </xs:restriction>
type="xs:string" minOccurs="1" maxOccurs="1"/> </xs:simpleType>
<xs:element name="ProviderID"
type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:element name="emergencyCall.ProviderInfo">
<xs:element name="ProviderIdSeries" <xs:complexType>
type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:sequence>
<xs:element name="TypeOfProvider" <xs:element name="DataProviderString"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI" <xs:element name="ProviderID"
minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="Language" type="ad:iso3166a2" <xs:element name="ProviderIdSeries"
minOccurs="0" maxOccurs="unbounded" /> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DataProviderContact" <xs:element name="TypeOfProvider"
type="xc:vcard" minOccurs="0" maxOccurs="1"> type="xs:string" minOccurs="0" maxOccurs="1"/>
</xs:sequence> <xs:element name="ContactURI" type="xs:anyURI"
</xs:complexType> minOccurs="1" maxOccurs="1"/>
</xs:element> <xs:element name="Language" type="ad:iso3166a2"
</xs:schema> minOccurs="0" maxOccurs="unbounded" />
<xs:element name="DataProviderContact"
type="xc:vcard" minOccurs="0" maxOccurs="1">
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 1: emergencyCall.ProviderInfo XML Schema
6. Service Information 6. Service Information
This block describes the service that the service provider provides This block describes the service that the service provider provides
to the caller. It SHOULD be included by all SPs in the path of the to the caller. It SHOULD be included by all SPs in the path of the
call. The mime subtype is "application/emergencyCall.SvcInfo+xml". call. The mime subtype is "application/emergencyCall.SvcInfo+xml".
6.1. Service Environment 6.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
Use: Required Use: Required
XML Element: <SvcEnvironment>
Description: This element defines whether a call is from a business XML Element: <SvcEnvironment>
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 assist in How Used by Call Taker: Information may be used to assist in
determining equipment and manpower requirements for emergency determining equipment and manpower requirements for emergency
responders. As the information is not always available, and the responders. As the information is not always available, and the
registry is not all encompassing, this is at best advisory registry is not all encompassing, this is at best advisory
information, but since it mimics a similar capability in some information, but since it mimics a similar capability in some
current emergency calling systems, it is known to be valuable. current emergency calling systems, it is known to be valuable.
The service provider uses its best information (such as a rate The service provider uses its best information (such as a rate
plan, facilities used to deliver service or service description) plan, facilities used to deliver service or service description)
to determine the information and is not responsible for to determine the information and is not responsible for
determining the actual characteristics of the location where the determining the actual characteristics of the location where the
call originates from. call originates from.
6.2. Service Delivered by Provider to End User 6.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
XML Element: <SvcDelByProvider> Use: Required
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 defined in this document will reflect the relied upon. A registry defined in this document will reflect the
following initial valid entries: following initial valid entries:
* Wireless Telephone Service: Includes Satellite, CDMA, GSM, Wi- * Wireless Telephone Service: Includes Satellite, CDMA, GSM,
Fi, WiMAX, UTMS/WCDMA, LTE (Long Term Evolution) Wi-Fi, WiMAX, UTMS/WCDMA, 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
* Multi-line telephone system (MLTS): Includes all PBX, Centrex, * Multi-line telephone system (MLTS): Includes all PBX, Centrex,
key systems, Shared Tenant Service. key systems, Shared Tenant Service.
* Sensor, unattended: Includes devices that generate DATA ONLY. * Sensor, unattended: Includes devices that generate DATA ONLY.
This is one-way information exchange and there will be no other This is one-way information exchange and there will be no other
form of communication. form of communication.
skipping to change at page 17, line 35 skipping to change at page 22, line 5
* Relay Service: a type of service where there is a human 3rd * Relay Service: a type of service where there is a human 3rd
party agent who provides some kind of additional assistance to party agent who provides some kind of additional assistance to
the caller. Includes sign language relay and telematics the caller. Includes sign language relay and telematics
services which provide a service assistant on the call. services which provide a service assistant on the call.
* Remote (off premise extension) * 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
inmate telephone service is a reasonable combination. inmate telephone service is a reasonable combination.
Reason for Need: Knowing the type of service may assist the PSAP with Reason for Need: Knowing the type of service may assist the PSAP
the handling of the call. with the handling of the call.
How Used by Call Taker: Call takers 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. As the is treated differently that a call from a sensor device. As the
information is not always available, and the registry is not all information is not always available, and the registry is not all
encompassing, this is at best advisory information, but since it encompassing, this is at best advisory information, but since it
mimics a similar capability in some current emergency calling mimics a similar capability in some current emergency calling
systems, it is known to be valuable. systems, it is known to be valuable.
6.3. Service Mobility Environment 6.3. Service Mobility Environment
Data Element: Service Mobility Environment Data Element: Service Mobility Environment
Use: Required Use: Required
XML Element: <SvcMobility> XML Element: <SvcMobility>
Description: This provides the service providers view of the mobility
of the caller. As the service provider may not know the Description: This provides the service providers view of the
mobility of the caller. As the service provider may not know the
characteristics of the actual access network used, the value not characteristics of the actual access network used, the value not
be relied upon. A registry will reflect the following initial be relied upon. A registry will reflect the following initial
valid entries: valid entries:
* Mobile: the device should be able to move at any time * Mobile: the device should be able to move at any time
* Fixed: the device is not expected to move unless the service is * Fixed: the device is not expected to move unless the service is
relocated relocated
* Nomadic: the device is not expected to move while on a call, * Nomadic: the device is not expected to move while on a call,
but may move between calls but may move between calls
Reason for Need: Knowing the service provider's belief of mobility Reason for Need: Knowing the service provider's belief of mobility
may assist the PSAP with the handling of the call. may assist the PSAP with the handling of the call.
How Used by Call Taker: To determine whether to assume the location How Used by Call Taker: To determine whether to assume the location
of the caller might change. of the caller might change.
6.4. emergencyCall.SvcInfo XML Schema 6.4. emergencyCall.SvcInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo" xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
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"/>
<xs:element name="emergencyCall.SvcInfo"> <xs:element name="emergencyCall.SvcInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="SvcEnvironment" <xs:element name="SvcEnvironment"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcDelByProvider" <xs:element name="SvcDelByProvider"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcMobility" <xs:element name="SvcMobility"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Link" <xs:element name="Link"
type="xs:string" minOccurs="0" maxOccurs="1"> type="xs:string" minOccurs="0" maxOccurs="1">
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Figure 2: emergencyCall.SvcInfo XML Schema
7. Device Information 7. 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 subtype is device is being used, and by the device itself. The mime subtype is
"application/emergencyCall.DevInfo+xml". "application/emergencyCall.DevInfo+xml".
7.1. Device Classification 7.1. Device Classification
Data Element: Device Classification Data Element: Device Classification
Use: Optional Use: Optional
XML Element: <DeviceClassification> XML Element: <DeviceClassification>
Description: This data element defines the kind of device making the Description: This data element defines the kind of device making the
emergency call. If the device provides the data structure, the emergency call. If the device provides the data structure, the
device information SHOULD be provided. If the service provider device information SHOULD be provided. If the service provider
provides the structure and it knows what the device is, the provides the structure and it knows what the device is, the
service provider SHOULD provide the device information. Often the service provider SHOULD provide the device information. Often the
carrier does not know what the device is. It is possible to carrier does not know what the device is. It is possible to
receive two Additional Data Associated with a Call data receive two Additional Data Associated with a Call data
structures, one created by the device and one created by the structures, one created by the device and one created by the
service provider. This information describes the the device, not service provider. This information describes the device, not how
how it is being used. This data element defines the kind of it is being used. This data element defines the kind of device
device making the emergency call. A registry will reflect the making the emergency call. A registry will reflect the following
following valid entries: 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 20, line 30 skipping to change at page 25, line 38
* Internet tablet * Internet tablet
* Gaming console * Gaming console
* Video phone * Video phone
* Other text device * Other text device
* Not Available * Not Available
Reason for Need: The device classification implies the capability of Reason for Need: The device classification implies the capability of
the calling device and assists in identifying the meaning of the the calling device and assists in identifying the meaning of the
emergency call location information that is being presented. For emergency call location information that is being presented. For
example, does the device require human intervention to initiate a example, does the device require human intervention to initiate a
call or is this call the result of programmed instructions? Does call or is this call the result of programmed instructions? Does
the calling device have the ability to update location or the calling device have the ability to update location or
condition changes? Is this device interactive or a one-way condition changes? Is this device interactive or a one-way
reporting device? 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, the capabilities provide calltaker some context about the caller, the capabilities
of the device used for the call or the environment the device is of the device used for the call or the environment the device is
being used in. being used in.
7.2. Device Manufacturer 7.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
device. device.
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.
7.3. Device Model Number 7.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 of the device. Description: Model number of the device.
Reason for Need: Used by PSAP management for after action Reason for Need: Used by PSAP management for after action
investigation/resolution. investigation/resolution.
How Used by Call Taker: Probably not used by calltaker, but by PSAP How Used by Call Taker: Probably not used by calltaker, but by PSAP
management. management.
7.4. Unique Device Identifier 7.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: String that identifies the specific device making the Description: String that identifies the specific device making the
call or creating an event. call or creating an event.
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.
7.5. Type of Device Identifier 7.5. Type of Device Identifier
Data Element: Type of Device Identifier Data Element: Type of Device Identifier
Use: Conditional: must be provided if DeviceID is provided Use: Conditional: must be provided if DeviceID is provided
XML Element: <TypeOfDeviceID> XML Element: <TypeOfDeviceID>
Description: Identifies the type of device identifier being generated Description: Identifies the type of device identifier being
in the unique device identifier data element. A registry will generated in the unique device identifier data element. A
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)
* MAC (Media Access Control) Address -- IEEE-delegated address * MAC (Media Access Control) Address -- IEEE-delegated address of
of any of the interfaces of the device with a MAC address any of the interfaces of the device with a MAC address (e.g.,
(e.g., Ethernet, WiFi) Ethernet, WiFi)
* WiMAX device certificate subject unique identifier * WiMAX device certificate subject unique identifier
* IMEI (International Mobile Equipment Identifier - GSM) * IMEI (International Mobile Equipment Identifier - GSM)
* Unique Device Identifier (UDI) assigned by US FDA for medical * Unique Device Identifier (UDI) assigned by US FDA 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
* 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.
7.6. emergencyCall.DevInfo XML Schema 7.6. Device/Service Specific Additional Data Structure
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
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: Device/service specific additional data structure
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCall.DevInfo"> Use: Optional
<xs:complexType>
<xs:sequence> XML Element: <DeviceSpecificData>
<xs:element name="DeviceClassification"
type="xs:string" minOccurs="0" maxOccurs="1"/> Description: A URI representing additional data whose schema is
<xs:element name="DeviceMfgr" specific to the device or service which created it. An example is
type="xs:string" minOccurs="0" maxOccurs="1"/> the VEDs structure for a vehicle telematics device. The URI, when
<xs:element name="DeviceModelNr" dereferenced, MUST yield a data structure defined by the Device/
type="xs:string" minOccurs="0" maxOccurs="1"/> service specific additional data type value. Different data may
<xs:element name="UniqueDeviceID" be created by each classification; e.g., telematics creates VEDS
type="xs:string" minOccurs="0" maxOccurs="1"/> data set.
<xs:element name="TypeOfDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/> Reason for Need: Provides device/service specific data that may be
</xs:sequence> used by the call taker and/or responders.
</xs:complexType>
</xs:element> How Used by Call Taker: Provide information to guide call takers to
</xs:schema> 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.
7.7. Device/Service Specific Additional Data Structure Type
Data Element: Type of Device/service specific additional data
structure
Use: Conditional. MUST be provided when Device/service specific
additional URI is provided
XML Element: <DeviceSpecificType>
Description: Value from a registry defined by this document to
describe the type of data that can be retrieved from the Device/
service specific additional data structure. Initial values are:
* IEEE 1512 - USDOT Model for traffic incidents
* VEDS
Reason for Need: This data element allows identification of
externally defined schemas, which may have additional data that
may assist in emergency response.
How Used by Call Taker: This data element allows the end user
(calltaker or first responder) to know what type of additional
data may be available to aid in providing the needed emergency
services.
Note: Information which is specific to a location or a caller
(person) should not be placed in this section.
7.8. emergencyCall.DevInfo XML Schema
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
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="emergencyCall.DevInfo">
<xs:complexType>
<xs:sequence>
<xs:element name="DeviceClassification"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceMfgr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceModelNr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="UniqueDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="TypeOfDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xsd:element name="DeviceSpecificData"
type="xsd:anyURI" minOccurs="0" maxOccurs="1"/>
<xsd:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 3: emergencyCallDevInfo XML Schema
8. Owner/Subscriber Information 8. 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 subtype is "application/emergencyCall.Subscriber+xml". The mime subtype is "application/emergencyCall.Subscriber+xml".
8.1. xCard for Subscriber\0x2019s Data 8.1. xCard for Subscriber\\0x2019s Data
Data Element: xCARD for Subscriber\0x2019s Data Data Element: xCARD for Subscriber\0x2019s Data
Use: Conditional: Some services (e.g. prepaid phones, initialized Use: Conditional: Some services (e.g. prepaid phones, initialized
phones, etc.) may not have this information. 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; e.g., Name, Address, Individual Telephone about the subscriber; e.g., Name, Address, Individual Telephone
Number, Main Telephone Number and any other data. N, ORG (if Number, Main Telephone Number and any other data. N, ORG (if
appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more
than one TEL property is provided, a parameter from the vCard than one TEL property is provided, a parameter from the vCard
Property Value registry MUST be specified on each TEL. Property Value registry MUST be specified on each TEL.
Reason for Need: When the caller is unable to provide information, Reason for Need: When the caller is unable to provide information,
this data may be used to obtain it this data may be used to obtain it
How Used by Call Taker: Obtaining critical information about the How Used by Call Taker: Obtaining critical information about the
caller and possibly the location when it is not able to be caller and possibly the location when it is not able to be
obtained otherwise. obtained otherwise.
8.2. emergencyCall.SubInfo XML Schema 8.2. emergencyCall.SubInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo" xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="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:element name="emergencyCall.SubInfo"> <xs:element name="emergencyCall.SubInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="SubscriberData" <xs:element name="SubscriberData"
type="xc:vcard" minOccurs="0" maxOccurs="1"> type="xc:vcard" minOccurs="0" maxOccurs="1">
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Figure 4: emergencyCall.SubInfo XML Schema
9. Comment 9. Comment
This block Provides a mechanism for the data provider to supply This block Provides a mechanism for the data provider to supply
extra, human readable information to the PSAP. It is not intended extra, human readable information to the PSAP. It is not intended
for a general purpose extension mechanism. The mime subtype is for a general purpose extension mechanism. The mime subtype is
"application/emergencyCall.Comment+xml" "application/emergencyCall.Comment+xml"
9.1. Comment 9.1. Comment
Data Element: EmergencyCall.Comment Data Element: EmergencyCall.Comment
Use: Optional Use: Optional
XML Element: <Comment>
Description: Human readable text providing additional information to XML Element: <Comment>
Description: Human readable text providing additional information to
the PSAP. the PSAP.
Reason for Need: Explanatory information for values in the data Reason for Need: Explanatory information for values in the data
structure structure
How Used by Call Taker: To interpret the data provided How Used by Call Taker: To interpret the data provided
9.2. emergencyCall.Comment XML Schema 9.2. emergencyCall.Comment XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment" xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
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"/>
<xs:element name="emergencyCall.Comment"> <xs:element name="emergencyCall.Comment">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="Comment" <xs:element name="Comment"
type="xs:string" minOccurs="0" maxOccurs="1"> type="xs:string" minOccurs="0" maxOccurs="1">
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Figure 5: EmergencyCall.Comment XML Schema
10. Example 10. Example
INVITE sips:bob@biloxi.example.com SIP/2.0
Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70
To: Bob <sips:bob@biloxi.example.com>
From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
<http://www.example.com/alice/> ;purpose=info,
<cid:1234567890@atlanta.example.com>
;purpose=emergencyCallData.ProviderInfo
Geolocation: <cid:target123@atlanta.example.com>
Geolocation-Routing: no
Accept: application/sdp, application/pidf+xml,
application/emergencyCallProviderinfo+xml
CSeq: 31862 INVITE
Contact: <sips:alice@atlanta.example.com>
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... INVITE sips:bob@biloxi.example.com SIP/2.0
Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70
To: Bob <sips:bob@biloxi.example.com>
From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
<http://www.example.com/alice/> ;purpose=info,
<cid:1234567890@atlanta.example.com>
;purpose=emergencyCallData.ProviderInfo
Geolocation: <cid:target123@atlanta.example.com>
Geolocation-Routing: no
Accept: application/sdp, application/pidf+xml,
application/emergencyCallProviderinfo+xml
CSeq: 31862 INVITE
Contact: <sips:alice@atlanta.example.com>
Content-Type: multipart/mixed; boundary=boundary1
--boundary1 Content-Length: ...
Content-Type: application/sdp --boundary1
...SDP goes here Content-Type: application/sdp
--boundary1 ...SDP goes here
Content-Type: application/pidf+xml --boundary1
Content-ID: <target123@atlanta.example.com>
\0x2026PIDF-LO goes here Content-Type: application/pidf+xml
Content-ID: <target123@atlanta.example.com>
--boundary1-- \0x2026PIDF-LO goes here
Content-Type: application/emergencyCall.ProviderInfo+xml --boundary1--
Content-ID: <1234567890@atlanta.example.com>
\0x2026Additional Data goes here Content-Type: application/emergencyCall.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com>
--boundary1-- \0x2026Additional Data goes here
--boundary1--
Example: Attaching Additional Data via CID to a SIP INVITE
11. Main Telephone Number 11. Main Telephone Number
In a xCard, used extensively in this document, there is no way to In a xCard, used extensively in this document, there is no way to
specify a "Main" telephone number. These numbers are useful to specify a "Main" telephone number. These numbers are useful to
emergency responders who are called to a large enterprise. This emergency responders who are called to a large enterprise. This
document adds a new Property Value to the "tel" property of the TYPE document adds a new Property Value to the "tel" property of the TYPE
parameter called "main". It can be used in any xCard in additional parameter called "main". It can be used in any xCard in additional
data. data.
skipping to change at page 29, line 18 skipping to change at page 41, line 11
for use in the TypeOfServicerProvider element for use in the TypeOfServicerProvider element
The content of this registry includes: The content of this registry includes:
Name: Value to be used in TypeOfServiceProvider. Name: Value to be used in TypeOfServiceProvider.
Description: A short description of the type of service provider Description: A short description of the type of service provider
The values defined are: The values defined are:
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Name | Description | | Name | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Access Infrastructure Provider| Access network service provider | |Access Infrastructure Provider| Access network service provider |
|Service Provider | Calling or Origination telecom SP | |Service Provider | Calling or Origination telecom SP |
|Service Provider Subcontractor| A contractor to another kind of SP | |Service Provider Subcontractor| A contractor to another kind of SP |
|Telematics Provider | A sensor based SP, especially | |Telematics Provider | A sensor based SP, especially |
| | vehicle based | | | vehicle based |
|Relay Provider | A interpretation SP, for example, | |Relay Provider | A interpretation SP, for example, |
| | video relay for sign language | | | video relay for sign language |
| | interpretors | | | interpretors |
|Other | Any other type of service provider | |Other | Any other type of service provider |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
RFC Editor Note: RFC Editor Note:
replace XXXX in the table above with this documents RFC number replace XXXX in the table above with this documents RFC number
14.1.3. Additional Call Data Service Delivered Registry 14.1.3. Additional Call Data Service Delivered Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called \0x2019Additional Call
Data Service Delivered\0x2019. As defined in [RFC5226], this Data Service Delivered\0x2019. As defined in [RFC5226], this
registry operates under "Expert Review" rules. The expert should registry operates under "Expert Review" rules. The expert should
consider whether the proposed service is unique from existing consider whether the proposed service is unique from existing
services and the definition of the service will be clear to services and the definition of the service will be clear to
implementors and PSAPS/responders. implementors and PSAPS/responders.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the service. Name: enumeration token of the service.
Description: Short description identifying the service. Description: Short description identifying the service.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | description |
+--------+-------+--------------------------------+ +--------+-------+--------------------------------+
| Wrless | Wireless Telephone Service: Includes | | Wrless | Wireless Telephone Service: Includes |
| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
| | LTE (Long Term Evolution) | | | LTE (Long Term Evolution) |
| Coin | Fixed Public Pay/Coin telephones: Any | | Coin | Fixed Public Pay/Coin telephones: Any |
| | coin or credit card operated device | | | coin or credit card operated device |
| 1way | One way outbound service | | 1way | One way outbound service |
| Prison | Inmate call/service | | Prison | Inmate call/service |
| Temp | Soft dialtone/quick service/warm | | Temp | Soft dialtone/quick service/warm |
| | disconnect/suspended | | | disconnect/suspended |
| MLTS | Multi-line telephone system: Includes | | MLTS | Multi-line telephone system: Includes |
| | all PBX, Centrex, key systems, | | | all PBX, Centrex, key systems, |
| | Shared Tenant Service | | | Shared Tenant Service |
| SenseU | Sensor, unattended: Includes devices | | SenseU | Sensor, unattended: Includes devices |
| | that generate DATA ONLY. This is | | | that generate DATA ONLY. This is |
| | one-way information exchange and | | | one-way information exchange and |
| | there will be no other form of | | | there will be no other form of |
| | communication | | | communication |
| SenseA | Sensor, attended: Includes devices | | SenseA | Sensor, attended: Includes devices |
| | that are supported by a monitoring | | | that are supported by a monitoring |
| | service provider or automatically | | | service provider or automatically |
| | open a two-way communication path | | | open a two-way communication path |
| POTS | Wireline: Plain Old Telephone Service | | POTS | Wireline: Plain Old Telephone Service |
| VOIP | VoIP Telephone Service: A type of | | VOIP | VoIP Telephone Service: A type of |
| | service that offers communication | | | service that offers communication |
| | over internet protocol, such as Fixed| | | over internet protocol, such as Fixed|
| | Nomadic, Mobile, ... | | | Nomadic, Mobile, ... |
+--------+-------+--------------------------------+ +--------+-------+--------------------------------+
14.1.4. Additional Call Data Device Classification Registry 14.1.4. Additional Call Data Device Classification Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called \0x2019Additional Call
Data Device Classification\0x2019. As defined in [RFC5226], this Data Device Classification\0x2019. As defined in [RFC5226], this
registry operates under "Expert Review" rules. The expert should registry operates under "Expert Review" rules. The expert should
consider whether the proposed class is unique from existing classes consider whether the proposed class is unique from existing classes
and the definition of the class will be clear to implementors and and the definition of the class will be clear to implementors and
PSAPS/responders. PSAPS/responders.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the device classification. Name: enumeration token of the device classification.
Description: Short description identifying the device type. Description: Short description identifying the device type.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | description |
+--------+-------+--------------------------------+ +--------+-------+--------------------------------+
|Cordless| Cordless handset | |Cordless| Cordless handset |
| Fixed | Fixed phone | | Fixed | Fixed phone |
| Mobile | Mobile handset | | Mobile | Mobile handset |
| ATA | analog terminal adapter | | ATA | analog terminal adapter |
|Satphone| Satellite phone | |Satphone| Satellite phone |
| FSense | Stationary computing device (alarm | | FSense | Stationary computing device (alarm |
| | system, data sensor) | | | system, data sensor) |
| Guard | Guardian devices | | Guard | Guardian devices |
| Desktop| Desktop PC | | Desktop| Desktop PC |
| Laptop | Laptop computing device | | Laptop | Laptop computing device |
| Tablet | Tablet computing device | | Tablet | Tablet computing device |
| Alarm | Alarm system | | Alarm | Alarm system |
| MSense | Mobile Data sensor | | MSense | Mobile Data sensor |
| Beacon | Personal beacons (spot) | | Beacon | Personal beacons (spot) |
| Auto | Auto telematics | | Auto | Auto telematics |
| Truck | Truck telematics | | Truck | Truck telematics |
| Farm | Farm equipment telematics | | Farm | Farm equipment telematics |
| Marine | Marine telematics | | Marine | Marine telematics |
| PDA | Personal digital assistant | | PDA | Personal digital assistant |
| PND | Personal navigation device) | | PND | Personal navigation device) |
| SmrtPhn| Smart phone | | SmrtPhn| Smart phone |
| Itab | Internet tablet | | Itab | Internet tablet |
| Game | Gaming console | | Game | Gaming console |
| Video | Video phone | | Video | Video phone |
| Text | Other text device | | Text | Other text device |
| NA | Not Available | | NA | Not Available |
+--------+----------------------------------------+ +--------+----------------------------------------+
14.1.5. Additional Call Data Device ID Type Registry 14.1.5. Additional Call Data Device ID Type Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called \0x2019Additional Call
Data Device ID Type\0x2019. As defined in [RFC5226], this registry Data Device ID Type\0x2019. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should ascertain operates under "Expert Review" rules. The expert should ascertain
that the proposed type is well understood, and provides the that the proposed type is well understood, and provides the
information useful to PSAPs and responders to uniquely identify a information useful to PSAPs and responders to uniquely identify a
device. device.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the device id type. Name: enumeration token of the device id type.
Description: Short description identifying the type of device id. Description: Short description identifying the type of device id.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | description |
+--------+-------+--------------------------------+ +--------+-------+--------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) | | MEID | Mobile Equipment Identifier (CDMA) |
| ESN | Electronic Serial Number(GSM) | | ESN | Electronic Serial Number(GSM) |
| MAC | Media Access Control Address (IEEE) | | MAC | Media Access Control Address (IEEE) |
| WiMAX | device certificate unique id | | WiMAX | device certificate unique id |
| IMEI | International Mobile Equipment ID (GSM)| | IMEI | International Mobile Equipment ID (GSM)|
| UDI | Unique Device Identifier (medical) | | UDI | Unique Device Identifier (medical) |
| RFID | Radio Frequency Identification | | RFID | Radio Frequency Identification |
| SN | Manufacturer Serial Number | | SN | Manufacturer Serial Number |
+--------+----------------------------------------+ +--------+----------------------------------------+
14.1.6. Additional Call Data Blocks Registry 14.1.6. Additional Call Data Blocks Registry
This document creates a new subregistry called \0x2019Additional Call This document creates a new subregistry called \0x2019Additional Call
Data Blocks\0x2019 in the purpose registry established by RFC3261. Data Blocks\0x2019 in the purpose registry established by RFC3261.
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
and "Specification Required" rules. The expert is responsible for and "Specification Required" rules. The expert is responsible for
verifying that the document contains a complete and clear verifying that the document contains a complete and clear
specification of the block and the block does not obviously duplicate specification of the block and the block does not obviously duplicate
existing blocks. existing blocks.
skipping to change at page 33, line 5 skipping to change at page 45, line 6
RFC Editor Note: RFC Editor Note:
replace XXXX in the table above with this documents RFC number replace XXXX in the table above with this documents RFC number
14.2. 'emergencyCallData' Purpose Parameter Value 14.2. 'emergencyCallData' Purpose Parameter Value
This document defines the 'emergencyCall' value for the "purpose" This document defines the 'emergencyCall' 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 emergencyCall [This RFC] Call-Info purpose emergencyCall [This RFC]
14.3. URN Sub-Namespace Registration for provided-by Registry Entry 14.3. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in Section 14.5.1 in This section registers the namespace specified in Section 14.5.1 in
the provided-by registry established by RFC 4119, for usage within the provided-by registry established by RFC 4119, for usage within
the 'provided-by' element of a PIDF-LO. the 'provided-by' element of a PIDF-LO.
14.3.1. Provided-By XML Schema 14.3.1. Provided-By XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCallAddlData" targetNamespace="urn:ietf:params:xml:ns:emergencyCallAddlData"
targetNamespace="urn:ietf:params:xml:ns:pidf: targetNamespace="urn:ietf:params:xml:ns:pidf:
geopriv10:emergencyCallData" geopriv10:emergencyCallData"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData" xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
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"/>
<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="emergencyCallDataReference"> <xs:element name="emergencyCallDataReference">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:attribute name="ref" <xs:attribute name="ref"
type="xs:anyURI" use="required"/> type="xs:anyURI" use="required"/>
<xs:attribute name="purpose" <xs:attribute name="purpose"
type="xs:string" use="required"/> type="xs:string" use="required"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="emergencyCallDataValue"> <xs:element name="emergencyCallDataValue">
<xs:attribute name="purpose" <xs:attribute name="purpose"
type="xs:string" use="required"/> type="xs:string" use="required"/>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Figure 6: Provided-By XML Schema
14.4. MIME Registrations 14.4. MIME Registrations
14.4.1. MIME Content-type Registration for 'application/ 14.4.1. MIME Content-type Registration for 'application/
emergencyCall.ProviderInfo+xml' emergencyCall.ProviderInfo+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: emergencyCall.ProviderInfo+xml MIME subtype name: emergencyCall.ProviderInfo+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].
Security considerations: Security considerations:
This content type is designed to carry the data provider information, This content type is designed to carry the data provider
which is a sub-category of additional data about an emergency call. information, which is a sub-category of additional data about an
emergency call.
Since this data contains personal information appropriate precautions Since this data contains personal information appropriate
have to be taken to limit unauthorized access, inappropriate precautions have to be taken to limit unauthorized access,
disclosure to third parties, and eavesdropping of this information. inappropriate disclosure to third parties, and eavesdropping of
Please refer to Section 12 and Section 13 for more information. this information. Please refer to Section 12 and Section 13 for
more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person 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>
14.4.2. MIME Content-type Registration for 'application/ 14.4.2. MIME Content-type Registration for 'application/
emergencyCall.SvcInfo+xml' emergencyCall.SvcInfo+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: emergencyCall.SvcInfo+xml MIME subtype name: emergencyCall.SvcInfo+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].
Security considerations: Security considerations:
This content type is designed to carry the service information, which This content type is designed to carry the service information,
is a sub-category of additional data about an emergency call. which is a sub-category of additional data about an emergency
call.
Since this data contains personal information appropriate precautions Since this data contains personal information appropriate
have to be taken to limit unauthorized access, inappropriate precautions have to be taken to limit unauthorized access,
disclosure to third parties, and eavesdropping of this information. inappropriate disclosure to third parties, and eavesdropping of
Please refer to Section 12 and Section 13 for more information. this information. Please refer to Section 12 and Section 13 for
more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT'
Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person 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>
14.4.3. MIME Content-type Registration for 'application/ 14.4.3. MIME Content-type Registration for 'application/
emergencyCall.DevInfo+xml' emergencyCall.DevInfo+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: emergencyCall.DevInfo+xml MIME subtype name: emergencyCall.DevInfo+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].
Security considerations: Security considerations:
This content type is designed to carry the device information This content type is designed to carry the device information
information, which is a sub-category of additional data about an information, which is a sub-category of additional data about an
emergency call. emergency call.
Since this data contains personal information appropriate precautions Since this data contains personal information appropriate
have to be taken to limit unauthorized access, inappropriate precautions have to be taken to limit unauthorized access,
disclosure to third parties, and eavesdropping of this information. inappropriate disclosure to third parties, and eavesdropping of
Please refer to Section 12 and Section 13 for more information. this information. Please refer to Section 12 and Section 13 for
more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
File Extension: .xml
Macintosh file type code: 'TEXT' File Extension: .xml
Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person 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>
14.4.4. MIME Content-type Registration for 'application/ 14.4.4. MIME Content-type Registration for 'application/
emergencyCall.SubInfo+xml' emergencyCall.SubInfo+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: emergencyCall.SubInfo+xml MIME subtype name: emergencyCall.SubInfo+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].
Security considerations: Security considerations:
This content type is designed to carry owner/subscriber information, This content type is designed to carry owner/subscriber
which is a sub-category of additional data about an emergency call. information, which is a sub-category of additional data about an
emergency call.
Since this data contains personal information appropriate precautions Since this data contains personal information appropriate
have to be taken to limit unauthorized access, inappropriate precautions have to be taken to limit unauthorized access,
disclosure to third parties, and eavesdropping of this information. inappropriate disclosure to third parties, and eavesdropping of
Please refer to Section 12 and Section 13 for more information. this information. Please refer to Section 12 and Section 13 for
more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person 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>
14.4.5. MIME Content-type Registration for 'application/ 14.4.5. MIME Content-type Registration for 'application/
emergencyCall.Comment+xml' emergencyCall.Comment+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: emergencyCall.Comment+xml MIME subtype name: emergencyCall.Comment+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].
Security considerations: Security considerations:
This content type is designed to carry a comment, which is a sub- This content type is designed to carry a comment, which is a sub-
category of additional data about an emergency call. category of additional data about an emergency call.
This data may contain personal information. Appropriate precautions This data may contain personal information. Appropriate
may have to be taken to limit unauthorized access, inappropriate precautions may have to be taken to limit unauthorized access,
disclosure to third parties, and eavesdropping of this information. inappropriate disclosure to third parties, and eavesdropping of
Please refer to Section 12 and Section 13 for more information. this information. Please refer to Section 12 and Section 13 for
more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
File Extension: .xml File Extension: .xml
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person 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>
14.5. URN Sub-Namespace Registration 14.5. URN Sub-Namespace Registration
14.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData 14.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData
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:emergencyCallAddlData URI: urn:ietf:params:xml:ns:emergencyCallAddlData
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data</title> <title>Namespace for Additional Emergency Call Data</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>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.5.2. Registration for 14.5.2. Registration for
urn:ietf:params:xml:ns:emergencyCallProviderInfo urn:ietf:params:xml:ns:emergencyCallProviderInfo
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:emergencyCallProviderInfo URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
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
14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo 14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo
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:emergencyCall.SvcInfo URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
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
14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo 14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo
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:emergencyCall.DevInfo URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
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
14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo 14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo
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:emergencyCall.SubInfo URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
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
14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment 14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment
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:emergencyCall.Comment URI: urn:ietf:params:xml:ns:emergencyCall.Comment
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data:Comment</title> <title>Namespace for Additional Emergency Call Data:Comment</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> Comment</h2> <h2> Comment</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.6. Schema Registrations 14.6. Schema Registrations
This specification registers five schemas, as per the guidelines in This specification registers five schemas, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:schema:additional- URI: urn:ietf:params:xml:schema:additional-
data:emergencyCallProviderInfo data:emergencyCallProviderInfo
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: The XML schema can be found in Figure 2. XML: The XML schema can be found in Figure 1.
URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo
Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Figure 3. XML: The XML schema can be found in Figure 2.
URI: urn:ietf:params:xml:schema:additional- URI:
data:emergencyCallDevInfo urn:ietf:params:xml:schema:additional-data:emergencyCallDevInfo
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: The XML schema can be found in Figure 4. XML: The XML schema can be found in Figure 3.
URI: urn:ietf:params:xml:schema:additional- URI:
data:emergencyCall.SubInfo urn:ietf:params:xml:schema:additional-data:emergencyCall.SubInfo
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: The XML schema can be found in Section 8.2. XML: The XML schema can be found in Section 8.2.
URI: urn:ietf:params:xml:schema:additional- URI:
data:emergencyCall.Comment urn:ietf:params:xml:schema:additional-data:emergencyCall.Comment
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: The XML schema can be found in Section 9.2. XML: The XML schema can be found in Section 9.2.
14.7. VCard Parameter Value Registration 14.7. VCard Parameter Value Registration
This document registers a new value in the vCARD Parameter Values This document registers a new value in the vCARD Parameter Values
registry as defined by [RFC6350] with the following template: registry as defined by [RFC6350] with the following template:
Value: main Value: main
Purpose: The main telephone number, typically of an enterprise, as Purpose: The main telephone number, typically of an enterprise, as
opposed to a direct dial number of an individual employee opposed to a direct dial number of an individual employee
Conformance: This value can be used with the "TYPE" parameter applied Conformance: This value can be used with the "TYPE" parameter
on the "TEL" property. applied on the "TEL" property.
Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-900 Example(s):
0 TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-9000
15. Acknowledgments 15. Acknowledgments
This work was originally started in NENA and has benefitted from a This work was originally started in NENA and has benefitted from a
large number of participants in NENA standardization efforts, large number of participants in NENA standardization efforts,
originally in the Long Term Definition Working Group, the Data originally in the Long Term Definition Working Group, the Data
Technical Committee and most recently the Additional Data working Technical Committee and most recently the Additional Data working
group. The authors are grateful for the initial work and extended group. The authors are grateful for the initial work and extended
comments provided by the many NENA participants. comments provided by the many NENA participants.
16. References 16. References
16.1. Normative References 16.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. Locators", RFC 2392, August 1998.
[RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, A., Peterson, J., Sparks, R., Handley, M., and E.
"SIP: Session Initiation Protocol", RFC 3261, June 2002. Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", RFC 4288, December 2005. Registration Procedures", RFC 4288, December 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
[RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC [RFC6351] Perreault, S., "xCard: vCard XML Representation",
6351, August 2011. RFC 6351, August 2011.
16.2. Informational References 16.2. Informational References
[I-D.iab-privacy-considerations] [I-D.iab-privacy-considerations]
Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M. and R. Smith, "Privacy Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", Internet-Draft Considerations for Internet Protocols",
draft-iab-privacy-considerations-03, July 2012. draft-iab-privacy-considerations-03 (work in progress),
July 2012.
[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",
Internet-Draft draft-ietf-ecrit-phonebcp-20, September draft-ietf-ecrit-phonebcp-20 (work in progress),
2011. September 2011.
[RFC5222] Hardie, T., Newton, A., Schulzrinne, H. and H. Tschofenig, [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.
"LoST: A Location-to-Service Translation Protocol", RFC Tschofenig, "LoST: A Location-to-Service Translation
5222, August 2008. Protocol", RFC 5222, August 2008.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J. and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 2011. 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
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Nokia Siemens Networks
Linnoitustie 6 Linnoitustie 6
Espoo, 02600 Espoo 02600
Finland Finland
Phone: +358 (50) 4871445 Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
Roger Marshall Roger Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
2401 Elliott Avenue 2401 Elliott Avenue
Seattle, WA 98121 Seattle, WA 98121
US US
Phone: +1 206 792 2424 Phone: +1 206 792 2424
Email: rmarshall@telecomsys.com Email: rmarshall@telecomsys.com
URI: http://www.telecomsys.com URI: http://www.telecomsys.com
Randall Gellens Randall Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, CA 92121 San Diego, CA 92121
US US
Email: rg+ietf@qti.qualcomm.com Email: rg+ietf@qti.qualcomm.com
 End of changes. 293 change blocks. 
777 lines changed or deleted 878 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/