< draft-ietf-ecrit-additional-data-16.txt		draft-ietf-ecrit-additional-data-17.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft NeuStar		Internet-Draft NeuStar
	Intended status: Standards Track H. Tschofenig		Intended status: Standards Track H. Tschofenig
	Expires: July 20, 2014 Nokia Solutions and Networks		Expires: July 26, 2014 Nokia Solutions and Networks
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	R. Gellens		R. Gellens
	Qualcomm Technologies, Inc.		Qualcomm Technologies, Inc.
	J. Winterbottom		J. Winterbottom
	January 16, 2014		January 22, 2014
	Additional Data related to an Emergency Call		Additional Data related to an Emergency Call
	draft-ietf-ecrit-additional-data-16.txt		draft-ietf-ecrit-additional-data-17.txt
	Abstract		Abstract
	When an emergency call is sent to a Public Safety Answering Point		When an emergency call is sent to a Public Safety Answering Point
	(PSAP), the device that sends it, as well as any application service		(PSAP), the device that sends it, as well as any application service
	provider in the path of the call, or access network provider through		provider in the path of the call, or access network provider through
	which the call originated may have information about the call, the		which the call originated may have information about the call, the
	caller or the location which the PSAP may be able to use. This		caller or the location which the PSAP may be able to use. This
	document describes data structures and a mechanism to convey such		document describes data structures and a mechanism to convey such
	data to the PSAP. The mechanism uses a Uniform Resource Identifier		data to the PSAP. The mechanism uses a Uniform Resource Identifier
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on July 20, 2014.		This Internet-Draft will expire on July 26, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 29 ¶		skipping to change at page 2, line 29 ¶
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6		3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Data Provider Information . . . . . . . . . . . . . . . . 7		3.1. Data Provider Information . . . . . . . . . . . . . . . . 7
	3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8		3.1.1. Data Provider String . . . . . . . . . . . . . . . . 8
	3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8		3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8
	3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 9		3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8
	3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9		3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9
	3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10		3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 10
	3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10		3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10
	3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11		3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 11
	3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 12		3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 11
	3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12		3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12
	3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 12		3.1.10. ProviderInfo Example . . . . . . . . . . . . . . . . 12
	3.2. Service Information . . . . . . . . . . . . . . . . . . . 15		3.2. Service Information . . . . . . . . . . . . . . . . . . . 14
	3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15		3.2.1. Service Environment . . . . . . . . . . . . . . . . . 15
	3.2.2. Service Delivered by Provider to End User . . . . . . 15		3.2.2. Service Delivered by Provider to End User . . . . . . 15
	3.2.3. Service Mobility Environment . . . . . . . . . . . . 17		3.2.3. Service Mobility Environment . . . . . . . . . . . . 17
	3.2.4. emergencyCallData.SvcInfo Example . . . . . . . . . . 17		3.2.4. emergencyCallData.ServiceInfo Example . . . . . . . . 17
	3.3. Device Information . . . . . . . . . . . . . . . . . . . 18		3.3. Device Information . . . . . . . . . . . . . . . . . . . 17
	3.3.1. Device Classification . . . . . . . . . . . . . . . . 18		3.3.1. Device Classification . . . . . . . . . . . . . . . . 18
	3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 19		3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 19
	3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 20		3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 19
	3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20		3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20
	3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 20		3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 20
	3.3.6. Device/Service Specific Additional Data Structure . . 21		3.3.6. Device/Service Specific Additional Data Structure . . 21
	3.3.7. Device/Service Specific Additional Data Structure		3.3.7. Device/Service Specific Additional Data Structure
	Type . . . . . . . . . . . . . . . . . . . . . . . . 22		Type . . . . . . . . . . . . . . . . . . . . . . . . 21
	3.3.8. Issues with getting new types of data into use . . . 22		3.3.8. Issues with getting new types of data into use . . . 22
	3.3.9. Choosing between defining a new type of block or new		3.3.9. Choosing between defining a new type of block or new
	type of device/service specific additional data . . . 23		type of device/service specific additional data . . . 23
	3.3.10. emergencyCallData.DevInfo Example . . . . . . . . . . 24		3.3.10. emergencyCallData.DeviceInfo Example . . . . . . . . 23
	3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24		3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24
	3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 24		3.4.1. Subscriber Data Privacy Indicator . . . . . . . . . . 24
	3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25		3.4.2. xCard for Subscriber's Data . . . . . . . . . . . . . 25
	3.4.3. emergencyCallData.SubInfo Example . . . . . . . . . . 25		3.4.3. emergencyCallData.SubscriberInfo Example . . . . . . 25
	3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 28		3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 27
	3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 28		3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 27
	3.5.2. emergencyCallData.Comment Example . . . . . . . . . . 28		3.5.2. emergencyCallData.Comment Example . . . . . . . . . . 28
	4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 28		4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 28
	4.1. Transmitting Blocks using the Call-Info Header . . . . . 30		4.1. Transmitting Blocks using the Call-Info Header . . . . . 30
	4.2. Transmitting Blocks by Reference using the Provided-By		4.2. Transmitting Blocks by Reference using the Provided-By
	Element . . . . . . . . . . . . . . . . . . . . . . . . . 31		Element . . . . . . . . . . . . . . . . . . . . . . . . . 31
	4.3. Transmitting Blocks by Value using the Provided-By		4.3. Transmitting Blocks by Value using the Provided-By
	Element . . . . . . . . . . . . . . . . . . . . . . . . . 31		Element . . . . . . . . . . . . . . . . . . . . . . . . . 32
	4.4. The Content-Disposition Parameter . . . . . . . . . . . . 32		4.4. The Content-Disposition Parameter . . . . . . . . . . . . 33
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 33		5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 34
	6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 44		6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 45
	6.1. emergencyCallData.ProviderInfo XML Schema . . . . . . . . 44		6.1. emergencyCallData.ProviderInfo XML Schema . . . . . . . . 45
	6.2. emergencyCallData.SvcInfo XML Schema . . . . . . . . . . 46		6.2. emergencyCallData.ServiceInfo XML Schema . . . . . . . . 46
	6.3. emergencyCallData.DevInfo XML Schema . . . . . . . . . . 47		6.3. emergencyCallData.DeviceInfo XML Schema . . . . . . . . . 47
	6.4. emergencyCallData.SubInfo XML Schema . . . . . . . . . . 48		6.4. emergencyCallData.SubscriberInfo XML Schema . . . . . . . 48
	6.5. emergencyCallData.Comment XML Schema . . . . . . . . . . 49		6.5. emergencyCallData.Comment XML Schema . . . . . . . . . . 49
	6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 50		6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 50
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 52		7. Security Considerations . . . . . . . . . . . . . . . . . . . 52
	8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 53		8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 53
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55
	9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 55		9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 55
	9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 55		9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 55
	9.1.2. Service Environment Registry . . . . . . . . . . . . 56		9.1.2. Service Environment Registry . . . . . . . . . . . . 56
	9.1.3. Service Provider Type Registry . . . . . . . . . . . 56		9.1.3. Service Provider Type Registry . . . . . . . . . . . 57
	9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57		9.1.4. Service Delivered Registry . . . . . . . . . . . . . 57
	9.1.5. Device Classification Registry . . . . . . . . . . . 57		9.1.5. Device Classification Registry . . . . . . . . . . . 57
	9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 57		9.1.6. Device ID Type Type Registry . . . . . . . . . . . . 58
	9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58		9.1.7. Device/Service Data Type Registry . . . . . . . . . . 58
	9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 58		9.1.8. Additional Data Blocks Registry . . . . . . . . . . . 59
	9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 59		9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 59
	9.3. URN Sub-Namespace Registration for provided-by Registry		9.3. URN Sub-Namespace Registration for provided-by Registry
	Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 59		Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 60
	9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 59		9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 60
	9.4.1. MIME Content-type Registration for		9.4.1. MIME Content-type Registration for
	'application/emergencyCallData.ProviderInfo+xml' . . 59		'application/emergencyCallData.ProviderInfo+xml' . . 60
	9.4.2. MIME Content-type Registration for		9.4.2. MIME Content-type Registration for
	'application/emergencyCallData.SvcInfo+xml' . . . . . 60		'application/emergencyCallData.ServiceInfo+xml' . . . 61
	9.4.3. MIME Content-type Registration for		9.4.3. MIME Content-type Registration for
	'application/emergencyCallData.DevInfo+xml' . . . . . 61		'application/emergencyCallData.DeviceInfo+xml' . . . 62
	9.4.4. MIME Content-type Registration for		9.4.4. MIME Content-type Registration for
	'application/emergencyCallData.SubInfo+xml' . . . . . 62		'application/emergencyCallData.SubscriberInfo+xml' . 63
	9.4.5. MIME Content-type Registration for		9.4.5. MIME Content-type Registration for
	'application/emergencyCallData.Comment+xml' . . . . . 63		'application/emergencyCallData.Comment+xml' . . . . . 64
	9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 64		9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 65
	9.5.1. Registration for		9.5.1. Registration for
	urn:ietf:params:xml:ns:emergencycalldata . . . . . . 64		urn:ietf:params:xml:ns:emergencycalldata . . . . . . 65
	9.5.2. Registration for		9.5.2. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:providerinfo 65		urn:ietf:params:xml:ns:emergencycalldata:providerinfo 65
	9.5.3. Registration for		9.5.3. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:svcinfo . . 66		urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo 66
	9.5.4. Registration for		9.5.4. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:devinfo . . 67		urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo . 67
	9.5.5. Registration for		9.5.5. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:subinfo . . 67		urn:ietf:params:xml:ns:emergencycalldata:SubscriberIn
			fo . . . . . . . . . . . . . . . . . . . . . . . . . 68
	9.5.6. Registration for		9.5.6. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:comment . . 68		urn:ietf:params:xml:ns:emergencycalldata:comment . . 68
	9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 69		9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 69
	9.7. VCard Parameter Value Registration . . . . . . . . . . . 69		9.7. VCard Parameter Value Registration . . . . . . . . . . . 70
	10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 70		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 70
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 70		11. References . . . . . . . . . . . . . . . . . . . . . . . . . 70
	11.1. Normative References . . . . . . . . . . . . . . . . . . 70		11.1. Normative References . . . . . . . . . . . . . . . . . . 70
	11.2. Informational References . . . . . . . . . . . . . . . . 71		11.2. Informational References . . . . . . . . . . . . . . . . 72
	Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 73		Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 73
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 95		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 95
	1. Introduction		1. Introduction
	When an IP-based emergency call is initiated a rich set of data from		When an IP-based emergency call is initiated a rich set of data from
	multiple data sources is conveyed to the Public Safety Answering		multiple data sources is conveyed to the Public Safety Answering
	Point (PSAP). This data includes information about the calling party		Point (PSAP). This data includes information about the calling party
	identity, the multimedia capabilities of the device, the emergency		identity, the multimedia capabilities of the device, the emergency
	service number, location information, and meta-data about the sources		service number, location information, and meta-data about the sources
	skipping to change at page 15, line 9 ¶		skipping to change at page 14, line 49 ¶
	</vcard>		</vcard>
	</ad:DataProviderContact>		</ad:DataProviderContact>
	</ad:emergencyCallData.ProviderInfo>		</ad:emergencyCallData.ProviderInfo>
	Figure 2: emergencyCall.ProviderInfo Example.		Figure 2: emergencyCall.ProviderInfo Example.
	3.2. Service Information		3.2. Service Information
	This block describes the service that the service provider provides		This block describes the service that the service provider provides
	to the caller. It SHOULD be included by all SPs in the path of the		to the caller. It SHOULD be included by all SPs in the path of the
	call. The mime subtype is "application/emergencyCall.SvcInfo+xml".		call. The mime subtype is "application/
			emergencyCall.ServiceInfo+xml".
	3.2.1. Service Environment		3.2.1. Service Environment
	Data Element: Service Environment		Data Element: Service Environment
	Use: Required		Use: Required
	XML Element: <SvcEnvironment>		XML Element: <SvcEnvironment>
	Description: This element defines whether a call is from a business		Description: This element defines whether a call is from a business
	skipping to change at page 17, line 45 ¶		skipping to change at page 17, line 36 ¶
	* Unknown: no information is known about the service mobility		* Unknown: no information is known about the service mobility
	environment for the device		environment for the device
	Reason for Need: Knowing the service provider's belief of mobility		Reason for Need: Knowing the service provider's belief of mobility
	may assist the PSAP with the handling of the call.		may assist the PSAP with the handling of the call.
	How Used by Call Taker: To determine whether to assume the location		How Used by Call Taker: To determine whether to assume the location
	of the caller might change.		of the caller might change.
	3.2.4. emergencyCallData.SvcInfo Example		3.2.4. emergencyCallData.ServiceInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<svc:emergencyCallData.SvcInfo		<svc:emergencyCallData.ServiceInfo
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.ServiceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<svc:id>12345</svc:id>		<svc:id>12345</svc:id>
	<svc:SvcEnvironment>Business</svc:SvcEnvironment>		<svc:SvcEnvironment>Business</svc:SvcEnvironment>
	<svc:SvcDelByProvider>MLTS</svc:SvcDelByProvider>		<svc:SvcDelByProvider>MLTS</svc:SvcDelByProvider>
	<svc:SvcMobility>Fixed</svc:SvcMobility>		<svc:SvcMobility>Fixed</svc:SvcMobility>
	</svc:emergencyCallData.SvcInfo>		</svc:emergencyCallData.ServiceInfo>
	Figure 4: emergencyCallData.SvcInfo Example.		Figure 4: emergencyCallData.ServiceInfo Example.
	3.3. Device Information		3.3. Device Information
	This block provides information about the device used to place the		This block provides information about the device used to place the
	call. It should be provided by any service provider that knows what		call. It should be provided by any service provider that knows what
	device is being used, and by the device itself. The mime subtype is		device is being used, and by the device itself. The mime subtype is
	"application/emergencyCall.DevInfo+xml".		"application/emergencyCall.DeviceInfo+xml".
	3.3.1. Device Classification		3.3.1. Device Classification
	Data Element: Device Classification		Data Element: Device Classification
	Use: Optional		Use: Optional
	XML Element: <DeviceClassification>		XML Element: <DeviceClassification>
	Description: This data element defines the kind of device making the		Description: This data element defines the kind of device making the
	skipping to change at page 22, line 49 ¶		skipping to change at page 22, line 32 ¶
	data may be available to aid in providing the needed emergency		data may be available to aid in providing the needed emergency
	services.		services.
	Note: Information which is specific to a location or a caller		Note: Information which is specific to a location or a caller
	(person) should not be placed in this section.		(person) should not be placed in this section.
	3.3.8. Issues with getting new types of data into use		3.3.8. Issues with getting new types of data into use
	This document describes two mechanisms which allow extension of the		This document describes two mechanisms which allow extension of the
	kind of data provided with an emergency call: define a new block or		kind of data provided with an emergency call: define a new block or
	define a new service specific additional data URL for the DevInfo		define a new service specific additional data URL for the DeviceInfo
	block. While defining new data types and getting a new device or		block. While defining new data types and getting a new device or
	application to send the new data may be easy, getting PSAPs and		application to send the new data may be easy, getting PSAPs and
	responders to actually retrieve the data and use it will be		responders to actually retrieve the data and use it will be
	difficult. New mechanism providers should understand that acquiring		difficult. New mechanism providers should understand that acquiring
	and using new forms of data usually require software upgrades at the		and using new forms of data usually require software upgrades at the
	PSAP and/or responders, as well as training of call takers and		PSAP and/or responders, as well as training of call takers and
	responders in how to interpret and use the information. Legal and		responders in how to interpret and use the information. Legal and
	operational review may also be needed. Overwhelming a call taker or		operational review may also be needed. Overwhelming a call taker or
	responder with too much information is highly discouraged. Thus, the		responder with too much information is highly discouraged. Thus, the
	barrier to supporting new data is quite high.		barrier to supporting new data is quite high.
	skipping to change at page 23, line 35 ¶		skipping to change at page 23, line 20 ¶
	designed to carry all additional data supplied in the call that		designed to carry all additional data supplied in the call that
	conform to this document, even if the PSAP does not fetch or		conform to this document, even if the PSAP does not fetch or
	interpret the data. This allows responders to get the data even if		interpret the data. This allows responders to get the data even if
	the PSAP does not.		the PSAP does not.
	3.3.9. Choosing between defining a new type of block or new type of		3.3.9. Choosing between defining a new type of block or new type of
	device/service specific additional data		device/service specific additional data
	For devices that have device or service specific data, there are two		For devices that have device or service specific data, there are two
	choices to carry it. A new block can be defined, or the device/		choices to carry it. A new block can be defined, or the device/
	service specific additional data URL the DevInfo block can be used		service specific additional data URL the DeviceInfo block can be used
	and a new type for it defined . The data passed would likely be the		and a new type for it defined . The data passed would likely be the
	same in both cases. Considerations for choosing which mechanism to		same in both cases. Considerations for choosing which mechanism to
	register under include:		register under include:
	Applicability: Information which will be carried by many kinds of		Applicability: Information which will be carried by many kinds of
	devices or services are more appropriately defined as separate		devices or services are more appropriately defined as separate
	blocks.		blocks.
	Privacy: Information which may contain private data may be better		Privacy: Information which may contain private data may be better
	sent in the DevInfo block, rather than a new block so that		sent in the DeviceInfo block, rather than a new block so that
	implementations are not tempted to send the data by value, and		implementations are not tempted to send the data by value, and
	thus having more exposure to the data than forcing the data to be		thus having more exposure to the data than forcing the data to be
	retrieved via the URL in DevInfo.		retrieved via the URL in DeviceInfo.
	Size: Information which may be very may be better sent in the		Size: Information which may be very may be better sent in the
	DevInfo block, rather than a new block so that implementations are		DeviceInfo block, rather than a new block so that implementations
	not tempted to send the data by value. Conversely, data which is		are not tempted to send the data by value. Conversely, data which
	small may best be sent in a separate block so that it can be sent		is small may best be sent in a separate block so that it can be
	by value		sent by value
	Availability of a server: Providing the data via the device block		Availability of a server: Providing the data via the device block
	requires a server be made available to retrieve the data.		requires a server be made available to retrieve the data.
	Providing the data via new block allows it to be sent by value		Providing the data via new block allows it to be sent by value
	(CID).		(CID).
	3.3.10. emergencyCallData.DevInfo Example		3.3.10. emergencyCallData.DeviceInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<dev:emergencyCallData.DevInfo		<dev:emergencyCallData.DeviceInfo
	xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<dev:id>12345</dev:id>		<dev:id>12345</dev:id>
	<dev:DeviceClassification>Fixed phone</dev:DeviceClassification>		<dev:DeviceClassification>Fixed phone</dev:DeviceClassification>
	<dev:DeviceMfgr>Nokia</dev:DeviceMfgr>		<dev:DeviceMfgr>Nokia</dev:DeviceMfgr>
	<dev:DeviceModelNr>Lumia 800</dev:DeviceModelNr>		<dev:DeviceModelNr>Lumia 800</dev:DeviceModelNr>
	<dev:UniqueDeviceID>35788104</dev:UniqueDeviceID>		<dev:UniqueDeviceID>35788104</dev:UniqueDeviceID>
	<dev:TypeOfDeviceID>IMEI</dev:TypeOfDeviceID>		<dev:TypeOfDeviceID>IMEI</dev:TypeOfDeviceID>
	</dev:emergencyCallData.DevInfo>		</dev:emergencyCallData.DeviceInfo>
	Figure 7: emergencyCallData.DevInfo Example.		Figure 7: emergencyCallData.DeviceInfo Example.
	3.4. Owner/Subscriber Information		3.4. Owner/Subscriber Information
	This block describes the owner of the device (if provided by the		This block describes the owner of the device (if provided by the
	device) or the subscriber information, if provided by a service		device) or the subscriber information, if provided by a service
	provider. The contact location is not necessarily the location of		provider. The contact location is not necessarily the location of
	the caller or incident, but is rather the nominal contact address.		the caller or incident, but is rather the nominal contact address.
	The mime subtype is "application/emergencyCall.Subscriber+xml".		The mime subtype is "application/emergencyCall.Subscriber+xml".
	In some jurisdictions some or all parts of the subscriber-specific		In some jurisdictions some or all parts of the subscriber-specific
	skipping to change at page 25, line 44 ¶		skipping to change at page 25, line 30 ¶
	than one TEL property is provided, a parameter from the vCard		than one TEL property is provided, a parameter from the vCard
	Property Value registry MUST be specified on each TEL.		Property Value registry MUST be specified on each TEL.
	Reason for Need: When the caller is unable to provide information,		Reason for Need: When the caller is unable to provide information,
	this data may be used to obtain it		this data may be used to obtain it
	How Used by Call Taker: Obtaining critical information about the		How Used by Call Taker: Obtaining critical information about the
	caller and possibly the location when it is not able to be		caller and possibly the location when it is not able to be
	obtained otherwise.		obtained otherwise.
	3.4.3. emergencyCallData.SubInfo Example		3.4.3. emergencyCallData.SubscriberInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<sub:emergencyCallData.SubInfo		<sub:emergencyCallData.SubscriberInfo
	xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:subinfo"		xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	privacyRequested="false">		privacyRequested="false">
	<sub:id>12345</sub:id>		<sub:id>12345</sub:id>
	<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">		<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>		<vcards>
	<vcard>		<vcard>
	<fn><text>Simon Perreault</text></fn>		<fn><text>Simon Perreault</text></fn>
	<n>		<n>
	<surname>Perreault</surname>		<surname>Perreault</surname>
	<given>Simon</given>		<given>Simon</given>
	skipping to change at page 27, line 51 ¶		skipping to change at page 27, line 37 ¶
	</key>		</key>
	<tz><text>America/Montreal</text></tz>		<tz><text>America/Montreal</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://nomis80.org</uri>		<uri>http://nomis80.org</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>		</vcards>
	</sub:SubscriberData>		</sub:SubscriberData>
	</sub:emergencyCallData.SubInfo>		</sub:emergencyCallData.SubscriberInfo>
	Figure 8: emergencyCallData.SubInfo Example.
			Figure 8: emergencyCallData.SubscriberInfo Example.
	3.5. Comment		3.5. Comment
	This block provides a mechanism for the data provider to supply		This block provides a mechanism for the data provider to supply
	extra, human readable information to the PSAP. It is not intended		extra, human readable information to the PSAP. It is not intended
	for a general purpose extension mechanism nor does it aim to provide		for a general purpose extension mechanism nor does it aim to provide
	machine-reable content. The mime subtype is "application/		machine-reable content. The mime subtype is "application/
	emergencyCall.Comment+xml"		emergencyCall.Comment+xml"
	3.5.1. Comment		3.5.1. Comment
	skipping to change at page 32, line 4 ¶		skipping to change at page 32, line 24 ¶
	purpose="emergencyCallData.ProviderInfo"/>		purpose="emergencyCallData.ProviderInfo"/>
	4.3. Transmitting Blocks by Value using the Provided-By Element		4.3. Transmitting Blocks by Value using the Provided-By Element
	It is RECOMMENDED that access networks supply the data specified in		It is RECOMMENDED that access networks supply the data specified in
	this document by reference, but they MAY provide the data by value.		this document by reference, but they MAY provide the data by value.
	The 'emergencyCallDataValue' element is used to transmit an		The 'emergencyCallDataValue' element is used to transmit an
	additional data block by value within a 'Provided-By' element of a		additional data block by value within a 'Provided-By' element of a
	PIDF-LO. The 'emergencyCallDataValue' element has one attribute:		PIDF-LO. The 'emergencyCallDataValue' element has one attribute:
	'purpose' to indicate the type of data block contained. The value of		'purpose' to indicate the type of data block contained. The value of
	'purpose' is the same as used in a 'Call-Info' header field (as		'purpose' is the same as used in a 'Call-Info' header field (as
	specified in Section 4.1, and in Section 4.1). The same XML		specified in Section 4.1, and in Section 4.1). The same XML
	structure as would be contained in the corresponding MIME type body		structure as would be contained in the corresponding MIME type body
	part is placed inside the 'emergencyCallDataValue' element.		part is placed inside the 'emergencyCallDataValue' element.
	For example:		For example:
	<provided-by		<provided-by
	xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData">		xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData">
	<emergencyCallData>		<emergencyCallData>
	<byRef purpose="emergencyCallData.SvcInfo"		<byRef purpose="emergencyCallData.ServiceInfo"
	ref="https://example.com/ref2"/>		ref="https://example.com/ref2"/>
	<sub:emergencyCall.Comment		<sub:emergencyCall.Comment
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment">		xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment">
	<sub:Comment xml:lang="en">This is an example text.		<sub:Comment xml:lang="en">This is an example text.
	</sub:Comment>		</sub:Comment>
	</sub:emergencyCall.Comment>		</sub:emergencyCall.Comment>
	</emergencyCallData>		</emergencyCallData>
	<emergencyCallDataValue		<emergencyCallDataValue
	purpose="emergencyCallData.ProviderInfo">		purpose="emergencyCallData.ProviderInfo">
	<ProviderID>Test</ProviderID>		<ProviderID>Test</ProviderID>
	skipping to change at page 35, line 4 ¶		skipping to change at page 35, line 22 ¶
	Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9		Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
	Max-Forwards: 70		Max-Forwards: 70
	To: <urn:service:sos>		To: <urn:service:sos>
	From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl		From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
	Call-ID: 3848276298220188511@example.com		Call-ID: 3848276298220188511@example.com
	Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,		Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
	<http://www.example.com/hannes/> ;purpose=info,		<http://www.example.com/hannes/> ;purpose=info,
	<cid:1234567890@atlanta.example.com>		<cid:1234567890@atlanta.example.com>
	;purpose=emergencyCallData.ProviderInfo,		;purpose=emergencyCallData.ProviderInfo,
	<cide:0123456789@atlanta.example.com>		<cide:0123456789@atlanta.example.com>
	;purpose=emergencyCallData.DevInfo		;purpose=emergencyCallData.DeviceInfo
	Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>		Geolocation: <https://ls.example.net:9768/357yc6s64ceyoiuy5ax3o>
	Geolocation-Routing: yes		Geolocation-Routing: yes
	Accept: application/sdp, application/pidf+xml,		Accept: application/sdp, application/pidf+xml,
	application/emergencyCallProviderinfo+xml		application/emergencyCallProviderinfo+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.DevInfo+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.DevInfo		<dev:emergencyCallData.DeviceInfo
	xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<dev:id>12345</svc:id>		<dev:id>12345</svc:id>
	<dev:DeviceClassification>SoftPhn</dev:DeviceClassification>		<dev:DeviceClassification>SoftPhn</dev:DeviceClassification>
	<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID>		<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID>
	<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID>		<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID>
	</dev:emergencyCallData.DevInfo>		</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">
	skipping to change at page 38, line 21 ¶		skipping to change at page 38, line 39 ¶
	Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9		Via: SIPS/2.0/TLS server.example.com;branch=z9hG4bK74bf9
	Max-Forwards: 70		Max-Forwards: 70
	To: <urn:service:sos>		To: <urn:service:sos>
	From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl		From: Hannes Tschofenig <sips:hannes@example.com>;tag=9fxced76sl
	Call-ID: 3848276298220188511@example.com		Call-ID: 3848276298220188511@example.com
	Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,		Call-Info: <http://wwww.example.com/hannes/photo.jpg> ;purpose=icon,
	<http://www.example.com/hannes/> ;purpose=info,		<http://www.example.com/hannes/> ;purpose=info,
	<cid:1234567890@atlanta.example.com>		<cid:1234567890@atlanta.example.com>
	;purpose=emergencyCallData.ProviderInfo		;purpose=emergencyCallData.ProviderInfo
	<cid:0123456789@atlanta.example.com>		<cid:0123456789@atlanta.example.com>
	;purpose=emergencyCallData.DevInfo		;purpose=emergencyCallData.DeviceInfo
	Call-Info: <cid:bloorpyhex@atlanta.example.com>		Call-Info: <cid:bloorpyhex@atlanta.example.com>
	;purpose=emergencyCallData.SrvcInfo		;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.DevInfo+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.DevInfo		<dev:emergencyCallData.DeviceInfo
	xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<dev:id>12345</svc:id>		<dev:id>12345</svc:id>
	<dev:DeviceClassification>SoftPhn</dev:DeviceClassification>		<dev:DeviceClassification>SoftPhn</dev:DeviceClassification>
	<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID>		<dev:UniqueDeviceID>00-0d-4b-30-72-df</dev:UniqueDeviceID>
	<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID>		<dev:TypeOfDeviceID>MAC</dev:TypeOfDeviceID>
	</dev:emergencyCallData.DevInfo>		</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">
	skipping to change at page 41, line 4 ¶		skipping to change at page 41, line 21 ¶
	</parameters>		</parameters>
	<uri>https://www.example.com/key.asc		<uri>https://www.example.com/key.asc
	</uri>		</uri>
	</key>		</key>
	<tz><text>Finland/Helsinki</text></tz>		<tz><text>Finland/Helsinki</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://example.com/hannes.tschofenig</uri>		<uri>http://example.com/hannes.tschofenig</uri>
	</url>		</url>
	</vcard>		</vcard>
	</xc:DataProviderContact>		</xc:DataProviderContact>
	</pi:emergencyCallData.ProviderInfo>		</pi:emergencyCallData.ProviderInfo>
	--boundary1--		--boundary1--
	Content-Type: application/emergencyCall.SvcInfo+xml		Content-Type: application/emergencyCall.ServiceInfo+xml
	Content-ID: <bloorpyhex@atlanta.example.com>		Content-ID: <bloorpyhex@atlanta.example.com>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<svc:emergencyCall.SvcInfo		<svc:emergencyCall.ServiceInfo
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.ServiceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<svc:id>abc123</svc:id>		<svc:id>abc123</svc:id>
	<svc:SvcEnvironment>Residence</svc:SvcEnvironment>		<svc:SvcEnvironment>Residence</svc:SvcEnvironment>
	<svc:SvcDelByProvider>VOIP</svc:SvcDelByProvider>		<svc:SvcDelByProvider>VOIP</svc:SvcDelByProvider>
	<svc:SvcMobility>Unknown</svc:SvcMobility>		<svc:SvcMobility>Unknown</svc:SvcMobility>
	</svc:emergencyCall.SvcInfo>		</svc:emergencyCall.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">
	skipping to change at page 44, line 12 ¶		skipping to change at page 44, line 29 ¶
	<gbp:retransmission-allowed>true		<gbp:retransmission-allowed>true
	</gbp:retransmission-allowed>		</gbp:retransmission-allowed>
	<gbp:retention-expiry>2013-12-10T20:00:00Z		<gbp:retention-expiry>2013-12-10T20:00:00Z
	</gbp:retention-expiry>		</gbp:retention-expiry>
	</gp:usage-rules>		</gp:usage-rules>
	<gp:method>802.11</gp:method>		<gp:method>802.11</gp:method>
	<provided-by		<provided-by
	xmlns="urn:ietf:params:xml:ns:emergencycalldata">		xmlns="urn:ietf:params:xml:ns:emergencycalldata">
	<emergencyCallDataReference purpose="emergencyCallData.SvcInfo"		<emergencyCallDataReference purpose="emergencyCallData.ServiceInfo"
	ref="https://example.com/ref2"/>		ref="https://example.com/ref2"/>
	<emergencyCallDataValue>		<emergencyCallDataValue>
	<emergencyCallData.ProviderInfo		<emergencyCallData.ProviderInfo
	xmlns="urn:ietf:params:xml:ns:emergencycalldata:providerinfo">		xmlns="urn:ietf:params:xml:ns:emergencycalldata:providerinfo">
	<DataProviderString>University of California, Irvine		<DataProviderString>University of California, Irvine
	</DataProviderString>		</DataProviderString>
	<ProviderID>urn:nena:companyid:uci</ProviderID>		<ProviderID>urn:nena:companyid:uci</ProviderID>
	<ProviderIDSeries>NENA</ProviderIDSeries>		<ProviderIDSeries>NENA</ProviderIDSeries>
	<TypeOfProvider>Other</TypeOfProvider>		<TypeOfProvider>Other</TypeOfProvider>
	skipping to change at page 46, line 31 ¶		skipping to change at page 46, line 49 ¶
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 15: emergencyCallData.ProviderInfo XML Schema.		Figure 15: emergencyCallData.ProviderInfo XML Schema.
	6.2. emergencyCallData.SvcInfo XML Schema		6.2. emergencyCallData.ServiceInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:emergencycalldata:svcinfo"		"urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:svcinfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCallData.SvcInfo" type="svc:SvcInfoType"/>		<xs:element name="emergencyCallData.ServiceInfo" type="svc:ServiceInfoType"/>
	<xs:complexType name="SvcInfoType">		<xs:complexType name="ServiceInfoType">
	<xs:sequence>		<xs:sequence>
	<xs:element name="id"		<xs:element name="id"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcEnvironment"		<xs:element name="SvcEnvironment"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcDelByProvider"		<xs:element name="SvcDelByProvider"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	skipping to change at page 47, line 24 ¶		skipping to change at page 47, line 41 ¶
	<xs:element name="Link"		<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 16: emergencyCallData.SvcInfo XML Schema.		Figure 16: emergencyCallData.ServiceInfo XML Schema.
	6.3. emergencyCallData.DevInfo XML Schema		6.3. emergencyCallData.DeviceInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		targetNamespace="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCallData.DevInfo" type="dev:DevInfoType"/>		<xs:element name="emergencyCallData.DeviceInfo" type="dev:DeviceInfoType"/>
	<xs:complexType name="DevInfoType">		<xs:complexType name="DeviceInfoType">
	<xs:sequence>		<xs:sequence>
	<xs:element name="id"		<xs:element name="id"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="DeviceClassification"		<xs:element name="DeviceClassification"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceMfgr"		<xs:element name="DeviceMfgr"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	skipping to change at page 48, line 27 ¶		skipping to change at page 48, line 44 ¶
	<xs:element name="DeviceSpecificType"		<xs:element name="DeviceSpecificType"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 17: emergencyCallData.DevInfo XML Schema.		Figure 17: emergencyCallData.DeviceInfo XML Schema.
	6.4. emergencyCallData.SubInfo XML Schema		6.4. emergencyCallData.SubscriberInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:emergencycalldata:subinfo"		"urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:subinfo"		xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>		<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>
	<xs:element name="emergencyCallData.SubInfo" type="sub:SubInfoType"/>		<xs:element name="emergencyCallData.SubscriberInfo" type="sub:SubscriberInfoType"/>
	<xs:complexType name="SubInfoType">		<xs:complexType name="SubscriberInfoType">
	<xs:complexContent>		<xs:complexContent>
	<xs:sequence>		<xs:sequence>
	<xs:element name="id"		<xs:element name="id"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SubscriberData" type="xc:vcardType"		<xs:element name="SubscriberData" type="xc:vcardType"
	minOccurs="0" maxOccurs="1" />		minOccurs="0" maxOccurs="1" />
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	<xs:attribute name="privacyRequested" type="xs:boolean" use="required"/>		<xs:attribute name="privacyRequested" type="xs:boolean" use="required"/>
	</xs:complexContent>		</xs:complexContent>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 18: emergencyCallData.SubInfo XML Schema.		Figure 18: emergencyCallData.SubscriberInfo XML Schema.
	6.5. emergencyCallData.Comment XML Schema		6.5. emergencyCallData.Comment XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:emergencycalldata:comment"		"urn:ietf:params:xml:ns:emergencycalldata:comment"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment"		xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	skipping to change at page 50, line 27 ¶		skipping to change at page 50, line 45 ¶
	This section defines the Provided-By schema.		This section defines the Provided-By schema.
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"		"urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"		xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"		xmlns:pi="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"
	xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:svcinfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo"
	xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:devinfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"
	xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:subinfo"		xmlns:sub="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"
	xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment"		xmlns:com="urn:ietf:params:xml:ns:emergencycalldata:comment"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"/>		<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:providerinfo"/>
	<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:svcinfo"/>		<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo"/>
	<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:devinfo"/>		<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo"/>
	<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:subinfo"/>		<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo"/>
	<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:comment"/>		<xs:import namespace="urn:ietf:params:xml:ns:emergencycalldata:comment"/>
	<xs:element name="provided-by" type="ad:provided-by-Type"/>		<xs:element name="provided-by" type="ad:provided-by-Type"/>
	<xs:complexType name="provided-by-Type">		<xs:complexType name="provided-by-Type">
	<xs:sequence>		<xs:sequence>
	<xs:element name="id"		<xs:element name="id"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="emergencyCallDataReference"		<xs:element name="emergencyCallDataReference"
	skipping to change at page 51, line 38 ¶		skipping to change at page 52, line 7 ¶
	</xs:complexContent>		</xs:complexContent>
	</xs:complexType>		</xs:complexType>
	<!-- Additional Data By Value -->		<!-- Additional Data By Value -->
	<xs:complexType name="emergencyCallDataValueType">		<xs:complexType name="emergencyCallDataValueType">
	<xs:sequence>		<xs:sequence>
	<xs:element name="emergencyCallData.ProviderInfo"		<xs:element name="emergencyCallData.ProviderInfo"
	type="pi:ProviderInfoType"		type="pi:ProviderInfoType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="emergencyCallData.SvcInfo"		<xs:element name="emergencyCallData.ServiceInfo"
	type="svc:SvcInfoType"		type="svc:ServiceInfoType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="emergencyCallData.DevInfo"		<xs:element name="emergencyCallData.DeviceInfo"
	type="dev:DevInfoType"		type="dev:DeviceInfoType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="emergencyCallData.SubInfo"		<xs:element name="emergencyCallData.SubscriberInfo"
	type="sub:SubInfoType"		type="sub:SubscriberInfoType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="emergencyCallData.Comment"		<xs:element name="emergencyCallData.Comment"
	type="com:CommentType"		type="com:CommentType"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	skipping to change at page 59, line 13 ¶		skipping to change at page 59, line 28 ¶
	Name: Element Name of enclosing block.		Name: Element Name of enclosing block.
	Reference: The document that describes the block		Reference: The document that describes the block
	The initial set of values are listed in Figure 24.		The initial set of values are listed in Figure 24.
	+--------------+------------+		+--------------+------------+
	| Token | Reference |		| Token | Reference |
	+--------------+------------+		+--------------+------------+
	| ProviderInfo | [This RFC] |		| ProviderInfo | [This RFC] |
	| SvcInfo | [This RFC] |		| ServiceInfo | [This RFC] |
	| DevInfo | [This RFC] |		| DeviceInfo | [This RFC] |
	| Subscriber | [This RFC] |		| Subscriber | [This RFC] |
	| Comment | [This RFC] |		| Comment | [This RFC] |
	+--------------+------------+		+--------------+------------+
	Figure 24: Additional Data Blocks Registry.		Figure 24: Additional Data Blocks Registry.
	9.2. 'emergencyCallData' Purpose Parameter Value		9.2. 'emergencyCallData' Purpose Parameter Value
	This document defines the 'emergencyCallData' value for the "purpose"		This document defines the 'emergencyCallData' value for the "purpose"
	parameter of the Call-Info header field. The Call-Info header and		parameter of the Call-Info header field. The Call-Info header and
	skipping to change at page 60, line 38 ¶		skipping to change at page 61, line 4 ¶
	Section 7 and Section 8 for more information.		Section 7 and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.2. MIME Content-type Registration for 'application/		9.4.2. MIME Content-type Registration for 'application/
	emergencyCallData.SvcInfo+xml'		emergencyCallData.ServiceInfo+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	MIME media type name: application		MIME media type name: application
	MIME subtype name: emergencyCallData.SvcInfo+xml		MIME subtype name: emergencyCallData.ServiceInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See
	Section 3.2 of RFC 3023 [RFC3023].		Section 3.2 of RFC 3023 [RFC3023].
	skipping to change at page 61, line 38 ¶		skipping to change at page 62, line 4 ¶
	and Section 8 for more information.		and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.3. MIME Content-type Registration for 'application/		9.4.3. MIME Content-type Registration for 'application/
	emergencyCallData.DevInfo+xml'		emergencyCallData.DeviceInfo+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	MIME media type name: application		MIME media type name: application
	MIME subtype name: emergencyCallData.DevInfo+xml		MIME subtype name: emergencyCallData.DeviceInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See
	Section 3.2 of RFC 3023 [RFC3023].		Section 3.2 of RFC 3023 [RFC3023].
	skipping to change at page 62, line 38 ¶		skipping to change at page 63, line 4 ¶
	Section 7 and Section 8 for more information.		Section 7 and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.4. MIME Content-type Registration for 'application/		9.4.4. MIME Content-type Registration for 'application/
	emergencyCallData.SubInfo+xml'		emergencyCallData.SubscriberInfo+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	MIME media type name: application		MIME media type name: application
	MIME subtype name: emergencyCallData.SubInfo+xml		MIME subtype name: emergencyCallData.SubscriberInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See
	Section 3.2 of RFC 3023 [RFC3023].		Section 3.2 of RFC 3023 [RFC3023].
	skipping to change at page 66, line 19 ¶		skipping to change at page 66, line 32 ¶
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Data Provider Information</h2>		<h2>Data Provider Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.5.3. Registration for		9.5.3. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:svcinfo		urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencycalldata:svcinfo		URI: urn:ietf:params:xml:ns:emergencycalldata:ServiceInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	skipping to change at page 67, line 6 ¶		skipping to change at page 67, line 18 ¶
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Service Information</h2>		<h2>Service Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.5.4. Registration for		9.5.4. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:devinfo		urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencycalldata:devinfo		URI: urn:ietf:params:xml:ns:emergencycalldata:DeviceInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	skipping to change at page 67, line 38 ¶		skipping to change at page 68, line 6 ¶
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Device Information</h2>		<h2>Device Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.5.5. Registration for		9.5.5. Registration for
	urn:ietf:params:xml:ns:emergencycalldata:subinfo		urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencycalldata:subinfo		URI: urn:ietf:params:xml:ns:emergencycalldata:SubscriberInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	skipping to change at page 69, line 20 ¶		skipping to change at page 69, line 35 ¶
	This specification registers five schemas, as per the guidelines in		This specification registers five schemas, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:schema:emergencycalldata:providerinfo		URI: urn:ietf:params:xml:schema:emergencycalldata:providerinfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 15.		XML: The XML schema can be found in Figure 15.
	URI: urn:ietf:params:xml:schema:emergencycalldata:svcinfo		URI: urn:ietf:params:xml:schema:emergencycalldata:ServiceInfo
	Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 16.		XML: The XML schema can be found in Figure 16.
	URI: urn:ietf:params:xml:schema:emergencycalldata:devinfo		URI: urn:ietf:params:xml:schema:emergencycalldata:DeviceInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 17.		XML: The XML schema can be found in Figure 17.
	URI: urn:ietf:params:xml:schema:emergencycalldata:subinfo		URI: urn:ietf:params:xml:schema:emergencycalldata:SubscriberInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Section 6.4.		XML: The XML schema can be found in Section 6.4.
	URI: urn:ietf:params:xml:schema:emergencycalldata:comment		URI: urn:ietf:params:xml:schema:emergencycalldata:comment
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
End of changes. 107 change blocks.
	137 lines changed or deleted		133 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/