< draft-ietf-ecrit-additional-data-28.txt   draft-ietf-ecrit-additional-data-29.txt >
ECRIT R. Gellens ECRIT R. Gellens
Internet-Draft Qualcomm Technologies, Inc. Internet-Draft Qualcomm Technologies, Inc.
Intended status: Standards Track B. Rosen Intended status: Standards Track B. Rosen
Expires: August 8, 2015 NeuStar Expires: September 9, 2015 NeuStar
H. Tschofenig H. Tschofenig
R. Marshall R. Marshall
TeleCommunication Systems, Inc. TeleCommunication Systems, Inc.
J. Winterbottom J. Winterbottom
March 8, 2015
February 4, 2015
Additional Data Related to an Emergency Call Additional Data Related to an Emergency Call
draft-ietf-ecrit-additional-data-28.txt draft-ietf-ecrit-additional-data-29.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 1, line 48
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 8, 2015.
This Internet-Draft will expire on September 9, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 6 skipping to change at page 3, line 4
4.3.1. Device Classification . . . . . . . . . . . . . . . . 20 4.3.1. Device Classification . . . . . . . . . . . . . . . . 20
4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 22 4.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 22
4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 22 4.3.3. Device Model Number . . . . . . . . . . . . . . . . . 22
4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 22 4.3.4. Unique Device Identifier . . . . . . . . . . . . . . 22
4.3.5. Device/Service Specific Additional Data Structure . . 23 4.3.5. Device/Service Specific Additional Data Structure . . 23
4.3.6. Device/Service Specific Additional Data Structure 4.3.6. Device/Service Specific Additional Data Structure
Type . . . . . . . . . . . . . . . . . . . . . . . . 24 Type . . . . . . . . . . . . . . . . . . . . . . . . 24
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 . . . 24
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 . . . 25
4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 26 4.3.9. EmergencyCallData.DeviceInfo Example . . . . . . . . 26
4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26 4.4. Owner/Subscriber Information . . . . . . . . . . . . . . 26
4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26 4.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 26
4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27 4.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 27
4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27 4.4.3. EmergencyCallData.SubscriberInfo Example . . . . . . 27
4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 30 4.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 30
4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30 4.5.2. EmergencyCallData.Comment Example . . . . . . . . . . 30
5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30 5. Data Transport Mechanisms . . . . . . . . . . . . . . . . . . 30
5.1. Transmitting Blocks using the Call-Info Header . . . . . 32 5.1. Transmitting Blocks using the Call-Info Header . . . . . 32
5.2. Transmitting Blocks by Reference using the provided-by 5.2. Transmitting Blocks by Reference using the provided-by
Element . . . . . . . . . . . . . . . . . . . . . . . . . 33 Element . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.3. Transmitting Blocks by Value using the provided-by 5.3. Transmitting Blocks by Value using the provided-by
Element . . . . . . . . . . . . . . . . . . . . . . . . . 34 Element . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4. The Content-Disposition Parameter . . . . . . . . . . . . 35 5.4. The Content-Disposition Parameter . . . . . . . . . . . . 35
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 48 7. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 48 7.1. EmergencyCallData.ProviderInfo XML Schema . . . . . . . . 48
7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 50 7.2. EmergencyCallData.ServiceInfo XML Schema . . . . . . . . 50
7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 51 7.3. EmergencyCallData.DeviceInfo XML Schema . . . . . . . . . 51
7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 52 7.4. EmergencyCallData.SubscriberInfo XML Schema . . . . . . . 53
7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 53 7.5. EmergencyCallData.Comment XML Schema . . . . . . . . . . 54
7.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 54 7.6. provided-by XML Schema . . . . . . . . . . . . . . . . . 55
8. Security Considerations . . . . . . . . . . . . . . . . . . . 57 8. Security Considerations . . . . . . . . . . . . . . . . . . . 58
9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 58 9. Privacy Considerations . . . . . . . . . . . . . . . . . . . 59
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 61 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
10.1. Registry creation . . . . . . . . . . . . . . . . . . . 61 10.1. Registry creation . . . . . . . . . . . . . . . . . . . 62
10.1.1. Provider ID Series Registry . . . . . . . . . . . . 61 10.1.1. Provider ID Series Registry . . . . . . . . . . . . 62
10.1.2. Service Environment Registry . . . . . . . . . . . . 62 10.1.2. Service Environment Registry . . . . . . . . . . . . 63
10.1.3. Service Type Registry . . . . . . . . . . . . . . . 62 10.1.3. Service Type Registry . . . . . . . . . . . . . . . 63
10.1.4. Service Mobility Registry . . . . . . . . . . . . . 63 10.1.4. Service Mobility Registry . . . . . . . . . . . . . 64
10.1.5. Service Provider Type Registry . . . . . . . . . . . 63 10.1.5. Service Provider Type Registry . . . . . . . . . . . 64
10.1.6. Service Delivered Registry . . . . . . . . . . . . . 64 10.1.6. Service Delivered Registry . . . . . . . . . . . . . 65
10.1.7. Device Classification Registry . . . . . . . . . . . 64 10.1.7. Device Classification Registry . . . . . . . . . . . 65
10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 64 10.1.8. Device ID Type Type Registry . . . . . . . . . . . . 65
10.1.9. Device/Service Data Type Registry . . . . . . . . . 65 10.1.9. Device/Service Data Type Registry . . . . . . . . . 66
10.1.10. Emergency Call Data Types Registry . . . . . . . . . 65 10.1.10. Emergency Call Data Types Registry . . . . . . . . . 66
10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 66 10.2. 'EmergencyCallData' Purpose Parameter Value . . . . . . 67
10.3. URN Sub-Namespace Registration for provided-by Registry 10.3. URN Sub-Namespace Registration for provided-by Registry
Entry . . . . . . . . . . . . . . . . . . . . . . . . . 66 Entry . . . . . . . . . . . . . . . . . . . . . . . . . 68
10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 67 10.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 68
10.4.1. MIME Content-type Registration for 10.4.1. MIME Content-type Registration for
'application/EmergencyCallData.ProviderInfo+xml' . . 67 'application/EmergencyCallData.ProviderInfo+xml' . . 68
10.4.2. MIME Content-type Registration for 10.4.2. MIME Content-type Registration for
'application/EmergencyCallData.ServiceInfo+xml' . . 68 'application/EmergencyCallData.ServiceInfo+xml' . . 69
10.4.3. MIME Content-type Registration for 10.4.3. MIME Content-type Registration for
'application/EmergencyCallData.DeviceInfo+xml' . . . 69 'application/EmergencyCallData.DeviceInfo+xml' . . . 70
10.4.4. MIME Content-type Registration for 10.4.4. MIME Content-type Registration for
'application/EmergencyCallData.SubscriberInfo+xml' . 70 'application/EmergencyCallData.SubscriberInfo+xml' . 71
10.4.5. MIME Content-type Registration for 10.4.5. MIME Content-type Registration for
'application/EmergencyCallData.Comment+xml' . . . . 71 'application/EmergencyCallData.Comment+xml' . . . . 72
10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 72 10.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 73
10.5.1. Registration for 10.5.1. Registration for
urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 72 urn:ietf:params:xml:ns:EmergencyCallData . . . . . . 73
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 . . . . . . . . . . . . . . . . . . . . . . . . . 73 o . . . . . . . . . . . . . . . . . . . . . . . . . 74
10.5.3. Registration for 10.5.3. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 74 urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo 75
10.5.4. Registration for 10.5.4. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 75 urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo 76
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 . . . . . . . . . . . . . . . . . . . . . . . . 76 nfo . . . . . . . . . . . . . . . . . . . . . . . . 77
10.5.6. Registration for 10.5.6. Registration for
urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 77 urn:ietf:params:xml:ns:EmergencyCallData:Comment . . 78
10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 78 10.6. Schema Registrations . . . . . . . . . . . . . . . . . . 79
10.7. VCard Parameter Value Registration . . . . . . . . . . . 79 10.7. VCard Parameter Value Registration . . . . . . . . . . . 80
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 79 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 80
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 80 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.1. Normative References . . . . . . . . . . . . . . . . . . 80 12.1. Normative References . . . . . . . . . . . . . . . . . . 81
12.2. Informational References . . . . . . . . . . . . . . . . 81 12.2. Informational References . . . . . . . . . . . . . . . . 82
12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 82 12.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 82 Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 83
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 105 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 106
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 11, line 43 skipping to change at page 11, line 43
data for assistance in handling the call. data for assistance in handling the call.
4.1.6. Data Provider Languages(s) Supported 4.1.6. Data Provider Languages(s) Supported
Data Element: Data Provider Language(s) supported Data Element: Data Provider Language(s) supported
Use: Required. Use: Required.
XML Element: <Language> XML Element: <Language>
Description: The language used by the entity at the Data Provider Description: This field encodes the language used by the entity at
Contact URI, as an alpha 2-character code as defined in ISO the Data Provider Contact URI. The content of this field consists
639-1:2002 Codes for the representation of names of languages -- of a single token from the language tags registry, which can be
Part 1: Alpha-2 code Multiple instances of this element may occur. found at [LanguageTagRegistry], and is defined in [RFC5646].
Order is significant; preferred language should appear first. The Multiple instances of this element may occur but the order is
significant and the preferred language should appear first. The
content MUST reflect the languages supported at the contact URI. content MUST reflect the languages supported at the contact URI.
Note that 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-slim-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.
skipping to change at page 13, line 46 skipping to change at page 13, line 46
element MUST have the value "main". element MUST have the value "main".
Reason for Need: Inform the call taker whom to contact first, if Reason for Need: Inform the call taker whom to contact first, if
support is needed. support is needed.
How Used by Call Taker: To decide which entity to contact first if How Used by Call Taker: To decide which entity to contact first if
assistance is needed. assistance is needed.
4.1.10. ProviderInfo Example 4.1.10. ProviderInfo Example
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<ad:EmergencyCallData.ProviderInfo <ad:EmergencyCallData.ProviderInfo
xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:ad="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ad:DataProviderReference>string0987654321@example.org <ad:DataProviderReference>string0987654321@example.org
</ad:DataProviderReference> </ad:DataProviderReference>
<ad:DataProviderString>Example VoIP Provider
</ad:DataProviderString> <ad:DataProviderString>Example VoIP Provider
<ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID> </ad:DataProviderString>
<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries> <ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>
<ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider> <ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
<ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI> <ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider>
<ad:Language>EN</ad:Language> <ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI>
<ad:DataProviderContact <ad:Language>en</ad:Language>
xmlns="urn:ietf:params:xml:ns:vcard-4.0"> <ad:DataProviderContact
<vcard> xmlns="urn:ietf:params:xml:ns:vcard-4.0">
<fn><text>Hannes Tschofenig</text></fn> <vcard>
<n> <fn><text>Hannes Tschofenig</text></fn>
<surname>Hannes</surname> <n>
<given>Tschofenig</given> <surname>Hannes</surname>
<additional/> <given>Tschofenig</given>
<prefix/> <additional/>
<suffix>Dipl. Ing.</suffix> <prefix/>
</n> <suffix>Dipl. Ing.</suffix>
<bday><date>--0203</date></bday> </n>
<anniversary> <bday><date>--0203</date></bday>
<date-time>20090808T1430-0500</date-time> <anniversary>
</anniversary> <date-time>20090808T1430-0500</date-time>
<gender><sex>M</sex></gender> </anniversary>
<lang> <gender><sex>M</sex></gender>
<parameters><pref><integer>1</integer></pref> <lang>
</parameters> <parameters><pref><integer>1</integer></pref>
<language-tag>de</language-tag> </parameters>
</lang> <language-tag>de</language-tag>
<lang> </lang>
<parameters><pref><integer>2</integer></pref> <lang>
</parameters> <parameters><pref><integer>2</integer></pref>
<language-tag>en</language-tag> </parameters>
</lang> <language-tag>en</language-tag>
<org> </lang>
<parameters><type><text>work</text></type> <org>
</parameters> <parameters><type><text>work</text></type>
<text>Example VoIP Provider</text> </parameters>
</org> <text>Example VoIP Provider</text>
<adr> </org>
<parameters> <adr>
<type><text>work</text></type> <parameters>
<label><text>Hannes Tschofenig <type><text>work</text></type>
Linnoitustie 6 <label><text>Hannes Tschofenig
Espoo , Finland Linnoitustie 6
02600</text></label> Espoo , Finland
</parameters> 02600</text></label>
<pobox/> </parameters>
<ext/> <pobox/>
<street>Linnoitustie 6</street> <ext/>
<locality>Espoo</locality> <street>Linnoitustie 6</street>
<region>Uusimaa</region> <locality>Espoo</locality>
<code>02600</code> <region>Uusimaa</region>
<country>Finland</country> <code>02600</code>
</adr> <country>Finland</country>
<tel> </adr>
<parameters> <tel>
<type> <parameters>
<text>work</text> <type>
<text>voice</text> <text>work</text>
</type> <text>voice</text>
</parameters> </type>
<uri>tel:+358 50 4871445</uri> </parameters>
</tel> <uri>tel:+358 50 4871445</uri>
<email> </tel>
<parameters><type><text>work</text></type> <email>
</parameters> <parameters><type><text>work</text></type>
<text>hannes.tschofenig@nsn.com</text> </parameters>
</email> <text>hannes.tschofenig@nsn.com</text>
<geo> </email>
<parameters><type><text>work</text></type> <geo>
</parameters> <parameters><type><text>work</text></type>
<uri>geo:60.210796,24.812924</uri> </parameters>
</geo> <uri>geo:60.210796,24.812924</uri>
<key> </geo>
<parameters><type><text>home</text></type> <key>
</parameters> <parameters><type><text>home</text></type>
<uri> </parameters>
http://www.tschofenig.priv.at/key.asc <uri>
</uri> http://www.tschofenig.priv.at/key.asc
</key> </uri>
<tz><text>Finland/Helsinki</text></tz> </key>
<url> <tz><text>Finland/Helsinki</text></tz>
<parameters><type><text>home</text></type> <url>
</parameters> <parameters><type><text>home</text></type>
<uri>http://www.tschofenig.priv.at</uri> </parameters>
</url> <uri>http://www.tschofenig.priv.at</uri>
</vcard> </url>
</ad:DataProviderContact> </vcard>
</ad:EmergencyCallData.ProviderInfo> </ad:DataProviderContact>
</ad:EmergencyCallData.ProviderInfo>
Figure 2: EmergencyCallData.ProviderInfo Example. Figure 2: EmergencyCallData.ProviderInfo Example.
4.2. Service Information 4.2. Service Information
This block describes the service that the service provider provides This block describes the service that the service provider provides
to the caller. It SHOULD be included by all SPs in the path of the to the caller. It SHOULD be included by all SPs in the path of the
call. The mime subtype is "application/ call. The mime subtype is "application/
EmergencyCallData.ServiceInfo+xml". EmergencyCallData.ServiceInfo+xml".
skipping to change at page 27, line 43 skipping to change at page 27, line 43
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.
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= xmlns:sub=
"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo" "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">
<vcard> <vcard>
<fn><text>Simon Perreault</text></fn> <fn><text>Simon Perreault</text></fn>
<n> <n>
<surname>Perreault</surname> <surname>Perreault</surname>
<given>Simon</given> <given>Simon</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix>ing. jr</suffix> <suffix>ing. jr</suffix>
<suffix>M.Sc.</suffix> <suffix>M.Sc.</suffix>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>fr</language-tag> <language-tag>fr</language-tag>
</lang> </lang>
<lang> <lang>
<parameters><pref><integer>2</integer></pref> <parameters><pref><integer>2</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<org> <org>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>Viagenie</text> <text>Viagenie</text>
</org> </org>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>Simon Perreault <label><text>Simon Perreault
2875 boul. Laurier, suite D2-630 2875 boul. Laurier, suite D2-630
Quebec, QC, Canada Quebec, QC, Canada
G1V 2M2</text></label> G1V 2M2</text></label>
</parameters> </parameters>
<pobox/> <pobox/>
<ext/> <ext/>
<street>2875 boul. Laurier, suite D2-630</street> <street>2875 boul. Laurier, suite D2-630</street>
<locality>Quebec</locality> <locality>Quebec</locality>
<region>QC</region> <region>QC</region>
<code>G1V 2M2</code> <code>G1V 2M2</code>
<country>Canada</country> <country>Canada</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+1-418-656-9254;ext=102</uri> <uri>tel:+1-418-656-9254;ext=102</uri>
</tel> </tel>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>text</text> <text>text</text>
<text>voice</text> <text>voice</text>
<text>cell</text> <text>cell</text>
<text>video</text> <text>video</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+1-418-262-6501</uri> <uri>tel:+1-418-262-6501</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>simon.perreault@viagenie.ca</text> <text>simon.perreault@viagenie.ca</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri>geo:46.766336,-71.28955</uri> <uri>geo:46.766336,-71.28955</uri>
</geo> </geo>
<key> <key>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri> <uri>
http://www.viagenie.ca/simon.perreault/simon.asc http://www.viagenie.ca/simon.perreault/simon.asc
</uri> </uri>
</key> </key>
<tz><text>America/Montreal</text></tz> <tz><text>America/Montreal</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://nomis80.org</uri> <uri>http://nomis80.org</uri>
</url> </url>
</vcard> </vcard>
</sub:SubscriberData> </sub:SubscriberData>
</sub:EmergencyCallData.SubscriberInfo> </sub:EmergencyCallData.SubscriberInfo>
Figure 8: EmergencyCallData.SubscriberInfo Example. Figure 8: EmergencyCallData.SubscriberInfo Example.
4.5. Comment 4.5. Comment
This block provides a mechanism for the data provider to supply This block provides a mechanism for the data provider to supply
extra, human readable information to the PSAP. It is not intended extra, human readable information to the PSAP. It is not intended
for a general purpose extension mechanism nor does it aim to provide for a general purpose extension mechanism nor does it aim to provide
machine-readable content. The mime subtype is "application/ machine-readable content. The mime subtype is "application/
EmergencyCallData.Comment+xml" EmergencyCallData.Comment+xml"
skipping to change at page 32, line 19 skipping to change at page 32, line 19
application layer signaling (and hence cannot add a Call-Info application layer signaling (and hence cannot add a Call-Info
header field to the SIP message), but may provide location header field to the SIP message), but may provide location
information in a PIDF-LO object to assist in locating the information in a PIDF-LO object to assist in locating the
caller's device. The <provided-by> element of the PIDF-LO is a caller's device. The <provided-by> element of the PIDF-LO is a
mechanism for the access network provider to supply the mechanism for the access network provider to supply the
information about the entity or organization that supplied this information about the entity or organization that supplied this
location information. For this reason, this document describes a location information. For this reason, this document describes a
namespace per RFC 4119 for inclusion in the <provided-by> element namespace per RFC 4119 for inclusion in the <provided-by> element
of a PIDF-LO for adding information known to the access network of a PIDF-LO for adding information known to the access network
provider. The access network provider SHOULD provide additional provider. The access network provider SHOULD provide additional
data within a provided-by element of a PDIF-LO it returns for data within a <provided-by> element of a PDIF-LO it returns for
emergency use (e.g., if requested with a HELD "responseTime" emergency use (e.g., if requested with a HELD "responseTime"
attribute of "emergencyRouting" or "emergencyDispatch" attribute of "emergencyRouting" or "emergencyDispatch"
[RFC5985]). [RFC5985]).
One or more blocks of data registered in the Emergency Call One or more blocks of data registered in the Emergency Call
Additional Data registry, as defined in Section 10.1, may be included Additional Data registry, as defined in Section 10.1, may be included
or referenced in the SIP signaling (using the Call-Info header field) or referenced in the SIP signaling (using the Call-Info header field)
or in the <provided-by> element of a PIDF-LO. Every block must be or in the <provided-by> element of a PIDF-LO. Every block must be
one of the types in the registry. Since the data of an emergency one of the types in the registry. Since the data of an emergency
call may come from multiple sources, the data itself needs call may come from multiple sources, the data itself needs
information describing the source. Consequently, each entity adding information describing the source. Consequently, each entity adding
additional data MUST supply the "Data Provider" block. All other additional data MUST supply the "Data Provider" block. All other
blocks are optional, but each entity SHOULD supply any blocks where blocks are optional, but each entity SHOULD supply any blocks where
it has at least some of the information in the block. it has at least some of the information in the block.
5.1. Transmitting Blocks using the Call-Info Header 5.1. Transmitting Blocks using the Call-Info Header
A URI to a block MAY be inserted in a SIP request or response method A URI to a block MAY be inserted in any SIP request or response
(most often INVITE or MESSAGE) with a Call-Info header field method (most often INVITE or MESSAGE) with a Call-Info header field
containing a purpose value starting with 'EmergencyCallData' and the containing a purpose value starting with 'EmergencyCallData' and the
type of data available at the URI. The type of data is denoted by type of data available at the URI. The type of data is denoted by
including the root of the MIME type (not including the including the root of the MIME type (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') with a '.' 'EmergencyCallData' prefix and any suffix such as '+xml') with a '.'
separator. For example, when referencing a block with MIME type separator. For example, when referencing a block with MIME type
'application/EmergencyCallData.ProviderInfo+xml', the 'purpose' 'application/EmergencyCallData.ProviderInfo+xml', the 'purpose'
parameter is set to 'EmergencyCallData.ProviderInfo'. An example parameter is set to 'EmergencyCallData.ProviderInfo'. An example
"Call-Info" header field for this would be: "Call-Info" header field for this would be:
Call-Info: https://www.example.com/23sedde3; Call-Info: https://www.example.com/23sedde3;
skipping to change at page 33, line 14 skipping to change at page 33, line 14
A Call-info header with a purpose value starting with A Call-info header with a purpose value starting with
'EmergencyCallData' MUST only be sent on an emergency call, which can 'EmergencyCallData' MUST only be sent on an emergency call, which can
be ascertained by the presence of an emergency service urn in a Route be ascertained by the presence of an emergency service urn in a Route
header of a SIP message. header of a SIP message.
If the data is provided by reference, an HTTPS URI MUST be included If the data is provided by reference, an HTTPS URI MUST be included
and consequently Transport Layer Security (TLS) protection is applied and consequently Transport Layer Security (TLS) protection is applied
for protecting the retrieval of the information. for protecting the retrieval of the information.
The data may also be supplied by value in a SIP message. In this The data may also be supplied by value in any SIP request or response
case, Content Indirection (CID) [RFC2392] is used, with the CID URL method that is permitted to contain a body (i.e., not a BYE request).
referencing the MIME body part. In this case, Content Indirection (CID) [RFC2392] is used, with the
CID URL referencing the MIME body part containing the data.
Transmitting data by value is especially useful in certain cases,
such as when the data exists in or is generated by the originating
device, but is not intended for very large data blocks. Additional
security and privacy considerations apply to data transmitted by
value, as discussed in Section 8 and Section 9.
More than one Call-Info header with a purpose value starting with More than one Call-Info header with a purpose value starting with
'EmergencyCallData' can be expected, but at least one MUST be 'EmergencyCallData' can be expected, but at least one MUST be
provided. The device MUST provide one if it knows no service provided. The device MUST provide one if it knows no service
provider is in the path of the call. The device MAY insert one if it provider is in the path of the call. The device MAY insert one if it
uses a service provider. Any service provider in the path of the uses a service provider. Any service provider in the path of the
call MUST insert its own. For example, a device, a telematics call MUST insert its own. For example, a device, a telematics
service provider in the call path, as well as the mobile carrier service provider in the call path, as well as the mobile carrier
handling the call will each provide one. There may be circumstances handling the call will each provide one. There may be circumstances
where there is a service provider who is unaware that the call is an where there is a service provider who is unaware that the call is an
emergency call and cannot reasonably be expected to determine that it emergency call and cannot reasonably be expected to determine that it
is an emergency call. In that case, that service provider is not is an emergency call. In that case, that service provider is not
expected to provide EmergencyCallData. expected to provide EmergencyCallData.
5.2. Transmitting Blocks by Reference using the provided-by Element 5.2. Transmitting Blocks by Reference using the provided-by Element
The 'EmergencyCallDataReference' element is used to transmit an The <EmergencyCallDataReference> element is used to transmit an
additional data block by reference within a 'provided-by' element of additional data block by reference within a <provided-by> element of
a PIDF-LO. The 'EmergencyCallDataReference' element has two a PIDF-LO. The <EmergencyCallDataReference> element has two
attributes: 'ref' to specify the URL, and 'purpose' to indicate the attributes: 'ref' to specify the URL, and 'purpose' to indicate the
type of data block referenced. The value of 'ref' is an HTTPS URL type of data block referenced. The value of 'ref' is an HTTPS URL
that resolves to a data structure with information about the call. that resolves to a data structure with information about the call.
The value of 'purpose' is the same as used in a 'Call-Info' header The value of 'purpose' is the same as used in a 'Call-Info' header
field (as specified in Section 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 The 'EmergencyCallDataReference' element transmits one additional
data block; multiple additional data blocks may be transmitted by data block; multiple additional data blocks may be transmitted by
using multiple 'EmergencyCallDataReference' elements. using multiple 'EmergencyCallDataReference' elements.
For example: For example:
<gp:provided-by <?xml version="1.0" encoding="UTF-8"?>
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> <gp:provided-by
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<ad:EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.ServiceInfo" purpose="EmergencyCallData.ServiceInfo"
ref="https://example.com/ref2" /> ref="https://example.com/ref2" />
<ad:EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.ProviderInfo" purpose="EmergencyCallData.ProviderInfo"
ref="https://example.com/ref3" /> ref="https://example.com/ref3" />
<ad:EmergencyCallDataReference <EmergencyCallDataReference
purpose="EmergencyCallData.Comment" purpose="EmergencyCallData.Comment"
ref="https://example.com/ref4" /> ref="https://example.com/ref4" />
</gp:provided-by> </gp:provided-by>
Example provided-by by Reference. 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 one or more The <EmergencyCallDataValue> element is used to transmit one or more
additional data blocks by value within a 'provided-by' element of a additional data blocks by value within a <provided-by> element of a
PIDF-LO. Each block being transmitted is placed (as a child element) PIDF-LO. Each block being transmitted is placed (as a child element)
inside the 'EmergencyCallDataValue' element. (The same XML structure inside the <EmergencyCallDataValue> element. (The same XML structure
as would be contained in the corresponding MIME type body part is as would be contained in the corresponding MIME type body part is
placed inside the 'EmergencyCallDataValue' element.) placed inside the <EmergencyCallDataValue> element.)
For example: For example:
<gp:provided-by <?xml version="1.0" encoding="UTF-8"?>
xmlns="urn:ietf:params:xml:ns:EmergencyCallData"> <gp:provided-by
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<EmergencyCallDataValue> <EmergencyCallDataValue>
<EmergencyCallData.ProviderInfo <EmergencyCallData.ProviderInfo
xmlns= xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>flurbit735@es.example.com <DataProviderReference>flurbit735@es.example.com
</DataProviderReference> </DataProviderReference>
<DataProviderString>Access Network Examples, Inc <DataProviderString>Access Network Examples, Inc
</DataProviderString> </DataProviderString>
<ProviderID>urn:nena:companyid:Test</ProviderID> <ProviderID>urn:nena:companyid:Test</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries> <ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Access Network Provider <TypeOfProvider>Access Network Provider
</TypeOfProvider> </TypeOfProvider>
<ContactURI>tel:+1-555-555-0897</ContactURI> <ContactURI>tel:+1-555-555-0897</ContactURI>
<Language>EN</Language> <Language>en</Language>
</EmergencyCallData.ProviderInfo> </EmergencyCallData.ProviderInfo>
<EmergencyCallData.Comment <EmergencyCallData.Comment
xmlns= xmlns=
"urn:ietf:params:xml:ns:EmergencyCallData:Comment"> "urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<DataProviderReference>flurbit735@es.example.com <DataProviderReference>flurbit735@es.example.com
</DataProviderReference> </DataProviderReference>
<Comment xml:lang="en">This is an example text. <Comment xml:lang="en">This is an example text.
</Comment> </Comment>
</EmergencyCallData.Comment> </EmergencyCallData.Comment>
</EmergencyCallDataValue> </EmergencyCallDataValue>
</gp:provided-by> </gp: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'
MIME bodies are used by many extensions (including this document) MIME bodies are used by many extensions (including this document)
skipping to change at page 37, line 40 skipping to change at page 37, line 42
... 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> Call-Info: <http://wwww.example.com/hannes/photo.jpg>
;purpose=icon, ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo, ;purpose=EmergencyCallData.ProviderInfo,
<cid:0123456789@atlanta.example.com>
<cid:0123456789@atlanta.example.com> ;purpose=EmergencyCallData.DeviceInfo
;purpose=EmergencyCallData.DeviceInfo Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation-Routing: yes
Geolocation-Routing: yes Accept: application/sdp, application/pidf+xml,
Accept: application/sdp, application/pidf+xml, application/EmergencyCallData.ProviderInfo+xml
application/EmergencyCallData.ProviderInfo+xml CSeq: 31862 INVITE
CSeq: 31862 INVITE Contact: <sips:hannes@example.com>
Contact: <sips:hannes@example.com> Content-Type: multipart/mixed; boundary=boundary1
Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...SDP goes here ...SDP goes here
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.DeviceInfo+xml Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-ID: <0123456789@atlanta.example.com> Content-ID: <0123456789@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<dev:EmergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119] <dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:DeviceClassification>laptop</dev:DeviceClassification> <dev:DeviceClassification>laptop</dev:DeviceClassification>
<dev:UniqueDeviceID <dev:UniqueDeviceID
TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119] <pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</pi:DataProviderReference> </pi:DataProviderReference>
<pi:DataProviderString>Hannes Tschofenig <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString> </pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>en</pi:Language>
<xc:DataProviderContact <pi:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix>Dipl. Ing.</suffix> <suffix>Dipl. Ing.</suffix>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>de</language-tag> <language-tag>de</language-tag>
</lang> </lang>
<lang> <lang>
<parameters><pref><integer>2</integer></pref> <parameters><pref><integer>2</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>Hannes Tschofenig <label><text>Hannes Tschofenig
Linnoitustie 6 Linnoitustie 6
Espoo, Finland Espoo, Finland
02600</text></label> 02600</text></label>
</parameters> </parameters>
<pobox/> <pobox/>
<ext/> <ext/>
<street>Linnoitustie 6</street> <street>Linnoitustie 6</street>
<locality>Espoo</locality> <locality>Espoo</locality>
<region>Uusimaa</region> <region>Uusimaa</region>
<code>02600</code> <code>02600</code>
<country>Finland</country> <country>Finland</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+358 50 4871445</uri> <uri>tel:+358 50 4871445</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>hannes.tschofenig@nsn.com</text> <text>hannes.tschofenig@nsn.com</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri>geo:60.210796,24.812924</uri> <uri>geo:60.210796,24.812924</uri>
</geo> </geo>
<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>http://example.com/hannes.tschofenig
</uri> </uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </pi: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
the location reference. The PSAP has to retrieve it via a separate the location reference. The PSAP has to retrieve it via a separate
look-up step. Since the access network provider and the VoIP service look-up step. Since the access network provider and the VoIP service
provider are two independent entities in this scenario, the access provider are two independent entities in this scenario, the access
network provider is not involved in application layer exchanges; the network provider is not involved in application layer exchanges; the
SIP INVITE transits the access network transparently, as illustrated SIP INVITE transits the access network transparently, as illustrated
skipping to change at page 41, line 17 skipping to change at page 41, line 21
It performs typical emergency services related tasks, including It performs typical emergency services related tasks, including
location-based routing, and adds additional data, namely service and location-based routing, and adds additional data, namely service and
subscriber information as well as data provider information #2, to subscriber information as well as data provider information #2, to
the outgoing message. For the example we assume a VoIP service the outgoing message. For the example we assume a VoIP service
provider that deploys a back-to-back user agent allowing additional provider that deploys a back-to-back user agent allowing additional
data to be included in the body of the SIP message (rather than per data to be included in the body of the SIP message (rather than per
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> Call-Info: <http://wwww.example.com/hannes/photo.jpg>
;purpose=icon, ;purpose=icon,
<http://www.example.com/hannes/> ;purpose=info, <http://www.example.com/hannes/> ;purpose=info,
<cid:1234567890@atlanta.example.com> <cid:1234567890@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo ;purpose=EmergencyCallData.ProviderInfo
<cid:0123456789@atlanta.example.com> <cid:0123456789@atlanta.example.com>
;purpose=EmergencyCallData.DeviceInfo ;purpose=EmergencyCallData.DeviceInfo
Call-Info: <cid:bloorpyhex@atlanta.example.com> Call-Info: <cid:bloorpyhex@atlanta.example.com>
;purpose=EmergencyCallData.ServiceInfo ;purpose=EmergencyCallData.ServiceInfo
Call-Info: <cid:aaabbb@atlanta.example.com> Call-Info: <cid:aaabbb@atlanta.example.com>
;purpose=EmergencyCallData.ProviderInfo ;purpose=EmergencyCallData.ProviderInfo
Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o> Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
Geolocation-Routing: yes Geolocation-Routing: yes
Accept: application/sdp, application/pidf+xml, Accept: application/sdp, application/pidf+xml,
application/EmergencyCallData.ProviderInfo+xml application/EmergencyCallData.ProviderInfo+xml
CSeq: 31862 INVITE CSeq: 31862 INVITE
Contact: <sips:hannes@example.com> Contact: <sips:hannes@example.com>
Content-Type: multipart/mixed; boundary=boundary1 Content-Type: multipart/mixed; boundary=boundary1
Content-Length: ... Content-Length: ...
--boundary1 --boundary1
Content-Type: application/sdp Content-Type: application/sdp
...SDP goes here
...SDP goes here --boundary1--
--boundary1-- Content-Type: application/EmergencyCallData.DeviceInfo+xml
Content-Type: application/EmergencyCallData.DeviceInfo+xml Content-ID: <0123456789@atlanta.example.com>
Content-ID: <0123456789@atlanta.example.com> Content-Disposition: by-reference;handling=optional
Content-Disposition: by-reference;handling=optional <?xml version="1.0" encoding="UTF-8"?>
<?xml version="1.0" encoding="UTF-8"?>
<dev:EmergencyCallData.DeviceInfo <dev:EmergencyCallData.DeviceInfo
xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo" xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119] <dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</dev:DataProviderReference> </dev:DataProviderReference>
<dev:DeviceClassification>laptop</dev:DeviceClassification> <dev:DeviceClassification>laptop</dev:DeviceClassification>
<dev:UniqueDeviceID <dev:UniqueDeviceID
TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID> TypeOfDeviceID="MAC">00-0d-4b-30-72-df</dev:UniqueDeviceID>
</dev:EmergencyCallData.DeviceInfo> </dev:EmergencyCallData.DeviceInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <1234567890@atlanta.example.com> Content-ID: <1234567890@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119] <pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
</pi:DataProviderReference> </pi:DataProviderReference>
<pi:DataProviderString>Hannes Tschofenig <pi:DataProviderString>Hannes Tschofenig
</pi:DataProviderString> </pi:DataProviderString>
<pi:TypeOfProvider>Other</pi:TypeOfProvider> <pi:TypeOfProvider>Other</pi:TypeOfProvider>
<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI> <pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>en</pi:Language>
<xc:DataProviderContact <pi:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>Hannes Tschofenig</text></fn> <fn><text>Hannes Tschofenig</text></fn>
<n> <n>
<surname>Hannes</surname> <surname>Hannes</surname>
<given>Tschofenig</given> <given>Tschofenig</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix>Dipl. Ing.</suffix> <suffix>Dipl. Ing.</suffix>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>de</language-tag> <language-tag>de</language-tag>
</lang> </lang>
<lang> <lang>
<parameters><pref><integer>2</integer></pref> <parameters><pref><integer>2</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>Hannes Tschofenig <label><text>Hannes Tschofenig
Linnoitustie 6 Linnoitustie 6
Espoo, Finland Espoo, Finland
02600</text></label> 02600</text></label>
</parameters> </parameters>
<pobox/> <pobox/>
<ext/> <ext/>
<street>Linnoitustie 6</street> <street>Linnoitustie 6</street>
<locality>Espoo</locality> <locality>Espoo</locality>
<region>Uusimaa</region> <region>Uusimaa</region>
<code>02600</code> <code>02600</code>
<country>Finland</country> <country>Finland</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>tel:+358 50 4871445</uri> <uri>tel:+358 50 4871445</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>hannes.tschofenig@nsn.com</text> <text>hannes.tschofenig@nsn.com</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri>geo:60.210796,24.812924</uri> <uri>geo:60.210796,24.812924</uri>
</geo> </geo>
<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>http://example.com/hannes.tschofenig
</uri> </uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </pi: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
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<svc:EmergencyCallData.ServiceInfo <svc:EmergencyCallData.ServiceInfo
xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo" xmlns:svc="urn:ietf:params:xml:ns:EmergencyCallData:ServiceInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<svc:DataProviderReference>string0987654321@example.org <svc:DataProviderReference>string0987654321@example.org
</svc:DataProviderReference> </svc:DataProviderReference>
<svc:ServiceEnvironment>Residence</svc:ServiceEnvironment> <svc:ServiceEnvironment>Residence</svc:ServiceEnvironment>
<svc:ServiceType>VOIP</svc:ServiceType> <svc:ServiceType>VOIP</svc:ServiceType>
<svc:ServiceMobility>Unknown</svc:ServiceMobility> <svc:ServiceMobility>Unknown</svc:ServiceMobility>
</svc:EmergencyCallData.ServiceInfo> </svc:EmergencyCallData.ServiceInfo>
--boundary1-- --boundary1--
Content-Type: application/EmergencyCallData.ProviderInfo+xml Content-Type: application/EmergencyCallData.ProviderInfo+xml
Content-ID: <aaabbb@atlanta.example.com> Content-ID: <aaabbb@atlanta.example.com>
Content-Disposition: by-reference;handling=optional Content-Disposition: by-reference;handling=optional
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<pi:EmergencyCallData.ProviderInfo <pi:EmergencyCallData.ProviderInfo
xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo" xmlns:pi="urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<pi:DataProviderReference>string0987654321@example.org <pi:DataProviderReference>string0987654321@example.org
</pi:DataProviderReference> </pi:DataProviderReference>
<pi:DataProviderString>Example VoIP Provider <pi:DataProviderString>Example VoIP Provider
</pi:DataProviderString> </pi:DataProviderString>
<pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID> <pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID>
<pi:ProviderIDSeries>NENA</pi:ProviderIDSeries> <pi:ProviderIDSeries>NENA</pi:ProviderIDSeries>
<pi:TypeOfProvider>Service Provider</pi:TypeOfProvider> <pi:TypeOfProvider>Service Provider</pi:TypeOfProvider>
<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI> <pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI>
<pi:Language>EN</pi:Language> <pi:Language>en</pi:Language>
<xc:DataProviderContact <pi:DataProviderContact
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
<vcard> <vcard>
<fn><text>John Doe</text></fn> <fn><text>John Doe</text></fn>
<n> <n>
<surname>John</surname> <surname>John</surname>
<given>Doe</given> <given>Doe</given>
<additional/> <additional/>
<prefix/> <prefix/>
<suffix/> <suffix/>
</n> </n>
<bday><date>--0203</date></bday> <bday><date>--0203</date></bday>
<anniversary> <anniversary>
<date-time>20090808T1430-0500</date-time> <date-time>20090808T1430-0500</date-time>
</anniversary> </anniversary>
<gender><sex>M</sex></gender> <gender><sex>M</sex></gender>
<lang> <lang>
<parameters><pref><integer>1</integer></pref> <parameters><pref><integer>1</integer></pref>
</parameters> </parameters>
<language-tag>en</language-tag> <language-tag>en</language-tag>
</lang> </lang>
<org> <org>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>Example VoIP Provider</text> <text>Example VoIP Provider</text>
</org> </org>
<adr> <adr>
<parameters> <parameters>
<type><text>work</text></type> <type><text>work</text></type>
<label><text>John Doe <label><text>John Doe
Downing Street 10 Downing Street 10
London, UK</text></label> London, UK</text></label>
</parameters> </parameters>
<pobox/> <pobox/>
<ext/> <ext/>
<street>Downing Street 10</street> <street>Downing Street 10</street>
<locality>London</locality> <locality>London</locality>
<region/> <region/>
<code>SW1A 2AA</code> <code>SW1A 2AA</code>
<country>UK</country> <country>UK</country>
</adr> </adr>
<tel> <tel>
<parameters> <parameters>
<type> <type>
<text>work</text> <text>work</text>
<text>voice</text> <text>voice</text>
</type> </type>
</parameters> </parameters>
<uri>sips:john.doe@example.com</uri> <uri>sips:john.doe@example.com</uri>
</tel> </tel>
<email> <email>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<text>john.doe@example.com</text> <text>john.doe@example.com</text>
</email> </email>
<geo> <geo>
<parameters><type><text>work</text></type> <parameters><type><text>work</text></type>
</parameters> </parameters>
<uri>geo:51.503396, 0.127640</uri> <uri>geo:51.503396, 0.127640</uri>
</geo> </geo>
<tz><text>Europe/London</text></tz> <tz><text>Europe/London</text></tz>
<url> <url>
<parameters><type><text>home</text></type> <parameters><type><text>home</text></type>
</parameters> </parameters>
<uri>http://www.example.com/john.doe</uri> <uri>http://www.example.com/john.doe</uri>
</url> </url>
</vcard> </vcard>
</xc:DataProviderContact> </pi:DataProviderContact>
</pi:EmergencyCallData.ProviderInfo> </pi:EmergencyCallData.ProviderInfo>
Figure 13: VoIP Provider sending SIP INVITE with Additional Data. Figure 13: VoIP Provider sending SIP INVITE with Additional Data.
Finally, the PSAP requests location information from the access Finally, the PSAP requests location information from the access
network provider. The response is shown in Figure 14. Along with network provider. The response is shown in Figure 14. Along with
the location information, additional data is provided in the the location information, additional data is provided in the
<provided-by> element of the PIDF-LO. This request and response is <provided-by> element of the PIDF-LO. This request and response is
step #4. step #4.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy" xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
entity="pres:alice@atlanta.example.com"> entity="pres:alice@atlanta.example.com">
<dm:device id="target123-1"> <dm:device id="target123-1">
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<civicAddress <civicAddress
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>AU</country> <country>AU</country>
<A1>NSW</A1> <A1>NSW</A1>
<A3>Wollongong</A3> <A3>Wollongong</A3>
<A4>North Wollongong</A4> <A4>North Wollongong</A4>
<RD>Flinders</RD> <RD>Flinders</RD>
<STS>Street</STS> <STS>Street</STS>
<RDBR>Campbell Street</RDBR> <RDBR>Campbell Street</RDBR>
<LMK>Gilligan's Island</LMK> <LMK>Gilligan's Island</LMK>
<LOC>Corner</LOC> <LOC>Corner</LOC>
<NAM>Video Rental Store</NAM> <NAM>Video Rental Store</NAM>
<PC>2500</PC> <PC>2500</PC>
<ROOM>Westerns and Classics</ROOM> <ROOM>Westerns and Classics</ROOM>
<PLC>store</PLC> <PLC>store</PLC>
<POBOX>Private Box 15</POBOX> <POBOX>Private Box 15</POBOX>
</civicAddress> </civicAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules> <gp:usage-rules>
<gbp:retransmission-allowed>true <gbp:retransmission-allowed>true
</gbp:retransmission-allowed> </gbp:retransmission-allowed>
<gbp:retention-expiry>2013-12-10T20:00:00Z <gbp:retention-expiry>2013-12-10T20:00:00Z
</gbp:retention-expiry> </gbp:retention-expiry>
</gp:usage-rules> </gp:usage-rules>
<gp:method>802.11</gp:method> <gp:method>802.11</gp:method>
<gp:provided-by
xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
<EmergencyCallDataReference <gp:provided-by
purpose="EmergencyCallData.ServiceInfo" xmlns="urn:ietf:params:xml:ns:EmergencyCallData">
ref="https://example.com/ref2"/>
<EmergencyCallDataValue> <EmergencyCallDataReference
<EmergencyCallData.ProviderInfo purpose="EmergencyCallData.ServiceInfo"
xmlns= ref="https://example.com/ref2"/>
"urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference>
<DataProviderString>University of Example
</DataProviderString>
<ProviderID>urn:nena:companyid:uoi</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Other</TypeOfProvider>
<ContactURI>tel:+1-555-824-5222</ContactURI>
<Language>EN</Language>
</EmergencyCallData.ProviderInfo>
<EmergencyCallData.Comment <EmergencyCallDataValue>
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment"> <EmergencyCallData.ProviderInfo
<DataProviderReference>88QV4FpfZ976T@example.com xmlns=
</DataProviderReference> "urn:ietf:params:xml:ns:EmergencyCallData:ProviderInfo">
<Comment xml:lang="en">This is an example text.</Comment> <DataProviderReference>88QV4FpfZ976T@example.com
</EmergencyCallData.Comment> </DataProviderReference>
<DataProviderString>University of Example
</DataProviderString>
<ProviderID>urn:nena:companyid:uoi</ProviderID>
<ProviderIDSeries>NENA</ProviderIDSeries>
<TypeOfProvider>Other</TypeOfProvider>
<ContactURI>tel:+1-555-824-5222</ContactURI>
<Language>en</Language>
</EmergencyCallData.ProviderInfo>
</EmergencyCallDataValue> <EmergencyCallData.Comment
xmlns="urn:ietf:params:xml:ns:EmergencyCallData:Comment">
<DataProviderReference>88QV4FpfZ976T@example.com
</DataProviderReference>
<Comment xml:lang="en">This is an example text.</Comment>
</EmergencyCallData.Comment>
</gp:provided-by> </EmergencyCallDataValue>
</gp:geopriv> </gp:provided-by>
<dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID> </gp:geopriv>
<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp> <dm:deviceID>mac:00-0d-4b-30-72-df</dm:deviceID>
</dm:device> <dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>
</presence> </dm:device>
</presence>
Figure 14: Access Network Provider returning PIDF-LO with Additional Figure 14: Access Network Provider returning PIDF-LO with Additional
Data. Data.
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
skipping to change at page 48, line 38 skipping to change at page 48, line 41
xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:xml="http://www.w3.org/XML/1998/namespace"
xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/> schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"> <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0">
<xs:simpleType name="iso3166a2">
<xs:restriction base="xs:token">
<xs:pattern value="[A-Z]{2}"/>
</xs:restriction>
</xs:simpleType>
<xs:element <xs:element
name="EmergencyCallData.ProviderInfo" name="EmergencyCallData.ProviderInfo"
type="pi:ProviderInfoType"/> type="pi:ProviderInfoType"
minOccurs="0" maxOccurs="1"/>
<xs:simpleType name="SubcontractorPriorityType"> <xs:simpleType name="SubcontractorPriorityType">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="sub"/> <xs:enumeration value="sub"/>
<xs:enumeration value="main"/> <xs:enumeration value="main"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="ProviderInfoType"> <xs:complexType name="ProviderInfoType">
<xs:sequence> <xs:sequence>
<xs:element name="DataProviderReference" <xs:element name="DataProviderReference"
type="xs:token" minOccurs="1" maxOccurs="1"/> type="xs:token" minOccurs="1" maxOccurs="1"/>
<xs:element name="DataProviderString" <xs:element name="DataProviderString"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ProviderID" <xs:element name="ProviderID"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="ProviderIDSeries" <xs:element name="ProviderIDSeries"
type="xs:string" minOccurs="1" maxOccurs="1"/> type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="TypeOfProvider" <xs:element name="TypeOfProvider"
type="xs:string" minOccurs="0" maxOccurs="1"/> type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="ContactURI" type="xs:anyURI" <xs:element name="ContactURI" type="xs:anyURI"
minOccurs="1" maxOccurs="1"/> minOccurs="1" maxOccurs="1"/>
<xs:element name="Language" type="pi:iso3166a2" <xs:element name="Language" minOccurs="1" maxOccurs="unbounded">
minOccurs="1" maxOccurs="unbounded" /> <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>
<xs:element name="DataProviderContact"> <xs:element name="DataProviderContact"
minOccurs="0" maxOccurs="1">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element minOccurs="0" <xs:element minOccurs="0"
maxOccurs="unbounded" ref="xc:vcard"/> maxOccurs="unbounded" ref="xc:vcard"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:element name="SubcontractorPrincipal" <xs:element name="SubcontractorPrincipal"
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" type="pi:SubcontractorPriorityType"
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>
skipping to change at page 50, line 33 skipping to change at page 51, line 26
<xs:element name="EmergencyCallData.ServiceInfo" <xs:element name="EmergencyCallData.ServiceInfo"
type="svc:ServiceInfoType"/> 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="0" maxOccurs="1"/>
<xs:element name="ServiceType" <xs:element name="ServiceType"
type="xs:string" minOccurs="1" type="xs:string" minOccurs="1"
maxOccurs="unbounded"/> 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"/>
skipping to change at page 62, line 18 skipping to change at page 63, line 18
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 s[RFC4119]hort 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 63, line 23 skipping to change at page 64, 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
skipping to change at page 65, line 49 skipping to change at page 66, line 49
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 registry contains an entry for every data block that can be sent
with an emergency call using the mechanisms as specified in this
document. Each data block is identified by the "root" of its MIME
subtype (which is the part after 'EmergencyCallData.'). If the MIME
subtype does not start with 'EmergencyCallData.' then it cannot be
registered here nor used in a Call-Info header as specified in this
document. The subtype MAY exist under any MIME type (although most
commonly these are under 'Application/' this is NOT REQUIRED).
The content of this registry includes: The content of this registry includes:
Token: The root of the data's MIME subtype (not including the Token: The root of the data's MIME subtype (not including the
'EmergencyCallData' prefix and any suffix such as '+xml') 'EmergencyCallData' prefix and any suffix such as '+xml')
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
skipping to change at page 67, line 5 skipping to change at page 68, line 16
Field Name Value Reference Field Name Value Reference
---------- --------- ----------------- --------- ---------- --------- ----------------- ---------
Call-Info purpose EmergencyCallData [This RFC] Call-Info purpose EmergencyCallData [This RFC]
10.3. URN Sub-Namespace Registration for provided-by Registry Entry 10.3. URN Sub-Namespace Registration for provided-by Registry Entry
This section registers the namespace specified in Section 10.5.1 in This section registers the namespace specified in Section 10.5.1 in
the provided-by registry established by RFC 4119, for usage within the provided-by registry established by RFC 4119, for usage within
the <provided-by> element of a PIDF-LO. the <provided-by> element of a PIDF-LO.
The schema for the provided-by element used by this document is The schema for the <provided-by> element used by this document is
specified in Section 7.6. specified in Section 7.6.
10.4. MIME Registrations 10.4. MIME Registrations
10.4.1. MIME Content-type Registration for 'application/ 10.4.1. MIME Content-type Registration for 'application/
EmergencyCallData.ProviderInfo+xml' EmergencyCallData.ProviderInfo+xml'
This specification requests the registration of a new MIME type This specification requests the registration of a new MIME type
according to the procedures of RFC 6838 [RFC6838] and guidelines in according to the procedures of RFC 6838 [RFC6838] and guidelines in
RFC 7303 [RFC7303]. RFC 7303 [RFC7303].
skipping to change at page 80, line 43 skipping to change at page 81, line 43
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008. October 2008.
[RFC5621] Camarillo, G., "Message Body Handling in the Session [RFC5621] Camarillo, G., "Message Body Handling in the Session
Initiation Protocol (SIP)", RFC 5621, September 2009. Initiation Protocol (SIP)", RFC 5621, September 2009.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009.
[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350, [RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
August 2011. August 2011.
[RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC [RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC
6351, August 2011. 6351, August 2011.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013. 6838, 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-slim-negotiating-human-language] [I-D.gellens-slim-negotiating-human-language]
Gellens, R., "Negotiating Human Language in Real-Time Randy, R., "Negotiating Human Language in Real-Time
Communications", draft-gellens-slim-negotiating-human- Communications", draft-gellens-slim-negotiating-human-
language (work in progress), October 2014. language-00 (work in progress), October 2014.
[LanguageTagRegistry]
IANA, "Language Subtag Registry", Feb 2015.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325, Asserted Identity within Trusted Networks", RFC 3325,
November 2002. November 2002.
[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat, [RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
"Indicating User Agent Capabilities in the Session "Indicating User Agent Capabilities in the Session
Initiation Protocol (SIP)", RFC 3840, August 2004. Initiation Protocol (SIP)", RFC 3840, August 2004.
skipping to change at page 83, line 4 skipping to change at page 84, line 11
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"
elementFormDefault="qualified" elementFormDefault="qualified"
targetNamespace="urn:ietf:params:xml:ns:vcard-4.0" targetNamespace="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:ns1="urn:ietf:params:xml:ns:vcard-4.0"> xmlns:ns1="urn:ietf:params:xml:ns:vcard-4.0">
<!-- <!--
3.3 3.3
iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" } iana-token = xsd:string { pattern = "[a-zA-Z0-9-]+" }
x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" } x-name = xsd:string { pattern = "x-[a-zA-Z0-9-]+" }
--> -->
<xs:simpleType name="iana-token"> <xs:simpleType name="iana-token">
<xs:annotation> <xs:annotation>
<xs:documentation>vCard Format Specification <xs:documentation>vCard Format Specification
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
<xs:restriction base="xs:string"/> <xs:restriction base="xs:string"/>
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="x-name"> <xs:simpleType name="x-name">
<xs:restriction base="xs:string"/> <xs:restriction base="xs:string"/>
</xs:simpleType> </xs:simpleType>
<!-- <!--
4.1 4.1
--> -->
skipping to change at page 83, line 36 skipping to change at page 84, line 44
</xs:sequence> </xs:sequence>
</xs:group> </xs:group>
<!-- 4.2 --> <!-- 4.2 -->
<xs:element name="uri" type="xs:anyURI"/> <xs:element name="uri" type="xs:anyURI"/>
<!-- 4.3.1 --> <!-- 4.3.1 -->
<xs:element name="date" <xs:element name="date"
substitutionGroup="ns1:value-date-and-or-time"> substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="\d{8}|\d{4}-\d\d| <xs:pattern value="\d{8}|\d{4}-\d\d|
--\d\d(\d\d)?|---\d\d"/> --\d\d(\d\d)?|---\d\d"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:element> </xs:element>
<!-- 4.3.2 --> <!-- 4.3.2 -->
<xs:element name="time" <xs:element name="time"
substitutionGroup="ns1:value-date-and-or-time"> substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d) <xs:pattern value="(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)
(Z|[+\-]\d\d(\d\d)?)?"/> (Z|[+\-]\d\d(\d\d)?)?"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:element> </xs:element>
<!-- 4.3.3 --> <!-- 4.3.3 -->
<xs:element name="date-time" <xs:element name="date-time"
substitutionGroup="ns1:value-date-and-or-time"> substitutionGroup="ns1:value-date-and-or-time">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value= <xs:pattern value=
"(\d{8}|--\d{4}|---\d\d)T "(\d{8}|--\d{4}|---\d\d)T
\d\d(\d\d(\d\d)?)?(Z|[+\-]\d\d(\d\d)?)?"/> \d\d(\d\d(\d\d)?)?(Z|[+\-]\d\d(\d\d)?)?"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:element> </xs:element>
<!-- 4.3.4 --> <!-- 4.3.4 -->
<xs:element name="value-date-and-or-time" abstract="true"/> <xs:element name="value-date-and-or-time" abstract="true"/>
<!-- 4.3.5 --> <!-- 4.3.5 -->
<xs:complexType name="value-timestamp"> <xs:complexType name="value-timestamp">
<xs:sequence> <xs:sequence>
<xs:element ref="ns1:timestamp"/> <xs:element ref="ns1:timestamp"/>
</xs:sequence> </xs:sequence>
skipping to change at page 84, line 47 skipping to change at page 86, line 6
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="[+\-]\d\d(\d\d)?"/> <xs:pattern value="[+\-]\d\d(\d\d)?"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:element> </xs:element>
<!-- 4.8 --> <!-- 4.8 -->
<xs:element name="language-tag"> <xs:element name="language-tag">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern <xs:pattern
value="([a-z]{2,3}((-[a-z]{3}){0,3})?|[a-z]{4,8}) 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}| (-[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})+)* \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} (-x(-[0-9a-z]{1,8})+)?|x(-[0-9a-z]{1,8})+|[a-z]{1,3}
(-[0-9a-z]{2,8}){1,2}"/> (-[0-9a-z]{2,8}){1,2}"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:element> </xs:element>
<!-- <!--
5.1 5.1
--> -->
<xs:group name="param-language"> <xs:group name="param-language">
<xs:annotation> <xs:annotation>
<xs:documentation>Section 5: Parameters</xs:documentation> <xs:documentation>Section 5: Parameters</xs:documentation>
skipping to change at page 104, line 46 skipping to change at page 106, line 5
</xs:restriction> </xs:restriction>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<xs:element name="vcard" type="ns1:vcardType"/> <xs:element name="vcard" type="ns1:vcardType"/>
<xs:element name="group"> <xs:element name="group">
<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 Randall Gellens
Qualcomm Technologies, Inc. Qualcomm Technologies, Inc.
5775 Morehouse Drive 5775 Morehouse Drive
 End of changes. 91 change blocks. 
762 lines changed or deleted 795 lines changed or added

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