draft-ietf-ecrit-additional-data-17.txt   draft-ietf-ecrit-additional-data-18.txt 
ECRIT B. Rosen ECRIT B. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: July 26, 2014 Nokia Solutions and Networks Expires: August 14, 2014 Nokia Solutions and Networks
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
R. Gellens R. Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
J. Winterbottom J. Winterbottom
January 22, 2014 February 10, 2014
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-17.txt draft-ietf-ecrit-additional-data-18.txt
Abstract Abstract
When an emergency call is sent to a Public Safety Answering Point When an emergency call is sent to a Public Safety Answering Point
(PSAP), the device that sends it, as well as any application service (PSAP), the device that sends it, as well as any application service
provider in the path of the call, or access network provider through provider in the path of the call, or access network provider through
which the call originated may have information about the call, the which the call originated may have information about the call, the
caller or the location which the PSAP may be able to use. This caller or the location which the PSAP may be able to use. This
document describes data structures and a mechanism to convey such document describes data structures and a mechanism to convey such
data to the PSAP. The mechanism uses a Uniform Resource Identifier data to the PSAP. The mechanism uses a Uniform Resource Identifier
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 26, 2014. This Internet-Draft will expire on August 14, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6 3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Data Provider Information . . . . . . . . . . . . . . . . 7 3.1. Data Provider Information . . . . . . . . . . . . . . . . 8
3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8
3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8 3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8
3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8 3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9
3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9 3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9
3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10 3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10
3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10 3.1.6. Data Provider Languages(s) Supported . . . . . . . . 11
3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11 3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11
3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 11 3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12
3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12 3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12
3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 12 3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13
3.2. Service Information . . . . . . . . . . . . . . . . . . . 14 3.2. Service Information . . . . . . . . . . . . . . . . . . . 15
3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15 3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15
3.2.2. Service Delivered by Provider to End User . . . . . . 15 3.2.2. Service Delivered by Provider to End User . . . . . . 16
3.2.3. Service Mobility Environment . . . . . . . . . . . . 17 3.2.3. Service Mobility Environment . . . . . . . . . . . . 17
3.2.4. emergencyCallData.ServiceInfo Example . . . . . . . . 17 3.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 18
3.3. Device Information . . . . . . . . . . . . . . . . . . . 17 3.3. Device Information . . . . . . . . . . . . . . . . . . . 18
3.3.1. Device Classification . . . . . . . . . . . . . . . . 18 3.3.1. Device Classification . . . . . . . . . . . . . . . . 18
3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 19 3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 20
3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 19 3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 20
3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20 3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20
3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 20 3.3.5. Device/Service Specific Additional Data Structure . . 21
3.3.6. Device/Service Specific Additional Data Structure . . 21 3.3.6. Device/Service Specific Additional Data Structure
3.3.7. Device/Service Specific Additional Data Structure Type . . . . . . . . . . . . . . . . . . . . . . . . 22
Type . . . . . . . . . . . . . . . . . . . . . . . . 21 3.3.7. Issues with getting new types of data into use . . . 22
3.3.8. Issues with getting new types of data into use . . . 22 3.3.8. Choosing between defining a new type of block or new
3.3.9. Choosing between defining a new type of block or new
type of device/service specific additional data . . . 23 type of device/service specific additional data . . . 23
3.3.10. emergencyCallData.DeviceInfo Example . . . . . . . . 23 3.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 24
3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24 3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24
3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 24 3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 24
3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25 3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25
3.4.3. emergencyCallData.SubscriberInfo Example . . . . . . 25 3.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 25
3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 27 3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28
3.5.2. emergencyCallData.Comment Example . . . . . . . . . . 28 3.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 28
4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 28
4.1. Transmitting Blocks using the Call-Info Header . . . . . 30 4.1. Transmitting Blocks using the Call-Info Header . . . . . 30
4.2. Transmitting Blocks by Reference using the Provided-By 4.2. Transmitting Blocks by Reference using the Provided-By
Element . . . . . . . . . . . . . . . . . . . . . . . . . 31 Element . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.3. Transmitting Blocks by Value using the Provided-By 4.3. Transmitting Blocks by Value using the Provided-By
Element . . . . . . . . . . . . . . . . . . . . . . . . . 32 Element . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.4. The Content-Disposition Parameter . . . . . . . . . . . . 33 4.4. The Content-Disposition Parameter . . . . . . . . . . . . 32
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34
6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45 6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45
6.1. emergencyCallData.ProviderInfo XML Schema . . . . . . . . 45 6.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 45
6.2. emergencyCallData.ServiceInfo XML Schema . . . . . . . . 46 6.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 47
6.3. emergencyCallData.DeviceInfo XML Schema . . . . . . . . . 47 6.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 48
6.4. emergencyCallData.SubscriberInfo XML Schema . . . . . . . 48 6.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 49
6.5. emergencyCallData.Comment XML Schema . . . . . . . . . . 49 6.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 50
6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 50 6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 51
7. Security Considerations . . . . . . . . . . . . . . . . . . . 52 7. Security Considerations . . . . . . . . . . . . . . . . . . . 52
8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 53 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 54
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 55 9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 56
9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 55 9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 56
9.1.2. Service Environment Registry . . . . . . . . . . . . 56 9.1.2. Service Environment Registry . . . . . . . . . . . . 57
9.1.3. Service Provider Type Registry . . . . . . . . . . . 57 9.1.3. Service Provider Type Registry . . . . . . . . . . . 57
9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57 9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57
9.1.5. Device Classification Registry . . . . . . . . . . . 57 9.1.5. Device Classification Registry . . . . . . . . . . . 58
9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 58 9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 58
9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58 9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58
9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 59 9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 59
9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 59 9.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . . 60
9.3. URN Sub-Namespace Registration for provided-by Registry 9.3. URN Sub-Namespace Registration for provided-by Registry
Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 60
9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 60 9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 60
9.4.1. MIME Content-type Registration for 9.4.1. MIME Content-type Registration for
'application/emergencyCallData.ProviderInfo+xml' . . 60 'application/EmergencyCallData.ProviderInfo+xml' . . 60
9.4.2. MIME Content-type Registration for 9.4.2. MIME Content-type Registration for
'application/emergencyCallData.ServiceInfo+xml' . . . 61 'application/EmergencyCallData.ServiceInfo+xml' . . . 61
9.4.3. MIME Content-type Registration for 9.4.3. MIME Content-type Registration for
'application/emergencyCallData.DeviceInfo+xml' . . . 62 'application/EmergencyCallData.DeviceInfo+xml' . . . 62
9.4.4. MIME Content-type Registration for 9.4.4. MIME Content-type Registration for
'application/emergencyCallData.SubscriberInfo+xml' . 63 'application/EmergencyCallData.SubscriberInfo+xml' . 63
9.4.5. MIME Content-type Registration for 9.4.5. MIME Content-type Registration for
'application/emergencyCallData.Comment+xml' . . . . . 64 'application/EmergencyCallData.Comment+xml' . . . . . 64
9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 65 9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 65
9.5.1. Registration for 9.5.1. Registration for
urn:ietf:params:xml:ns:emergencycalldata . . . . . . 65 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 65
9.5.2. Registration for 9.5.2. Registration for
urn:ietf:params:xml:ns:emergencycalldata:providerinfo 65 urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo 66
9.5.3. Registration for 9.5.3. Registration for
urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo 66 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 67
9.5.4. Registration for 9.5.4. Registration for
urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo . 67 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo . 68
9.5.5. Registration for 9.5.5. Registration for
urn:ietf:params:xml:ns:emergencycalldata:SubscriberIn urn:ietf:params:xml:ns:EmergencyCallData:SubscriberIn
fo . . . . . . . . . . . . . . . . . . . . . . . . . 68 fo . . . . . . . . . . . . . . . . . . . . . . . . . 68
9.5.6. Registration for 9.5.6. Registration for
urn:ietf:params:xml:ns:emergencycalldata:comment . . 68 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 69
9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 69 9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 70
9.7. VCard Parameter Value Registration . . . . . . . . . . . 70 9.7. VCard Parameter Value Registration . . . . . . . . . . . 71
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 70 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 71
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 70 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 71
11.1. Normative References . . . . . . . . . . . . . . . . . . 70 11.1. Normative References . . . . . . . . . . . . . . . . . . 71
11.2. Informational References . . . . . . . . . . . . . . . . 72 11.2. Informational References . . . . . . . . . . . . . . . . 72
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 73 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 74
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96
1. Introduction 1. Introduction
When an IP-based emergency call is initiated a rich set of data from When an IP-based emergency call is initiated, a rich set of data from
multiple data sources is conveyed to the Public Safety Answering multiple data sources is conveyed to the Public Safety Answering
Point (PSAP). This data includes information about the calling party Point (PSAP). This data includes information about the calling party
identity, the multimedia capabilities of the device, the emergency identity, the multimedia capabilities of the device, the emergency
service number, location information, and meta-data about the sources service number, location information, and meta-data about the sources
of the data. The device, the access network provider, and any of the data. The device, the access network provider, and any
service provider in the call path may have even more information service provider in the call path may have even more information
useful for a PSAP. This document extends the basic set of data useful for a PSAP. This document extends the basic set of data
communicated with an IP-based emergency call, as described in communicated with an IP-based emergency call, as described in
[RFC6443] and [RFC6881], in order to carry additional data which may [RFC6443] and [RFC6881], in order to carry additional data which may
be useful to an entity or call taker handling the call. This data is be useful to an entity or call taker handling the call. This data is
"additional" to the basic information found in the emergency call "additional" to the basic information found in the emergency call
signaling used. signaling used.
In general, there are three categories of data communicated in an In general, there are three categories of this additional data that
emergency call: may be transmitted with an emergency call:
Data Associated with a Location: Location data is conveyed in the Data Associated with a Location: Primary location data is conveyed
Presence Information Data Format Location Object (PIDF-LO) data in the Presence Information Data Format Location Object (PIDF-LO)
structure originally defined in RFC 4119 [RFC4119] and extended by data structure as defined in RFC 4119 [RFC4119] and extended by
RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location
information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for
geodetic location information), and geodetic location information), and
[I-D.ietf-geopriv-relative-location] (for relative location). [I-D.ietf-geopriv-relative-location] (for relative location).
There may be data that is specific to the location not available This primary location data identifies the location or estimated
in the location data structure itself, such as floor plans, tenant location of the caller. However, there may exist additional,
and building owner contact data, heating, ventilation and air secondary data which is specific to the location, such as floor
conditioning (HVAC) status, etc. plans, tenant and building owner contact data, heating,
ventilation and air conditioning (HVAC) status, etc. Such
secondary location data is not included in the location data
structure but can be transmitted using the mechanisms defined in
this document; although this document does not define any
structures for such data, future documents may do so following the
procedures defined here.
Data Associated with a Call: While information is carried in the Data Associated with a Call: While some information is carried in
call setup procedure itself (as part of the SIP headers as well as the call setup procedure itself (as part of the SIP headers as
in the body of the SIP message), there is additional data known by well as in the body of the SIP message), there is additional data
the device making the call, and the service provider along the known by the device making the call and/or a service provider
path of the call. This information may include the service along the path of the call. This information may include the
provider contact information, subscriber identity and contact service provider contact information, subscriber identity and
information, the type of service the service provider and the contact information, the type of service the service provider and
access network provider offer, what kind of device is being used, the access network provider offer, what type of device is being
etc. Some data is device or service dependent data. For example, used, etc. Some data is broadly applicable, while other data is
a car telematics system may have crash information. A medical dependent on the type of device or service. For example, a
monitoring device may have sensor data. medical monitoring device may have sensor data. The data
structures defined in this document (Data Provider Information,
Device Information, and Owner/Subscriber Information) all fall
into this category ("Data Associated with a Call").
Data Associated with a Caller: This is personal data about a caller, Data Associated with a Caller: This is personal data about a caller,
such as medical information and emergency contact data. such as medical information and emergency contact data. Although
this document does not define any structures within this category,
future documents may do so following the procedures defined here.
This document only defines data structures relevant to data While this document defines data structures only within the category
associated with the call but defines extension points for other data of Data Associated with a Call, by establishing the overall framework
to be added via other specifications. of Additional Data, along with general mechanisms for transport of
such data, extension points and procedures for future extensions, it
minimizes the work needed to carry data in the other categories.
Other specifications may 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
accessed. successfully accessed.
This document defines the data structures and a way to communicate This document defines an extensible set of data structures, and
the information in several ways. Although current standardization mechanisms to transmit this data either by value or by reference,
efforts around IP-based emergency services are focused on the Session either in the Session Initiation Protocol (SIP) call signaling or in
Initiation Protocol (SIP) and HTTP the data structures in XML format the Presence Information Data Format Location Object (PIDF-LO). The
described in this document are usable for other communication systems data structures are usable by other communication systems and
as well. In Section 3 the data structures are defined and the SIP/ transports as well. The data structures are defined in Section 3,
HTTP transport components are defined in Section 4 to offer a clear and the transport mechanisms (using SIP and HTTPS) are defined in
separation between the two. Section 4.
More technically, the data structure described in this document is Each data structure described in this document is encoded as a
represented as one or more "blocks" of information. Each of the "block" of information. Each block is an XML structure with an
blocks is an XML structure with an associated Multipurpose Internet associated Multipurpose Internet Mail Extensions (MIME) type for
Mail Extensions (MIME) type for encapsulation, and an extensible set identification within transport such as SIP and HTTPS. The set of
of these types constitute the data set. A registry is defined to blocks is extensible. Registries are defined to identify the block
list the block types that may be included. types that may be used and to allow blocks to be included in
emergency call signaling.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
This document also uses terminology from [RFC5012]. We use the term This document also uses terminology from [RFC5012]. We use the term
service provider to refer to an Application Service Provider (ASP). service provider to refer to an Application Service Provider (ASP).
A Voice Service Provider (VSP) is a special type of ASP. With the A Voice Service Provider (VSP) is a special type of ASP. With the
term "Access Network Provider" we refer to the Internet Access term "Access Network Provider" we refer to the Internet Access
Provider (IAP) and the Internet Service Provider (ISP) without Provider (IAP) and the Internet Service Provider (ISP) without
further distinguishing these two entities, since the difference further distinguishing these two entities, since the difference
between the two is not relevant for this document. Note that the between the two is not relevant for this document. Note that the
roles of ASP and access network provider may be provided by a single roles of ASP and access network provider may be provided by a single
company. company.
In the data block definitions, see Section 3, the values for the Within each data block definition (see Section 3), the values for the
"Use:" label are specified as one of: "Use:" label are specified as one of the following:
'Required': means they MUST be present in the data structure. 'Required': means they MUST be present in the data structure.
'Conditional': means they MUST be present if the specified 'Conditional': means they MUST be present if the specified
condition(s) is met. They MAY be present if the condition(s) is condition(s) is met. They MAY be present if the condition(s) is
not met. not met.
'Optional': means they MAY be present. 'Optional': means they MAY be present.
vCard is a data format for representing and exchanging a variety of vCard is a data format for representing and exchanging a variety of
information about individuals and other entities. For applications information about individuals and other entities. For applications
that use XML the format defined in vCard is not immediately that use XML the format defined in vCard is not immediately
applicable. For this purpose an XML-based encoding of the applicable. For this purpose an XML-based encoding of the
information elements defined in the vCard specification has been information elements defined in the vCard specification has been
defined and the name of that specification is xCard. Since the term defined and the name of that specification is xCard. Since the term
vCard is more familiar to most readers we use the term xCard and vCard is more familiar to most readers, we use the term xCard and
vCard interchangeable but it would be accurate to use the term vCard vCard interchangeably.
only.
3. Data Structures 3. 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 data block. For each block we define the MIME type, and the XML
structure. The five data structures are: encoding. The five data structures are:
'Data Provider': This block supplies name and contact information 'Data Provider': This block supplies name and contact information
for the entity that created the data. Section 3.1 provides the for the entity that created the data. Section 3.1 provides the
details. details.
'Service Information': This block supplies information about the 'Service Information': This block supplies information about the
service. The description can be found in Section 3.2. service. The description can be found in Section 3.2.
'Device Information': This block supplies information about the 'Device Information': This block supplies information about the
device placing the call. Device information can be found in device placing the call. Device information can be found in
Section 3.3. Section 3.3.
'Owner/Subscriber': This block supplies information about the owner 'Owner/Subscriber': This block supplies information about the owner
of the device or about the subscriber. Details can be found in of the device or about the subscriber. Details can be found in
Section 3.4. Section 3.4.
'Comment': This block provides a way to supply free form human 'Comment': This block provides a way to supply free form human
readable text to the PSAP or emergency responders. This simple readable text to the PSAP or emergency responders. This simple
structure is defined in Section 3.5. structure is defined in Section 3.5.
Each block contains a mandatory <id> element. The purpose of this Each block contains a mandatory <DataProviderReference> element. The
<id> element is to associate the data added by a data provider to the purpose of the <DataProviderReference> element is to associate all
data provider block. Consequently, when a data provider adds blocks added by the same data provider as a unit. The
additional data to an emergency call (such as device information) it <DataProviderReference> element associates the data provider block to
MUST add information about itself (via the data provider block) and each of the other blocks added as a unit. Consequently, when a data
the two blocks contain the same value in the <id> element, whereby provider adds additional data to an emergency call (such as device
the chosen value for the <id> element MUST be different to any other information) it MUST add information about itself (via the data
<id> elements already added by other data providers. provider block) and the blocks added contain the same value in the
<DataProviderReference> element. All blocks added by a single entity
at the same time MUST have the same <DataProviderReference> value.
The value of the <DataProviderReference> element has the same syntax
and properties (specifically, world-uniqueness) as the value of the
"Content-ID" message body header field specified in RFC 2045
[RFC2045] except that the <DataProviderReference> element is not
enclosed in brackets (the "<" and ">" symbols are omitted). In other
words, the value of an <DataProviderReference> element is
syntactically an addr-spec as specified in RFC 822 [RFC0822].
Note that the xCard format is re-used in some of the data structures Note that the xCard format is re-used in some of the data structures
to provide contact information. In an xCard there is no way to to provide contact information. In an xCard there is no way to
specify a "main" telephone number. These numbers are useful to specify a "main" telephone number. These numbers are useful to
emergency responders who are called to a large enterprise. This emergency responders who are called to a large enterprise. This
document adds a new property value to the "tel" property of the TYPE document adds a new property value to the "tel" property of the TYPE
parameter called "main". It can be used in any xCard in additional parameter called "main". It can be used in any xCard in additional
data. data.
3.1. Data Provider Information 3.1. Data Provider Information
This block is intended to be provided by any service provider in the This block is intended to be supplied by any service provider in the
path of the call or the access network provider. It includes path of the call or the access network provider. It includes
identification and contact information. This block SHOULD be identification and contact information. This block SHOULD be
provided by every service provider in the call path, and by the supplied by every service provider in the call path, and by the
access network provider. Devices MAY use this block to provide access network provider. Devices MAY use this block to provide
identifying information. The MIME subtype is "application/ identifying information. The MIME subtype is "application/
emergencyCall.ProviderInfo+xml". An access network provider SHOULD EmergencyCallData.ProviderInfo+xml". An access network provider
provide this block either by value or by reference in the Provided-By SHOULD provide this block either by value or by reference in the
section of a PIDF-LO Provided-By section of a PIDF-LO
3.1.1. Data Provider String 3.1.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Required Use: Required
XML Element: <DataProviderString> XML Element: <DataProviderString>
Description: This is a plain language string suitable for displaying Description: This is a plain text string suitable for displaying the
the name of the service provider that created the additional data name of the service provider that supplied the data structure. If
structure. If the device created the structure the value is the device creates the structure, it SHOULD use the value of the
identical to the contact header in the SIP INVITE. contact header in the SIP INVITE.
Reason for Need: Inform the call taker of the identity of the entity Reason for Need: Inform the call taker of the identity of the entity
providing the additional call data structure. providing the data.
How Used by Call Taker: Allows the call taker to interpret the data How Used by Call Taker: Allows the call taker to interpret the data
in this structure. The source of the information often influences in this structure. The source of the information often influences
how the information is used, believed or verified. how the information is used, believed or verified.
3.1.2. Data Provider ID 3.1.2. Data Provider ID
Data Element: Data Provider ID Data Element: Data Provider ID
Use: Conditional. This data SHOULD be provided if the service Use: Conditional. This data SHOULD be provided if the service
provider or access provider is located in a jurisdiction that provider or access provider is located in a jurisdiction that
maintains such ids. For example, in North America, this would be maintains such IDs. For example, in North America, this would be
a "NENA Company ID". a NENA Company ID.
XML Element: <ProviderID> XML Element: <ProviderID>
Description: A jurisdiction specific code for the access provider or Description: A jurisdiction-specific code for the access network
service provider shown in the <DataProvidedBy> element that provider or service provider shown in the <DataProvidedBy> element
created the structure of the call. NOTE: In the US, the NENA that created the structure. NOTE: In the US, the provider's NENA
Company ID must appear here. Additional information can be found Company ID MUST appear here. Additional information can be found
at http://www.nena.org/nena-company-id. The NENA Company ID MUST at NENA Company Identifier Program [1] or NENA Company ID [2].
be in the form of a URI in the following format: The NENA Company ID MUST be in the form of a URI in the following
urn:nena:companyid:<NENA Company ID> format: urn:nena:companyid:<NENA Company ID>
Reason for Need: Inform the call taker of the identity of the entity Reason for Need: Inform the call taker of the identity of the entity
providing the additional call data structure. providing the data.
How Used by Call Taker: Where jurisdictions have lists of providers How Used by Call Taker: Where jurisdictions have lists of providers
the Data Provider ID provides useful information about the data the Data Provider ID provides useful information about the data
source. source.
3.1.3. Data Provider ID Series 3.1.3. Data Provider ID Series
Data Element: Data Provider ID Series Data Element: Data Provider ID Series
Use: Conditional. If Data Provider ID is provided, Data Provider ID Use: Conditional. If Data Provider ID is provided, Data Provider ID
Series is required. Series is required.
XML Element: <ProviderIDSeries> XML Element: <ProviderIDSeries>
Description: Identifies the issuer of the ProviderId. A registry Description: Identifies the issuer of the ProviderId. The Provider
will reflect the following valid entries: ID Series Registry (see Section 9.1) initially contains the
following valid entries:
* NENA * NENA
* EENA * EENA
Reason for Need: Identifies how to interpret the Data Provider ID. Reason for Need: Identifies how to interpret the Data Provider ID.
How Used by Call Taker: Determines which provider ID registry to How Used by Call Taker: Determines which provider ID registry to
consult for more information consult for more information
3.1.4. Type of Data Provider 3.1.4. Type of Data Provider
Data Element: Type of Data Provider ID Data Element: Type of Data Provider ID
Use: Conditional. If Data Provider ID is provided, Type of Data Use: Conditional. If Data Provider ID is provided, Type of Data
Provider ID is required. Provider ID is required.
XML Element: <TypeOfProviderID> XML Element: <TypeOfProviderID>
Description: Identifies the type of data provider ID being supplied
Description: Identifies the type of data provider id being supplied in the ProviderID data element. A registry with an initial set of
in the ProviderId data element. A registry with an initial set of values is shown in Figure 1 (see also Section 9.1).
values is shown in Figure 1.
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Token | Description | | Token | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Access Network Provider | Access network service provider | |Access Network Provider | Access network service provider |
|Service Provider | Calling or Origination telecom SP | |Service Provider | Calling or Origination telecom SP |
|Subcontractor | A contractor to another SP | |Subcontractor | A contractor to another SP |
|Telematics Provider | A sensor based SP, especially | |Telematics Provider | A sensor based SP, especially |
| | vehicle based | | | vehicle based |
|Language Translation Provider | A spoken language translation SP | |Language Translation Provider | A spoken language translation SP |
skipping to change at page 10, line 11 skipping to change at page 10, line 31
| | modality translation service | | | modality translation service |
| | e.g., for sign language | | | e.g., for sign language |
|Relay Provider | A interpretation SP, for example, | |Relay Provider | A interpretation SP, for example, |
| | video relay for sign language | | | video relay for sign language |
| | interpreting | | | interpreting |
|Other | Any other type of service provider | |Other | Any other type of service provider |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
Figure 1: Type of Data Provider ID Registry. Figure 1: Type of Data Provider ID Registry.
Reason for Need: Identifies what kind of data provider this is. Reason for Need: Identifies the category of data provider.
How Used by Call Taker: To decide who to contact when further How Used by Call Taker: This information may be helpful when
information is needed deciding whom to contact when further information is needed.
3.1.5. Data Provider Contact URI 3.1.5. Data Provider Contact URI
Data Element: Data Provider Contact URI Data Element: Data Provider Contact URI
Use: Required Use: Required
XML Element: <ContactURI> XML Element: <ContactURI>
Description: When provided by a service provider or an access Description: When provided by a service provider or an access
provider, this information MUST be a URI to a 24/7 support network provider, this information MUST be a URI to a 24/7 support
organization tasked to provide PSAP support for this emergency organization tasked to provide PSAP support for this emergency
call. If the call is from a device, this would reflect the call. If the call is from a device, this SHOULD be the contact
contact information of the owner of the device. If a telephone information of the owner of the device. If a telephone number is
number is the contact address then it MUST be tel URI. If it is the contact address then it MUST be a tel URI. If it is provided
provided as a SIP URI then it MUST be in the form of as a SIP URI then it MUST be in the form of
sip:telephonenumber@serviceprovider:user=phone. Note that this sip:telephonenumber@serviceprovider:user=phone. Note that this
contact information is not used by PSAPs for callbacks using a SIP contact information is not used by PSAPs for callbacks (a call
Priority header field with the value set to "psap- callback", as from a PSAP directly related to a recently terminated emergency
described in [I-D.ietf-ecrit-psap-callback]. call, placed by the PSAP using a SIP Priority header field set to
"psap-callback", as described in [I-D.ietf-ecrit-psap-callback]).
Reason for Need: Additional data providers may need to be contacted Reason for Need: Additional data providers may need to be contacted
for error or other unusual circumstances. in error cases or other unusual circumstances.
How Used by Call Taker: To contact the supplier of the additional How Used by Call Taker: To contact the supplier of the additional
data for assistance in handling the call. data for assistance in handling the call.
3.1.6. Data Provider Languages(s) Supported 3.1.6. Data Provider Languages(s) Supported
Data Element: Data Provider Language(s) supported Data Element: Data Provider Language(s) supported
Use: Required. Use: Required.
XML Element: <Language> XML Element: <Language>
Description: The language used by the entity at the Data Provider Description: The language used by the entity at the Data Provider
Contact URI as an alpha 2-character code as defined in ISO Contact URI, as an alpha 2-character code as defined in ISO
639-1:2002 Codes for the representation of names of languages -- 639-1:2002 Codes for the representation of names of languages --
Part 1: Alpha-2 code Multiple instances of this element may occur. Part 1: Alpha-2 code Multiple instances of this element may occur.
Order is significant; preferred language should appear first. The Order is significant; preferred language should appear first. The
content MUST reflect the languages supported at the contact URI. content MUST reflect the languages supported at the contact URI.
Note that the 'language' media feature tag, defined in RFC 3840 Note that the 'language' media feature tag, defined in RFC 3840
[RFC3840] and the more extensive language negotiation mechanism [RFC3840] and the more extensive language negotiation mechanism
proposed with [I-D.gellens-negotiating-human-language] are proposed with [I-D.gellens-negotiating-human-language] are
independent of this data provider language indication. independent of this data provider language indication.
Reason for Need: Information needed to determine if emergency Reason for Need: This information indicates if the emergency service
service authority can communicate with the service provider or if authority can directly communicate with the service provider or if
an interpreter will be needed. an interpreter will be needed.
How Used by Call Taker: If call taker cannot speak language(s) How Used by Call Taker: If call taker cannot speak language(s)
supported by the service provider, a translation service will need supported by the service provider, a translation service will need
to be added to the conversation. Alternatively, other persons at to be added to the conversation. Alternatively, other persons at
the PSAP, besides the call taker, might be consulted for help the PSAP, besides the call taker, might be consulted for help
(depending on the urgency and the type of interaction). (depending on the urgency and the type of interaction).
3.1.7. xCard of Data Provider 3.1.7. xCard of Data Provider
skipping to change at page 11, line 31 skipping to change at page 12, line 4
the PSAP, besides the call taker, might be consulted for help the PSAP, besides the call taker, might be consulted for help
(depending on the urgency and the type of interaction). (depending on the urgency and the type of interaction).
3.1.7. xCard of Data Provider 3.1.7. xCard of Data Provider
Data Element: xCard of Data Provider Data Element: xCard of Data Provider
Use: Optional Use: Optional
XML Element: <DataProviderContact> XML Element: <DataProviderContact>
Description: There are many fields in the xCard and the creator of Description: There are many fields in the xCard and the creator of
the data structure is encouraged to provide as much information as the data structure is encouraged to provide as much information as
they have available. N, ORG, ADR, TEL, EMAIL are suggested at a they have available. N, ORG, ADR, TEL, EMAIL are suggested at a
minimum. N should contain name of support group or device owner minimum. N SHOULD contain the name of the support group or device
as appropriate. If more than one TEL property is provided, a owner as appropriate. If more than one TEL property is provided,
parameter from the vCard Property Value registry MUST be specified a parameter from the vCard Property Value registry MUST be
on each TEL. For encoding of the xCard this specification uses specified on each TEL. For encoding of the xCard this
the XML-based encoding specified in [RFC6351]. and is hereinafter specification uses the XML-based encoding specified in [RFC6351],
referred to as "xCard" referred to in this document as "xCard"
Reason for Need: Information needed to determine additional contact Reason for Need: Information needed to determine additional contact
information. information.
How Used by Call Taker: Assists call taker by providing additional How Used by Call Taker: Assists call taker by providing additional
contact information that may not be included in the SIP invite or contact information that may not be included in the SIP invite or
the PIDF-LO. the PIDF-LO.
3.1.8. Subcontractor Principal 3.1.8. Subcontractor Principal
skipping to change at page 12, line 44 skipping to change at page 13, line 18
Reason for Need: Inform the call taker whom to contact first, if Reason for Need: Inform the call taker whom to contact first, if
support is needed. support is needed.
How Used by Call Taker: To decide which entity to contact first if How Used by Call Taker: To decide which entity to contact first if
assistance is needed. assistance is needed.
3.1.10. ProviderInfo Example 3.1.10. ProviderInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<ad:emergencyCallData.ProviderInfo <ad:EmergencyCallData.ProviderInfo
xmlns:ad="urn:ietf:params:xml:ns:emergencycalldata:providerinfo" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ad:id>12345</ad:id> <ad:id>12345</ad:id>
<ad:DataProviderReference>string0987654321@example.org
</ad:DataProviderReference>
<ad:DataProviderString>Example VoIP Provider <ad:DataProviderString>Example VoIP Provider
</ad:DataProviderString> </ad:DataProviderString>
<ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID> <ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>
<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries> <ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
<ad:TypeOfProvider>Service Provider</ad:TypeOfProvider> <ad:TypeOfProvider>Service Provider</ad:TypeOfProvider>
<ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI> <ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI>
<ad:Language>EN</ad:Language> <ad:Language>EN</ad:Language>
<ad:DataProviderContact <ad:DataProviderContact
xmlns="urn:ietf:params:xml:ns:vcard-4.0"> xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
skipping to change at page 14, line 41 skipping to change at page 15, line 17
</uri> </uri>
</key> </key>
<tz><text>Finland/Helsinki</text></tz> <tz><text>Finland/Helsinki</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://www.tschofenig.priv.at</uri> <uri>http://www.tschofenig.priv.at</uri>
</url> </url>
</vcard> </vcard>
</ad:DataProviderContact> </ad:DataProviderContact>
</ad:emergencyCallData.ProviderInfo> </ad:EmergencyCallData.ProviderInfo>
Figure 2: emergencyCall.ProviderInfo Example. Figure 2: EmergencyCallData.ProviderInfo Example.
3.2. Service Information 3.2. Service Information
This block describes the service that the service provider provides This block describes the service that the service provider provides
to the caller. It SHOULD be included by all SPs in the path of the to the caller. It SHOULD be included by all SPs in the path of the
call. The mime subtype is "application/ call. The mime subtype is "application/
emergencyCall.ServiceInfo+xml". EmergencyCallData.ServiceInfo+xml".
3.2.1. Service Environment 3.2.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
Use: Required Use: Required
XML Element: <SvcEnvironment> XML Element: <SvcEnvironment>
Description: This element defines whether a call is from a business Description: This element defines whether a call is from a business
skipping to change at page 17, line 36 skipping to change at page 18, line 14
* Unknown: no information is known about the service mobility * Unknown: no information is known about the service mobility
environment for the device environment for the device
Reason for Need: Knowing the service provider's belief of mobility Reason for Need: Knowing the service provider's belief of mobility
may assist the PSAP with the handling of the call. may assist the PSAP with the handling of the call.
How Used by Call Taker: To determine whether to assume the location How Used by Call Taker: To determine whether to assume the location
of the caller might change. of the caller might change.
3.2.4. emergencyCallData.ServiceInfo Example 3.2.4. EmergencyCallData.ServiceInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<svc:emergencyCallData.ServiceInfo <svc:EmergencyCallData.ServiceInfo
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData.ServiceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:DataProviderReference>string0987654321@example.org
</svc:DataProviderReference>
<svc:id>12345</svc:id> <svc:id>12345</svc:id>
<svc:SvcEnvironment>Business</svc:SvcEnvironment> <svc:SvcEnvironment>Business</svc:SvcEnvironment>
<svc:SvcDelByProvider>MLTS</svc:SvcDelByProvider> <svc:SvcDelByProvider>MLTS</svc:SvcDelByProvider>
<svc:SvcMobility>Fixed</svc:SvcMobility> <svc:SvcMobility>Fixed</svc:SvcMobility>
</svc:emergencyCallData.ServiceInfo> </svc:EmergencyCallData.ServiceInfo>
Figure 4: emergencyCallData.ServiceInfo Example. Figure 4: EmergencyCallData.ServiceInfo Example.
3.3. Device Information 3.3. Device Information
This block provides information about the device used to place the This block provides information about the device used to place the
call. It should be provided by any service provider that knows what call. It should be provided by any service provider that knows what
device is being used, and by the device itself. The mime subtype is device is being used, and by the device itself. The mime subtype is
"application/emergencyCall.DeviceInfo+xml". "application/EmergencyCallData.DeviceInfo+xml".
3.3.1. Device Classification 3.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
skipping to change at page 20, line 24 skipping to change at page 20, line 52
PSAP management. PSAP management.
3.3.4. Unique Device Identifier 3.3.4. Unique Device Identifier
Data Element: Unique Device Identifier Data Element: Unique Device Identifier
Use: Optional Use: Optional
XML Element: <UniqueDeviceID> XML Element: <UniqueDeviceID>
Description: String that identifies the specific device making the XML Attribute: <TypeOfDeviceID>
Description: A string that identifies the specific device making the
call or creating an event. call or creating an event.
Reason for Need: Uniquely identifies the device as opposed to any The <TypeOfDeviceID> attribute identifies the type of device
signaling identifiers encountered in the call signaling stream. identifier. A registry with an initial set of values can be seen
in Figure 6.
How Used by Call Taker: Probably not used by the calltaker; they
would need to refer to management for investigation.
3.3.5. Type of Device Identifier
Data Element: Type of Device Identifier
Use: Conditional: must be provided if the DeviceID is provided
XML Element: <TypeOfDeviceID>
Description: Identifies the type of device identifier being
generated in the unique device identifier data element. A
registry with an initial set of values can be seen in Figure 6.
+--------+----------------------------------------+ +--------+----------------------------------------+
| Token | Description | | Token | Description |
+--------+----------------------------------------+ +--------+----------------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) | | MEID | Mobile Equipment Identifier (CDMA) |
| ESN | Electronic Serial Number(GSM) | | ESN | Electronic Serial Number(GSM) |
| MAC | Media Access Control Address (IEEE) | | MAC | Media Access Control Address (IEEE) |
| WiMAX | Device Certificate Unique ID | | WiMAX | Device Certificate Unique ID |
| IMEI | International Mobile Equipment ID (GSM)| | IMEI | International Mobile Equipment ID (GSM)|
| UDI | Unique Device Identifier | | UDI | Unique Device Identifier |
| RFID | Radio Frequency Identification | | RFID | Radio Frequency Identification |
| SN | Manufacturer Serial Number | | SN | Manufacturer Serial Number |
+--------+----------------------------------------+ +--------+----------------------------------------+
Figure 6: Registry with Device Identifier Types. Figure 6: Registry with Device Identifier Types.
Reason for Need: Identifies how to interpret the Unique Device Reason for Need: Uniquely identifies the device (independent of any
Identifier. signaling identifiers present in the call signaling stream).
How Used by Call Taker: Additional information that may be used to How Used by Call Taker: Probably not used by the call taker; may be
assist with call handling. used by PSAP management during an investigation.
3.3.6. Device/Service Specific Additional Data Structure Example: <UniqueDeviceID TypeOfDeviceID="SN">12345</UniqueDeviceID>
3.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. An example is specific to the device or service which created it. An example is
the Vehicular Emergency Data Set (VEDS) structure for a vehicle the Vehicular Emergency Data Set (VEDS) structure for a vehicle
skipping to change at page 21, line 43 skipping to change at page 22, line 11
Reason for Need: Provides device/service specific data that may be Reason for Need: Provides device/service specific data that may be
used by the call taker and/or responders. used by the call taker and/or responders.
How Used by Call Taker: Provide information to guide call takers to How Used by Call Taker: Provide information to guide call takers to
select appropriate responders, give appropriate pre-arrival select appropriate responders, give appropriate pre-arrival
instructions to callers, and advise responders of what to be instructions to callers, and advise responders of what to be
prepared for. May be used by responders to guide assistance prepared for. May be used by responders to guide assistance
provided. provided.
3.3.7. Device/Service Specific Additional Data Structure Type 3.3.6. Device/Service Specific Additional Data Structure Type
Data Element: Type of device/service specific additional data Data Element: Type of device/service specific additional data
structure structure
Use: Conditional. MUST be provided when device/service specific Use: Conditional. MUST be provided when device/service specific
additional URI is provided additional URI is provided
XML Element: <DeviceSpecificType> XML Element: <DeviceSpecificType>
Description: Value from a registry defined by this document to Description: Value from a registry defined by this document to
describe the type of data that can be retrieved from the device/ describe the type of data that can be retrieved from the device/
service specific additional data structure. Initial values are: service specific additional data structure. Initial values are:
* IEEE 1512 * IEEE 1512
* VEDS * VEDS
IEEE 1512 is the USDoT model for traffic incidents and VEDS IEEE 1512 is the USDoT model for traffic incidents and VEDS
provides data elements needed for an efficient emergency response provides data elements needed for an efficient emergency response
skipping to change at page 22, line 28 skipping to change at page 22, line 45
may assist in emergency response. may assist in emergency response.
How Used by Call Taker: This data element allows the end user How Used by Call Taker: This data element allows the end user
(calltaker or first responder) to know what type of additional (calltaker or first responder) to know what type of additional
data may be available to aid in providing the needed emergency data may be available to aid in providing the needed emergency
services. services.
Note: Information which is specific to a location or a caller Note: Information which is specific to a location or a caller
(person) should not be placed in this section. (person) should not be placed in this section.
3.3.8. Issues with getting new types of data into use 3.3.7. Issues with getting new types of data into use
This document describes two mechanisms which allow extension of the This document describes two mechanisms which allow extension of the
kind of data provided with an emergency call: define a new block or kind of data provided with an emergency call: define a new block or
define a new service specific additional data URL for the DeviceInfo define a new service specific additional data URL for the DeviceInfo
block. While defining new data types and getting a new device or block. While defining new data types and getting a new device or
application to send the new data may be easy, getting PSAPs and application to send the new data may be easy, getting PSAPs and
responders to actually retrieve the data and use it will be responders to actually retrieve the data and use it will be
difficult. New mechanism providers should understand that acquiring difficult. New mechanism providers should understand that acquiring
and using new forms of data usually require software upgrades at the and using new forms of data usually require software upgrades at the
PSAP and/or responders, as well as training of call takers and PSAP and/or responders, as well as training of call takers and
skipping to change at page 23, line 15 skipping to change at page 23, line 30
Implementers should consider that data from sensor-based devices in Implementers should consider that data from sensor-based devices in
some cases may not be useful to call takers or PSAPs (and privacy or some cases may not be useful to call takers or PSAPs (and privacy or
other considerations may preclude the PSAP from touching the data), other considerations may preclude the PSAP from touching the data),
but may be of use to responders. Some standards being developed by but may be of use to responders. Some standards being developed by
other organizations to carry data from the PSAP to responders are other organizations to carry data from the PSAP to responders are
designed to carry all additional data supplied in the call that designed to carry all additional data supplied in the call that
conform to this document, even if the PSAP does not fetch or conform to this document, even if the PSAP does not fetch or
interpret the data. This allows responders to get the data even if interpret the data. This allows responders to get the data even if
the PSAP does not. the PSAP does not.
3.3.9. Choosing between defining a new type of block or new type of 3.3.8. Choosing between defining a new type of block or new type of
device/service specific additional data device/service specific additional data
For devices that have device or service specific data, there are two For devices that have device or service specific data, there are two
choices to carry it. A new block can be defined, or the device/ choices to carry it. A new block can be defined, or the device/
service specific additional data URL the DeviceInfo block can be used service specific additional data URL the DeviceInfo block can be used
and a new type for it defined . The data passed would likely be the and a new type for it defined . The data passed would likely be the
same in both cases. Considerations for choosing which mechanism to same in both cases. Considerations for choosing which mechanism to
register under include: register under include:
Applicability: Information which will be carried by many kinds of Applicability: Information which will be carried by many kinds of
skipping to change at page 23, line 46 skipping to change at page 24, line 13
DeviceInfo block, rather than a new block so that implementations DeviceInfo block, rather than a new block so that implementations
are not tempted to send the data by value. Conversely, data which are not tempted to send the data by value. Conversely, data which
is small may best be sent in a separate block so that it can be is small may best be sent in a separate block so that it can be
sent by value sent by value
Availability of a server: Providing the data via the device block Availability of a server: Providing the data via the device block
requires a server be made available to retrieve the data. requires a server be made available to retrieve the data.
Providing the data via new block allows it to be sent by value Providing the data via new block allows it to be sent by value
(CID). (CID).
3.3.10. emergencyCallData.DeviceInfo Example 3.3.9. EmergencyCallData.DeviceInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:emergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>string0987654321@example.org
</dev:DataProviderReference>
<dev:id>12345</dev:id> <dev:id>12345</dev:id>
<dev:DeviceClassification>Fixed phone</dev:DeviceClassification> <dev:DeviceClassification>Fixed phone</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>35788104</dev:UniqueDeviceID> <dev:UniqueDeviceID TypeOfDeviceID="IMEI">35788104
<dev:TypeOfDeviceID>IMEI</dev:TypeOfDeviceID> </dev:UniqueDeviceID>
</dev:emergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
Figure 7: emergencyCallData.DeviceInfo Example. Figure 7: EmergencyCallData.DeviceInfo Example.
3.4. Owner/Subscriber Information 3.4. Owner/Subscriber Information
This block describes the owner of the device (if provided by the This block describes the owner of the device (if provided by the
device) or the subscriber information, if provided by a service device) or the subscriber information, if provided by a service
provider. The contact location is not necessarily the location of provider. The contact location is not necessarily the location of
the caller or incident, but is rather the nominal contact address. the caller or incident, but is rather the nominal contact address.
The mime subtype is "application/emergencyCall.Subscriber+xml". The mime subtype is "application/EmergencyCallData.Subscriber+xml".
In some jurisdictions some or all parts of the subscriber-specific In some jurisdictions some or all parts of the subscriber-specific
information are subject to privacy constraints. These constraints information are subject to privacy constraints. These constraints
vary but dictate what information and be displayed and logged. A vary but dictate what information and be displayed and logged. A
general privacy indicator expressing a desire for privacy is general privacy indicator expressing a desire for privacy is
provided. The interpretation of how this is applied is left to the provided. The interpretation of how this is applied is left to the
receiving jurisdiction as the custodians of the local regulatory receiving jurisdiction as the custodians of the local regulatory
requirements. requirements.
3.4.1. Subscriber Data Privacy Indicator 3.4.1. Subscriber Data Privacy Indicator
skipping to change at page 25, line 30 skipping to change at page 25, line 47
than one TEL property is provided, a parameter from the vCard than one TEL property is provided, a parameter from the vCard
Property Value registry MUST be specified on each TEL. Property Value registry MUST be specified on each TEL.
Reason for Need: When the caller is unable to provide information, Reason for Need: When the caller is unable to provide information,
this data may be used to obtain it this data may be used to obtain it
How Used by Call Taker: Obtaining critical information about the How Used by Call Taker: Obtaining critical information about the
caller and possibly the location when it is not able to be caller and possibly the location when it is not able to be
obtained otherwise. obtained otherwise.
3.4.3. emergencyCallData.SubscriberInfo Example 3.4.3. EmergencyCallData.SubscriberInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<sub:emergencyCallData.SubscriberInfo <sub:EmergencyCallData.SubscriberInfo
xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
privacyRequested="false"> privacyRequested="false">
<sub:id>12345</sub:id> <sub:DataProviderReference>string0987654321@example.org
</sub:DataProviderReference>
<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcards> <vcards>
<vcard> <vcard>
<fn><text>Simon Perreault</text></fn> <fn><text>Simon Perreault</text></fn>
<n> <n>
<surname>Perreault</surname> <surname>Perreault</surname>
<given>Simon</given> <given>Simon</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix>ing. jr</suffix> <suffix>ing. jr</suffix>
skipping to change at page 27, line 34 skipping to change at page 28, line 4
<uri> <uri>
http://www.viagenie.ca/simon.perreault/simon.asc http://www.viagenie.ca/simon.perreault/simon.asc
</uri> </uri>
</key> </key>
<tz><text>America/Montreal</text></tz> <tz><text>America/Montreal</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://nomis80.org</uri> <uri>http://nomis80.org</uri>
</url> </url>
</vcard> </vcard>
</vcards> </vcards>
</sub:SubscriberData> </sub:SubscriberData>
</sub:emergencyCallData.SubscriberInfo> </sub:EmergencyCallData.SubscriberInfo>
Figure 8: emergencyCallData.SubscriberInfo Example. Figure 8: EmergencyCallData.SubscriberInfo Example.
3.5. Comment 3.5. Comment
This block provides a mechanism for the data provider to supply This block provides a mechanism for the data provider to supply
extra, human readable information to the PSAP. It is not intended extra, human readable information to the PSAP. It is not intended
for a general purpose extension mechanism nor does it aim to provide for a general purpose extension mechanism nor does it aim to provide
machine-reable content. The mime subtype is "application/ machine-reable content. The mime subtype is "application/
emergencyCall.Comment+xml" EmergencyCallData.Comment+xml"
3.5.1. Comment 3.5.1. Comment
Data Element: EmergencyCall.Comment Data Element: EmergencyCallData.Comment
Use: Optional Use: Optional
XML Element: <Comment> XML Element: <Comment>
Description: Human readable text providing additional information to Description: Human readable text providing additional information to
the PSAP staff. the PSAP staff.
Reason for Need: Explanatory information for values in the data Reason for Need: Explanatory information for values in the data
structure structure
How Used by Call Taker: To interpret the data provided How Used by Call Taker: To interpret the data provided
3.5.2. emergencyCallData.Comment Example 3.5.2. EmergencyCallData.Comment Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<com:emergencyCallData.Comment <com:EmergencyCallData.Comment
xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:comment" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<com:id>12345</com:id> <com:DataProviderReference>string0987654321@example.org
</com:DataProviderReference>
<com:Comment xml:lang="en">This is an example text.</com:Comment> <com:Comment xml:lang="en">This is an example text.</com:Comment>
</com:emergencyCallData.Comment> </com:EmergencyCallData.Comment>
Figure 9: EmergencyCallData.Comment Example. Figure 9: EmergencyCallData.Comment Example.
4. Transport 4. Data Transport Mechanisms
This section defines how to convey additional data to an emergency This section defines how to convey additional data to an emergency
service provider. Two different means are specified: the first uses service provider. Two different means are specified: the first uses
the call signaling; the second uses the <provided-by> element of a the call signaling; the second uses the <provided-by> element of a
PIDF-LO [RFC4119]. PIDF-LO [RFC4119].
1. First, the ability to embed a Uniform Resource Identifier (URI) 1. First, the ability to embed a Uniform Resource Identifier (URI)
in an existing SIP header field, the Call-Info header, is in an existing SIP header field, the Call-Info header, is
defined. The URI points to the additional data structure. The defined. The URI points to the additional data structure. The
Call-Info header is specified in Section 20.9 of [RFC3261]. This Call-Info header is specified in Section 20.9 of [RFC3261]. This
document adds a new compound token starting with the value 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 contains either an 'EmergencyCallData', then the Call-Info header contains either an
HTTPS URL pointing to an external resource or a CID (content HTTPS URL pointing to an external resource or a CID (content
indirection) URI that allows the data structure to be placed in indirection) URI that allows the data structure to be placed in
the body of the SIP message. The "purpose" parameter also the body of the SIP message. The "purpose" parameter also
indicates the kind of data (by its MIME type) that is available indicates the kind of data (by its MIME type) that is available
at the URI. As the data is conveyed using a URI in the SIP at the URI. As the data is conveyed using a URI in the SIP
signaling, the data itself may reside on an external resource, or signaling, the data itself may reside on an external resource, or
may be contained within the body of the SIP message. When the may be contained within the body of the SIP message. When the
URI refers to data at an external resource, the data is said to URI refers to data at an external resource, the data is said to
be passed by reference. When the URI refers to data contained be passed by reference. When the URI refers to data contained
within the body of the SIP message, the data is said to be passed within the body of the SIP message, the data is said to be passed
skipping to change at page 31, line 4 skipping to change at page 30, line 39
or referenced in the SIP signaling (using the Call-Info header field) or referenced in the SIP signaling (using the Call-Info header field)
or in the <provided-by> element of a PIDF-LO. Every block must be or in the <provided-by> element of a PIDF-LO. Every block must be
one of the types in the registry. Since the data of an emergency one of the types in the registry. Since the data of an emergency
call may come from multiple sources, the data itself needs call may come from multiple sources, the data itself needs
information describing the source. Consequently, each entity adding information describing the source. Consequently, each entity adding
additional data MUST supply the "Data Provider" block. All other additional data MUST supply the "Data Provider" block. All other
blocks are optional, but each entity SHOULD supply any blocks where blocks are optional, but each entity SHOULD supply any blocks where
it has at least some of the information in the block. it has at least some of the information in the block.
4.1. Transmitting Blocks using the Call-Info Header 4.1. Transmitting Blocks using the Call-Info Header
A URI to a block MAY be inserted in a SIP request or response method A URI to a block MAY be inserted in a SIP request or response method
(most often INVITE or MESSAGE) with a Call-Info header field (most often INVITE or MESSAGE) with a Call-Info header field
containing a purpose value starting with 'emergencyCallData' and the containing a purpose value starting with 'EmergencyCallData' and the
type of data available at the URI. The type of data is denoted by type of data available at the URI. The type of data is denoted by
including the root of the MIME type (not including the including the root of the MIME type (not including the
'emergencyCall' prefix and any suffix such as '+xml') with a '.' 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.'
separator. For example, when referencing a block with MIME type separator. For example, when referencing a block with MIME type
'application/emergencyCall.ProviderInfo+xml', the 'purpose' parameter 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose'
is set to 'emergencyCallData.ProviderInfo'. An example "Call-Info" parameter is set to 'EmergencyCallData.ProviderInfo'. An example
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 with a purpose value starting with A Call-info header with a purpose value starting with
'emergencyCallData' MUST only be sent on an emergency call, which can 'EmergencyCallData' MUST only be sent on an emergency call, which can
be ascertained by the presence of an emergency service urn in a Route be ascertained by the presence of an emergency service urn in a Route
header of a SIP message. header of a SIP message.
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 applied
for protecting the retrieval of the information. for protecting the retrieval of the information.
The data may also be supplied by value in a SIP message. In this The data may also be supplied by value in a SIP message. In this
case, Content Indirection (CID) [RFC2392] is used, with the CID URL case, Content Indirection (CID) [RFC2392] is used, with the CID URL
referencing the MIME body part. referencing the MIME body part.
More than one Call-Info header with a purpose value starting with More than one Call-Info header with a purpose value starting with
'emergencyCallData' can be expected, but at least one MUST be '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 if it knows no 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. Any service provider in the path of the
call MUST insert its own. For example, a device, a telematics call MUST insert its own. For example, a device, a telematics
service provider in the call path, as well as the mobile carrier service provider in the call path, as well as the mobile carrier
handling the call will each provide one. There may be circumstances handling the call will each provide one. There may be circumstances
where there is a service provider who is unaware that the call is an where there is a service provider who is unaware that the call is an
emergency call and cannot reasonably be expected to determine that it emergency call and cannot reasonably be expected to determine that it
is an emergency call. In that case, that service provider is not is an emergency call. In that case, that service provider is not
expected to provide emergencyCallData. expected to provide EmergencyCallData.
4.2. Transmitting Blocks by Reference using the Provided-By Element 4.2. Transmitting Blocks by Reference using the Provided-By Element
The 'emergencyCallDataReference' element is used to transmit an The 'EmergencyCallDataReference' element is used to transmit an
additional data block by reference within a 'Provided-By' element of additional data block by reference within a 'Provided-By' element of
a PIDF-LO. The 'emergencyCallDataReference' element has two a PIDF-LO. The 'EmergencyCallDataReference' element has two
attributes: 'ref' to specify the URL, and 'purpose' to indicate the attributes: 'ref' to specify the URL, and 'purpose' to indicate the
type of data block referenced. The value of 'ref' is an HTTPS URL type of data block referenced. The value of 'ref' is an HTTPS URL
that resolves to a data structure with information about the call. that resolves to a data structure with information about the call.
The value of 'purpose' is the same as used in a 'Call-Info' header The value of 'purpose' is the same as used in a 'Call-Info' header
field (as specified in Section 4.1). field (as specified in Section 4.1).
For example, to reference a block with MIME type 'application/ For example, to reference a block with MIME type 'application/
emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set
'emergencyCallData.ProviderInfo'. An example to 'EmergencyCallData.ProviderInfo'. An example
'emergencyCallDataReference' element for this would be: 'EmergencyCallDataReference' element for this would be:
<emergencyCallDataReference ref="https://www.example.com/23sedde3" <EmergencyCallDataReference ref="https://www.example.com/23sedde3"
purpose="emergencyCallData.ProviderInfo"/> purpose="EmergencyCallData.ProviderInfo"/>
4.3. Transmitting Blocks by Value using the Provided-By Element 4.3. Transmitting Blocks by Value using the Provided-By Element
It is RECOMMENDED that access networks supply the data specified in It is RECOMMENDED that access networks supply the data specified in
this document by reference, but they MAY provide the data by value. this document by reference, but they MAY provide the data by value.
The 'emergencyCallDataValue' element is used to transmit an The 'EmergencyCallDataValue' element is used to transmit an
additional data block by value within a 'Provided-By' element of a additional data block by value within a 'Provided-By' element of a
PIDF-LO. The 'emergencyCallDataValue' element has one attribute: PIDF-LO. The 'EmergencyCallDataValue' element has one attribute:
'purpose' to indicate the type of data block contained. The value of 'purpose' to indicate the type of data block contained. The value of
'purpose' is the same as used in a 'Call-Info' header field (as 'purpose' is the same as used in a 'Call-Info' header field (as
specified in Section 4.1, and in Section 4.1). The same XML specified in Section 4.1, and in Section 4.1). The same XML
structure as would be contained in the corresponding MIME type body structure as would be contained in the corresponding MIME type body
part is placed inside the 'emergencyCallDataValue' element. part is placed inside the 'EmergencyCallDataValue' element.
For example: For example:
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<emergencyCallData> <EmergencyCallData>
<byRef purpose="emergencyCallData.ServiceInfo" <byRef purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2"/> ref="https://example.com/ref2"/>
<sub:emergencyCall.Comment <sub:EmergencyCallData.Comment
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"> xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData.Comment">
<sub:Comment xml:lang="en">This is an example text. <sub:Comment xml:lang="en">This is an example text.
</sub:Comment> </sub:Comment>
</sub:emergencyCall.Comment> </sub:EmergencyCallData.Comment>
</emergencyCallData> </EmergencyCallData>
<emergencyCallDataValue <EmergencyCallDataValue
purpose="emergencyCallData.ProviderInfo"> purpose="EmergencyCallData.ProviderInfo">
<ProviderID>Test</ProviderID> <ProviderID>Test</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProviderID>Access Infrastructure Provider <TypeOfProviderID>Access Infrastructure Provider
</TypeOfProviderID> </TypeOfProviderID>
<ContactURI>sip:15555550987@burf.example.com;user=phone <ContactURI>sip:15555550987@burf.example.com;user=phone
</ContactURI> </ContactURI>
</emergencyCallDataValue> </EmergencyCallDataValue>
</provided-by> </provided-by>
Example Provided-By by Value. Example Provided-By by Value.
4.4. The Content-Disposition Parameter 4.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'
skipping to change at page 33, line 49 skipping to change at page 33, line 38
--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/emergencyCall.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference; handling=optional Content-Disposition: by-reference; handling=optional
...Data provider information data goes in here ...Data provider information data goes in here
--boundary1-- --boundary1--
Figure 10: Example for use of the Content-Disposition Parameter in Figure 10: Example for use of the Content-Disposition Parameter in
SIP. SIP.
skipping to change at page 35, line 20 skipping to change at page 35, line 11
INVITE urn:service:sos SIP/2.0 INVITE urn:service:sos SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=emergencyCallData.ProviderInfo, ;purpose=EmergencyCallData.ProviderInfo,
<cide:0123456789@atlanta.example.com> <cide:0123456789@atlanta.example.com>
;purpose=emergencyCallData.DeviceInfo ;purpose=EmergencyCallData.DeviceInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/emergencyCallProviderinfo+xml application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Contact: <sips:hannes@example.com> Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...SDP goes here ...SDP goes here
--boundary1-- --boundary1--
Content-Type: application/emergencyCallData.DeviceInfo+xml Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-ID: <0123456789@atlanta.example.com> Content-ID: <0123456789@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:emergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:id>12345</svc:id> <dev:DataProviderReference>string0987654321@example.org
</dev:DataProviderReference>
<dev:DeviceClassification>SoftPhn</dev:DeviceClassification> <dev:DeviceClassification>SoftPhn</dev:DeviceClassification>
<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID> <dev:UniqueDeviceID
<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:emergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/emergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:emergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:id>12345</pi:id> <pi:id>12345</pi:id>
<pi:DataProviderReference>string0987654321@example.org
</pi:DataProviderReference>
<pi:DataProviderString>Hannes Tschofenig <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString> </pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>sip:hannes@example.com</pi:ContactURI> <pi:ContactURI>sip:hannes@example.com</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>EN</pi:Language>
<xc:DataProviderContact <xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
skipping to change at page 37, line 51 skipping to change at page 37, line 45
</uri> </uri>
</key> </key>
<tz><text>Finland/Helsinki</text></tz> <tz><text>Finland/Helsinki</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://example.com/hannes.tschofenig</uri> <uri>http://example.com/hannes.tschofenig</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:emergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
--boundary1-- --boundary1--
Figure 12: End Device sending SIP INVITE with Additional Data. Figure 12: End Device sending SIP INVITE with Additional Data.
In this example, information available to the access network operator In this example, information available to the access network operator
is included in the call setup message only indirectly via the use of is included in the call setup message only indirectly via the use of
the location reference. The PSAP has to retrieve it via a separate the location reference. The PSAP has to retrieve it via a separate
look-up step. Since the access network provider and the VoIP service look-up step. Since the access network provider and the VoIP service
provider are two independent entities in this scenario the access provider are two independent entities in this scenario, the access
network operator is not involved in the processing of application network operator is not involved in application layer exchanges; the
layer exchanges and forwards the SIP INVITE transparently, as SIP INVITE transits the access network transparently, as illustrated
illustrated in step #1. No change to the SIP INVITE is applied. in step #1. No change to the SIP INVITE is applied.
When the VoIP service provider receives the message and determines When the VoIP service provider receives the message and determines
based on the Service URN that the incoming request is an emergency based on the Service URN that the incoming request is an emergency
call. It performs the typical emergency services related tasks, call. It performs the typical emergency services related tasks,
including location-based routing, and adds additional data, namely including location-based routing, and adds additional data, namely
service and subscriber information, to the outgoing message. For the service and subscriber information, to the outgoing message. For the
example we assume a VoIP service provider that deploys a back-to-back example we assume a VoIP service provider that deploys a back-to-back
user agent allowing additional data to be included in the body of the user agent allowing additional data to be included in the body of the
SIP message (rather than per reference in the header), which allows SIP message (rather than per reference in the header), which allows
us to illustrate the use of multiple data provider info blocks. The us to illustrate the use of multiple data provider info blocks. The
skipping to change at page 38, line 37 skipping to change at page 38, line 31
INVITE sips:psap@example.org SIP/2.0 INVITE sips:psap@example.org SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;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 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...SDP goes here ...SDP goes here
--boundary1-- --boundary1--
Content-Type: application/emergencyCallData.DeviceInfo+xml Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-ID: <0123456789@atlanta.example.com> Content-ID: <0123456789@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:emergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:id>12345</svc:id> <dev:DataProviderReference>string0987654321@example.org
</dev:DataProviderReference>
<dev:DeviceClassification>SoftPhn</dev:DeviceClassification> <dev:DeviceClassification>SoftPhn</dev:DeviceClassification>
<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID> <dev:UniqueDeviceID
<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:emergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/emergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:emergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:id>12345</pi:id> <pi:DataProviderReference>string0987654321@example.org
<pi:DataProviderString>Hannes Tschofenig </pi:DataProviderReference>
</pi:DataProviderString> <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>sip:hannes@example.com</pi:ContactURI> <pi:ContactURI>sip:hannes@example.com</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>EN</pi:Language>
<xc:DataProviderContact <xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
skipping to change at page 41, line 23 skipping to change at page 41, line 19
</uri> </uri>
</key> </key>
<tz><text>Finland/Helsinki</text></tz> <tz><text>Finland/Helsinki</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://example.com/hannes.tschofenig</uri> <uri>http://example.com/hannes.tschofenig</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:emergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
--boundary1-- --boundary1--
Content-Type: application/emergencyCall.ServiceInfo+xml Content-Type: application/EmergencyCallData.ServiceInfo+xml
Content-ID: <bloorpyhex@atlanta.example.com> Content-ID: <bloorpyhex@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<svc:emergencyCall.ServiceInfo <svc:EmergencyCallData.ServiceInfo
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData.ServiceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:id>abc123</svc:id> <svc:DataProviderReference>string0987654321@example.org
</svc:DataProviderReference>
<svc:SvcEnvironment>Residence</svc:SvcEnvironment> <svc:SvcEnvironment>Residence</svc:SvcEnvironment>
<svc:SvcDelByProvider>VOIP</svc:SvcDelByProvider> <svc:SvcDelByProvider>VOIP</svc:SvcDelByProvider>
<svc:SvcMobility>Unknown</svc:SvcMobility> <svc:SvcMobility>Unknown</svc:SvcMobility>
</svc:emergencyCall.ServiceInfo> </svc:EmergencyCallData.ServiceInfo>
--boundary1-- --boundary1--
Content-Type: application/emergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <aaabbb@atlanta.example.com> Content-ID: <aaabbb@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:emergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:id>abc123</pi:id> <pi:DataProviderReference>string0987654321@example.org
<pi:DataProviderString>Example VoIP Provider </pi:DataProviderReference>
<pi:DataProviderString>Example VoIP Provider
</pi:DataProviderString> </pi:DataProviderString>
<pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID> <pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID>
<pi:ProviderIDSeries>NENA</pi:ProviderIDSeries> <pi:ProviderIDSeries>NENA</pi:ProviderIDSeries>
<pi:TypeOfProvider>Service Provider</pi:TypeOfProvider> <pi:TypeOfProvider>Service Provider</pi:TypeOfProvider>
<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI> <pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>EN</pi:Language>
<xc:DataProviderContact <xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>John Doe</text></fn> <fn><text>John Doe</text></fn>
<n> <n>
skipping to change at page 43, line 29 skipping to change at page 43, line 27
<uri>geo:51.503396, 0.127640</uri> <uri>geo:51.503396, 0.127640</uri>
</geo> </geo>
<tz><text>Europe/London</text></tz> <tz><text>Europe/London</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://www.example.com/john.doe</uri> <uri>http://www.example.com/john.doe</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:emergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
Figure 13: VoIP Provider sending SIP INVITE with Additional Data. Figure 13: VoIP Provider sending SIP INVITE with Additional Data.
Finally, the PSAP requests location information from the access Finally, the PSAP requests location information from the access
network operator. The response is shown in Figure 14. Along with network operator. The response is shown in Figure 14. Along with
the location information additional data is provided in the the location information additional data is provided in the
<Provided-By> element of the PIDF-LO. <Provided-By> element of the PIDF-LO.
<?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"
skipping to change at page 44, line 27 skipping to change at page 44, line 25
</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>
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:emergencycalldata"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<emergencyCallDataReference purpose="emergencyCallData.ServiceInfo" <EmergencyCallDataReference purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2"/> ref="https://example.com/ref2"/>
<emergencyCallDataValue> <EmergencyCallDataValue>
<emergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>string0987654321@example.org
</DataProviderReference>
<DataProviderString>University of California, Irvine <DataProviderString>University of California, Irvine
</DataProviderString> </DataProviderString>
<ProviderID>urn:nena:companyid:uci</ProviderID> <ProviderID>urn:nena:companyid:uci</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Other</TypeOfProvider> <TypeOfProvider>Other</TypeOfProvider>
<ContactURI>tel:+1 9498245222</ContactURI> <ContactURI>tel:+1 9498245222</ContactURI>
<Language>EN</Language> <Language>EN</Language>
</emergencyCallData.ProviderInfo> </EmergencyCallData.ProviderInfo>
<emergencyCallData.Comment <EmergencyCallData.Comment
xmlns="urn:ietf:params:xml:ns:emergencycalldata:comment"> xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<DataProviderReference>string0987654321@example.org
</DataProviderReference>
<Comment xml:lang="en">This is an example text.</Comment> <Comment xml:lang="en">This is an example text.</Comment>
</emergencyCallData.Comment> </EmergencyCallData.Comment>
</EmergencyCallDataValue>
</emergencyCallDataValue>
</provided-by> </provided-by>
</gp:geopriv> </gp:geopriv>
<dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID> <dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID>
<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp> <dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>
</dm:device> </dm:device>
</presence> </presence>
Figure 14: Access Network Provider returning PIDF-LO with Additional Figure 14: Access Network Provider returning PIDF-LO with Additional
Data. Data.
6. XML Schemas 6. XML Schemas
This section defines the XML schemas of the five data blocks. This section defines the XML schemas of the five data blocks.
Additionally, the Provided-By schema is specified. Additionally, the Provided-By schema is specified.
6.1. emergencyCallData.ProviderInfo XML Schema 6.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"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0">
<xs:simpleType name="iso3166a2"> <xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/> <xs:pattern value="[A-Z]{2}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:element <xs:element
name="emergencyCallData.ProviderInfo" name="EmergencyCallData.ProviderInfo"
type="pi:ProviderInfoType"/> type="pi:ProviderInfoType"/>
<xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:simpleType name="SubcontractorPriorityType"> <xs:simpleType name="SubcontractorPriorityType">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="sub"/> <xs:enumeration value="sub"/>
<xs:enumeration value="main"/> <xs:enumeration value="main"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="ProviderInfoType"> <xs:complexType name="ProviderInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="id"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="DataProviderString" <xs:element name="DataProviderString"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
skipping to change at page 46, line 47 skipping to change at page 46, line 52
<xs:element name="SubcontractorPriority" <xs:element name="SubcontractorPriority"
type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/> type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 15: emergencyCallData.ProviderInfo XML Schema. Figure 15: EmergencyCallData.ProviderInfo XML Schema.
6.2. emergencyCallData.ServiceInfo XML Schema 6.2. EmergencyCallData.ServiceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo" "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCallData.ServiceInfo" type="svc:ServiceInfoType"/> <xs:element name="EmergencyCallData.ServiceInfo" type="svc:ServiceInfoType"/>
<xs:complexType name="ServiceInfoType"> <xs:complexType name="ServiceInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="DataProviderReference"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcEnvironment" <xs:element name="SvcEnvironment"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcDelByProvider" <xs:element name="SvcDelByProvider"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcMobility" <xs:element name="SvcMobility"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Link" <xs:element name="Link"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 16: emergencyCallData.ServiceInfo XML Schema. Figure 16: EmergencyCallData.ServiceInfo XML Schema.
6.3. emergencyCallData.DeviceInfo XML Schema 6.3. EmergencyCallData.DeviceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCallData.DeviceInfo" type="dev:DeviceInfoType"/> <xs:element name="EmergencyCallData.DeviceInfo" type="dev:DeviceInfoType"/>
<xs:complexType name="DeviceInfoType"> <xs:complexType name="DeviceInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="DataProviderReference"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="DeviceClassification" <xs:element name="DeviceClassification"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceMfgr" <xs:element name="DeviceMfgr"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceModelNr" <xs:element name="DeviceModelNr"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="UniqueDeviceID" <xs:element name="UniqueDeviceID" minOccurs="0"
type="xs:string" minOccurs="0" maxOccurs="1"/> maxOccurs="unbounded">
<xs:complexType>
<xs:element name="TypeOfDeviceID" <xs:simpleContent>
type="xs:string" minOccurs="0" maxOccurs="1"/> <xs:extension base="xs:string">
<xs:attribute name="TypeOfDeviceID"
type="xs:string"
use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="DeviceSpecificData" <xs:element name="DeviceSpecificData"
type="xs:anyURI" minOccurs="0" maxOccurs="1"/> type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceSpecificType" <xs:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 17: emergencyCallData.DeviceInfo XML Schema. Figure 17: EmergencyCallData.DeviceInfo XML Schema.
6.4. emergencyCallData.SubscriberInfo XML Schema 6.4. EmergencyCallData.SubscriberInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo" "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>
<xs:element name="emergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType"/> <xs:element name="EmergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType"/>
<xs:complexType name="SubscriberInfoType"> <xs:complexType name="SubscriberInfoType">
<xs:complexContent> <xs:complexContent>
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="DataProviderReference"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="SubscriberData" type="xc:vcardType" <xs:element name="SubscriberData" type="xc:vcardType"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="privacyRequested" type="xs:boolean" use="required"/> <xs:attribute name="privacyRequested" type="xs:boolean" use="required"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 18: emergencyCallData.SubscriberInfo XML Schema. Figure 18: EmergencyCallData.SubscriberInfo XML Schema.
6.5. emergencyCallData.Comment XML Schema 6.5. EmergencyCallData.Comment XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:emergencycalldata:comment" "urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCallData.Comment" type="com:CommentType"/> <xs:element name="EmergencyCallData.Comment" type="com:CommentType"/>
<xs:complexType name="CommentType"> <xs:complexType name="CommentType">
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="DataProviderReference"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="Comment" <xs:element name="Comment"
type="com:CommentSubType" minOccurs="0" type="com:CommentSubType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<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>
skipping to change at page 50, line 40 skipping to change at page 51, line 12
Figure 19: EmergencyCallData.Comment XML Schema. Figure 19: EmergencyCallData.Comment XML Schema.
6.6. Provided-By XML Schema 6.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:pidf:geopriv10: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:pidf:geopriv10: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"
xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo" xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"/> <xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo"/> <xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"/> <xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"/> <xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:comment"/> <xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:Comment"/>
<xs:element name="provided-by" type="ad:provided-by-Type"/> <xs:element name="provided-by" type="ad:provided-by-Type"/>
<xs:complexType name="provided-by-Type"> <xs:complexType name="provided-by-Type">
<xs:sequence> <xs:sequence>
<xs:element name="id" <xs:element name="DataProviderReference"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="emergencyCallDataReference" <xs:element name="EmergencyCallDataReference"
type="ad:ByRefType" type="ad:ByRefType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="emergencyCallDataValue" <xs:element name="EmergencyCallDataValue"
type="ad:emergencyCallDataValueType" type="ad:EmergencyCallDataValueType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<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>
<!-- Additional Data By Reference --> <!-- Additional Data By Reference -->
skipping to change at page 51, line 50 skipping to change at page 52, line 21
<xs:attribute name="purpose" type="xs:anyURI" <xs:attribute name="purpose" type="xs:anyURI"
use="required"/> use="required"/>
<xs:attribute name="ref" type="xs:anyURI" <xs:attribute name="ref" type="xs:anyURI"
use="required"/> use="required"/>
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- Additional Data By Value --> <!-- Additional Data By Value -->
<xs:complexType name="emergencyCallDataValueType"> <xs:complexType name="EmergencyCallDataValueType">
<xs:sequence> <xs:sequence>
<xs:element name="emergencyCallData.ProviderInfo" <xs:element name="EmergencyCallData.ProviderInfo"
type="pi:ProviderInfoType" type="pi:ProviderInfoType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="emergencyCallData.ServiceInfo" <xs:element name="EmergencyCallData.ServiceInfo"
type="svc:ServiceInfoType" type="svc:ServiceInfoType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="emergencyCallData.DeviceInfo" <xs:element name="EmergencyCallData.DeviceInfo"
type="dev:DeviceInfoType" type="dev:DeviceInfoType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="emergencyCallData.SubscriberInfo" <xs:element name="EmergencyCallData.SubscriberInfo"
type="sub:SubscriberInfoType" type="sub:SubscriberInfoType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="emergencyCallData.Comment" <xs:element name="EmergencyCallData.Comment"
type="com:CommentType" type="com:CommentType"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<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>
skipping to change at page 59, line 36 skipping to change at page 60, line 9
+--------------+------------+ +--------------+------------+
| ProviderInfo | [This RFC] | | ProviderInfo | [This RFC] |
| ServiceInfo | [This RFC] | | ServiceInfo | [This RFC] |
| DeviceInfo | [This RFC] | | DeviceInfo | [This RFC] |
| Subscriber | [This RFC] | | Subscriber | [This RFC] |
| Comment | [This RFC] | | Comment | [This RFC] |
+--------------+------------+ +--------------+------------+
Figure 24: Additional Data Blocks Registry. Figure 24: Additional Data Blocks Registry.
9.2. 'emergencyCallData' Purpose Parameter Value 9.2. 'EmergencyCallData' Purpose Parameter Value
This document defines the 'emergencyCallData' value for the "purpose" This document defines the 'EmergencyCallData' value for the "purpose"
parameter of the Call-Info header field. The Call-Info header and parameter of the Call-Info header field. The Call-Info header and
the corresponding registry for the 'purpose' parameter was the corresponding registry for the 'purpose' parameter was
established with RFC 3261 [RFC3261]. established with RFC 3261 [RFC3261].
Header Parameter New Header Parameter New
Field Name Value Reference Field Name Value Reference
---------- --------- ----------------- --------- ---------- --------- ----------------- ---------
Call-Info purpose emergencyCallData [This RFC] Call-Info purpose EmergencyCallData [This RFC]
9.3. URN Sub-Namespace Registration for provided-by Registry Entry 9.3. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in Section 9.5.1 in This section registers the namespace specified in Section 9.5.1 in
the provided-by registry established by RFC 4119, for usage within the provided-by registry established by RFC 4119, for usage within
the <provided-by> element of a PIDF-LO. the <provided-by> element of a PIDF-LO.
The schema for the provided-by schema used by this document is The schema for the provided-by schema used by this document is
specified in Section 6.6. specified in Section 6.6.
9.4. MIME Registrations 9.4. MIME Registrations
9.4.1. MIME Content-type Registration for 'application/ 9.4.1. MIME Content-type Registration for 'application/
emergencyCallData.ProviderInfo+xml' EmergencyCallData.ProviderInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.ProviderInfo+xml MIME subtype name: EmergencyCallData.ProviderInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset Indicates the character encoding of
enclosed XML. enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 61, line 15 skipping to change at page 61, line 37
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
9.4.2. MIME Content-type Registration for 'application/ 9.4.2. MIME Content-type Registration for 'application/
emergencyCallData.ServiceInfo+xml' EmergencyCallData.ServiceInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.ServiceInfo+xml MIME subtype name: EmergencyCallData.ServiceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset Indicates the character encoding of
enclosed XML. enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 62, line 15 skipping to change at page 62, line 37
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
9.4.3. MIME Content-type Registration for 'application/ 9.4.3. MIME Content-type Registration for 'application/
emergencyCallData.DeviceInfo+xml' EmergencyCallData.DeviceInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.DeviceInfo+xml MIME subtype name: EmergencyCallData.DeviceInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset Indicates the character encoding of
enclosed XML. enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 63, line 15 skipping to change at page 63, line 37
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
9.4.4. MIME Content-type Registration for 'application/ 9.4.4. MIME Content-type Registration for 'application/
emergencyCallData.SubscriberInfo+xml' EmergencyCallData.SubscriberInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.SubscriberInfo+xml MIME subtype name: EmergencyCallData.SubscriberInfo+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset Indicates the character encoding of
enclosed XML. enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 64, line 15 skipping to change at page 64, line 37
Tschofenig, Hannes.Tschofenig@gmx.net Tschofenig, Hannes.Tschofenig@gmx.net
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
9.4.5. MIME Content-type Registration for 'application/ 9.4.5. MIME Content-type Registration for 'application/
emergencyCallData.Comment+xml' EmergencyCallData.Comment+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
MIME media type name: application MIME media type name: application
MIME subtype name: emergencyCallData.Comment+xml MIME subtype name: EmergencyCallData.Comment+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: charset Indicates the character encoding of Optional parameters: charset Indicates the character encoding of
enclosed XML. enclosed XML.
Encoding considerations: Uses XML, which can employ 8-bit Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See characters, depending on the character encoding used. See
Section 3.2 of RFC 3023 [RFC3023]. Section 3.2 of RFC 3023 [RFC3023].
skipping to change at page 65, line 16 skipping to change at page 65, line 38
Intended usage: LIMITED USE Intended usage: LIMITED USE
Author: This specification is a work item of the IETF ECRIT Author: This specification is a work item of the IETF ECRIT
working group, with mailing list address <ecrit@ietf.org>. working group, with mailing list address <ecrit@ietf.org>.
Change controller: The IESG <ietf@ietf.org> Change controller: The IESG <ietf@ietf.org>
9.5. URN Sub-Namespace Registration 9.5. URN Sub-Namespace Registration
9.5.1. Registration for urn:ietf:params:xml:ns:emergencycalldata 9.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:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 65, line 46 skipping to change at page 66, line 20
<title>Namespace for Additional Emergency Call Data</title> <title>Namespace for Additional Emergency Call Data</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.5.2. Registration for 9.5.2. Registration for
urn:ietf:params:xml:ns:emergencycalldata:providerinfo urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencycalldata:providerinfo URI: urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 66, line 32 skipping to change at page 67, line 25
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Data Provider Information</h2> <h2>Data Provider Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.5.3. Registration for 9.5.3. Registration for
urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 67, line 12 skipping to change at page 68, line 4
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
Service Information</title> Service Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Service Information</h2> <h2>Service Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.5.4. Registration for 9.5.4. Registration for
urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 68, line 6 skipping to change at page 68, line 43
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Device Information</h2> <h2>Device Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.5.5. Registration for 9.5.5. Registration for
urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo URI: urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
skipping to change at page 68, line 38 skipping to change at page 69, line 29
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2> Owner/Subscriber Information</h2> <h2> Owner/Subscriber Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.5.6. Registration for 9.5.6. Registration for
urn:ietf:params:xml:ns:emergencycalldata:comment urn:ietf:params:xml:ns:EmergencyCallData:Comment
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencycalldata:comment URI: urn:ietf:params:xml:ns:EmergencyCallData:Comment
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
skipping to change at page 69, line 28 skipping to change at page 70, line 20
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
9.6. Schema Registrations 9.6. Schema Registrations
This specification registers five schemas, as per the guidelines in This specification registers five schemas, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:schema:emergencycalldata:providerinfo URI: urn:ietf:params:xml:schema:emergencycalldata:ProviderInfo
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Figure 15. XML: The XML schema can be found in Figure 15.
URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo
Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
skipping to change at page 71, line 5 skipping to change at page 71, line 43
and Robert (Bob) Sherry. and Robert (Bob) Sherry.
We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin
Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review
comments. comments.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC0822] Crocker, D., "Standard for the format of ARPA Internet
text messages", STD 11, RFC 822, August 1982.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. Locators", RFC 2392, August 1998.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, January 2001.
[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
 End of changes. 244 change blocks. 
412 lines changed or deleted 461 lines changed or added

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