draft-ietf-ecrit-additional-data-07.txt   draft-ietf-ecrit-additional-data-08.txt 
ECRIT B. Rosen ECRIT B.R. Rosen
Internet-Draft NeuStar Internet-Draft NeuStar
Intended status: Standards Track H. Tschofenig Intended status: Standards Track H. Tschofenig
Expires: August 30, 2013 Nokia Siemens Networks Expires: November 06, 2013 Nokia Siemens Networks
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
R. Gellens R. Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
February 26, 2013 May 05, 2013
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-07.txt draft-ietf-ecrit-additional-data-08.txt
Abstract Abstract
When an emergency call is sent to a Public Safety Answering Point When an emergency call is sent to a Public Safety Answering Point
(PSAP), the device that sends it, as well as any service provider in (PSAP), the device that sends it, as well as any application service
the path of the call, or access network through which the call provider in the path of the call, or access network provider through
originated may have information about the call which the PSAP may be which the call originated may have information about the call or the
able to use. This document describes an XML data structure to caller which the PSAP may be able to use. This document describes
contains such data and a Uniform Resource Identifier (URI) for data structures to convey such data to the PSAP. In addition, data
conveying the data to the PSAP. The URI may point to either an may also be included by reference, via a Uniform Resource Identifier
external resource, or the body of the SIP message. (URI) pointing to data found at an external resource. Consequently,
this document follows the tradition of prior emergency services
standardization work where data can be conveyed by value within the
call signaling (i.e., in body of the SIP message) and also by
reference.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 30, 2013. This Internet-Draft will expire on November 06, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents 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
skipping to change at page 2, line 15 skipping to change at page 2, line 19
(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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Block Overview . . . . . . . . . . . . . . . . . . . . . . . . 9 3. Data Structure Overview . . . . . . . . . . . . . . . . . . . 6
4. Transmitting Blocks of Additional Data . . . . . . . . . . . . 10 4. Transmitting Blocks of Additional Data . . . . . . . . . . . 7
4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 10 4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 8
4.2. Transmitting blocks by reference using Provided-By . . . . 11 4.2. Transmitting blocks by reference using Provided-By . . . 9
4.3. Transmitting blocks by value using Provided-By . . . . . . 12 4.3. Transmitting blocks by value using Provided-By . . . . . 9
5. Data Provider Information . . . . . . . . . . . . . . . . . . 13 5. Data Provider Information . . . . . . . . . . . . . . . . . . 10
5.1. Data Provider String . . . . . . . . . . . . . . . . . . . 13 5.1. Data Provider String . . . . . . . . . . . . . . . . . . 10
5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 13 5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . 11
5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 14 5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 11
5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 14 5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 12
5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 15 5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 13
5.6. Data Provider Languages(s) Supported . . . . . . . . . . . 16 5.6. Data Provider Languages(s) Supported . . . . . . . . . . 13
5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . . 16 5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . 14
5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 17 5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 15
5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . . 18 5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . 15
5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 19 5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 16
6. Service Information . . . . . . . . . . . . . . . . . . . . . 20 5.11. emergencyCall.ProviderInfo Example . . . . . . . . . . . 17
6.1. Service Environment . . . . . . . . . . . . . . . . . . . 20 6. Service Information . . . . . . . . . . . . . . . . . . . . . 19
6.2. Service Delivered by Provider to End User . . . . . . . . 20 6.1. Service Environment . . . . . . . . . . . . . . . . . . . 19
6.3. Service Mobility Environment . . . . . . . . . . . . . . . 22 6.2. Service Delivered by Provider to End User . . . . . . . . 20
6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 23 6.3. Service Mobility Environment . . . . . . . . . . . . . . 21
7. Device Information . . . . . . . . . . . . . . . . . . . . . . 24 6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 22
7.1. Device Classification . . . . . . . . . . . . . . . . . . 24 6.5. emergencyCall.SvcInfo Example . . . . . . . . . . . . . . 22
7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 26 7. Device Information . . . . . . . . . . . . . . . . . . . . . 23
7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 26 7.1. Device Classification . . . . . . . . . . . . . . . . . . 23
7.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 27 7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 25
7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 27 7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 25
7.6. Device/Service Specific Additional Data Structure . . . . 28 7.4. Unique Device Identifier . . . . . . . . . . . . . . . . 26
7.7. Device/Service Specific Additional Data Structure Type . . 29 7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 26
7.8. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . . 30 7.6. Device/Service Specific Additional Data Structure . . . . 27
8. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 31 7.7. Device/Service Specific Additional Data Structure Type . 28
8.1. xCard for Subscriber\\0x2019s Data . . . . . . . . . . . . 31 7.8. Choosing between defining a new type of block or new type
8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . . 32 of device/service specific additional data . . . . . . . 28
9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.9. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 29
9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.10. emergencyCall.DevInfo Example . . . . . . . . . . . . . . 30
9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . . 34 8. Owner/Subscriber Information . . . . . . . . . . . . . . . . 30
10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 8.1. xCard for Subscriber's Data . . . . . . . . . . . . . . . 30
11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 36 8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 31
12. Security Considerations . . . . . . . . . . . . . . . . . . . 37 8.3. emergencyCall.SubInfo Example . . . . . . . . . . . . . . 32
13. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 39 9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 34
14.1. Registry creation . . . . . . . . . . . . . . . . . . . . 40 9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . 34
14.1.1. Additional Call Data Blocks Registry . . . . . . . . 40 9.3. emergencyCall.Comment Example . . . . . . . . . . . . . . 35
14.1.2. Additional Call Data Service Provider Type 10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Registry . . . . . . . . . . . . . . . . . . . . . . 40 11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 36
14.1.3. Additional Call Data Service Delivered Registry . . . 41 12. Security Considerations . . . . . . . . . . . . . . . . . . . 37
14.1.4. Additional Call Data Device Classification 13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 38
Registry . . . . . . . . . . . . . . . . . . . . . . 42 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
14.1.5. Additional Call Data Device ID Type Registry . . . . 43 14.1. Registry creation . . . . . . . . . . . . . . . . . . . 38
14.1.6. Additional Call Data Blocks Registry . . . . . . . . 44 14.1.1. Additional Call Data Provider ID Series Registry . . 38
14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 44 14.1.2. Additional Call Data Service Provider Type Registry 39
14.3. URN Sub-Namespace Registration for provided-by 14.1.3. Additional Call Data Service Delivered Registry . . 40
Registry Entry . . . . . . . . . . . . . . . . . . . . . . 45 14.1.4. Additional Call Data Device Classification Registry 41
14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 46 14.1.5. Additional Call Data Device ID Type Type Registry . 42
14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 46 14.1.6. Device/Service Specific Additional Data Type
Registry . . . . . . . . . . . . . . . . . . . . . . 42
14.1.7. Additional Call Data Blocks Registry . . . . . . . . 43
14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . 43
14.3. URN Sub-Namespace Registration for provided-by Registry
Entry . . . . . . . . . . . . . . . . . . . . . . . . . 44
14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 44
14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 45
14.4.1. MIME Content-type Registration for 14.4.1. MIME Content-type Registration for
'application/emergencyCall.ProviderInfo+xml' . . . . 46 'application/emergencyCall.ProviderInfo+xml' . . . . 45
14.4.2. MIME Content-type Registration for 14.4.2. MIME Content-type Registration for
'application/emergencyCall.SvcInfo+xml' . . . . . . . 48 'application/emergencyCall.SvcInfo+xml' . . . . . . 46
14.4.3. MIME Content-type Registration for 14.4.3. MIME Content-type Registration for
'application/emergencyCall.DevInfo+xml' . . . . . . . 49 'application/emergencyCall.DevInfo+xml' . . . . . . 47
14.4.4. MIME Content-type Registration for 14.4.4. MIME Content-type Registration for
'application/emergencyCall.SubInfo+xml' . . . . . . . 50 'application/emergencyCall.SubInfo+xml' . . . . . . 49
14.4.5. MIME Content-type Registration for 14.4.5. MIME Content-type Registration for
'application/emergencyCall.Comment+xml' . . . . . . . 51 'application/emergencyCall.Comment+xml' . . . . . . 50
14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 53 14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 51
14.5.1. Registration for 14.5.1. Registration for
urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 53 urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 51
14.5.2. Registration for 14.5.2. Registration for
urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 53 urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 52
14.5.3. Registration for 14.5.3. Registration for
urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 54 urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 52
14.5.4. Registration for 14.5.4. Registration for
urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 55 urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 53
14.5.5. Registration for 14.5.5. Registration for
urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 56 urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 54
14.5.6. Registration for 14.5.6. Registration for
urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 57 urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 55
14.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 58 14.6. Schema Registrations . . . . . . . . . . . . . . . . . . 55
14.7. VCard Parameter Value Registration . . . . . . . . . . . . 59 14.7. VCard Parameter Value Registration . . . . . . . . . . . 56
15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 60 15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 61 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
16.1. Normative References . . . . . . . . . . . . . . . . . . . 61 16.1. Normative References . . . . . . . . . . . . . . . . . . 57
16.2. Informational References . . . . . . . . . . . . . . . . . 61 16.2. Informational References . . . . . . . . . . . . . . . . 57
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 63 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 58
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80
1. Introduction 1. Introduction
This document extends the basic signaling of an emergency call as When an emergency call is triggered and the Session Initiation
described in [RFC6443] and [I-D.ietf-ecrit-phonebcp] in order to Protocol (SIP) is used a rich set of data is conveyed to the Public
carry additional data which may be useful to an entity handling the Safety Answering Point (PSAP) already as part of the call setup,
call. This data is "additional" to the basic signaling used in which includes information about the calling party identity, the
processing the call. multimedia capabilities of the device, the emergency service number,
etc. The device, as well as any service provider in the path may
Three general categories of such data are defined, for the caller, have even more information that may be useful for a PSAP call taker.
the location and the call. An XML data structure is defined for such This document extends the basic signaling of an emergency call, as
data, and a means of conveying the data by including a Uniform described in [RFC6443] and [RFC6881], in order to carry additional
Resource Identifier (URI) in the SIP signaling which resolves to the data which may be useful to an entity handling the call. This data
data. The data itself may reside on an external resource, or may be is "additional" to the basic information found in the emergency call
contained within the BODY of the SIP message. signaling used.
In general, there are three types of data exchanged: Three general categories of such data are defined, namely data about
the call, the location and the caller. In more detail, the three
types of data exchanged are:
Data Associated with a Call: While information is carried in the Data Associated with a Call: While information is carried in the
call setup procedure itself (as part of the SIP headers as well as call setup procedure itself (as part of the SIP headers as well as
in the body of the SIP message), there is additional data known by in the body of the SIP message), there is additional data known by
the device making the call, or a service provider in the path of the device making the call, or a service provider in the path of
the call. This information may include the identity and contact the call. This information may include the identity and contact
information of the service provider, subscriber identity and information of the service provider, subscriber identity and
contact information, the type of service the provider offers, what contact information, the type of service the provider offers, what
kind of device is being used, etc. Some data is device or service kind of device is being used, etc. Some data is device or service
dependent data. For example, a car telematics system or service dependent data. For example, a car telematics system or service
may have crash information. A medical monitoring device may have may have crash information. A medical monitoring device may have
sensor data. While the details of the information may vary by sensor data. While the details of the information may vary by
device or service, there needs to be a common way to send such device or service, there needs to be a common way to send such
data to a PSAP. data to a PSAP.
Data Associated with a Location: There may be data that is specific Data Associated with a Location: Location data is conveyed in the
to the location not available in the location data structure Presence Informatoin Data Format Location Object (PIDF-LO) data
(PIDF-LO [RFC4119]) itself, such as floor plan, tenant and structure originally defined in RFC 4119 [RFC4119]. There may be
building owner contact data, HVAC status, etc. data that is specific to the location not available in the
location data structure itself, such as floor plans, tenant and
building owner contact data, Heating, Ventilation and Air
Conditioning (HVAC) status, etc.
Data Associated with a Caller: This is personal data about a caller, Data Associated with a Caller: This is personal data about a caller,
such as medical information and emergency contact data. such as medical information and emergency contact data.
When an emergency call is sent to a PSAP, while there is a rich set This document only defines data structures relevant to data
of data in the SIP message used for the call setup, the device, as associated with the call. Other forms of additional data may use
well as any service provider in the path may have even more this mechanism to carry data, but those blocks are not defined in
information that may be useful for a PSAP. this document.
This document focuses on additional data associated with an emergency Data structures are defined for such data, and a means of conveying
call and a mechanism for transporting it in an existing SIP header the data by including a Uniform Resource Identifier (URI) in an
field, the Call-Info header, which is specified in Section 20.9 of existing SIP header field, the Call-Info header, which is specified
[RFC3261]. For this purpose a new token, namely 'emergencyCallData' in Section 20.9 of [RFC3261]. For this purpose a new token, namely
is defined to be carried in the "purpose" parameter. If the 'emergencyCallData' is defined to be carried in the "purpose"
"purpose" parameter is set to 'emergencyCallData' then the Call-Info parameter. If the "purpose" parameter is set to 'emergencyCallData'
header contains a HTTPS URL that resolves to a data structure with then the Call-Info header contains a HTTPS URL that resolves to a
information about the call, or is a CID that allows the data data structure with information about the call, or is a CID (content
structure itself to be placed in the body of the message. Section 10 indirection) that allows the data structure to be placed in the body
shows a SIP INVITE example containing such a Call-Info header using of the message. The "purpose" parameter also contains an indication
the purpose parameter. The "purpose" parameter also contains an of what kind of data is available at the URI. As such, the
indication of what kind of data is available at the URI. additional data may reside on an external database, or may be
contained within the body of the SIP message.
Section 10 shows a SIP INVITE example containing such a Call-Info
header using the purpose parameter.
Besides a service provider in the path of a call, the access network Besides a service provider in the path of a call, the access network
(which in the IETF emergency call architecture provides location in provider (which may provide location in the form of a PIDF-LO
the form of a PIDF-LO [RFC4119]) also has similar information that [RFC4119] from a location server via a location configuration
may be valuable to the PSAP. This information is not specific to the protocol) also has similar information that may be valuable to the
location itsef, but rather provides descriptive information having to PSAP. This information is not specific to the location itsef, but
do with the immediate circumstances about the provision of the rather provides descriptive information having to do with the
location (who the access network is, how to contact that entity, what immediate circumstances about the provision of the location (who the
kind of service the access network provides, possibly subscriber access network is, how to contact that entity, what kind of service
data, etc.). This data is similar in nearly every respect with the the access network provides, subscriber information, etc.). This
data known by service providers in the path of the call. When the data is similar in nearly every respect to the data known by service
access network and service provider are separate, the access network providers in the path of the call. When the access network provider
doesn't participate in the call path (and hence cannot add a Call- and service provider are separate entities, the access network does
Info' header field), but may provide a PIDF-LO for emergency not participate in the application layer signaling (and hence cannot
purposes. The 'provided-by' element of the PIDF-LO is a mechanism add a Call-Info' header field to the SIP message), but may provide
for the access network to supply the information. For this reason, location information to assist in locating the caller's device. The
this document describes a namespace per [RFC4119] for inclusion in 'provided-by' element of the PIDF-LO is a mechanism for the access
the "provided-by" element of a PDIF-LO for adding information known network to supply the information about the entity or organization
to the access network. that supplied this location information. For this reason, this
document describes a namespace per [RFC4119] for inclusion in the
"provided-by" element of a PIDF-LO for adding information known to
the access network.
The data described in this document is represented as one or more More technically, the data structure described in this document is
"blocks" of information. Each of the blocks is a MIME type, and an represented as one or more "blocks" of information. Each of the
blocks is a Multipurpose Internet Mail Extensions (MIME) type, and an
extensible set of these types constitute the data set. A registry is extensible set of these types constitute the data set. A registry is
defined to list the block types that may be included. This document defined to list the block types that may be included.
only defines blocks relevant to data associated with the call. Other
forms of additional data may use this mechanism to carry data, but
those blocks are not defined in this document.
Devices or services may have data useful to PSAPs and emergency
responders that is specific to the type of device or service
providing the data. An example is telematics data available from
vehicles equipped with sensors and mechanisms to provide the sensor
data (for example, the VEDS data set). The mechanism described in
this document can be used to provide such data by defining a MIME
type and including a reference to the data in the Call-Info header.
PSAPS and emergency responders have to be prepared in advance to
handle such data, and may or may not choose to accept it. To control
the types of data a PSAP or responder may encounter using this
mechanism, a registry of data sets is created by this document. The
registry allows the PSAP, responder, or entity processing the call to
identify in advance the types of data it is prepared to accept, and
fetch or access only those types.
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
service provider to refer to an Application Service Provider (ASP) or
to Voice Service Provider (VSP), which is a specific type of ASP.
With the term "Access Network Provider" we refer to the Internet
Access Provider (IAP) and the Internet Service Provider (ISP) without
further distinguishing these two entities, since the difference
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
company.
In the data block definitions, the "Use:" values are specified as one In the data block definitions, the "Use:" values are specified as one
of: of:
Mandatory which means they MUST be present in the data structure. 'Mandatory': means they must be present in the data structure.
Conditional which means they MUST be present unless the specified 'Conditional': means they must be present unless the specified
condition is met, in which case the they MAY be present. condition is met, in which case the they may be present.
Optional which means they MAY be present. 'Optional': means they may be present.
3. Block Overview 3. Data Structure Overview
The following section defines an initial set of blocks which may be The following section defines an initial set of blocks which may be
sent by value or by reference in SIP signaling or within a PIDF-LO. sent by value or by reference in SIP signaling or within a PIDF-LO.
For each block, we define the MIME type, and the XML data structure For each block, we define the MIME type, and the XML data structure
for the block. Blocks are defined for: for the block. The following blocks are defined:
Data Provider which supplies name and contact information for the 'Data Provider': This block supplies name and contact information
entity that created the data. for the entity that created the data.
Service Information which supplies information about the service 'Service Information': This block supplies information about the
provided by a service provider. service provided by a service provider.
Device Information which supplies information about the device 'Device Information': This block supplies information about the
placing the call. device placing the call.
Owner/Subscriber which supplies information about the owner of the 'Owner/Subscriber': This block supplies information about the owner
device or the subscriber to the service provider. of the device or about the subscriber of the application service.
Comment which provides a way to supply free form human readable text 'Comment': This block provides a way to supply free form human
to the PSAP or emergency responders. readable text to the PSAP or emergency responders.
PSAPs and emergency responders can examine the type of data provided PSAPs and emergency responders can examine the type of data provided
and selectively retrieve the data each is interested in, while and selectively retrieve the data each they are interested in, while
forwarding all of it (the values or references) to downstream forwarding all of it (the values or references) to downstream
entities. entities.
Blocks can be sent by value (the data in the SIP body or PIDF-LO) or Blocks can be sent by value (the data in the SIP body or PIDF-LO) or
by reference (the data is retrieved via HTTPS from an external by reference (the data is retrieved via HTTPS from an external
server). Data may be provided by the device and/or one or more server). Data may be provided by the device and/or one or more
service providers. For example, the device may provide device service providers. For example, the device may provide device
specific information by value, a telematics service provider may specific information by value, a telematics service provider may
provide its contact data and data derived from the sensor data (e.g., provide its contact data and data derived from the sensor data (e.g.,
injury prediction) by reference, and a carrier may provide its injury prediction) by reference, and an access network provider may
contact data by value, all in the same SIP INVITE. provide contact information by value, all in the same SIP INVITE.
The access network MAY supply additional data as well, by including The access network provider may supply additional data as well, by
the data within a Provided-By element of a PDIF-LO object it returns including the data within a Provided-By element of a PDIF-LO it
for emergency use (e.g., if requested with a HELD "responseTime" returns for emergency use (e.g., if requested with a HELD
attribute of "emergencyRouting" or "emergencyDispatch"). Access "responseTime" attribute of "emergencyRouting" or "emergencyDispatch"
networks are expected to normally supply such information by [RFC5985]). Access network providers are expected to normally supply
reference (by including an HTTPS URI within the Provided-By element). such information by reference (by including an HTTPS URI within the
This document defines a namespace and adds the namespace to the Provided-By element). This document defines a namespace and adds the
"provided-by" registry defined by PIDF-LO [RFC4119]. namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].
4. Transmitting Blocks of Additional Data 4. Transmitting Blocks of Additional Data
One or more blocks of data registered in the Emergency Call One or more blocks of data registered in the Emergency Call
Additional Data registry as defined in Section 14.1 may be included Additional Data registry, as defined in Section 14.1, may be included
or referenced in the SIP signaling (using the Call-Info header field) or referenced in the SIP signaling (using the Call-Info header field)
or in the provided-by element of a PIDF-LO. Each block is a MIME or in the provided-by element of a PIDF-LO. Each block is a MIME
type, and any set of blocks may be included. type, and any set of blocks may be included.
Additional data about a call is defined as a series of MIME objects, Additional data about a call is defined as a series of MIME objects,
each with an XML data structure contained inside. As usual, whenever each with an XML data structure contained inside. As usual, whenever
more than one MIME part is included in the body of a message, MIME- more than one MIME part is included in the body of a message, MIME-
multipart (i.e., 'multipart/mixed') encloses them all. The sections multipart (i.e., 'multipart/mixed') encloses them all. The sections
below define the XML schema and MIME types used for each block. When below define the XML schema and MIME types used for each block. When
additional data is passed by value in the SIP signaling, each CID URL additional data is passed by value in the SIP signaling, each CID URL
points to one block in the body. Multiple URIs are used within a points to one block in the body. Multiple URIs are used within a
Call-Info header field (or multiple Call-Info header fields) to point Call-Info header field (or multiple Call-Info header fields) to point
to multiple blocks. When additional data is provided by reference to multiple blocks. When additional data is provided by reference
(in SIP signaling or Provided-By), each HTTPS URL references one (in SIP signaling or Provided-By), each HTTPS URL references one
block; the data is retrieved with an HTTP Get operation, which block; the data is retrieved with an HTTP GET operation, which
returns one of the blocks as an XML object. returns one of the blocks as an XML object.
A registry of allowed types is created by this document. Every block A registry of allowed types is created by this document. Every block
MUST be one of the types in the registry. must be one of the types in the registry.
In regions where callers can elect to suppress certain personally In regions where callers can elect to suppress certain personally
identifying information, the network or PSAP functionality can identifying information, the network or PSAP functionality can
inspect privacy flags within the SIP headers to determine what inspect privacy flags within the SIP headers to determine what
information may be passed, stored, or displayed to comply with local information may be passed, stored, or displayed to comply with local
policy or law. policy or law.
Each entity adding Additional Information MUST supply the "Data Each entity adding additional data MUST supply the "Data Provider"
Provider" block. All other blocks are optional, but each entity block. All other blocks are optional, but each entity SHOULD supply
SHOULD supply any blocks where it has at least some of the any blocks where it has at least some of the information in the
information in the block. block.
4.1. Transmitting blocks using Call-Info 4.1. Transmitting blocks using Call-Info
A URI to a block MAY be inserted in a SIP request or response method A URI to a block MAY be inserted in a SIP request or response method
(most often INVITE or MESSAGE) with a Call-Info header field (most often INVITE or MESSAGE) with a Call-Info header field
containing a purpose of "emergencyCallData" together with the type of containing a purpose of "emergencyCallData" together with the type of
data available at the URI. The type of data is denoted by including data available at the URI. The type of data is denoted by including
the root of the MIME type (not including the emergencyCall prefix and the root of the MIME type (not including the emergencyCall prefix and
the +xml suffix) with a "." separator. For example, when referencing the +xml suffix) with a "." separator. For example, when
a block with MIME type 'application/emergencyCall.ProviderInfo+xml', referencing a block with MIME type 'application/
the 'purpose' parameter is set to 'emergencyCallData.ProviderInfo'. emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
An example "Call-Info" header field for this would be: 'emergencyCallData.ProviderInfo'. An example "Call-Info" header
field for this would be:
Call-Info: https:23sedde3@example.com; Call-Info: https://www.example.com/23sedde3;
purpose="emergencyCallData.ProviderInfo" purpose="emergencyCallData.ProviderInfo"
The Call-info header with purpose='emergencyCallData' MUST only be The Call-info header with purpose='emergencyCallData' MUST only be
sent on an emergency call, which can be ascertained by the presence sent on an emergency call, which can be ascertained by the presence
of an emergency service urn in a Route header of a SIP message. of an emergency service urn in a Route header of a SIP message.
If the data is provided by reference, it may be retrieved with an If the data is provided by reference, it may be retrieved with an
HTTPS Get from the URI. The URI MUST specify an HTTPS scheme, and HTTPS GET from the URI. The URI MUST specify an HTTPS scheme, and
TLS protection for the data MUST be negotiated. consequently Transport Layer Security (TLS) protection is applied.
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 an emergencyCallData purpose can More than one Call-Info header with an emergencyCallData purpose can
be expected, but at least one MUST be provided. The device MUST be expected, but at least one MUST be provided. The device MUST
provide one if it knows no service provider is in the path of the provide one if it knows no service provider is in the path of the
call. The device MAY insert one if it uses a service provider. Any call. The device MAY insert one if it uses a service provider. Any
service provider in the path of the call MUST insert its own. For service provider in the path of the call MUST insert its own. For
skipping to change at page 11, line 49 skipping to change at page 9, line 38
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 Section 4.1, Transmitting blocks using field (as specified in section Section 4.1, Transmitting blocks using
Call-Info). Call-Info).
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 emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
'emergencyCallData.ProviderInfo'. An example 'emergencyCallData.ProviderInfo'. An example
'emergencyCallDataReference' element for this would be: 'emergencyCallDataReference' element for this would be:
<emergencyCallDataReference ref="https:23sedde3@example.com" <emergencyCallDataReference ref="https://www.example.com/23sedde3"
purpose="emergencyCallData.ProviderInfo"/> purpose="emergencyCallData.ProviderInfo"/>
4.3. Transmitting blocks by value using Provided-By 4.3. Transmitting blocks by value using Provided-By
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 Section 4.1, Transmitting blocks using Call- specified in Section 4.1, and in Section 4.1). The same XML
Info). The same XML structure as would be wrapped in the structure as would be wrapped in the corresponding MIME type is
corresponding MIME type is placed inside the emergencyCallDataValue placed inside the emergencyCallDataValue element.
element.
For example: For example:
<provided-by: xmlns="urn:ietf:params:xml:ns: <provided-by: xmlns="urn:ietf:params:xml:ns:
emergencyCallAddlData"> emergencyCallAddlData">
<emergencyCallDataValue purpose= <emergencyCallDataValue purpose=
"emergencyCallData.ProviderInfo"> "emergencyCallData.ProviderInfo">
<ProviderID>HooThrooPoo</ProviderID> <ProviderID>HooThrooPoo</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProviderID>Access Infrastructure Provider <TypeOfProviderID>Access Infrastructure Provider
</TypeOfProviderID> </TypeOfProviderID>
<ContactURI>sip:15555550987@burf.example.com:user=phone <ContactURI>sip:15555550987@burf.example.com;user=phone
</ContactURI> </ContactURI>
</emergencyCallDataValue> </emergencyCallDataValue>
</provided-by> </provided-by>
Example Provided-By by value Example Provided-By by Value.
5. Data Provider Information 5. Data Provider Information
This block is intended to be provided by any service provider in the This block is intended to be provided by any service provider in the
path of the call or the access network provider. It includes path of the call or the access network provider. It includes
identification and contact information. This block SHOULD be identification and contact information. This block SHOULD be
provided for every service provider in the path of the call, and the provided 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". emergencyCall.ProviderInfo+xml".
5.1. Data Provider String 5.1. Data Provider String
Data Element: Data Provider String Data Element: Data Provider String
Use: Required Use: Required
skipping to change at page 15, line 4 skipping to change at page 12, line 22
* EENA * EENA
Reason for Need: Identifies how to interpret the Data Provider ID. Reason for Need: Identifies how to interpret the Data Provider ID.
How Used by Call Taker: Determines which provider ID registry to How Used by Call Taker: Determines which provider ID registry to
consult for more information consult for more information
5.4. Type of Data Provider 5.4. Type of Data Provider
Data Element: Type of Data Provider ID Data Element: Type of Data Provider ID
Use: Conditional. If Data Provider ID is provided, Type of Data Use: Conditional. If Data Provider ID is provided, Type of Data
Provider ID is required. Provider ID is required.
XML Element: <TypeOfProviderID> XML Element: <TypeOfProviderID>
Description: Identifies the type of data provider id being supplied Description: Identifies the type of data provider id being supplied
in the ProviderId data element. A registry will reflect the in the ProviderId data element. A registry will reflect the
following valid entries: following valid entries:
* Access Infrastructure Provider * Access Network Provider
* Service Provider * Service Provider
* Service Provider Subcontractor * Service Provider Subcontractor
* Telematics Provider * Telematics Provider
* Relay Provider * Relay Provider
* Other * Other
skipping to change at page 16, line 21 skipping to change at page 13, line 40
5.6. Data Provider Languages(s) Supported 5.6. Data Provider Languages(s) Supported
Data Element: Data Provider Language(s) supported Data Element: Data Provider Language(s) supported
Use: Conditional Use: Conditional
XML Element: <Language> XML Element: <Language>
Description: The language used by the entity at the Data Provider Description: The language used by the entity at the Data Provider
Contact URI as an alpha 2-character code as defined in ISO 639- Contact URI as an alpha 2-character code as defined in ISO
1:2002 (http://www.iso.org/iso/catalogue_detail?csnumber=22109) 639-1:2002 Codes for the representation of names of languages --
Codes for the representation of names of languages -- Part 1: Part 1: Alpha-2 code Multiple instances of this element may occur.
Alpha-2 code Multiple instances of this element may occur. Order Order is significant; preferred language should appear first.
is significant; preferred language should appear first. This data This data is required if a Data Provider Contact URI is provided.
is required if a Data Provider Contact URI is provided. The
content must reflect the languages supported at the contact URI. The content must reflect the languages supported at the contact
URI.
Reason for Need: Information needed to determine if emergency Reason for Need: Information needed to determine if emergency
service authority can communicate with the service provider or if service authority can 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. to be added to the conversation.
5.7. xCard of Data Provider 5.7. xCard of Data Provider
skipping to change at page 19, line 7 skipping to change at page 16, line 7
Reason for Need: Inform the call taker whether the network operator Reason for Need: Inform the call taker whether the network operator
or the subcontractor should be contacted first if support is or the subcontractor should be contacted first if support is
needed. needed.
How Used by Call Taker: To decide which entity to contact first if How Used by Call Taker: To decide which entity to contact first if
assistance is needed. assistance is needed.
5.10. emergencyCall.ProviderInfo XML Schema 5.10. emergencyCall.ProviderInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo" xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.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" attributeFormDefault="unqualified"> elementFormDefault="qualified"
ttributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:simpleType name="iso3166a2"> <xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/> <xs:pattern value="[A-Z]{2}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:element name="emergencyCall.ProviderInfo"> <xs:element name="emergencyCall.ProviderInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderString" <xs:element name="DataProviderString"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ProviderID" <xs:element name="ProviderID"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ProviderIdSeries" <xs:element name="ProviderIDSeries"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="TypeOfProvider" <xs:element name="TypeOfProvider"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI" <xs:element name="ContactURI" type="xs:anyURI"
minOccurs="1" maxOccurs="1"/> minOccurs="1" maxOccurs="1"/>
<xs:element name="Language" type="ad:iso3166a2" <xs:element name="Language" type="ad:iso3166a2"
minOccurs="0" maxOccurs="unbounded" /> minOccurs="0" maxOccurs="unbounded" />
<xs:element name="DataProviderContact" <xs:element name="DataProviderContact"
type="xc:vcard" minOccurs="0" maxOccurs="1"> type="xc:vcardType" minOccurs="0"
</xs:sequence> maxOccurs="1"/>
</xs:complexType>
</xs:element>
</xs:schema>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 1: emergencyCall.ProviderInfo XML Schema Figure 1: emergencyCall.ProviderInfo XML Schema
5.11. emergencyCall.ProviderInfo Example
<?xml version="1.0" encoding="UTF-8"?>
<ad:emergencyCall.ProviderInfo
xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ad:DataProviderString>Example VoIP Provider
</ad:DataProviderString>
<ad:ProviderID>ID123</ad:ProviderID>
<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
<ad:TypeOfProvider>Service Provider</ad:TypeOfProvider>
<ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI>
<ad:Language>EN</ad:Language>
<xc:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard>
<fn><text>Hannes Tschofenig</text></fn>
<n>
<surname>Hannes</surname>
<given>Tschofenig</given>
<additional/>
<prefix/>
<suffix>Dipl. Ing.</suffix>
</n>
<bday><date>--0203</date></bday>
<anniversary>
<date-time>20090808T1430-0500</date-time>
</anniversary>
<gender><sex>M</sex></gender>
<lang>
<parameters><pref><integer>1</integer></pref>
</parameters>
<language-tag>de</language-tag>
</lang>
<lang>
<parameters><pref><integer>2</integer></pref>
</parameters>
<language-tag>en</language-tag>
</lang>
<org>
<parameters><type><text>work</text></type>
</parameters>
<text>Example VoIP Provider</text>
</org>
<adr>
<parameters>
<type><text>work</text></type>
<label><text>Hannes Tschofenig
Linnoitustie 6
Espoo , Finland
02600</text></label>
</parameters>
<pobox/>
<ext/>
<street>Linnoitustie 6</street>
<locality>Espoo</locality>
<region>Uusimaa</region>
<code>02600</code>
<country>Finland</country>
</adr>
<tel>
<parameters>
<type>
<text>work</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+358 50 4871445</uri>
</tel>
<email>
<parameters><type><text>work</text></type>
</parameters>
<text>hannes.tschofenig@nsn.com</text>
</email>
<geo>
<parameters><type><text>work</text></type>
</parameters>
<uri>geo:60.210796,24.812924</uri>
</geo>
<key>
<parameters><type><text>home</text></type>
</parameters>
<uri>
http://www.tschofenig.priv.at/key.asc
</uri>
</key>
<tz><text>Finland/Helsinki</text></tz>
<url>
<parameters><type><text>home</text></type>
</parameters>
<uri>http://www.tschofenig.priv.at</uri>
</url>
</vcard>
</xc:DataProviderContact>
</ad:emergencyCall.ProviderInfo>
Figure 2: emergencyCall.ProviderInfo Example
6. Service Information 6. Service Information
This block describes the service that the service provider provides This block describes the service that the service provider provides
to the caller. It SHOULD be included by all SPs in the path of the to the caller. It SHOULD be included by all SPs in the path of the
call. The mime subtype is "application/emergencyCall.SvcInfo+xml". call. The mime subtype is "application/emergencyCall.SvcInfo+xml".
6.1. Service Environment 6.1. Service Environment
Data Element: Service Environment Data Element: Service Environment
skipping to change at page 21, line 4 skipping to change at page 20, line 10
plan, facilities used to deliver service or service description) plan, facilities used to deliver service or service description)
to determine the information and is not responsible for to determine the information and is not responsible for
determining the actual characteristics of the location where the determining the actual characteristics of the location where the
call originates from. call originates from.
6.2. Service Delivered by Provider to End User 6.2. Service Delivered by Provider to End User
Data Element: Service Delivered by Provider to End User Data Element: Service Delivered by Provider to End User
Use: Required Use: Required
XML Element: <SvcDelByProvider> XML Element: <SvcDelByProvider>
Description: This defines the type of service the end user has Description: This defines the type of service the end user has
subscribed to. The implied mobility of this service can not be subscribed to. The implied mobility of this service can not be
relied upon. A registry defined in this document will reflect the relied upon. A registry defined in this document will reflect the
following initial valid entries: following initial valid entries:
* Wireless Telephone Service: Includes Satellite, CDMA, GSM, * Wireless Telephone Service: Includes Satellite, CDMA, GSM, Wi-
Wi-Fi, WiMAX, UTMS/WCDMA, LTE (Long Term Evolution) Fi, WiMAX, UTMS/WCDMA, LTE (Long Term Evolution)
* Fixed Public Pay/Coin telephones: Any coin or credit card * Fixed Public Pay/Coin telephones: Any coin or credit card
operated device. operated device.
* One way outbound service * One way outbound service
* Inmate call/service * Inmate call/service
* Soft dialtone/quick service/warm disconnect/suspended * Soft dialtone/quick service/warm disconnect/suspended
skipping to change at page 22, line 36 skipping to change at page 21, line 46
mobility of the caller. As the service provider may not know the mobility of the caller. As the service provider may not know the
characteristics of the actual access network used, the value not characteristics of the actual access network used, the value not
be relied upon. A registry will reflect the following initial be relied upon. A registry will reflect the following initial
valid entries: valid entries:
* Mobile: the device should be able to move at any time * Mobile: the device should be able to move at any time
* Fixed: the device is not expected to move unless the service is * Fixed: the device is not expected to move unless the service is
relocated relocated
* Nomadic: the device is not expected to move while on a call, * Nomadic: the device is not expected to change its point of
but may move between calls attachment while on a call
* Unknown: no information is known about the service mobility
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.
6.4. emergencyCall.SvcInfo XML Schema 6.4. emergencyCall.SvcInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo" xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCall.SvcInfo"> <xs:element name="emergencyCall.SvcInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="SvcEnvironment" <xs:element name="SvcEnvironment"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcDelByProvider" <xs:element name="SvcDelByProvider"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="SvcMobility" <xs:element name="SvcMobility"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="Link" <xs:element name="Link"
type="xs:string" minOccurs="0" maxOccurs="1"> type="xs:string" minOccurs="0" maxOccurs="1"/>
</xs:sequence> <xs:any namespace="##other" processContents="lax"
</xs:complexType> minOccurs="0" maxOccurs="unbounded"/>
</xs:element> </xs:sequence>
</xs:schema> </xs:complexType>
</xs:element>
</xs:schema>
Figure 2: emergencyCall.SvcInfo XML Schema Figure 3: emergencyCall.SvcInfo XML Schema
6.5. emergencyCall.SvcInfo Example
<?xml version="1.0" encoding="UTF-8"?>
<svc:emergencyCall.SvcInfo
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:SvcEnvironment>Business</svc:SvcEnvironment>
<svc:SvcDelByProvider>MLTS</svc:SvcDelByProvider>
<svc:SvcMobility>Fixed</svc:SvcMobility>
</svc:emergencyCall.SvcInfo>
Figure 4: emergencyCall.SvcInfo Example
7. Device Information 7. Device Information
This block provides information about the device used to place the This block provides information about the device used to place the
call. It should be provided by any service provider that knows what call. It should be provided by any service provider that knows what
device is being used, and by the device itself. The mime subtype is device is being used, and by the device itself. The mime subtype is
"application/emergencyCall.DevInfo+xml". "application/emergencyCall.DevInfo+xml".
7.1. Device Classification 7.1. Device Classification
skipping to change at page 30, line 5 skipping to change at page 28, line 44
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.
7.8. emergencyCall.DevInfo XML Schema 7.8. Choosing between defining a new type of block or new type of
device/service specific additional data
<?xml version="1.0"?> For devices that have device or service specific data, there are two
<xs:schema choices to carry it. A new block can be defined, or the device/
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo" service specific additional data URL the the DevInfo block can be
xmlns:xs="http://www.w3.org/2001/XMLSchema" used and a new type for it defined . The data passed would likely be
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo" the same in both cases. Considerations for choosing which mechanism
xmlns:xml="http://www.w3.org/XML/1998/namespace" to register under include:
elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" Applicability: Information which will be carried by many kinds of
schemaLocation="http://www.w3.org/2001/xml.xsd"/> devices or services are more appropriately defined as separate
blocks.
<xs:element name="emergencyCall.DevInfo"> Privacy: Information which may contain private data may be better
<xs:complexType> sent in the DevInfo block, rather than a new block so that
<xs:sequence> implementations are not tempted to send the data by value, and
<xs:element name="DeviceClassification" thus having more exposure to the data than forcing the data to be
type="xs:string" minOccurs="0" maxOccurs="1"/> retrieved via the URL in DevInfo.
<xs:element name="DeviceMfgr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceModelNr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="UniqueDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="TypeOfDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xsd:element name="DeviceSpecificData"
type="xsd:anyURI" minOccurs="0" maxOccurs="1"/>
<xsd:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 3: emergencyCallDevInfo XML Schema Size: Information which may be very may be better sent in the
DevInfo block, rather than a new block so that implementations are
not tempted to send the data by value. Conversely, data which is
small may best be sent in a separate block so that it can be sent
by value
Availability of a server: Providing the data via the device block
requires a server be made available to retrieve the data.
Providing the data via new block allows it to be sent by value
(CID).
7.9. emergencyCall.DevInfo XML Schema
<?xml version="1.0"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCall.DevInfo">
<xs:complexType>
<xs:sequence>
<xs:element name="DeviceClassification"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceMfgr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceModelNr"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="UniqueDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="TypeOfDeviceID"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceSpecificData"
type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Figure 5: emergencyCallDevInfo XML Schema
7.10. emergencyCall.DevInfo Example
<?xml version="1.0" encoding="UTF-8"?>
<svc:emergencyCall.DevInfo
xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:DeviceClassification>Fixed phone</svc:DeviceClassification>
<svc:DeviceMfgr>Nokia</svc:DeviceMfgr>
<svc:DeviceModelNr>Lumia 800</svc:DeviceModelNr>
<svc:UniqueDeviceID>35788104</svc:UniqueDeviceID>
<svc:TypeOfDeviceID>IMEI</svc:TypeOfDeviceID>
</svc:emergencyCall.DevInfo>
Figure 6: emergencyCallDevInfo Example
8. Owner/Subscriber Information 8. Owner/Subscriber Information
This block describes the owner of the device (if provided by the This block describes the owner of the device (if provided by the
device) or the subscriber information, if provided by a service device) or the subscriber information, if provided by a service
provider. The contact location is not necessarily the location of provider. The contact location is not necessarily the location of
the caller or incident, but is rather the nominal contact address. the caller or incident, but is rather the nominal contact address.
The mime subtype is "application/emergencyCall.Subscriber+xml". The mime subtype is "application/emergencyCall.Subscriber+xml".
8.1. xCard for Subscriber\\0x2019s Data 8.1. xCard for Subscriber's Data
Data Element: xCARD for Subscriber\0x2019s Data
Use: Conditional: Some services (e.g. prepaid phones, initialized Data Element: xCARD for Subscriber's Data
phones, etc.) may not have this information. Use: Conditional: Some services (e.g., prepaid phones, initialized
phones, etc.) may not have this information.
XML Element: <SubscriberData> XML Element: <SubscriberData>
Description: Information known by the service provider or device Description: Information known by the service provider or device
about the subscriber; e.g., Name, Address, Individual Telephone about the subscriber; e.g., Name, Address, Individual Telephone
Number, Main Telephone Number and any other data. N, ORG (if Number, Main Telephone Number and any other data. N, ORG (if
appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more
than one TEL property is provided, a parameter from the vCard than one TEL property is provided, a parameter from the vCard
Property Value registry MUST be specified on each TEL. Property Value registry MUST be specified on each TEL.
Reason for Need: When the caller is unable to provide information, Reason for Need: When the caller is unable to provide information,
this data may be used to obtain it this data may be used to obtain it
How Used by Call Taker: Obtaining critical information about the How Used by Call Taker: Obtaining critical information about the
caller and possibly the location when it is not able to be caller and possibly the location when it is not able to be
obtained otherwise. obtained otherwise.
8.2. emergencyCall.SubInfo XML Schema 8.2. emergencyCall.SubInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo" xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCall.SubInfo"> <xs:element name="emergencyCall.SubInfo">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="SubscriberData" <!-- VCard data structure goes in here.
type="xc:vcard" minOccurs="0" maxOccurs="1"> <xs:element name="SubscriberData"
</xs:sequence> type="xc:vcard" minOccurs="0" maxOccurs="1"/>
</xs:complexType> -->
</xs:element> <xs:any namespace="##other" processContents="lax"
</xs:schema> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
Figure 4: emergencyCall.SubInfo XML Schema </xs:complexType>
</xs:element>
</xs:schema>
Figure 7: emergencyCall.SubInfo XML Schema
8.3. emergencyCall.SubInfo Example
<?xml version="1.0" encoding="UTF-8"?>
<ad:emergencyCall.SubInfo
xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<xc:SubscriberData xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcard>
<fn><text>Simon Perreault</text></fn>
<n>
<surname>Perreault</surname>
<given>Simon</given>
<additional/>
<prefix/>
<suffix>ing. jr</suffix>
<suffix>M.Sc.</suffix>
</n>
<bday><date>--0203</date></bday>
<anniversary>
<date-time>20090808T1430-0500</date-time>
</anniversary>
<gender><sex>M</sex></gender>
<lang>
<parameters><pref><integer>1</integer></pref>
</parameters>
<language-tag>fr</language-tag>
</lang>
<lang>
<parameters><pref><integer>2</integer></pref>
</parameters>
<language-tag>en</language-tag>
</lang>
<org>
<parameters><type><text>work</text></type>
</parameters>
<text>Viagenie</text>
</org>
<adr>
<parameters>
<type><text>work</text></type>
<label><text>Simon Perreault
2875 boul. Laurier, suite D2-630
Quebec, QC, Canada
G1V 2M2</text></label>
</parameters>
<pobox/>
<ext/>
<street>2875 boul. Laurier, suite D2-630</street>
<locality>Quebec</locality>
<region>QC</region>
<code>G1V 2M2</code>
<country>Canada</country>
</adr>
<tel>
<parameters>
<type>
<text>work</text>
<text>voice</text>
</type>
</parameters>
<uri>tel:+1-418-656-9254;ext=102</uri>
</tel>
<tel>
<parameters>
<type>
<text>work</text>
<text>text</text>
<text>voice</text>
<text>cell</text>
<text>video</text>
</type>
</parameters>
<uri>tel:+1-418-262-6501</uri>
</tel>
<email>
<parameters><type><text>work</text></type>
</parameters>
<text>simon.perreault@viagenie.ca</text>
</email>
<geo>
<parameters><type><text>work</text></type>
</parameters>
<uri>geo:46.766336,-71.28955</uri>
</geo>
<key>
<parameters><type><text>work</text></type>
</parameters>
<uri>
http://www.viagenie.ca/simon.perreault/simon.asc
</uri>
</key>
<tz><text>America/Montreal</text></tz>
<url>
<parameters><type><text>home</text></type>
</parameters>
<uri>http://nomis80.org</uri>
</url>
</vcard>
</vcards>
</xc:SubscriberData>
</ad:emergencyCall.SubInfo>
Figure 8: emergencyCall.SubInfo Example
9. Comment 9. Comment
This block Provides a mechanism for the data provider to supply This block provides a mechanism for the data provider to supply
extra, human readable information to the PSAP. It is not intended extra, human readable information to the PSAP. It is not intended
for a general purpose extension mechanism. The mime subtype is for a general purpose extension mechanism. The mime subtype is
"application/emergencyCall.Comment+xml" "application/emergencyCall.Comment+xml"
9.1. Comment 9.1. Comment
Data Element: EmergencyCall.Comment Data Element: EmergencyCall.Comment
Use: Optional Use: Optional
XML Element: <Comment> XML Element: <Comment>
Description: Human readable text providing additional information to Description: Human readable text providing additional information to
the PSAP. 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
9.2. emergencyCall.Comment XML Schema 9.2. emergencyCall.Comment XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment" targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment" xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="emergencyCall.Comment"> <xs:element name="emergencyCall.Comment">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="Comment" <xs:element name="Comment"
type="xs:string" minOccurs="0" maxOccurs="1"> type="sub:CommentType" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> <xs:any namespace="##other" processContents="lax" minOccurs="0"
</xs:complexType> maxOccurs="unbounded"/>
</xs:element> </xs:sequence>
</xs:schema> </xs:complexType>
</xs:element>
Figure 5: EmergencyCall.Comment XML Schema <xs:complexType name="CommentType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
10. Example </xs:schema>
INVITE sips:bob@biloxi.example.com SIP/2.0 Figure 9: EmergencyCall.Comment XML Schema
Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70
To: Bob <sips:bob@biloxi.example.com>
From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
<http://www.example.com/alice/> ;purpose=info,
<cid:1234567890@atlanta.example.com>
;purpose=emergencyCallData.ProviderInfo
Geolocation: <cid:target123@atlanta.example.com>
Geolocation-Routing: no
Accept: application/sdp, application/pidf+xml,
application/emergencyCallProviderinfo+xml
CSeq: 31862 INVITE
Contact: <sips:alice@atlanta.example.com>
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... 9.3. emergencyCall.Comment Example
--boundary1 <?xml version="1.0" encoding="UTF-8"?>
<sub:emergencyCall.Comment
xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<sub:Comment xml:lang="en">This is an example text.</sub:Comment>
</sub:emergencyCall.Comment>
Content-Type: application/sdp Figure 10: EmergencyCall.Comment Example
...SDP goes here 10. Example
INVITE sips:bob@biloxi.example.com SIP/2.0
Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70
To: Bob <sips:bob@biloxi.example.com>
From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@atlanta.example.com
Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
<http://www.example.com/alice/> ;purpose=info,
<cid:1234567890@atlanta.example.com>
;purpose=emergencyCallData.ProviderInfo
Geolocation: <cid:target123@atlanta.example.com>
Geolocation-Routing: no
Accept: application/sdp, application/pidf+xml,
application/emergencyCallProviderinfo+xml
CSeq: 31862 INVITE
Contact: <sips:alice@atlanta.example.com>
Content-Type: multipart/mixed; boundary=boundary1
--boundary1 Content-Length: ...
Content-Type: application/pidf+xml --boundary1
Content-ID: <target123@atlanta.example.com>
\0x2026PIDF-LO goes here Content-Type: application/sdp
--boundary1-- ...SDP goes here
Content-Type: application/emergencyCall.ProviderInfo+xml --boundary1
Content-ID: <1234567890@atlanta.example.com>
\0x2026Additional Data goes here Content-Type: application/pidf+xml
Content-ID: <target123@atlanta.example.com>
--boundary1-- \0x2026PIDF-LO goes here
--boundary1--
Content-Type: application/emergencyCall.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com>
...Additional Data goes here
--boundary1--
Example: Attaching Additional Data via CID to a SIP INVITE Example: Attaching Additional Data via CID to a SIP INVITE
11. Main Telephone Number 11. Main Telephone Number
In a xCard, used extensively in this document, there is no way to In a xCard, used extensively in this document, there is no way to
specify a "Main" telephone number. These numbers are useful to specify a "Main" telephone number. These numbers are useful to
emergency responders who are called to a large enterprise. This emergency responders who are called to a large enterprise. This
document adds a new Property Value to the "tel" property of the TYPE document adds a new Property Value to the "tel" property of the TYPE
parameter called "main". It can be used in any xCard in additional parameter called "main". It can be used in any xCard in additional
skipping to change at page 40, line 5 skipping to change at page 38, line 23
There is much private data in this information. Local regulations There is much private data in this information. Local regulations
may govern what data must be provided in emergency calls, but in may govern what data must be provided in emergency calls, but in
general, the emergency call system is often aided by the kinds of general, the emergency call system is often aided by the kinds of
information described in this document. There is a tradeoff between information described in this document. There is a tradeoff between
the privacy considerations and the utility of the data. Certainly, the privacy considerations and the utility of the data. Certainly,
if the data cannot be protected, due to failure to establish (by TLS) if the data cannot be protected, due to failure to establish (by TLS)
a secure connection to the data provider, data SHOULD NOT be sent a secure connection to the data provider, data SHOULD NOT be sent
unless specifically required by regulation. unless specifically required by regulation.
Some forms of data can be sent by value in the SIP signaling or by
value (URL in SIP signaling). When data is sent by value, all
intermediaries have access to the data. If the data is private,
sending by reference is more appropriate.
14. IANA Considerations 14. IANA Considerations
14.1. Registry creation 14.1. Registry creation
This document creates a new registry called 'Emergency Call This document creates a new registry called 'Emergency Call
Additional Data'. The following subregistries are created in Additional Data'. The following subregistries are created in
Emergency Call Additional Data: Emergency Call Additional Data:
14.1.1. Additional Call Data Blocks Registry 14.1.1. Additional Call Data Provider ID Series Registry
This document creates a new subregistry called \0x2019Provider ID This document creates a new subregistry called 'Additional Call Data
Series\0x2019. As defined in [RFC5226], this registry operates under Provider ID Series'. As defined in [RFC5226], this registry operates
"Expert Review" rules. The expert should determine that the entity under "Expert Review" rules. The expert should determine that the
requesting a new value is a legitimate issuer of service provider IDs entity requesting a new value is a legitimate issuer of service
suitable for use in Additional Call Data. provider IDs suitable for use in Additional Call Data.
The content of this registry includes: The content of this registry includes:
Name: The identifier which will be used in the ProviderIDSeries Name: The identifier which will be used in the ProviderIDSeries
element element
Source: The full name of the organization issuing the identifiers Source: The full name of the organization issuing the identifiers
URL: A URL to the organization for further information URL: A URL to the organization for further information
The values defined are: The values defined are:
+-----------+-----------+--------------+--------------+ +-----------+-----------+--------------+--------------+
| Name | Source | URL | | Name | Source | URL |
+-----------+--------------------------+--------------+ +-----------+--------------------------+--------------+
| NENA | North American Emergency | www.nena.org | | NENA | North American Emergency | www.nena.org |
| | Number Association | | | | Number Association | |
| EENA | European Emergency | www.eena.org | | EENA | European Emergency | www.eena.org |
| | Number Association | | | | Number Association | |
+-----------+--------------------------+--------------+ +-----------+--------------------------+--------------+
skipping to change at page 40, line 45 skipping to change at page 39, line 19
| NENA | North American Emergency | www.nena.org | | NENA | North American Emergency | www.nena.org |
| | Number Association | | | | Number Association | |
| EENA | European Emergency | www.eena.org | | EENA | European Emergency | www.eena.org |
| | Number Association | | | | Number Association | |
+-----------+--------------------------+--------------+ +-----------+--------------------------+--------------+
RFC Editor Note: RFC Editor Note:
replace XXXX in the table above with this documents RFC number replace XXXX in the table above with this documents RFC number
14.1.2. Additional Call Data Service Provider Type Registry 14.1.2. Additional Call Data Service Provider Type Registry
This document creates a new subregistry called \0x2019Service This document creates a new subregistry called 'Service Provider
Provider Type\0x2019. As defined in [RFC5226], this registry Type'. As defined in [RFC5226], this registry operates under "Expert
operates under "Expert Review". The expert should determine that the Review". The expert should determine that the proposed new value is
proposed new value is distinct from existing values and appropriate distinct from existing values and appropriate for use in the
for use in the TypeOfServicerProvider element TypeOfServicerProvider element
The content of this registry includes: The content of this registry includes:
Name: Value to be used in TypeOfServiceProvider. Name: Value to be used in TypeOfServiceProvider.
Description: A short description of the type of service provider Description: A short description of the type of service provider
The values defined are: The values defined are:
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Name | Description | | Name | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Access Infrastructure Provider| Access network service provider | |Access Infrastructure Provider| Access network service provider |
|Service Provider | Calling or Origination telecom SP | |Service Provider | Calling or Origination telecom SP |
|Service Provider Subcontractor| A contractor to another kind of SP | |Service Provider Subcontractor| A contractor to another kind of SP |
|Telematics Provider | A sensor based SP, especially | |Telematics Provider | A sensor based SP, especially |
| | vehicle based | | | vehicle based |
|Relay Provider | A interpretation SP, for example, | |Relay Provider | A interpretation SP, for example, |
| | video relay for sign language | | | video relay for sign language |
| | interpretors | | | interpretors |
|Other | Any other type of service provider | |Other | Any other type of service provider |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
RFC Editor Note: RFC Editor Note:
replace XXXX in the table above with this documents RFC number replace XXXX in the table above with this documents RFC number
14.1.3. Additional Call Data Service Delivered Registry 14.1.3. Additional Call Data Service Delivered Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called 'Additional Call Data
Data Service Delivered\0x2019. As defined in [RFC5226], this Service Delivered'. As defined in [RFC5226], this registry operates
registry operates under "Expert Review" rules. The expert should under "Expert Review" rules. The expert should consider whether the
consider whether the proposed service is unique from existing proposed service is unique from existing services and the definition
services and the definition of the service will be clear to of the service will be clear to implementors and PSAPS/responders.
implementors and PSAPS/responders.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the service. Name: enumeration token of the service.
Description: Short description identifying the service. Description: Short description identifying the service.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | Description |
+--------+-------+--------------------------------+ +--------+----------------------------------------+
| Wrless | Wireless Telephone Service: Includes | | Wrless | Wireless Telephone Service: Includes |
| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, | | | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
| | LTE (Long Term Evolution) | | | LTE (Long Term Evolution) |
| Coin | Fixed Public Pay/Coin telephones: Any | | Coin | Fixed Public Pay/Coin telephones: Any |
| | coin or credit card operated device | | | coin or credit card operated device |
| 1way | One way outbound service | | 1way | One way outbound service |
| Prison | Inmate call/service | | Prison | Inmate call/service |
| Temp | Soft dialtone/quick service/warm | | Temp | Soft dialtone/quick service/warm |
| | disconnect/suspended | | | disconnect/suspended |
| MLTS | Multi-line telephone system: Includes | | MLTS | Multi-line telephone system: Includes |
| | all PBX, Centrex, key systems, | | | all PBX, Centrex, key systems, |
| | Shared Tenant Service | | | Shared Tenant Service |
| SenseU | Sensor, unattended: Includes devices | | SenseU | Sensor, unattended: Includes devices |
| | that generate DATA ONLY. This is | | | that generate DATA ONLY. This is |
| | one-way information exchange and | | | one-way information exchange and |
| | there will be no other form of | | | there will be no other form of |
| | communication | | | communication |
| SenseA | Sensor, attended: Includes devices | | SenseA | Sensor, attended: Includes devices |
| | that are supported by a monitoring | | | that are supported by a monitoring |
| | service provider or automatically | | | service provider or automatically |
| | open a two-way communication path | | | open a two-way communication path |
| POTS | Wireline: Plain Old Telephone Service | | POTS | Wireline: Plain Old Telephone Service |
| VOIP | VoIP Telephone Service: A type of | | VOIP | VoIP Telephone Service: A type of |
| | service that offers communication | | | service that offers communication |
| | over internet protocol, such as Fixed| | | over internet protocol, such as Fixed|
| | Nomadic, Mobile, ... | | | Nomadic, Mobile, ... |
+--------+-------+--------------------------------+ +--------+----------------------------------------+
14.1.4. Additional Call Data Device Classification Registry 14.1.4. Additional Call Data Device Classification Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called 'Additional Call Data
Data Device Classification\0x2019. As defined in [RFC5226], this Device Classification'. As defined in [RFC5226], this registry
registry operates under "Expert Review" rules. The expert should operates under "Expert Review" rules. The expert should consider
consider whether the proposed class is unique from existing classes whether the proposed class is unique from existing classes and the
and the definition of the class will be clear to implementors and definition of the class will be clear to implementors and PSAPS/
PSAPS/responders. responders.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the device classification. Name: enumeration token of the device classification.
Description: Short description identifying the device type. Description: Short description identifying the device type.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | Description |
+--------+-------+--------------------------------+ +--------+----------------------------------------+
|Cordless| Cordless handset | |Cordless| Cordless handset |
| Fixed | Fixed phone | | Fixed | Fixed phone |
| Mobile | Mobile handset | | Mobile | Mobile handset |
| ATA | analog terminal adapter | | ATA | analog terminal adapter |
|Satphone| Satellite phone | |Satphone| Satellite phone |
| FSense | Stationary computing device (alarm | | FSense | Stationary computing device (alarm |
| | system, data sensor) | | | system, data sensor) |
| Guard | Guardian devices | | Guard | Guardian devices |
| Desktop| Desktop PC | | Desktop| Desktop PC |
| Laptop | Laptop computing device | | Laptop | Laptop computing device |
| Tablet | Tablet computing device | | Tablet | Tablet computing device |
| Alarm | Alarm system | | Alarm | Alarm system |
| MSense | Mobile Data sensor | | MSense | Mobile Data sensor |
| Beacon | Personal beacons (spot) | | Beacon | Personal beacons (spot) |
| Auto | Auto telematics | | Auto | Auto telematics |
| Truck | Truck telematics | | Truck | Truck telematics |
| Farm | Farm equipment telematics | | Farm | Farm equipment telematics |
| Marine | Marine telematics | | Marine | Marine telematics |
| PDA | Personal digital assistant | | PDA | Personal digital assistant |
| PND | Personal navigation device) | | PND | Personal navigation device) |
| SmrtPhn| Smart phone | | SmrtPhn| Smart phone |
| Itab | Internet tablet | | Itab | Internet tablet |
| Game | Gaming console | | Game | Gaming console |
| Video | Video phone | | Video | Video phone |
| Text | Other text device | | Text | Other text device |
| NA | Not Available | | NA | Not Available |
+--------+----------------------------------------+ +--------+----------------------------------------+
14.1.5. Additional Call Data Device ID Type Registry 14.1.5. Additional Call Data Device ID Type Type Registry
This document creates a new registry called \0x2019Additional Call This document creates a new registry called 'Additional Call Data
Data Device ID Type\0x2019. As defined in [RFC5226], this registry Device ID Type'. As defined in [RFC5226], this registry operates
operates under "Expert Review" rules. The expert should ascertain under "Expert Review" rules. The expert should ascertain that the
that the proposed type is well understood, and provides the proposed type is well understood, and provides the information useful
information useful to PSAPs and responders to uniquely identify a to PSAPs and responders to uniquely identify a device.
device.
The content of this registry includes: The content of this registry includes:
Name: enumeration token of the device id type. Name: enumeration token of the device id type.
Description: Short description identifying the type of device id. Description: Short description identifying type of device id.
The values defined are: The values defined are:
+--------+----------------------------------------+ +--------+----------------------------------------+
| Name | description | | Name | Description |
+--------+-------+--------------------------------+ +--------+----------------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) | | MEID | Mobile Equipment Identifier (CDMA) |
| ESN | Electronic Serial Number(GSM) | | ESN | Electronic Serial Number(GSM) |
| MAC | Media Access Control Address (IEEE) | | MAC | Media Access Control Address (IEEE) |
| WiMAX | device certificate unique id | | WiMAX | device certificate unique id |
| IMEI | International Mobile Equipment ID (GSM)| | IMEI | International Mobile Equipment ID (GSM)|
| UDI | Unique Device Identifier (medical) | | UDI | Unique Device Identifier (medical) |
| RFID | Radio Frequency Identification | | RFID | Radio Frequency Identification |
| SN | Manufacturer Serial Number | | SN | Manufacturer Serial Number |
+--------+----------------------------------------+ +--------+----------------------------------------+
14.1.6. Additional Call Data Blocks Registry 14.1.6. Device/Service Specific Additional Data Type Registry
This document creates a new subregistry called \0x2019Additional Call This document creates a new registry called 'Device/Service Specific
Data Blocks\0x2019 in the purpose registry established by RFC3261. Additional Data Type Registry'. As defined in [RFC5226], this
As defined in [RFC5226], this registry operates under "Expert Review" registry operates under "Expert Review" and "Specification Required"
and "Specification Required" rules. The expert is responsible for rules. The expert should ascertain that the proposed type is well
understood, and provides information useful to PSAPs and responders.
The specification must contain a complete description of the data,
and a precise format specification suitable to allow interoperable
implementations.
The content of this registry includes:
Name: enumeration token of the data type.
Description: Short description identifying the the data.
Specification: Citation for the specification of the data.
The values defined are:
+---------+----------------------------------------+----------------+
| Name | description | specification |
+---------+-------+--------------------------------+----------------+
| IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 |
+---------+----------------------------------------+----------------+
| VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS |
+---------+----------------------------------------+----------------+
14.1.7. Additional Call Data Blocks Registry
This document creates a new subregistry called 'Additional Call Data
Blocks' in the purpose registry established by RFC 261. As defined
in [RFC5226], this registry operates under "Expert Review" and
"Specification Required" rules. The expert is responsible for
verifying that the document contains a complete and clear verifying that the document contains a complete and clear
specification of the block and the block does not obviously duplicate specification of the block and the block does not obviously duplicate
existing blocks. existing blocks.
The content of this registry includes: The content of this registry includes:
Name: Element Name of enclosing block. Name: Element Name of enclosing block.
Reference: The document that describes the block Reference: The document that describes the block
skipping to change at page 46, line 7 skipping to change at page 44, line 18
Call-Info purpose emergencyCall [This RFC] Call-Info purpose emergencyCall [This RFC]
14.3. URN Sub-Namespace Registration for provided-by Registry Entry 14.3. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in Section 14.5.1 in This section registers the namespace specified in Section 14.5.1 in
the provided-by registry established by RFC 4119, for usage within the provided-by registry established by RFC 4119, for usage within
the 'provided-by' element of a PIDF-LO. the 'provided-by' element of a PIDF-LO.
14.3.1. Provided-By XML Schema 14.3.1. Provided-By XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:emergencyCallAddlData" targetNamespace="urn:ietf:params:xml:ns:emergencyCallAddlData"
targetNamespace="urn:ietf:params:xml:ns:pidf: targetNamespace="urn:ietf:params:xml:ns:pidf:
geopriv10:emergencyCallData" geopriv10:emergencyCallData"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData" xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:simpleType name="iso3166a2"> <xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token"> <xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/> <xs:pattern value="[A-Z]{2}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:element name="emergencyCallDataReference"> <xs:element name="emergencyCallDataReference">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:attribute name="ref" <xs:attribute name="ref"
type="xs:anyURI" use="required"/> type="xs:anyURI" use="required"/>
<xs:attribute name="purpose" <xs:attribute name="purpose"
type="xs:string" use="required"/> type="xs:string" use="required"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="emergencyCallDataValue"> <xs:element name="emergencyCallDataValue">
<xs:attribute name="purpose" <xs:attribute name="purpose"
type="xs:string" use="required"/> type="xs:string" use="required"/>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Figure 6: Provided-By XML Schema Figure 11: Provided-By XML Schema
14.4. MIME Registrations 14.4. MIME Registrations
14.4.1. MIME Content-type Registration for 'application/ 14.4.1. MIME Content-type Registration for 'application/
emergencyCall.ProviderInfo+xml' emergencyCall.ProviderInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 4288 [RFC4288] and guidelines in according to the procedures of RFC 4288 [RFC4288] and guidelines in
RFC 3023 [RFC3023]. RFC 3023 [RFC3023].
skipping to change at page 53, line 21 skipping to change at page 51, line 36
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCallAddlData URI: urn:ietf:params:xml:ns:emergencyCallAddlData
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data</title> <title>Namespace for Additional Emergency Call Data</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.5.2. Registration for 14.5.2. Registration for
urn:ietf:params:xml:ns:emergencyCallProviderInfo urn:ietf:params:xml:ns:emergencyCallProviderInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
Data Provider Information</title> Data Provider Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Data Provider Information</h2> <h2>Data Provider Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo 14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
Service Information</title> Service Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2>Service Information</h2> <h2>Service Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo 14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data:
Device Information</title> <title>Namespace for Additional Emergency Call Data:
</head> Device Information</title>
<body> </head>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <body>
<h2>Device Information</h2> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<p>See [TBD: This document].</p> <h2>Device Information</h2>
</body> <p>See [TBD: This document].</p>
</html> </body>
END </html>
END
14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo 14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
Owner/Subscriber Information</title> Owner/Subscriber Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2> Owner/Subscriber Information</h2> <h2> Owner/Subscriber Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment 14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:ns:emergencyCall.Comment URI: urn:ietf:params:xml:ns:emergencyCall.Comment
Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
delegated by the IESG <iesg@ietf.org>. delegated by the IESG <iesg@ietf.org>.
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data:Comment</title> <title>Namespace for Additional Emergency Call Data:Comment</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call</h1>
<h2> Comment</h2> <h2> Comment</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
14.6. Schema Registrations 14.6. Schema Registrations
This specification registers five schemas, as per the guidelines in This specification registers five schemas, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
URI: urn:ietf:params:xml:schema:additional- URI: urn:ietf:params:xml:schema:additional-
data:emergencyCallProviderInfo data:emergencyCallProviderInfo
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
skipping to change at page 58, line 21 skipping to change at page 56, line 4
URI: urn:ietf:params:xml:schema:additional- URI: urn:ietf:params:xml:schema:additional-
data:emergencyCallProviderInfo data:emergencyCallProviderInfo
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Figure 1. XML: The XML schema can be found in Figure 1.
URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo
Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Figure 2. XML: The XML schema can be found in Figure 3.
URI: URI: urn:ietf:params:xml:schema:additional-
urn:ietf:params:xml:schema:additional-data:emergencyCallDevInfo data:emergencyCallDevInfo
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Figure 3. XML: The XML schema can be found in Figure 5.
URI: URI: urn:ietf:params:xml:schema:additional-
urn:ietf:params:xml:schema:additional-data:emergencyCall.SubInfo data:emergencyCall.SubInfo
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Section 8.2. XML: The XML schema can be found in Section 8.2.
URI: URI: urn:ietf:params:xml:schema:additional-
urn:ietf:params:xml:schema:additional-data:emergencyCall.Comment data:emergencyCall.Comment
Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
delegated by the IESG (iesg@ietf.org). delegated by the IESG (iesg@ietf.org).
XML: The XML schema can be found in Section 9.2. XML: The XML schema can be found in Section 9.2.
14.7. VCard Parameter Value Registration 14.7. VCard Parameter Value Registration
This document registers a new value in the vCARD Parameter Values This document registers a new value in the vCARD Parameter Values
registry as defined by [RFC6350] with the following template: registry as defined by [RFC6350] with the following template:
Value: main Value: main
Purpose: The main telephone number, typically of an enterprise, as Purpose: The main telephone number, typically of an enterprise, as
opposed to a direct dial number of an individual employee opposed to a direct dial number of an individual employee
Conformance: This value can be used with the "TYPE" parameter Conformance: This value can be used with the "TYPE" parameter
applied on the "TEL" property. applied on the "TEL" property.
Example(s): Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90
TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-9000 00
15. Acknowledgments 15. Acknowledgments
This work was originally started in NENA and has benefitted from a This work was originally started in NENA and has benefitted from a
large number of participants in NENA standardization efforts, large number of participants in NENA standardization efforts,
originally in the Long Term Definition Working Group, the Data originally in the Long Term Definition Working Group, the Data
Technical Committee and most recently the Additional Data working Technical Committee and most recently the Additional Data working
group. The authors are grateful for the initial work and extended group. The authors are grateful for the initial work and extended
comments provided by the many NENA participants. comments provided by the many NENA participants.
16. References 16. References
16.1. Normative References 16.1. Normative References
skipping to change at page 61, line 39 skipping to change at page 57, line 45
[RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and [RFC4288] Freed, N. and J. Klensin, "Media Type Specifications and
Registration Procedures", RFC 4288, December 2005. Registration Procedures", RFC 4288, December 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
[RFC6351] Perreault, S., "xCard: vCard XML Representation", [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC
RFC 6351, August 2011. 6351, August 2011.
16.2. Informational References 16.2. Informational References
[I-D.iab-privacy-considerations] [I-D.iab-privacy-considerations]
Cooper, A., Tschofenig, H., Aboba, B., Peterson, J., Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M., and R. Smith, "Privacy Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", Considerations for Internet Protocols", draft-iab-privacy-
draft-iab-privacy-considerations-03 (work in progress), considerations-03 (work in progress), July 2012.
July 2012.
[I-D.ietf-ecrit-phonebcp] [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
Rosen, B. and J. Polk, "Best Current Practice for Emergency Context Resolution with Internet Technologies",
Communications Services in support of Emergency Calling", RFC 5012, January 2008.
draft-ietf-ecrit-phonebcp-20 (work in progress),
September 2011.
[RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H. [RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.
Tschofenig, "LoST: A Location-to-Service Translation Tschofenig, "LoST: A Location-to-Service Translation
Protocol", RFC 5222, August 2008. Protocol", RFC 5222, August 2008.
[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC
5985, September 2010.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 2011. Multimedia", RFC 6443, December 2011.
Authors' Addresses [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013.
Appendix A. XML Schema for vCard/xCard
This section contains the vCard/xCard XML schema version of the Relax
NG schema defined in RFC 6351 [RFC6351] for simplified use with the
XML schemas defined in this document. The schema in RFC 6351
[RFC6351] is the normative source and this section is informative
only.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
targetNamespace="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:ns1="urn:ietf:params:xml:ns:vcard-4.0">
<!--
3.3
iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" }
x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" }
-->
<xs:simpleType name="iana-token">
<xs:annotation>
<xs:documentation>vCard Format Specification
</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string"/>
</xs:simpleType>
<xs:simpleType name="x-name">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!--
4.1
-->
<xs:element name="text" type="xs:string"/>
<xs:group name="value-text-list">
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="ns1:text"/>
</xs:sequence>
</xs:group>
<!-- 4.2 -->
<xs:element name="uri" type="xs:anyURI"/>
<!-- 4.3.1 -->
<xs:element name="date"
substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="\d{8}|\d{4}-\d\d|
--\d\d(\d\d)?|---\d\d"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- 4.3.2 -->
<xs:element name="time"
substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)
(Z|[+\-]\d\d(\d\d)?)?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- 4.3.3 -->
<xs:element name="date-time"
substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value=
"(\d{8}|--\d{4}|---\d\d)T
\d\d(\d\d(\d\d)?)?(Z|[+\-]\d\d(\d\d)?)?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- 4.3.4 -->
<xs:element name="value-date-and-or-time" abstract="true"/>
<!-- 4.3.5 -->
<xs:complexType name="value-timestamp">
<xs:sequence>
<xs:element ref="ns1:timestamp"/>
</xs:sequence>
</xs:complexType>
<xs:element name="timestamp">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="\d{8}T\d{6}(Z|[+\-]\d\d(\d\d)?)?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- 4.4 -->
<xs:element name="boolean" type="xs:boolean"/>
<!-- 4.5 -->
<xs:element name="integer" type="xs:integer"/>
<!-- 4.6 -->
<xs:element name="float" type="xs:float"/>
<!-- 4.7 -->
<xs:element name="utc-offset">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="[+\-]\d\d(\d\d)?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- 4.8 -->
<xs:element name="language-tag">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern
value="([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8})
(-[a-z]{4})?(-([a-z]{2}|\d{3}))?(-([0-9a-z]{5,8}|
\d[0-9a-z]{3}))*(-[0-9a-wyz](-[0-9a-z]{2,8})+)*
(-x(-[0-9a-z]{1,8})+)?|x(-[0-9a-z]{1,8})+|[a-z]{1,3}
(-[0-9a-z]{2,8}){1,2}"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<!--
5.1
-->
<xs:group name="param-language">
<xs:annotation>
<xs:documentation>Section 5: Parameters</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:language"/>
</xs:sequence>
</xs:group>
<xs:element name="language">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:language-tag"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.2 -->
<xs:group name="param-pref">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:pref"/>
</xs:sequence>
</xs:group>
<xs:element name="pref">
<xs:complexType>
<xs:sequence>
<xs:element name="integer">
<xs:simpleType>
<xs:restriction base="xs:integer">
<xs:minInclusive value="1"/>
<xs:maxInclusive value="100"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.4 -->
<xs:group name="param-altid">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:altid"/>
</xs:sequence>
</xs:group>
<xs:element name="altid">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.5 -->
<xs:group name="param-pid">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:pid"/>
</xs:sequence>
</xs:group>
<xs:element name="pid">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="text">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="\d+(\.\d+)?"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.6 -->
<xs:group name="param-type">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:type"/>
</xs:sequence>
</xs:group>
<xs:element name="type">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="text">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="work"/>
<xs:enumeration value="home"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.7 -->
<xs:group name="param-mediatype">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:mediatype"/>
</xs:sequence>
</xs:group>
<xs:element name="mediatype">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.8 -->
<xs:group name="param-calscale">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:calscale"/>
</xs:sequence>
</xs:group>
<xs:element name="calscale">
<xs:complexType>
<xs:sequence>
<xs:element name="text">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="gregorian"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.9 -->
<xs:group name="param-sort-as">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:sort-as"/>
</xs:sequence>
</xs:group>
<xs:element name="sort-as">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 5.10 -->
<xs:group name="param-geo">
<xs:sequence>
<xs:element minOccurs="0" name="geo">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
<!-- 5.11 -->
<xs:group name="param-tz">
<xs:sequence>
<xs:element minOccurs="0" name="tz">
<xs:complexType>
<xs:choice>
<xs:element ref="ns1:text"/>
<xs:element ref="ns1:uri"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
<!--
6.1.3
-->
<xs:element name="source">
<xs:complexType>
<xs:sequence>
<xs:element name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.1.4 -->
<xs:element name="kind">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded" name="text">
<xs:simpleType>
<xs:union memberTypes="ns1:x-name ns1:iana-token">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="individual"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="group"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="org"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="location"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.1 -->
<xs:element name="fn">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.2 -->
<xs:element name="n">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-sort-as"/>
<xs:group ref="ns1:param-altid"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element maxOccurs="unbounded" ref="ns1:surname"/>
<xs:element maxOccurs="unbounded" ref="ns1:given"/>
<xs:element maxOccurs="unbounded" ref="ns1:additional"/>
<xs:element maxOccurs="unbounded" ref="ns1:prefix"/>
<xs:element maxOccurs="unbounded" ref="ns1:suffix"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="surname" type="xs:string"/>
<xs:element name="given" type="xs:string"/>
<xs:element name="additional" type="xs:string"/>
<xs:element name="prefix" type="xs:string"/>
<xs:element name="suffix" type="xs:string"/>
<!-- 6.2.3 -->
<xs:element name="nickname">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:group ref="ns1:value-text-list"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.4 -->
<xs:element name="photo">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.5 -->
<xs:element name="bday">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-calscale"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:value-date-and-or-time"/>
<xs:element ref="ns1:text"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.6 -->
<xs:element name="anniversary">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-calscale"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:value-date-and-or-time"/>
<xs:element ref="ns1:text"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.2.7 -->
<xs:element name="gender">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:sex"/>
<xs:element minOccurs="0" ref="ns1:identity"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sex">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value=""/>
<xs:enumeration value="M"/>
<xs:enumeration value="F"/>
<xs:enumeration value="O"/>
<xs:enumeration value="N"/>
<xs:enumeration value="U"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
<xs:element name="identity" type="xs:string"/>
<!-- 6.3.1 -->
<xs:group name="param-label">
<xs:sequence>
<xs:element minOccurs="0" ref="ns1:label"/>
</xs:sequence>
</xs:group>
<xs:element name="label">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="adr">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-geo"/>
<xs:group ref="ns1:param-tz"/>
<xs:group ref="ns1:param-label"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element maxOccurs="unbounded" ref="ns1:pobox"/>
<xs:element maxOccurs="unbounded" ref="ns1:ext"/>
<xs:element maxOccurs="unbounded" ref="ns1:street"/>
<xs:element maxOccurs="unbounded" ref="ns1:locality"/>
<xs:element maxOccurs="unbounded" ref="ns1:region"/>
<xs:element maxOccurs="unbounded" ref="ns1:code"/>
<xs:element maxOccurs="unbounded" ref="ns1:country"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="pobox" type="xs:string"/>
<xs:element name="ext" type="xs:string"/>
<xs:element name="street" type="xs:string"/>
<xs:element name="locality" type="xs:string"/>
<xs:element name="region" type="xs:string"/>
<xs:element name="code" type="xs:string"/>
<xs:element name="country" type="xs:string"/>
<!-- 6.4.1 -->
<xs:element name="tel">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:element minOccurs="0" name="type">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="text">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="work"/>
<xs:enumeration value="home"/>
<xs:enumeration value="text"/>
<xs:enumeration value="voice"/>
<xs:enumeration value="fax"/>
<xs:enumeration value="cell"/>
<xs:enumeration value="video"/>
<xs:enumeration value="pager"/>
<xs:enumeration value="textphone"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:text"/>
<xs:element ref="ns1:uri"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.4.2 -->
<xs:element name="email">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.4.3 -->
<xs:element name="impp">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.4.4 -->
<xs:element name="lang">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:language-tag"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.5.1 -->
<xs:group name="property-tz">
<xs:sequence>
<xs:element name="tz">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:text"/>
<xs:element ref="ns1:uri"/>
<xs:element ref="ns1:utc-offset"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
<!-- 6.5.2 -->
<xs:group name="property-geo">
<xs:sequence>
<xs:element name="geo">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:group>
<!-- 6.6.1 -->
<xs:element name="title">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.6.2 -->
<xs:element name="role">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.6.3 -->
<xs:element name="logo">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.6.4 -->
<xs:element name="org">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-sort-as"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:group ref="ns1:value-text-list"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.6.5 -->
<xs:element name="member">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.6.6 -->
<xs:element name="related">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:element minOccurs="0" name="type">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="text">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="work"/>
<xs:enumeration value="home"/>
<xs:enumeration value="contact"/>
<xs:enumeration value="acquaintance"/>
<xs:enumeration value="friend"/>
<xs:enumeration value="met"/>
<xs:enumeration value="co-worker"/>
<xs:enumeration value="colleague"/>
<xs:enumeration value="co-resident"/>
<xs:enumeration value="neighbor"/>
<xs:enumeration value="child"/>
<xs:enumeration value="parent"/>
<xs:enumeration value="sibling"/>
<xs:enumeration value="spouse"/>
<xs:enumeration value="kin"/>
<xs:enumeration value="muse"/>
<xs:enumeration value="crush"/>
<xs:enumeration value="date"/>
<xs:enumeration value="sweetheart"/>
<xs:enumeration value="me"/>
<xs:enumeration value="agent"/>
<xs:enumeration value="emergency"/>
</xs:restriction>
</xs:simpleType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:uri"/>
<xs:element ref="ns1:text"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.1 -->
<xs:element name="categories">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:group ref="ns1:value-text-list"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.2 -->
<xs:element name="note">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.3 -->
<xs:element name="prodid">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:text"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.4 -->
<xs:element name="rev" type="ns1:value-timestamp"/>
<!-- 6.7.5 -->
<xs:element name="sound">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-language"/>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.6 -->
<xs:element name="uid">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.7.7 -->
<xs:element name="clientpidmap">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns1:sourceid"/>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sourceid" type="xs:positiveInteger"/>
<!-- 6.7.8 -->
<xs:element name="url">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.8.1 -->
<xs:element name="key">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:choice>
<xs:element ref="ns1:uri"/>
<xs:element ref="ns1:text"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.9.1 -->
<xs:element name="fburl">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.9.2 -->
<xs:element name="caladruri">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- 6.9.3 -->
<xs:element name="caluri">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="parameters">
<xs:complexType>
<xs:sequence>
<xs:group ref="ns1:param-altid"/>
<xs:group ref="ns1:param-pid"/>
<xs:group ref="ns1:param-pref"/>
<xs:group ref="ns1:param-type"/>
<xs:group ref="ns1:param-mediatype"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element ref="ns1:uri"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- Top-level grammar -->
<xs:group name="property">
<xs:choice>
<xs:element ref="ns1:adr"/>
<xs:element ref="ns1:anniversary"/>
<xs:element ref="ns1:bday"/>
<xs:element ref="ns1:caladruri"/>
<xs:element ref="ns1:caluri"/>
<xs:element ref="ns1:categories"/>
<xs:element ref="ns1:clientpidmap"/>
<xs:element ref="ns1:email"/>
<xs:element ref="ns1:fburl"/>
<xs:element ref="ns1:fn"/>
<xs:group ref="ns1:property-geo"/>
<xs:element ref="ns1:impp"/>
<xs:element ref="ns1:key"/>
<xs:element ref="ns1:kind"/>
<xs:element ref="ns1:lang"/>
<xs:element ref="ns1:logo"/>
<xs:element ref="ns1:member"/>
<xs:element ref="ns1:n"/>
<xs:element ref="ns1:nickname"/>
<xs:element ref="ns1:note"/>
<xs:element ref="ns1:org"/>
<xs:element ref="ns1:photo"/>
<xs:element ref="ns1:prodid"/>
<xs:element ref="ns1:related"/>
<xs:element ref="ns1:rev"/>
<xs:element ref="ns1:role"/>
<xs:element ref="ns1:gender"/>
<xs:element ref="ns1:sound"/>
<xs:element ref="ns1:source"/>
<xs:element ref="ns1:tel"/>
<xs:element ref="ns1:title"/>
<xs:group ref="ns1:property-tz"/>
<xs:element ref="ns1:uid"/>
<xs:element ref="ns1:url"/>
</xs:choice>
</xs:group>
<xs:element name="vcards">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="ns1:vcard"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="vcardType">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:choice maxOccurs="unbounded">
<xs:group ref="ns1:property"/>
<xs:element ref="ns1:group"/>
</xs:choice>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="vcard" type="ns1:vcardType"/>
<xs:element name="group">
<xs:complexType>
<xs:group minOccurs="0" maxOccurs="unbounded"
ref="ns1:property"/>
<xs:attribute name="name" use="required"/>
</xs:complexType>
</xs:element>
</xs:schema>
Authors' Addresses
Brian Rosen Brian Rosen
NeuStar NeuStar
470 Conrad Dr. 470 Conrad Dr.
Mars, PA 16046 Mars, PA 16046
US US
Phone: +1 724 382 1051 Phone: +1 724 382 1051
Email: br@brianrosen.net Email: br@brianrosen.net
Hannes Tschofenig Hannes Tschofenig
 End of changes. 143 change blocks. 
677 lines changed or deleted 2110 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/