< draft-ietf-ecrit-additional-data-22.txt   draft-ietf-ecrit-additional-data-23.txt >
ECRIT B. Rosen ECRIT B. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: October 25, 2014 (no affiliation) Expires: April 5, 2015 (no affiliation)
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
R. Gellens R. Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
J. Winterbottom J. Winterbottom
(no affiliation) (no affiliation)
April 23, 2014 October 02, 2014
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-22.txt draft-ietf-ecrit-additional-data-23.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 application service (PSAP), the device that sends it, as well as any application service
provider in the path of the call, or access network provider through provider in the path of the call, or access network provider through
which the call originated may have information about the call, the which the call originated may have information about the call, the
caller or the location which the PSAP may be able to use. This caller or the location which the PSAP may be able to use. This
document describes data structures and a mechanism to convey such document describes data structures and a mechanism to convey such
data to the PSAP. The mechanism uses a Uniform Resource Identifier data to the PSAP. The mechanism uses a Uniform Resource Identifier
skipping to change at page 2, line 4 skipping to change at page 2, line 4
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 October 25, 2014. This Internet-Draft will expire on April 5, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Data Provider Information . . . . . . . . . . . . . . . . 8 4. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7
3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 4.1. Data Provider Information . . . . . . . . . . . . . . . . 8
3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8 4.1.1. Data Provider String . . . . . . . . . . . . . . . . 8
3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9 4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9
3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9 4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9
3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10 4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 10
3.1.6. Data Provider Languages(s) Supported . . . . . . . . 11 4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 11
3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11 4.1.6. Data Provider Languages(s) Supported . . . . . . . . 11
3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12 4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 12
3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13 4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12
3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13 4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13
3.2. Service Information . . . . . . . . . . . . . . . . . . . 15 4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13
3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15 4.2. Service Information . . . . . . . . . . . . . . . . . . . 16
3.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16
3.2.3. Service Mobility Environment . . . . . . . . . . . . 17 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16
3.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 18 4.2.3. Service Mobility Environment . . . . . . . . . . . . 19
3.3. Device Information . . . . . . . . . . . . . . . . . . . 18 4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 19
3.3.1. Device Classification . . . . . . . . . . . . . . . . 18 4.3. Device Information . . . . . . . . . . . . . . . . . . . 20
3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 20 4.3.1. Device Classification . . . . . . . . . . . . . . . . 20
3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 20 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 21
3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 22
3.3.5. Device/Service Specific Additional Data Structure . . 21 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 22
3.3.6. Device/Service Specific Additional Data Structure 4.3.5. Device/Service Specific Additional Data Structure . . 23
Type . . . . . . . . . . . . . . . . . . . . . . . . 22 4.3.6. Device/Service Specific Additional Data Structure
3.3.7. Issues with getting new types of data into use . . . 23 Type . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.8. Choosing between defining a new type of block or new 4.3.7. Issues with getting new types of data into use . . . 24
type of device/service specific additional data . . . 23 4.3.8. Choosing between defining a new type of block or new
3.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 24 type of device/service specific additional data . . . 25
3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 25
3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 25 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26
3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26
3.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 26 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27
3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27
3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 28 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 29
4. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 29 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30
4.1. Transmitting Blocks using the Call-Info Header . . . . . 31 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30
4.2. Transmitting Blocks by Reference using the Provided-By 5.1. Transmitting Blocks using the Call-Info Header . . . . . 32
Element . . . . . . . . . . . . . . . . . . . . . . . . . 31 5.2. Transmitting Blocks by Reference using the Provided-By
4.3. Transmitting Blocks by Value using the Provided-By Element . . . . . . . . . . . . . . . . . . . . . . . . . 33
Element . . . . . . . . . . . . . . . . . . . . . . . . . 32 5.3. Transmitting Blocks by Value using the Provided-By
4.4. The Content-Disposition Parameter . . . . . . . . . . . . 33 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 34
6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 45 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 47 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 47
6.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 48 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 49
6.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 49 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 49
6.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 50 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 51
6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 51 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 51
7. Security Considerations . . . . . . . . . . . . . . . . . . . 53 7.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 52
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 54 8. Security Considerations . . . . . . . . . . . . . . . . . . . 54
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 56
9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 56 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59
9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 56 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 59
9.1.2. Service Environment Registry . . . . . . . . . . . . 57 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 59
9.1.3. Service Provider Type Registry . . . . . . . . . . . 57 10.1.2. Service Environment Registry . . . . . . . . . . . . 60
9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 60
9.1.5. Device Classification Registry . . . . . . . . . . . 58 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 61
9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 58 10.1.5. Service Provider Type Registry . . . . . . . . . . . 61
9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 62
9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 59 10.1.7. Device Classification Registry . . . . . . . . . . . 62
9.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . . 60 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 63
9.3. URN Sub-Namespace Registration for provided-by Registry 10.1.9. Device/Service Data Type Registry . . . . . . . . . 63
Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 60 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 63
9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 60 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 64
9.4.1. MIME Content-type Registration for 10.3. URN Sub-Namespace Registration for provided-by Registry
'application/EmergencyCallData.ProviderInfo+xml' . . 60 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 65
9.4.2. MIME Content-type Registration for 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 65
'application/EmergencyCallData.ServiceInfo+xml' . . . 61 10.4.1. MIME Content-type Registration for
9.4.3. MIME Content-type Registration for 'application/EmergencyCallData.ProviderInfo+xml' . . 65
'application/EmergencyCallData.DeviceInfo+xml' . . . 62 10.4.2. MIME Content-type Registration for
9.4.4. MIME Content-type Registration for 'application/EmergencyCallData.ServiceInfo+xml' . . 66
'application/EmergencyCallData.SubscriberInfo+xml' . 63 10.4.3. MIME Content-type Registration for
'application/EmergencyCallData.DeviceInfo+xml' . . . 67
9.4.5. MIME Content-type Registration for 10.4.4. MIME Content-type Registration for
'application/EmergencyCallData.Comment+xml' . . . . . 64 'application/EmergencyCallData.SubscriberInfo+xml' . 68
9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 65 10.4.5. MIME Content-type Registration for
9.5.1. Registration for 'application/EmergencyCallData.Comment+xml' . . . . 69
urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 65 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 71
9.5.2. Registration for 10.5.1. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 66 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 71
9.5.3. Registration for 10.5.2. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 67 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf
9.5.4. Registration for o . . . . . . . . . . . . . . . . . . . . . . . . . 71
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo . 67 10.5.3. Registration for
9.5.5. Registration for urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 72
urn:ietf:params:xml:ns:EmergencyCallData:SubscriberIn 10.5.4. Registration for
fo . . . . . . . . . . . . . . . . . . . . . . . . . 68 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 73
9.5.6. Registration for 10.5.5. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 69 urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI
9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 69 nfo . . . . . . . . . . . . . . . . . . . . . . . . 73
9.7. VCard Parameter Value Registration . . . . . . . . . . . 70 10.5.6. Registration for
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 74
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 71 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 75
11.1. Normative References . . . . . . . . . . . . . . . . . . 71 10.7. VCard Parameter Value Registration . . . . . . . . . . . 76
11.2. Informational References . . . . . . . . . . . . . . . . 72 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 76
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 74 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 76
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 12.1. Normative References . . . . . . . . . . . . . . . . . . 76
12.2. Informational References . . . . . . . . . . . . . . . . 77
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 79
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 101
1. Introduction 1. Introduction
When an IP-based emergency call is initiated, a rich set of data from When an IP-based emergency call is initiated, a rich set of data from
multiple data sources is conveyed to the Public Safety Answering multiple data sources is conveyed to the Public Safety Answering
Point (PSAP). This data includes information about the calling party Point (PSAP). This data includes information about the calling party
identity, the multimedia capabilities of the device, the emergency identity, the multimedia capabilities of the device, the request for
service number, location information, and meta-data about the sources emergency services, location information, and meta-data about the
of the data. The device, the access network provider, and any sources of the data. The device, the access network provider, and
service provider in the call path may have even more information any service provider in the call path may have even more information
useful for a PSAP. This document extends the basic set of data useful for a PSAP. This document extends the basic set of data
communicated with an IP-based emergency call, as described in communicated with an IP-based emergency call, as described in
[RFC6443] and [RFC6881], in order to carry additional data which may [RFC6443] and [RFC6881], in order to carry additional data which may
be useful to an entity or call taker handling the call. This data is be useful to an entity or call taker handling the call. This data is
"additional" to the basic information found in the emergency call "additional" to the basic information found in the emergency call
signaling used. signaling used.
In general, there are three categories of this additional data that In general, there are three categories of this additional data that
may be transmitted with an emergency call: may be transmitted with an emergency call:
Data Associated with a Location: Primary location data is conveyed Data Associated with a Location: Primary location data is conveyed
in the Presence Information Data Format Location Object (PIDF-LO) in the Presence Information Data Format Location Object (PIDF-LO)
data structure as defined in RFC 4119 [RFC4119] and extended by data structure as defined in RFC 4119 [RFC4119] and extended by
RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location
information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for
geodetic location information), and geodetic location information), and [RFC7035] (for relative
[I-D.ietf-geopriv-relative-location] (for relative location). location). This primary location data identifies the location or
This primary location data identifies the location or estimated estimated location of the caller. However, there may exist
location of the caller. However, there may exist additional, additional, secondary data which is specific to the location, such
secondary data which is specific to the location, such as floor as floor plans, tenant and building owner contact data, heating,
plans, tenant and building owner contact data, heating,
ventilation and air conditioning (HVAC) status, etc. Such ventilation and air conditioning (HVAC) status, etc. Such
secondary location data is not included in the location data secondary location data is not included in the location data
structure but can be transmitted using the mechanisms defined in structure but can be transmitted using the mechanisms defined in
this document; although this document does not define any this document. Although this document does not define any
structures for such data, future documents may do so following the structures for such data, future documents may do so following the
procedures defined here. procedures defined here.
Data Associated with a Call: While some information is carried in Data Associated with a Call: While some information is carried in
the call setup procedure itself (as part of the SIP headers as the call setup procedure itself (as part of the SIP headers as
well as in the body of the SIP message), there is additional data well as in the body of the SIP message), there is additional data
known by the device making the call and/or a service provider known by the device making the call and/or a service provider
along the path of the call. This information may include the along the path of the call. This information may include the
service provider contact information, subscriber identity and service provider contact information, subscriber identity and
contact information, the type of service the service provider and contact information, the type of service the service provider and
the access network provider offer, what type of device is being the access network provider offer, what type of device is being
used, etc. Some data is broadly applicable, while other data is used, etc. Some data is broadly applicable, while other data is
dependent on the type of device or service. For example, a dependent on the type of device or service. For example, a
medical monitoring device may have sensor data. The data medical monitoring device may have sensor data. The data
structures defined in this document (Data Provider Information, structures defined in this document (Data Provider Information,
Device Information, and Owner/Subscriber Information) all fall Device Information, and Owner/Subscriber Information) all fall
into this category ("Data Associated with a Call"). into the category of "Data Associated with a Call".
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. Although such as medical information and emergency contact data. Although
this document does not define any structures within this category, this document does not define any structures within this category,
future documents may do so following the procedures defined here. future documents may do so following the procedures defined here.
While this document defines data structures only within the category While this document defines data structures only within the category
of Data Associated with a Call, by establishing the overall framework of Data Associated with a Call, by establishing the overall framework
of Additional Data, along with general mechanisms for transport of of Additional Data, along with general mechanisms for transport of
such data, extension points and procedures for future extensions, it such data, extension points and procedures for future extensions, it
skipping to change at page 6, line 10 skipping to change at page 6, line 12
Identification allows emergency services authorities to know during Identification allows emergency services authorities to know during
call processing which types of data are present and to determine if call processing which types of data are present and to determine if
they wish to access it. A common encoding allows the data to be they wish to access it. A common encoding allows the data to be
successfully accessed. successfully accessed.
This document defines an extensible set of data structures, and This document defines an extensible set of data structures, and
mechanisms to transmit this data either by value or by reference, mechanisms to transmit this data either by value or by reference,
either in the Session Initiation Protocol (SIP) call signaling or in either in the Session Initiation Protocol (SIP) call signaling or in
the Presence Information Data Format Location Object (PIDF-LO). The the Presence Information Data Format Location Object (PIDF-LO). The
data structures are usable by other communication systems and data structures are usable by other communication systems and
transports as well. The data structures are defined in Section 3, transports as well. The data structures are defined in Section 4,
and the transport mechanisms (using SIP and HTTPS) are defined in and the transport mechanisms (using SIP and HTTPS) are defined in
Section 4. Section 5.
Each data structure described in this document is encoded as a Each data structure described in this document is encoded as a
"block" of information. Each block is an XML structure with an "block" of information. Each block is an XML structure with an
associated Multipurpose Internet Mail Extensions (MIME) type for associated Multipurpose Internet Mail Extensions (MIME) type for
identification within transport such as SIP and HTTPS. The set of identification within transport such as SIP and HTTPS. The set of
blocks is extensible. Registries are defined to identify the block blocks is extensible. Registries are defined to identify the block
types that may be used and to allow blocks to be included in types that may be used and to allow blocks to be included in
emergency call signaling. emergency call signaling.
2. Terminology 2. Terminology
skipping to change at page 6, line 36 skipping to change at page 6, line 38
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
This document also uses terminology from [RFC5012]. We use the term This document also uses terminology from [RFC5012]. We use the term
service provider to refer to an Application Service Provider (ASP). service provider to refer to an Application Service Provider (ASP).
A Voice Service Provider (VSP) is a special type of ASP. With the A Voice Service Provider (VSP) is a special type of ASP. With the
term "Access Network Provider" we refer to the Internet Access term "Access Network Provider" we refer to the Internet Access
Provider (IAP) and the Internet Service Provider (ISP) without Provider (IAP) and the Internet Service Provider (ISP) without
further distinguishing these two entities, since the difference further distinguishing these two entities, since the difference
between the two is not relevant for this document. Note that the between the two is not relevant for this document. Note that the
roles of ASP and access network provider may be provided by a single roles of ASP and access network provider may be provided by a single
company. company. An Emergency Services Provider is an entity directly
involved in providing emergency services. This includes PSAPs,
dispatch, police, fire, emergency medical, other responders, and
other similar agencies.
Within each data block definition (see Section 3), the values for the Within each data block definition (see Section 4), the values for the
"Use:" label are specified as one of the following: "Use:" label are specified as one of the following:
'Required': means it MUST be present in the data structure. 'Required': means it MUST be present in the data structure.
'Conditional': means it MUST be present if the specified 'Conditional': means it MUST be present if the specified
condition(s) is met. It MAY be present if the condition(s) is not condition(s) is met. It MAY be present if the condition(s) is not
met. met.
'Optional': means it MAY be present. 'Optional': means it MAY be present.
vCard is a data format for representing and exchanging a variety of vCard is a data format for representing and exchanging a variety of
information about individuals and other entities. For applications information about individuals and other entities. For applications
that use XML the format defined in vCard is not immediately that use XML the format defined in vCard is not immediately
applicable. For this purpose an XML-based encoding of the applicable. For this purpose an XML-based encoding of the
information elements defined in the vCard specification has been information elements defined in the vCard specification has been
defined and the name of that specification is xCard. Since the term defined and the name of that specification is xCard. Since the term
vCard is more familiar to most readers, we use the term xCard and vCard is more familiar to most readers, we use the term xCard and
vCard interchangeably. vCard interchangeably.
3. Data Structures 3. Document Scope
The scope of this document is explicitly limited to emergency calls.
The data structures defined here are not appropriate to be conveyed
with non-emergency calls because they carry sensitive and private
data.
4. Data Structures
This section defines the following five data structures, each as a This section defines the following five data structures, each as a
data block. For each block we define the MIME type, and the XML data block. For each block we define the MIME type, and the XML
encoding. The five data structures are: encoding. The five data structures are:
'Data Provider': This block supplies name and contact information 'Data Provider': This block supplies name and contact information
for the entity that created the data. Section 3.1 provides the for the entity that created the data. Section 4.1 provides the
details. details.
'Service Information': This block supplies information about the 'Service Information': This block supplies information about the
service. The description can be found in Section 3.2. service. The description can be found in Section 4.2.
'Device Information': This block supplies information about the 'Device Information': This block supplies information about the
device placing the call. Device information can be found in device placing the call. Device information can be found in
Section 3.3. Section 4.3.
'Owner/Subscriber': This block supplies information about the owner 'Owner/Subscriber': This block supplies information about the owner
of the device or about the subscriber. Details can be found in of the device or about the subscriber. Details can be found in
Section 3.4. Section 4.4.
'Comment': This block provides a way to supply free form human 'Comment': This block provides a way to supply free form human
readable text to the PSAP or emergency responders. This simple readable text to the PSAP or emergency responders. This simple
structure is defined in Section 3.5. structure is defined in Section 4.5.
Each block contains a mandatory <DataProviderReference> element. The Each block contains a mandatory <DataProviderReference> element. The
purpose of the <DataProviderReference> element is to associate all purpose of the <DataProviderReference> element is to associate all
blocks added by the same data provider as a unit. The blocks added by the same data provider as a unit. The
<DataProviderReference> element associates the data provider block to <DataProviderReference> element associates the data provider block to
each of the other blocks added as a unit. Consequently, when a data each of the other blocks added as a unit. Consequently, when a data
provider adds additional data to an emergency call (such as device provider adds additional data to an emergency call (such as device
information) it MUST add information about itself (via the data information) it MUST add information about itself (via the data
provider block) and the blocks added contain the same value in the provider block) and the blocks added contain the same value in the
<DataProviderReference> element. All blocks added by a single entity <DataProviderReference> element. All blocks added by a single entity
at the same time MUST have the same <DataProviderReference> value. at the same time MUST have the same <DataProviderReference> value.
The value of the <DataProviderReference> element has the same syntax The value of the <DataProviderReference> element has the same syntax
and properties (specifically, world-uniqueness) as the value of the and properties (specifically, world-uniqueness) as the value of the
"Content-ID" message body header field specified in RFC 2045 "Message-ID" message body header field specified in RFC 5322
[RFC2045] except that the <DataProviderReference> element is not [RFC5322] except that the <DataProviderReference> element is not
enclosed in brackets (the "<" and ">" symbols are omitted). In other enclosed in brackets (the "<" and ">" symbols are omitted). In other
words, the value of an <DataProviderReference> element is words, the value of a <DataProviderReference> element is
syntactically an addr-spec as specified in RFC 822 [RFC0822]. syntactically a msg-id as specified in RFC 5322 [RFC5322].
Note that the xCard format is re-used in some of the data structures Note that the xCard format is re-used in some of the data structures
to provide contact information. In an xCard there is no way to to provide contact information. In an xCard 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.
3.1. Data Provider Information 4.1. Data Provider Information
This block is intended to be supplied by any service provider in the This block is intended to be supplied 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
supplied by every service provider in the call path, and by the supplied by every service provider in the call path, and by 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/
EmergencyCallData.ProviderInfo+xml". An access network provider EmergencyCallData.ProviderInfo+xml". An access network provider
SHOULD provide this block either by value or by reference in the SHOULD provide this block either by value or by reference in the
Provided-By section of a PIDF-LO Provided-By section of a PIDF-LO
3.1.1. Data Provider String 4.1.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Required Use: Required
XML Element: <DataProviderString> XML Element: <DataProviderString>
Description: This is a plain text string suitable for displaying the Description: This is a plain text string suitable for displaying the
name of the service provider that supplied the data structure. If name of the service provider that supplied the data structure. If
the device creates the structure, it SHOULD use the value of the the device creates the structure, it SHOULD use the value of the
contact header in the SIP INVITE. 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 data. providing the data.
How Used by Call Taker: Allows the call taker to interpret the data How Used by Call Taker: Allows the call taker to interpret the data
in this structure. The source of the information often influences in this structure. The source of the information often influences
how the information is used, believed or verified. how the information is used, believed or verified.
3.1.2. Data Provider ID 4.1.2. Data Provider ID
Data Element: Data Provider ID Data Element: Data Provider ID
Use: Conditional. This data SHOULD be provided if the service Use: Required. This data MUST be provided in order to uniquely
provider or access provider is located in a jurisdiction that identify the service provider or access provider.
maintains such IDs. For example, in North America, this would be
a NENA Company ID.
XML Element: <ProviderID> XML Element: <ProviderID>
Description: A jurisdiction-specific code for the access network Description: A jurisdiction-specific code for, or the fully-
provider or service provider shown in the <DataProvidedBy> element qualified domain name of, the access network provider or service
that created the structure. NOTE: In the US, the provider's NENA provider shown in the <DataProvidedBy> element that created the
Company ID MUST appear here. Additional information can be found structure. NOTE: The value SHOULD be assigned by an organization
at NENA Company Identifier Program [1] or NENA Company ID [2]. appropriate for the jurisdiction. In the U.S., the provider's
The NENA Company ID MUST be in the form of a URI in the following NENA Company ID MUST appear here. Additional information can be
format: urn:nena:companyid:<NENA Company ID> found at NENA Company Identifier Program [1] or NENA Company ID
[2]. The NENA Company ID MUST be in the form of a URI in the
following format: urn:nena:companyid:<NENA Company ID>. The value
MAY be the fully-qualified domain name of the service provider or
access provider.
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 data. providing the data.
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 provides useful information about the data the Data Provider ID provides useful information about the data
source. source. The Data Provider ID uniquely identifies the source of
the data, which might be needed especially during unusual
circumstances and for routine logging.
3.1.3. Data Provider ID Series 4.1.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: Required.
Series is required.
XML Element: <ProviderIDSeries> XML Element: <ProviderIDSeries>
Description: Identifies the issuer of the ProviderId. The Provider Description: Identifies the issuer of the <ProviderID>. The
ID Series Registry (see Section 9.1) initially contains the Provider ID Series Registry (see Section 10.1) initially contains
following valid entries: the following valid entries:
* NENA * NENA
* EENA * EENA
* domain
Reason for Need: Identifies how to interpret the Data Provider ID. Reason for Need: Identifies how to interpret the Data Provider ID.
The combination of ProviderIDSeries and ProviderID MUST be
globally unique.
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
3.1.4. Type of Data Provider 4.1.4. Type of Data Provider
Data Element: Type of Data Provider ID Data Element: Type of Data Provider
Use: Conditional. If Data Provider ID is provided, Type of Data Use: Required.
Provider ID is required.
XML Element: <TypeOfProviderID> XML Element: <TypeOfProvider>
Description: Identifies the type of data provider ID being supplied
in the ProviderID data element. A registry with an initial set of Description: Identifies the type of data provider supplying the
values is shown in Figure 1 (see also Section 9.1). data. A registry with an initial set of values is shown in Figure
1 (see also Section 10.1).
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Token | Description | | Token | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Access Network Provider | Access network service provider | |Access Network Provider | Access network service provider |
|Telecom Provider | Calling or origination telecom SP | |Telecom Provider | Calling or origination telecom SP |
|Telematics Provider | A sensor based service provider, | |Telematics Provider | A sensor based service provider, |
| | especially vehicle based | | | especially vehicle based |
|Language Translation Provider | A spoken language translation SP | |Language Translation Provider | A spoken language translation SP |
|Emergency Service Provider | An emergency service provider | |Emergency Service Provider | An emergency service provider |
skipping to change at page 10, line 28 skipping to change at page 10, line 47
| | emergency service provider. | | | emergency service provider. |
|Emergency Modality Translation| An emergency call specific | |Emergency Modality Translation| An emergency call specific |
| | modality translation service | | | modality translation service |
| | e.g., for sign language | | | e.g., for sign language |
|Relay Provider | A interpretation SP, for example, | |Relay Provider | A interpretation SP, for example, |
| | video relay for sign language | | | video relay for sign language |
| | interpreting | | | interpreting |
|Other | Any other type of service provider | |Other | Any other type of service provider |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
Figure 1: Type of Data Provider ID Registry. Figure 1: Type of Data Provider Registry.
Reason for Need: Identifies the category of data provider. Reason for Need: Identifies the category of data provider.
How Used by Call Taker: This information may be helpful when How Used by Call Taker: This information may be helpful when
deciding whom to contact when further information is needed. deciding whom to contact when further information is needed.
3.1.5. Data Provider Contact URI 4.1.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: When provided by a service provider or an access Description: When provided by a service provider or an access
network provider, this information MUST be a URI to a 24/7 support network provider, this information MUST be a URI to a 24/7 support
organization tasked to provide PSAP support for this emergency organization tasked to provide PSAP support for this emergency
call. If the call is from a device, this SHOULD be the contact call. If the call is from a device, this SHOULD be the contact
information of the owner of the device. If a telephone number is information of the owner of the device. The Data Provider Contact
the contact address then it MUST be a tel URI. If it is provided URI SHOULD be a TEL URI [RFC3966] in E.164 format fully specified
as a SIP URI then it MUST be in the form of with country code. If a TEL URI is not available, it MAY be a
sip:telephonenumber@serviceprovider:user=phone. Note that this generic SIP URI. Note that this contact information is not used
contact information is not used by PSAPs for callbacks (a call by PSAPs for callbacks (a call from a PSAP directly related to a
from a PSAP directly related to a recently terminated emergency recently terminated emergency call, placed by the PSAP using a SIP
call, placed by the PSAP using a SIP Priority header field set to Priority header field set to "psap-callback", as described in
"psap-callback", as described in [I-D.ietf-ecrit-psap-callback]). [RFC7090]).
Reason for Need: Additional data providers may need to be contacted Reason for Need: Additional data providers may need to be contacted
in error cases or other unusual circumstances. in error cases 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.
3.1.6. Data Provider Languages(s) Supported 4.1.6. Data Provider Languages(s) Supported
Data Element: Data Provider Language(s) supported Data Element: Data Provider Language(s) supported
Use: Required. Use: Required.
XML Element: <Language> XML Element: <Language>
Description: The language used by the entity at the Data Provider Description: The language used by the entity at the Data Provider
Contact URI, as an alpha 2-character code as defined in ISO Contact URI, as an alpha 2-character code as defined in ISO
639-1:2002 Codes for the representation of names of languages -- 639-1:2002 Codes for the representation of names of languages --
Part 1: Alpha-2 code Multiple instances of this element may occur. Part 1: Alpha-2 code Multiple instances of this element may occur.
Order is significant; preferred language should appear first. The Order is significant; preferred language should appear first. The
content MUST reflect the languages supported at the contact URI. content MUST reflect the languages supported at the contact URI.
Note that the 'language' media feature tag, defined in RFC 3840 Note that the 'language' media feature tag, defined in RFC 3840
[RFC3840] and the more extensive language negotiation mechanism [RFC3840] and the more extensive language negotiation mechanism
proposed with [I-D.gellens-negotiating-human-language] are proposed with [I-D.gellens-mmusic-negotiating-human-language] are
independent of this data provider language indication. independent of this data provider language indication.
Reason for Need: This information indicates if the emergency service Reason for Need: This information indicates if the emergency service
authority can directly communicate with the service provider or if authority can directly communicate with the service provider or if
an interpreter will be needed. an interpreter will be needed.
How Used by Call Taker: If call taker cannot speak language(s) How Used by Call Taker: If the call taker cannot speak any language
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. Alternatively, other persons at to be added to the conversation. Alternatively, other persons at
the PSAP, besides the call taker, might be consulted for help the PSAP, besides the call taker, might be consulted for help
(depending on the urgency and the type of interaction). (depending on the urgency and the type of interaction).
3.1.7. xCard of Data Provider 4.1.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 the name of the support group or device minimum. N SHOULD contain the name of the support group or device
owner as appropriate. If more than one TEL property is provided, owner as appropriate. If more than one TEL property is provided,
a parameter from the vCard Property Value registry MUST be a parameter from the vCard Property Value registry MUST be
specified on each TEL. For encoding of the xCard this specified on each TEL. For encoding of the xCard this
specification uses the XML-based encoding specified in [RFC6351], specification uses the XML-based encoding specified in [RFC6351],
referred to in this document as "xCard" referred to in this document 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 the call taker by providing
contact information that may not be included in the SIP invite or additional contact information aside from what may be included in
the PIDF-LO. the SIP INVITE or the PIDF-LO.
3.1.8. Subcontractor Principal 4.1.8. Subcontractor Principal
When the entity providing the data is a subcontractor, the Data When the entity providing the data is a subcontractor, the Data
Provider Type is set to that of the primary service provider and this Provider Type is set to that of the primary service provider and this
entry is supplied to provide information regarding the subcontracting entry is supplied to provide information regarding the subcontracting
entity. entity.
Data Element: Subcontractor Principal Data Element: Subcontractor Principal
Use: Conditional. This data is required if the entity providing the Use: Conditional. This data is required if the entity providing the
data is a subcontractor. data is a subcontractor.
XML Element: <SubcontratorPrincipal> XML Element: <SubcontratorPrincipal>
Description: Some providers outsource their obligations to handle Description: Some providers outsource their obligations to handle
aspects of emergency services to specialized providers. If the aspects of emergency services to specialized providers. If the
data provider is a subcontractor to another provider this element data provider is a subcontractor to another provider this element
contains the DataProviderString of the service provider to contains the DataProviderString of the service provider to
indicate which provider the subcontractor is working for. indicate which provider the subcontractor is working for.
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.
3.1.9. Subcontractor Priority 4.1.9. Subcontractor Priority
Data Element: Subcontractor Priority Data Element: Subcontractor Priority
Use: Conditional. This element is required if the Data Provider Use: Conditional. This element is required if the Data Provider
type is set to "Subcontractor". type is set to "Subcontractor".
XML Element: <SubcontractorPriority> XML Element: <SubcontractorPriority>
Description: If the subcontractor has to be contacted first then Description: If the subcontractor has to be contacted first then
this element MUST have the value "sub". If the provider the this element MUST have the value "sub". If the provider the
subcontractor is working for has to be contacted first then this subcontractor is working for has to be contacted first then this
element MUST have the value "main". element MUST have the value "main".
Reason for Need: Inform the call taker whom to contact first, if Reason for Need: Inform the call taker whom to contact first, if
support is needed. support is 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.
3.1.10. ProviderInfo Example 4.1.10. ProviderInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<ad:EmergencyCallData.ProviderInfo <ad:EmergencyCallData.ProviderInfo
xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ad:id>12345</ad:id> <ad:id>12345</ad:id>
<ad:DataProviderReference>string0987654321@example.org <ad:DataProviderReference>string0987654321@example.org
</ad:DataProviderReference> </ad:DataProviderReference>
<ad:DataProviderString>Example VoIP Provider <ad:DataProviderString>Example VoIP Provider
</ad:DataProviderString> </ad:DataProviderString>
<ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID> <ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>
<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries> <ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
<ad:TypeOfProvider>Service Provider</ad:TypeOfProvider> <ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider>
<ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI> <ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI>
<ad:Language>EN</ad:Language> <ad:Language>EN</ad:Language>
<ad:DataProviderContact <ad:DataProviderContact
xmlns="urn:ietf:params:xml:ns:vcard-4.0"> xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
<additional/> <additional/>
<prefix/> <prefix/>
skipping to change at page 15, line 30 skipping to change at page 16, line 5
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://www.tschofenig.priv.at</uri> <uri>http://www.tschofenig.priv.at</uri>
</url> </url>
</vcard> </vcard>
</ad:DataProviderContact> </ad:DataProviderContact>
</ad:EmergencyCallData.ProviderInfo> </ad:EmergencyCallData.ProviderInfo>
Figure 2: EmergencyCallData.ProviderInfo Example. Figure 2: EmergencyCallData.ProviderInfo Example.
3.2. Service Information 4.2. 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/ call. The mime subtype is "application/
EmergencyCallData.ServiceInfo+xml". EmergencyCallData.ServiceInfo+xml".
3.2.1. Service Environment 4.2.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
Use: Required Use: Optional when a 'ServiceType' value is 'wireless'; required
otherwise.
XML Element: <ServiceEnvironment> XML Element: <ServiceEnvironment>
Description: This element defines whether a call is from a business Description: This element defines whether a call is from a business
or residence caller. Currently, the only valid entries are or residence caller. Currently, the only valid entries are
'Business' or 'Residence'. New values can be defined via the 'Business', 'Residence', and 'unknown'. New values can be defined
registry created in Figure 22. via the registry created in Figure 22.
Reason for Need: To assist in determining equipment and manpower Reason for Need: To provide context and a hint when determining
requirements. equipment and manpower requirements.
How Used by Call Taker: Information may be used to assist in How Used by Call Taker: Information may be used to provide context
determining equipment and manpower requirements for emergency and a hint to assist in determining equipment and manpower
responders. As the information is not always available, and the requirements for emergency responders. Because there are cases
registry is not all encompassing, this is at best advisory where the service provider does not know (such as anonymous pre-
paid service), and the type of service does not neccessarily
reflect the nature of the premises (for example, a business line
installed in a residence, or wireless service), and the registry
is not all encompassing, therefore 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 (e.g., a field in the Automatic
The service provider uses its best information (such as a rate Location Information (ALI) information used with legacy North
plan, facilities used to deliver service or service description) American wireline systems), it is known to be valuable. The
to determine the information and is not responsible for service provider uses its best information (such as a rate plan,
determining the actual characteristics of the location where the facilities used to deliver service or service description) to
call originates from. determine the information and is not responsible for determining
the actual characteristics of the location from which the call
originated. Because the usefulness is unknown (and less clear)
for wireless, this element is OPTIONAL for wireless and REQUIRED
otherwise.
3.2.2. Service Type 4.2.2. Service Type
Data Element: Service Delivered by Provider to End User Data Element: Service Delivered by Provider to End User
Use: Required Use: Required
XML Element: <ServiceType> XML Element: <ServiceType>
Description: This defines the type of service over which the call is Description: This defines the type of service over which the call is
placed. The implied mobility of this service cannot be relied placed. The implied mobility of this service cannot be relied
upon. A registry with an initial set of values is defined in upon. A registry with an initial set of values is defined in
Figure 3. Figure 3.
+--------------+----------------------------------------+ +--------------+----------------------------------------+
| Name | Description | | Name | Description |
+--------------+----------------------------------------+ +--------------+----------------------------------------+
| wireless | Wireless Telephone Service: Includes | | wireless | Wireless Telephone Service: Includes |
| | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but |
| | not satellite ) | | | not satellite) |
| 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 |
| one-way | One way outbound service | | one-way | One way outbound service |
| prison | Inmate call/service | | prison | Inmate call/service |
| temp | Soft dialtone/quick service/warm | | temp | Soft dial tone/quick service/warm |
| | disconnect/suspended | | | disconnect/suspended |
| MLTS | Multi-line telephone system: Includes | | MLTS-hosted | Hosted multi-line telephone system |
| | all PBX, Centrex, key systems, | | | such as Centrex |
| MLTS-local | Local multi-line telephone system, |
| | includes all PBX, key systems, |
| | Shared Tenant Service | | | Shared Tenant Service |
| sensor- | | sensor- |
| unattended | These are devices that generate DATA | | unattended | These are devices that generate DATA |
| | ONLY. This is a one-way information | | | ONLY. This is a one-way information |
| | transmit without interactive media | | | transmit without interactive media |
| sensor- | | | sensor- | |
| attended | Devices that are supported by a | | attended | Devices that are supported by a |
| | monitoring service provider or that | | | monitoring service provider or that |
| | are capable of supporting interactive| | | are capable of supporting interactive|
| | media | | | media |
skipping to change at page 17, line 29 skipping to change at page 19, line 8
More than one value MAY be returned. For example, a VoIP inmate More than one value MAY be returned. For example, a VoIP inmate
telephone service is a reasonable combination. telephone service is a reasonable combination.
Reason for Need: Knowing the type of service may assist the PSAP Reason for Need: Knowing the type of service may assist the PSAP
with the handling of the call. with the handling of the call.
How Used by Call Taker: 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 than 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.
3.2.3. Service Mobility Environment 4.2.3. Service Mobility Environment
Data Element: Service Mobility Environment Data Element: Service Mobility Environment
Use: Required Use: Required
XML Element: <ServiceMobility> XML Element: <ServiceMobility>
Description: This provides the service provider's view of the Description: This provides the service provider's view of the
mobility of the caller. As the service provider may not know the mobility of the caller's device. As the service provider may not
characteristics of the actual device or access network used, the know the characteristics of the actual device or access network
value MUST NOT be relied upon. A registry reflects the following used, the value MUST NOT be relied upon. The registry specified
initial valid entries: in Figure 23 reflects the following initial valid entries:
* Mobile: the device is 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 change its point of * Nomadic: the device is not expected to change its point of
attachment while on a call attachment while on a call
* Unknown: no information is known about the service mobility * Unknown: no information is known about the service mobility
environment for the device environment for the device
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.
3.2.4. EmergencyCallData.ServiceInfo Example 4.2.4. EmergencyCallData.ServiceInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<svc:EmergencyCallData.ServiceInfo <svc:EmergencyCallData.ServiceInfo
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData.ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData.ServiceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:DataProviderReference>string0987654321@example.org <svc:DataProviderReference>2468.IBOC.MLTS.1359@example.org
</svc:DataProviderReference> </svc:DataProviderReference>
<svc:id>12345</svc:id> <svc:id>12345</svc:id>
<svc:ServiceEnvironment>Business</svc:ServiceEnvironment> <svc:ServiceEnvironment>Business</svc:ServiceEnvironment>
<svc:ServiceType>MLTS</svc:ServiceType> <svc:ServiceType>MLTS-hosted</svc:ServiceType>
<svc:ServiceMobility>Fixed</svc:ServiceMobility> <svc:ServiceMobility>Fixed</svc:ServiceMobility>
</svc:EmergencyCallData.ServiceInfo> </svc:EmergencyCallData.ServiceInfo>
Figure 4: EmergencyCallData.ServiceInfo Example. Figure 4: EmergencyCallData.ServiceInfo Example.
3.3. Device Information 4.3. 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/EmergencyCallData.DeviceInfo+xml". "application/EmergencyCallData.DeviceInfo+xml".
3.3.1. Device Classification 4.3.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 device, not how service provider. This information describes the device, not how
it is being used. This data element defines the kind of device it is being used. This data element defines the kind of device
making the emergency call. The registry with the initial set of making the emergency call. The registry with the initial set of
values is shown in Figure 5. values is shown in Figure 5.
+---------------+----------------------------------------+ +---------------+----------------------------------------+
| Token | Description | | Token | Description |
+---------------+----------------------------------------+ +---------------+----------------------------------------+
|cordless | Cordless handset | |cordless | Cordless handset |
|fixed | Fixed phone | |fixed | Fixed phone |
|satellite | Satellite phone | |satellite | Satellite phone |
|sensor-fixed | Fixed (non mobile) sensor/alarm device | |sensor-fixed | Fixed (non mobile) sensor/alarm device |
|desktop | Desktop PC | |desktop | Soft client on desktop PC |
|laptop | Laptop computing device | |laptop | Soft client on laptop type device |
|tablet | Tablet computing device | |tablet | Soft client on tablet type device |
|alarm-monitored| Alarm system | |alarm-monitored| Alarm system |
|sensor-mobile | Mobile sensor device | |sensor-mobile | Mobile sensor device |
|aircraft | Aircraft telematics device | |aircraft | Aircraft telematics device |
|automobile | Automobile/cycle/off-road telematics | |automobile | Automobile/cycle/off-road telematics |
|truck | Truck/construction telematics | |truck | Truck/construction telematics |
|farm | Farm equipment telematics | |farm | Farm equipment telematics |
|marine | Marine telematics | |marine | Marine telematics |
|personal | Personal telematics device | |personal | Personal telematics device |
|feature-phone | Feature (not smart-) cellular phone | |feature-phone | Feature- (not smart-) cellular phone |
|smart-phone | Smart-phone cellular phone | |smart-phone | Smart-phone cellular phone (native) |
|smart-phone-app| Soft client app on smart-phone |
|unknown-device | Soft client on unknown device type |
|game | Gaming console | |game | Gaming console |
|text-only | Other text device | |text-only | Other text device |
|NA | Not Available | |NA | Not Available |
+---------------+----------------------------------------+ +---------------+----------------------------------------+
Figure 5: Device Classification Registry. Figure 5: Device Classification Registry.
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 provide the call taker context regarding
example, a cordless handset may be outside or next door. May the caller, the capabilities of the calling device or the
provide the calltaker some context about the caller, the environment in which the device is being used, and may assist in
capabilities of the device used for the call or the environment understanding the location information and capabilities of the
the device is being used in. calling device. For example, a cordless handset may be outside or
next door.
3.3.2. Device Manufacturer 4.3.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 the calltaker, but by How Used by Call Taker: Probably not used by the calltaker, but by
PSAP management. PSAP management.
3.3.3. Device Model Number 4.3.3. Device Model Number
Data Element: Device Model Number Data Element: Device Model Number
Use: Optional Use: Optional
XML Element: <DeviceModelNr> XML Element: <DeviceModelNr>
Description: Model number 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 the calltaker, but by How Used by Call Taker: Probably not used by the calltaker, but by
PSAP management. PSAP management.
3.3.4. Unique Device Identifier 4.3.4. Unique Device Identifier
Data Element: Unique Device Identifier Data Element: Unique Device Identifier
Use: Optional Use: Optional
XML Element: <UniqueDeviceID> XML Element: <UniqueDeviceID>
XML Attribute: <TypeOfDeviceID> XML Attribute: <TypeOfDeviceID>
Description: A string that identifies the specific device (or the Description: A string that identifies the specific device (or the
device's current SIM) making the call or creating an event. Note device's current SIM) making the call or creating an event. Note
that more than one <UniqueDeviceID> may be present, to supply more that more than one <UniqueDeviceID> may be present, to supply more
than one of the identifying values. than one of the identifying values.
The <TypeOfDeviceID> attribute identifies the type of device The <TypeOfDeviceID> attribute identifies the type of device
identifier. A registry with an initial set of values can be seen identifier. A registry with an initial set of values can be seen
in Figure 6. in Figure 6.
+--------+------------------------------------------+ +--------+------------------------------------------+
skipping to change at page 21, line 38 skipping to change at page 23, line 19
Reason for Need: Uniquely identifies the device (or, in the case of Reason for Need: Uniquely identifies the device (or, in the case of
IMSI, a SIM), independent of any signaling identifiers present in IMSI, a SIM), independent of any signaling identifiers present in
the call signaling stream. the call signaling stream.
How Used by Call Taker: Probably not used by the call taker; may be How Used by Call Taker: Probably not used by the call taker; may be
used by PSAP management during an investigation. used by PSAP management during an investigation.
Example: <UniqueDeviceID TypeOfDeviceID="SN">12345</UniqueDeviceID> Example: <UniqueDeviceID TypeOfDeviceID="SN">12345</UniqueDeviceID>
3.3.5. Device/Service Specific Additional Data Structure 4.3.5. Device/Service Specific Additional Data Structure
Data Element: Device/service specific additional data structure Data Element: Device/service specific additional data structure
Use: Optional Use: Optional
XML Element: <DeviceSpecificData> XML Element: <DeviceSpecificData>
Description: A URI representing additional data whose schema is Description: A URI representing additional data whose schema is
specific to the device or service which created it. (For example, specific to the device or service which created it. (For example,
a medical device or medical device monitoring service may have a a medical device or medical device monitoring service may have a
defined set of medical data.) The URI, when dereferenced, MUST defined set of medical data). The URI, when dereferenced, MUST
yield a data structure defined by the Device/service specific yield a data structure defined by the Device/service specific
additional data type value. Different data may be created by each additional data type value. Different data may be created by each
classification; e.g., a medical device created data set. classification; e.g., a medical device created data set.
Reason for Need: Provides device/service specific data that may be Reason for Need: Provides device/service specific data that may be
used by the call taker and/or responders. used by the call taker and/or responders.
How Used by Call Taker: Provide information to guide call takers to How Used by Call Taker: Provide information to guide call takers to
select appropriate responders, give appropriate pre-arrival select appropriate responders, give appropriate pre-arrival
instructions to callers, and advise responders of what to be instructions to callers, and advise responders of what to be
prepared for. May be used by responders to guide assistance prepared for. May be used by responders to guide assistance
provided. provided.
3.3.6. Device/Service Specific Additional Data Structure Type 4.3.6. Device/Service Specific Additional Data Structure Type
Data Element: Type of device/service specific additional data Data Element: Type of device/service specific additional data
structure structure
Use: Conditional. MUST be provided when device/service specific Use: Conditional. MUST be provided when device/service specific
additional URI is provided additional URI is provided
XML Element: <DeviceSpecificType> XML Element: <DeviceSpecificType>
Description: Value from a registry defined by this document to Description: Value from a registry defined by this document to
skipping to change at page 23, line 5 skipping to change at page 24, line 27
may assist in emergency response. may assist in emergency response.
How Used by Call Taker: This data element allows the end user How Used by Call Taker: This data element allows the end user
(calltaker or first responder) to know what type of additional (calltaker or first responder) to know what type of additional
data may be available to aid in providing the needed emergency data may be available to aid in providing the needed emergency
services. services.
Note: Information which is specific to a location or a caller Note: Information which is specific to a location or a caller
(person) should not be placed in this section. (person) should not be placed in this section.
3.3.7. Issues with getting new types of data into use 4.3.7. Issues with getting new types of data into use
This document describes two mechanisms which allow extension of the This document describes two mechanisms which allow extension of the
kind of data provided with an emergency call: define a new block or kind of data provided with an emergency call: define a new block or
define a new service specific additional data URL for the DeviceInfo define a new service specific additional data URL for the DeviceInfo
block. While defining new data types and getting a new device or block. While defining new data types and getting a new device or
application to send the new data may be easy, getting PSAPs and application to send the new data may be easy, getting PSAPs and
responders to actually retrieve the data and use it will be responders to actually retrieve the data and use it will be
difficult. New mechanism providers should understand that acquiring difficult. New mechanism providers should understand that acquiring
and using new forms of data usually require software upgrades at the and using new forms of data usually require software upgrades at the
PSAP and/or responders, as well as training of call takers and PSAP and/or responders, as well as training of call takers and
skipping to change at page 23, line 39 skipping to change at page 25, line 12
Implementers should consider that data from sensor-based devices in Implementers should consider that data from sensor-based devices in
some cases may not be useful to call takers or PSAPs (and privacy or some cases may not be useful to call takers or PSAPs (and privacy or
other considerations may preclude the PSAP from touching the data), other considerations may preclude the PSAP from touching the data),
but may be of use to responders. Some standards being developed by but may be of use to responders. Some standards being developed by
other organizations to carry data from the PSAP to responders are other organizations to carry data from the PSAP to responders are
designed to carry all additional data supplied in the call that designed to carry all additional data supplied in the call that
conform to this document, even if the PSAP does not fetch or conform to this document, even if the PSAP does not fetch or
interpret the data. This allows responders to get the data even if interpret the data. This allows responders to get the data even if
the PSAP does not. the PSAP does not.
3.3.8. Choosing between defining a new type of block or new type of 4.3.8. Choosing between defining a new type of block or new type of
device/service specific additional data device/service specific additional data
For devices that have device or service specific data, there are two For devices that have device or service specific data, there are two
choices to carry it. A new block can be defined, or the device/ choices to carry it. A new block can be defined, or the device/
service specific additional data URL the DeviceInfo block can be used service specific additional data URL the DeviceInfo block can be used
and a new type for it defined . The data passed would likely be the and a new type for it defined . The data passed would likely be the
same in both cases. Considerations for choosing which mechanism to same in both cases. Considerations for choosing which mechanism to
register under include: register under include:
Applicability: Information which will be carried by many kinds of Applicability: Information which will be carried by many kinds of
devices or services are more appropriately defined as separate devices or services are more appropriately defined as separate
blocks. blocks.
Privacy: Information which may contain private data may be better Privacy: Information which may contain private data may be better
sent in the DeviceInfo block, rather than a new block so that sent in the DeviceInfo block, rather than a new block so that
implementations are not tempted to send the data by value, and implementations are not tempted to send the data by value, and
thus having more exposure to the data than forcing the data to be thus having more exposure to the data than forcing the data to be
retrieved via the URL in DeviceInfo. retrieved via the URL in DeviceInfo.
Size: Information which may be very may be better sent in the Size: Information which may be very large may be better sent in the
DeviceInfo block, rather than a new block so that implementations DeviceInfo block, rather than a new block so that implementations
are not tempted to send the data by value. Conversely, data which are not tempted to send the data by value. Conversely, data which
is small may best be sent in a separate block so that it can be is small may best be sent in a separate block so that it can be
sent by value sent by value
Availability of a server: Providing the data via the device block Availability of a server: Providing the data via the device block
requires a server be made available to retrieve the data. requires a server be made available to retrieve the data.
Providing the data via new block allows it to be sent by value Providing the data via new block allows it to be sent by value
(CID). (CID).
3.3.9. EmergencyCallData.DeviceInfo Example 4.3.9. EmergencyCallData.DeviceInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:EmergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>string0987654321@example.org <dev:DataProviderReference>d4b3072df.201409182208075@example.org
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:id>12345</dev:id> <dev:id>12345</dev:id>
<dev:DeviceClassification>Fixed phone</dev:DeviceClassification> <dev:DeviceClassification>fixed</dev:DeviceClassification>
<dev:DeviceMfgr>Nokia</dev:DeviceMfgr> <dev:DeviceMfgr>Nokia</dev:DeviceMfgr>
<dev:DeviceModelNr>Lumia 800</dev:DeviceModelNr> <dev:DeviceModelNr>Lumia 800</dev:DeviceModelNr>
<dev:UniqueDeviceID TypeOfDeviceID="IMEI">35788104 <dev:UniqueDeviceID TypeOfDeviceID="IMEI">35788104
</dev:UniqueDeviceID> </dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
Figure 7: EmergencyCallData.DeviceInfo Example. Figure 7: EmergencyCallData.DeviceInfo Example.
3.4. Owner/Subscriber Information 4.4. 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/EmergencyCallData.Subscriber+xml". The MIME type is "application/EmergencyCallData.SubscriberInfo+xml".
In some jurisdictions some or all parts of the subscriber-specific In some jurisdictions some or all parts of the subscriber-specific
information are subject to privacy constraints. These constraints information are subject to privacy constraints. These constraints
vary but dictate what information and be displayed and logged. A vary but dictate what information can be displayed and logged. A
general privacy indicator expressing a desire for privacy is general privacy indicator expressing a desire for privacy is
provided. The interpretation of how this is applied is left to the provided. The interpretation of how this is applied is left to the
receiving jurisdiction as the custodians of the local regulatory receiving jurisdiction as the custodians of the local regulatory
requirements. requirements.
3.4.1. Subscriber Data Privacy Indicator 4.4.1. Subscriber Data Privacy Indicator
Attribute: privacyRequested, boolean. Attribute: privacyRequested, boolean.
Use: Conditional. This attribute MUST be provided if the owner/ Use: Conditional. This attribute MUST be provided if the owner/
subscriber information block is not empty. subscriber information block is not empty.
Description: The subscriber data privacy indicator specifically Description: The subscriber data privacy indicator specifically
expresses the subscriber's desire for privacy. In some expresses the subscriber's desire for privacy. In some
jurisdictions subscriber services can have a specific "Type of jurisdictions subscriber services can have a specific "Type of
Service" which prohibits information, such as the name of the Service" which prohibits information, such as the name of the
subscriber, from being displayed. This attribute should be used subscriber, from being displayed. This attribute should be used
to explicitly indicate whether the subscriber service includes to explicitly indicate whether the subscriber service includes
such constraints. such constraints.
Reason for Need: Some jurisdictions require subscriber privacy to be Reason for Need: Some jurisdictions require subscriber privacy to be
observed. observed when processing emergency calls.
How Used by Call Taker: Where privacy is indicated the call taker How Used by Call Taker: Where privacy is indicated the call taker
may not have access to some aspects of the subscriber information. may not have access to some aspects of the subscriber information.
3.4.2. xCard for Subscriber's Data 4.4.2. xCard for Subscriber's Data
Data Element: xCARD for Subscriber's Data Data Element: xCARD for Subscriber's Data
Use: Conditional. Subscriber data is provided unless it is not Use: Conditional. Subscriber data is provided unless it is not
available. Some services, for example prepaid phones, non- available. Some services, for example prepaid phones, non-
initialized phones, etc., do not have information about the initialized phones, etc., do not have information about the
subscriber. subscriber.
XML Element: <SubscriberData> XML Element: <SubscriberData>
skipping to change at page 26, line 9 skipping to change at page 27, line 30
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.
3.4.3. EmergencyCallData.SubscriberInfo Example 4.4.3. EmergencyCallData.SubscriberInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<sub:EmergencyCallData.SubscriberInfo <sub:EmergencyCallData.SubscriberInfo
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
privacyRequested="false"> privacyRequested="false">
<sub:DataProviderReference>string0987654321@example.org <sub:DataProviderReference>FEABFECD901@example.org
</sub:DataProviderReference> </sub:DataProviderReference>
<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcards> <vcards>
<vcard> <vcard>
<fn><text>Simon Perreault</text></fn> <fn><text>Simon Perreault</text></fn>
<n> <n>
<surname>Perreault</surname> <surname>Perreault</surname>
<given>Simon</given> <given>Simon</given>
<additional/> <additional/>
<prefix/> <prefix/>
skipping to change at page 28, line 21 skipping to change at page 29, line 42
</parameters> </parameters>
<uri>http://nomis80.org</uri> <uri>http://nomis80.org</uri>
</url> </url>
</vcard> </vcard>
</vcards> </vcards>
</sub:SubscriberData> </sub:SubscriberData>
</sub:EmergencyCallData.SubscriberInfo> </sub:EmergencyCallData.SubscriberInfo>
Figure 8: EmergencyCallData.SubscriberInfo Example. Figure 8: EmergencyCallData.SubscriberInfo Example.
3.5. Comment 4.5. 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 nor does it aim to provide for a general purpose extension mechanism nor does it aim to provide
machine-reable content. The mime subtype is "application/ machine-readable content. The mime subtype is "application/
EmergencyCallData.Comment+xml" EmergencyCallData.Comment+xml"
3.5.1. Comment 4.5.1. Comment
Data Element: EmergencyCallData.Comment Data Element: EmergencyCallData.Comment
Use: Optional Use: Optional
XML Element: <Comment> XML Element: <Comment>
Description: Human readable text providing additional information to Description: Human readable text providing additional information to
the PSAP staff. the PSAP staff.
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.
3.5.2. EmergencyCallData.Comment Example 4.5.2. EmergencyCallData.Comment Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<com:EmergencyCallData.Comment <com:EmergencyCallData.Comment
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<com:DataProviderReference>string0987654321@example.org <com:DataProviderReference>string0987654321@example.org
</com:DataProviderReference> </com:DataProviderReference>
<com:Comment xml:lang="en">This is an example text.</com:Comment> <com:Comment xml:lang="en">This is an example text.</com:Comment>
</com:EmergencyCallData.Comment> </com:EmergencyCallData.Comment>
Figure 9: EmergencyCallData.Comment Example. Figure 9: EmergencyCallData.Comment Example.
4. Data Transport Mechanisms 5. Data Transport Mechanisms
This section defines how to convey additional data to an emergency This section defines how to convey additional data to an emergency
service provider. Two different means are specified: the first uses service provider. Two different means are specified: the first uses
the call signaling; the second uses the <provided-by> element of a the call signaling; the second uses the <provided-by> element of a
PIDF-LO [RFC4119]. PIDF-LO [RFC4119].
1. First, the ability to embed a Uniform Resource Identifier (URI) 1. First, the ability to embed a Uniform Resource Identifier (URI)
in an existing SIP header field, the Call-Info header, is in an existing SIP header field, the Call-Info header, is
defined. The URI points to the additional data structure. The defined. The URI points to the additional data structure. The
Call-Info header is specified in Section 20.9 of [RFC3261]. This Call-Info header is specified in Section 20.9 of [RFC3261]. This
skipping to change at page 30, line 4 skipping to change at page 31, line 25
structure identified by its MIME type. (Blocks defined by others structure identified by its MIME type. (Blocks defined by others
may be encoded in XML or not, as identified by their MIME may be encoded in XML or not, as identified by their MIME
registration.) As usual, whenever more than one MIME part is registration.) As usual, whenever more than one MIME part is
included in the body of a message, MIME-multipart (i.e., included in the body of a message, MIME-multipart (i.e.,
'multipart/mixed') encloses them all. This document defines a 'multipart/mixed') encloses them all. This document defines a
set of XML schemas and MIME types used for each block defined set of XML schemas and MIME types used for each block defined
here. When additional data is passed by value in the SIP here. When additional data is passed by value in the SIP
signaling, each CID URL points to one block in the body. signaling, each CID URL points to one block in the body.
Multiple URIs are used within a Call-Info header field (or Multiple URIs are used within a Call-Info header field (or
multiple Call-Info header fields) to point to multiple blocks. multiple Call-Info header fields) to point to multiple blocks.
When additional data is provided by reference (in SIP signaling When additional data is provided by reference (in SIP signaling
or Provided-By), each HTTPS URL references one block; the data is or Provided-By), each HTTPS URL references one block; the data is
retrieved with an HTTPS GET operation, which returns one of the retrieved with an HTTPS GET operation, which returns one of the
blocks as an object (the blocks defined here are returned as XML blocks as an object (the blocks defined here are returned as XML
objects). objects).
2. Second, the ability to embed additional data structures in the 2. Second, the ability to embed additional data structures in the
<provided-by> element of a PIDF-LO [RFC4119] is defined. Besides <provided-by> element of a PIDF-LO [RFC4119] is defined. In
a service provider in the call path, the access network provider addition to service providers in the call path, the access
may also have similar information that may be valuable to the network provider may also have similar information that may be
PSAP. The access network provider may provide location in the valuable to the PSAP. The access network provider MAY provide
form of a PIDF-LO from a location server via a location location in the form of a PIDF-LO from a location server via a
configuration protocol. The data structures described in this location configuration protocol. The data structures described
document are not specific to the location itself, but rather in this document are not specific to the location itself, but
provides descriptive information having to do with the immediate rather provides descriptive information having to do with the
circumstances about the provision of the location (who the access immediate circumstances about the provision of the location (who
network is, how to contact that entity, what kind of service the the access network is, how to contact that entity, what kind of
access network provides, subscriber information, etc.). This service the access network provides, subscriber information,
data is similar in nearly every respect to the data known by etc.). This data is similar in nearly every respect to the data
service providers in the path of the call. When the access known by service providers in the path of the call. When the
network provider and service provider are separate entities, the access network provider and service provider are separate
access network does not participate in the application layer entities, the access network does not participate in the
signaling (and hence cannot add a Call-Info header field to the application layer signaling (and hence cannot add a Call-Info
SIP message), but may provide location information to assist in header field to the SIP message), but may provide location
locating the caller's device. The <provided-by> element of the information in a PIDF-LO object to assist in locating the
PIDF-LO is a mechanism for the access network provider to supply caller's device. The <provided-by> element of the PIDF-LO is a
the information about the entity or organization that supplied mechanism for the access network provider to supply the
this location information. For this reason, this document information about the entity or organization that supplied this
describes a namespace per RFC 4119 for inclusion in the location information. For this reason, this document describes a
<provided-by> element of a PIDF-LO for adding information known namespace per RFC 4119 for inclusion in the <provided-by> element
to the access network provider. of a PIDF-LO for adding information known to the access network
provider. The access network provider SHOULD provide additional
data within a Provided-By element of a PDIF-LO it returns for
emergency use (e.g., if requested with a HELD "responseTime"
attribute of "emergencyRouting" or "emergencyDispatch"
[RFC5985]).
One or more blocks of data registered in the Emergency Call One or more blocks of data registered in the Emergency Call
Additional Data registry, as defined in Section 9.1, may be included Additional Data registry, as defined in Section 10.1, may be included
or referenced in the SIP signaling (using the Call-Info header field) or referenced in the SIP signaling (using the Call-Info header field)
or in the <provided-by> element of a PIDF-LO. Every block must be or in the <provided-by> element of a PIDF-LO. Every block must be
one of the types in the registry. Since the data of an emergency one of the types in the registry. Since the data of an emergency
call may come from multiple sources, the data itself needs call may come from multiple sources, the data itself needs
information describing the source. Consequently, each entity adding information describing the source. Consequently, each entity adding
additional data MUST supply the "Data Provider" block. All other additional data MUST supply the "Data Provider" block. All other
blocks are optional, but each entity SHOULD supply any blocks where blocks are optional, but each entity SHOULD supply any blocks where
it has at least some of the information in the block. it has at least some of the information in the block.
4.1. Transmitting Blocks using the Call-Info Header 5.1. Transmitting Blocks using the Call-Info Header
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 value starting with 'EmergencyCallData' and the containing a purpose value starting with 'EmergencyCallData' and the
type of data available at the URI. The type of data is denoted by type of data available at the URI. The type of data is denoted by
including the root of the MIME type (not including the including the root of the MIME type (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.'
separator. For example, when referencing a block with MIME type separator. For example, when referencing a block with MIME type
'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose'
parameter is set to 'EmergencyCallData.ProviderInfo'. An example parameter is set to 'EmergencyCallData.ProviderInfo'. An example
skipping to change at page 31, line 47 skipping to change at page 33, line 22
provider is in the path of the call. The device MAY insert one if it provider is in the path of the call. The device MAY insert one if it
uses a service provider. Any service provider in the path of the uses a service provider. Any service provider in the path of the
call MUST insert its own. For example, a device, a telematics call MUST insert its own. For example, a device, a telematics
service provider in the call path, as well as the mobile carrier service provider in the call path, as well as the mobile carrier
handling the call will each provide one. There may be circumstances handling the call will each provide one. There may be circumstances
where there is a service provider who is unaware that the call is an where there is a service provider who is unaware that the call is an
emergency call and cannot reasonably be expected to determine that it emergency call and cannot reasonably be expected to determine that it
is an emergency call. In that case, that service provider is not is an emergency call. In that case, that service provider is not
expected to provide EmergencyCallData. expected to provide EmergencyCallData.
4.2. Transmitting Blocks by Reference using the Provided-By Element 5.2. Transmitting Blocks by Reference using the Provided-By Element
The 'EmergencyCallDataReference' element is used to transmit an The 'EmergencyCallDataReference' element is used to transmit an
additional data block by reference within a 'Provided-By' element of additional data block by reference within a 'Provided-By' element of
a PIDF-LO. The 'EmergencyCallDataReference' element has two a PIDF-LO. The 'EmergencyCallDataReference' element has two
attributes: 'ref' to specify the URL, and 'purpose' to indicate the attributes: 'ref' to specify the URL, and 'purpose' to indicate the
type of data block referenced. The value of 'ref' is an HTTPS URL type of data block referenced. The value of 'ref' is an HTTPS URL
that resolves to a data structure with information about the call. that resolves to a data structure with information about the call.
The value of 'purpose' is the same as used in a 'Call-Info' header The value of 'purpose' is the same as used in a 'Call-Info' header
field (as specified in Section 4.1). field (as specified in Section 5.1).
For example, to reference a block with MIME type 'application/ For example, to reference a block with MIME type 'application/
EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set
to 'EmergencyCallData.ProviderInfo'. An example to 'EmergencyCallData.ProviderInfo'. An example
'EmergencyCallDataReference' element for this would be: 'EmergencyCallDataReference' element for this would be:
<EmergencyCallDataReference ref="https://www.example.com/23sedde3" <EmergencyCallDataReference ref="https://www.example.com/23sedde3"
purpose="EmergencyCallData.ProviderInfo"/> purpose="EmergencyCallData.ProviderInfo"/>
4.3. Transmitting Blocks by Value using the Provided-By Element 5.3. Transmitting Blocks by Value using the Provided-By Element
It is RECOMMENDED that access networks supply the data specified in It is RECOMMENDED that access networks supply the data specified in
this document by reference, but they MAY provide the data by value. this document by reference, but they MAY provide the data by value.
The 'EmergencyCallDataValue' element is used to transmit an The 'EmergencyCallDataValue' element is used to transmit an
additional data block by value within a 'Provided-By' element of a additional data block by value within a 'Provided-By' element of a
PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: PIDF-LO. The 'EmergencyCallDataValue' element has one attribute:
'purpose' to indicate the type of data block contained. The value of 'purpose' to indicate the type of data block contained. The value of
'purpose' is the same as used in a 'Call-Info' header field (as 'purpose' is the same as used in a 'Call-Info' header field (as
specified in Section 4.1, and in Section 4.1). The same XML specified in Section 5, and in Section 5.1). The same XML structure
structure as would be contained in the corresponding MIME type body as would be contained in the corresponding MIME type body part is
part is placed inside the 'EmergencyCallDataValue' element. placed inside the 'EmergencyCallDataValue' element.
For example: For example:
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<EmergencyCallData> <ad:DataProviderReference>flurbit735@es.example.com
<byRef purpose="EmergencyCallData.ServiceInfo" </ad:DataProviderReference>
ref="https://example.com/ref2"/> <ad:EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2" />
<sub:EmergencyCallData.Comment <sub:EmergencyCallData.Comment
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData.Comment"> xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData.Comment">
<sub:Comment xml:lang="en">This is an example text. <sub:Comment xml:lang="en">This is an example text.
</sub:Comment> </sub:Comment>
</sub:EmergencyCallData.Comment> </sub:EmergencyCallData.Comment>
</EmergencyCallData>
<EmergencyCallDataValue <EmergencyCallDataValue
purpose="EmergencyCallData.ProviderInfo"> purpose="EmergencyCallData.ProviderInfo">
<ProviderID>Test</ProviderID> <ProviderID>Test</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProviderID>Access Infrastructure Provider <TypeOfProvider>Access Network Provider
</TypeOfProviderID> </TypeOfProvider>
<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. Example Provided-By by Value.
4.4. The Content-Disposition Parameter 5.4. The Content-Disposition Parameter
RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. RFC 5621 [RFC5621] discusses the handling of message bodies in SIP.
It updates and clarifies handling originally defined in RFC 3261 It updates and clarifies handling originally defined in RFC 3261
[RFC3261] based on implementation experience. While RFC 3261 did not [RFC3261] based on implementation experience. While RFC 3261 did not
mandate support for 'multipart' message bodies, 'multipart/mixed' mandate support for 'multipart' message bodies, 'multipart/mixed'
MIME bodies are used by many extensions (including this document) MIME bodies are used by many extensions (including this document)
today. For example, adding a PIDF-LO, SDP, and additional data in today. For example, adding a PIDF-LO, SDP, and additional data in
body of a SIP message requires a 'multipart' message body. body of a SIP message requires a 'multipart' message body.
RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling' RFC 3204 [RFC3204] and RFC 3459 [RFC3459] define the 'handling'
skipping to change at page 34, line 4 skipping to change at page 35, line 34
--boundary1 --boundary1
Content-Type: application/pidf+xml Content-Type: application/pidf+xml
Content-ID: <target123@atlanta.example.com> Content-ID: <target123@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
...PIDF-LO goes in here ...PIDF-LO goes in here
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference; handling=optional Content-Disposition: by-reference; handling=optional
...Data provider information data goes in here ...Data provider information data goes in here
--boundary1-- --boundary1--
Figure 10: Example for use of the Content-Disposition Parameter in Figure 10: Example for use of the Content-Disposition Parameter in
SIP. SIP.
5. Examples 6. Examples
This section illustrates a longer and more complex example, as shown This section illustrates a longer and more complex example, as shown
in Figure 11. In this example additional data is added by the end in Figure 11. In this example additional data is added by the end
device, included by the VoIP provider (via the PIDF-LO), and provided device, included by the VoIP provider (via the PIDF-LO), and provided
by the access network provider. by the access network provider.
[================] (1) [================] O +----+ [=============] [==============]
[ O +----+ ] Emergency Call [ ] /|\ | UA | [ Access ] [ VoIP ]
[ /|\ | UA |-------------------------------> ] | +----+ [ Network ] [ Provider ]
[ | +----+ ] +Device Info [ ] / \ [ Provider ] [ example.org ]
[ / \ ] +Data Provider Info [ ] [ ] [ ]
[ ] +Location URI [ ] (1) [ ] (2) [ ]
[ Access Network ] [ ] Emergency Call [ ] Emergency Call [ ]
[ Provider ] [ VoIP Provider ] ------------------------------------------------------------> ]
[ ] [ example.org ] +Device Info [ ] +Device Info [ ]
[ ^ ] [ ] +Data Provider Info [ ^ ] +Data Provider Info [ | ]
[=======.========] [============|===] +Location URI [===.=========] +Location URI [=====|========]
. | . |
. | . |
. [================] | +Location . [================] |
. [ ] (2) | +Owner/Subscriber Info . [ ] (3) |
. (3) [ <--------------+ +Device Info . (4) [ <---------------+
....................> PSAP ] Emergency Call +Data Provider Info #3 .............> ] Emergency Call
Location [ ] +Device Info [ ] +Device Info
+Owner/Subscriber Info [ ] +Data Provider Info #2 [ PSAP ] +Data Provider Info #2
+Device Info [ ] +Location URI [ ] +Location URI
+Data Provider Info #3 [================] [================]
Legend: Legend:
--- Emergency Call Setup Procedure --- Emergency Call Setup Procedure
... Location Retrieval/Response ... Location Retrieval/Response
Figure 11: Additional Data Example Flow Figure 11: Additional Data Example Flow
The example scenario starts with the end device itself adding device The example scenario starts with the end device itself adding device
information, owner/subscriber information, a location URI, and data information, owner/subscriber information, a location URI, and data
provider information to the outgoing emergency call setup message provider information to the outgoing emergency call setup message
(see step #1 in Figure 11). The SIP INVITE example is shown in (see step #1 in Figure 11). The SIP INVITE example is shown in
Figure 12. Figure 12.
INVITE urn:service:sos SIP/2.0 INVITE urn:service:sos SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo, ;purpose=EmergencyCallData.ProviderInfo,
<cide:0123456789@atlanta.example.com> <cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo ;purpose=EmergencyCallData.DeviceInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Contact: <sips:hannes@example.com> Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
skipping to change at page 35, line 50 skipping to change at page 37, line 40
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.DeviceInfo+xml Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-ID: <0123456789@atlanta.example.com> Content-ID: <0123456789@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:EmergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>string0987654321@example.org <dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:DeviceClassification>SoftPhn</dev:DeviceClassification> <dev:DeviceClassification>laptop</dev:DeviceClassification>
<dev:UniqueDeviceID <dev:UniqueDeviceID
TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:id>12345</pi:id> <pi:id>12345</pi:id>
<pi:DataProviderReference>string0987654321@example.org <pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</pi:DataProviderReference> </pi:DataProviderReference>
<pi:DataProviderString>Hannes Tschofenig <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString> </pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>sip:hannes@example.com</pi:ContactURI> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>EN</pi:Language>
<xc:DataProviderContact <xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
<additional/> <additional/>
<prefix/> <prefix/>
skipping to change at page 38, line 13 skipping to change at page 39, line 50
</parameters> </parameters>
<uri>http://example.com/hannes.tschofenig</uri> <uri>http://example.com/hannes.tschofenig</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
--boundary1-- --boundary1--
Figure 12: End Device sending SIP INVITE with Additional Data. Figure 12: End Device sending SIP INVITE with Additional Data.
In this example, information available to the access network operator In this example, information available to the access network provider
is included in the call setup message only indirectly via the use of is included in the call setup message only indirectly via the use of
the location reference. The PSAP has to retrieve it via a separate the location reference. The PSAP has to retrieve it via a separate
look-up step. Since the access network provider and the VoIP service look-up step. Since the access network provider and the VoIP service
provider are two independent entities in this scenario, the access provider are two independent entities in this scenario, the access
network operator is not involved in application layer exchanges; the network provider is not involved in application layer exchanges; the
SIP INVITE transits the access network transparently, as illustrated SIP INVITE transits the access network transparently, as illustrated
in step #1. No change to the SIP INVITE is applied. in steps #1 and #2. The access network does not alter the SIP
INVITE.
When the VoIP service provider receives the message and determines The VoIP service provider receives the message and determines based
based on the Service URN that the incoming request is an emergency on the Service URN that the incoming request is an emergency call.
call. It performs the typical emergency services related tasks, It performs typical emergency services related tasks, including
including location-based routing, and adds additional data, namely location-based routing, and adds additional data, namely service and
service and subscriber information, to the outgoing message. For the subscriber information as well as data provider information #2, to
example we assume a VoIP service provider that deploys a back-to-back the outgoing message. For the example we assume a VoIP service
user agent allowing additional data to be included in the body of the provider that deploys a back-to-back user agent allowing additional
SIP message (rather than per reference in the header), which allows data to be included in the body of the SIP message (rather than per
us to illustrate the use of multiple data provider info blocks. The reference in the header), which allows us to illustrate the use of
resulting message is shown in Figure 13. multiple data provider info blocks. The resulting message is shown
in Figure 13. The SIP INVITE is sent to the PSAP in step #3.
INVITE sips:psap@example.org SIP/2.0 INVITE sips:psap@example.org SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
skipping to change at page 39, line 13 skipping to change at page 41, line 4
Geolocation-Routing: yes Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Contact: <sips:hannes@example.com> Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...SDP goes here ...SDP goes here
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.DeviceInfo+xml Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-ID: <0123456789@atlanta.example.com> Content-ID: <0123456789@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:EmergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>string0987654321@example.org <dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:DeviceClassification>SoftPhn</dev:DeviceClassification> <dev:DeviceClassification>laptop</dev:DeviceClassification>
<dev:UniqueDeviceID <dev:UniqueDeviceID
TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:DataProviderReference>string0987654321@example.org <pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</pi:DataProviderReference> </pi:DataProviderReference>
<pi:DataProviderString>Hannes Tschofenig <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString> </pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>sip:hannes@example.com</pi:ContactURI> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>EN</pi:Language>
<xc:DataProviderContact <xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
<additional/> <additional/>
<prefix/> <prefix/>
skipping to change at page 43, line 44 skipping to change at page 45, line 34
</parameters> </parameters>
<uri>http://www.example.com/john.doe</uri> <uri>http://www.example.com/john.doe</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
Figure 13: VoIP Provider sending SIP INVITE with Additional Data. Figure 13: VoIP Provider sending SIP INVITE with Additional Data.
Finally, the PSAP requests location information from the access Finally, the PSAP requests location information from the access
network operator. The response is shown in Figure 14. Along with network provider. The response is shown in Figure 14. Along with
the location information additional data is provided in the the location information, additional data is provided in the
<Provided-By> element of the PIDF-LO. <Provided-By> element of the PIDF-LO. This request and response is
step #4.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
entity="pres:alice@atlanta.example.com"> entity="pres:alice@atlanta.example.com">
<dm:device id="target123-1"> <dm:device id="target123-1">
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
skipping to change at page 44, line 45 skipping to change at page 46, line 36
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<EmergencyCallDataReference purpose="EmergencyCallData.ServiceInfo" <EmergencyCallDataReference purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2"/> ref="https://example.com/ref2"/>
<EmergencyCallDataValue> <EmergencyCallDataValue>
<EmergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>string0987654321@example.org <DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference> </DataProviderReference>
<DataProviderString>University of California, Irvine <DataProviderString>University of Example
</DataProviderString> </DataProviderString>
<ProviderID>urn:nena:companyid:uci</ProviderID> <ProviderID>urn:nena:companyid:uoi</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Other</TypeOfProvider> <TypeOfProvider>Other</TypeOfProvider>
<ContactURI>tel:+1 9498245222</ContactURI> <ContactURI>tel:+1 555-824-5222</ContactURI>
<Language>EN</Language> <Language>EN</Language>
</EmergencyCallData.ProviderInfo> </EmergencyCallData.ProviderInfo>
<EmergencyCallData.Comment <EmergencyCallData.Comment
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<DataProviderReference>string0987654321@example.org <DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference> </DataProviderReference>
<Comment xml:lang="en">This is an example text.</Comment> <Comment xml:lang="en">This is an example text.</Comment>
</EmergencyCallData.Comment> </EmergencyCallData.Comment>
</EmergencyCallDataValue> </EmergencyCallDataValue>
</provided-by> </provided-by>
</gp:geopriv> </gp:geopriv>
<dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID> <dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID>
<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp> <dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>
</dm:device> </dm:device>
</presence> </presence>
Figure 14: Access Network Provider returning PIDF-LO with Additional Figure 14: Access Network Provider returning PIDF-LO with Additional
Data. Data.
6. XML Schemas 7. XML Schemas
This section defines the XML schemas of the five data blocks. This section defines the XML schemas of the five data blocks.
Additionally, the Provided-By schema is specified. Additionally, the Provided-By schema is specified.
6.1. EmergencyCallData.ProviderInfo XML Schema 7.1. EmergencyCallData.ProviderInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
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" elementFormDefault="qualified"
skipping to change at page 46, line 44 skipping to change at page 48, line 36
<xs:element name="ProviderIDSeries" <xs:element name="ProviderIDSeries"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="TypeOfProvider" <xs:element name="TypeOfProvider"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI" <xs:element name="ContactURI" type="xs:anyURI"
minOccurs="1" maxOccurs="1"/> minOccurs="1" maxOccurs="1"/>
<xs:element name="Language" type="pi:iso3166a2" <xs:element name="Language" type="pi:iso3166a2"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="1" maxOccurs="unbounded" />
<xs:element name="DataProviderContact" <xs:element name="DataProviderContact"
type="xc:vcardType" minOccurs="0" type="xc:vcardType" minOccurs="0"
maxOccurs="1"/> maxOccurs="1"/>
<xs:element name="SubcontratorPrincipal" <xs:element name="SubcontratorPrincipal"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="SubcontractorPriority" <xs:element name="SubcontractorPriority"
type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/> type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 15: EmergencyCallData.ProviderInfo XML Schema. Figure 15: EmergencyCallData.ProviderInfo XML Schema.
6.2. EmergencyCallData.ServiceInfo XML Schema 7.2. EmergencyCallData.ServiceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
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">
skipping to change at page 47, line 42 skipping to change at page 49, line 34
<xs:complexType name="ServiceInfoType"> <xs:complexType name="ServiceInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="ServiceEnvironment" <xs:element name="ServiceEnvironment"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ServiceType" <xs:element name="ServiceType"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
<xs:element name="ServiceMobility" <xs:element name="ServiceMobility"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Link"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 16: EmergencyCallData.ServiceInfo XML Schema. Figure 16: EmergencyCallData.ServiceInfo XML Schema.
6.3. EmergencyCallData.DeviceInfo XML Schema 7.3. EmergencyCallData.DeviceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
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"
skipping to change at page 49, line 16 skipping to change at page 51, line 4
<xs:element name="DeviceSpecificData" <xs:element name="DeviceSpecificData"
type="xs:anyURI" minOccurs="0" maxOccurs="1"/> type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceSpecificType" <xs:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 17: EmergencyCallData.DeviceInfo XML Schema. Figure 17: EmergencyCallData.DeviceInfo XML Schema.
6.4. EmergencyCallData.SubscriberInfo XML Schema 7.4. EmergencyCallData.SubscriberInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
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">
skipping to change at page 50, line 4 skipping to change at page 51, line 41
<xs:complexContent> <xs:complexContent>
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="SubscriberData" type="xc:vcardType" <xs:element name="SubscriberData" type="xc:vcardType"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="privacyRequested" type="xs:boolean" use="required"/> <xs:attribute name="privacyRequested" type="xs:boolean" use="required"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 18: EmergencyCallData.SubscriberInfo XML Schema. Figure 18: EmergencyCallData.SubscriberInfo XML Schema.
6.5. EmergencyCallData.Comment XML Schema 7.5. EmergencyCallData.Comment XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:Comment" "urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData: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"
skipping to change at page 51, line 9 skipping to change at page 52, line 44
<xs:extension base="xs:string"> <xs:extension base="xs:string">
<xs:attribute ref="xml:lang"/> <xs:attribute ref="xml:lang"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 19: EmergencyCallData.Comment XML Schema. Figure 19: EmergencyCallData.Comment XML Schema.
6.6. Provided-By XML Schema 7.6. Provided-By XML Schema
This section defines the Provided-By schema. This section defines the Provided-By schema.
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData" "urn:ietf:params:xml:ns:EmergencyCallData"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
skipping to change at page 52, line 16 skipping to change at page 54, line 4
<!-- Additional Data By Reference --> <!-- Additional Data By Reference -->
<xs:complexType name="ByRefType"> <xs:complexType name="ByRefType">
<xs:complexContent> <xs:complexContent>
<xs:restriction base="xs:anyType"> <xs:restriction base="xs:anyType">
<xs:sequence> <xs:sequence>
<xs:any namespace="##other" minOccurs="0" <xs:any namespace="##other" minOccurs="0"
maxOccurs="unbounded" processContents="lax"/> maxOccurs="unbounded" processContents="lax"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="purpose" type="xs:anyURI" <xs:attribute name="purpose" type="xs:token"
use="required"/> use="required"/>
<xs:attribute name="ref" type="xs:anyURI" <xs:attribute name="ref" type="xs:anyURI"
use="required"/> use="required"/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- Additional Data By Value --> <!-- Additional Data By Value -->
<xs:complexType name="EmergencyCallDataValueType"> <xs:complexType name="EmergencyCallDataValueType">
skipping to change at page 53, line 5 skipping to change at page 54, line 42
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 20: Provided-By XML Schema. Figure 20: Provided-By XML Schema.
7. Security Considerations 8. Security Considerations
The information in this data structure will usually be considered The data structures described in this document contain information
private. HTTPS is specified to require the provider of the usually considered private. When information is provided by value,
information to validate the credentials of the requester. While the entities that are a party to the SIP signaling (such as proxy servers
creation of a public key infrastructure (PKI) that has global scope and back-to-back user agents) will have access to it and need to
may be difficult, the alternatives to creating devices and services protect it against inappropriate disclosure. An entity that is able
that can provide critical information securely are more daunting. to eavesdrop on the SIP signaling will also have access. Some media
The provider may enforce any policy it wishes to use, but PSAPs and (such as in the clear Wi-Fi) is more vulnerable than others (such as
responder agencies should deploy a PKI so that providers of 3G or 4G cellular data traffic) to eavesdropping. Mechanisms that
additional data can check the certificate of the client and decide protect against eavesdropping (such as Transport Layer Security
the appropriate policy to enforce based on that certificate. (TLS)) SHOULD be preferentially used whenever feasible. When
information is provided by reference, HTTPS is specified for
dereferencing, and the provider of the information is REQUIRED to
validate the credentials of the requester. While the creation of a
public key infrastructure (PKI) that has global scope may be
difficult, the alternatives to creating devices and services that can
provide critical information securely are more daunting. The
provider of the information MAY enforce any policy it wishes to use,
but PSAPs and responder agencies SHOULD deploy a PKI so that
providers of additional data can check the certificate of the client
and decide the appropriate policy to enforce based on that
certificate.
Ideally, the PSAP and emergency responders will be given credentials Ideally, the PSAP and emergency responders will be given credentials
signed by an authority trusted by the data provider. In most signed by an authority trusted by the data provider. In most
circumstances, nationally recognized credentials would be sufficient, circumstances, nationally recognized credentials would be sufficient,
and if the emergency services arranges a PKI, data providers could be and if the emergency services arranges a PKI, data providers could be
provisioned with the root CA public key for a given nation. Some provisioned with the root CA public key for a given nation. Some
nations are developing a PKI for this, and related, purposes. Since nations are developing a PKI for this, and related, purposes. Since
calls could be made from devices where the device and/or the service calls could be made from devices where the device and/or the service
provider(s) are not local to the emergency authorities, globally provider(s) are not local to the emergency services authorities,
recognized credentials are useful. This might be accomplished by globally recognized credentials are useful. This might be
extending the notion of the "forest guide" described in [RFC5222] to accomplished by extending the notion of the "forest guide" described
allow the forest guide to provide the credential of the PKI root for in [RFC5582] to allow the forest guide to provide the credential of
areas that it has coverage information for, but standards for such a the PKI root for areas for which it has coverage information, but
mechanism are not yet available. In its absence, the data provider standards for such a mechanism are not yet available. In its
will need to obtain the root CA credentials for any areas it is absence, the data provider will need to obtain by out of band means
willing to provide additional data by out of band means. With the the root CA credentials for any areas to which it is willing to
credential of the root CA for a national emergency services PKI, the provide additional data. With the credential of the root CA for a
data provider server can validate the credentials of an entity national emergency services PKI, the data provider server can
requesting additional data by reference. validate the credentials of an entity requesting additional data by
reference.
The data provider also needs a credential that can be verified by the The data provider also needs a credential that can be verified by the
emergency services to know that it is receiving data from the right emergency services to know that it is receiving data from an
server. The emergency authorities could provide credentials, authorized server. The emergency services authorities could provide
distinguishable from credentials it provides to emergency responders credentials, distinguishable from credentials provided to emergency
and PSAPs, which could be used to validate data providers. Such responders and PSAPs, which could be used to validate data providers.
credentials would have to be acceptable to any PSAP or responder that Such credentials would have to be acceptable to any PSAP or responder
could receive a call with additional data supplied by that provider. that could receive a call with additional data supplied by that
This would be extensible to global credential validation using the provider. This would be extensible to global credential validation
forest guide as above. In the absence of such credentials, the using the forest guide as mentioned above. In the absence of such
emergency authorities could maintain a list of local data providers' credentials, the emergency services authorities could maintain a list
credentials provided to it out of band. At a minimum, the emergency of local data providers' credentials as provided to them out of band.
authorities could obtain a credential from the DNS entry of the At a minimum, the emergency services authorities could obtain a
domain in the Additional Data URI to at least validate that the credential from the DNS entry of the domain in the Additional Data
server is known to the domain providing the URI. URI to at least validate that the server is known to the domain
providing the URI.
Data provided by devices by reference have similar credential Data provided by devices by reference have similar credential
validation issues to service providers, and the solutions are the validation issues as for service providers, and the solutions are the
same. same.
8. Privacy Considerations Much of the information supplied by service providers and devices is
private and confidential; service providers and devices generally go
to lengths to protect this information; disclosing it in the context
of an emergency call is a trade-off to protect the greater interest
of the customer in an emergency.
Neither service providers nor devices will supply private information
unless the call is recognized as an emergency call. In cellular
telephony systems (such as those using 3GPP IMS), there are different
procedures for an originating device to place an emergency versus a
normal call. If a call that is really an emergency call is initiated
as a normal call and the cellular service provider recognizes this,
3GPP IMS permits the service provider to either accept the call
anyway or reject it with a specific code that instructs the device to
retry the call as an emergency call. Service providers SHOULD choose
the latter, because otherwise the device will not have included the
information specified in this document (since the device didn't
recognize the call as being an emergency call).
9. Privacy Considerations
This document enables functionality for conveying additional This document enables functionality for conveying additional
information about the caller to the callee. Some of this information information about the caller and the caller's device and service to
is personal data and therefore privacy concerns arise. An explicit the callee. Some of this information is personal data and therefore
privacy indicator for information directly relating to the callers privacy concerns arise. An explicit privacy indicator for
identity is defined and use is mandatory. However, observance of information directly relating to the caller's identity is defined and
this request for privacy and what information it relates to is use is mandatory. However, observance of this request for privacy
controlled by the destination jurisdiction. and what information it relates to is determined by the destination
jurisdiction.
There are a number of privacy concerns with regular real-time There are a number of privacy concerns with non-emergency real-time
communication services that are also applicable to emergency calling. communication services that are also applicable to emergency calling.
Data protection regulation world-wide has, however, decided to create Data protection regulation world-wide has, however, decided to create
exceptions for emergency services since the drawbacks of disclosing exceptions for emergency services since the drawbacks of disclosing
personal data in comparison to the benefit for the emergency caller personal data are outweighed by the benefit for the emergency caller.
are often towards the latter. Hence, the data protection rights of Hence, the data protection rights of individuals are commonly waived
individuals are often waived for emergency situations. There are, for emergency situations. There are, however, still various
however, still various countries that offer some degree of anonymity countries that offer some degree of anonymity for the caller towards
for the caller towards PSAP call takers. PSAP call takers.
The functionality defined in this document, however, far exceeds the The functionality defined in this document, however, far exceeds the
amount of information sharing found in the Plain old telephone system amount of information sharing found in the legacy POTS system. For
(POTS). For this reason there are additional privacy threats to this reason there are additional privacy threats to consider, which
consider, which are described in more detail in [RFC6973]. are described in more detail in [RFC6973].
Stored Data Compromise: First, there is an increased risk of stored Stored Data Compromise: There is an increased risk of stored data
data compromise since additional data is collected and stored in compromise since additional data is collected and stored in
databases. Without adequate measures to secure stored data from databases. Without adequate measures to secure stored data from
unauthorized or inappropriate access at access network operators, unauthorized or inappropriate access at access network providers,
service providers, end devices, as well as PSAPs individuals are service providers, end devices, as well as PSAPs, individuals are
exposed to potential financial, reputational, or physical harm. exposed to potential financial, reputational, or physical harm.
Misattribution: If the personal data collected and conveyed is Misattribution: If the personal data collected and conveyed is
incorrect or inaccurate then this may lead to misattribution. incorrect or inaccurate then this may lead to misattribution.
Misattribution occurs when data or communications related to one Misattribution occurs when data or communications related to one
individual are attributed to another. individual are attributed to another.
Identification: By the nature of the additional data and its Identification: By the nature of the additional data and its
capability to provide much richer information about the caller, capability to provide much richer information about the caller,
the call, and the location the calling party is identified in a the call, and the location, the calling party is identified in a
much better way. Some users may feel uncomfortable with this much better way. Some users may feel uncomfortable with this
degree of information sharing even in emergency services degree of information sharing even in emergency services
situations. situations.
Secondary Use: Furthermore, there is the risk of secondary use. Secondary Use: There is a risk of secondary use, which is the use of
Secondary use is the use of collected information about an collected information about an individual without the individual's
individual without the individual's consent for a purpose consent for a purpose different from that for which the
different from that for which the information was collected. The information was collected. The stated purpose of the additional
stated purpose of the additional data is for emergency services data is for emergency services purposes but theoretically the same
purposes but theoretically the same information could be used for information could be used for any other call as well.
any other call as well. Additionally, parties involved in the Additionally, parties involved in the emergency call may retain
emergency call may retain the obtained information and may re-use the obtained information and may re-use it for other, non-
it for other, non-emergency services purposes. emergency services purposes.
Disclosure: When the data defined in this document is not properly Disclosure: When the data defined in this document is not properly
security (while in transit with traditional communication security protected (while in transit with traditional communication
techniques, and while at rest using access control mechanisms) security techniques, and while stored using access control
there is the risk of disclosure, which is the revelation of mechanisms) there is the risk of disclosure, which is the
information about an individual that affects the way others judge revelation of private information about an individual.
the individual.
To mitigate these privacy risks the following countermeasures can be To mitigate these privacy risks the following countermeasures can be
taken. taken:
In regions where callers can elect to suppress certain personally In regions where callers can elect to suppress certain personally
identifying information, the network or PSAP functionality can identifying information, network or PSAP functionality can inspect
inspect privacy flags within the SIP headers to determine what privacy flags within the SIP headers to determine what information
information may be passed, stored, or displayed to comply with local may be passed, stored, or displayed to comply with local policy or
policy or law. RFC 3325 [RFC3325] defines the "id" priv-value token. law. RFC 3325 [RFC3325] defines the "id" priv-value token. The
The presence of this privacy type in a Privacy header field indicates presence of this privacy type in a Privacy header field indicates
that the user would like the network asserted identity to be kept that the user would like the network asserted identity to be kept
private with respect to SIP entities outside the trust domain with private with respect to SIP entities outside the trust domain with
which the user authenticated, including the PSAP. which the user authenticated, including the PSAP.
This document defines various data structures that constitutes This document defines various data structures that contain privacy-
personal data. Local regulations may govern what data must be sensitive data. For example, identifiers for the device (e.g.,
provided in emergency calls, but in general, the emergency call serial number, MAC address) or account/SIM (e.g., IMSI), contact
system is often aided by the kinds of information described in this information for the user, location of the caller. Local regulations
document. There is a tradeoff between the privacy considerations and may govern what data must be provided in emergency calls, but in
the utility of the data. For adequate protection this specification general, the emergency call system is aided by the information
requires all data exchanges to be secured via communication security described in this document. There is a tradeoff between the privacy
techniques (namely TLS) against eavesdropping and inception. considerations and the utility of the data. For protection, this
Furthermore, security safeguards are required to prevent unauthorized specification requires all retrieval of data passed by reference to
access to data at rest. Various security incidents over the last 10 be protected against eavesdropping and alteration via communication
years have shown data breaches are not not uncommon and are often security techniques (namely TLS). Furthermore, security safeguards
caused by lack of proper access control frameworks, software bugs are required to prevent unauthorized access to stored data. Various
(buffer overflows), or missing input parsing (SQL injection attacks). security incidents over at least the past few decades have shown that
The risks of data breaches is increased with the obligation for data breaches are not uncommon and are often caused by lack of proper
emergency services to retain emergency call related data for extended access control frameworks, software bugs (such as buffer overflows),
periods, e.g., several years are the norm. or missing input parsing (such as SQL injection attacks). The risks
of data breaches is increased with the obligation for emergency
services to retain emergency call related data for extended periods
(e.g., several years are the norm).
Finally, it is also worth to highlight the nature of the SIP Finally, it is also worth highlighting the nature of the SIP
communication architecture, which introduces additional complications communication architecture, which introduces additional complications
for privacy. Some forms of data can be sent by value in the SIP for privacy. Some forms of data can be sent by value in the SIP
signaling or by value (URL in SIP signaling). When data is sent by signaling or by reference (a URL in the SIP signaling). When data is
value, all intermediaries have access to the data. As such, these sent by value, all intermediaries have access to the data. As such,
intermediaries may also introduce additional privacy risk. these intermediaries may also introduce additional privacy risk.
Therefore, in situations where the conveyed information raises Therefore, in situations where the conveyed information is privacy-
privacy concerns and intermediaries are involved transmitting a sensitive and intermediaries are involved, transmitting by reference
reference is more appropriate (assuming proper access control might be appropriate, assuming the source of the data can operate a
policies are available for distinguishing the different entities sufficient dereferencing infrastructure and that proper access
dereferencing the reference). Without access control policies any control policies are available for distinguishing the different
party in possession of the reference is able to resolve the reference entities dereferencing the reference. Without access control
and to obtain the data, including intermediaries. policies any party in possession of the reference is able to resolve
the reference and to obtain the data, including intermediaries.
9. IANA Considerations 10. IANA Considerations
9.1. Registry creation 10.1. Registry creation
This document creates a new registry called 'Emergency Call This document creates a new registry called 'Emergency Call
Additional Data'. The following sub-registries are created for this Additional Data'. The following sub-registries are created for this
registry. registry.
9.1.1. Provider ID Series Registry 10.1.1. Provider ID Series Registry
This document creates a new sub-registry called 'Additional Call Data This document creates a new sub-registry called 'Additional Call Data
Provider ID Series'. As defined in [RFC5226], this registry operates Provider ID Series'. As defined in [RFC5226], this registry operates
under "Expert Review" rules. The expert should determine that the under "Expert Review" rules. The expert should determine that the
entity requesting a new value is a legitimate issuer of service entity requesting a new value is a legitimate issuer of service
provider IDs suitable for use in Additional Call Data. provider IDs suitable for use in Additional Call Data.
Private entities issuing and using internally-generated IDs are
encouraged to register and use a unique identifier. This guarantees
that IDs issued and used by the entity are globally unique and
distinguishable.
The content of this registry includes: The content of this registry includes:
Name: The identifier which will be used in the ProviderIDSeries Name: The identifier which will be used in the 'ProviderIDSeries'
element element.
Source: The full name of the organization issuing the identifiers Source: The full name of the organization issuing the identifiers.
URL: A URL to the organization for further information URL: A URL to the organization for further information.
The initial set of values is listed in Figure 21. The initial set of values is listed in Figure 21.
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
| Name | Source | URL | | Name | Source | URL |
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
| NENA | National Emergency | http://www.nena.org | | NENA | National Emergency | http://www.nena.org |
| | Number Association | | | | Number Association | |
| EENA | European Emergency | http://www.eena.org | | EENA | European Emergency | http://www.eena.org |
| | Number Association | | | | Number Association | |
| domain | (The ID is a fully- | (not applicable) |
| | qualified domain name) | |
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
Figure 21: Provider ID Series Registry. Figure 21: Provider ID Series Registry.
9.1.2. Service Environment Registry 10.1.2. Service Environment Registry
This document creates a new sub-registry called 'Additional Call This document creates a new sub-registry called 'Additional Call
Service Environment'. As defined in [RFC5226], this registry Service Environment'. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine operates under "Expert Review" rules. The expert should determine
that the entity requesting a new value is relevant for this service that the entity requesting a new value is relevant for this service
element. element, and that the new value is distinct from existing values, and
its use is unambiguous.
The content of this registry includes: The content of this registry includes:
Token: The value to be used in <ServiceEnvironment> element. Token: The value to be used in the <ServiceEnvironment> element.
Description: A short description of the token. Description: A short description of the value.
The initial set of values is listed in Figure 22. The initial set of values is listed in Figure 22.
+-----------+--------------------------+ +-----------+--------------------------+
| Token | Description | | Token | Description |
+-----------+--------------------------+ +-----------+--------------------------+
| Business | [[This RFC]] | | Business | Business service |
| Residence | [[This RFC]] | | Residence | Residential service |
| unknown | Type of service unknown |
| | (e.g., anonymous pre- |
| | paid service) |
+-----------+--------------------------+ +-----------+--------------------------+
Figure 22: Service Environment Registry. Figure 22: Service Environment Registry.
9.1.3. Service Provider Type Registry 10.1.3. Service Type Registry
This document creates a new sub-registry called 'Additional Call
Service Type'. As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the entity
requesting a new value is relevant for this service element and that
the requested value is clearly distinct from other values so that
there is no ambiguity as to when the value is to be used or which
value is to be used.
The content of this registry includes:
Name: The value to be used in the <ServiceType> element.
Description: A short description of the value.
The initial set of values is listed in Figure 3.
10.1.4. Service Mobility Registry
This document creates a new sub-registry called 'Additional Call
Service Mobility'. As defined in [RFC5226], this registry operates
under "Expert Review" rules. The expert should determine that the
entity requesting a new value is relevant for this service element
and that the requested value is clearly distinct from other values so
that there is no ambiguity as to when the value is to be used or
which value is to be used.
The content of this registry includes:
Token: The value used in the <ServiceMobility> element.
Description: A short description of the value.
The initial set of values is listed in Figure 23.
+-----------+----------------------------+
| Token | Description |
+-----------+----------------------------+
| Mobile | The device is able to |
| | move at any time |
| Fixed | The device is not expected |
| | to move unless the service |
| | is relocated |
| Nomadic | The device is not expected |
| | to change its point of |
| | attachment while on a call |
| Unknown | No information is known |
| | about the service mobility |
| | environment for the device |
+-----------+----------------------------+
Figure 23: Service Environment Registry.
10.1.5. Service Provider Type Registry
This document creates a new sub-registry called 'Service Provider This document creates a new sub-registry called 'Service Provider
Type'. As defined in [RFC5226], this registry operates under "Expert Type'. As defined in [RFC5226], this registry operates under "Expert
Review". The expert should determine that the proposed new value is Review". The expert should determine that the proposed new value is
distinct from existing values and appropriate for use in the distinct from existing values and appropriate for use in the
TypeOfServicerProvider element TypeOfServicerProvider element
The content of this registry includes: The content of this registry includes:
Name: The value to be used in TypeOfServiceProvider. Tokenproviderid: The value used in the 'TypeOfProvider' element.
Description: A short description of the type of service provider Description: A short description of the type of service provider.
The initial set of values is defined in Figure 1. The initial set of values is defined in Figure 1.
9.1.4. Service Delivered Registry 10.1.6. Service Delivered Registry
This document creates a new sub-registry called 'Service Delivered'. This document creates a new sub-registry called 'Service Delivered'.
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should consider whether the proposed service is rules. The expert should consider whether the proposed service is
unique from existing services and the definition of the service will unique from existing services and the definition of the service will
be clear to implementors and PSAPS/responders. be clear to implementors and PSAPs/responders.
The content of this registry includes: The content of this registry includes:
Name: Enumeration token of the service. Name: The value used in the 'ServiceType' element.
Description: Short description identifying the service. Description: Short description identifying the nature of the
service.
The initial set of values are defined in Figure 3. The initial set of values are defined in Figure 3.
9.1.5. Device Classification Registry 10.1.7. Device Classification Registry
This document creates a new sub-registry called 'Device This document creates a new sub-registry called 'Device
Classification'. As defined in [RFC5226], this registry operates Classification'. As defined in [RFC5226], this registry operates
under "Expert Review" rules. The expert should consider whether the under "Expert Review" rules. The expert should consider whether the
proposed class is unique from existing classes and the definition of proposed class is unique from existing classes and the definition of
the class will be clear to implementors and PSAPS/responders. the class will be clear to implementors and PSAPs/responders.
The content of this registry includes: The content of this registry includes:
Name: Enumeration token of the device classification. Token: Value used in the 'DeviceClassification' element.
Description: Short description identifying the device type. Description: Short description identifying the device type.
The initial set of values are defined in Figure 5. The initial set of values are defined in Figure 5.
9.1.6. Device ID Type Type Registry 10.1.8. Device ID Type Type Registry
This document creates a new sub-registry called 'Additional Call Data This document creates a new sub-registry called 'Additional Call Data
Device ID Type'. As defined in [RFC5226], this registry operates Device ID Type'. As defined in [RFC5226], this registry operates
under "Expert Review" rules. The expert should ascertain that the under "Expert Review" rules. The expert should ascertain that the
proposed type is well understood, and provides the information useful proposed type is well understood, and provides the information useful
to PSAPs and responders to uniquely identify a device. to PSAPs and responders to uniquely identify a device.
The content of this registry includes: The content of this registry includes:
Name: Enumeration token of the device id type. Token: The value to be placed in the 'TypeOfDeviceID' element.
Description: Short description identifying type of device id. Description: Short description identifying the type of the device
ID.
The initial set of values are defined in Figure 6. The initial set of values are defined in Figure 6.
9.1.7. Device/Service Data Type Registry 10.1.9. Device/Service Data Type Registry
This document creates a new sub-registry called 'Device/Service Data This document creates a new sub-registry called 'Device/Service Data
Type Registry'. As defined in [RFC5226], this registry operates Type Registry'. As defined in [RFC5226], this registry operates
under "Expert Review" and "Specification Required" rules. The expert under "Expert Review" and "Specification Required" rules. The expert
should ascertain that the proposed type is well understood, and should ascertain that the proposed type is well understood, and
provides information useful to PSAPs and responders. The provides information useful to PSAPs and responders. The
specification must contain a complete description of the data, and a specification must contain a complete description of the data, and a
precise format specification suitable to allow interoperable precise format specification suitable to allow interoperable
implementations. implementations.
The content of this registry includes: The content of this registry includes:
Name: Enumeration token of the data type. Token: The value to be placed in the <DeviceSpecificType> element.
Description: Short description identifying the the data. Description: Short description identifying the the data.
Specification: Citation for the specification of the data. Specification: Citation for the specification of the data.
The initial set of values are listed in Figure 23. The initial set of values are listed in Figure 24.
+---------+----------------------------------------+----------------+
| Token | Description | Specification |
+---------+----------------------------------------+----------------+
| IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 |
+---------+----------------------------------------+----------------+
Figure 23: Device/Service Data Type Registry. +----------+----------------------------------------+----------------+
| Token | Description | Specification |
+----------+----------------------------------------+----------------+
| IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006 |
+----------+----------------------------------------+----------------+
9.1.8. Additional Data Blocks Registry Figure 24: Device/Service Data Type Registry.
This document creates a new sub-registry called 'Additional Data 10.1.10. Emergency Call Data Types Registry
Blocks' in the purpose registry established by RFC 3261 [RFC3261]. This document creates a new sub-registry called 'Emergency Call Data
Types' in the 'purpose' registry established by RFC 3261 [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 and the proposed functionality does not obviously specification and the proposed functionality does not obviously
duplicate existing functionality. duplicate existing functionality.
The content of this registry includes: The content of this registry includes:
Name: Element Name of enclosing block. Token: The root of the data's MIME subtype (not including the
'EmergencyCallData' prefix and any suffix such as '+xml')
Reference: The document that describes the block Reference: The document that describes the data object
The initial set of values are listed in Figure 24. Note that the values from this registry are part of the
'EmergencyCallData' compound value; when used as a value of the
'purpose' parameter of the Call-Info header, the values listed in
this registry are prefixed by 'EmergencyCallData.' per the the
'EmergencyCallData' registation Section 10.2.
+--------------+------------+ The initial set of values are listed in Figure 25.
| Token | Reference |
+--------------+------------+
| ProviderInfo | [This RFC] |
| ServiceInfo | [This RFC] |
| DeviceInfo | [This RFC] |
| Subscriber | [This RFC] |
| Comment | [This RFC] |
+--------------+------------+
Figure 24: Additional Data Blocks Registry. +----------------+------------+
| Token | Reference |
+----------------+------------+
| ProviderInfo | [This RFC] |
| ServiceInfo | [This RFC] |
| DeviceInfo | [This RFC] |
| SubscriberInfo | [This RFC] |
| Comment | [This RFC] |
+----------------+------------+
9.2. 'EmergencyCallData' Purpose Parameter Value Figure 25: Additional Data Blocks Registry.
10.2. 'EmergencyCallData' Purpose Parameter Value
This document defines the 'EmergencyCallData' value for the "purpose" This document defines the 'EmergencyCallData' value for the "purpose"
parameter of the Call-Info header field. The Call-Info header and parameter of the Call-Info header field. The Call-Info header and
the corresponding registry for the 'purpose' parameter was the corresponding registry for the 'purpose' parameter was
established with RFC 3261 [RFC3261]. established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData'
is a compound value; when used as a value of the 'purpose' parameter
of the Call-Info header, 'EmergencyCallData' is immediately followed
by a dot ('.') and a value from the 'Emergency Call Data Types'
registry Section 10.1.10.
Header Parameter New Header Parameter New
Field Name Value Reference Field Name Value Reference
---------- --------- ----------------- --------- ---------- --------- ----------------- ---------
Call-Info purpose EmergencyCallData [This RFC] Call-Info purpose EmergencyCallData [This RFC]
9.3. URN Sub-Namespace Registration for provided-by Registry Entry 10.3. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in Section 9.5.1 in This section registers the namespace specified in Section 10.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.
The schema for the provided-by schema used by this document is The schema for the provided-by element used by this document is
specified in Section 6.6. specified in Section 7.6.
9.4. MIME Registrations 10.4. MIME Registrations
9.4.1. MIME Content-type Registration for 'application/ 10.4.1. MIME Content-type Registration for 'application/
EmergencyCallData.ProviderInfo+xml' EmergencyCallData.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 6838 [RFC6838] and guidelines in
RFC 3023 [RFC3023]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.ProviderInfo+xml MIME subtype name: EmergencyCallData.ProviderInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of
enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Optional parameters: charset (indicates the character encoding of
characters, depending on the character encoding used. See the contents)
Section 3.2 of RFC 3023 [RFC3023].
Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
the data provider information, which is a sub-category of the data provider information, which is a sub-category of
additional data about an emergency call. Since this data contains additional data about an emergency call. Since this data may
personal information appropriate precautions have to be taken to contain personal information, appropriate precautions might be
limit unauthorized access, inappropriate disclosure to third needed to limit unauthorized access, inappropriate disclosure, and
parties, and eavesdropping of this information. Please refer to eavesdropping of personal information. Please refer to Section 8
Section 7 and Section 8 for more information. and Section 9 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: Magic Number: None File Extension: .xml Additional information:
Macintosh file type code: 'TEXT'
Magic Number: None
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>
9.4.2. MIME Content-type Registration for 'application/ 10.4.2. MIME Content-type Registration for 'application/
EmergencyCallData.ServiceInfo+xml' EmergencyCallData.ServiceInfo+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 6838 [RFC6838] and guidelines in
RFC 3023 [RFC3023]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.ServiceInfo+xml MIME subtype name: EmergencyCallData.ServiceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of
enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Optional parameters: charset (indicates the character encoding of
characters, depending on the character encoding used. See the contents)
Section 3.2 of RFC 3023 [RFC3023].
Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
the service information, which is a sub-category of additional the service information, which is a sub-category of additional
data about an emergency call. Since this data contains personal data about an emergency call. Since this data may contain
information appropriate precautions have to be taken to limit personal information, appropriate precautions may be needed to
unauthorized access, inappropriate disclosure to third parties, limit unauthorized access, inappropriate disclosure, and
and eavesdropping of this information. Please refer to Section 7 eavesdropping of personal information. Please refer to Section 8
and Section 8 for more information. and Section 9 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: Magic Number: None File Extension: .xml Additional information:
Macintosh file type code: 'TEXT'
Magic Number: None
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>
9.4.3. MIME Content-type Registration for 'application/ 10.4.3. MIME Content-type Registration for 'application/
EmergencyCallData.DeviceInfo+xml' EmergencyCallData.DeviceInfo+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 6838 [RFC6838] and guidelines in
RFC 3023 [RFC3023]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.DeviceInfo+xml MIME subtype name: EmergencyCallData.DeviceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of
enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Optional parameters: charset (indicates the character encoding of
characters, depending on the character encoding used. See the contents)
Section 3.2 of RFC 3023 [RFC3023]. Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
the device information information, which is a sub-category of device information, which is a sub-category of additional data
additional data about an emergency call. Since this data contains about an emergency call. Since this data contains personal
personal information appropriate precautions have to be taken to information, appropriate precautions need to be taken to limit
limit unauthorized access, inappropriate disclosure to third unauthorized access, inappropriate disclosure to third parties,
parties, and eavesdropping of this information. Please refer to and eavesdropping of this information. Please refer to Section 8
Section 7 and Section 8 for more information. and Section 9 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: Magic Number: None File Extension: .xml Additional information:
Macintosh file type code: 'TEXT'
Magic Number: None
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>
9.4.4. MIME Content-type Registration for 'application/ 10.4.4. MIME Content-type Registration for 'application/
EmergencyCallData.SubscriberInfo+xml' EmergencyCallData.SubscriberInfo+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 6838 [RFC6838] and guidelines in
RFC 3023 [RFC3023]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.SubscriberInfo+xml MIME subtype name: EmergencyCallData.SubscriberInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset (indicates the character encoding of
enclosed XML. the contents)
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding. See Section 3.2
Section 3.2 of RFC 3023 [RFC3023]. of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
owner/subscriber information, which is a sub-category of owner/subscriber information, which is a sub-category of
additional data about an emergency call. Since this data contains additional data about an emergency call. Since this data contains
personal information appropriate precautions have to be taken to personal information, appropriate precautions need to be taken to
limit unauthorized access, inappropriate disclosure to third limit unauthorized access, inappropriate disclosure to third
parties, and eavesdropping of this information. Please refer to parties, and eavesdropping of this information. Please refer to
Section 7 and Section 8 for more information. Section 8 and Section 9 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: Magic Number: None File Extension: .xml Additional information:
Macintosh file type code: 'TEXT'
Magic Number: None
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>
9.4.5. MIME Content-type Registration for 'application/ 10.4.5. MIME Content-type Registration for 'application/
EmergencyCallData.Comment+xml' EmergencyCallData.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 6838 [RFC6838] and guidelines in
RFC 3023 [RFC3023]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.Comment+xml MIME subtype name: EmergencyCallData.Comment+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of
enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Optional parameters: charset (indicates the character encoding of
characters, depending on the character encoding used. See the contents)
Section 3.2 of RFC 3023 [RFC3023].
Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry a Security considerations: This content type is designed to carry a
comment, which is a sub-category of additional data about an comment, which is a sub-category of additional data about an
emergency call. This data may contain personal information. emergency call. This data may contain personal information.
Appropriate precautions may have to be taken to limit unauthorized Appropriate precautions may be needed to limit unauthorized
access, inappropriate disclosure to third parties, and access, inappropriate disclosure to third parties, and
eavesdropping of this information. Please refer to Section 7 and eavesdropping of this information. Please refer to Section 8 and
Section 8 for more information. Section 9 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: Magic Number: None File Extension: .xml Additional information:
Macintosh file type code: 'TEXT'
Magic Number: None
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>
9.5. URN Sub-Namespace Registration 10.5. URN Sub-Namespace Registration
9.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData
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:EmergencyCallData URI: urn:ietf:params:xml:ns:EmergencyCallData
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 66, line 22 skipping to change at page 71, line 36
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
9.5.2. Registration for 10.5.2. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo
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:EmergencyCallData:ProviderInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 67, line 7 skipping to change at page 72, line 22
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
9.5.3. Registration for 10.5.3. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo
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:EmergencyCallData:ServiceInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 67, line 39 skipping to change at page 73, line 8
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
9.5.4. Registration for 10.5.4. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo
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:EmergencyCallData:DeviceInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
skipping to change at page 68, line 26 skipping to change at page 73, line 40
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
9.5.5. Registration for 10.5.5. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo
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:EmergencyCallData:SubscriberInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo
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">
skipping to change at page 69, line 12 skipping to change at page 74, line 28
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
9.5.6. Registration for 10.5.6. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment urn:ietf:params:xml:ns:EmergencyCallData: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:EmergencyCallData:Comment URI: urn:ietf:params:xml:ns:EmergencyCallData: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:
skipping to change at page 69, line 33 skipping to change at page 75, line 4
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
9.6. Schema Registrations 10.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:emergencycalldata:ProviderInfo URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo
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 15. XML: The XML schema can be found in Figure 15.
URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo
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).
skipping to change at page 70, line 28 skipping to change at page 75, line 46
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 17. XML: The XML schema can be found in Figure 17.
URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo
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 6.4. XML: The XML schema can be found in Section 7.4.
URI: urn:ietf:params:xml:schema:emergencycalldata:comment URI: urn:ietf:params:xml:schema:emergencycalldata: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 6.5. XML: The XML schema can be found in Section 7.5.
9.7. VCard Parameter Value Registration 10.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 Conformance: This value can be used with the "TYPE" parameter
applied on the "TEL" property. applied on the "TEL" property.
Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90 Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90
00 00
10. Acknowledgments 11. 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 many NENA participants, including Delaine comments provided by many NENA participants, including Delaine
Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James
Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra,
and Robert (Bob) Sherry. and Robert (Bob) Sherry.
We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin
Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review
comments. Guy Caron deserves special mention for his detailed review
comments. comments.
11. References 12. References
11.1. Normative References
[RFC0822] Crocker, D., "Standard for the format of ARPA Internet 12.1. Normative References
text messages", STD 11, RFC 822, August 1982.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. Locators", RFC 2392, August 1998.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001.
[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
F., Watson, M., and M. Zonoun, "MIME media types for ISUP F., Watson, M., and M. Zonoun, "MIME media types for ISUP
and QSIG Objects", RFC 3204, December 2001. and QSIG Objects", RFC 3204, December 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. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
skipping to change at page 72, line 19 skipping to change at page 77, line 28
[RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail [RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail
Extensions (MIME) Parameter", RFC 3459, January 2003. Extensions (MIME) Parameter", RFC 3459, January 2003.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", 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.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008.
[RFC5621] Camarillo, G., "Message Body Handling in the Session [RFC5621] Camarillo, G., "Message Body Handling in the Session
Initiation Protocol (SIP)", RFC 5621, September 2009. Initiation Protocol (SIP)", RFC 5621, September 2009.
[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", RFC
6351, August 2011. 6351, August 2011.
11.2. Informational References [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013.
[I-D.gellens-negotiating-human-language] [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
Randy, R., "Negotiating Human Language Using SDP", draft- July 2014.
gellens-negotiating-human-language-02 (work in progress),
February 2013. 12.2. Informational References
[I-D.gellens-mmusic-negotiating-human-language]
Randy, R., "Negotiating Human Language in Real-Time
Communications", draft-gellens-mmusic-negotiating-human-
language-02 (work in progress), February 2014.
[I-D.ietf-ecrit-psap-callback] [I-D.ietf-ecrit-psap-callback]
Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback", Patel, "Public Safety Answering Point (PSAP) Callback",
draft-ietf-ecrit-psap-callback-13 (work in progress), draft-ietf-ecrit-psap-callback-13 (work in progress),
October 2013. October 2013.
[I-D.ietf-geopriv-relative-location]
Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.
Thomson, "Relative Location Representation", draft-ietf-
geopriv-relative-location-08 (work in progress), September
2013.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC
3966, December 2004.
[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, January 2008. RFC 5012, January 2008.
[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
Format for Presence Information Data Format Location Format for Presence Information Data Format Location
Object (PIDF-LO)", RFC 5139, February 2008. Object (PIDF-LO)", RFC 5139, February 2008.
[RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.
Tschofenig, "LoST: A Location-to-Service Translation
Protocol", RFC 5222, August 2008.
[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV [RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV
Presence Information Data Format Location Object (PIDF-LO) Presence Information Data Format Location Object (PIDF-LO)
Usage Clarification, Considerations, and Recommendations", Usage Clarification, Considerations, and Recommendations",
RFC 5491, March 2009. RFC 5491, March 2009.
[RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and
Framework", RFC 5582, September 2009.
[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M. [RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.
Thomson, "Dynamic Extensions to the Presence Information Thomson, "Dynamic Extensions to the Presence Information
Data Format Location Object (PIDF-LO)", RFC 5962, Data Format Location Object (PIDF-LO)", RFC 5962,
September 2010. September 2010.
[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC [RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC
5985, September 2010. 5985, September 2010.
[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
skipping to change at page 74, line 5 skipping to change at page 79, line 16
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013. BCP 181, RFC 6881, March 2013.
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., [RFC6973] 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", RFC 6973, July Considerations for Internet Protocols", RFC 6973, July
2013. 2013.
[RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.
Thomson, "Relative Location Representation", RFC 7035,
October 2013.
[RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, April 2014.
Appendix A. XML Schema for vCard/xCard Appendix A. XML Schema for vCard/xCard
This section contains the vCard/xCard XML schema version of the Relax This section contains the vCard/xCard XML schema version of the Relax
NG schema defined in RFC 6351 [RFC6351] for simplified use with the NG schema defined in RFC 6351 [RFC6351] for simplified use with the
XML schemas defined in this document. The schema in RFC 6351 XML schemas defined in this document. The schema in RFC 6351
[RFC6351] is the normative source and this section is informative [RFC6351] is the normative source and this section is informative
only. only.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
 End of changes. 285 change blocks. 
653 lines changed or deleted 838 lines changed or added

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