draft-ietf-ecrit-additional-data-34.txt   draft-ietf-ecrit-additional-data-35.txt 
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Qualcomm Technologies, Inc. Internet-Draft Qualcomm Technologies, Inc.
Intended status: Standards Track B. Rosen Updates: 6443, 6881 (if approved) B. Rosen
Expires: February 27, 2016 NeuStar Intended status: Standards Track NeuStar
H. Tschofenig Expires: March 19, 2016 H. Tschofenig
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
J. Winterbottom J. Winterbottom
August 26, 2015 September 16, 2015
Additional Data Related to an Emergency Call Additional Data Related to an Emergency Call
draft-ietf-ecrit-additional-data-34.txt draft-ietf-ecrit-additional-data-35.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 originating device, the access network provider to which (PSAP), the originating device, the access network provider to which
the device is connected, and all service providers in the path of the the device is connected, and all service providers in the path of the
call have information about the call, the caller or the location call have information about the call, the caller or the location
which is helpful for the PSAP to have in handling the emergency. which is helpful for the PSAP to have in handling the emergency.
This document describes data structures and mechanisms to convey such This document describes data structures and mechanisms to convey such
data to the PSAP. The intent is that every emergency call carry the data to the PSAP. The intent is that every emergency call carry as
information described here using the mechanisms described here. much as possible of the information described here using the
mechanisms described here.
The mechanisms permit the data to be conveyed by reference (as an The mechanisms permit the data to be conveyed by reference (as an
external resource) or by value (within the body of a SIP message or a external resource) or by value (within the body of a SIP message or a
location object). This follows the tradition of prior emergency location object). This follows the tradition of prior emergency
services standardization work where data can be conveyed by value services standardization work where data can be conveyed by value
within the call signaling (i.e., in the body of the SIP message) or within the call signaling (i.e., in the body of the SIP message) or
by reference. by reference.
Status of This Memo Status of This Memo
skipping to change at page 2, line 4 skipping to change at page 2, line 6
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 February 27, 2016.
This Internet-Draft will expire on March 19, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
skipping to change at page 2, line 29 skipping to change at page 2, line 32
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. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7 3. Document Scope . . . . . . . . . . . . . . . . . . . . . . . 7
4. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7 4. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Data Provider Information . . . . . . . . . . . . . . . . 9 4.1. Data Provider Information . . . . . . . . . . . . . . . . 9
4.1.1. Data Provider String . . . . . . . . . . . . . . . . 9 4.1.1. Data Provider String . . . . . . . . . . . . . . . . 9
4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9 4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 10
4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 10 4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 10
4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 11 4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 11
4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 12 4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 12
4.1.6. Data Provider Languages(s) Supported . . . . . . . . 13 4.1.6. Data Provider Languages(s) Supported . . . . . . . . 13
4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 13 4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 14
4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 14 4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 14
4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 15 4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 15
4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 15 4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 15
4.2. Service Information . . . . . . . . . . . . . . . . . . . 17 4.2. Service Information . . . . . . . . . . . . . . . . . . . 17
4.2.1. Service Environment . . . . . . . . . . . . . . . . . 17 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 18
4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 18 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 19
4.2.3. Service Mobility Environment . . . . . . . . . . . . 20 4.2.3. Service Mobility Environment . . . . . . . . . . . . 20
4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 21 4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 21
4.3. Device Information . . . . . . . . . . . . . . . . . . . 22 4.3. Device Information . . . . . . . . . . . . . . . . . . . 22
4.3.1. Device Classification . . . . . . . . . . . . . . . . 22 4.3.1. Device Classification . . . . . . . . . . . . . . . . 22
4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 23 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 23
4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 24 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 24
4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 24 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 24
4.3.5. Device/Service-Specific Additional Data Structure . . 25 4.3.5. Device/Service-Specific Additional Data Structure . . 25
4.3.6. Device/Service-Specific Additional Data Structure 4.3.6. Device/Service-Specific Additional Data Structure
Type . . . . . . . . . . . . . . . . . . . . . . . . 26 Type . . . . . . . . . . . . . . . . . . . . . . . . 26
4.3.7. Issues with getting new types of data into use . . . 26 4.3.7. EmergencyCallData.DeviceInfo Example . . . . . . . . 26
4.3.8. Choosing between defining a new type of block or new 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 27
type of device/service specific additional data . . . 27 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 27
4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 28 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 28
4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 28 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 28
4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 28 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 29 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 31
4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 30 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 31
4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 32 5. Issues with getting new types of data into use . . . . . . . 32
4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 32 5.1. Choosing between defining a new type of block or new type
4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 32 of device/service-specific additional data . . . . . . . 32
5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 33 6. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 33
5.1. Transmitting Blocks using Call-Info . . . . . . . . . . . 34 6.1. Transmitting Blocks using Call-Info . . . . . . . . . . . 35
5.2. Transmitting Blocks by Reference using the <provided-by> 6.2. Transmitting Blocks by Reference using the <provided-by>
Element . . . . . . . . . . . . . . . . . . . . . . . . . 36 Element . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.3. Transmitting Blocks by Value using the <provided-by> 6.3. Transmitting Blocks by Value using the <provided-by>
Element . . . . . . . . . . . . . . . . . . . . . . . . . 37 Element . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.4. The Content-Disposition Parameter . . . . . . . . . . . . 38 6.4. The Content-Disposition Parameter . . . . . . . . . . . . 39
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 40 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 52 8. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 52 8.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 53
7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 54 8.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 55
7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 55 8.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 56
7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 57 8.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 58
7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 58 8.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 59
7.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 59 8.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 60
8. Security Considerations . . . . . . . . . . . . . . . . . . . 61 9. Security Considerations . . . . . . . . . . . . . . . . . . . 62
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 63 10. Privacy Considerations . . . . . . . . . . . . . . . . . . . 64
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 66 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 67
10.1. Registry creation . . . . . . . . . . . . . . . . . . . 66 11.1. Registry creation . . . . . . . . . . . . . . . . . . . 67
10.1.1. Provider ID Series Registry . . . . . . . . . . . . 66 11.1.1. Provider ID Series Registry . . . . . . . . . . . . 67
10.1.2. Service Environment Registry . . . . . . . . . . . . 66 11.1.2. Service Environment Registry . . . . . . . . . . . . 67
10.1.3. Service Type Registry . . . . . . . . . . . . . . . 67 11.1.3. Service Type Registry . . . . . . . . . . . . . . . 68
10.1.4. Service Mobility Registry . . . . . . . . . . . . . 67 11.1.4. Service Mobility Registry . . . . . . . . . . . . . 68
10.1.5. Service Provider Type Registry . . . . . . . . . . . 68 11.1.5. Service Provider Type Registry . . . . . . . . . . . 69
10.1.6. Device Classification Registry . . . . . . . . . . . 68 11.1.6. Device Classification Registry . . . . . . . . . . . 69
10.1.7. Device ID Type Type Registry . . . . . . . . . . . . 68 11.1.7. Device ID Type Type Registry . . . . . . . . . . . . 69
10.1.8. Device/Service Data Type Registry . . . . . . . . . 69 11.1.8. Device/Service Data Type Registry . . . . . . . . . 70
10.1.9. Emergency Call Data Types Registry . . . . . . . . . 69 11.1.9. Emergency Call Data Types Registry . . . . . . . . . 70
10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 70 11.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 71
10.3. URN Sub-Namespace Registration for <provided-by> 11.3. URN Sub-Namespace Registration for <provided-by>
Registry Entry . . . . . . . . . . . . . . . . . . . . . 71 Registry Entry . . . . . . . . . . . . . . . . . . . . . 72
10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 71 11.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 72
10.4.1. MIME Content-type Registration for 11.4.1. MIME Content-type Registration for
'application/EmergencyCallData.ProviderInfo+xml' . . 71 'application/EmergencyCallData.ProviderInfo+xml' . . 72
10.4.2. MIME Content-type Registration for 11.4.2. MIME Content-type Registration for
'application/EmergencyCallData.ServiceInfo+xml' . . 72 'application/EmergencyCallData.ServiceInfo+xml' . . 73
10.4.3. MIME Content-type Registration for 11.4.3. MIME Content-type Registration for
'application/EmergencyCallData.DeviceInfo+xml' . . . 73 'application/EmergencyCallData.DeviceInfo+xml' . . . 74
11.4.4. MIME Content-type Registration for
10.4.4. MIME Content-type Registration for 'application/EmergencyCallData.SubscriberInfo+xml' . 75
'application/EmergencyCallData.SubscriberInfo+xml' . 74 11.4.5. MIME Content-type Registration for
10.4.5. MIME Content-type Registration for 'application/EmergencyCallData.Comment+xml' . . . . 76
'application/EmergencyCallData.Comment+xml' . . . . 75 11.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 77
10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 76 11.5.1. Registration for
10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 77
urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 76 11.5.2. Registration for
10.5.2. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf
o . . . . . . . . . . . . . . . . . . . . . . . . . 77 o . . . . . . . . . . . . . . . . . . . . . . . . . 78
10.5.3. Registration for 11.5.3. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 78 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 79
10.5.4. Registration for 11.5.4. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 79 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 80
10.5.5. Registration for 11.5.5. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI
nfo . . . . . . . . . . . . . . . . . . . . . . . . 80 nfo . . . . . . . . . . . . . . . . . . . . . . . . 81
10.5.6. Registration for 11.5.6. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 81 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 82
10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 82 11.6. Schema Registrations . . . . . . . . . . . . . . . . . . 83
10.7. VCard Parameter Value Registration . . . . . . . . . . . 83 11.7. VCard Parameter Value Registration . . . . . . . . . . . 84
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 83 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 84
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 84 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 85
12.1. Normative References . . . . . . . . . . . . . . . . . . 84 13.1. Normative References . . . . . . . . . . . . . . . . . . 85
12.2. Informational References . . . . . . . . . . . . . . . . 85 13.2. Informational References . . . . . . . . . . . . . . . . 86
12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 86 13.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 87 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 89
Appendix B. XML Validation . . . . . . . . . . . . . . . . . . . 109 Appendix B. XML Validation . . . . . . . . . . . . . . . . . . . 111
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 109 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 111
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 request for identity, the multimedia capabilities of the device, the request for
emergency services, location information, and meta-data about the emergency services, location information, and meta-data about the
sources of the data. In addition, the device, the access network sources of the data. In addition, the device, the access network
provider, and any service provider in the call path has even more provider, and any service provider in the call path has even more
information that is useful for a PSAP when handling an emergency. information that is useful for a PSAP when handling an emergency.
This document extends the basic set of data communicated with an IP- This document extends the basic set of data communicated with an IP-
based emergency call, as described in [RFC6443] and [RFC6881], in based emergency call, as described in [RFC6443] and [RFC6881], in
order to carry additional data which is useful to an entity or call order to carry additional data which is useful to an entity or call
taker handling the call. This data is "additional" to the basic taker handling the call. This data is "additional" to the basic
information found in the emergency call signaling used. The intent information found in the emergency call signaling used. The intent
is that every emergency call carry the information described here is that every emergency call carry as much as possible of the
using the mechanisms described here. information described here using the mechanisms described here.
This document defines three categories of this additional data that This document defines three categories of this additional data that
can be transmitted with an emergency call: can 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 [RFC7035] (for relative geodetic location information), and [RFC7035] (for relative
location). This primary location data identifies the location or location). This primary location data identifies the location or
estimated location of the caller. However, there may exist estimated location of the caller. However, there might exist
additional, secondary data which is specific to the location, such additional, secondary data which is specific to the location, such
as floor plans, tenant and building owner contact data, heating, as floor 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 can 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, the access network to which known by the device making the call, the access network to which
the device is connected, and service providers along the path of the device is connected, and service providers along the path of
the call. This information includes service provider contact the call. This information includes service provider contact
information, subscriber identity and contact information, the type information, subscriber identity and contact information, the type
of service the service provider and the access network provide, of service the service provider and the access network provide,
what type of device is being used, etc. Some data is broadly what type of device is being used, etc. Some data is broadly
applicable, while other data is dependent on the type of device or applicable, while other data is dependent on the type of device or
service. For example, a medical monitoring device may have sensor service. For example, a medical monitoring device might have
data. The data structures defined in this document (Data Provider sensor data. The data structures defined in this document (Data
Information, Device Information, and Owner/Subscriber Information) Provider Information, Device Information, and Owner/Subscriber
all fall into the category of "Data Associated with a Call". Note Information) all fall into the category of "Data Associated with a
that the Owner/Subscriber Information includes the subscriber's Call". Note that the Owner/Subscriber Information includes the
vCard, which may contain personal information such as birthday, subscriber's vCard, which might contain personal information such
anniversary, etc., but the data block itself is still considered as birthday, anniversary, etc., but the data block itself is still
to be about the call, not the caller. considered to be about the call, not the caller.
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 can 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
minimizes the work needed to carry data in the other categories. minimizes the work needed to carry data in the other categories.
Other specifications may make use of the facilities provided here. Other specifications can make use of the facilities provided here.
For interoperability, there needs to be a common way for the For interoperability, there needs to be a common way for the
information conveyed to a PSAP to be encoded and identified. information conveyed to a PSAP to be encoded and identified.
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 4, 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 5. Section 6.
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) media type
identification within transport such as SIP and HTTPS. The set of for identification within transport such as SIP and HTTPS. The set
blocks is extensible. Registries are defined to identify the block of blocks is extensible. Registries are defined to identify the
types that may be used and to allow blocks to be included in block types that can be used and to allow blocks to be included in
emergency call signaling. emergency call signaling.
Much of the information supplied by service providers and devices is Much of the information supplied by service providers and devices is
private and confidential; service providers and devices generally go private and confidential; service providers and devices generally go
to lengths to protect this information; disclosing it in the context 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 an emergency call is a trade-off to protect the greater interest
of the customer in an emergency. of the customer in an emergency.
2. Terminology 2. Terminology
skipping to change at page 6, line 50 skipping to change at page 7, line 6
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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 might be provided by a
company. An Emergency Services Provider is an entity directly single company. An Emergency Services Provider is an entity directly
involved in providing emergency services. This includes PSAPs, involved in providing emergency services. This includes PSAPs,
dispatch, police, fire, emergency medical, other responders, and dispatch, police, fire, emergency medical, other responders, and
other similar agencies. other similar agencies.
Within each data block definition (see Section 4), 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
skipping to change at page 7, line 33 skipping to change at page 7, line 37
the information elements defined in the vCard specification has been the information elements defined in the vCard specification has been
defined and the name of that specification is xCard [RFC6351]. Since defined and the name of that specification is xCard [RFC6351]. Since
the term vCard is more familiar to most readers, we use the terms the term vCard is more familiar to most readers, we use the terms
xCard and vCard interchangeably. xCard and vCard interchangeably.
3. Document Scope 3. Document Scope
The scope of this document is explicitly limited to emergency calls. The scope of this document is explicitly limited to emergency calls.
The data structures defined here are not appropriate to be conveyed The data structures defined here are not appropriate to be conveyed
with non-emergency calls because they carry sensitive and private with non-emergency calls because they carry sensitive and private
data. However, in certain private-use situations where the endpoints data. However, in certain private-use situations (such as
have a preexisting relationship and privacy issues are addressed communications between a telematics or other service provider and
within the relationship or do not apply because of it, the mechanisms dedicated equipment such as in a vehicle) where the endpoints have a
and data structures defined here MAY be used. preexisting relationship and privacy issues are addressed within the
relationship, the mechanisms and data structures defined here can be
used.
4. Data Structures 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 media type, and the
encoding. The five data structures are: XML 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 4.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 4.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
skipping to change at page 8, line 27 skipping to change at page 8, line 34
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 (In certain situations, the same provider might process a call more
and properties (specifically, world-uniqueness) as the value of the than once, likely in different roles, and in such cases, each time it
"Message-ID" message body header field specified in RFC 5322 processes the call, it adds a new set of bocks with a new
[RFC5322] except that the <DataProviderReference> element is not <DataProviderReference> value.) The value of the
enclosed in brackets (the "<" and ">" symbols are omitted). In other <DataProviderReference> element has the same syntax and properties
words, the value of a <DataProviderReference> element is (specifically, world-uniqueness) as the value of the "Message-ID"
syntactically a msg-id as specified in RFC 5322 [RFC5322]. message body header field specified in RFC 5322 [RFC5322] except that
the <DataProviderReference> element is not enclosed in brackets (the
"<" and ">" symbols are omitted). In other words, the value of a
<DataProviderReference> element is syntactically a msg-id as
specified in RFC 5322 [RFC5322].
Each block is added to the Additional Data Blocks Registry created in Each block is added to the Additional Data Blocks Registry created in
Section 10.1.9 and categorized as providing data about the caller. Section 11.1.9 and categorized as providing data about the caller.
New blocks added to the registry in the future MUST also be New blocks added to the registry in the future MUST also be
categorized per the description of the three categories in Section 1. categorized per the description of the three categories in Section 1.
See Section 4.3.7 and Section 4.3.8 for additional considerations See Section 5 and Section 5.1 for additional considerations when
when adding new blocks or types of data. adding new blocks or types of data.
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 (that is, a primary or main contact
emergency responders who are called to a large enterprise. This number, typically of an enterprise, as opposed to a direct dial
document adds a new property value to the "tel" property of the TYPE number of an individual). These numbers are useful to emergency
parameter called "main". It can be used in any xCard in additional responders who are called to a large enterprise. This document adds
data. a new parameter value called "main-number" to the "TYPE" parameter of
the "tel" property. It can be used in any xCard in an emergency call
additional data block.
4.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, and the device. It path of the call, or the access network provider, and the device. It
includes identification and contact information. This block MUST be includes identification and contact information. This block MUST be
supplied by any entity that provides any other block; it SHOULD be supplied by any entity that provides any other block; it SHOULD be
supplied by every service provider in the call path and by the access supplied by every service provider in the call path and by the access
network provider if those entities do not add any other blocks. network provider if those entities do not add any other blocks.
Devices SHOULD use this block to provide identifying information. Devices SHOULD use this block to provide identifying information.
The MIME subtype is "application/EmergencyCallData.ProviderInfo+xml". The MIME media type is "application/
An access network provider SHOULD provide this block either by value EmergencyCallData.ProviderInfo+xml". An access network provider
or by reference in the <provided-by> element of a PIDF-LO SHOULD provide this block either by value or by reference in the
<provided-by> element of a PIDF-LO
4.1.1. Data Provider String 4.1.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Conditional. Optional for blocks supplied by the originating Use: Conditional. Optional for blocks supplied by the originating
device, mandatory otherwise. device, mandatory otherwise.
XML Element: <DataProviderString> XML Element: <DataProviderString>
skipping to change at page 10, line 35 skipping to change at page 11, line 4
circumstances and for routine logging. circumstances and for routine logging.
4.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. Optional for blocks supplied by the originating Use: Conditional. Optional for blocks supplied by the originating
device, mandatory otherwise. device, mandatory otherwise.
XML Element: <ProviderIDSeries> XML Element: <ProviderIDSeries>
Description: Identifies the issuer of the <ProviderID>. The Description: Identifies the issuer of the <ProviderID>. The
Provider ID Series Registry created in Section 10.1.1 initially Provider ID Series Registry created in Section 11.1.1 initially
contains the entries shown in Figure 1. contains the entries shown in Figure 1.
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 The combination of ProviderIDSeries and ProviderID MUST be
globally unique. 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
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
| 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) | | domain | (The ID is a fully- | (not applicable) |
| | qualified domain name) | | | | qualified domain name) | |
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
skipping to change at page 11, line 27 skipping to change at page 11, line 38
4.1.4. Type of Data Provider 4.1.4. Type of Data Provider
Data Element: Type of Data Provider Data Element: Type of Data Provider
Use: Required. Use: Required.
XML Element: <TypeOfProvider> XML Element: <TypeOfProvider>
Description: Identifies the type of data provider supplying the Description: Identifies the type of data provider supplying the
data. The registry containing all valid values is created in data. The registry containing all valid values is created in
Section 10.1.5 and the initial set of values is shown in Figure 2. Section 11.1.5 and the initial set of values is shown in Figure 2.
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 can be helpful when
deciding whom to contact when further information is needed. deciding whom to contact when further information is needed.
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Token | Description | | Token | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Client | Originating client/device | |Client | Originating client/device |
|Access Network Provider | Access network service provider | |Access Network Provider | Access network service provider |
|Telecom Provider | Telecom service provider (including| |Telecom Provider | Telecom service provider (including|
| | over-the-top VoIP services) | | | native and over-the-top VoIP |
| | services) |
|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 | |Language Translation Provider | A spoken language translation |
| | service | | | service |
|Emergency Service Provider | An emergency service provider | |Emergency Service Provider | An emergency service provider |
| | conveying information to another| | | conveying information to another|
| | 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 |
skipping to change at page 12, line 48 skipping to change at page 12, line 49
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. When provided by a device, this MUST be the contact call. When provided by a device, this MUST be the contact
information of the user or owner of the device. (Ideally, this is information of the user or owner of the device. (Ideally, this is
the contact information of the device user, but when the owner and the contact information of the device user, but when the owner and
user are separate (e.g., the device owner is an organization), user are separate (e.g., the device owner is an organization),
this MAY be the contact information of the owner.) The Data this MAY be the contact information of the owner.) The Data
Provider Contact URI SHOULD be a TEL URI [RFC3966] in E.164 format Provider Contact URI SHOULD be a TEL URI [RFC3966] in E.164 format
fully specified with country code. If a TEL URI is not available, fully specified with country code. If a TEL URI is not available,
it MAY be a generic SIP URI. Note that this contact information a generic SIP URI is acceptable. Note that this contact
is not used by PSAPs for callbacks (a call from a PSAP directly information is not used by PSAPs for callbacks (a call from a PSAP
related to a recently terminated emergency call, placed by the directly related to a recently terminated emergency call, placed
PSAP using a SIP Priority header field set to "psap-callback", as by the PSAP using a SIP Priority header field set to "psap-
described in [RFC7090]). callback", as described in [RFC7090]).
Reason for Need: Additional data providers may need to be contacted Reason for Need: Additional data providers might need to be
in error cases or other unusual circumstances. contacted 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.
4.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: This field encodes the language used by the entity at Description: This field encodes the language used by the entity at
the Data Provider Contact URI. The content of this field consists the Data Provider Contact URI. The content of this field consists
of a single token from the language tags registry, which can be of a single token from the language tags registry, which can be
found at [LanguageTagRegistry], and is defined in [RFC5646]. found at [LanguageTagRegistry], and is defined in [RFC5646].
Multiple instances of this element may occur but the order is Multiple instances of this element MAY occur but the order is
significant and the preferred language should appear first. The significant and the 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 this field informs the PSAP of the language(s) used by (Note that this field informs the PSAP of the language(s) used by
the data provider. If the PSAP needs to contact the data the data provider. If the PSAP needs to contact the data
provider, it can be helpful to know in advance the language(s) provider, it can be helpful to know in advance the language(s)
used by the data provider. If the PSAP uses a communication used by the data provider. If the PSAP uses a communication
protocol to reach the data provider, that protocol may have protocol to reach the data provider, that protocol might have
language facilities of its own (such as the 'language' media language facilities of its own (such as the 'language' media
feature tag, defined in RFC 3840 [RFC3840] and the more extensive feature tag, defined in RFC 3840 [RFC3840] and the more extensive
language negotiation mechanism proposed with language negotiation mechanism proposed with
[I-D.gellens-slim-negotiating-human-language]), and if so, those [I-D.gellens-slim-negotiating-human-language]), and if so, those
are independent of this field.) are independent of this field.)
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.
skipping to change at page 14, line 4 skipping to change at page 14, line 10
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).
4.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: Per [RFC6351] the xCard structure is represented within Description: Per [RFC6351] the xCard structure is represented within
a <vcard> element. Although multiple <vcard> elements may be a <vcard> element. Although multiple <vcard> elements can be
contained in a structure only one <vcard> element SHOULD be contained in a structure only one <vcard> element SHOULD be
provided. If more than one appears, the first SHOULD be used. provided. If more than one appears, the first SHOULD be used.
There are many fields in the xCard and the creator of the data There are many fields in the xCard and the creator of the data
structure is encouraged to provide all available information. N, structure is encouraged to provide all available information. N,
ORG, ADR, TEL, EMAIL are suggested at a minimum. N SHOULD contain ORG, ADR, TEL, EMAIL are suggested at a minimum. N SHOULD contain
the name of the support group or device owner as appropriate. If the name of the support group or device owner as appropriate. If
more than one TEL property is provided, a parameter from the vCard more than one TEL property is provided, a parameter from the vCard
Property Value registry MUST be specified for each TEL. For Property Value registry SHOULD be specified for each TEL. For
encoding of the vCard this specification uses the XML-based encoding of the vCard this specification uses the XML-based
encoding specified in [RFC6351], referred to in this document as encoding specified in [RFC6351], referred to in this document as
"xCard". "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 the call taker by providing How Used by Call Taker: Assists the call taker by providing
additional contact information aside from what may be included in additional contact information aside from what is included in the
the SIP INVITE or the PIDF-LO. SIP INVITE or the PIDF-LO.
4.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
skipping to change at page 16, line 46 skipping to change at page 17, line 4
<country>Finland</country> <country>Finland</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+358 50 4871445</uri> <uri>tel:+358 50 4871445</uri>
</tel>
<tel>
<parameters>
<type>
<text>work</text>
<text>main-number</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+358 50 5050505</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>hannes.tschofenig@nsn.com</text> <text>hannes.tschofenig@nsn.com</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri>geo:60.210796,24.812924</uri> <uri>geo:60.210796,24.812924</uri>
skipping to change at page 17, line 32 skipping to change at page 17, line 49
</vcard> </vcard>
</ad:DataProviderContact> </ad:DataProviderContact>
</ad:EmergencyCallData.ProviderInfo> </ad:EmergencyCallData.ProviderInfo>
Figure 3: EmergencyCallData.ProviderInfo Example. Figure 3: EmergencyCallData.ProviderInfo Example.
4.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 service providers in the to the caller. It SHOULD be included by all service providers in the
path of the call. The mime subtype is "application/ path of the call. The mime media type is "application/
EmergencyCallData.ServiceInfo+xml". EmergencyCallData.ServiceInfo+xml".
4.2.1. Service Environment 4.2.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
Use: Conditional: Required unless the 'ServiceType' value is Use: Conditional: Required unless the 'ServiceType' value is
'wireless'. 'wireless'.
XML Element: <ServiceEnvironment> XML Element: <ServiceEnvironment>
Description: This element indicates whether a call is from a Description: This element indicates whether a call is from a
business or residence. Currently, the only valid entries are business or residence. Currently, the only valid entries are
'Business', 'Residence', and 'unknown', as shown in Figure 4. New 'Business', 'Residence', and 'unknown', as shown in Figure 4. New
values can be defined via the registry created in Section 10.1.2. values can be defined via the registry created in Section 11.1.2.
Reason for Need: To provide context and a hint when determining Reason for Need: To provide context and a hint when determining
equipment and manpower requirements. equipment and manpower requirements.
How Used by Call Taker: Information may be used to provide context How Used by Call Taker: Information can be used to provide context
and a hint to assist in determining equipment and manpower and a hint to assist in determining equipment and manpower
requirements for emergency responders. Because there are requirements for emergency responders. This is non-authoritative:
situations where the service provider does not know (such as There are situations where the service provider does not know the
anonymous pre-paid service), and because the type of service does type of service (e.g., anonymous pre-paid service). The type of
not neccessarily reflect the nature of the premises (for example, service does not necessarily reflect the nature of the premises
a business line installed in a residence, or wireless service), (e.g., a business line installed in a residence, or cellular
and the registry is not all-encompassing, this is at best advisory service). The registry does not contain all possible values for
information, but since it mimics a similar capability in some all situations. Hence, this is at best advisory information, but
current emergency calling systems (e.g., a field in the Automatic since it mimics a similar capability in some current emergency
Location Information (ALI) information used with legacy North calling systems (e.g., a field in the Automatic Location
American wireline systems), it is known to be valuable. The Information (ALI) information used with legacy North American
wireline systems), it is known to be valuable to PSAPs. The
service provider uses its best information (such as a rate plan, service provider uses its best information (such as a rate plan,
facilities used to deliver service or service description) to facilities used to deliver service or service description) to
determine the information and is not responsible for determining determine the information and is not responsible for determining
the actual characteristics of the location from which the call the actual characteristics of the location from which the call
originated. Because the usefulness is unknown (and less clear) originated. Because the usefulness is unknown (and less clear)
for wireless, this element is OPTIONAL for wireless and REQUIRED for cellular, this element is OPTIONAL for commercial mobile radio
otherwise. services (e.g., cellular) and REQUIRED otherwise.
+-----------+--------------------------+ +-----------+--------------------------+
| Token | Description | | Token | Description |
+-----------+--------------------------+ +-----------+--------------------------+
| Business | Business service | | Business | Business service |
| Residence | Residential service | | Residence | Residential service |
| unknown | Type of service unknown | | unknown | Type of service unknown |
| | (e.g., anonymous pre- | | | (e.g., anonymous pre- |
| | paid service) | | | paid service) |
+-----------+--------------------------+ +-----------+--------------------------+
skipping to change at page 18, line 49 skipping to change at page 19, line 29
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 (similar to the Class of Service delivered with legacy placed (similar to the Class of Service delivered with legacy
emergency calls in some some regions). The implied mobility of emergency calls in some some regions). The implied mobility of
this service cannot be relied upon. A registry is created in this service cannot be relied upon. A registry is created in
Section 10.1.3. The initial set of values is shown in Figure 5. Section 11.1.3. The initial set of values is shown in Figure 5.
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 in Reason for Need: Knowing the type of service can assist the PSAP in
handling of the call. 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. As the information is not always
is treated differently than a call from a sensor device. As the available, and the registry is not all-encompassing, this is at
information is not always available, and the registry is not all- best advisory information, but since it mimics a similar
encompassing, this is at best advisory information, but since it capability in some legacy emergency calling systems, it is known
mimics a similar capability in some legacy emergency calling to be valuable.
systems, it is known to be valuable.
+--------------+----------------------------------------+ +--------------+----------------------------------------+
| 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 |
| temp | Soft dial tone/quick service/warm | | temp | Soft dial tone/quick service/warm |
| | disconnect/suspended | | | disconnect/suspended |
| MLTS-hosted | Hosted multi-line telephone system | | MLTS-hosted | Hosted multi-line telephone system |
| | such as Centrex | | | such as Centrex |
| MLTS-local | Local multi-line telephone system, | | MLTS-local | Local multi-line telephone system, |
| | includes all PBX, key systems, | | | includes all PBX, key systems, |
| | Shared Tenant Service | | | Shared Tenant Service |
| sensor- | These are devices that generate DATA | | sensor- | These are devices that generate DATA |
| unattended | ONLY. This is a one-way information | | unattended | ONLY. This is a one-way information |
| | transmit without interactive media | | | transmit without interactive media |
| sensor- | Devices that are supported by a | | sensor- | Devices that are supported by a |
| attended | monitoring service provider or that | | attended | monitoring service provider or that |
| | are capable of supporting interactive| | | are capable of supporting interactive|
| | media | | | media |
| POTS | Wireline: Plain Old Telephone Service | | POTS | Wireline: Plain Old Telephone Service |
| VOIP | An over-the-top service that provides | | OTT | An over-the-top service that provides |
| | communication over arbitrary Internet| | | communication over arbitrary Internet|
| | access (fixed, nomadic, mobile) | | | access (fixed, nomadic, mobile) |
| remote | Off-premise extension | | digital | Wireline non-OTT digital phone service |
| OPX | Off-premise extension |
| relay | A service where a human third-party | | relay | A service where a human third-party |
| | agent provides additional assistance | | | agent provides additional assistance |
| | This includes sign language relay/ | | | This includes sign language relay/ |
| | interpretation, telematics services | | | interpretation, telematics services |
| | that provide a human on the call, | | | that provide a human on the call, |
| | and similar services. | | | and similar services |
+--------------+----------------------------------------+ +--------------+----------------------------------------+
Figure 5: Service Delivered by Provider to End User Registry Figure 5: Service Delivered by Provider to End User Registry
The initial set of values has been collected from sources of
currently-used systems, including [NENA-02-010], [nc911], [NANP], and
[LERG].
4.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's device. As the service provider might mobility of the caller's device. As the service provider might
not know the characteristics of the actual device or access not know the characteristics of the actual device or access
network used, the value should be treated as advisory and not be network used, the value should be treated as advisory and not be
relied upon. A registry is created in Section 10.1.4 with the relied upon. A registry is created in Section 11.1.4 with the
initial valid entries shown in Figure 6. initial valid entries shown in Figure 6.
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. can 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.
+-----------+----------------------------+ +-----------+----------------------------+
| Token | Description | | Token | Description |
+-----------+----------------------------+ +-----------+----------------------------+
| Mobile | The device is able to move | | Mobile | The device is able to move |
| | at any time | | | at any time |
| Fixed | The device is not expected | | Fixed | The device is not expected |
skipping to change at page 22, line 8 skipping to change at page 22, line 19
<svc:ServiceEnvironment>Business</svc:ServiceEnvironment> <svc:ServiceEnvironment>Business</svc:ServiceEnvironment>
<svc:ServiceType>MLTS-hosted</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 7: EmergencyCallData.ServiceInfo Example. Figure 7: EmergencyCallData.ServiceInfo Example.
4.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 media type
"application/EmergencyCallData.DeviceInfo+xml". is "application/EmergencyCallData.DeviceInfo+xml".
4.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 Device Information blocks, one provided by the device
structures, one created by the device and one created by the and one from the service provider. This information describes the
service provider. This information describes the device, not how device, not how it is being used. This data element defines the
it is being used. This data element defines the kind of device kind of device making the emergency call. A registry is created
making the emergency call. A registry is created in in Section 11.1.6 with the initial set of values as shown in
Section 10.1.6 with the initial set of values as shown in
Figure 8. Figure 8.
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 provide the call taker context regarding How Used by Call Taker: Can provide the call taker context regarding
the caller, the capabilities of the calling device or the the caller, the capabilities of the calling device or the
environment in which the device is being used, and may assist in environment in which the device is being used, and can assist in
understanding the location information and capabilities of the understanding the location information and capabilities of the
calling device. For example, a cordless handset may be outside or calling device. For example, a cordless handset might be outside
next door. or next door.
+---------------+----------------------------------------+ +---------------+----------------------------------------+
| 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 | Soft client on desktop PC | |desktop | Soft client on desktop PC |
|laptop | Soft client on laptop type device | |laptop | Soft client on laptop type device |
skipping to change at page 24, line 33 skipping to change at page 24, line 39
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> can 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 is created in Section 10.1.7 with an identifier. A registry is created in Section 11.1.7 with an
initial set of values shown in Figure 9. initial set of values shown in Figure 9.
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; might
used by PSAP management during an investigation. (For example, if be used by PSAP management during an investigation. (For example,
a PSAP experiences repeated false/accidental calls and there is no if a PSAP experiences repeated false/accidental calls and there is
callback number or it isn't usable, the PSAP may need to try and no callback number or it isn't usable, the PSAP might need to try
track down the device using various means (e.g., contacting and track down the device using various means (e.g., contacting
service providers in the area). In the case of handsets without service providers in the area). In the case of handsets without
current service, it may be possible to determine who last had current service, it might be possible to determine who last had
service. Another example might be a disconnected call where the service. Another example might be a disconnected call where the
call taker believes there is a need for assistance but was not call taker believes there is a need for assistance but was not
able to obtain a location or other information). able to obtain a location or other information).
Example: <UniqueDeviceID TypeOfDeviceID="SN">12345</UniqueDeviceID> Example: <UniqueDeviceID TypeOfDeviceID="SN">12345</UniqueDeviceID>
+--------+------------------------------------------+ +--------+------------------------------------------+
| Token | Description | | Token | Description |
+--------+------------------------------------------+ +--------+------------------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) | | MEID | Mobile Equipment Identifier (CDMA) |
skipping to change at page 25, line 35 skipping to change at page 25, line 40
4.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 might 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 can 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 can 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.
4.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 a device/service-specific-
additional URI is provided additional URI is provided
XML Element: <DeviceSpecificType> XML Element: <DeviceSpecificType>
Description: A value from the registry defined in Section 10.1.8 to Description: A value from the registry defined in Section 11.1.8 to
describe the type of data located at the device/service-specific describe the type of data located at the device/service-specific
additional data structure. The initial values shown in Figure 10 additional data structure. The initial values shown in Figure 10
currently only include IEEE 1512, which is the USDoT model for currently only include IEEE 1512, which is the USDoT model for
traffic incidents. traffic incidents.
Reason for Need: This data element allows identification of Reason for Need: This data element allows identification of
externally defined schemas, which may have additional data that externally defined schemas, which might have additional data that
may assist in emergency response. can assist in emergency response.
How Used by Call Taker: This data element allows the end user (call How Used by Call Taker: This data element allows the end user (call
taker or first responder) to know what type of additional data may taker or first responder) to know what type of additional data is
be available to aid in providing the needed emergency services. available to aid in providing the needed emergency services.
Note: Information which is specific to a location or a caller Note: This mechanism is not appropriate for information specific to
(person) should not be placed in this section. a location or a caller (person).
+----------+----------------------------+--------------------------------+ +----------+----------------------------+--------------------------------+
| Token | Description | Specification | | Token | Description | Specification |
+----------+----------------------------+--------------------------------+ +----------+----------------------------+--------------------------------+
| IEEE1512 | Common Incident Management |IEEE 1512-2006 | | IEEE1512 | Common Incident Management |IEEE 1512-2006 |
| | Message Set (USDoT model |https://standards.ieee.org/ | | | Message Set (USDoT model |https://standards.ieee.org/ |
| | for traffic incidents) |findstds/standard/1512-2006.html| | | for traffic incidents) |findstds/standard/1512-2006.html|
+----------+----------------------------+--------------------------------+ +----------+----------------------------+--------------------------------+
Figure 10: Device/Service Data Type Registry Figure 10: Device/Service Data Type Registry
4.3.7. Issues with getting new types of data into use 4.3.7. EmergencyCallData.DeviceInfo Example
This document describes two mechanisms that allow extension of the
kind of data provided with an emergency call: define a new block or
define a new service specific additional data URL for the DeviceInfo
block. While defining new data types and getting a new device or
application to send the new data may be easy, getting PSAPs and
responders to actually retrieve the data and use it will be
difficult. New mechanism providers should understand that acquiring
and using new forms of data usually require software upgrades at the
PSAP and/or responders, as well as training of call takers and
responders in how to interpret and use the information. Legal and
operational review may also be needed. Overwhelming a call taker or
responder with too much information is highly discouraged. Thus, the
barrier to supporting new data is quite high.
The mechanisms this document describes are meant to encourage
development of widely supported, common data formats for classes of
devices. If all manufacturers of a class of device use the same
format, and the data can be shown to improve outcomes, then PSAPs and
responders may be encouraged to upgrade their systems and train their
staff to use the data. Variations, however well intentioned, are
unlikely to be supported.
Implementers should consider that data from sensor-based devices in
some cases may not be useful to call takers or PSAPs (and privacy,
liability, or other considerations might preclude the PSAP from
touching the data), but may be of use to responders. Each data item
provided with the call in conformance with this document can be
accessed by responders or other entities in the emergency services,
whether or not the data is accessed by the PSAP.
4.3.8. Choosing between defining a new type of block or new type of
device/service specific additional data
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/
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
same in both cases. Considerations for choosing which mechanism to
register under include:
Applicability: Information which will be carried by many kinds of
devices or services are more appropriately defined as separate
blocks.
Privacy: Information which may contain private data may be better
sent in the DeviceInfo block, rather than a new block so that
implementations are not tempted to send the data by value, and
thus having more exposure to the data than forcing the data to be
retrieved via the URL in DeviceInfo.
Size: Information which may be very large may be better sent in the
DeviceInfo block, rather than a new block so that implementations
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
sent by value
Availability of a server: Providing the data via the device block
requires a server be made available to retrieve the data.
Providing the data via new block allows it to be sent by value
(CID).
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">
<dev:DataProviderReference>d4b3072df.201409182208075@example.org <dev:DataProviderReference>d4b3072df.201409182208075@example.org
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:DeviceClassification>fixed</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 11: EmergencyCallData.DeviceInfo Example. Figure 11: EmergencyCallData.DeviceInfo Example.
4.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 type is "application/EmergencyCallData.SubscriberInfo+xml". The MIME media 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 which information can be displayed and logged. A vary but dictate which information can be displayed and logged. A
general privacy indicator expressing a desire for privacy by the general privacy indicator expressing a desire for privacy by the
subscriber is provided. The interpretation of how this is applied is subscriber is provided. The interpretation of how this is applied is
left to the receiving jurisdiction as the custodians of the local left to the receiving jurisdiction as the custodians of the local
regulatory requirements. This matches an equivalent privacy flag regulatory requirements. This matches an equivalent privacy flag
provided in some legacy emergency call systems. provided in some legacy emergency call systems.
skipping to change at page 29, line 21 skipping to change at page 28, line 15
Because the interpretation of this indicator varies based on local Because the interpretation of this indicator varies based on local
regulations, this document cannot describe the exact semantics nor regulations, this document cannot describe the exact semantics nor
indicate which fields are affected (the application of this indicate which fields are affected (the application of this
indicator might affect the display of data contained in any of the indicator might affect the display of data contained in any of the
blocks). blocks).
Reason for Need: Some jurisdictions require subscriber privacy to be Reason for Need: Some jurisdictions require subscriber privacy to be
observed when processing emergency calls. 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. might not have access to some aspects of the subscriber
information.
4.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 MUST be provided unless it is not Use: Conditional. Subscriber data MUST be provided unless it is not
available. Some services, such as prepaid phones, non-initialized available. Some services, such as prepaid phones, non-initialized
phones, etc., do not have information about the subscriber. phones, etc., do not have information about the subscriber.
XML Element: <SubscriberData> XML Element: <SubscriberData>
skipping to change at page 29, line 44 skipping to change at page 28, line 39
about the subscriber; e.g., Name, Address, Individual Telephone about the subscriber; e.g., Name, Address, Individual Telephone
Number, Main Telephone Number and any other data. <n>, <org> (if Number, Main Telephone Number and any other data. <n>, <org> (if
appropriate), <adr>, <tel>, <email> are suggested at a minimum. appropriate), <adr>, <tel>, <email> are suggested at a minimum.
If more than one <tel> property is provided, a parameter from the If more than one <tel> property is provided, a parameter from the
vCard Property Value registry MUST be specified on each <tel>. vCard Property Value registry MUST be specified on each <tel>.
While some data (such as <anniversary>) might not seem obviously While some data (such as <anniversary>) might not seem obviously
relevant for emergency services, any data is potentially useful in relevant for emergency services, any data is potentially useful in
some emergency circumstances. some emergency circumstances.
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 can 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. While the location here is not necessarily obtained otherwise. While the location here is not necessarily
that of caller, in some circumstances it can be helpful in that of caller, in some circumstances it can be helpful in
locating the caller when other means have failed. locating the caller when other means have failed.
4.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"?>
skipping to change at page 31, line 27 skipping to change at page 30, line 20
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+1-418-656-9254;ext=102</uri> <uri>tel:+1-418-656-9254;ext=102</uri>
</tel> </tel>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text>
<text>main-number</text>
</type>
</parameters>
<uri>tel:+1-418-555-0000</uri>
</tel>
<tel>
<parameters>
<type>
<text>work</text>
<text>text</text> <text>text</text>
<text>voice</text> <text>voice</text>
<text>cell</text> <text>cell</text>
<text>video</text> <text>video</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+1-418-262-6501</uri> <uri>tel:+1-418-262-6501</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
skipping to change at page 32, line 20 skipping to change at page 31, line 24
</sub:SubscriberData> </sub:SubscriberData>
</sub:EmergencyCallData.SubscriberInfo> </sub:EmergencyCallData.SubscriberInfo>
Figure 12: EmergencyCallData.SubscriberInfo Example. Figure 12: EmergencyCallData.SubscriberInfo Example.
4.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-readable content. The mime subtype is "application/ machine-readable content. The mime media type is "application/
EmergencyCallData.Comment+xml" EmergencyCallData.Comment+xml"
4.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>
skipping to change at page 33, line 5 skipping to change at page 32, line 14
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<com:EmergencyCallData.Comment <com:EmergencyCallData.Comment
xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"> xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<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 13: EmergencyCallData.Comment Example. Figure 13: EmergencyCallData.Comment Example.
5. Data Transport Mechanisms 5. Issues with getting new types of data into use
This document describes two mechanisms that allow extension of the
kind of data provided with an emergency call: define a new block or
define a new service specific additional data URL for the DeviceInfo
block (Section 4.3.5). While defining new data types and getting a
new device or application to send the new data might be easy, getting
PSAPs and responders to actually retrieve the data and use it will be
difficult. New mechanism providers should understand that acquiring
and using new forms of data usually require software upgrades at the
PSAP and/or responders, as well as training of call takers and
responders in how to interpret and use the information. Legal and
operational review might also be needed. Overwhelming a call taker
or responder with too much information is highly discouraged. Thus,
the barrier to supporting new data is quite high.
The mechanisms this document describes are meant to encourage
development of widely supported, common data formats for classes of
devices. If all manufacturers of a class of device use the same
format, and the data can be shown to improve outcomes, then PSAPs and
responders can be encouraged to upgrade their systems and train their
staff to use the data. Variations, however well intentioned, are
unlikely to be supported.
Implementers should consider that data from sensor-based devices in
some cases might not be useful to call takers or PSAPs (and privacy,
liability, or other considerations might preclude the PSAP from
accessing or handling the data), but might be of use to responders.
Each data item provided with the call in conformance with this
document can be accessed by responders or other entities in the
emergency services, whether or not the data is accessed by the PSAP.
5.1. Choosing between defining a new type of block or new type of
device/service-specific additional data
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/
service-specific additional data URL in the DeviceInfo block can be
used and a new type for it defined. The data passed would likely be
the same in either case. Considerations for choosing the mechanism
under which to register include:
Applicability: Information which will be supported by many kinds of
devices or services are more appropriately defined as separate
blocks.
Privacy: Information sent as a device/service-specific additional
data URL in the DeviceInfo block is by reference (not by value),
which inherently provides some additional privacy protection
(since the requester needs to supply a certificate which is
verified by the supplier).
Size: Information which can be very large might be better sent in
the DeviceInfo block, rather than a new block, so that
implementations are unable to send the data by value. Conversely,
data which is small might best be sent in a separate block so that
it can be sent by value.
Availability of a server: Providing the data via the device block
requires a server be available from which to retrieve the data.
Providing the data via new block allows it to be sent by value.
6. 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 field, is in an existing SIP header field, the Call-Info header field, is
defined. The URI points to the additional data structure. The defined. The URI points to the additional data structure. The
Call-Info header field is specified in Section 20.9 of [RFC3261]. Call-Info header field is specified in Section 20.9 of [RFC3261].
skipping to change at page 33, line 16 skipping to change at page 33, line 39
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 field, is in an existing SIP header field, the Call-Info header field, is
defined. The URI points to the additional data structure. The defined. The URI points to the additional data structure. The
Call-Info header field is specified in Section 20.9 of [RFC3261]. Call-Info header field is specified in Section 20.9 of [RFC3261].
This document adds a new compound token starting with the value This document adds a new compound token starting with the value
'EmergencyCallData' for the Call-Info "purpose" parameter. If 'EmergencyCallData' for the Call-Info "purpose" parameter. If
the "purpose" parameter is set to a value starting with the "purpose" parameter is set to a value starting with
'EmergencyCallData', then the Call-Info header field contains 'EmergencyCallData', then the Call-Info header field contains
either an HTTPS URL pointing to an external resource or a CID either an HTTPS URL pointing to an external resource or a CID
(content indirection) URI that allows the data structure to be (content indirection) URI that allows the data structure to be
placed in the body of the SIP message. The "purpose" parameter placed in the body of the SIP message. The "purpose" parameter
also indicates the kind of data (by its MIME subtype) that is also indicates the kind of data (by its MIME media subtype) that
available at the URI. As the data is conveyed using a URI in the is available at the URI.
SIP signaling, the data itself may reside on an external
resource, or may be contained within the body of the SIP message. As the data is conveyed using a URI in the SIP signaling, the
When the URI refers to data at an external resource, the data is data itself can reside on an external resource, or can be
said to be passed by reference. When the URI refers to data contained within the body of the SIP message. When the URI
contained within the body of the SIP message, the data is said to refers to data at an external resource, the data is said to be
be passed by value. A PSAP or emergency responder is able to passed by reference. When the URI refers to data contained
examine the type of data provided and selectively inspect the within the body of the SIP message, the data is said to be passed
data it is interested in, while forwarding all of it (the values by value. A PSAP or emergency responder is able to examine the
or references) to downstream entities. To be conveyed in a SIP type of data provided and selectively inspect the data it is
body, additional data about a call is defined as a series of MIME interested in, while forwarding all of it (the values or
objects. Each block defined in this document is an XML data references) to downstream entities.
structure identified by its MIME type. (Blocks defined by others
may be encoded in XML or not, as identified by their MIME To be conveyed in a SIP body, additional data about a call is
registration.) As usual, whenever more than one MIME part is defined as a series of MIME objects (also referred to as a
included in the body of a message, MIME multipart (i.e., "block" of data). Each block defined in this document is an XML
'multipart/mixed') encloses them all. This document defines a data structure identified by its MIME media type. (Blocks
set of XML schemas and MIME types used for each block defined defined by others can be encoded in XML or not, as identified by
here. When additional data is passed by value in the SIP their MIME registration.) As usual, whenever more than one MIME
signaling, each CID URL points to one block in the body. part is included in the body of a message, MIME multipart (i.e.,
Multiple URIs are used within a Call-Info header field (or 'multipart/mixed') encloses them all.
multiple Call-Info header fields) to point to multiple blocks.
When additional data is provided by reference (in SIP signaling This document defines a set of XML schemas and MIME media types
or the <provided-by> element of a PIDF-LO), each HTTPS URL used for each block defined here. When additional data is passed
references one block; the data is retrieved with an HTTPS GET by value in the SIP signaling, each CID URL points to one block
in the body. Multiple URIs are used within a Call-Info header
field (or multiple Call-Info header fields) to point to multiple
blocks. When additional data is provided by reference (in SIP
signaling or the <provided-by> element of a PIDF-LO), each HTTPS
URL references one block; the data is retrieved with an HTTPS GET
operation, which returns the block as an object (the blocks operation, which returns the block as an object (the blocks
defined here are returned as XML objects). defined here are returned as XML 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. In <provided-by> element of a PIDF-LO [RFC4119] is defined.
addition to service providers in the call path, the access
network provider may also have similar information that can be In addition to service providers in the call path, the access
valuable to the PSAP. When the access network provider supplies network provider generally has similar information that can be
location information in the form of a PIDF-LO from a location valuable to the PSAP. When the access network provider and
server via a location configuration protocol, it has the ability service provider are separate entities, the access network does
to add the data structures defined in this document within the not participate in the application layer signaling (and hence
PIDF-LO. The data in these data structures is not specific to cannot add a Call-Info header field to the SIP message), but can
the location itself, but rather provides descriptive information provide location information in a PIDF-LO. When the access
having to do with the immediate circumstances about the provision network provider supplies location information in the form of a
PIDF-LO from a location server via a location configuration
protocol, it has the ability to add the data structures defined
in this document (or references to them) within the PIDF-LO.
The data in these data structures is not specific to the location
itself, but rather provides descriptive information having to do
with the immediate circumstances about the provider's provision
of the location (e.g., the identity of the access network of the location (e.g., the identity of the access network
provider, how to contact that entity, what kind of service the provider, how to contact that entity, what kind of service the
access network provides, subscriber information, etc.). This access network provides, subscriber information, etc.). This
data is similar in nearly every respect to the data known by data is similar in nearly every respect to the data known by
service providers in the path of the call. When the access service providers in the path of the call. The <provided-by>
network provider and service provider are separate entities, the element of the PIDF-LO is a mechanism for the access network
access network does not participate in the application layer provider to supply the information. This document describes a
signaling (and hence cannot add a Call-Info header field to the namespace per [RFC4119] for inclusion in the <provided-by>
SIP message), but can provide location information in a PIDF-LO. element of a PIDF-LO for adding information known to the access
The <provided-by> element of the PIDF-LO is a mechanism for the network provider. The access network provider SHOULD provide
access network provider to supply the information. For this additional data within a <provided-by> element of a PDIF-LO it
reason, this document describes a namespace per [RFC4119] for returns for emergency use (e.g., if requested with a HELD
inclusion in the <provided-by> element of a PIDF-LO for adding "responseTime" attribute of "emergencyRouting" or
information known to the access network provider. The access "emergencyDispatch" [RFC5985]).
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 10.1.9, can be Additional Data registry, as defined in Section 11.1.9, can be
included or referenced in the SIP signaling (using the Call-Info included or referenced in the SIP signaling (using the Call-Info
header field) or in the <provided-by> element of a PIDF-LO. For header field) or in the <provided-by> element of a PIDF-LO. For
interoperability, only blocks in the registry are permitted to be interoperability, only blocks in the registry are permitted to be
sent using the mechanisms specified in this document. Since multiple sent using the mechanisms specified in this document. Since multiple
entities are expected to provide sets of data, the data itself needs entities are expected to provide sets of data, the data itself needs
information describing the source. Consequently, each entity adding information describing the source. Consequently, each entity adding
additional data MUST supply a "Data Provider" block. All other additional data MUST supply a "Data Provider" block. All other
blocks are optional, but each entity SHOULD supply all blocks where blocks are optional, but each entity SHOULD supply all blocks where
it has at least some of the information in the block. it has at least some of the information in the block.
5.1. Transmitting Blocks using Call-Info 6.1. Transmitting Blocks using Call-Info
A URI to a block MAY be inserted in any SIP request or response A URI to a block MAY be inserted in any SIP request or response
method (most often INVITE or MESSAGE) with a Call-Info header field method (most often INVITE or MESSAGE) with a Call-Info header field
containing a purpose value starting with 'EmergencyCallData', a dot containing a purpose value starting with 'EmergencyCallData', a dot
("."), and the type of data available at the URI. The type of data ("."), and the type of data available at the URI. The type of data
is denoted by including the root of the MIME subtype (the is denoted by including the root of the MIME media subtype (the
'EmergencyCallData' prefix is not repeated), omitting any suffix such 'EmergencyCallData' prefix is not repeated), omitting any suffix such
as '+xml'). For example, when referencing a block with MIME type as '+xml'). For example, when referencing a block with MIME media
'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' type 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose'
parameter is set to 'EmergencyCallData.ProviderInfo'. An example parameter is set to 'EmergencyCallData.ProviderInfo'. An example
"Call-Info" header field for this would be: "Call-Info" header field for this would be:
Call-Info: https://www.example.com/23sedde3; Call-Info: https://www.example.com/23sedde3;
purpose="EmergencyCallData.ProviderInfo" purpose="EmergencyCallData.ProviderInfo"
A Call-info header field with a purpose value starting with A Call-info header field with a purpose value starting with
'EmergencyCallData' only has meaning in the context of an emergency 'EmergencyCallData' only has meaning in the context of an emergency
call (as ascertained by the presence of an emergency service URN in a call (as ascertained by the presence of an emergency service URN in a
Request-URI header field of a SIP message), test emergency calls Request-URI header field of a SIP message), test emergency calls
(using an appropriate service URN), and some private-use calls where (using an appropriate service URN), and some private-use calls where
the endpoints have a preexisting relationship and privacy concerns do the endpoints have a preexisting relationship and privacy concerns do
not apply because of the relationship; use in other contexts is not apply because of the relationship; use in other contexts is
undefined and is likely to unnecessarily expose confidential data. undefined and is likely to unnecessarily expose confidential data.
If the data is provided by reference, an HTTPS URI MUST be included If the data is provided by reference, an HTTPS URI MUST be included
and consequently Transport Layer Security (TLS) protection is applied and consequently Transport Layer Security (TLS) protection is used
for protecting the retrieval of the information. during the retrieval of the information.
The data may also be supplied by value in any SIP request or response The data can also be supplied by value in any SIP request or response
method that is permitted to contain a body (i.e., not a BYE request). method that is permitted to contain a body (i.e., not a BYE request)
In this case, Content Indirection (CID) [RFC2392] is used, with the [RFC3261]. In this case, Content Indirection (CID) [RFC2392] is
CID URL referencing the MIME body part containing the data. Note used, with the CID URL referencing the MIME body part containing the
that [RFC3261] forbids proxies from altering message bodies, so data. Note that [RFC3261] forbids proxies from altering message
entities in the call path that add blocks by value need to do so bodies, so entities in the call path that add blocks by value need to
using an appropriate SIP entity (e.g., a back-to-back user agent). do so using an appropriate SIP entity (e.g., a back-to-back user
agent).
Transmitting data by value is especially useful in certain cases, Transmitting data by value is especially useful in certain cases,
such as when the data exists in or is generated by the originating such as when the data exists in or is generated by the originating
device, but is not intended for very large data blocks. Additional device, but is not intended for very large data blocks. Additional
security and privacy considerations apply to data transmitted by security and privacy considerations apply to data transmitted by
value, as discussed in Section 8 and Section 9. value, as discussed in Section 9 and Section 10.
More than one Call-Info header field with a purpose value starting More than one Call-Info header field with a purpose value starting
with 'EmergencyCallData' can be expected, but at least one MUST be with 'EmergencyCallData' can be expected, but at least one MUST be
provided. The device MUST provide one if it knows no service provided. The device MUST provide one unless it knows that a service
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. Each service provider in the path of an
call MUST insert its own. For example, a device, a telematics emergency call MUST insert its own. For example, a device, a
service provider in the call path, as well as the mobile carrier telematics service provider in the call path, as well as the mobile
handling the call will each provide one. There may be circumstances carrier handling the call will each provide one. There might be
where there is a service provider who is unaware that the call is an circumstances where there is a service provider who is unaware that
emergency call and cannot reasonably be expected to determine that it the call is an emergency call and cannot reasonably be expected to
is an emergency call. In that case, that service provider is not determine that it is an emergency call. In that case, that service
expected to provide EmergencyCallData. provider is not expected to provide EmergencyCallData.
5.2. Transmitting Blocks by Reference using the <provided-by> Element 6.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 5.1). field (as specified in Section 6.1).
For example, to reference a block with MIME type 'application/ For example, to reference a block with MIME media 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"/>
The <EmergencyCallDataReference> element transmits one data block; The <EmergencyCallDataReference> element transmits one data block;
multiple data blocks may be transmitted by using multiple multiple data blocks are transmitted by using multiple
<EmergencyCallDataReference> elements. Multiple <EmergencyCallDataReference> elements. Multiple
<EmergencyCallDataReference> elements MAY be included as child <EmergencyCallDataReference> elements MAY be included as child
elements inside the <provided-by> element. elements inside the <provided-by> element.
The following is a simplified example: The following is a simplified example:
<provided-by <provided-by>
<EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo" purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2" /> ref="https://example.com/ref2" />
<EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.ProviderInfo" purpose="EmergencyCallData.ProviderInfo"
ref="https://example.com/ref3" /> ref="https://example.com/ref3" />
<EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.Comment" purpose="EmergencyCallData.Comment"
skipping to change at page 37, line 11 skipping to change at page 37, line 40
</provided-by> </provided-by>
Example <provided-by> by Reference Example <provided-by> by Reference
For an example in context, Figure 18 shows a PIDF-LO example with an For an example in context, Figure 18 shows a PIDF-LO example with an
<EmergencyCallDataReference> element pointing to an <EmergencyCallDataReference> element pointing to an
EmergencyCallData.ServiceInfo data block with the URL in the 'ref' EmergencyCallData.ServiceInfo data block with the URL in the 'ref'
attribute and the purpose attribute set to attribute and the purpose attribute set to
"EmergencyCallData.ServiceInfo". "EmergencyCallData.ServiceInfo".
5.3. Transmitting Blocks by Value using the <provided-by> Element 6.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, because PIDF-LOs can be fetched by a
client or other entity and stored locally, so providing the data by
value risks exposing private information to a larger audience.
The <EmergencyCallDataValue> element is used to transmit one or more The <EmergencyCallDataValue> element is used to transmit one or more
additional data blocks by value within a <provided-by> element of a additional data blocks by value within a <provided-by> element of a
PIDF-LO. Each block being transmitted is placed (as a child element) PIDF-LO. Each block being transmitted is placed (as a child element)
inside the <EmergencyCallDataValue> element. (The same XML structure inside the <EmergencyCallDataValue> element. (The same XML structure
as would be contained in the corresponding MIME type body part is as would be contained in the corresponding MIME media type body part
placed inside the <EmergencyCallDataValue> element.) Multiple is placed inside the <EmergencyCallDataValue> element.) Multiple
<EmergencyCallDataValue> elements MAY be included as child elements <EmergencyCallDataValue> elements MAY be included as child elements
in the <provided-by> element. in the <provided-by> element.
The following is a simplified example: The following is a simplified example:
<provided-by <provided-by>
<EmergencyCallDataValue> <EmergencyCallDataValue>
<EmergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns= xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>flurbit735@es.example.com <DataProviderReference>flurbit735@es.example.com
</DataProviderReference> </DataProviderReference>
<DataProviderString>Access Network Examples, Inc <DataProviderString>Access Network Examples, Inc
</DataProviderString> </DataProviderString>
skipping to change at page 38, line 44 skipping to change at page 39, line 5
</provided-by> </provided-by>
Example <provided-by> by Value Example <provided-by> by Value
For an example in context, Figure 18 shows a PIDF-LO example that For an example in context, Figure 18 shows a PIDF-LO example that
contains a <provided-by> element with the contains a <provided-by> element with the
<EmergencyCallData.ProviderInfo> and the <EmergencyCallData.Comment> <EmergencyCallData.ProviderInfo> and the <EmergencyCallData.Comment>
elements as child elements of an <EmergencyCallDataValue> element. elements as child elements of an <EmergencyCallDataValue> element.
5.4. The Content-Disposition Parameter 6.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'
parameter for the Content-Disposition header field. These RFCs parameter for the Content-Disposition header field. These RFCs
describe how a UAS reacts if it receives a message body whose content describe how a UAS reacts if it receives a message body whose content
type or disposition type it does not understand. If the 'handling' type or disposition type it does not understand. If the 'handling'
parameter has the value "optional", the UAS ignores the message body. parameter has the value "optional", the UAS ignores the message body.
If the 'handling' parameter has the value "required", the UAS returns If the 'handling' parameter has the value "required", the UAS returns
a 415 (Unsupported Media Type) response. The 'by-reference' a 415 (Unsupported Media Type) response. The 'by-reference'
disposition type allows a SIP message to contain a reference to the disposition type of [RFC5621] allows a SIP message to contain a
body part, and the SIP UA processes the body part according to the reference to the body part, and the SIP UA processes the body part
reference. This is the case for a Call-info header field containing according to the reference. This is the case for a Call-info header
a Content Indirection (CID) URL. field containing a Content Indirection (CID) URL.
As an example, a SIP message indicates the Content-Disposition As an example, a SIP message indicates the Content-Disposition
parameter in the body of the SIP message as shown in Figure 14. parameter in the body of the SIP message as shown in Figure 14.
Content-Type: application/sdp Content-Type: application/sdp
...Omit Content-Disposition here; defaults are ok ...Omit Content-Disposition here; defaults are ok
...SDP goes in here ...SDP goes in here
--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 14: Example for use of the Content-Disposition Parameter in Figure 14: Example for use of the Content-Disposition Parameter in
SIP SIP
6. Examples 7. 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 15. In this example additional data is added by the end in Figure 15. In this example additional data is added by the end
device, included by the VoIP provider, and provided by the access device, included by the VoIP provider, and provided by the access
network provider (via the PIDF-LO). network provider (via the PIDF-LO).
O +----+ [============] [=============] O +----+ [============] [=============]
/|\ | UA | [ Access ] [ VoIP ] /|\ | UA | [ Access ] [ VoIP ]
| +----+ [ Network ] [ Provider ] | +----+ [ Network ] [ Provider ]
/ \ [ Provider ] [ example.org ] / \ [ Provider ] [ example.org ]
skipping to change at page 40, line 47 skipping to change at page 41, line 40
... Location Retrieval/Response ... Location Retrieval/Response
Figure 15: Additional Data Example Flow Figure 15: 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 15). The SIP INVITE example is shown in (see step #1 in Figure 15). The SIP INVITE example is shown in
Figure 16. Figure 16.
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> Call-Info: <http://wwww.example.com/hannes/photo.jpg>
;purpose=icon, ;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,
<cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE
Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ...
--boundary1
Content-Type: application/sdp <cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE
Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ...
...SDP goes here --boundary1
Content-Type: application/sdp
--boundary1-- ...SDP goes here
Content-Type: application/EmergencyCallData.DeviceInfo+xml --boundary1
Content-ID: <0123456789@atlanta.example.com> Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-Disposition: by-reference;handling=optional Content-ID: <0123456789@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?> Content-Disposition: by-reference;handling=optional
<dev:EmergencyCallData.DeviceInfo <?xml version="1.0" encoding="UTF-8"?>
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"> <dev:EmergencyCallData.DeviceInfo
<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119] xmlns:dev=
</dev:DataProviderReference> "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo">
<dev:DeviceClassification>laptop</dev:DeviceClassification> <dev:DataProviderReference>
<dev:UniqueDeviceID d4b3072df09876543@[93.184.216.119]
TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID> </dev:DataProviderReference>
</dev:EmergencyCallData.DeviceInfo> <dev:DeviceClassification>laptop</dev:DeviceClassification>
<dev:UniqueDeviceID
TypeOfDeviceID="MAC">00-0d-4b-30-72-df
</dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1
Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional
Content-Type: application/EmergencyCallData.ProviderInfo+xml <?xml version="1.0" encoding="UTF-8"?>
Content-ID: <1234567890@atlanta.example.com> <pi:EmergencyCallData.ProviderInfo
Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119] <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>Client</pi:TypeOfProvider>
<pi:TypeOfProvider>Client</pi:TypeOfProvider> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI> <pi:Language>en</pi:Language>
<pi:Language>en</pi:Language> <pi:DataProviderContact
<pi: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/> <suffix>Dipl. Ing.</suffix>
<suffix>Dipl. Ing.</suffix> </n>
</n> <bday><date>--0203</date></bday>
<bday><date>--0203</date></bday> <anniversary>
<anniversary> <date-time>20090808T1430-0500</date-time>
<date-time>20090808T1430-0500</date-time> </anniversary>
</anniversary> <gender><sex>M</sex></gender>
<gender><sex>M</sex></gender> <lang>
<lang> <parameters><pref><integer>1</integer></pref>
<parameters><pref><integer>1</integer></pref> </parameters>
</parameters> <language-tag>de</language-tag>
<language-tag>de</language-tag> </lang>
</lang> <lang>
<lang> <parameters><pref><integer>2</integer></pref>
<parameters><pref><integer>2</integer></pref> </parameters>
</parameters> <language-tag>en</language-tag>
<language-tag>en</language-tag> </lang>
</lang> <adr>
<adr> <parameters>
<parameters> <type><text>work</text></type>
<type><text>work</text></type> <label><text>Hannes Tschofenig
<label><text>Hannes Tschofenig Linnoitustie 6
Linnoitustie 6 Espoo, Finland
Espoo, Finland 02600</text></label>
02600</text></label> </parameters>
</parameters> <pobox/>
<pobox/> <ext/>
<ext/> <street>Linnoitustie 6</street>
<street>Linnoitustie 6</street> <locality>Espoo</locality>
<locality>Espoo</locality> <region>Uusimaa</region>
<region>Uusimaa</region> <code>02600</code>
<code>02600</code> <country>Finland</country>
<country>Finland</country> </adr>
</adr> <adr>
<adr> <parameters>
<parameters> <type><text>home</text></type>
<type><text>home</text></type> <label><text>Hannes Tschofenig
<label><text>Hannes Tschofenig c/o Hotel DuPont
c/o Hotel DuPont 42 W 11th St
42 W 11th St Wilmington, DE 19801
Wilmington, DE 19801 USA</text></label>
USA</text></label> </parameters>
</parameters> <pobox/>
<pobox/> <ext/>
<ext/> <street>42 W 11th St</street>
<street>42 W 11th St</street> <locality>Wilmington</locality>
<locality>Wilmington</locality> <region>DE</region>
<region>DE</region> <code>19801</code>
<code>19801</code> <country>USA</country>
<country>USA</country> </adr>
</adr> <tel>
<tel> <parameters>
<parameters> <type>
<type> <text>work</text>
<text>work</text> <text>voice</text>
<text>voice</text> </type>
</type> </parameters>
</parameters> <uri>tel:+358 50 4871445</uri>
<uri>tel:+358 50 4871445</uri> </tel>
</tel> <tel>
<tel> <parameters>
<parameters> <type>
<type> <text>home</text>
<text>home</text> <text>voice</text>
<text>voice</text> </type>
</type> </parameters>
</parameters> <uri>tel:+1 555 555 0123</uri>
<uri>tel:+1 555 555 0123</uri> </tel>
</tel> <tel>
<email> <parameters>
<parameters><type><text>work</text></type> <type>
</parameters> <text>work</text>
<text>hannes.tschofenig@nsn.com</text> <text>voice</text>
</email> <text>main-number</text>
<geo> </type>
<parameters><type><text>work</text></type> </parameters>
</parameters> <uri>tel:+1 302 594-3100</uri>
<uri>geo:60.210796,24.812924</uri> </tel>
</geo> <email>
<geo> <parameters><type><text>work</text></type>
<parameters><type><text>home</text></type> </parameters>
</parameters> <text>hannes.tschofenig@nsn.com</text>
<uri>geo:39.746537,-75.548027</uri> </email>
</geo> <geo>
<key> <parameters><type><text>work</text></type>
<parameters> </parameters>
<type><text>home</text></type> <uri>geo:60.210796,24.812924</uri>
</parameters>
<uri>https://www.example.com/key.asc </geo>
</uri> <geo>
</key> <parameters><type><text>home</text></type>
<tz><text>Finland/Helsinki</text></tz> </parameters>
<url> <uri>geo:39.746537,-75.548027</uri>
<parameters><type><text>home</text></type> </geo>
</parameters> <key>
<uri>http://example.com/hannes.tschofenig <parameters>
</uri> <type><text>home</text></type>
</url> </parameters>
</vcard> <uri>https://www.example.com/key.asc</uri>
</pi:DataProviderContact> </key>
</pi:EmergencyCallData.ProviderInfo> <tz><text>Finland/Helsinki</text></tz>
--boundary1-- <url>
<parameters><type><text>home</text></type>
</parameters>
<uri>http://example.com/hannes.tschofenig
</uri>
</url>
</vcard>
</pi:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo>
--boundary1--
Figure 16: End Device sending SIP INVITE with Additional Data Figure 16: End Device sending SIP INVITE with Additional Data
In this example, information available to the access network provider 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 provider 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
skipping to change at page 45, line 7 skipping to change at page 46, line 5
It performs typical emergency services related tasks (such as It performs typical emergency services related tasks (such as
location-based routing), and adds additional data, namely service and location-based routing), and adds additional data, namely service and
subscriber information as well as data provider information #2, to subscriber information as well as data provider information #2, to
the outgoing message. For the example we assume a VoIP service the outgoing message. For the example we assume a VoIP service
provider that deploys a back-to-back user agent allowing additional provider that deploys a back-to-back user agent allowing additional
data to be included in the body of the SIP message (rather than by data to be included in the body of the SIP message (rather than by
reference), which allows us to illustrate the use of multiple data reference), which allows us to illustrate the use of multiple data
provider info blocks. The resulting message is shown in Figure 17. provider info blocks. The resulting message is shown in Figure 17.
The SIP INVITE is sent to the PSAP in step #3. 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> Call-Info: <http://wwww.example.com/hannes/photo.jpg>;
;purpose=icon, 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
<cid:0123456789@atlanta.example.com> <cid:0123456789@atlanta.example.com>;
;purpose=EmergencyCallData.DeviceInfo purpose=EmergencyCallData.DeviceInfo
Call-Info: <cid:bloorpyhex@atlanta.example.com> Call-Info: <cid:bloorpyhex@atlanta.example.com>;
;purpose=EmergencyCallData.ServiceInfo purpose=EmergencyCallData.ServiceInfo
Call-Info: <cid:aaabbb@atlanta.example.com> Call-Info: <cid:aaabbb@atlanta.example.com>;
;purpose=EmergencyCallData.ProviderInfo purpose=EmergencyCallData.ProviderInfo
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: ...
--boundary1
Content-Type: application/sdp
...SDP goes here --boundary1
Content-Type: application/sdp
--boundary1-- ...SDP goes here
Content-Type: application/EmergencyCallData.DeviceInfo+xml --boundary1
Content-ID: <0123456789@atlanta.example.com> Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-Disposition: by-reference;handling=optional Content-ID: <0123456789@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?> Content-Disposition: by-reference;handling=optional
<dev:EmergencyCallData.DeviceInfo <?xml version="1.0" encoding="UTF-8"?>
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"> <dev:EmergencyCallData.DeviceInfo
<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119] xmlns:dev=
</dev:DataProviderReference> "urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo">
<dev:DeviceClassification>laptop</dev:DeviceClassification> <dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
<dev:UniqueDeviceID </dev:DataProviderReference>
<dev:DeviceClassification>laptop</dev:DeviceClassification>
<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-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional
Content-Type: application/EmergencyCallData.ProviderInfo+xml <?xml version="1.0" encoding="UTF-8"?>
Content-ID: <1234567890@atlanta.example.com> <pi:EmergencyCallData.ProviderInfo
Content-Disposition: by-reference;handling=optional xmlns:pi=
<?xml version="1.0" encoding="UTF-8"?> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<pi:EmergencyCallData.ProviderInfo <pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> </pi:DataProviderReference>
<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119] <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderReference> </pi:DataProviderString>
<pi:DataProviderString>Hannes Tschofenig <pi:TypeOfProvider>Client</pi:TypeOfProvider>
</pi:DataProviderString> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:TypeOfProvider>Client</pi:TypeOfProvider> <pi:Language>en</pi:Language>
<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI> <pi:DataProviderContact
<pi:Language>en</pi:Language>
<pi: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/>
<suffix>Dipl. Ing.</suffix> <suffix>Dipl. Ing.</suffix>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>de</language-tag> <language-tag>de</language-tag>
</lang> </lang>
<lang> <lang>
<parameters><pref><integer>2</integer></pref> <parameters><pref><integer>2</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>Hannes Tschofenig <label><text>Hannes Tschofenig
Linnoitustie 6 Linnoitustie 6
Espoo, Finland Espoo, Finland
02600</text></label> 02600</text></label>
</parameters>
<pobox/>
<ext/>
<street>Linnoitustie 6</street>
<locality>Espoo</locality>
<region>Uusimaa</region>
<code>02600</code>
<country>Finland</country>
</adr>
<adr>
<parameters>
<type><text>home</text></type>
<label><text>Hannes Tschofenig
c/o Hotel DuPont
42 W 11th St
Wilmington, DE 19801
USA</text></label>
</parameters>
<pobox/>
<ext/>
<street>42 W 11th St</street>
<locality>Wilmington</locality>
<region>DE</region>
<code>19801</code>
<country>USA</country>
</adr>
<tel>
<parameters>
<type>
<text>work</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+358 50 4871445</uri>
</tel>
<tel>
<parameters>
<type>
<text>home</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+1 555 555 0123</uri>
</tel>
<email>
<parameters><type><text>work</text></type>
</parameters>
<text>hannes.tschofenig@nsn.com</text>
</email>
<geo>
<parameters><type><text>work</text></type>
</parameters>
<uri>geo:60.210796,24.812924</uri>
</geo>
<geo>
<parameters><type><text>home</text></type>
</parameters>
<uri>geo:39.746537,-75.548027</uri>
</geo>
<key>
<parameters>
<type><text>home</text></type>
</parameters>
<uri>https://www.example.com/key.asc
</uri>
</key>
<tz><text>Finland/Helsinki</text></tz>
<url>
<parameters><type><text>home</text></type>
</parameters>
<uri>http://example.com/hannes.tschofenig
</uri>
</url>
</vcard>
</pi:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo>
--boundary1-- </parameters>
<pobox/>
<ext/>
<street>Linnoitustie 6</street>
<locality>Espoo</locality>
<region>Uusimaa</region>
<code>02600</code>
<country>Finland</country>
</adr>
<adr>
<parameters>
<type><text>home</text></type>
<label><text>Hannes Tschofenig
c/o Hotel DuPont
42 W 11th St
Wilmington, DE 19801
USA</text></label>
</parameters>
<pobox/>
<ext/>
<street>42 W 11th St</street>
<locality>Wilmington</locality>
<region>DE</region>
<code>19801</code>
<country>USA</country>
</adr>
<tel>
<parameters>
<type>
<text>work</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+358 50 4871445</uri>
</tel>
<tel>
<parameters>
<type>
<text>home</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+1 555 555 0123</uri>
</tel>
<email>
<parameters><type><text>work</text></type>
</parameters>
<text>hannes.tschofenig@nsn.com</text>
Content-Type: application/EmergencyCallData.ServiceInfo+xml </email>
Content-ID: <bloorpyhex@atlanta.example.com> <geo>
Content-Disposition: by-reference;handling=optional <parameters><type><text>work</text></type>
<?xml version="1.0" encoding="UTF-8"?> </parameters>
<svc:EmergencyCallData.ServiceInfo <uri>geo:60.210796,24.812924</uri>
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"> </geo>
<svc:DataProviderReference>string0987654321@example.org <geo>
</svc:DataProviderReference> <parameters><type><text>home</text></type>
<svc:ServiceEnvironment>Residence</svc:ServiceEnvironment> </parameters>
<svc:ServiceType>VOIP</svc:ServiceType> <uri>geo:39.746537,-75.548027</uri>
<svc:ServiceMobility>Unknown</svc:ServiceMobility> </geo>
<key>
<parameters>
<type><text>home</text></type>
</parameters>
<uri>https://www.example.com/key.asc</uri>
</key>
<tz><text>Finland/Helsinki</text></tz>
<url>
<parameters><type><text>home</text></type>
</parameters>
<uri>http://example.com/hannes.tschofenig</uri>
</url>
</vcard>
</pi:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo>
</svc:EmergencyCallData.ServiceInfo> --boundary1
Content-Type: application/EmergencyCallData.ServiceInfo+xml
Content-ID: <bloorpyhex@atlanta.example.com>
Content-Disposition: by-reference;handling=optional
--boundary1-- <?xml version="1.0" encoding="UTF-8"?>
<svc:EmergencyCallData.ServiceInfo
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo">
<svc:DataProviderReference>string0987654321@example.org
</svc:DataProviderReference>
<svc:ServiceEnvironment>Residence</svc:ServiceEnvironment>
<svc:ServiceType>VOIP</svc:ServiceType>
<svc:ServiceMobility>Unknown</svc:ServiceMobility>
</svc:EmergencyCallData.ServiceInfo>
Content-Type: application/EmergencyCallData.ProviderInfo+xml --boundary1
Content-ID: <aaabbb@atlanta.example.com> Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-Disposition: by-reference;handling=optional Content-ID: <aaabbb@atlanta.example.com>
<?xml version="1.0" encoding="UTF-8"?> Content-Disposition: by-reference;handling=optional
<pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> <?xml version="1.0" encoding="UTF-8"?>
<pi:DataProviderReference>string0987654321@example.org <pi:EmergencyCallData.ProviderInfo
</pi:DataProviderReference> xmlns:pi=
<pi:DataProviderString>Exemplar VoIP Provider "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
</pi:DataProviderString> <pi:DataProviderReference>string0987654321@example.org
<pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID> </pi:DataProviderReference>
<pi:ProviderIDSeries>NENA</pi:ProviderIDSeries> <pi:DataProviderString>Exemplar VoIP Provider
<pi:TypeOfProvider>Service Provider</pi:TypeOfProvider> </pi:DataProviderString>
<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI> <pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID>
<pi:Language>en</pi:Language> <pi:ProviderIDSeries>NENA</pi:ProviderIDSeries>
<pi:DataProviderContact <pi:TypeOfProvider>Service Provider</pi:TypeOfProvider>
<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI>
<pi:Language>en</pi:Language>
<pi: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>John Doe</text></fn> <fn><text>John Doe</text></fn>
<n> <n>
<surname>John</surname> <surname>John</surname>
<given>Doe</given> <given>Doe</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix/> <suffix/>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<org> <org>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>Exemplar VoIP Provider</text> <text>Exemplar VoIP Provider</text>
</org> </org>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>John Doe <label><text>John Doe
123 Middle Street 123 Middle Street
The Sticks, IA 50055</text></label> The Sticks, IA 50055</text></label>
</parameters> </parameters>
<pobox/> <pobox/>
<ext/> <ext/>
<street>123 Middle Street</street> <street>123 Middle Street</street>
<locality>the Sticks</locality> <locality>the Sticks</locality>
<region>IA</region> <region>IA</region>
<code>50055</code> <code>50055</code>
<country>USA</country> <country>USA</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> <text>main-number</text>
</parameters> </type>
<uri>sips:john.doe@example.com</uri> </parameters>
</tel> <uri>sips:john.doe@example.com</uri>
<email> </tel>
<parameters><type><text>work</text></type> <email>
</parameters> <parameters><type><text>work</text></type>
<text>john.doe@example.com</text> </parameters>
</email> <text>john.doe@example.com</text>
<geo> </email>
<parameters><type><text>work</text></type> <geo>
</parameters> <parameters><type><text>work</text></type>
<uri>geo:41.761838,-92.963268</uri> </parameters>
</geo> <uri>geo:41.761838,-92.963268</uri>
<tz><text>America/Chicago</text></tz> </geo>
<url> <tz><text>America/Chicago</text></tz>
<parameters><type><text>home</text></type> <url>
</parameters> <parameters><type><text>home</text></type>
<uri>http://www.example.com/john.doe</uri> </parameters>
</url> <uri>http://www.example.com/john.doe</uri>
</vcard> </url>
</pi:DataProviderContact> </vcard>
</pi:EmergencyCallData.ProviderInfo> </pi:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo>
--boundary1--
Figure 17: VoIP Provider sending SIP INVITE with Additional Data Figure 17: 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 provider. The response is shown in Figure 18. Along with network provider. The response is shown in Figure 18. 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. This request and response is <provided-by> element of the PIDF-LO. This request and response is
step #4. 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>
<civicAddress <civicAddress
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>US</country> <country>US</country>
<A1>DE</A1> <A1>DE</A1>
<A3>Wilmington</A3> <A3>Wilmington</A3>
<PRD>W</PRD> <PRD>W</PRD>
<RD>11th</RD> <RD>11th</RD>
<STS>Street</STS> <STS>Street</STS>
<HNO>42</HNO> <HNO>42</HNO>
<NAM>The Hotel DuPont</NAM> <NAM>The Hotel DuPont</NAM>
<PC>19801</PC> <PC>19801</PC>
</civicAddress> </civicAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules> <gp:usage-rules>
<gbp:retransmission-allowed>true <gbp:retransmission-allowed>true
</gbp:retransmission-allowed> </gbp:retransmission-allowed>
<gbp:retention-expiry>2013-12-10T20:00:00Z <gbp:retention-expiry>2013-12-10T20:00:00Z
</gbp:retention-expiry> </gbp:retention-expiry>
</gp:usage-rules> </gp:usage-rules>
<gp:method>802.11</gp:method> <gp:method>802.11</gp:method>
<gp:provided-by <gp:provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo" purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2" /> ref="https://example.com/ref2" />
<EmergencyCallDataValue> <EmergencyCallDataValue>
<EmergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns= xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>88QV4FpfZ976T@example.com <DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference> </DataProviderReference>
<DataProviderString>Diamond State Exemplar <DataProviderString>Diamond State Exemplar
</DataProviderString> </DataProviderString>
<ProviderID>urn:nena:companyid:diamond</ProviderID> <ProviderID>urn:nena:companyid:diamond</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Access Network Provider</TypeOfProvider> <TypeOfProvider>Access Network Provider</TypeOfProvider>
<ContactURI>tel:+1-302-555-0000</ContactURI> <ContactURI>tel:+1-302-555-0000</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>88QV4FpfZ976T@example.com <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>
</gp:provided-by> </gp:provided-by>
</gp:geopriv>
<dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID> </gp:geopriv>
<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp> <dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID>
</dm:device> <dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>
</dm:device>
</presence> </presence>
Figure 18: Access Network Provider returning PIDF-LO with Additional Figure 18: Access Network Provider returning PIDF-LO with Additional
Data Data
7. XML Schemas 8. 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.
7.1. EmergencyCallData.ProviderInfo XML Schema 8.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 54, line 29 skipping to change at page 55, line 25
<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 19: EmergencyCallData.ProviderInfo XML Schema. Figure 19: EmergencyCallData.ProviderInfo XML Schema.
7.2. EmergencyCallData.ServiceInfo XML Schema 8.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" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
skipping to change at page 55, line 44 skipping to change at page 56, line 44
<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: EmergencyCallData.ServiceInfo XML Schema. Figure 20: EmergencyCallData.ServiceInfo XML Schema.
7.3. EmergencyCallData.DeviceInfo XML Schema 8.3. EmergencyCallData.DeviceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" "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" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
skipping to change at page 57, line 9 skipping to change at page 58, line 9
<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 21: EmergencyCallData.DeviceInfo XML Schema. Figure 21: EmergencyCallData.DeviceInfo XML Schema.
7.4. EmergencyCallData.SubscriberInfo XML Schema 8.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= xmlns:sub=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" "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"
skipping to change at page 58, line 14 skipping to change at page 59, line 14
<xs:attribute name="privacyRequested" type="xs:boolean" <xs:attribute name="privacyRequested" type="xs:boolean"
use="required"/> use="required"/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 22: EmergencyCallData.SubscriberInfo XML Schema. Figure 22: EmergencyCallData.SubscriberInfo XML Schema.
7.5. EmergencyCallData.Comment XML Schema 8.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" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
skipping to change at page 59, line 46 skipping to change at page 60, line 46
<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 23: EmergencyCallData.Comment XML Schema. Figure 23: EmergencyCallData.Comment XML Schema.
7.6. provided-by XML Schema 8.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 61, line 41 skipping to change at page 62, line 41
<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 24: provided-by XML Schema Figure 24: provided-by XML Schema
8. Security Considerations 9. Security Considerations
The data structures described in this document contain information The data structures described in this document contain information
usually considered private. When information is provided by value, usually considered private. When information is provided by value,
entities that are a party to the SIP signaling (such as proxy servers entities that are a party to the SIP signaling (such as proxy servers
and back-to-back user agents) will have access to it and need to and back-to-back user agents) will have access to it and need to
protect it against inappropriate disclosure. An entity that is able protect it against inappropriate disclosure. An entity that is able
to eavesdrop on the SIP signaling will also have access. Some access to eavesdrop on the SIP signaling will also have access. Some access
types (such as in-the-clear Wi-Fi) are more vulnerable than others types (such as in-the-clear Wi-Fi) are more vulnerable than others
(such as 3G or 4G cellular data traffic) to eavesdropping. (such as 3G or 4G cellular data traffic) to eavesdropping.
Mechanisms that protect against eavesdropping (such as Transport Mechanisms that protect against eavesdropping (such as Transport
Layer Security (TLS)) SHOULD be preferentially used whenever Layer Security (TLS) version 1.2 or later) SHOULD be preferentially
feasible. (This requirement is not a "MUST" because there is an used whenever feasible. (This requirement is not a "MUST" because
existing deployed base of clear-text SIP, and also because, as an there is an existing deployed base of clear-text SIP, and also
emergency call, it is more important for the call to go through than because, as an emergency call, it is more important for the call to
for it to be protected; e.g., the call MUST proceed even if the TLS go through than for it to be protected; e.g., the call MUST proceed
negotiation or certificate verification fails for whatever reason.) even if the TLS negotiation or certificate verification fails for
When information is provided by reference, HTTPS is REQUIRED for whatever reason.) When information is provided by reference, TLS
dereferencing, and the provider of the information is REQUIRED to mutual authentication is REQUIRED. That is, HTTPS is REQUIRED for
validate the credentials of the requester. While the creation of a dereferencing, the requestor MUST use a client certificate to
public key infrastructure (PKI) that has global scope may be authenticate the HTTP request, and the provider of the information is
difficult, the alternatives to creating devices and services that can REQUIRED to validate the credentials provided by the requester.
provide critical information securely are more daunting. The While the creation of a public key infrastructure (PKI) that has
provider of the information MAY enforce any policy it wishes to use, global scope might be difficult, the alternatives to creating devices
but PSAPs and responder agencies SHOULD deploy a PKI so that and services that can provide critical information securely are more
providers of additional data can check the certificate of the client daunting. The provider of the information MAY enforce any policy it
(the requester) and decide the appropriate policy to enforce based on wishes to use, but PSAPs and responder agencies are strongly advised
that certificate. to deploy a PKI so that providers of additional data can check the
certificate of the client (the requester) and decide the appropriate
policy to enforce based on that certificate.
TLS MUST be version 1.2 or later. TLS MUST be version 1.2 or later.
It is RECOMMENDED to use only cipher suites that offer Perfect
Forward Secrecy (PFS) and avoid Cipher Block Chaining (CBC), and to
follow the recommendations in BCP 195 [RFC7525].
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 are sufficient; the circumstances, nationally recognized credentials are sufficient; the
emergency services community within a country can arrange a PKI, data emergency services community within a country can arrange a PKI, data
providers can be provisioned with the root CA public key for the providers can be provisioned with the root CA public key for the
country. Some nations are developing a PKI for this, and related, country. Some nations are developing a PKI for this, and related,
purposes. Since calls could be made from devices where the device purposes. Since calls could be made from devices where the device
and/or the service provider(s) are not local to the emergency and/or the service provider(s) are not local to the emergency
services authorities, globally recognized credentials are useful. services authorities, globally recognized credentials are useful.
skipping to change at page 63, line 4 skipping to change at page 64, line 11
emergency services to know that it is receiving data from an emergency services to know that it is receiving data from an
authorized server. The emergency services authorities could provide authorized server. The emergency services authorities could provide
credentials, distinguishable from credentials provided to emergency credentials, distinguishable from credentials provided to emergency
responders and PSAPs, which could be used to validate data providers. responders and PSAPs, which could be used to validate data providers.
Such credentials would have to be acceptable to any PSAP or responder Such credentials would have to be acceptable to any PSAP or responder
that could receive a call with additional data supplied by that that could receive a call with additional data supplied by that
provider. This would be extensible to global credential validation provider. This would be extensible to global credential validation
using the forest guide as mentioned above. In the absence of such using the forest guide as mentioned above. In the absence of such
credentials, the emergency services authorities could maintain a list credentials, the emergency services authorities could maintain a list
of local data providers' credentials as provided to them out of band. of local data providers' credentials as provided to them out of band.
At a minimum, the emergency services authorities could obtain a At a minimum, the emergency services authorities could obtain a
credential from the DNS entry of the domain in the Additional Data credential from the DNS entry of the domain in the Additional Data
URI to at least validate that the server is known to the domain URI (e.g., using DANE [RFC6698]) to at least validate that the server
providing the URI. 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 as for service providers, and while the solutions validation issues as for service providers, and while the solutions
are the same, the challenges of doing so for every device are are the same, the challenges of doing so for every device are
obviously more difficult, especially when considering root obviously more difficult, especially when considering root
certificate updates, revocation lists, etc. However, in general, certificate updates, revocation lists, etc. However, in general,
devices are not expected to provide data directly by reference, but devices are not expected to provide data directly by reference, but
rather, to either provide data by value, or upload the data to a rather, to either provide data by value, or upload the data to a
server which can more reliably make it available and more easily server which can more reliably make it available and more easily
enforce security policy. Devices which do provide data directly by enforce security policy. Devices which do provide data directly by
reference, which might include fixed-location sensors, will need to reference, which might include fixed-location sensors, will need to
be capable of handling this. be capable of handling this.
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 Neither service providers nor devices will supply private information
unless the call is recognized as an emergency call. In cellular unless the call is recognized as an emergency call. In cellular
telephony systems (such as those using 3GPP IMS), there are different telephony systems (such as those using 3GPP IMS), there are different
procedures for an originating device to place an emergency versus a procedures for an originating device to place an emergency versus a
normal call. If a call that is really an emergency call is initiated normal call. If a call that is really an emergency call is initiated
as a normal call and the cellular service provider recognizes this, as a normal call and the cellular service provider recognizes this,
3GPP IMS permits the service provider to either accept the call 3GPP IMS permits the service provider to either accept the call
anyway or reject it with a specific code that instructs the device to anyway or reject it with a specific code that instructs the device to
retry the call as an emergency call. Service providers ought to retry the call as an emergency call. Service providers ought to
choose the latter, because otherwise the device will not have choose the latter, because otherwise the device will not have
included the information specified in this document (since the device included the information specified in this document (since the device
didn't recognize the call as being an emergency call). didn't recognize the call as being an emergency call).
9. Privacy Considerations 10. Privacy Considerations
This document enables functionality for conveying additional This document enables functionality for conveying additional
information about the caller and the caller's device and service to information about the caller and the caller's device and service to
the callee. Some of this information is personal data and therefore the callee. Some of this information is personal data and therefore
privacy concerns arise. An explicit privacy indicator for privacy concerns arise. An explicit privacy indicator for
information directly relating to the caller's identity is defined and information directly relating to the caller's identity is defined and
use is mandatory. However, observance of this request for privacy use is mandatory. However, observance of this request for privacy
and which information it relates to is determined by the destination and which information it relates to is determined by the destination
jurisdiction (which replicates functionality provided in some legacy jurisdiction (which replicates functionality provided in some legacy
emergency services systems). emergency services systems).
skipping to change at page 64, line 28 skipping to change at page 65, line 28
described in more detail in [RFC6973]. described in more detail in [RFC6973].
Stored Data Compromise: There is an increased risk of stored data Stored Data Compromise: There is an increased risk of stored 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 providers, 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 can 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 could feel uncomfortable with this
degree of information sharing even in emergency services degree of information sharing even in emergency services
situations. situations.
Secondary Use: There is a risk of secondary use, which is the use of Secondary Use: There is a risk of secondary use, which is the use of
collected information about an individual without the individual's collected information about an individual without the individual's
consent for a purpose different from that for which the consent for a purpose different from that for which the
information was collected. The stated purpose of the additional information was collected. The stated purpose of the additional
data is for emergency services purposes but theoretically the same data is for emergency services purposes, but theoretically the
information could be used for any other call as well. same information could be used for any other call as well.
Additionally, parties involved in the emergency call may retain Additionally, parties involved in the emergency call could retain
the obtained information and may re-use it for other, non- the obtained information and re-use it for other, non-emergency
emergency services purposes. services purposes. While technical measures are not in place to
prevent such secondary re-use, policy, legal, regulatory, and
other non-technical approaches can be effective.
Disclosure: When the data defined in this document is not properly Disclosure: When the data defined in this document is not properly
protected (while in transit with traditional communication protected (while in transit with traditional communication
security techniques, and while stored using access control security techniques, and while stored using access control
mechanisms) there is the risk of disclosure, which is the mechanisms) there is the risk of disclosure, which is the
revelation of private information about an individual. revelation of private information about an 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, network or PSAP functionality can inspect identifying information, network or PSAP functionality can inspect
privacy flags within the SIP headers to determine what information privacy flags within the SIP headers to determine what information
may be passed, stored, or displayed to comply with local policy or can be passed, stored, or displayed to comply with local policy or
law. RFC 3325 [RFC3325] defines the "id" priv-value token. The law. RFC 3325 [RFC3325] defines the "id" priv-value token. 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 contain privacy- This document defines various data structures that contain privacy-
sensitive data. For example, identifiers for the device (e.g., sensitive data. For example, identifiers for the device (e.g.,
serial number, MAC address) or account/SIM (e.g., IMSI), contact serial number, MAC address) or account/SIM (e.g., IMSI), contact
information for the user, location of the caller. Local regulations information for the user, location of the caller. Local regulations
skipping to change at page 65, line 45 skipping to change at page 66, line 46
or missing input parsing (such as SQL injection attacks). The risks or missing input parsing (such as SQL injection attacks). The risks
of data breaches is increased with the obligation for emergency of data breaches is increased with the obligation for emergency
services to retain emergency call related data for extended periods services to retain emergency call related data for extended periods
(e.g., several years are the norm). (e.g., several years are the norm).
Finally, it is also worth highlighting 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 reference (a URL in the SIP signaling). When data is signaling or by reference (a URL in the SIP signaling). When data is
sent by value, all intermediaries have access to the data. As such, sent by value, all intermediaries have access to the data. As such,
these intermediaries may also introduce additional privacy risk. these intermediaries could also introduce additional privacy risk.
Therefore, in situations where the conveyed information is privacy- Therefore, in situations where the conveyed information is privacy-
sensitive and intermediaries are involved, transmitting by reference sensitive and intermediaries are involved, transmitting by reference
might be appropriate, assuming the source of the data can operate a might be appropriate, assuming the source of the data can operate a
sufficient dereferencing infrastructure and that proper access sufficient dereferencing infrastructure and that proper access
control policies are available for distinguishing the different control policies are available for distinguishing the different
entities dereferencing the reference. Without access control entities dereferencing the reference. Without access control
policies any party in possession of the reference is able to resolve policies any party in possession of the reference is able to resolve
the reference and to obtain the data, including intermediaries. the reference and to obtain the data, including intermediaries.
10. IANA Considerations 11. IANA Considerations
10.1. Registry creation 11.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.
10.1.1. Provider ID Series Registry 11.1.1. Provider ID Series Registry
This document creates a new sub-registry called "Provider ID Series". This document creates a new sub-registry called "Provider ID Series".
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the entity requesting a new rules. The expert should determine that the entity requesting a new
value is a legitimate issuer of service provider IDs suitable for use value is a legitimate issuer of service provider IDs suitable for use
in Additional Call Data. in Additional Call Data.
Private entities issuing or using internally-generated IDs are Private entities issuing or using internally-generated IDs are
encouraged to register here and to ensure that all IDs they issue or encouraged to register here and to ensure that all IDs they issue or
use are unique. This guarantees that IDs issued or used by the use are unique. This guarantees that IDs issued or used by the
skipping to change at page 66, line 44 skipping to change at page 67, line 45
The content of this registry includes: The content of this registry includes:
Name: An identifier to be used in the 'ProviderIDSeries' element. Name: An identifier to be used in the 'ProviderIDSeries' 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 1. The initial set of values is listed in Figure 1.
10.1.2. Service Environment Registry 11.1.2. Service Environment Registry
This document creates a new sub-registry called "Service This document creates a new sub-registry called "Service
Environment". As defined in [RFC5226], this registry operates under Environment". As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the entity "Expert Review" rules. The expert should determine that the entity
requesting a new value is relevant for this service element, and that requesting a new value is relevant for this service element (e.g., a
the new value is distinct from existing values, and its use is recognized emergency services related SDO), and that the new value is
unambiguous. 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 the <ServiceEnvironment> element. Token: The value to be used in the <ServiceEnvironment> element.
Description: A short description of the value. Description: A short description of the value.
The initial set of values is listed in Figure 4. The initial set of values is listed in Figure 4.
10.1.3. Service Type Registry 11.1.3. Service Type Registry
This document creates a new sub-registry called "Service Type". As This document creates a new sub-registry called "Service Type". As
defined in [RFC5226], this registry operates under "Expert Review" defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the entity requesting a new rules. The expert should determine that the entity requesting a new
value is relevant for this service element and that the requested value is relevant for this service element (e.g., a recognized
value is clearly distinct from other values so that there is no emergency services related SDO) and that the requested value is
ambiguity as to when the value is to be used or which value is to be clearly distinct from other values so that there is no ambiguity as
used. to when the value is to be used or which value is to be used.
The content of this registry includes: The content of this registry includes:
Name: The value to be used in the <ServiceType> element. Name: The value to be used in the <ServiceType> element.
Description: A short description of the value. Description: A short description of the value.
The initial set of values is listed in Figure 5. The initial set of values is listed in Figure 5.
10.1.4. Service Mobility Registry 11.1.4. Service Mobility Registry
This document creates a new sub-registry called "Service Mobility". This document creates a new sub-registry called "Service Mobility".
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should determine that the entity requesting a new rules. The expert should determine that the entity requesting a new
value is relevant for this service element and that the requested value is relevant for this service element (e.g., a recognized
value is clearly distinct from other values so that there is no emergency services related SDO) and that the requested value is
ambiguity as to when the value is to be used or which value is to be clearly distinct from other values so that there is no ambiguity as
used. to when the value is to be used or which value is to be used.
The content of this registry includes: The content of this registry includes:
Token: The value used in the <ServiceMobility> element. Token: The value used in the <ServiceMobility> element.
Description: A short description of the value. Description: A short description of the value.
The initial set of values is listed in Figure 6. The initial set of values is listed in Figure 6.
10.1.5. Service Provider Type Registry 11.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:
Token: The value used in the <TypeOfProvider> element. Token: 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 2. The initial set of values is defined in Figure 2.
10.1.6. Device Classification Registry 11.1.6. 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:
Token: Value used in the <DeviceClassification> element. 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 8. The initial set of values are defined in Figure 8.
10.1.7. Device ID Type Type Registry 11.1.7. Device ID Type Type Registry
This document creates a new sub-registry called "Device ID Type". As This document creates a new sub-registry called "Device ID Type". As
defined in [RFC5226], this registry operates under "Expert Review" defined in [RFC5226], this registry operates under "Expert Review"
rules. The expert should ascertain that the proposed type is well rules. The expert should ascertain that the proposed type is well
understood, and provides information which PSAPs and responders are understood, and provides information which PSAPs and responders are
able to use to uniquely identify a device. (For example, a biometric able to use to uniquely identify a device. (For example, a biometric
fingerprint used to authenticate a device would not normally be fingerprint used to authenticate a device would not normally be
useful by a PSAP or responder to identify a device.) useful by a PSAP or responder to identify a device.)
The content of this registry includes: The content of this registry includes:
Token: The value to be placed in the <TypeOfDeviceID> element. Token: The value to be placed in the <TypeOfDeviceID> element.
Description: Short description identifying the type of the device Description: Short description identifying the type of the device
ID. ID.
The initial set of values are defined in Figure 9. The initial set of values are defined in Figure 9.
10.1.8. Device/Service Data Type Registry 11.1.8. 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". As defined in [RFC5226], this registry operates under Type". As defined in [RFC5226], this registry operates under
"Specification Required" rules, which include an explicit expert "Specification Required" rules, which include an explicit expert
review. The designated expert should ascertain that the proposed review. The designated expert should ascertain that the proposed
type is well understood, and provides information useful to PSAPs and type is well understood, and provides information useful to PSAPs and
responders. The specification must contain a complete description of responders. The specification must contain a complete description of
the data, and a precise format specification suitable to allow the data, and a precise format specification suitable to allow
interoperable implementations. interoperable implementations.
The content of this registry includes: The content of this registry includes:
Token: The value to be placed in the <DeviceSpecificType> element. Token: The value to be placed in the <DeviceSpecificType> element.
Description: Short description identifying the data. Description: Short description identifying 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 10. The initial set of values are listed in Figure 10.
10.1.9. Emergency Call Data Types Registry 11.1.9. Emergency Call Data Types Registry
This document creates a new sub-registry called 'Emergency Call Data This document creates a new sub-registry called 'Emergency Call Data
Types'. As defined in [RFC5226], this registry operates under Types'. As defined in [RFC5226], this registry operates under
"Specification Required" rules, which include an explicit expert "Specification Required" rules, which include an explicit expert
review. The expert is responsible for verifying that the document review. The expert is responsible for verifying that the document
contains a complete and clear specification and the proposed contains a complete and clear specification and the proposed
functionality does not obviously duplicate existing functionality. functionality does not obviously duplicate existing functionality.
The expert is also responsible for verifying that the block is The expert is also responsible for verifying that the block is
correctly categorized per the description of the categories in correctly categorized per the description of the categories in
Section 1. Section 1.
The registry contains an entry for every data block that can be sent The registry contains an entry for every data block that can be sent
with an emergency call using the mechanisms as specified in this with an emergency call using the mechanisms as specified in this
document. Each data block is identified by the "root" of its MIME document. Each data block is identified by the "root" of its MIME
subtype (which is the part after 'EmergencyCallData.'). If the MIME media subtype (which is the part after 'EmergencyCallData.'). If the
subtype does not start with 'EmergencyCallData.', then it cannot be MIME media subtype does not start with 'EmergencyCallData.', then it
registered here nor used in a Call-Info header field as specified in cannot be registered here nor used in a Call-Info header field as
this document. The subtype MAY exist under any MIME media type specified in this document. The subtype MAY exist under any MIME
(although most commonly these are under 'Application/' this is NOT media type (although most commonly these are under 'Application/'
REQUIRED), however, to be added to the registry the "root" needs to this is NOT REQUIRED), however, to be added to the registry the
be unique regardless of the MIME media type. "root" needs to be unique regardless of the MIME media type.
The content of this registry includes: The content of this registry includes:
Token: The root of the data's MIME subtype (not including the Token: The root of the data's MIME media subtype (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') 'EmergencyCallData' prefix and any suffix such as '+xml')
Data About: A hint as to if the block is considered descriptive of Data About: A hint as to if the block is considered descriptive of
the call, the caller, or the location (or is applicable to more the call, the caller, or the location (or is applicable to more
than one), which may help PSAPs and other entities determine if than one), which can help PSAPs and other entities determine if
they wish to process the block. Note that this is only a hint; they wish to process the block. Note that this is only a hint;
entities need to consider the block's contents, not just this entities need to consider the block's contents, not just this
field, when determining if they wish to process the block (which field, when determining if they wish to process the block (which
is why the field only exists in the registry, and is not contained is why the field only exists in the registry, and is not contained
within the block). The value MUST be either "The Call", "The within the block). The value MUST be either "The Call", "The
Caller", "The Location", or "Multiple". New values are created by Caller", "The Location", or "Multiple". New values are created by
extending this registry in a subsequent RFC. extending this registry in a subsequent RFC.
Reference: The document that describes the data object Reference: The document that describes the data object
Note that the tokens in this registry are part of the Note that the tokens in this registry are part of the
'EmergencyCallData' compound value; when used as a value of the 'EmergencyCallData' compound value; when used as a value of the
'purpose' parameter of a Call-Info header field, the values listed in 'purpose' parameter of a Call-Info header field, the values listed in
this registry are prefixed by 'EmergencyCallData.' per the this registry are prefixed by 'EmergencyCallData.' per the
'EmergencyCallData' registation Section 10.2. 'EmergencyCallData' registration Section 11.2.
The initial set of values are listed in Figure 25. The initial set of values are listed in Figure 25.
+----------------+--------------+------------+ +----------------+--------------+------------+
| Token | Data About | Reference | | Token | Data About | Reference |
+----------------+--------------+------------+ +----------------+--------------+------------+
| ProviderInfo | The Call | [This RFC] | | ProviderInfo | The Call | [This RFC] |
| ServiceInfo | The Call | [This RFC] | | ServiceInfo | The Call | [This RFC] |
| DeviceInfo | The Call | [This RFC] | | DeviceInfo | The Call | [This RFC] |
| SubscriberInfo | The Call | [This RFC] | | SubscriberInfo | The Call | [This RFC] |
| Comment | The Call | [This RFC] | | Comment | The Call | [This RFC] |
+----------------+--------------+------------+ +----------------+--------------+------------+
Figure 25: Additional Data Blocks Registry Figure 25: Additional Data Blocks Registry
10.2. 'EmergencyCallData' Purpose Parameter Value 11.2. 'EmergencyCallData' Purpose Parameter Value
This document defines the 'EmergencyCallData' value for the 'purpose' This document defines the 'EmergencyCallData' value for the 'purpose'
parameter of the Call-Info header field [RFC3261]. IANA has added parameter of the Call-Info header field [RFC3261]. IANA has added
this document to the list of references for the 'purpose' value of this document to the list of references for the 'purpose' value of
Call-Info in the Header Field Parameters and Parameter Values sub- Call-Info in the Header Field Parameters and Parameter Values sub-
registry of the Session Initiation Protocol (SIP) Parameters registry of the Session Initiation Protocol (SIP) Parameters
registry. Note that 'EmergencyCallData' is a compound value; when registry. Note that 'EmergencyCallData' is a compound value; when
used as a value of the 'purpose' parameter of a Call-Info header used as a value of the 'purpose' parameter of a Call-Info header
field, 'EmergencyCallData' is immediately followed by a dot ('.') and field, 'EmergencyCallData' is immediately followed by a dot ('.') and
a value from the 'Emergency Call Data Types' registry Section 10.1.9. a value from the 'Emergency Call Data Types' registry Section 11.1.9.
10.3. URN Sub-Namespace Registration for <provided-by> Registry Entry 11.3. URN Sub-Namespace Registration for <provided-by> Registry Entry
This section registers the namespace specified in Section 10.5.1 in This section registers the namespace specified in Section 11.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> element used by this document is The schema for the <provided-by> element used by this document is
specified in Section 7.6. specified in Section 8.6.
10.4. MIME Registrations 11.4. MIME Registrations
10.4.1. MIME Content-type Registration for 'application/ 11.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 media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.ProviderInfo+xml MIME media subtype name: EmergencyCallData.ProviderInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset (indicates the character encoding of Optional parameters: charset (indicates the character encoding of
the contents) the contents)
Encoding considerations: Uses XML, which can contain 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2 characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303]. 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 may additional data about an emergency call. Since this data can
contain personal information, appropriate precautions might be contain personal information, appropriate precautions are needed
needed to limit unauthorized access, inappropriate disclosure, and to limit unauthorized access, inappropriate disclosure, and
eavesdropping of personal information. Please refer to Section 8 eavesdropping of personal information. Please refer to Section 9
and Section 9 for more information. and Section 10 for more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
skipping to change at page 72, line 16 skipping to change at page 73, line 16
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <iesg@ietf.org>
10.4.2. MIME Content-type Registration for 'application/ 11.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 media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.ServiceInfo+xml MIME media subtype name: EmergencyCallData.ServiceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset (indicates the character encoding of Optional parameters: charset (indicates the character encoding of
the contents) the contents)
Encoding considerations: Uses XML, which can contain 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2 characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303]. 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 may contain data about an emergency call. Since this data can contain
personal information, appropriate precautions may be needed to personal information, appropriate precautions are needed to limit
limit unauthorized access, inappropriate disclosure, and unauthorized access, inappropriate disclosure, and eavesdropping
eavesdropping of personal information. Please refer to Section 8 of personal information. Please refer to Section 9 and Section 10
and Section 9 for more information. for more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
skipping to change at page 73, line 20 skipping to change at page 74, line 20
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <iesg@ietf.org>
10.4.3. MIME Content-type Registration for 'application/ 11.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 media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.DeviceInfo+xml MIME media subtype name: EmergencyCallData.DeviceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset (indicates the character encoding of Optional parameters: charset (indicates the character encoding of
the contents) the contents)
Encoding considerations: Uses XML, which can contain 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2 characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303]. of RFC 7303 [RFC7303].
Security considerations: This content type is designed to carry Security considerations: This content type is designed to carry
device information, which is a sub-category of additional data device information, which is a sub-category of additional data
about an emergency call. Since this data contains personal about an emergency call. Since this data contains personal
information, appropriate precautions need to be taken to limit information, appropriate precautions need to be taken to limit
unauthorized access, inappropriate disclosure to third parties, unauthorized access, inappropriate disclosure to third parties,
and eavesdropping of this information. Please refer to Section 8 and eavesdropping of this information. Please refer to Section 9
and Section 9 for more information. and Section 10 for more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
skipping to change at page 74, line 24 skipping to change at page 75, line 24
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <iesg@ietf.org>
10.4.4. MIME Content-type Registration for 'application/ 11.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 media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.SubscriberInfo+xml MIME media 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
the contents) the contents)
Encoding considerations: Uses XML, which can contain 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2 characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303]. 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 need 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 8 and Section 9 for more information. Section 9 and Section 10 for more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
skipping to change at page 75, line 29 skipping to change at page 76, line 29
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <iesg@ietf.org>
10.4.5. MIME Content-type Registration for 'application/ 11.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 media type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
MIME media type name: application MIME media type name: application
MIME subtype name: EmergencyCallData.Comment+xml MIME media subtype name: EmergencyCallData.Comment+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset (indicates the character encoding of Optional parameters: charset (indicates the character encoding of
the contents) the contents)
Encoding considerations: Uses XML, which can contain 8-bit Encoding considerations: Uses XML, which can contain 8-bit
characters, depending on the character encoding. See Section 3.2 characters, depending on the character encoding. See Section 3.2
of RFC 7303 [RFC7303]. 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 can contain personal information.
Appropriate precautions may be needed to limit unauthorized Appropriate precautions are needed to limit unauthorized access,
access, inappropriate disclosure to third parties, and inappropriate disclosure to third parties, and eavesdropping of
eavesdropping of this information. Please refer to Section 8 and this information. Please refer to Section 9 and Section 10 for
Section 9 for more information. more information.
Interoperability considerations: None Interoperability considerations: None
Published specification: [TBD: This specification] Published specification: [TBD: This specification]
Applications which use this media type: Emergency Services Applications which use this media type: Emergency Services
Additional information: Additional information:
Magic Number: None Magic Number: None
skipping to change at page 76, line 35 skipping to change at page 77, line 35
Macintosh file type code: 'TEXT' Macintosh file type code: 'TEXT'
Person and email address for further information: Hannes Person and email address for further information: Hannes
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <iesg@ietf.org>
10.5. URN Sub-Namespace Registration 11.5. URN Sub-Namespace Registration
10.5.1. Registration for urn:ietf:params:xml:ns:EmergencyCallData 11.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 77, line 23 skipping to change at page 78, line 23
<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>Namespace for Additional Data related to an Emergency Call
</h1> </h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
10.5.2. Registration for 11.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>.
skipping to change at page 78, line 25 skipping to change at page 79, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call <h1>Namespace for Additional Data related to an Emergency Call
</h1> </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
10.5.3. Registration for 11.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>.
skipping to change at page 79, line 25 skipping to change at page 80, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call <h1>Namespace for Additional Data related to an Emergency Call
</h1> </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
10.5.4. Registration for 11.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>.
skipping to change at page 80, line 25 skipping to change at page 81, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call <h1>Namespace for Additional Data related to an Emergency Call
</h1> </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
10.5.5. Registration for 11.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>.
skipping to change at page 81, line 25 skipping to change at page 82, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call <h1>Namespace for Additional Data related to an Emergency Call
</h1> </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
10.5.6. Registration for 11.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>.
skipping to change at page 82, line 25 skipping to change at page 83, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call <h1>Namespace for Additional Data related to an Emergency Call
</h1> </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
10.6. Schema Registrations 11.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 19. XML: The XML schema can be found in Figure 19.
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 (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 20. XML: The XML schema can be found in Figure 20.
URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo URI: urn:ietf:params:xml:schema: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: The XML schema can be found in Figure 21. XML: The XML schema can be found in Figure 21.
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 7.4. XML: The XML schema can be found in Section 8.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 7.5. XML: The XML schema can be found in Section 8.5.
10.7. VCard Parameter Value Registration 11.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
11. Acknowledgments 12. Acknowledgments
This work was originally started in NENA and has benefitted from a This work was originally started in NENA and has benefited 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. Amursana Khiyod, Robert Sherry, Frank and Robert (Bob) Sherry. Amursana Khiyod, Robert Sherry, Frank
Rahoi, Scott Ross, and Tom Klepetka provided valuable feedback Rahoi, Scott Ross, and Tom Klepetka provided valuable feedback
regarding the vCard/xCard use in this specification. regarding the vCard/xCard use in this specification.
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, Chris Santer, Barbara Stark, Chris Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris
Santer, and Archie Cobbs for their review comments. Alissa Cooper Santer, Archie Cobbs, Magnus Nystrom, and Francis Dupont for their
and Guy Caron deserves special mention for their detailed and review comments. Alissa Cooper, Guy Caron, Ben Campbell, and Barry
extensive review comments, which were very helpful and appreciated. Leiba deserves special mention for their detailed and extensive
review comments, which were very helpful and appreciated.
12. References 13. References
12.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[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.
[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.
[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. DOI 10.17487/RFC3688, January 2004,
<http://www.rfc-editor.org/info/rfc3688>.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC
3966, December 2004. 3966, December 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, DOI 10.17487/RFC4119, December 2005,
<http://www.rfc-editor.org/info/rfc4119>.
[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. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008. 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.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, 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.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013. 6838, DOI 10.17487/RFC6838, January 2013,
<http://www.rfc-editor.org/info/rfc6838>.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
July 2014. DOI 10.17487/RFC7303, July 2014,
<http://www.rfc-editor.org/info/rfc7303>.
12.2. Informational References 13.2. Informational References
[ECRIT-WG-wiki] [ECRIT-WG-wiki]
IETF, "ECRIT WG Wiki"", July 2015, IETF, "ECRIT WG Wiki"", July 2015,
<http://tools.ietf.org/wg/ecrit/trac/attachment/wiki/ <http://tools.ietf.org/wg/ecrit/trac/attachment/wiki/
WikiStart/additional-data-examples.zip>. WikiStart/additional-data-examples.zip>.
[I-D.gellens-slim-negotiating-human-language] [I-D.gellens-slim-negotiating-human-language]
Gellens, R., "Negotiating Human Language in Real-Time Gellens, R., "Negotiating Human Language in Real-Time
Communications", draft-gellens-slim-negotiating-human- Communications", draft-gellens-slim-negotiating-human-
language-01 (work in progress), April 2015. language-02 (work in progress), July 2015.
[IANA-XML-Schemas] [IANA-XML-Schemas]
IANA, "IANA XML Schemas"", July 2015, IANA, "IANA XML Schemas"", July 2015,
<http://www.iana.org/assignments/xml-registry/ <http://www.iana.org/assignments/xml-registry/
xml-registry.xhtml#schema>. xml-registry.xhtml#schema>.
[LERG] Telcordia Technologies, Inc., "Local Exchange Routing
Guide (LERG)", ANI II Digits Definitions , June 2015.
[LanguageTagRegistry] [LanguageTagRegistry]
IANA, "Language Subtag Registry", Feb 2015, IANA, "Language Subtag Registry", Feb 2015,
<http://www.iana.org/assignments/language-subtag-registry/ <http://www.iana.org/assignments/language-subtag-registry/
language-subtag-registry>. language-subtag-registry>.
[NANP] North American Numbering Plan Administration, "ANI II
Digits Assignments", September 2015,
<http://nanpa.com/number_resource_info/
ani_ii_assignments.html>.
[NENA-02-010]
National Emergency Number Association (NENA), "NENA
Standard Data Formats for 9-1-1 Data Exchange & GIS
Mapping", NENA Standard 02-010, December 2010,
<http://www.nena.org>.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325, Asserted Identity within Trusted Networks", RFC 3325,
November 2002. November 2002.
[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.
[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, Ed., "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
RFC 5012, January 2008. RFC 5012, DOI 10.17487/RFC5012, January 2008,
<http://www.rfc-editor.org/info/rfc5012>.
[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.
[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, DOI 10.17487/RFC5491, March 2009,
<http://www.rfc-editor.org/info/rfc5491>.
[RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and [RFC5582] Schulzrinne, H., "Location-to-URL Mapping Architecture and
Framework", RFC 5582, September 2009. 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, DOI
September 2010. 10.17487/RFC5962, September 2010,
<http://www.rfc-editor.org/info/rfc5962>.
[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
Multimedia", RFC 6443, December 2011. Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>.
[RFC6698] Hoffman, P. and J. Schlyter, "The DNS-Based Authentication
of Named Entities (DANE) Transport Layer Security (TLS)
Protocol: TLSA", RFC 6698, DOI 10.17487/RFC6698, August
2012, <http://www.rfc-editor.org/info/rfc6698>.
[RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and [RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and
R. George, "Specifying Civic Address Extensions in the R. George, "Specifying Civic Address Extensions in the
Presence Information Data Format Location Object (PIDF- Presence Information Data Format Location Object (PIDF-
LO)", RFC 6848, January 2013. LO)", RFC 6848, January 2013.
[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, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>.
[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. [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.
Thomson, "Relative Location Representation", RFC 7035, Thomson, "Relative Location Representation", RFC 7035,
October 2013. October 2013.
[RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback", Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, April 2014. RFC 7090, DOI 10.17487/RFC7090, April 2014,
<http://www.rfc-editor.org/info/rfc7090>.
12.3. URIs [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre,
"Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <http://www.rfc-editor.org/info/rfc7525>.
[nc911] North Carolina 911 Board, "North Carolina Telecommunicator
Reference", January 2009, <https://www.nc911.nc.gov/pdf/
A_TelecommunicatorReference.pdf>.
13.3. URIs
[1] http://www.nena.org/?page=cid2014 [1] http://www.nena.org/?page=cid2014
[2] http://www.nena.org/?page=CompanyID [2] http://www.nena.org/?page=CompanyID
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
 End of changes. 250 change blocks. 
1005 lines changed or deleted 1107 lines changed or added

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