draft-ietf-ecrit-additional-data-23.txt   draft-ietf-ecrit-additional-data-24.txt 
ECRIT B. Rosen ECRIT R. Gellens
Internet-Draft NeuStar Internet-Draft Qualcomm Technologies, Inc.
Intended status: Standards Track H. Tschofenig Intended status: Standards Track B. Rosen
Expires: April 5, 2015 (no affiliation) Expires: April 16, 2015 NeuStar
H. Tschofenig
(no affiliation)
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
R. Gellens
Qualcomm Technologies, Inc.
J. Winterbottom J. Winterbottom
(no affiliation) (no affiliation)
October 02, 2014 October 13, 2014
Additional Data related to an Emergency Call Additional Data related to an Emergency Call
draft-ietf-ecrit-additional-data-23.txt draft-ietf-ecrit-additional-data-24.txt
Abstract Abstract
When an emergency call is sent to a Public Safety Answering Point When an emergency call is sent to a Public Safety Answering Point
(PSAP), the device that sends it, as well as any application service (PSAP), the device that sends it, as well as any application service
provider in the path of the call, or access network provider through provider in the path of the call, or access network provider through
which the call originated may have information about the call, the which the call originated may have information about the call, the
caller or the location which the PSAP may be able to use. This caller or the location which the PSAP may be able to use. This
document describes data structures and a mechanism to convey such document describes data structures and a mechanism to convey such
data to the PSAP. The mechanism uses a Uniform Resource Identifier data to the PSAP. The mechanism uses a Uniform Resource Identifier
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 5, 2015. This Internet-Draft will expire on April 16, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 38 skipping to change at page 2, line 38
4.1.1. Data Provider String . . . . . . . . . . . . . . . . 8 4.1.1. Data Provider String . . . . . . . . . . . . . . . . 8
4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9 4.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 9
4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9 4.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9
4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 10 4.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 10
4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 11 4.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 11
4.1.6. Data Provider Languages(s) Supported . . . . . . . . 11 4.1.6. Data Provider Languages(s) Supported . . . . . . . . 11
4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 12 4.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 12
4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12 4.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12
4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13 4.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 13
4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13 4.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 13
4.2. Service Information . . . . . . . . . . . . . . . . . . . 16 4.2. Service Information . . . . . . . . . . . . . . . . . . . 15
4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16 4.2.1. Service Environment . . . . . . . . . . . . . . . . . 16
4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16 4.2.2. Service Type . . . . . . . . . . . . . . . . . . . . 16
4.2.3. Service Mobility Environment . . . . . . . . . . . . 19 4.2.3. Service Mobility Environment . . . . . . . . . . . . 18
4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 19 4.2.4. EmergencyCallData.ServiceInfo Example . . . . . . . . 18
4.3. Device Information . . . . . . . . . . . . . . . . . . . 20 4.3. Device Information . . . . . . . . . . . . . . . . . . . 19
4.3.1. Device Classification . . . . . . . . . . . . . . . . 20 4.3.1. Device Classification . . . . . . . . . . . . . . . . 19
4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 21 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 21
4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 22 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 21
4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 22 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 21
4.3.5. Device/Service Specific Additional Data Structure . . 23 4.3.5. Device/Service Specific Additional Data Structure . . 22
4.3.6. Device/Service Specific Additional Data Structure 4.3.6. Device/Service Specific Additional Data Structure
Type . . . . . . . . . . . . . . . . . . . . . . . . 23 Type . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3.7. Issues with getting new types of data into use . . . 24 4.3.7. Issues with getting new types of data into use . . . 23
4.3.8. Choosing between defining a new type of block or new 4.3.8. Choosing between defining a new type of block or new
type of device/service specific additional data . . . 25 type of device/service specific additional data . . . 24
4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 25 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 25
4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 25
4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 25
4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 26
4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 26
4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 29 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 29
5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 29
5.1. Transmitting Blocks using the Call-Info Header . . . . . 32 5.1. Transmitting Blocks using the Call-Info Header . . . . . 31
5.2. Transmitting Blocks by Reference using the Provided-By 5.2. Transmitting Blocks by Reference using the Provided-By
Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 Element . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.3. Transmitting Blocks by Value using the Provided-By 5.3. Transmitting Blocks by Value using the Provided-By
Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4. The Content-Disposition Parameter . . . . . . . . . . . . 34 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 34
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 47 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 47 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 47
7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 49 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 49
7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 49 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 50
7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 51 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 51
7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 51 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 52
7.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 52 7.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 53
8. Security Considerations . . . . . . . . . . . . . . . . . . . 54 8. Security Considerations . . . . . . . . . . . . . . . . . . . 56
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 56 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 57
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 60
10.1. Registry creation . . . . . . . . . . . . . . . . . . . 59 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 60
10.1.1. Provider ID Series Registry . . . . . . . . . . . . 59 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 60
10.1.2. Service Environment Registry . . . . . . . . . . . . 60 10.1.2. Service Environment Registry . . . . . . . . . . . . 61
10.1.3. Service Type Registry . . . . . . . . . . . . . . . 60 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 61
10.1.4. Service Mobility Registry . . . . . . . . . . . . . 61 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 62
10.1.5. Service Provider Type Registry . . . . . . . . . . . 61 10.1.5. Service Provider Type Registry . . . . . . . . . . . 62
10.1.6. Service Delivered Registry . . . . . . . . . . . . . 62 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 63
10.1.7. Device Classification Registry . . . . . . . . . . . 62 10.1.7. Device Classification Registry . . . . . . . . . . . 63
10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 63 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 63
10.1.9. Device/Service Data Type Registry . . . . . . . . . 63 10.1.9. Device/Service Data Type Registry . . . . . . . . . 64
10.1.10. Emergency Call Data Types Registry . . . . . . . . . 63 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 64
10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 64 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 65
10.3. URN Sub-Namespace Registration for provided-by Registry 10.3. URN Sub-Namespace Registration for provided-by Registry
Entry . . . . . . . . . . . . . . . . . . . . . . . . . 65 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 65 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 66
10.4.1. MIME Content-type Registration for 10.4.1. MIME Content-type Registration for
'application/EmergencyCallData.ProviderInfo+xml' . . 65 'application/EmergencyCallData.ProviderInfo+xml' . . 66
10.4.2. MIME Content-type Registration for 10.4.2. MIME Content-type Registration for
'application/EmergencyCallData.ServiceInfo+xml' . . 66 'application/EmergencyCallData.ServiceInfo+xml' . . 67
10.4.3. MIME Content-type Registration for 10.4.3. MIME Content-type Registration for
'application/EmergencyCallData.DeviceInfo+xml' . . . 67 'application/EmergencyCallData.DeviceInfo+xml' . . . 68
10.4.4. MIME Content-type Registration for 10.4.4. MIME Content-type Registration for
'application/EmergencyCallData.SubscriberInfo+xml' . 68 'application/EmergencyCallData.SubscriberInfo+xml' . 69
10.4.5. MIME Content-type Registration for 10.4.5. MIME Content-type Registration for
'application/EmergencyCallData.Comment+xml' . . . . 69 'application/EmergencyCallData.Comment+xml' . . . . 70
10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 71 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 71
10.5.1. Registration for 10.5.1. Registration for
urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 71 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 71
10.5.2. Registration for 10.5.2. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf urn:ietf:params:xml:ns:EmergencyCallData:ProviderInf
o . . . . . . . . . . . . . . . . . . . . . . . . . 71 o . . . . . . . . . . . . . . . . . . . . . . . . . 72
10.5.3. Registration for 10.5.3. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 72 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 73
10.5.4. Registration for 10.5.4. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 73 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 74
10.5.5. Registration for 10.5.5. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI urn:ietf:params:xml:ns:EmergencyCallData:SubscriberI
nfo . . . . . . . . . . . . . . . . . . . . . . . . 73 nfo . . . . . . . . . . . . . . . . . . . . . . . . 75
10.5.6. Registration for 10.5.6. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 74 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 76
10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 75 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 77
10.7. VCard Parameter Value Registration . . . . . . . . . . . 76 10.7. VCard Parameter Value Registration . . . . . . . . . . . 78
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 76 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 78
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 76 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.1. Normative References . . . . . . . . . . . . . . . . . . 76 12.1. Normative References . . . . . . . . . . . . . . . . . . 79
12.2. Informational References . . . . . . . . . . . . . . . . 77 12.2. Informational References . . . . . . . . . . . . . . . . 80
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 79 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 101 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 81
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 104
1. Introduction 1. Introduction
When an IP-based emergency call is initiated, a rich set of data from When an IP-based emergency call is initiated, a rich set of data from
multiple data sources is conveyed to the Public Safety Answering multiple data sources is conveyed to the Public Safety Answering
Point (PSAP). This data includes information about the calling party Point (PSAP). This data includes information about the calling party
identity, the multimedia capabilities of the device, the request for identity, the multimedia capabilities of the device, the request for
emergency services, location information, and meta-data about the emergency services, location information, and meta-data about the
sources of the data. The device, the access network provider, and sources of the data. The device, the access network provider, and
any service provider in the call path may have even more information any service provider in the call path may have even more information
skipping to change at page 10, line 24 skipping to change at page 10, line 24
4.1.4. Type of Data Provider 4.1.4. Type of Data Provider
Data Element: Type of Data Provider Data Element: Type of Data Provider
Use: Required. Use: Required.
XML Element: <TypeOfProvider> XML Element: <TypeOfProvider>
Description: Identifies the type of data provider supplying the Description: Identifies the type of data provider supplying the
data. A registry with an initial set of values is shown in Figure data. A registry with an initial set of values is shown in
1 (see also Section 10.1). Figure 1 (see also Section 10.1).
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
| Token | Description | | Token | Description |
+------------------------------+------------------------------------+ +------------------------------+------------------------------------+
|Access Network Provider | Access network service provider | |Access Network Provider | Access network service provider |
|Telecom Provider | Calling or origination telecom SP | |Telecom Provider | Calling or origination telecom SP |
|Telematics Provider | A sensor based service provider, | |Telematics Provider | A sensor based service provider, |
| | especially vehicle based | | | especially vehicle based |
|Language Translation Provider | A spoken language translation SP | |Language Translation Provider | A spoken language translation SP |
|Emergency Service Provider | An emergency service provider | |Emergency Service Provider | An emergency service provider |
skipping to change at page 12, line 7 skipping to change at page 12, line 4
Description: The language used by the entity at the Data Provider Description: The language used by the entity at the Data Provider
Contact URI, as an alpha 2-character code as defined in ISO Contact URI, as an alpha 2-character code as defined in ISO
639-1:2002 Codes for the representation of names of languages -- 639-1:2002 Codes for the representation of names of languages --
Part 1: Alpha-2 code Multiple instances of this element may occur. Part 1: Alpha-2 code Multiple instances of this element may occur.
Order is significant; preferred language should appear first. The Order is significant; preferred language should appear first. The
content MUST reflect the languages supported at the contact URI. content MUST reflect the languages supported at the contact URI.
Note that the 'language' media feature tag, defined in RFC 3840 Note that the 'language' media feature tag, defined in RFC 3840
[RFC3840] and the more extensive language negotiation mechanism [RFC3840] and the more extensive language negotiation mechanism
proposed with [I-D.gellens-mmusic-negotiating-human-language] are proposed with [I-D.gellens-slim-negotiating-human-language] are
independent of this data provider language indication. independent of this data provider language indication.
Reason for Need: This information indicates if the emergency service Reason for Need: This information indicates if the emergency service
authority can directly communicate with the service provider or if authority can directly communicate with the service provider or if
an interpreter will be needed. an interpreter will be needed.
How Used by Call Taker: If the call taker cannot speak any language How Used by Call Taker: If the call taker cannot speak any language
supported by the service provider, a translation service will need supported by the service provider, a translation service will need
to be added to the conversation. Alternatively, other persons at to be added to the conversation. Alternatively, other persons at
the PSAP, besides the call taker, might be consulted for help the PSAP, besides the call taker, might be consulted for help
skipping to change at page 17, line 4 skipping to change at page 16, line 47
facilities used to deliver service or service description) to facilities used to deliver service or service description) to
determine the information and is not responsible for determining determine the information and is not responsible for determining
the actual characteristics of the location from which the call the actual characteristics of the location from which the call
originated. Because the usefulness is unknown (and less clear) originated. Because the usefulness is unknown (and less clear)
for wireless, this element is OPTIONAL for wireless and REQUIRED for wireless, this element is OPTIONAL for wireless and REQUIRED
otherwise. otherwise.
4.2.2. Service Type 4.2.2. Service Type
Data Element: Service Delivered by Provider to End User Data Element: Service Delivered by Provider to End User
Use: Required Use: Required
XML Element: <ServiceType> XML Element: <ServiceType>
Description: This defines the type of service over which the call is Description: This defines the type of service over which the call is
placed. The implied mobility of this service cannot be relied placed. The implied mobility of this service cannot be relied
upon. A registry with an initial set of values is defined in upon. A registry with an initial set of values is defined in
Figure 3. Figure 3.
+--------------+----------------------------------------+ +--------------+----------------------------------------+
| Name | Description | | Name | Description |
+--------------+----------------------------------------+ +--------------+----------------------------------------+
| wireless | Wireless Telephone Service: Includes | | wireless | Wireless Telephone Service: Includes |
| | CDMA, GSM, Wi-Fi, WiMAX, LTE (but | | | CDMA, GSM, Wi-Fi, WiMAX, LTE (but |
| | not satellite) | | | not satellite) |
| coin | Fixed public pay/coin telephones: Any | | coin | Fixed public pay/coin telephones: Any |
| | coin or credit card operated device | | | coin or credit card operated device |
| one-way | One way outbound service | | one-way | One way outbound service |
| prison | Inmate call/service | | prison | Inmate call/service |
| temp | Soft dial tone/quick service/warm | | temp | Soft dial tone/quick service/warm |
| | disconnect/suspended | | | disconnect/suspended |
| MLTS-hosted | Hosted multi-line telephone system | | MLTS-hosted | Hosted multi-line telephone system |
| | such as Centrex | | | such as Centrex |
| MLTS-local | Local multi-line telephone system, | | MLTS-local | Local multi-line telephone system, |
| | includes all PBX, key systems, | | | includes all PBX, key systems, |
| | Shared Tenant Service | | | Shared Tenant Service |
| sensor- | | sensor- |
| unattended | These are devices that generate DATA | | unattended | These are devices that generate DATA |
| | ONLY. This is a one-way information | | | ONLY. This is a one-way information |
| | transmit without interactive media | | | transmit without interactive media |
| sensor- | | | sensor- | |
| attended | Devices that are supported by a | | attended | Devices that are supported by a |
| | monitoring service provider or that | | | monitoring service provider or that |
| | are capable of supporting interactive| | | are capable of supporting interactive|
| | media | | | media |
| POTS | Wireline: Plain Old Telephone Service | | POTS | Wireline: Plain Old Telephone Service |
| VOIP | An over-the-top service that provides | | VOIP | An over-the-top service that provides |
| | communication over arbitrary Internet| | | communication over arbitrary Internet|
| | access (fixed, nomadic, mobile) | | | access (fixed, nomadic, mobile) |
| remote | Off premise extension | | remote | Off premise extension |
| relay | A service where there is a human third | | relay | A service where there is a human third |
| | party agent who provides additional | | | party agent who provides additional |
| | assistance. This includes sign | | | assistance. This includes sign |
| | language relay and telematics | | | language relay and telematics |
| | services that provide a human on the | | | services that provide a human on the |
| | call. | | | call. |
+--------------+----------------------------------------+ +--------------+----------------------------------------+
Figure 3: Service Delivered by Provider to End User Registry. Figure 3: Service Delivered by Provider to End User Registry.
More than one value MAY be returned. For example, a VoIP inmate More than one value MAY be returned. For example, a VoIP inmate
telephone service is a reasonable combination. telephone service is a reasonable combination.
Reason for Need: Knowing the type of service may assist the PSAP Reason for Need: Knowing the type of service may assist the PSAP
with the handling of the call. with the handling of the call.
How Used by Call Taker: Call takers often use this information to How Used by Call Taker: Call takers often use this information to
skipping to change at page 20, line 41 skipping to change at page 20, line 5
provides the structure and it knows what the device is, the provides the structure and it knows what the device is, the
service provider SHOULD provide the device information. Often the service provider SHOULD provide the device information. Often the
carrier does not know what the device is. It is possible to carrier does not know what the device is. It is possible to
receive two Additional Data Associated with a Call data receive two Additional Data Associated with a Call data
structures, one created by the device and one created by the structures, one created by the device and one created by the
service provider. This information describes the device, not how service provider. This information describes the device, not how
it is being used. This data element defines the kind of device it is being used. This data element defines the kind of device
making the emergency call. The registry with the initial set of making the emergency call. The registry with the initial set of
values is shown in Figure 5. values is shown in Figure 5.
+---------------+----------------------------------------+ +---------------+----------------------------------------+
| Token | Description | | Token | Description |
+---------------+----------------------------------------+ +---------------+----------------------------------------+
|cordless | Cordless handset | |cordless | Cordless handset |
|fixed | Fixed phone | |fixed | Fixed phone |
|satellite | Satellite phone | |satellite | Satellite phone |
|sensor-fixed | Fixed (non mobile) sensor/alarm device | |sensor-fixed | Fixed (non mobile) sensor/alarm device |
|desktop | Soft client on desktop PC | |desktop | Soft client on desktop PC |
|laptop | Soft client on laptop type device | |laptop | Soft client on laptop type device |
|tablet | Soft client on tablet type device | |tablet | Soft client on tablet type device |
|alarm-monitored| Alarm system | |alarm-monitored| Alarm system |
|sensor-mobile | Mobile sensor device | |sensor-mobile | Mobile sensor device |
|aircraft | Aircraft telematics device | |aircraft | Aircraft telematics device |
|automobile | Automobile/cycle/off-road telematics | |automobile | Automobile/cycle/off-road telematics |
|truck | Truck/construction telematics | |truck | Truck/construction telematics |
|farm | Farm equipment telematics | |farm | Farm equipment telematics |
|marine | Marine telematics | |marine | Marine telematics |
|personal | Personal telematics device | |personal | Personal telematics device |
|feature-phone | Feature- (not smart-) cellular phone | |feature-phone | Feature- (not smart-) cellular phone |
|smart-phone | Smart-phone cellular phone (native) | |smart-phone | Smart-phone cellular phone (native) |
|smart-phone-app| Soft client app on smart-phone | |smart-phone-app| Soft client app on smart-phone |
|unknown-device | Soft client on unknown device type | |unknown-device | Soft client on unknown device type |
|game | Gaming console | |game | Gaming console |
|text-only | Other text device | |text-only | Other text device |
|NA | Not Available | |NA | Not Available |
+---------------+----------------------------------------+ +---------------+----------------------------------------+
Figure 5: Device Classification Registry. Figure 5: Device Classification Registry.
Reason for Need: The device classification implies the capability of Reason for Need: The device classification implies the capability of
the calling device and assists in identifying the meaning of the the calling device and assists in identifying the meaning of the
emergency call location information that is being presented. For emergency call location information that is being presented. For
example, does the device require human intervention to initiate a example, does the device require human intervention to initiate a
call or is this call the result of programmed instructions? Does call or is this call the result of programmed instructions? Does
the calling device have the ability to update location or the calling device have the ability to update location or
condition changes? Is this device interactive or a one-way condition changes? Is this device interactive or a one-way
skipping to change at page 22, line 43 skipping to change at page 22, line 9
Description: A string that identifies the specific device (or the Description: A string that identifies the specific device (or the
device's current SIM) making the call or creating an event. Note device's current SIM) making the call or creating an event. Note
that more than one <UniqueDeviceID> may be present, to supply more that more than one <UniqueDeviceID> may be present, to supply more
than one of the identifying values. than one of the identifying values.
The <TypeOfDeviceID> attribute identifies the type of device The <TypeOfDeviceID> attribute identifies the type of device
identifier. A registry with an initial set of values can be seen identifier. A registry with an initial set of values can be seen
in Figure 6. in Figure 6.
+--------+------------------------------------------+ +--------+------------------------------------------+
| Token | Description | | Token | Description |
+--------+------------------------------------------+ +--------+------------------------------------------+
| MEID | Mobile Equipment Identifier (CDMA) | | MEID | Mobile Equipment Identifier (CDMA) |
| ESN | Electronic Serial Number (GSM) | | ESN | Electronic Serial Number (GSM) |
| MAC | Media Access Control Address (IEEE) | | MAC | Media Access Control Address (IEEE) |
| WiMAX | Device Certificate Unique ID | | WiMAX | Device Certificate Unique ID |
| IMEI | International Mobile Equipment ID (GSM) | | IMEI | International Mobile Equipment ID (GSM) |
| IMSI | International Mobile Subscriber ID (GSM) | | IMSI | International Mobile Subscriber ID (GSM) |
| UDI | Unique Device Identifier | | UDI | Unique Device Identifier |
| RFID | Radio Frequency Identification | | RFID | Radio Frequency Identification |
| SN | Manufacturer Serial Number | | SN | Manufacturer Serial Number |
+--------+------------------------------------------+ +--------+------------------------------------------+
Figure 6: Registry with Device Identifier Types. Figure 6: Registry with Device Identifier Types.
Reason for Need: Uniquely identifies the device (or, in the case of Reason for Need: Uniquely identifies the device (or, in the case of
IMSI, a SIM), independent of any signaling identifiers present in IMSI, a SIM), independent of any signaling identifiers present in
the call signaling stream. the call signaling stream.
How Used by Call Taker: Probably not used by the call taker; may be How Used by Call Taker: Probably not used by the call taker; may be
used by PSAP management during an investigation. used by PSAP management during an investigation.
skipping to change at page 27, line 34 skipping to change at page 26, line 48
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.
4.4.3. EmergencyCallData.SubscriberInfo Example 4.4.3. EmergencyCallData.SubscriberInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<sub:EmergencyCallData.SubscriberInfo <sub:EmergencyCallData.SubscriberInfo
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:sub=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
privacyRequested="false"> privacyRequested="false">
<sub:DataProviderReference>FEABFECD901@example.org <sub:DataProviderReference>FEABFECD901@example.org
</sub:DataProviderReference> </sub:DataProviderReference>
<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<vcards> <vcards>
<vcard> <vcard>
<fn><text>Simon Perreault</text></fn> <fn><text>Simon Perreault</text></fn>
<n> <n>
<surname>Perreault</surname> <surname>Perreault</surname>
<given>Simon</given> <given>Simon</given>
<additional/> <additional/>
skipping to change at page 33, line 41 skipping to change at page 33, line 8
field (as specified in Section 5.1). field (as specified in Section 5.1).
For example, to reference a block with MIME type 'application/ For example, to reference a block with MIME type 'application/
EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set EmergencyCallData.ProviderInfo+xml', the 'purpose' parameter is set
to 'EmergencyCallData.ProviderInfo'. An example to 'EmergencyCallData.ProviderInfo'. An example
'EmergencyCallDataReference' element for this would be: 'EmergencyCallDataReference' element for this would be:
<EmergencyCallDataReference ref="https://www.example.com/23sedde3" <EmergencyCallDataReference ref="https://www.example.com/23sedde3"
purpose="EmergencyCallData.ProviderInfo"/> purpose="EmergencyCallData.ProviderInfo"/>
The 'EmergencyCallDataReference' element transmits one additional
data block; multiple additional data blocks may be transmitted by
using multiple 'EmergencyCallDataReference' elements.
For example:
<provided-by
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10">
<ad:DataProviderReference>flurbit735@es.example.com
</ad:DataProviderReference>
<ad:EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2" />
<ad:EmergencyCallDataReference
purpose="EmergencyCallData.ProviderInfo"
ref="https://example.com/ref3" />
<ad:EmergencyCallDataReference
purpose="EmergencyCallData.Comment"
ref="https://example.com/ref4" />
</provided-by>
Example Provided-By by Reference.
5.3. Transmitting Blocks by Value using the Provided-By Element 5.3. Transmitting Blocks by Value using the Provided-By Element
It is RECOMMENDED that access networks supply the data specified in It is RECOMMENDED that access networks supply the data specified in
this document by reference, but they MAY provide the data by value. this document by reference, but they MAY provide the data by value.
The 'EmergencyCallDataValue' element is used to transmit an The 'EmergencyCallDataValue' element is used to transmit one or more
additional data block by value within a 'Provided-By' element of a additional data blocks by value within a 'Provided-By' element of a
PIDF-LO. The 'EmergencyCallDataValue' element has one attribute: PIDF-LO. Each block being transmitted is placed (as a child element)
'purpose' to indicate the type of data block contained. The value of inside the 'EmergencyCallDataValue' element. (The same XML structure
'purpose' is the same as used in a 'Call-Info' header field (as
specified in Section 5, and in Section 5.1). The same XML structure
as would be contained in the corresponding MIME type body part is as would be contained in the corresponding MIME type body part is
placed inside the 'EmergencyCallDataValue' element. placed inside the 'EmergencyCallDataValue' element.)
For example: For example:
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10">
<ad:DataProviderReference>flurbit735@es.example.com
</ad:DataProviderReference> <EmergencyCallDataValue>
<ad:EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo" <EmergencyCallData.ProviderInfo
ref="https://example.com/ref2" /> xmlns=
<sub:EmergencyCallData.Comment "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData.Comment"> <DataProviderReference>flurbit735@es.example.com
<sub:Comment xml:lang="en">This is an example text. </DataProviderReference>
</sub:Comment> <DataProviderString>Access Network Examples, Inc
</sub:EmergencyCallData.Comment> </DataProviderString>
<ProviderID>urn:nena:companyid:Test</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Access Network Provider
</TypeOfProvider>
<ContactURI>tel:+1 555-555-0897</ContactURI>
<Language>EN</Language>
</EmergencyCallData.ProviderInfo>
<EmergencyCallData.Comment
xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<DataProviderReference>flurbit735@es.example.com
</DataProviderReference>
<Comment xml:lang="en">This is an example text.
</Comment>
</EmergencyCallData.Comment>
<EmergencyCallDataValue
purpose="EmergencyCallData.ProviderInfo">
<ProviderID>Test</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Access Network Provider
</TypeOfProvider>
<ContactURI>sip:15555550987@burf.example.com;user=phone
</ContactURI>
</EmergencyCallDataValue> </EmergencyCallDataValue>
</provided-by> </provided-by>
Example Provided-By by Value. Example Provided-By by Value.
5.4. The Content-Disposition Parameter 5.4. The Content-Disposition Parameter
RFC 5621 [RFC5621] discusses the handling of message bodies in SIP. RFC 5621 [RFC5621] discusses the handling of message bodies in SIP.
It updates and clarifies handling originally defined in RFC 3261 It updates and clarifies handling originally defined in RFC 3261
[RFC3261] based on implementation experience. While RFC 3261 did not [RFC3261] based on implementation experience. While RFC 3261 did not
mandate support for 'multipart' message bodies, 'multipart/mixed' mandate support for 'multipart' message bodies, 'multipart/mixed'
skipping to change at page 36, line 12 skipping to change at page 36, line 5
Figure 10: Example for use of the Content-Disposition Parameter in Figure 10: Example for use of the Content-Disposition Parameter in
SIP. SIP.
6. Examples 6. Examples
This section illustrates a longer and more complex example, as shown This section illustrates a longer and more complex example, as shown
in Figure 11. In this example additional data is added by the end in Figure 11. In this example additional data is added by the end
device, included by the VoIP provider (via the PIDF-LO), and provided device, included by the VoIP provider (via the PIDF-LO), and provided
by the access network provider. by the access network provider.
O +----+ [=============] [==============] O +----+ [============] [=============]
/|\ | UA | [ Access ] [ VoIP ] /|\ | UA | [ Access ] [ VoIP ]
| +----+ [ Network ] [ Provider ] | +----+ [ Network ] [ Provider ]
/ \ [ Provider ] [ example.org ] / \ [ Provider ] [ example.org ]
[ ] [ ] [ ] [ ]
(1) [ ] (2) [ ] (1) [ ] (2) [ ]
Emergency Call [ ] Emergency Call [ ] Emergency Call [ ] Emergency Call [ ]
------------------------------------------------------------> ] -------------------------------------------------------> ]
+Device Info [ ] +Device Info [ ] +Device Info [ ] +Device Info [ ]
+Data Provider Info [ ^ ] +Data Provider Info [ | ] +Data Prov. Info [ ^ ] +Data Provider Info [ | ]
+Location URI [===.=========] +Location URI [=====|========] +Location URI [=======.====] +Location URI [==|==========]
. | . |
. | . |
+Location . [================] | +Location . [==============] |
+Owner/Subscriber Info . [ ] (3) | +Owner/Subscriber Info . [ ] (3) |
+Device Info . (4) [ <---------------+ +Device Info . (4) [ <----------+
+Data Provider Info #3 .............> ] Emergency Call +Data Provider Info #3 ..........> ] Emergency Call
[ ] +Device Info [ ] +Device Info
[ PSAP ] +Data Provider Info #2 [ PSAP ] +Data Prov. Info #2
[ ] +Location URI [ ] +Location URI
[================] [==============]
Legend: Legend:
--- Emergency Call Setup Procedure --- Emergency Call Setup Procedure
... Location Retrieval/Response ... Location Retrieval/Response
Figure 11: Additional Data Example Flow Figure 11: Additional Data Example Flow
The example scenario starts with the end device itself adding device The example scenario starts with the end device itself adding device
information, owner/subscriber information, a location URI, and data information, owner/subscriber information, a location URI, and data
provider information to the outgoing emergency call setup message provider information to the outgoing emergency call setup message
(see step #1 in Figure 11). The SIP INVITE example is shown in (see step #1 in Figure 11). The SIP INVITE example is shown in
Figure 12. Figure 12.
INVITE urn:service:sos SIP/2.0 INVITE urn:service:sos SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg>
;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo, ;purpose=EmergencyCallData.ProviderInfo,
<cid:0123456789@atlanta.example.com> <cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo ;purpose=EmergencyCallData.DeviceInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Contact: <sips:hannes@example.com> Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
skipping to change at page 39, line 40 skipping to change at page 39, line 32
<key> <key>
<parameters> <parameters>
<type><text>home</text></type> <type><text>home</text></type>
</parameters> </parameters>
<uri>https://www.example.com/key.asc <uri>https://www.example.com/key.asc
</uri> </uri>
</key> </key>
<tz><text>Finland/Helsinki</text></tz> <tz><text>Finland/Helsinki</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://example.com/hannes.tschofenig</uri> <uri>http://example.com/hannes.tschofenig
</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
--boundary1-- --boundary1--
Figure 12: End Device sending SIP INVITE with Additional Data. Figure 12: End Device sending SIP INVITE with Additional Data.
In this example, information available to the access network provider In this example, information available to the access network provider
is included in the call setup message only indirectly via the use of is included in the call setup message only indirectly via the use of
skipping to change at page 40, line 30 skipping to change at page 40, line 23
reference in the header), which allows us to illustrate the use of reference in the header), which allows us to illustrate the use of
multiple data provider info blocks. The resulting message is shown multiple data provider info blocks. The resulting message is shown
in Figure 13. The SIP INVITE is sent to the PSAP in step #3. in Figure 13. The SIP INVITE is sent to the PSAP in step #3.
INVITE sips:psap@example.org SIP/2.0 INVITE sips:psap@example.org SIP/2.0
Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9 Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
Max-Forwards: 70 Max-Forwards: 70
To: <urn:service:sos> To: <urn:service:sos>
From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
Call-ID: 3848276298220188511@example.com Call-ID: 3848276298220188511@example.com
Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon, Call-Info: <http://wwww.example.com/hannes/photo.jpg>
;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo ;purpose=EmergencyCallData.ProviderInfo
<cid:0123456789@atlanta.example.com> <cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo ;purpose=EmergencyCallData.DeviceInfo
Call-Info: <cid:bloorpyhex@atlanta.example.com> Call-Info: <cid:bloorpyhex@atlanta.example.com>
;purpose=EmergencyCallData.ServiceInfo ;purpose=EmergencyCallData.ServiceInfo
Call-Info: <cid:aaabbb@atlanta.example.com> Call-Info: <cid:aaabbb@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo ;purpose=EmergencyCallData.ProviderInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
skipping to change at page 43, line 16 skipping to change at page 43, line 10
<key> <key>
<parameters> <parameters>
<type><text>home</text></type> <type><text>home</text></type>
</parameters> </parameters>
<uri>https://www.example.com/key.asc <uri>https://www.example.com/key.asc
</uri> </uri>
</key> </key>
<tz><text>Finland/Helsinki</text></tz> <tz><text>Finland/Helsinki</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://example.com/hannes.tschofenig</uri> <uri>http://example.com/hannes.tschofenig
</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </xc:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ServiceInfo+xml Content-Type: application/EmergencyCallData.ServiceInfo+xml
Content-ID: <bloorpyhex@atlanta.example.com> Content-ID: <bloorpyhex@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
skipping to change at page 46, line 28 skipping to change at page 46, line 23
</gp:location-info> </gp:location-info>
<gp:usage-rules> <gp:usage-rules>
<gbp:retransmission-allowed>true <gbp:retransmission-allowed>true
</gbp:retransmission-allowed> </gbp:retransmission-allowed>
<gbp:retention-expiry>2013-12-10T20:00:00Z <gbp:retention-expiry>2013-12-10T20:00:00Z
</gbp:retention-expiry> </gbp:retention-expiry>
</gp:usage-rules> </gp:usage-rules>
<gp:method>802.11</gp:method> <gp:method>802.11</gp:method>
<provided-by <provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10">
<EmergencyCallDataReference purpose="EmergencyCallData.ServiceInfo" <EmergencyCallDataReference
ref="https://example.com/ref2"/> purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2"/>
<EmergencyCallDataValue> <EmergencyCallDataValue>
<EmergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>88QV4FpfZ976T@example.com <DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference> </DataProviderReference>
<DataProviderString>University of Example <DataProviderString>University of Example
</DataProviderString> </DataProviderString>
<ProviderID>urn:nena:companyid:uoi</ProviderID> <ProviderID>urn:nena:companyid:uoi</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Other</TypeOfProvider> <TypeOfProvider>Other</TypeOfProvider>
<ContactURI>tel:+1 555-824-5222</ContactURI> <ContactURI>tel:+1 555-824-5222</ContactURI>
<Language>EN</Language> <Language>EN</Language>
</EmergencyCallData.ProviderInfo> </EmergencyCallData.ProviderInfo>
skipping to change at page 47, line 28 skipping to change at page 47, line 25
7. XML Schemas 7. XML Schemas
This section defines the XML schemas of the five data blocks. This section defines the XML schemas of the five data blocks.
Additionally, the Provided-By schema is specified. Additionally, the Provided-By schema is specified.
7.1. EmergencyCallData.ProviderInfo XML Schema 7.1. EmergencyCallData.ProviderInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
skipping to change at page 48, line 46 skipping to change at page 48, line 43
minOccurs="1" maxOccurs="unbounded" /> minOccurs="1" maxOccurs="unbounded" />
<xs:element name="DataProviderContact" <xs:element name="DataProviderContact"
type="xc:vcardType" minOccurs="0" type="xc:vcardType" minOccurs="0"
maxOccurs="1"/> maxOccurs="1"/>
<xs:element name="SubcontratorPrincipal" <xs:element name="SubcontratorPrincipal"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="SubcontractorPriority" <xs:element name="SubcontractorPriority"
type="pi:SubcontractorPriorityType" minOccurs="0" maxOccurs="1"/> type="pi:SubcontractorPriorityType"
minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 15: EmergencyCallData.ProviderInfo XML Schema. Figure 15: EmergencyCallData.ProviderInfo XML Schema.
7.2. EmergencyCallData.ServiceInfo XML Schema 7.2. EmergencyCallData.ServiceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="EmergencyCallData.ServiceInfo" type="svc:ServiceInfoType"/> <xs:element name="EmergencyCallData.ServiceInfo"
type="svc:ServiceInfoType"/>
<xs:complexType name="ServiceInfoType"> <xs:complexType name="ServiceInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="ServiceEnvironment" <xs:element name="ServiceEnvironment"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ServiceType" <xs:element name="ServiceType"
type="xs:string" minOccurs="1" maxOccurs="unbounded"/> type="xs:string" minOccurs="1"
maxOccurs="unbounded"/>
<xs:element name="ServiceMobility" <xs:element name="ServiceMobility"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 16: EmergencyCallData.ServiceInfo XML Schema. Figure 16: EmergencyCallData.ServiceInfo XML Schema.
7.3. EmergencyCallData.DeviceInfo XML Schema 7.3. EmergencyCallData.DeviceInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="EmergencyCallData.DeviceInfo" type="dev:DeviceInfoType"/> <xs:element name="EmergencyCallData.DeviceInfo"
type="dev:DeviceInfoType"/>
<xs:complexType name="DeviceInfoType"> <xs:complexType name="DeviceInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="DeviceClassification" <xs:element name="DeviceClassification"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceMfgr" <xs:element name="DeviceMfgr"
skipping to change at page 51, line 4 skipping to change at page 51, line 11
<xs:element name="DeviceSpecificData" <xs:element name="DeviceSpecificData"
type="xs:anyURI" minOccurs="0" maxOccurs="1"/> type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
<xs:element name="DeviceSpecificType" <xs:element name="DeviceSpecificType"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 17: EmergencyCallData.DeviceInfo XML Schema. Figure 17: EmergencyCallData.DeviceInfo XML Schema.
7.4. EmergencyCallData.SubscriberInfo XML Schema 7.4. EmergencyCallData.SubscriberInfo XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" "urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:sub=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>
<xs:element name="EmergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType"/> <xs:element name="EmergencyCallData.SubscriberInfo"
type="sub:SubscriberInfoType"/>
<xs:complexType name="SubscriberInfoType"> <xs:complexType name="SubscriberInfoType">
<xs:complexContent> <xs:complexContent>
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="SubscriberData" type="xc:vcardType" <xs:element name="SubscriberData"
type="xc:vcardType"
minOccurs="0" maxOccurs="1" /> minOccurs="0" maxOccurs="1" />
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="privacyRequested" type="xs:boolean" use="required"/> <xs:attribute name="privacyRequested" type="xs:boolean"
use="required"/>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
Figure 18: EmergencyCallData.SubscriberInfo XML Schema. Figure 18: EmergencyCallData.SubscriberInfo XML Schema.
7.5. EmergencyCallData.Comment XML Schema 7.5. EmergencyCallData.Comment XML Schema
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData:Comment" "urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:element name="EmergencyCallData.Comment" type="com:CommentType"/> <xs:element name="EmergencyCallData.Comment"
type="com:CommentType"/>
<xs:complexType name="CommentType"> <xs:complexType name="CommentType">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="Comment" <xs:element name="Comment"
type="com:CommentSubType" minOccurs="0" type="com:CommentSubType" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
skipping to change at page 53, line 4 skipping to change at page 54, line 6
Figure 19: EmergencyCallData.Comment XML Schema. Figure 19: EmergencyCallData.Comment XML Schema.
7.6. Provided-By XML Schema 7.6. Provided-By XML Schema
This section defines the Provided-By schema. This section defines the Provided-By schema.
<?xml version="1.0"?> <?xml version="1.0"?>
<xs:schema <xs:schema
targetNamespace= targetNamespace=
"urn:ietf:params:xml:ns:EmergencyCallData" "urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData"
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:sub="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" xmlns:sub=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment" xmlns:com="urn:ietf:params:xml:ns:EmergencyCallData:Comment"
elementFormDefault="qualified" attributeFormDefault="unqualified"> elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"/> <xs:import namespace=
<xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"/> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"/> <xs:import namespace=
<xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"/> "urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"/>
<xs:import namespace="urn:ietf:params:xml:ns:EmergencyCallData:Comment"/> <xs:import namespace=
"urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"/>
<xs:import namespace=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"/>
<xs:import namespace=
"urn:ietf:params:xml:ns:EmergencyCallData:Comment"/>
<xs:element name="provided-by" type="ad:provided-by-Type"/> <xs:element name="provided-by" type="ad:provided-by-Type"/>
<xs:complexType name="provided-by-Type"> <xs:complexType name="provided-by-Type">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="EmergencyCallDataReference" <xs:element name="EmergencyCallDataReference"
type="ad:ByRefType" type="ad:ByRefType"
skipping to change at page 59, line 47 skipping to change at page 60, line 37
Name: The identifier which will be used in the 'ProviderIDSeries' Name: The identifier which will be used in the 'ProviderIDSeries'
element. element.
Source: The full name of the organization issuing the identifiers. Source: The full name of the organization issuing the identifiers.
URL: A URL to the organization for further information. URL: A URL to the organization for further information.
The initial set of values is listed in Figure 21. The initial set of values is listed in Figure 21.
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
| Name | Source | URL | | Name | Source | URL |
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
| NENA | National Emergency | http://www.nena.org | | NENA | National Emergency | http://www.nena.org |
| | Number Association | | | | Number Association | |
| EENA | European Emergency | http://www.eena.org | | EENA | European Emergency | http://www.eena.org |
| | Number Association | | | | Number Association | |
| domain | (The ID is a fully- | (not applicable) | | domain | (The ID is a fully- | (not applicable) |
| | qualified domain name) | | | | qualified domain name) | |
+-----------+--------------------------+----------------------+ +-----------+--------------------------+----------------------+
Figure 21: Provider ID Series Registry. Figure 21: Provider ID Series Registry.
10.1.2. Service Environment Registry 10.1.2. Service Environment Registry
This document creates a new sub-registry called 'Additional Call This document creates a new sub-registry called 'Additional Call
Service Environment'. As defined in [RFC5226], this registry Service Environment'. As defined in [RFC5226], this registry
operates under "Expert Review" rules. The expert should determine operates under "Expert Review" rules. The expert should determine
that the entity requesting a new value is relevant for this service that the entity requesting a new value is relevant for this service
element, and that the new value is distinct from existing values, and element, and that the new value is distinct from existing values, and
its use is unambiguous. its use is unambiguous.
The content of this registry includes: The content of this registry includes:
Token: The value to be used in the <ServiceEnvironment> element. Token: The value to be used in the <ServiceEnvironment> element.
Description: A short description of the value. Description: A short description of the value.
The initial set of values is listed in Figure 22. The initial set of values is listed in Figure 22.
+-----------+--------------------------+ +-----------+--------------------------+
| Token | Description | | Token | Description |
+-----------+--------------------------+ +-----------+--------------------------+
| Business | Business service | | Business | Business service |
| Residence | Residential service | | Residence | Residential service |
| unknown | Type of service unknown | | unknown | Type of service unknown |
| | (e.g., anonymous pre- | | | (e.g., anonymous pre- |
| | paid service) | | | paid service) |
+-----------+--------------------------+ +-----------+--------------------------+
Figure 22: Service Environment Registry. Figure 22: Service Environment Registry.
10.1.3. Service Type Registry 10.1.3. Service Type Registry
This document creates a new sub-registry called 'Additional Call This document creates a new sub-registry called 'Additional Call
Service Type'. As defined in [RFC5226], this registry operates under Service Type'. As defined in [RFC5226], this registry operates under
"Expert Review" rules. The expert should determine that the entity "Expert Review" rules. The expert should determine that the entity
requesting a new value is relevant for this service element and that requesting a new value is relevant for this service element and that
the requested value is clearly distinct from other values so that the requested value is clearly distinct from other values so that
skipping to change at page 61, line 29 skipping to change at page 62, line 23
which value is to be used. which value is to be used.
The content of this registry includes: The content of this registry includes:
Token: The value used in the <ServiceMobility> element. Token: The value used in the <ServiceMobility> element.
Description: A short description of the value. Description: A short description of the value.
The initial set of values is listed in Figure 23. The initial set of values is listed in Figure 23.
+-----------+----------------------------+ +-----------+----------------------------+
| Token | Description | | Token | Description |
+-----------+----------------------------+ +-----------+----------------------------+
| Mobile | The device is able to | | Mobile | The device is able to |
| | move at any time | | | move at any time |
| Fixed | The device is not expected | | Fixed | The device is not expected |
| | to move unless the service | | | to move unless the service |
| | is relocated | | | is relocated |
| Nomadic | The device is not expected | | Nomadic | The device is not expected |
| | to change its point of | | | to change its point of |
| | attachment while on a call | | | attachment while on a call |
| Unknown | No information is known | | Unknown | No information is known |
| | about the service mobility | | | about the service mobility |
| | environment for the device | | | environment for the device |
+-----------+----------------------------+ +-----------+----------------------------+
Figure 23: Service Environment Registry. Figure 23: Service Environment Registry.
10.1.5. Service Provider Type Registry 10.1.5. Service Provider Type Registry
This document creates a new sub-registry called 'Service Provider This document creates a new sub-registry called 'Service Provider
Type'. As defined in [RFC5226], this registry operates under "Expert Type'. As defined in [RFC5226], this registry operates under "Expert
Review". The expert should determine that the proposed new value is Review". The expert should determine that the proposed new value is
distinct from existing values and appropriate for use in the distinct from existing values and appropriate for use in the
TypeOfServicerProvider element TypeOfServicerProvider element
The content of this registry includes: The content of this registry includes:
Tokenproviderid: The value used in the 'TypeOfProvider' element. Tokenproviderid: The value used in the 'TypeOfProvider' element.
skipping to change at page 63, line 43 skipping to change at page 64, line 31
The content of this registry includes: The content of this registry includes:
Token: The value to be placed in the <DeviceSpecificType> element. Token: The value to be placed in the <DeviceSpecificType> element.
Description: Short description identifying the the data. Description: Short description identifying the the data.
Specification: Citation for the specification of the data. Specification: Citation for the specification of the data.
The initial set of values are listed in Figure 24. The initial set of values are listed in Figure 24.
+----------+----------------------------------------+----------------+ +----------+----------------------------------------+---------------+
| Token | Description | Specification | | Token | Description | Specification |
+----------+----------------------------------------+----------------+ +----------+----------------------------------------+---------------+
| IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006 | | IEEE1512 | Common Incident Management Message Set | IEEE 1512-2006|
+----------+----------------------------------------+----------------+ +----------+----------------------------------------+---------------+
Figure 24: Device/Service Data Type Registry. Figure 24: Device/Service Data Type Registry.
10.1.10. Emergency Call Data Types Registry 10.1.10. Emergency Call Data Types Registry
This document creates a new sub-registry called 'Emergency Call Data This document creates a new sub-registry called 'Emergency Call Data
Types' in the 'purpose' registry established by RFC 3261 [RFC3261]. Types' in the 'purpose' registry established by RFC 3261 [RFC3261].
As defined in [RFC5226], this registry operates under "Expert Review" As defined in [RFC5226], this registry operates under "Expert Review"
and "Specification Required" rules. The expert is responsible for and "Specification Required" rules. The expert is responsible for
verifying that the document contains a complete and clear verifying that the document contains a complete and clear
specification and the proposed functionality does not obviously specification and the proposed functionality does not obviously
duplicate existing functionality. duplicate existing functionality.
The content of this registry includes: The content of this registry includes:
skipping to change at page 64, line 27 skipping to change at page 65, line 15
Reference: The document that describes the data object Reference: The document that describes the data object
Note that the values from this registry are part of the Note that the values from this registry are part of the
'EmergencyCallData' compound value; when used as a value of the 'EmergencyCallData' compound value; when used as a value of the
'purpose' parameter of the Call-Info header, the values listed in 'purpose' parameter of the Call-Info header, the values listed in
this registry are prefixed by 'EmergencyCallData.' per the the this registry are prefixed by 'EmergencyCallData.' per the the
'EmergencyCallData' registation Section 10.2. 'EmergencyCallData' registation Section 10.2.
The initial set of values are listed in Figure 25. The initial set of values are listed in Figure 25.
+----------------+------------+ +----------------+------------+
| Token | Reference | | Token | Reference |
+----------------+------------+ +----------------+------------+
| ProviderInfo | [This RFC] | | ProviderInfo | [This RFC] |
| ServiceInfo | [This RFC] | | ServiceInfo | [This RFC] |
| DeviceInfo | [This RFC] | | DeviceInfo | [This RFC] |
| SubscriberInfo | [This RFC] | | SubscriberInfo | [This RFC] |
| Comment | [This RFC] | | Comment | [This RFC] |
+----------------+------------+ +----------------+------------+
Figure 25: Additional Data Blocks Registry. Figure 25: Additional Data Blocks Registry.
10.2. 'EmergencyCallData' Purpose Parameter Value 10.2. 'EmergencyCallData' Purpose Parameter Value
This document defines the 'EmergencyCallData' value for the "purpose" This document defines the 'EmergencyCallData' value for the "purpose"
parameter of the Call-Info header field. The Call-Info header and parameter of the Call-Info header field. The Call-Info header and
the corresponding registry for the 'purpose' parameter was the corresponding registry for the 'purpose' parameter was
established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData' established with RFC 3261 [RFC3261]. Note that 'EmergencyCallData'
is a compound value; when used as a value of the 'purpose' parameter is a compound value; when used as a value of the 'purpose' parameter
skipping to change at page 71, line 30 skipping to change at page 72, line 16
<?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
10.5.2. Registration for 10.5.2. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
skipping to change at page 72, line 15 skipping to change at page 73, line 17
<!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
10.5.3. Registration for 10.5.3. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
skipping to change at page 72, line 47 skipping to change at page 74, line 17
<!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
10.5.4. Registration for 10.5.4. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
skipping to change at page 73, line 33 skipping to change at page 75, line 17
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Namespace for Additional Emergency Call Data: <title>Namespace for Additional Emergency Call Data:
Device Information</title> Device Information</title>
</head> </head>
<body> <body>
<h1>Namespace for Additional Data related to an Emergency Call</h1> <h1>Namespace for Additional Data related to an Emergency Call
</h1>
<h2>Device Information</h2> <h2>Device Information</h2>
<p>See [TBD: This document].</p> <p>See [TBD: This document].</p>
</body> </body>
</html> </html>
END END
10.5.5. Registration for 10.5.5. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
skipping to change at page 74, line 21 skipping to change at page 76, line 17
<!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
10.5.6. Registration for 10.5.6. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment urn:ietf:params:xml:ns:EmergencyCallData:Comment
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
skipping to change at page 75, line 4 skipping to change at page 77, line 13
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>Namespace for Additional Emergency Call Data:Comment</title> </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
10.6. Schema Registrations 10.6. Schema Registrations
This specification registers five schemas, as per the guidelines in This specification registers five schemas, as per the guidelines in
RFC 3688 [RFC3688]. RFC 3688 [RFC3688].
skipping to change at page 76, line 36 skipping to change at page 78, line 45
large number of participants in NENA standardization efforts, large number of participants in NENA standardization efforts,
originally in the Long Term Definition Working Group, the Data originally in the Long Term Definition Working Group, the Data
Technical Committee and most recently the Additional Data working Technical Committee and most recently the Additional Data working
group. The authors are grateful for the initial work and extended group. The authors are grateful for the initial work and extended
comments provided by many NENA participants, including Delaine comments provided by many NENA participants, including Delaine
Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James
Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra, Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra,
and Robert (Bob) Sherry. and Robert (Bob) Sherry.
We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin
Thomson, Keith Drage, Laura Liess, and Barbara Stark for their review Thomson, Keith Drage, Laura Liess, Chris Santer, and Barbara Stark
comments. Guy Caron deserves special mention for his detailed review for their review comments. Guy Caron deserves special mention for
comments. his detailed and extensive review comments.
12. References 12. References
12.1. Normative References 12.1. Normative References
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. Locators", RFC 2392, August 1998.
[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet, [RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
F., Watson, M., and M. Zonoun, "MIME media types for ISUP F., Watson, M., and M. Zonoun, "MIME media types for ISUP
and QSIG Objects", RFC 3204, December 2001. and QSIG Objects", RFC 3204, December 2001.
skipping to change at page 78, line 5 skipping to change at page 80, line 14
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013. 6838, January 2013.
[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303, [RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
July 2014. July 2014.
12.2. Informational References 12.2. Informational References
[I-D.gellens-mmusic-negotiating-human-language] [I-D.gellens-slim-negotiating-human-language]
Randy, R., "Negotiating Human Language in Real-Time Gellens, R., "Negotiating Human Language in Real-Time
Communications", draft-gellens-mmusic-negotiating-human- Communications", draft-gellens-slim-negotiating-human-
language-02 (work in progress), February 2014. language (work in progress), October 2014.
[I-D.ietf-ecrit-psap-callback]
Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback",
draft-ietf-ecrit-psap-callback-13 (work in progress),
October 2013.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC [RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC
3966, December 2004. 3966, December 2004.
[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for [RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
Emergency Context Resolution with Internet Technologies", Emergency Context Resolution with Internet Technologies",
skipping to change at page 79, line 24 skipping to change at page 81, line 27
2013. 2013.
[RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A. [RFC7035] Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.
Thomson, "Relative Location Representation", RFC 7035, Thomson, "Relative Location Representation", RFC 7035,
October 2013. October 2013.
[RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M. [RFC7090] Schulzrinne, H., Tschofenig, H., Holmberg, C., and M.
Patel, "Public Safety Answering Point (PSAP) Callback", Patel, "Public Safety Answering Point (PSAP) Callback",
RFC 7090, April 2014. RFC 7090, April 2014.
12.3. URIs
[1] http://www.nena.org/?page=cid2014
[2] http://www.nena.org/?page=CompanyID
Appendix A. XML Schema for vCard/xCard Appendix A. XML Schema for vCard/xCard
This section contains the vCard/xCard XML schema version of the Relax This section contains the vCard/xCard XML schema version of the Relax
NG schema defined in RFC 6351 [RFC6351] for simplified use with the NG schema defined in RFC 6351 [RFC6351] for simplified use with the
XML schemas defined in this document. The schema in RFC 6351 XML schemas defined in this document. The schema in RFC 6351
[RFC6351] is the normative source and this section is informative [RFC6351] is the normative source and this section is informative
only. only.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
skipping to change at page 101, line 42 skipping to change at page 104, line 7
<xs:complexType> <xs:complexType>
<xs:group minOccurs="0" maxOccurs="unbounded" <xs:group minOccurs="0" maxOccurs="unbounded"
ref="ns1:property"/> ref="ns1:property"/>
<xs:attribute name="name" use="required"/> <xs:attribute name="name" use="required"/>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
</xs:schema> </xs:schema>
Authors' Addresses Authors' Addresses
Randall Gellens
Qualcomm Technologies, Inc.
5775 Morehouse Drive
San Diego, CA 92121
US
Email: rg+ietf@qti.qualcomm.com
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
(no affiliation) (no affiliation)
Email: Hannes.Tschofenig@gmx.net Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
Roger Marshall Roger Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
2401 Elliott Avenue 2401 Elliott Avenue
Seattle, WA 98121 Seattle, WA 98121
skipping to change at page 102, line 20 skipping to change at page 104, line 40
Roger Marshall Roger Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
2401 Elliott Avenue 2401 Elliott Avenue
Seattle, WA 98121 Seattle, WA 98121
US US
Phone: +1 206 792 2424 Phone: +1 206 792 2424
Email: rmarshall@telecomsys.com Email: rmarshall@telecomsys.com
URI: http://www.telecomsys.com URI: http://www.telecomsys.com
Randall Gellens
Qualcomm Technologies, Inc.
5775 Morehouse Drive
San Diego, CA 92121
US
Email: rg+ietf@qti.qualcomm.com
James Winterbottom James Winterbottom
(no affiliation) (no affiliation)
AU AU
Email: a.james.winterbottom@gmail.com Email: a.james.winterbottom@gmail.com
 End of changes. 98 change blocks. 
313 lines changed or deleted 380 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/