< draft-ietf-ecrit-additional-data-08.txt		draft-ietf-ecrit-additional-data-09.txt >
	ECRIT B.R. Rosen		ECRIT B.R. Rosen
	Internet-Draft NeuStar		Internet-Draft NeuStar
	Intended status: Standards Track H. Tschofenig		Intended status: Standards Track H. Tschofenig
	Expires: November 06, 2013 Nokia Siemens Networks		Expires: November 29, 2013 Nokia Siemens Networks
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	R. Gellens		R. Gellens
	Qualcomm Technologies, Inc.		Qualcomm Technologies, Inc.
	May 05, 2013		May 28, 2013
	Additional Data related to an Emergency Call		Additional Data related to an Emergency Call
	draft-ietf-ecrit-additional-data-08.txt		draft-ietf-ecrit-additional-data-09.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 or the		which the call originated may have information about the call or the
	caller which the PSAP may be able to use. This document describes		caller which the PSAP may be able to use. This document describes
	data structures to convey such data to the PSAP. In addition, data		data structures and a mechanism to convey such data to the PSAP. The
	may also be included by reference, via a Uniform Resource Identifier		mechanism uses a Uniform Resource Identifier (URI), which may point
	(URI) pointing to data found at an external resource. Consequently,		to either an external resource or an object in the body of the SIP
	this document follows the tradition of prior emergency services		message. The mechanism thus allows the data to be passed by
	standardization work where data can be conveyed by value within the		reference (when the URI points to an external resource) or by value
	call signaling (i.e., in body of the SIP message) and also by		(when it points into the body of the message). This follows the
	reference.		tradition of prior emergency services standardization work where data
			can be conveyed by value within the call signaling (i.e., in body of
			the SIP message) and also by reference.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on November 06, 2013.		This Internet-Draft will expire on November 29, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Data Structure Overview . . . . . . . . . . . . . . . . . . . 6		3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6
	4. Transmitting Blocks of Additional Data . . . . . . . . . . . 7		3.1. Data Provider Information . . . . . . . . . . . . . . . . 7
	4.1. Transmitting blocks using Call-Info . . . . . . . . . . . 8		3.1.1. Data Provider String . . . . . . . . . . . . . . . . 7
	4.2. Transmitting blocks by reference using Provided-By . . . 9		3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 7
	4.3. Transmitting blocks by value using Provided-By . . . . . 9		3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8
	5. Data Provider Information . . . . . . . . . . . . . . . . . . 10		3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 8
	5.1. Data Provider String . . . . . . . . . . . . . . . . . . 10		3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 9
	5.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . 11		3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10
	5.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 11		3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 10
	5.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 12		3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 11
	5.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 13		3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 12
	5.6. Data Provider Languages(s) Supported . . . . . . . . . . 13		3.1.10. emergencyCall.ProviderInfo Example . . . . . . . . . 12
	5.7. xCard of Data Provider . . . . . . . . . . . . . . . . . 14		3.2. Service Information . . . . . . . . . . . . . . . . . . . 14
	5.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 15		3.2.1. Service Environment . . . . . . . . . . . . . . . . . 14
	5.9. Subcontractor Priority . . . . . . . . . . . . . . . . . 15		3.2.2. Service Delivered by Provider to End User . . . . . . 15
	5.10. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 16		3.2.3. Service Mobility Environment . . . . . . . . . . . . 16
	5.11. emergencyCall.ProviderInfo Example . . . . . . . . . . . 17		3.2.4. emergencyCall.SvcInfo Example . . . . . . . . . . . . 17
	6. Service Information . . . . . . . . . . . . . . . . . . . . . 19		3.3. Device Information . . . . . . . . . . . . . . . . . . . 17
	6.1. Service Environment . . . . . . . . . . . . . . . . . . . 19		3.3.1. Device Classification . . . . . . . . . . . . . . . . 18
	6.2. Service Delivered by Provider to End User . . . . . . . . 20		3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 19
	6.3. Service Mobility Environment . . . . . . . . . . . . . . 21		3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 20
	6.4. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 22		3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 20
	6.5. emergencyCall.SvcInfo Example . . . . . . . . . . . . . . 22		3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 21
	7. Device Information . . . . . . . . . . . . . . . . . . . . . 23		3.3.6. Device/Service Specific Additional Data Structure . . 21
	7.1. Device Classification . . . . . . . . . . . . . . . . . . 23		3.3.7. Device/Service Specific Additional Data Structure
	7.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 25		Type . . . . . . . . . . . . . . . . . . . . . . . . 22
	7.3. Device Model Number . . . . . . . . . . . . . . . . . . . 25		3.3.8. Choosing between defining a new type of block or new
	7.4. Unique Device Identifier . . . . . . . . . . . . . . . . 26		type of device/service specific additional data . . . 23
	7.5. Type of Device Identifier . . . . . . . . . . . . . . . . 26		3.3.9. emergencyCall.DevInfo Example . . . . . . . . . . . . 23
	7.6. Device/Service Specific Additional Data Structure . . . . 27
	7.7. Device/Service Specific Additional Data Structure Type . 28
	7.8. Choosing between defining a new type of block or new type
	of device/service specific additional data . . . . . . . 28
	7.9. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 29
	7.10. emergencyCall.DevInfo Example . . . . . . . . . . . . . . 30
	8. Owner/Subscriber Information . . . . . . . . . . . . . . . . 30
	8.1. xCard for Subscriber's Data . . . . . . . . . . . . . . . 30
	8.2. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 31
	8.3. emergencyCall.SubInfo Example . . . . . . . . . . . . . . 32
	9. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
	9.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 34
	9.2. emergencyCall.Comment XML Schema . . . . . . . . . . . . 34
	9.3. emergencyCall.Comment Example . . . . . . . . . . . . . . 35
	10. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
	11. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 36
	12. Security Considerations . . . . . . . . . . . . . . . . . . . 37
	13. Privacy Considerations . . . . . . . . . . . . . . . . . . . 38
	14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 38
	14.1. Registry creation . . . . . . . . . . . . . . . . . . . 38
	14.1.1. Additional Call Data Provider ID Series Registry . . 38
	14.1.2. Additional Call Data Service Provider Type Registry 39
	14.1.3. Additional Call Data Service Delivered Registry . . 40
	14.1.4. Additional Call Data Device Classification Registry 41
	14.1.5. Additional Call Data Device ID Type Type Registry . 42
	14.1.6. Device/Service Specific Additional Data Type
	Registry . . . . . . . . . . . . . . . . . . . . . . 42
	14.1.7. Additional Call Data Blocks Registry . . . . . . . . 43
	14.2. 'emergencyCallData' Purpose Parameter Value . . . . . . 43
	14.3. URN Sub-Namespace Registration for provided-by Registry
	Entry . . . . . . . . . . . . . . . . . . . . . . . . . 44
	14.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 44
	14.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 45
	14.4.1. MIME Content-type Registration for
	'application/emergencyCall.ProviderInfo+xml' . . . . 45
	14.4.2. MIME Content-type Registration for
	'application/emergencyCall.SvcInfo+xml' . . . . . . 46
	14.4.3. MIME Content-type Registration for
	'application/emergencyCall.DevInfo+xml' . . . . . . 47
	14.4.4. MIME Content-type Registration for
	'application/emergencyCall.SubInfo+xml' . . . . . . 49
	14.4.5. MIME Content-type Registration for
	'application/emergencyCall.Comment+xml' . . . . . . 50
	14.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 51
	14.5.1. Registration for
	urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 51
	14.5.2. Registration for
	urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 52
	14.5.3. Registration for
	urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 52
	14.5.4. Registration for		3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 24
	urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 53		3.4.1. xCard for Subscriber's Data . . . . . . . . . . . . . 24
	14.5.5. Registration for		3.4.2. emergencyCall.SubInfo Example . . . . . . . . . . . . 24
	urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 54		3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 27
	14.5.6. Registration for		3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 27
	urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 55		3.5.2. emergencyCall.Comment Example . . . . . . . . . . . . 27
	14.6. Schema Registrations . . . . . . . . . . . . . . . . . . 55		4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 27
	14.7. VCard Parameter Value Registration . . . . . . . . . . . 56		4.1. Transmitting Blocks using the Call-Info Header . . . . . 29
	15. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56		4.2. Transmitting Blocks by Reference using the Provided-By
	16. References . . . . . . . . . . . . . . . . . . . . . . . . . 57		Element . . . . . . . . . . . . . . . . . . . . . . . . . 30
	16.1. Normative References . . . . . . . . . . . . . . . . . . 57		4.3. Transmitting Blocks by Value using the Provided-By
	16.2. Informational References . . . . . . . . . . . . . . . . 57		Element . . . . . . . . . . . . . . . . . . . . . . . . . 31
			5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 31
			6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 33
			6.1. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 33
			6.2. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 34
			6.3. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 35
			6.4. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 36
			6.5. emergencyCall.Comment XML Schema . . . . . . . . . . . . 37
			7. Security Considerations . . . . . . . . . . . . . . . . . . . 37
			8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 39
			9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39
			9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 39
			9.1.1. Additional Call Data Provider ID Series Registry . . 39
			9.1.2. Additional Call Data Service Provider Type Registry . 40
			9.1.3. Additional Call Data Service Delivered Registry . . . 40
			9.1.4. Additional Call Data Device Classification Registry . 40
			9.1.5. Additional Call Data Device ID Type Type Registry . . 41
			9.1.6. Device/Service Specific Additional Data Type Registry 41
			9.1.7. Additional Call Data Blocks Registry . . . . . . . . 42
			9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 42
			9.3. URN Sub-Namespace Registration for provided-by Registry
			Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 43
			9.3.1. Provided-By XML Schema . . . . . . . . . . . . . . . 43
			9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 44
			9.4.1. MIME Content-type Registration for
			'application/emergencyCall.ProviderInfo+xml' . . . . 45
			9.4.2. MIME Content-type Registration for
			'application/emergencyCall.SvcInfo+xml' . . . . . . . 46
			9.4.3. MIME Content-type Registration for
			'application/emergencyCall.DevInfo+xml' . . . . . . . 47
			9.4.4. MIME Content-type Registration for
			'application/emergencyCall.SubInfo+xml' . . . . . . . 48
			9.4.5. MIME Content-type Registration for
			'application/emergencyCall.Comment+xml' . . . . . . . 50
			9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 51
			9.5.1. Registration for
			urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 51
			9.5.2. Registration for
			urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 51
			9.5.3. Registration for
			urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 52
			9.5.4. Registration for
			urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 53
			9.5.5. Registration for
			urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 54
			9.5.6. Registration for
			urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 54
			9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 55
			9.7. VCard Parameter Value Registration . . . . . . . . . . . 56
			10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 56
			11. References . . . . . . . . . . . . . . . . . . . . . . . . . 57
			11.1. Normative References . . . . . . . . . . . . . . . . . . 57
			11.2. Informational References . . . . . . . . . . . . . . . . 57
	Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 58		Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 58
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80
	1. Introduction		1. Introduction
	When an emergency call is triggered and the Session Initiation		When an IP-based emergency call is initiated a rich set of data from
	Protocol (SIP) is used a rich set of data is conveyed to the Public		multiple data sources is conveyed to the Public Safety Answering
	Safety Answering Point (PSAP) already as part of the call setup,		Point (PSAP). This data includes information about the calling party
	which includes information about the calling party identity, the		identity, the multimedia capabilities of the device, the emergency
	multimedia capabilities of the device, the emergency service number,		service number, location information, and meta-data about the
	etc. The device, as well as any service provider in the path may		sources. The device, the access network provider, and any service
	have even more information that may be useful for a PSAP call taker.		provider in the call path may have even more information that may be
	This document extends the basic signaling of an emergency call, as		useful for a PSAP call taker. This document extends the basic set of
	described in [RFC6443] and [RFC6881], in order to carry additional		data communicated with an IP-based emergency call providing call
	data which may be useful to an entity handling the call. This data		takers and the PSAP organization valuable insight and increased
	is "additional" to the basic information found in the emergency call		situational awareness.
	signaling used.
	Three general categories of such data are defined, namely data about
	the call, the location and the caller. In more detail, the three
	types of data exchanged are:
	Data Associated with a Call: While information is carried in the		In general, there are three categories of data communicated in an
	call setup procedure itself (as part of the SIP headers as well as		emergency call:
	in the body of the SIP message), there is additional data known by
	the device making the call, or a service provider in the path of
	the call. This information may include the identity and contact
	information of the service provider, subscriber identity and
	contact information, the type of service the provider offers, what
	kind of device is being used, etc. Some data is device or service
	dependent data. For example, a car telematics system or service
	may have crash information. A medical monitoring device may have
	sensor data. While the details of the information may vary by
	device or service, there needs to be a common way to send such
	data to a PSAP.
	Data Associated with a Location: Location data is conveyed in the		Data Associated with a Location: Location data is conveyed in the
	Presence Informatoin Data Format Location Object (PIDF-LO) data		Presence Information Data Format Location Object (PIDF-LO) data
	structure originally defined in RFC 4119 [RFC4119]. There may be		structure originally defined in RFC 4119 [RFC4119]. There may be
	data that is specific to the location not available in the		data that is specific to the location not available in the
	location data structure itself, such as floor plans, tenant and		location data structure itself, such as floor plans, tenant and
	building owner contact data, Heating, Ventilation and Air		building owner contact data, heating, ventilation and air
	Conditioning (HVAC) status, etc.		conditioning (HVAC) status, etc.
			Data Associated with a Call: While information is carried in the
			call setup procedure itself (as part of the SIP headers as well as
			in the body of the SIP message), there is additional data known by
			the device making the call, or a service provider in the path of
			the call. This information may include the service provider
			contact information, subscriber identity and contact information,
			the type of service the service provider and access network
			provider offer, what kind of device is being used, etc. Some data
			is device or service dependent data. For example, a car
			telematics system may have crash information. A medical
			monitoring device may have sensor data.
	Data Associated with a Caller: This is personal data about a caller,		Data Associated with a Caller: This is personal data about a caller,
	such as medical information and emergency contact data.		such as medical information and emergency contact data.
	This document only defines data structures relevant to data		This document only defines data structures relevant to data
	associated with the call. Other forms of additional data may use		associated with the call. Other forms of additional data may use
	this mechanism to carry data, but those blocks are not defined in		this mechanism to carry data, but those blocks are not defined in
	this document.		this document.
	Data structures are defined for such data, and a means of conveying		For interoperability, there needs to be a common way for the
	the data by including a Uniform Resource Identifier (URI) in an		information conveyed to a PSAP to be encoded and identified.
	existing SIP header field, the Call-Info header, which is specified		Identification allows emergency services authorities to know during
	in Section 20.9 of [RFC3261]. For this purpose a new token, namely		call processing which types of data are present and to determine if
	'emergencyCallData' is defined to be carried in the "purpose"		they wish to access it. A common encoding allows the data to be
	parameter. If the "purpose" parameter is set to 'emergencyCallData'		accessed. This document defines the data structures and a way to
	then the Call-Info header contains a HTTPS URL that resolves to a		communicate the information in several ways. Although current
	data structure with information about the call, or is a CID (content		standization efforts around IP-based emergency services are focused
	indirection) that allows the data structure to be placed in the body		on the Session Initiation Protocol (SIP) and HTTP the data structures
	of the message. The "purpose" parameter also contains an indication		in XML format described in this document are usable for other
	of what kind of data is available at the URI. As such, the		communication systems as well. In Section 3 the data structures are
	additional data may reside on an external database, or may be		defined and the SIP/HTTP transport components are defined in
	contained within the body of the SIP message.		Section 4 to offer a clear separation between the two.
	Section 10 shows a SIP INVITE example containing such a Call-Info
	header using the purpose parameter.
	Besides a service provider in the path of a call, the access network
	provider (which may provide location in the form of a PIDF-LO
	[RFC4119] from a location server via a location configuration
	protocol) also has similar information that may be valuable to the
	PSAP. This information is not specific to the location itsef, but
	rather provides descriptive information having to do with the
	immediate circumstances about the provision of the location (who the
	access network is, how to contact that entity, what kind of service
	the access network provides, subscriber information, etc.). This
	data is similar in nearly every respect to the data known by service
	providers in the path of the call. When the access network provider
	and service provider are separate entities, the access network does
	not participate in the application layer signaling (and hence cannot
	add a Call-Info' header field to the SIP message), but may provide
	location information to assist in locating the caller's device. The
	'provided-by' element of the PIDF-LO is a mechanism for the access
	network to supply the information about the entity or organization
	that supplied this location information. For this reason, this
	document describes a namespace per [RFC4119] for inclusion in the
	"provided-by" element of a PIDF-LO for adding information known to
	the access network.
	More technically, the data structure described in this document is		More technically, the data structure described in this document is
	represented as one or more "blocks" of information. Each of the		represented as one or more "blocks" of information. Each of the
	blocks is a Multipurpose Internet Mail Extensions (MIME) type, and an		blocks is an XML structure with an associated Multipurpose Internet
	extensible set of these types constitute the data set. A registry is		Mail Extensions (MIME) type for encapsulation, and an extensible set
	defined to list the block types that may be included.		of these types constitute the data set. A registry is defined to
			list the block types that may be included.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	This document also uses terminology from [RFC5012]. We use the term		This document also uses terminology from [RFC5012]. We use the term
	service provider to refer to an Application Service Provider (ASP) or		service provider to refer to an Application Service Provider (ASP) or
	to Voice Service Provider (VSP), which is a specific type of ASP.		to Voice Service Provider (VSP), which is a specific type of ASP.
	With the term "Access Network Provider" we refer to the Internet		With the term "Access Network Provider" we refer to the Internet
	Access Provider (IAP) and the Internet Service Provider (ISP) without		Access Provider (IAP) and the Internet Service Provider (ISP) without
	further distinguishing these two entities, since the difference		further distinguishing these two entities, since the difference
	between the two is not relevant for this document. Note that the		between the two is not relevant for this document. Note that the
	roles of ASP and access network provider may be provided by a single		roles of ASP and access network provider may be provided by a single
	company.		company.
	In the data block definitions, the "Use:" values are specified as one		In the data block definitions, see Section 3, the values for the
	of:		"Use:" label are specified as one of:
	'Mandatory': means they must be present in the data structure.		'Required': means they must be present in the data structure.
	'Conditional': means they must be present unless the specified		'Conditional': means they must be present unless the specified
	condition is met, in which case the they may be present.		condition is met, in which case the they may be present.
	'Optional': means they may be present.		'Optional': means they may be present.
	3. Data Structure Overview		3. Data Structures
	The following section defines an initial set of blocks which may be		This section defines the following five data structures, each as a
	sent by value or by reference in SIP signaling or within a PIDF-LO.		data block. For each block we define the MIME type, and the XML data
	For each block, we define the MIME type, and the XML data structure		structure
	for the block. The following blocks are defined:
	'Data Provider': This block supplies name and contact information		'Data Provider': This block supplies name and contact information
	for the entity that created the data.		for the entity that created the data. Section 3.1 provides the
			details.
	'Service Information': This block supplies information about the		'Service Information': This block supplies information about the
	service provided by a service provider.		service. The description can be found in Section 3.2.
	'Device Information': This block supplies information about the		'Device Information': This block supplies information about the
	device placing the call.		device placing the call. Device information can be found in
			Section 3.3.
	'Owner/Subscriber': This block supplies information about the owner		'Owner/Subscriber': This block supplies information about the owner
	of the device or about the subscriber of the application service.		of the device or about the subscriber. Details can be found in
			Section 3.4.
	'Comment': This block provides a way to supply free form human		'Comment': This block provides a way to supply free form human
	readable text to the PSAP or emergency responders.		readable text to the PSAP or emergency responders. This simple
			structure is defined in Section 3.5.
	PSAPs and emergency responders can examine the type of data provided
	and selectively retrieve the data each they are interested in, while
	forwarding all of it (the values or references) to downstream
	entities.
	Blocks can be sent by value (the data in the SIP body or PIDF-LO) or
	by reference (the data is retrieved via HTTPS from an external
	server). Data may be provided by the device and/or one or more
	service providers. For example, the device may provide device
	specific information by value, a telematics service provider may
	provide its contact data and data derived from the sensor data (e.g.,
	injury prediction) by reference, and an access network provider may
	provide contact information by value, all in the same SIP INVITE.
	The access network provider may supply additional data as well, by
	including the data within a Provided-By element of a PDIF-LO it
	returns for emergency use (e.g., if requested with a HELD
	"responseTime" attribute of "emergencyRouting" or "emergencyDispatch"
	[RFC5985]). Access network providers are expected to normally supply
	such information by reference (by including an HTTPS URI within the
	Provided-By element). This document defines a namespace and adds the
	namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].
	4. Transmitting Blocks of Additional Data
	One or more blocks of data registered in the Emergency Call
	Additional Data registry, as defined in Section 14.1, may be included
	or referenced in the SIP signaling (using the Call-Info header field)
	or in the provided-by element of a PIDF-LO. Each block is a MIME
	type, and any set of blocks may be included.
	Additional data about a call is defined as a series of MIME objects,
	each with an XML data structure contained inside. As usual, whenever
	more than one MIME part is included in the body of a message, MIME-
	multipart (i.e., 'multipart/mixed') encloses them all. The sections
	below define the XML schema and MIME types used for each block. When
	additional data is passed by value in the SIP signaling, each CID URL
	points to one block in the body. Multiple URIs are used within a
	Call-Info header field (or multiple Call-Info header fields) to point
	to multiple blocks. When additional data is provided by reference
	(in SIP signaling or Provided-By), each HTTPS URL references one
	block; the data is retrieved with an HTTP GET operation, which
	returns one of the blocks as an XML object.
	A registry of allowed types is created by this document. Every block
	must be one of the types in the registry.
	In regions where callers can elect to suppress certain personally
	identifying information, the network or PSAP functionality can
	inspect privacy flags within the SIP headers to determine what
	information may be passed, stored, or displayed to comply with local
	policy or law.
	Each entity adding additional data MUST supply the "Data Provider"
	block. All other blocks are optional, but each entity SHOULD supply
	any blocks where it has at least some of the information in the
	block.
	4.1. Transmitting blocks using Call-Info
	A URI to a block MAY be inserted in a SIP request or response method
	(most often INVITE or MESSAGE) with a Call-Info header field
	containing a purpose of "emergencyCallData" together with the type of
	data available at the URI. The type of data is denoted by including
	the root of the MIME type (not including the emergencyCall prefix and
	the +xml suffix) with a "." separator. For example, when
	referencing a block with MIME type 'application/
	emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
	'emergencyCallData.ProviderInfo'. An example "Call-Info" header
	field for this would be:
	Call-Info: https://www.example.com/23sedde3;
	purpose="emergencyCallData.ProviderInfo"
	The Call-info header with purpose='emergencyCallData' MUST only be
	sent on an emergency call, which can be ascertained by the presence
	of an emergency service urn in a Route header of a SIP message.
	If the data is provided by reference, it may be retrieved with an
	HTTPS GET from the URI. The URI MUST specify an HTTPS scheme, and
	consequently Transport Layer Security (TLS) protection is applied.
	The data may also be supplied by value in a SIP message. In this
	case, Content Indirection (CID) [RFC2392] is used, with the CID URL
	referencing the MIME body part.
	More than one Call-Info header with an emergencyCallData purpose can
	be expected, but at least one MUST be provided. The device MUST
	provide one if it knows no service provider is in the path of the
	call. The device MAY insert one if it uses a service provider. Any
	service provider in the path of the call MUST insert its own. For
	example, a device, a telematics service provider in the call path, as
	well as the mobile carrier 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 emergency call and cannot reasonably be
	expected to determine that it is an emergency call. In that case,
	that service provider is not expected to provide emergencyCallData.
	4.2. Transmitting blocks by reference using Provided-By
	The 'emergencyCallDataReference' element is used to transmit an
	additional data block by reference within a 'Provided-By' element of
	a PIDF-LO. The 'emergencyCallDataReference' element has two
	attributes: 'ref' to specify the URL, and 'purpose' to indicate the
	type of data block referenced. The value of 'ref' is an HTTPS URL
	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
	field (as specified in section Section 4.1, Transmitting blocks using
	Call-Info).
	For example, to reference a block with MIME type 'application/
	emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
	'emergencyCallData.ProviderInfo'. An example
	'emergencyCallDataReference' element for this would be:
	<emergencyCallDataReference ref="https://www.example.com/23sedde3"
	purpose="emergencyCallData.ProviderInfo"/>
	4.3. Transmitting blocks by value using Provided-By
	It is RECOMMENDED that access networks supply the data specified in
	this document by reference, but they MAY provide the data by value.
	The 'emergencyCallDataValue' element is used to transmit an
	additional data block by value within a 'Provided-By' element of a
	PIDF-LO. The 'emergencyCallDataValue' element has one attribute:
	'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
	specified in Section 4.1, and in Section 4.1). The same XML
	structure as would be wrapped in the corresponding MIME type is
	placed inside the emergencyCallDataValue element.
	For example:
	<provided-by: xmlns="urn:ietf:params:xml:ns:
	emergencyCallAddlData">
	<emergencyCallDataValue purpose=
	"emergencyCallData.ProviderInfo">
	<ProviderID>HooThrooPoo</ProviderID>
	<ProviderIDSeries>NENA</ProviderIDSeries>
	<TypeOfProviderID>Access Infrastructure Provider
	</TypeOfProviderID>
	<ContactURI>sip:15555550987@burf.example.com;user=phone
	</ContactURI>
	</emergencyCallDataValue>
	</provided-by>
	Example Provided-By by Value.		Note that the xCard format is re-used in some of the data structures
			to provide contact information. In a xCard there is no way to
			specify a "main" telephone number. These numbers are useful to
			emergency responders who are called to a large enterprise. This
			document adds a new property value to the "tel" property of the TYPE
			parameter called "main". It can be used in any xCard in additional
			data.
	5. Data Provider Information		3.1. Data Provider Information
	This block is intended to be provided by any service provider in the		This block is intended to be provided by any service provider in the
	path of the call or the access network provider. It includes		path of the call or the access network provider. It includes
	identification and contact information. This block SHOULD be		identification and contact information. This block SHOULD be
	provided by every service provider in the call path, and by the		provided by every service provider in the call path, and by the
	access network provider. Devices MAY use this block to provide		access network provider. Devices MAY use this block to provide
	identifying information. The MIME subtype is "application/		identifying information. The MIME subtype is "application/
	emergencyCall.ProviderInfo+xml".		emergencyCall.ProviderInfo+xml".
	5.1. Data Provider String		3.1.1. Data Provider String
	Data Element: Data Provider String		Data Element: Data Provider String
	Use: Required		Use: Required
	XML Element: <DataProviderString>		XML Element: <DataProviderString>
	Description: This is a plain language string suitable for displaying		Description: This is a plain language string suitable for displaying
	the name of the service provider that created the additional data		the name of the service provider that created the additional data
	structure. If the device created the structure the value is		structure. If the device created the structure the value is
	identical to the contact header in the SIP INVITE.		identical to the contact header in the SIP INVITE.
	Reason for Need: Inform the call taker of the identity of the entity		Reason for Need: Inform the call taker of the identity of the entity
	providing the additional call data structure.		providing the additional call data structure.
	How Used by Call Taker: Allows the call taker to interpret the data		How Used by Call Taker: Allows the call taker to interpret the data
	in this structure. The source of the information often influences		in this structure. The source of the information often influences
	how the information is used, believed or verified.		how the information is used, believed or verified.
	5.2. Data Provider ID		3.1.2. Data Provider ID
	Data Element: Data Provider ID		Data Element: Data Provider ID
	Use: Conditional. Must be provided if the service provider is		Use: Conditional. Must be provided if the service provider is
	located in a jurisdiction that maintains such ids. Devices are		located in a jurisdiction that maintains such ids. Devices are
	not required to provide it.		not required to provide it.
	XML Element: <ProviderID>		XML Element: <ProviderID>
	Description: A jurisdiction specific code for the provider shown in		Description: A jurisdiction specific code for the provider shown in
	the <DataProvidedBy> element that created the structure of the		the <DataProvidedBy> element that created the structure of the
	call. This data SHOULD be provided if the local jurisdiction		call. This data SHOULD be provided if the local jurisdiction
	maintains such an ID list. For example, in North America, this		maintains such an ID list. For example, in North America, this
	would be a "NENA Company ID". Devices SHOULD NOT use this		would be a "NENA Company ID". Devices SHOULD NOT use this
	element.		element.
	Reason for Need: Inform the call taker of the identity of the entity		Reason for Need: Inform the call taker of the identity of the entity
	providing the additional call data structure.		providing the additional call data structure.
	How Used by Call Taker: Where jurisdictions have lists of providers		How Used by Call Taker: Where jurisdictions have lists of providers
	the Data Provider ID can be useful.		the Data Provider ID can be useful.
	5.3. Data Provider ID Series		3.1.3. Data Provider ID Series
	Data Element: Data Provider ID Series		Data Element: Data Provider ID Series
	Use: Conditional. If Data Provider ID is provided, Data Provider ID		Use: Conditional. If Data Provider ID is provided, Data Provider ID
	Series is required.		Series is required.
	XML Element: <ProviderIDSeries>		XML Element: <ProviderIDSeries>
	Description: Identifies the issuer of the the ProviderId. A		Description: Identifies the issuer of the the ProviderId. A
	registry will reflect the following valid entries:		registry will reflect the following valid entries:
	* NENA		* NENA
	* EENA		* EENA
	Reason for Need: Identifies how to interpret the Data Provider ID.		Reason for Need: Identifies how to interpret the Data Provider ID.
	How Used by Call Taker: Determines which provider ID registry to		How Used by Call Taker: Determines which provider ID registry to
	consult for more information		consult for more information
	5.4. Type of Data Provider		3.1.4. Type of Data Provider
	Data Element: Type of Data Provider ID		Data Element: Type of Data Provider ID
	Use: Conditional. If Data Provider ID is provided, Type of Data		Use: Conditional. If Data Provider ID is provided, Type of Data
	Provider ID is required.		Provider ID is required.
	XML Element: <TypeOfProviderID>		XML Element: <TypeOfProviderID>
	Description: Identifies the type of data provider id being supplied		Description: Identifies the type of data provider id being supplied
	in the ProviderId data element. A registry will reflect the		in the ProviderId data element. A registry with an initial set of
	following valid entries:		values is shown in the table below.
	* Access Network Provider
	* Service Provider
	* Service Provider Subcontractor
	* Telematics Provider
	* Relay Provider		+------------------------------+------------------------------------+
			| Token | Description |
			+------------------------------+------------------------------------+
			|Access Network Provider | Access network service provider |
			|Service Provider | Calling or Origination telecom SP |
			|Service Provider Subcontractor| A contractor to another kind of SP |
			|Telematics Provider | A sensor based SP, especially |
			| | vehicle based |
			|Language Translation Provider | A spoken language translation SP |
			|Expert Advice Provider | An SP giving expert advice |
			|Emergency Modality Translation| An emergency call specific |
			| | modality translation service |
			| | e.g. for sign language |
			|Relay Provider | A interpretation SP, for example, |
			| | video relay for sign language |
			| | interpreting |
			|Other | Any other type of service provider |
			+------------------------------+------------------------------------+
	* Other		Figure 1: Type of Data Provider ID Registry
	Reason for Need: Identifies what kind of data provider this is.		Reason for Need: Identifies what kind of data provider this is.
	How Used by Call Taker: To decide who to contact when further		How Used by Call Taker: To decide who to contact when further
	information is needed		information is needed
	5.5. Data Provider Contact URI		3.1.5. Data Provider Contact URI
	Data Element: Data Provider Contact URI		Data Element: Data Provider Contact URI
	Use: Required		Use: Required
	XML Element: <ContactURI>		XML Element: <ContactURI>
	Description: For a service provider the contact SHOULD be a contact		Description: For a service provider the contact SHOULD be a contact
	URI. This MUST be a SIP URI. If a telephone number is the		URI. This MUST be a SIP URI. If a telephone number is the
	contact address it should be provided in the form of		contact address it should be provided in the form of
	skipping to change at page 13, line 31 ¶		skipping to change at page 10, line 17 ¶
	owner of the device. When provided by a service provider, this		owner of the device. When provided by a service provider, this
	would be a URI to a 24/7 support organization tasked to provide		would be a URI to a 24/7 support organization tasked to provide
	PSAP support for this emergency call.		PSAP support for this emergency call.
	Reason for Need: Additional data providers may need to be contacted		Reason for Need: Additional data providers may need to be contacted
	for error or other unusual circumstances.		for error or other unusual circumstances.
	How Used by Call Taker: To contact the supplier of the additional		How Used by Call Taker: To contact the supplier of the additional
	data for assistance in handling the call.		data for assistance in handling the call.
	5.6. Data Provider Languages(s) Supported		3.1.6. Data Provider Languages(s) Supported
	Data Element: Data Provider Language(s) supported		Data Element: Data Provider Language(s) supported
	Use: Conditional		Use: Conditional
	XML Element: <Language>		XML Element: <Language>
	Description: The language used by the entity at the Data Provider		Description: The language used by the entity at the Data Provider
	Contact URI as an alpha 2-character code as defined in ISO		Contact URI as an alpha 2-character code as defined in ISO
	639-1:2002 Codes for the representation of names of languages --		639-1:2002 Codes for the representation of names of languages --
	skipping to change at page 14, line 4 ¶		skipping to change at page 10, line 31 ¶
	Use: Conditional		Use: Conditional
	XML Element: <Language>		XML Element: <Language>
	Description: The language used by the entity at the Data Provider		Description: The language used by the entity at the Data Provider
	Contact URI as an alpha 2-character code as defined in ISO		Contact URI as an alpha 2-character code as defined in ISO
	639-1:2002 Codes for the representation of names of languages --		639-1:2002 Codes for the representation of names of languages --
	Part 1: Alpha-2 code Multiple instances of this element may occur.		Part 1: Alpha-2 code Multiple instances of this element may occur.
	Order is significant; preferred language should appear first.		Order is significant; preferred language should appear first.
	This data is required if a Data Provider Contact URI is provided.		This data is required if a Data Provider Contact URI is provided.
	The content must reflect the languages supported at the contact		The content must reflect the languages supported at the contact
	URI.		URI.
	Reason for Need: Information needed to determine if emergency		Reason for Need: Information needed to determine if emergency
	service authority can communicate with the service provider or if		service authority can communicate with the service provider or if
	an interpreter will be needed.		an interpreter will be needed.
	How Used by Call Taker: If call taker cannot speak language(s)		How Used by Call Taker: If call taker cannot speak language(s)
	supported by the service provider, a translation service will need		supported by the service provider, a translation service will need
	to be added to the conversation.		to be added to the conversation.
	5.7. xCard of Data Provider		3.1.7. xCard of Data Provider
	Data Element: xCard of Data Provider		Data Element: xCard of Data Provider
	Use: Optional		Use: Optional
	XML Element: <DataProviderContact>		XML Element: <DataProviderContact>
	Description: There are many fields in the xCARD and the creator of		Description: There are many fields in the xCARD and the creator of
	the data structure is encouraged to provide as much information as		the data structure is encouraged to provide as much information as
	they have available. N, ORG, ADR, TEL, EMAIL are suggested at a		they have available. N, ORG, ADR, TEL, EMAIL are suggested at a
	minimum. N should contain name of support group or device owner		minimum. N should contain name of support group or device owner
	as appropriate. If more than one TEL property is provided, a		as appropriate. If more than one TEL property is provided, a
	parameter from the vCard Property Value registry MUST be specified		parameter from the vCard Property Value registry MUST be specified
	skipping to change at page 15, line 5 ¶		skipping to change at page 11, line 26 ¶
	and is hereinafter referred to as "xCard"		and is hereinafter referred to as "xCard"
	Reason for Need: Information needed to determine additional contact		Reason for Need: Information needed to determine additional contact
	information.		information.
	How Used by Call Taker: Assists call taker by providing additional		How Used by Call Taker: Assists call taker by providing additional
	contact information that may not be included in the SIP invite or		contact information that may not be included in the SIP invite or
	the PIDF-LO.		the PIDF-LO.
	5.8. Subcontractor Principal		3.1.8. Subcontractor Principal
	Data Element: Subcontractor Principal		Data Element: Subcontractor Principal
	XML Element: <SubcontratorPrincipal>		XML Element: <SubcontratorPrincipal>
	Description: If the data provider is a subcontractor to another		Description: If the data provider is a subcontractor to another
	provider such as an access infrastructure provider or telematics		provider such as an access infrastructure provider or telematics
	provider, this element contains the DataProviderString of the		provider, this element contains the DataProviderString of the
	service provider to indicate which provider the subcontractor is		service provider to indicate which provider the subcontractor is
	working for. This data is required if the Data Provider type is		working for. This data is required if the Data Provider type is
	subcontractor.		subcontractor.
	Reason for Need: Identify the entity the subcontractor works for.		Reason for Need: Identify the entity the subcontractor works for.
	How Used by Call Taker: Allows the call taker to understand what the		How Used by Call Taker: Allows the call taker to understand what the
	relationship between data providers and the service providers in		relationship between data providers and the service providers in
	the path of the call are.		the path of the call are.
	5.9. Subcontractor Priority		3.1.9. Subcontractor Priority
	Data Element: Subcontractor Priority		Data Element: Subcontractor Priority
	Use: Required		Use: Required
	XML Element: <SubcontractorPriority>		XML Element: <SubcontractorPriority>
	Description: If the subcontractor should be contacted first, this		Description: If the subcontractor should be contacted first, this
	element should have a "sub" value. If the access or origination		element should have a "sub" value. If the access or origination
	service provider should be contacted first, this element should		service provider should be contacted first, this element should
	have a "main" value. This data is required if the Data Provider		have a "main" value. This data is required if the Data Provider
	type is "subcontractor".		type is "subcontractor".
	Reason for Need: Inform the call taker whether the network operator		Reason for Need: Inform the call taker whether the network operator
	or the subcontractor should be contacted first if support is		or the subcontractor should be contacted first if support is
	needed.		needed.
	How Used by Call Taker: To decide which entity to contact first if		How Used by Call Taker: To decide which entity to contact first if
	assistance is needed.		assistance is needed.
	5.10. emergencyCall.ProviderInfo XML Schema		3.1.10. emergencyCall.ProviderInfo Example
	<?xml version="1.0"?>
	<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	elementFormDefault="qualified"
	ttributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:simpleType name="iso3166a2">
	<xs:restriction base="xs:token">
	<xs:pattern value="[A-Z]{2}"/>
	</xs:restriction>
	</xs:simpleType>
	<xs:element name="emergencyCall.ProviderInfo">
	<xs:complexType>
	<xs:sequence>
	<xs:element name="DataProviderString"
	type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="ProviderID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="ProviderIDSeries"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="TypeOfProvider"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="ContactURI" type="xs:anyURI"
	minOccurs="1" maxOccurs="1"/>
	<xs:element name="Language" type="ad:iso3166a2"
	minOccurs="0" maxOccurs="unbounded" />
	<xs:element name="DataProviderContact"
	type="xc:vcardType" minOccurs="0"
	maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	</xs:schema>
	Figure 1: emergencyCall.ProviderInfo XML Schema
	5.11. emergencyCall.ProviderInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<ad:emergencyCall.ProviderInfo		<ad:emergencyCall.ProviderInfo
	xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"		xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<ad:DataProviderString>Example VoIP Provider		<ad:DataProviderString>Example VoIP Provider
	</ad:DataProviderString>		</ad:DataProviderString>
	<ad:ProviderID>ID123</ad:ProviderID>		<ad:ProviderID>ID123</ad:ProviderID>
	<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>		<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
	<ad:TypeOfProvider>Service Provider</ad:TypeOfProvider>		<ad:TypeOfProvider>Service Provider</ad:TypeOfProvider>
	skipping to change at page 19, line 4 ¶		skipping to change at page 14, line 27 ¶
	http://www.tschofenig.priv.at/key.asc		http://www.tschofenig.priv.at/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://www.tschofenig.priv.at</uri>		<uri>http://www.tschofenig.priv.at</uri>
	</url>		</url>
	</vcard>		</vcard>
	</xc:DataProviderContact>		</xc:DataProviderContact>
	</ad:emergencyCall.ProviderInfo>		</ad:emergencyCall.ProviderInfo>
	Figure 2: emergencyCall.ProviderInfo Example		Figure 2: emergencyCall.ProviderInfo Example
	6. 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.SvcInfo+xml".
	6.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
	or residence caller. Currently, the only valid entries are		or residence caller. Currently, the only valid entries are
	'Business' or 'Residence'.		'Business' or 'Residence'.
	skipping to change at page 20, line 5 ¶		skipping to change at page 15, line 20 ¶
	responders. As the information is not always available, and the		responders. As the information is not always available, and the
	registry is not all encompassing, this is at best advisory		registry is not all encompassing, this is at best advisory
	information, but since it mimics a similar capability in some		information, but since it mimics a similar capability in some
	current emergency calling systems, it is known to be valuable.		current emergency calling systems, it is known to be valuable.
	The service provider uses its best information (such as a rate		The service provider uses its best information (such as a rate
	plan, facilities used to deliver service or service description)		plan, facilities used to deliver service or service description)
	to determine the information and is not responsible for		to determine the information and is not responsible for
	determining the actual characteristics of the location where the		determining the actual characteristics of the location where the
	call originates from.		call originates from.
	6.2. Service Delivered by Provider to End User		3.2.2. Service Delivered by Provider to End User
	Data Element: Service Delivered by Provider to End User		Data Element: Service Delivered by Provider to End User
	Use: Required		Use: Required
	XML Element: <SvcDelByProvider>		XML Element: <SvcDelByProvider>
	Description: This defines the type of service the end user has		Description: This defines the type of service the end user has
	subscribed to. The implied mobility of this service can not be		subscribed to. The implied mobility of this service can not be
	relied upon. A registry defined in this document will reflect the		relied upon. A registry with a initial set of values is defined
	following initial valid entries:		in the table below.
	* Wireless Telephone Service: Includes Satellite, CDMA, GSM, Wi-
	Fi, WiMAX, UTMS/WCDMA, LTE (Long Term Evolution)
	* Fixed Public Pay/Coin telephones: Any coin or credit card
	operated device.
	* One way outbound service
	* Inmate call/service
	* Soft dialtone/quick service/warm disconnect/suspended
	* Multi-line telephone system (MLTS): Includes all PBX, Centrex,
	key systems, Shared Tenant Service.
	* Sensor, unattended: Includes devices that generate DATA ONLY.
	This is one-way information exchange and there will be no other
	form of communication.
	* Sensor, attended: Includes devices that are supported by a
	monitoring service provider or automatically open a two-way
	communication path.
	* Wireline: Plain Old Telephone Service (POTS).
	* VoIP Telephone Service: A type of service that offers
	communication over internet protocol, such as Fixed, Nomadic,
	Mobile, Unknown
	* Relay Service: a type of service where there is a human 3rd		+--------+----------------------------------------+
	party agent who provides some kind of additional assistance to		| Name | Description |
	the caller. Includes sign language relay and telematics		+--------+----------------------------------------+
	services which provide a service assistant on the call.		| Wrless | Wireless Telephone Service: Includes |
			| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
			| | LTE (Long Term Evolution) |
			| Coin | Fixed Public Pay/Coin telephones: Any |
			| | coin or credit card operated device |
			| 1way | One way outbound service |
			| Prison | Inmate call/service |
			| Temp | Soft dialtone/quick service/warm |
			| | disconnect/suspended |
			| MLTS | Multi-line telephone system: Includes |
			| | all PBX, Centrex, key systems, |
			| | Shared Tenant Service |
			| SenseU | Sensor, unattended: Includes devices |
			| | that generate DATA ONLY. This is |
			| | one-way information exchange and |
			| | there will be no other form of |
			| | communication |
			| SenseA | Sensor, attended: Includes devices |
			| | that are supported by a monitoring |
			| | service provider or automatically |
			| | open a two-way communication path |
			| POTS | Wireline: Plain Old Telephone Service |
			| VOIP | VoIP Telephone Service: A type of |
			| | service that offers communication |
			| | over internet protocol, such as Fixed|
			| | Nomadic, Mobile, ... |
			| Remote | Off premise extension |
			| Relay | Relay Service: a type of service where |
			| | there is a human 3rd party agent who |
			| | provides some kind of additional |
			| | assistance to the caller. Includes |
			| | sign language relay and telematics |
			| | services which provide a service |
			| | assistant on the call. |
			+--------+----------------------------------------+
	* Remote (off premise extension)		Figure 3: Service Delivered by Provider to End User Registry
	There can be more than one value returned. For example, a VoIP		More than one value MAY be returned. For example, a VoIP inmate
	inmate telephone service is a reasonable combination.		telephone service is a reasonable combination.
	Reason for Need: Knowing the type of service may assist the PSAP		Reason for Need: Knowing the type of service may assist the PSAP
	with the handling of the call.		with the handling of the call.
	How Used by Call Taker: Call takers often use this information to		How Used by Call Taker: Call takers often use this information to
	determine what kinds of questions to ask callers, and how much to		determine what kinds of questions to ask callers, and how much to
	rely on supportive information. An emergency call from a prison		rely on supportive information. An emergency call from a prison
	is treated differently that a call from a sensor device. As the		is treated differently that a call from a sensor device. As the
	information is not always available, and the registry is not all		information is not always available, and the registry is not all
	encompassing, this is at best advisory information, but since it		encompassing, this is at best advisory information, but since it
	mimics a similar capability in some current emergency calling		mimics a similar capability in some current emergency calling
	systems, it is known to be valuable.		systems, it is known to be valuable.
	6.3. Service Mobility Environment		3.2.3. Service Mobility Environment
	Data Element: Service Mobility Environment		Data Element: Service Mobility Environment
	Use: Required		Use: Required
	XML Element: <SvcMobility>		XML Element: <SvcMobility>
	Description: This provides the service providers view of the		Description: This provides the service providers view of the
	mobility of the caller. As the service provider may not know the		mobility of the caller. As the service provider may not know the
	characteristics of the actual access network used, the value not		characteristics of the actual access network used, the value not
	be relied upon. A registry will reflect the following initial		be relied upon. A registry will reflect the following initial
	valid entries:		valid entries:
	* Mobile: the device should be able to move at any time		* Mobile: the device should be able to move at any time
	skipping to change at page 22, line 14 ¶		skipping to change at page 17, line 29 ¶
	* 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.
	6.4. emergencyCall.SvcInfo XML Schema		3.2.4. emergencyCall.SvcInfo Example
	<?xml version="1.0"?>
	<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified"
	attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCall.SvcInfo">
	<xs:complexType>
	<xs:sequence>
	<xs:element name="SvcEnvironment"
	type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcDelByProvider"
	type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcMobility"
	type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	</xs:schema>
	Figure 3: emergencyCall.SvcInfo XML Schema
	6.5. emergencyCall.SvcInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<svc:emergencyCall.SvcInfo		<svc:emergencyCall.SvcInfo
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<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:emergencyCall.SvcInfo>		</svc:emergencyCall.SvcInfo>
	Figure 4: emergencyCall.SvcInfo Example		Figure 4: emergencyCall.SvcInfo Example
	7. 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.DevInfo+xml".
	7.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
	emergency call. If the device provides the data structure, the		emergency call. If the device provides the data structure, the
	device information SHOULD be provided. If the service provider		device information SHOULD be provided. If the service provider
	provides the structure and it knows what the device is, the		provides the structure and it knows what the device is, the
	service provider SHOULD provide the device information. Often the		service provider SHOULD provide the device information. Often the
	carrier does not know what the device is. It is possible to		carrier does not know what the device is. It is possible to
	receive two Additional Data Associated with a Call data		receive two Additional Data Associated with a Call data
	structures, one created by the device and one created by the		structures, one created by the device and one created by the
	service provider. This information describes the device, not how		service provider. This information describes the device, not how
	it is being used. This data element defines the kind of device		it is being used. This data element defines the kind of device
	making the emergency call. A registry will reflect the following		making the emergency call. The registry with the initial set of
	valid entries:		values is shown below.
	* Cordless handset
	* Fixed phone
	* Mobile handset
	* ATA (analog terminal adapter)
	* Satellite phone
	* Stationary computing device (alarm system, data sensor)
	* Guardian devices
	* Desktop PC
	* Laptop computing device
	* Tablet computing device
	* Alarm system
	* Data sensor
	* Personal beacons (spot)
	* Auto telematics (indicates VEDS data set)
	* Trucking telematics
	* Farm equipment telematics
	* Marine telematics
	* PDA (personal digital assistant)
	* PND (personal navigation device)
	* Smart phone
	* Internet tablet
	* Gaming console
	* Video phone
	* Other text device		+--------+----------------------------------------+
			| Token | Description |
			+--------+----------------------------------------+
			|Cordless| Cordless handset |
			| Fixed | Fixed phone |
			| Mobile | Mobile handset |
			| ATA | analog terminal adapter |
			|Satphone| Satellite phone |
			| FSense | Stationary computing device (alarm |
			| | system, data sensor) |
			| Guard | Guardian devices |
			| Desktop| Desktop PC |
			| Laptop | Laptop computing device |
			| Tablet | Tablet computing device |
			| Alarm | Alarm system |
			| MSense | Mobile Data sensor |
			| Beacon | Personal beacons (spot) |
			| Auto | Auto telematics |
			| Truck | Truck telematics |
			| Farm | Farm equipment telematics |
			| Marine | Marine telematics |
			| PDA | Personal digital assistant |
			| PND | Personal navigation device) |
			| SmrtPhn| Smart phone |
			| Itab | Internet tablet |
			| Game | Gaming console |
			| Video | Video phone |
			| Text | Other text device |
			| NA | Not Available |
			+--------+----------------------------------------+
	* Not Available		Figure 5: Device Classification Registry
	Reason for Need: The device classification implies the capability of		Reason for Need: The device classification implies the capability of
	the calling device and assists in identifying the meaning of the		the calling device and assists in identifying the meaning of the
	emergency call location information that is being presented. For		emergency call location information that is being presented. For
	example, does the device require human intervention to initiate a		example, does the device require human intervention to initiate a
	call or is this call the result of programmed instructions? Does		call or is this call the result of programmed instructions? Does
	the calling device have the ability to update location or		the calling device have the ability to update location or
	condition changes? Is this device interactive or a one-way		condition changes? Is this device interactive or a one-way
	reporting device?		reporting device?
	How Used by Call Taker: May assist with location of caller. For		How Used by Call Taker: May assist with location of caller. For
	example, a cordless handset may be outside or next door. May		example, a cordless handset may be outside or next door. May
	provide calltaker some context about the caller, the capabilities		provide calltaker some context about the caller, the capabilities
	of the device used for the call or the environment the device is		of the device used for the call or the environment the device is
	being used in.		being used in.
	7.2. Device Manufacturer		3.3.2. Device Manufacturer
	Data Element: Device Manufacturer		Data Element: Device Manufacturer
	Use: Optional		Use: Optional
	XML Element: <DeviceMfgr>		XML Element: <DeviceMfgr>
	Description: The plain language name of the manufacturer of the		Description: The plain language name of the manufacturer of the
	device.		device.
	Reason for Need: Used by PSAP management for post-mortem		Reason for Need: Used by PSAP management for post-mortem
	investigation/resolution.		investigation/resolution.
	How Used by Call Taker: Probably not used by calltaker, but by PSAP		How Used by Call Taker: Probably not used by calltaker, but by PSAP
	management.		management.
	7.3. Device Model Number		3.3.3. Device Model Number
	Data Element: Device Model Number		Data Element: Device Model Number
	Use: Optional		Use: Optional
	XML Element: <DeviceModelNr>		XML Element: <DeviceModelNr>
	Description: Model number of the device.		Description: Model number of the device.
	Reason for Need: Used by PSAP management for after action		Reason for Need: Used by PSAP management for after action
	investigation/resolution.		investigation/resolution.
	How Used by Call Taker: Probably not used by calltaker, but by PSAP		How Used by Call Taker: Probably not used by calltaker, but by PSAP
	management.		management.
	7.4. Unique Device Identifier		3.3.4. Unique Device Identifier
	Data Element: Unique Device Identifier		Data Element: Unique Device Identifier
	Use: Optional		Use: Optional
	XML Element: <UniqueDeviceID>		XML Element: <UniqueDeviceID>
	Description: String that identifies the specific device making the		Description: String that identifies the specific device making the
	call or creating an event.		call or creating an event.
	Reason for Need: Uniquely identifies the device as opposed to any		Reason for Need: Uniquely identifies the device as opposed to any
	signaling identifiers encountered in the call signaling stream.		signaling identifiers encountered in the call signaling stream.
	How Used by Call Taker: Probably not used by calltaker they would		How Used by Call Taker: Probably not used by calltaker they would
	need to refer to management for investigation.		need to refer to management for investigation.
	7.5. Type of Device Identifier		3.3.5. Type of Device Identifier
	Data Element: Type of Device Identifier		Data Element: Type of Device Identifier
	Use: Conditional: must be provided if DeviceID is provided		Use: Conditional: must be provided if DeviceID is provided
	XML Element: <TypeOfDeviceID>		XML Element: <TypeOfDeviceID>
	Description: Identifies the type of device identifier being		Description: Identifies the type of device identifier being
	generated in the unique device identifier data element. A		generated in the unique device identifier data element. A
	registry will reflect the following valid entries:		registry with an initial set of values can be seen below:
	* MEID (CDMA)
	* ESN (Electronic Serial Number -- superseded by MEID)
	* MAC (Media Access Control) Address -- IEEE-delegated address of
	any of the interfaces of the device with a MAC address (e.g.,
	Ethernet, WiFi)
	* WiMAX device certificate subject unique identifier
	* IMEI (International Mobile Equipment Identifier - GSM)
	* Unique Device Identifier (UDI) assigned by US FDA for medical
	devices
	* RFID (Radio Frequency Identification)
	* Sensors (types to be identified in a future document version)
	* Manufacturer Serial Number		+--------+----------------------------------------+
			| Token | Description |
			+--------+----------------------------------------+
			| MEID | Mobile Equipment Identifier (CDMA) |
			| ESN | Electronic Serial Number(GSM) |
			| MAC | Media Access Control Address (IEEE) |
			| WiMAX | Device Certificate Unique ID |
			| IMEI | International Mobile Equipment ID (GSM)|
			| UDI | Unique Device Identifier |
			| RFID | Radio Frequency Identification |
			| SN | Manufacturer Serial Number |
			+--------+----------------------------------------+
	* Other		Figure 6: Registry with Device Identifier Types
	Reason for Need: Identifies how to interpret the Unique Device		Reason for Need: Identifies how to interpret the Unique Device
	Identifier.		Identifier.
	How Used by Call Taker: Additional information that may be used to		How Used by Call Taker: Additional information that may be used to
	assist with call handling.		assist with call handling.
	7.6. Device/Service Specific Additional Data Structure		3.3.6. Device/Service Specific Additional Data Structure
	Data Element: Device/service specific additional data structure		Data Element: Device/service specific additional data structure
	Use: Optional		Use: Optional
	XML Element: <DeviceSpecificData>		XML Element: <DeviceSpecificData>
	Description: A URI representing additional data whose schema is		Description: A URI representing additional data whose schema is
	specific to the device or service which created it. An example is		specific to the device or service which created it. An example is
	the VEDs structure for a vehicle telematics device. The URI, when		the VEDs structure for a vehicle telematics device. The URI, when
	dereferenced, MUST yield a data structure defined by the Device/		dereferenced, MUST yield a data structure defined by the Device/
	service specific additional data type value. Different data may		service specific additional data type value. Different data may
	be created by each classification; e.g., telematics creates VEDS		be created by each classification; e.g., telematics creates VEDS
	data set.		data set.
	Reason for Need: Provides device/service specific data that may be		Reason for Need: Provides device/service specific data that may be
	used by the call taker and/or responders.		used by the call taker and/or responders.
	How Used by Call Taker: Provide information to guide call takers to		How Used by Call Taker: Provide information to guide call takers to
	select appropriate responders, give appropriate pre-arrival		select appropriate responders, give appropriate pre-arrival
	instructions to callers, and advise responders of what to be		instructions to callers, and advise responders of what to be
	prepared for. May be used by responders to guide assistance		prepared for. May be used by responders to guide assistance
	provided.		provided.
	7.7. Device/Service Specific Additional Data Structure Type		3.3.7. Device/Service Specific Additional Data Structure Type
	Data Element: Type of Device/service specific additional data		Data Element: Type of Device/service specific additional data
	structure		structure
	Use: Conditional. MUST be provided when Device/service specific		Use: Conditional. MUST be provided when Device/service specific
	additional URI is provided		additional URI is provided
	XML Element: <DeviceSpecificType>		XML Element: <DeviceSpecificType>
	Description: Value from a registry defined by this document to		Description: Value from a registry defined by this document to
	skipping to change at page 28, line 44 ¶		skipping to change at page 23, line 10 ¶
	may assist in emergency response.		may assist in emergency response.
	How Used by Call Taker: This data element allows the end user		How Used by Call Taker: This data element allows the end user
	(calltaker or first responder) to know what type of additional		(calltaker or first responder) to know what type of additional
	data may be available to aid in providing the needed emergency		data may be available to aid in providing the needed emergency
	services.		services.
	Note: Information which is specific to a location or a caller		Note: Information which is specific to a location or a caller
	(person) should not be placed in this section.		(person) should not be placed in this section.
	7.8. Choosing between defining a new type of block or new type of		3.3.8. Choosing between defining a new type of block or new type of
	device/service specific additional data		device/service specific additional data
	For devices that have device or service specific data, there are two		For devices that have device or service specific data, there are two
	choices to carry it. A new block can be defined, or the device/		choices to carry it. A new block can be defined, or the device/
	service specific additional data URL the the DevInfo block can be		service specific additional data URL the the DevInfo block can be
	used and a new type for it defined . The data passed would likely be		used and a new type for it defined . The data passed would likely be
	the same in both cases. Considerations for choosing which mechanism		the same in both cases. Considerations for choosing which mechanism
	to register under include:		to 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
	skipping to change at page 29, line 33 ¶		skipping to change at page 23, line 41 ¶
	DevInfo block, rather than a new block so that implementations are		DevInfo block, rather than a new block so that implementations are
	not tempted to send the data by value. Conversely, data which is		not tempted to send the data by value. Conversely, data which is
	small may best be sent in a separate block so that it can be sent		small may best be sent in a separate block so that it can be sent
	by value		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).
	7.9. emergencyCall.DevInfo XML Schema		3.3.9. emergencyCall.DevInfo Example
	<?xml version="1.0"?>
	<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified"
	attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCall.DevInfo">
	<xs:complexType>
	<xs:sequence>
	<xs:element name="DeviceClassification"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceMfgr"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceModelNr"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="UniqueDeviceID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="TypeOfDeviceID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceSpecificData"
	type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceSpecificType"
	type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	</xs:schema>
	Figure 5: emergencyCallDevInfo XML Schema
	7.10. emergencyCall.DevInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<svc:emergencyCall.DevInfo		<svc:emergencyCall.DevInfo
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<svc:DeviceClassification>Fixed phone</svc:DeviceClassification>		<svc:DeviceClassification>Fixed phone</svc:DeviceClassification>
	<svc:DeviceMfgr>Nokia</svc:DeviceMfgr>		<svc:DeviceMfgr>Nokia</svc:DeviceMfgr>
	<svc:DeviceModelNr>Lumia 800</svc:DeviceModelNr>		<svc:DeviceModelNr>Lumia 800</svc:DeviceModelNr>
	<svc:UniqueDeviceID>35788104</svc:UniqueDeviceID>		<svc:UniqueDeviceID>35788104</svc:UniqueDeviceID>
	<svc:TypeOfDeviceID>IMEI</svc:TypeOfDeviceID>		<svc:TypeOfDeviceID>IMEI</svc:TypeOfDeviceID>
	</svc:emergencyCall.DevInfo>		</svc:emergencyCall.DevInfo>
	Figure 6: emergencyCallDevInfo Example		Figure 7: emergencyCallDevInfo Example
	8. 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".
	8.1. xCard for Subscriber's Data		3.4.1. xCard for Subscriber's Data
	Data Element: xCARD for Subscriber's Data		Data Element: xCARD for Subscriber's Data
	Use: Conditional: Some services (e.g., prepaid phones, initialized		Use: Conditional: Some services (e.g., prepaid phones, initialized
	phones, etc.) may not have this information.		phones, etc.) may not have this information.
	XML Element: <SubscriberData>		XML Element: <SubscriberData>
	Description: Information known by the service provider or device		Description: Information known by the service provider or device
	about the subscriber; e.g., Name, Address, Individual Telephone		about the subscriber; e.g., Name, Address, Individual Telephone
	Number, Main Telephone Number and any other data. N, ORG (if		Number, Main Telephone Number and any other data. N, ORG (if
	appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more		appropriate), ADR, TEL, EMAIL are suggested at a minimum. If more
	than one TEL property is provided, a parameter from the vCard		than one TEL property is provided, a parameter from the vCard
	Property Value registry MUST be specified on each TEL.		Property Value registry MUST be specified on each TEL.
	Reason for Need: When the caller is unable to provide information,		Reason for Need: When the caller is unable to provide information,
	this data may be used to obtain it		this data may be used to obtain it
	How Used by Call Taker: Obtaining critical information about the		How Used by Call Taker: Obtaining critical information about the
	caller and possibly the location when it is not able to be		caller and possibly the location when it is not able to be
	obtained otherwise.		obtained otherwise.
	8.2. emergencyCall.SubInfo XML Schema		3.4.2. emergencyCall.SubInfo Example
	<?xml version="1.0"?>
	<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCall.SubInfo">
	<xs:complexType>
	<xs:sequence>
	<!-- VCard data structure goes in here.
	<xs:element name="SubscriberData"
	type="xc:vcard" minOccurs="0" maxOccurs="1"/>
	-->
	<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	</xs:schema>
	Figure 7: emergencyCall.SubInfo XML Schema
	8.3. emergencyCall.SubInfo Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<ad:emergencyCall.SubInfo		<ad:emergencyCall.SubInfo
	xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.SubInfo"		xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<xc:SubscriberData xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">		<xc:SubscriberData xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards xmlns="urn:ietf:params:xml:ns:vcard-4.0">		<vcards 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>
	skipping to change at page 34, line 16 ¶		skipping to change at page 27, line 4 ¶
	</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>
	</xc:SubscriberData>		</xc:SubscriberData>
	</ad:emergencyCall.SubInfo>		</ad:emergencyCall.SubInfo>
	Figure 8: emergencyCall.SubInfo Example		Figure 8: emergencyCall.SubInfo Example
	9. 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. The mime subtype is		for a general purpose extension mechanism. The mime subtype is
	"application/emergencyCall.Comment+xml"		"application/emergencyCall.Comment+xml"
	9.1. Comment		3.5.1. Comment
	Data Element: EmergencyCall.Comment		Data Element: EmergencyCall.Comment
	Use: Optional		Use: Optional
	XML Element: <Comment>		XML Element: <Comment>
	Description: Human readable text providing additional information to		Description: Human readable text providing additional information to
	the PSAP staff.		the PSAP staff.
	Reason for Need: Explanatory information for values in the data		Reason for Need: Explanatory information for values in the data
	structure		structure
	How Used by Call Taker: To interpret the data provided		How Used by Call Taker: To interpret the data provided
	9.2. emergencyCall.Comment XML Schema		3.5.2. emergencyCall.Comment Example
	<?xml version="1.0"?>		<?xml version="1.0" encoding="UTF-8"?>
	<xs:schema		<sub:emergencyCall.Comment
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"		xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	elementFormDefault="qualified" attributeFormDefault="unqualified">		<sub:Comment xml:lang="en">This is an example text.</sub:Comment>
			</sub:emergencyCall.Comment>
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		Figure 9: EmergencyCall.Comment Example
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCall.Comment">		4. Transport
	<xs:complexType>
	<xs:sequence>
	<xs:element name="Comment"
	type="sub:CommentType" minOccurs="0" maxOccurs="unbounded"/>
	<xs:any namespace="##other" processContents="lax" minOccurs="0"
	maxOccurs="unbounded"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	<xs:complexType name="CommentType">		This section defines how to convey additional data to an emergency
	<xs:simpleContent>		service provider. Two different means are specified: the first uses
	<xs:extension base="xs:string">		the call signaling; the second uses the <provided-by> element of a
	<xs:attribute ref="xml:lang"/>		PIDF-LO [RFC4119].
	</xs:extension>
	</xs:simpleContent>
	</xs:complexType>
	</xs:schema>		1. First, the ability to embed a Uniform Resource Identifier (URI)
			in an existing SIP header field, the Call-Info header, is
			defined. The URI points to the additional data structure. The
			Call-Info header is specified in Section 20.9 of [RFC3261]. This
			document adds a new token with the value 'emergencyCallData' for
			the Call-Info "purpose" parameter. If the "purpose" parameter is
			set to 'emergencyCallData' then the Call-Info header contains
			either an HTTPS URL pointing to an external resource or a CID
			(content indirection) URI that allows the data structure to be
			placed in the body of the SIP message. The "purpose" parameter
			also contains an indication of what kind of data is available at
			the URI.
	Figure 9: EmergencyCall.Comment XML Schema		As the data is conveyed using a URI in the SIP signaling, the
			data itself may reside on an external resource, or may be
			contained within the body of the SIP message. When the URI
			refers to data at an external resource, the data is said to be
			passed by reference. When the URI refers to data contained
			within the body of the SIP message, the data is said to be passed
			by value. A PSAP or emergency responder is able to examine the
			type of data provided and selectively inspect the data it is
			interested in, while forwarding all of it (the values or
			references) to downstream entities.
	9.3. emergencyCall.Comment Example		To be conveyed in a SIP body additional data about a call is
			defined as a series of MIME objects, each with an XML data
			structure contained inside. As usual, whenever more than one
			MIME part is included in the body of a message, MIME-multipart
			(i.e., 'multipart/mixed') encloses them all. This document
			defines the XML schemas and MIME types used for each block. When
			additional data is passed by value in the SIP signaling, each CID
			URL points to one block in the body. Multiple URIs are used
			within a Call-Info header field (or multiple Call-Info header
			fields) to point to multiple blocks. When additional data is
			provided by reference (in SIP signaling or Provided-By), each
			HTTPS URL references one block; the data is retrieved with an
			HTTPS GET operation, which returns one of the blocks as an XML
			object.
	<?xml version="1.0" encoding="UTF-8"?>		2. Second, the ability to embed additional data structures in the
	<sub:emergencyCall.Comment		<provided-by> element of a PIDF-LO [RFC4119] is defined. Besides
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"		a service provider in the call path, the access network provider
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		may also have similar information that may be valuable to the
	<sub:Comment xml:lang="en">This is an example text.</sub:Comment>		PSAP. The access network provider may provide location in the
	</sub:emergencyCall.Comment>		form of a PIDF-LO from a location server via a location
			configuration protocol. The data structures described in this
			document are not specific to the location itsef, but rather
			provides descriptive information having to do with the immediate
			circumstances about the provision of the location (who the access
			network is, how to contact that entity, what kind of service the
			access network provides, subscriber information, etc.). This
			data is similar in nearly every respect to the data known by
			service providers in the path of the call. When the access
			network provider and service provider are separate entities, the
			access network does not participate in the application layer
			signaling (and hence cannot add a Call-Info header field to the
			SIP message), but may provide location information to assist in
			locating the caller's device. The <provided-by> element of the
			PIDF-LO is a mechanism for the access network provider to supply
			the information about the entity or organization that supplied
			this location information. For this reason, this document
			describes a namespace per RFC 4119 for inclusion in the
			<provided-by> element of a PIDF-LO for adding information known
			to the access network provider.
	Figure 10: EmergencyCall.Comment Example		One or more blocks of data registered in the Emergency Call
			Additional Data registry, as defined in Section 9.1, may be included
			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
			one of the types in the registry. Since the data of an emergency
			call may come from multiple sources, the data itself needs
			information describing the source. Consequently, each entity adding
			additional data MUST supply the "Data Provider" block. All other
			blocks are optional, but each entity SHOULD supply any blocks where
			it has at least some of the information in the block.
			4.1. Transmitting Blocks using the Call-Info Header
			A URI to a block MAY be inserted in a SIP request or response method
			(most often INVITE or MESSAGE) with a Call-Info header field
			containing a purpose of "emergencyCallData" together with the type of
			data available at the URI. The type of data is denoted by including
			the root of the MIME type (not including the emergencyCall prefix and
			the +xml suffix) with a "." separator. For example, when
			referencing a block with MIME type 'application/
			emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
			'emergencyCallData.ProviderInfo'. An example "Call-Info" header
			field for this would be:
			Call-Info: https://www.example.com/23sedde3;
			purpose="emergencyCallData.ProviderInfo"
			The Call-info header with purpose='emergencyCallData' MUST only be
			sent on an emergency call, which can be ascertained by the presence
			of an emergency service urn in a Route header of a SIP message.
			If the data is provided by reference, an HTTPS URI MUST be included
			and consequently Transport Layer Security (TLS) protection is applied
			for protecting the retrieval of the information.
			The data may also be supplied by value in a SIP message. In this
			case, Content Indirection (CID) [RFC2392] is used, with the CID URL
			referencing the MIME body part.
			More than one Call-Info header with an emergencyCallData purpose can
			be expected, but at least one MUST be provided. The device MUST
			provide one if it knows no service provider is in the path of the
			call. The device MAY insert one if it uses a service provider. Any
			service provider in the path of the call MUST insert its own. For
			example, a device, a telematics service provider in the call path, as
			well as the mobile carrier 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 emergency call and cannot reasonably be
			expected to determine that it is an emergency call. In that case,
			that service provider is not expected to provide emergencyCallData.
			4.2. Transmitting Blocks by Reference using the Provided-By Element
			The 'emergencyCallDataReference' element is used to transmit an
			additional data block by reference within a 'Provided-By' element of
			a PIDF-LO. The 'emergencyCallDataReference' element has two
			attributes: 'ref' to specify the URL, and 'purpose' to indicate the
			type of data block referenced. The value of 'ref' is an HTTPS URL
			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
			field (as specified in Section 4.1).
			For example, to reference a block with MIME type 'application/
			emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
			'emergencyCallData.ProviderInfo'. An example
			'emergencyCallDataReference' element for this would be:
			<emergencyCallDataReference ref="https://www.example.com/23sedde3"
			purpose="emergencyCallData.ProviderInfo"/>
			4.3. Transmitting Blocks by Value using the Provided-By Element
			It is RECOMMENDED that access networks supply the data specified in
			this document by reference, but they MAY provide the data by value.
			The 'emergencyCallDataValue' element is used to transmit an
			additional data block by value within a 'Provided-By' element of a
			PIDF-LO. The 'emergencyCallDataValue' element has one attribute:
			'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
			specified in Section 4.1, and in Section 4.1). The same XML
			structure as would be wrapped in the corresponding MIME type is
			placed inside the emergencyCallDataValue element.
			For example:
			<provided-by xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData">
			<emergencyCallDataValue purpose="emergencyCallData.ProviderInfo">
			<ProviderID>Test</ProviderID>
			<ProviderIDSeries>NENA</ProviderIDSeries>
			<TypeOfProviderID>Access Infrastructure Provider
			</TypeOfProviderID>
			<ContactURI>sip:15555550987@burf.example.com;user=phone
			</ContactURI>
			</emergencyCallDataValue>
			</provided-by>
			Example Provided-By by Value.
			5. Examples
			This section provides three examples of communicating additional
			data. In Figure 10 additional data is communicated in a SIP INVITE
			per value. In Figure 11 we illustrate how additional data is added
			by a SIP proxy per reference. Finally, an example of conveying
			additional data in the <Provided-By> is illustrated.
	10. Example
	INVITE sips:bob@biloxi.example.com SIP/2.0		INVITE sips:bob@biloxi.example.com SIP/2.0
	Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9		Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
	Max-Forwards: 70		Max-Forwards: 70
	To: Bob <sips:bob@biloxi.example.com>		To: Bob <sips:bob@biloxi.example.com>
	From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl		From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
	Call-ID: 3848276298220188511@atlanta.example.com		Call-ID: 3848276298220188511@atlanta.example.com
	Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,		Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
	<http://www.example.com/alice/> ;purpose=info,		<http://www.example.com/alice/> ;purpose=info,
	<cid:1234567890@atlanta.example.com>		<cid:1234567890@atlanta.example.com>
	;purpose=emergencyCallData.ProviderInfo		;purpose=emergencyCallData.ProviderInfo
	skipping to change at page 36, line 46 ¶		skipping to change at page 32, line 39 ¶
	--boundary1--		--boundary1--
	Content-Type: application/emergencyCall.ProviderInfo+xml		Content-Type: application/emergencyCall.ProviderInfo+xml
	Content-ID: <1234567890@atlanta.example.com>		Content-ID: <1234567890@atlanta.example.com>
	...Additional Data goes here		...Additional Data goes here
	--boundary1--		--boundary1--
	Example: Attaching Additional Data via CID to a SIP INVITE		Figure 10: Example: Attaching Additional Data via CID to a SIP
			INVITE.
	11. Main Telephone Number		INVITE sips:bob@biloxi.example.com SIP/2.0
			Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
			Max-Forwards: 70
			To: Bob <sips:bob@biloxi.example.com>
			From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
			Call-ID: 3848276298220188511@atlanta.example.com
			Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
			<http://www.example.com/alice/> ;purpose=info,
			<https://www.example.com/abc123456/>
			;purpose=emergencyCallData.ProviderInfo
			Geolocation: <cid:target123@atlanta.example.com>
			Geolocation-Routing: no
			Accept: application/sdp, application/pidf+xml,
			application/emergencyCallProviderinfo+xml
			CSeq: 31862 INVITE
			Contact: <sips:alice@atlanta.example.com>
			Content-Type: multipart/mixed; boundary=boundary1
	In a xCard, used extensively in this document, there is no way to		Content-Length: ...
	specify a "Main" telephone number. These numbers are useful to
	emergency responders who are called to a large enterprise. This
	document adds a new Property Value to the "tel" property of the TYPE
	parameter called "main". It can be used in any xCard in additional
	data.
	12. Security Considerations		--boundary1
			Content-Type: application/sdp
			...SDP goes here
			--boundary1
			Content-Type: application/pidf+xml
			Content-ID: <target123@atlanta.example.com>
			PIDF-LO goes here
			--boundary1--
			Figure 11: Example: Attaching Additional Data per Reference in a SIP
			INVITE.
			TBD.
			Figure 12: Example: Attaching Additional Data to Provided-By Element.
			6. XML Schemas
			This section defines the XML schemas of the five data blocks.
			6.1. emergencyCall.ProviderInfo XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:ad="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
			elementFormDefault="qualified"
			ttributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:simpleType name="iso3166a2">
			<xs:restriction base="xs:token">
			<xs:pattern value="[A-Z]{2}"/>
			</xs:restriction>
			</xs:simpleType>
			<xs:element name="emergencyCall.ProviderInfo">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="DataProviderString"
			type="xs:string" minOccurs="1" maxOccurs="1"/>
			<xs:element name="ProviderID"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="ProviderIDSeries"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="TypeOfProvider"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="ContactURI" type="xs:anyURI"
			minOccurs="1" maxOccurs="1"/>
			<xs:element name="Language" type="ad:iso3166a2"
			minOccurs="0" maxOccurs="unbounded" />
			<xs:element name="DataProviderContact"
			type="xc:vcardType" minOccurs="0"
			maxOccurs="1"/>
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
			Figure 13: emergencyCall.ProviderInfo XML Schema
			6.2. emergencyCall.SvcInfo XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			elementFormDefault="qualified"
			attributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:element name="emergencyCall.SvcInfo">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="SvcEnvironment"
			type="xs:string" minOccurs="1" maxOccurs="1"/>
			<xs:element name="SvcDelByProvider"
			type="xs:string" minOccurs="1" maxOccurs="unbounded"/>
			<xs:element name="SvcMobility"
			type="xs:string" minOccurs="1" maxOccurs="1"/>
			<xs:element name="Link"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
			Figure 14: emergencyCall.SvcInfo XML Schema
			6.3. emergencyCall.DevInfo XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			elementFormDefault="qualified"
			attributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:element name="emergencyCall.DevInfo">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="DeviceClassification"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="DeviceMfgr"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="DeviceModelNr"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="UniqueDeviceID"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="TypeOfDeviceID"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="DeviceSpecificData"
			type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="DeviceSpecificType"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
			Figure 15: emergencyCallDevInfo XML Schema
			6.4. emergencyCall.SubInfo XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
			elementFormDefault="qualified" attributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:element name="emergencyCall.SubInfo">
			<xs:complexType>
			<xs:sequence>
			<!-- VCard data structure goes in here.
			<xs:element name="SubscriberData"
			type="xc:vcard" minOccurs="0" maxOccurs="1"/>
			-->
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
			Figure 16: emergencyCall.SubInfo XML Schema
			6.5. emergencyCall.Comment XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			elementFormDefault="qualified" attributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:element name="emergencyCall.Comment">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="Comment"
			type="sub:CommentType" minOccurs="0" maxOccurs="unbounded"/>
			<xs:any namespace="##other" processContents="lax" minOccurs="0"
			maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			<xs:complexType name="CommentType">
			<xs:simpleContent>
			<xs:extension base="xs:string">
			<xs:attribute ref="xml:lang"/>
			</xs:extension>
			</xs:simpleContent>
			</xs:complexType>
			</xs:schema>
			Figure 17: EmergencyCall.Comment XML Schema
			7. Security Considerations
	The information in this data structure will usually be considered		The information in this data structure will usually be considered
	private. HTTPS is specified to require the provider of the		private. HTTPS is specified to require the provider of the
	information to validate the credentials of the requester. While the		information to validate the credentials of the requester. While the
	creation of a PKI that has global scope may be difficult, the		creation of a PKI that has global scope may be difficult, the
	alternatives to creating devices and services that can provide		alternatives to creating devices and services that can provide
	critical information securely are more daunting. The provider may		critical information securely are more daunting. The provider may
	enforce any policy it wishes to use, but PSAPs and responder agencies		enforce any policy it wishes to use, but PSAPs and responder agencies
	should deploy a PKI so that providers of additional data can check		should deploy a PKI so that providers of additional data can check
	the certificate of the client and decide the appropriate policy to		the certificate of the client and decide the appropriate policy to
	enforce based on that certificate.		enforce based on that certificate.
	skipping to change at page 38, line 12 ¶		skipping to change at page 39, line 5 ¶
	emergency authorities could maintain a list of local data providers'		emergency authorities could maintain a list of local data providers'
	credentials provided to it out of band. At a minimum, the emergency		credentials provided to it out of band. At a minimum, the emergency
	authorities could obtain a credential from the DNS entry of the		authorities could obtain a credential from the DNS entry of the
	domain in the Addional Data URI to at least validate that the server		domain in the Addional Data URI to at least validate that the server
	is known to the domain providing the URI.		is known to the domain providing the URI.
	Data provided by devices by reference have similar credential		Data provided by devices by reference have similar credential
	validation issues to service providers, and the solutions are the		validation issues to service providers, and the solutions are the
	same.		same.
	13. Privacy Considerations		8. Privacy Considerations
			[Editor's Note: Text to be re-written.]
			In regions where callers can elect to suppress certain personally
			identifying information, the network or PSAP functionality can
			inspect privacy flags within the SIP headers to determine what
			information may be passed, stored, or displayed to comply with local
			policy or law.
	There is much private data in this information. Local regulations		There is much private data in this information. Local regulations
	may govern what data must be provided in emergency calls, but in		may govern what data must be provided in emergency calls, but in
	general, the emergency call system is often aided by the kinds of		general, the emergency call system is often aided by the kinds of
	information described in this document. There is a tradeoff between		information described in this document. There is a tradeoff between
	the privacy considerations and the utility of the data. Certainly,		the privacy considerations and the utility of the data. Certainly,
	if the data cannot be protected, due to failure to establish (by TLS)		if the data cannot be protected, due to failure to establish (by TLS)
	a secure connection to the data provider, data SHOULD NOT be sent		a secure connection to the data provider, data SHOULD NOT be sent
	unless specifically required by regulation.		unless specifically required by regulation.
	Some forms of data can be sent by value in the SIP signaling or by		Some forms of data can be sent by value in the SIP signaling or by
	value (URL in SIP signaling). When data is sent by value, all		value (URL in SIP signaling). When data is sent by value, all
	intermediaries have access to the data. If the data is private,		intermediaries have access to the data. If the data is private,
	sending by reference is more appropriate.		sending by reference is more appropriate.
	14. IANA Considerations		9. IANA Considerations
	14.1. Registry creation		9.1. Registry creation
	This document creates a new registry called 'Emergency Call		This document creates a new registry called 'Emergency Call
	Additional Data'. The following subregistries are created in		Additional Data'. The following subregistries are created in
	Emergency Call Additional Data:		Emergency Call Additional Data:
	14.1.1. Additional Call Data Provider ID Series Registry		9.1.1. Additional Call Data Provider ID Series Registry
	This document creates a new subregistry called 'Additional Call Data		This document creates a new subregistry called 'Additional Call Data
	Provider ID Series'. As defined in [RFC5226], this registry operates		Provider ID Series'. As defined in [RFC5226], this registry operates
	under "Expert Review" rules. The expert should determine that the		under "Expert Review" rules. The expert should determine that the
	entity requesting a new value is a legitimate issuer of service		entity requesting a new value is a legitimate issuer of service
	provider IDs suitable for use in Additional Call Data.		provider IDs suitable for use in Additional Call Data.
	The content of this registry includes:		The content of this registry includes:
	Name: The identifier which will be used in the ProviderIDSeries		Name: The identifier which will be used in the ProviderIDSeries
	element		element
	Source: The full name of the organization issuing the identifiers		Source: The full name of the organization issuing the identifiers
	URL: A URL to the organization for further information		URL: A URL to the organization for further information
	The values defined are:		The initial set of values is listed in the table below.
	+-----------+-----------+--------------+--------------+		+-----------+-----------+--------------+----------------------+
	| Name | Source | URL |		| Name | Source | URL |
	+-----------+--------------------------+--------------+		+-----------+--------------------------+----------------------+
	| NENA | North American Emergency | www.nena.org |		| NENA | North American Emergency | http://www.nena.org |
	| | Number Association | |		| | Number Association | |
	| EENA | European Emergency | www.eena.org |		| EENA | European Emergency | http://www.eena.org |
	| | Number Association | |		| | Number Association | |
	+-----------+--------------------------+--------------+		+-----------+--------------------------+----------------------+
	RFC Editor Note:
	replace XXXX in the table above with this documents RFC number
	14.1.2. Additional Call Data Service Provider Type Registry		9.1.2. Additional Call Data Service Provider Type Registry
	This document creates a new subregistry called 'Service Provider		This document creates a new subregistry called 'Service Provider
	Type'. As defined in [RFC5226], this registry operates under "Expert		Type'. As defined in [RFC5226], this registry operates under "Expert
	Review". The expert should determine that the proposed new value is		Review". The expert should determine that the proposed new value is
	distinct from existing values and appropriate for use in the		distinct from existing values and appropriate for use in the
	TypeOfServicerProvider element		TypeOfServicerProvider element
	The content of this registry includes:		The content of this registry includes:
	Name: Value to be used in TypeOfServiceProvider.		Name: Value to be used in TypeOfServiceProvider.
	Description: A short description of the type of service provider		Description: A short description of the type of service provider
	The values defined are:		The initial set of values is defined in Figure 1.
	+------------------------------+------------------------------------+
	| Name | Description |
	+------------------------------+------------------------------------+
	|Access Infrastructure Provider| Access network service provider |
	|Service Provider | Calling or Origination telecom SP |
	|Service Provider Subcontractor| A contractor to another kind of SP |
	|Telematics Provider | A sensor based SP, especially |
	| | vehicle based |
	|Relay Provider | A interpretation SP, for example, |
	| | video relay for sign language |
	| | interpretors |
	|Other | Any other type of service provider |
	+------------------------------+------------------------------------+
	RFC Editor Note:
	replace XXXX in the table above with this documents RFC number
	14.1.3. Additional Call Data Service Delivered Registry		9.1.3. Additional Call Data Service Delivered Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Service Delivered'. As defined in [RFC5226], this registry operates		Service Delivered'. As defined in [RFC5226], this registry operates
	under "Expert Review" rules. The expert should consider whether the		under "Expert Review" rules. The expert should consider whether the
	proposed service is unique from existing services and the definition		proposed service is unique from existing services and the definition
	of the service will be clear to implementors and PSAPS/responders.		of the service will be clear to implementors and PSAPS/responders.
	The content of this registry includes:		The content of this registry includes:
	Name: enumeration token of the service.		Name: enumeration token of the service.
	Description: Short description identifying the service.		Description: Short description identifying the service.
	The values defined are:		The initial set of values are defined in Figure 3.
	+--------+----------------------------------------+
	| Name | Description |
	+--------+----------------------------------------+
	| Wrless | Wireless Telephone Service: Includes |
	| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
	| | LTE (Long Term Evolution) |
	| Coin | Fixed Public Pay/Coin telephones: Any |
	| | coin or credit card operated device |
	| 1way | One way outbound service |
	| Prison | Inmate call/service |
	| Temp | Soft dialtone/quick service/warm |
	| | disconnect/suspended |
	| MLTS | Multi-line telephone system: Includes |
	| | all PBX, Centrex, key systems, |
	| | Shared Tenant Service |
	| SenseU | Sensor, unattended: Includes devices |
	| | that generate DATA ONLY. This is |
	| | one-way information exchange and |
	| | there will be no other form of |
	| | communication |
	| SenseA | Sensor, attended: Includes devices |
	| | that are supported by a monitoring |
	| | service provider or automatically |
	| | open a two-way communication path |
	| POTS | Wireline: Plain Old Telephone Service |
	| VOIP | VoIP Telephone Service: A type of |
	| | service that offers communication |
	| | over internet protocol, such as Fixed|
	| | Nomadic, Mobile, ... |
	+--------+----------------------------------------+
	14.1.4. Additional Call Data Device Classification Registry		9.1.4. Additional Call Data Device Classification Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Device Classification'. As defined in [RFC5226], this registry		Device Classification'. As defined in [RFC5226], this registry
	operates under "Expert Review" rules. The expert should consider		operates under "Expert Review" rules. The expert should consider
	whether the proposed class is unique from existing classes and the		whether the proposed class is unique from existing classes and the
	definition of the class will be clear to implementors and PSAPS/		definition of the class will be clear to implementors and PSAPS/
	responders.		responders.
	The content of this registry includes:		The content of this registry includes:
	Name: enumeration token of the device classification.		Name: enumeration token of the device classification.
	Description: Short description identifying the device type.		Description: Short description identifying the device type.
	The values defined are:		The initial set of values are defined in Figure 5.
	+--------+----------------------------------------+
	| Name | Description |
	+--------+----------------------------------------+
	|Cordless| Cordless handset |
	| Fixed | Fixed phone |
	| Mobile | Mobile handset |
	| ATA | analog terminal adapter |
	|Satphone| Satellite phone |
	| FSense | Stationary computing device (alarm |
	| | system, data sensor) |
	| Guard | Guardian devices |
	| Desktop| Desktop PC |
	| Laptop | Laptop computing device |
	| Tablet | Tablet computing device |
	| Alarm | Alarm system |
	| MSense | Mobile Data sensor |
	| Beacon | Personal beacons (spot) |
	| Auto | Auto telematics |
	| Truck | Truck telematics |
	| Farm | Farm equipment telematics |
	| Marine | Marine telematics |
	| PDA | Personal digital assistant |
	| PND | Personal navigation device) |
	| SmrtPhn| Smart phone |
	| Itab | Internet tablet |
	| Game | Gaming console |
	| Video | Video phone |
	| Text | Other text device |
	| NA | Not Available |
	+--------+----------------------------------------+
	14.1.5. Additional Call Data Device ID Type Type Registry		9.1.5. Additional Call Data Device ID Type Type Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Device ID Type'. As defined in [RFC5226], this registry operates		Device ID Type'. As defined in [RFC5226], this registry operates
	under "Expert Review" rules. The expert should ascertain that the		under "Expert Review" rules. The expert should ascertain that the
	proposed type is well understood, and provides the information useful		proposed type is well understood, and provides the information useful
	to PSAPs and responders to uniquely identify a device.		to PSAPs and responders to uniquely identify a device.
	The content of this registry includes:		The content of this registry includes:
	Name: enumeration token of the device id type.		Name: enumeration token of the device id type.
	Description: Short description identifying type of device id.		Description: Short description identifying type of device id.
	The values defined are:		The initial set of values are defined in Figure 6.
	+--------+----------------------------------------+
	| Name | Description |
	+--------+----------------------------------------+
	| MEID | Mobile Equipment Identifier (CDMA) |
	| ESN | Electronic Serial Number(GSM) |
	| MAC | Media Access Control Address (IEEE) |
	| WiMAX | device certificate unique id |
	| IMEI | International Mobile Equipment ID (GSM)|
	| UDI | Unique Device Identifier (medical) |
	| RFID | Radio Frequency Identification |
	| SN | Manufacturer Serial Number |
	+--------+----------------------------------------+
	14.1.6. Device/Service Specific Additional Data Type Registry		9.1.6. Device/Service Specific Additional Data Type Registry
	This document creates a new registry called 'Device/Service Specific		This document creates a new registry called 'Device/Service Specific
	Additional Data Type Registry'. As defined in [RFC5226], this		Additional Data Type Registry'. As defined in [RFC5226], this
	registry operates under "Expert Review" and "Specification Required"		registry operates under "Expert Review" and "Specification Required"
	rules. The expert should ascertain that the proposed type is well		rules. The expert should ascertain that the proposed type is well
	understood, and provides information useful to PSAPs and responders.		understood, and provides information useful to PSAPs and responders.
	The specification must contain a complete description of the data,		The specification must contain a complete description of the data,
	and a precise format specification suitable to allow interoperable		and a precise format specification suitable to allow interoperable
	implementations.		implementations.
	The content of this registry includes:		The content of this registry includes:
	Name: enumeration token of the data type.		Name: enumeration token of the data type.
	Description: Short description identifying the the data.		Description: Short description identifying the the data.
	Specification: Citation for the specification of the data.		Specification: Citation for the specification of the data.
	The values defined are:		The initial set of values are listed below:
	+---------+----------------------------------------+----------------+		+---------+----------------------------------------+----------------+
	| Name | description | specification |		| Token | Description | Specification |
	+---------+-------+--------------------------------+----------------+		+---------+----------------------------------------+----------------+
	| IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 |		| IEE1512 | Common Incident Management Message Set | IEEE 1512-2006 |
	+---------+----------------------------------------+----------------+		+---------+----------------------------------------+----------------+
	| VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS |		| VEDS | Vehicle Emergency Data Set | APCO/NENA VEDS |
	+---------+----------------------------------------+----------------+		+---------+----------------------------------------+----------------+
	14.1.7. Additional Call Data Blocks Registry		9.1.7. Additional Call Data Blocks Registry
	This document creates a new subregistry called 'Additional Call Data		This document creates a new subregistry called 'Additional Call Data
	Blocks' in the purpose registry established by RFC 261. As defined		Blocks' in the purpose registry established by RFC 261. As defined
	in [RFC5226], this registry operates under "Expert Review" and		in [RFC5226], this registry operates under "Expert Review" and
	"Specification Required" rules. The expert is responsible for		"Specification Required" rules. The expert is responsible for
	verifying that the document contains a complete and clear		verifying that the document contains a complete and clear
	specification of the block and the block does not obviously duplicate		specification of the block and the block does not obviously duplicate
	existing blocks.		existing blocks.
	The content of this registry includes:		The content of this registry includes:
	Name: Element Name of enclosing block.		Name: Element Name of enclosing block.
	Reference: The document that describes the block		Reference: The document that describes the block
	The values defined are:		This document defines the following set of values:
	+-------------+-----------+		+--------------+-----------+
	| Name | Reference |		| Token | Reference |
	+-------------+-----------+		+--------------+-----------+
	|ProviderInfo | RFCXXXX |		| ProviderInfo | RFCXXXX |
	| SvcInfo | RFCXXXX |		| SvcInfo | RFCXXXX |
	| DevInfo | RFCXXXX |		| DevInfo | RFCXXXX |
	| Subscriber | RFCXXXX |		| Subscriber | RFCXXXX |
	| Comment | RFCXXXX |		| Comment | RFCXXXX |
	+-------------+-----------+		+--------------+-----------+
	RFC Editor Note:		RFC Editor Note:
	replace XXXX in the table above with this documents RFC number		replace XXXX in the table above with this documents RFC number
	14.2. 'emergencyCallData' Purpose Parameter Value		9.2. 'emergencyCallData' Purpose Parameter Value
	This document defines the 'emergencyCall' value for the "purpose"		This document defines the 'emergencyCall' value for the "purpose"
	parameter of the Call-Info header field. The Call-Info header and		parameter of the Call-Info header field. The Call-Info header and
	the corresponding registry for the 'purpose' parameter was		the corresponding registry for the 'purpose' parameter was
	established with RFC 3261 [RFC3261].		established with RFC 3261 [RFC3261].
	Header Parameter New		Header Parameter New
	Field Name Value Reference		Field Name Value Reference
	---------- --------- ----------------- ---------		---------- --------- ----------------- ---------
	Call-Info purpose emergencyCall [This RFC]		Call-Info purpose emergencyCall [This RFC]
	14.3. URN Sub-Namespace Registration for provided-by Registry Entry		9.3. URN Sub-Namespace Registration for provided-by Registry Entry
	This section registers the namespace specified in Section 14.5.1 in		This section registers the namespace specified in Section 9.5.1 in
	the provided-by registry established by RFC 4119, for usage within		the provided-by registry established by RFC 4119, for usage within
	the 'provided-by' element of a PIDF-LO.		the 'provided-by' element of a PIDF-LO.
	14.3.1. Provided-By XML Schema		9.3.1. Provided-By XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCallAddlData"		targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	targetNamespace="urn:ietf:params:xml:ns:pidf:		xmlns:xs="http://www.w3.org/2001/XMLSchema";
	geopriv10:emergencyCallData"		xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xml="http://www.w3.org/XML/1998/namespace";
	xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"		xmlns:pi="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		xmlns:dev="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
			xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
			xmlns:com="urn:ietf:params:xml:ns:emergencyCall.Comment"
			elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<!-- Additional Data By Reference -->
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:simpleType name="iso3166a2">		<xs:element name="emergencyCallDataReference">
	<xs:restriction base="xs:token">		<xs:complexType>
	<xs:pattern value="[A-Z]{2}"/>		<xs:sequence>
	</xs:restriction>		<xs:element name="emergencyProviderInfo"
	</xs:simpleType>		type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyServiceInfo"
			type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyDeviceInfo"
			type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencySubscriberInfo"
			type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyComment"
			type="xs:anyURI" minOccurs="0" maxOccurs="1"/>
			<xs:element name="anyOtherRefs"
			type="xs:anyURI" minOccurs="0" maxOccurs="unbounded"/>
	<xs:element name="emergencyCallDataReference">		<xs:any namespace="##other" processContents="lax"
	<xs:complexType>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:sequence>
	<xs:attribute name="ref"
	type="xs:anyURI" use="required"/>
	<xs:attribute name="purpose"
	type="xs:string" use="required"/>
	</xs:sequence>
	</xs:complexType>
	</xs:element>
	<xs:element name="emergencyCallDataValue">		</xs:sequence>
	<xs:attribute name="purpose"		</xs:ComplexType>
	type="xs:string" use="required"/>		</xs:element>
	</xs:element>
	</xs:schema>
	Figure 11: Provided-By XML Schema		<!-- Additional Data By Value -->
	14.4. MIME Registrations		<xs:element name="emergencyCallDataValue">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="emergencyProviderInfo"
			type="pi:emergencyCall.ProviderInfo"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyServiceInfo"
			type="svc:emergencyCall.SvcInfo"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyDeviceInfo"
			type="dev:emergencyCall.DeviceInfo"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencySubscriberInfo"
			type="sub:emergencyCall.SubInfo"
			minOccurs="0" maxOccurs="1"/>
			<xs:element name="emergencyComment"
			type="com:emergencyCall.Comment"
			minOccurs="0" maxOccurs="1"/>
			<xs:any namespace="##other" processContents="lax"
			minOccurs="0" maxOccurs="unbounded"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
	14.4.1. MIME Content-type Registration for 'application/		<xs:any namespace="##other" processContents="lax"
	emergencyCall.ProviderInfo+xml'		minOccurs="0" maxOccurs="unbounded"/>
			</xs:schema>
			Figure 18: Provided-By XML Schema
			9.4. MIME Registrations
			9.4.1. MIME Content-type Registration for 'application/
			emergencyCall.ProviderInfo+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	MIME media type name: application		MIME media type name: application
	MIME subtype name: emergencyCall.ProviderInfo+xml		MIME subtype name: emergencyCall.ProviderInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	skipping to change at page 45, line 43 ¶		skipping to change at page 45, line 35 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry the data provider		This content type is designed to carry the data provider
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 12 and Section 13 for		this information. Please refer to Section 7 and Section 8 for
	more information.		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:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		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>
	14.4.2. MIME Content-type Registration for 'application/		9.4.2. MIME Content-type Registration for 'application/
	emergencyCall.SvcInfo+xml'		emergencyCall.SvcInfo+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: emergencyCall.SvcInfo+xml		MIME subtype name: emergencyCall.SvcInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	skipping to change at page 47, line 8 ¶		skipping to change at page 46, line 45 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry the service information,		This content type is designed to carry the service information,
	which is a sub-category of additional data about an emergency		which is a sub-category of additional data about an emergency
	call.		call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 12 and Section 13 for		this information. Please refer to Section 7 and Section 8 for
	more information.		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:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		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>
	14.4.3. MIME Content-type Registration for 'application/		9.4.3. MIME Content-type Registration for 'application/
	emergencyCall.DevInfo+xml'		emergencyCall.DevInfo+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: emergencyCall.DevInfo+xml		MIME subtype name: emergencyCall.DevInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	skipping to change at page 48, line 19 ¶		skipping to change at page 48, line 8 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry the device information		This content type is designed to carry the device information
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 12 and Section 13 for		this information. Please refer to Section 7 and Section 8 for
	more information.		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:		Additional information:
	skipping to change at page 49, line 5 ¶		skipping to change at page 48, line 35 ¶
	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>
	14.4.4. MIME Content-type Registration for 'application/		9.4.4. MIME Content-type Registration for 'application/
	emergencyCall.SubInfo+xml'		emergencyCall.SubInfo+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: emergencyCall.SubInfo+xml		MIME subtype name: emergencyCall.SubInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	skipping to change at page 49, line 36 ¶		skipping to change at page 49, line 19 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry owner/subscriber		This content type is designed to carry owner/subscriber
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 12 and Section 13 for		this information. Please refer to Section 7 and Section 8 for
	more information.		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:		Additional information:
	skipping to change at page 50, line 4 ¶		skipping to change at page 49, line 35 ¶
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		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>
	14.4.5. MIME Content-type Registration for 'application/		9.4.5. MIME Content-type Registration for 'application/
	emergencyCall.Comment+xml'		emergencyCall.Comment+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	MIME media type name: application		MIME media type name: application
	MIME subtype name: emergencyCall.Comment+xml		MIME subtype name: emergencyCall.Comment+xml
	Mandatory parameters: none		Mandatory parameters: none
	skipping to change at page 50, line 44 ¶		skipping to change at page 50, line 35 ¶
	character encoding used. See Section 3.2 of RFC 3023 [RFC3023].		character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
	Security considerations:		Security considerations:
	This content type is designed to carry a comment, which is a sub-		This content type is designed to carry a comment, which is a sub-
	category of additional data about an emergency call.		category of additional data about an emergency call.
	This data may contain personal information. Appropriate		This data may contain personal information. Appropriate
	precautions may have to be taken to limit unauthorized access,		precautions may have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 12 and Section 13 for		this information. Please refer to Section 7 and Section 8 for
	more information.		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:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		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>
	14.5. URN Sub-Namespace Registration		9.5. URN Sub-Namespace Registration
	14.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData		9.5.1. Registration for urn:ietf:params:xml:ns:emergencyCallAddlData
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCallAddlData		URI: urn:ietf:params:xml:ns:emergencyCallAddlData
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 52, line 7 ¶		skipping to change at page 51, line 45 ¶
	content="text/html;charset=iso-8859-1"/>		content="text/html;charset=iso-8859-1"/>
	<title>Namespace for Additional Emergency Call Data</title>		<title>Namespace for Additional Emergency Call Data</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.5.2. Registration for		9.5.2. Registration for
	urn:ietf:params:xml:ns:emergencyCallProviderInfo		urn:ietf:params:xml:ns:emergencyCallProviderInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo		URI: urn:ietf:params:xml:ns:emergencyCallProviderInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 52, line 39 ¶		skipping to change at page 52, line 34 ¶
	Data Provider Information</title>		Data Provider Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Data Provider Information</h2>		<h2>Data Provider Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo		9.5.3. Registration for urn:ietf:params:xml:ns:emergencyCall.SvcInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo		URI: urn:ietf:params:xml:ns:emergencyCall.SvcInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">		<html xmlns="http://www.w3.org/1999/xhtml">
	skipping to change at page 53, line 28 ¶		skipping to change at page 53, line 20 ¶
	Service Information</title>		Service Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Service Information</h2>		<h2>Service Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo		9.5.4. Registration for urn:ietf:params:xml:ns:emergencyCall.DevInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo		URI: urn:ietf:params:xml:ns:emergencyCall.DevInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 54, line 4 ¶		skipping to change at page 53, line 40 ¶
	XML:		XML:
	BEGIN		BEGIN
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"		<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
	"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">		"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
	<html xmlns="http://www.w3.org/1999/xhtml">		<html xmlns="http://www.w3.org/1999/xhtml">
	<head>		<head>
	<meta http-equiv="content-type"		<meta http-equiv="content-type"
	content="text/html;charset=iso-8859-1"/>		content="text/html;charset=iso-8859-1"/>
	<title>Namespace for Additional Emergency Call Data:		<title>Namespace for Additional Emergency Call Data:
	Device Information</title>		Device Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Device Information</h2>		<h2>Device Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo		9.5.5. Registration for urn:ietf:params:xml:ns:emergencyCall.SubInfo
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo		URI: urn:ietf:params:xml:ns:emergencyCall.SubInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 55, line 5 ¶		skipping to change at page 54, line 37 ¶
	Owner/Subscriber Information</title>		Owner/Subscriber Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2> Owner/Subscriber Information</h2>		<h2> Owner/Subscriber Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment		9.5.6. Registration for urn:ietf:params:xml:ns:emergencyCall.Comment
	This section registers a new XML namespace, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:ns:emergencyCall.Comment		URI: urn:ietf:params:xml:ns:emergencyCall.Comment
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 55, line 35 ¶		skipping to change at page 55, line 25 ¶
	<title>Namespace for Additional Emergency Call Data:Comment</title>		<title>Namespace for Additional Emergency Call Data:Comment</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2> Comment</h2>		<h2> Comment</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	14.6. Schema Registrations		9.6. Schema Registrations
	This specification registers five schemas, as per the guidelines in		This specification registers five schemas, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI: urn:ietf:params:xml:schema:additional-		URI: urn:ietf:params:xml:schema:additional-
	data:emergencyCallProviderInfo		data:emergencyCallProviderInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 1.		XML: The XML schema can be found in Figure 13.
	URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo		URI: urn:ietf:params:xml:schema:additional-data:addCallSvcInfo
	Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ectit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 3.		XML: The XML schema can be found in Figure 14.
	URI: urn:ietf:params:xml:schema:additional-		URI: urn:ietf:params:xml:schema:additional-
	data:emergencyCallDevInfo		data:emergencyCallDevInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 5.		XML: The XML schema can be found in Figure 15.
	URI: urn:ietf:params:xml:schema:additional-		URI: urn:ietf:params:xml:schema:additional-
	data:emergencyCall.SubInfo		data:emergencyCall.SubInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Section 8.2.		XML: The XML schema can be found in Section 6.4.
	URI: urn:ietf:params:xml:schema:additional-		URI: urn:ietf:params:xml:schema:additional-
	data:emergencyCall.Comment		data:emergencyCall.Comment
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Section 9.2.		XML: The XML schema can be found in Section 6.5.
	14.7. VCard Parameter Value Registration		9.7. VCard Parameter Value Registration
	This document registers a new value in the vCARD Parameter Values		This document registers a new value in the vCARD Parameter Values
	registry as defined by [RFC6350] with the following template:		registry as defined by [RFC6350] with the following template:
	Value: main		Value: main
	Purpose: The main telephone number, typically of an enterprise, as		Purpose: The main telephone number, typically of an enterprise, as
	opposed to a direct dial number of an individual employee		opposed to a direct dial number of an individual employee
	Conformance: This value can be used with the "TYPE" parameter		Conformance: This value can be used with the "TYPE" parameter
	applied on the "TEL" property.		applied on the "TEL" property.
	Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90		Example(s): TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-90
	00		00
	15. Acknowledgments		10. Acknowledgments
	This work was originally started in NENA and has benefitted from a		This work was originally started in NENA and has benefitted from a
	large number of participants in NENA standardization efforts,		large number of participants in NENA standardization efforts,
	originally in the Long Term Definition Working Group, the Data		originally in the Long Term Definition Working Group, the Data
	Technical Committee and most recently the Additional Data working		Technical Committee and most recently the Additional Data working
	group. The authors are grateful for the initial work and extended		group. The authors are grateful for the initial work and extended
	comments provided by the many NENA participants.		comments provided by many NENA participants, including Delaine
			Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James
			Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra,
			and Robert (Bob) Sherry.
	16. References		We would also like to thank James Winterbottom, Paul Kyzivat, Gunnar
			Hellstrom, Martin Thomson, Keith Drage, and Laura Liess for their
			review comments.
	16.1. Normative References		11. References
			11.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource		[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
	Locators", RFC 2392, August 1998.		Locators", RFC 2392, August 1998.
	[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media		[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
	Types", RFC 3023, January 2001.		Types", RFC 3023, January 2001.
	skipping to change at page 57, line 48 ¶		skipping to change at page 57, line 46 ¶
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,		[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
	August 2011.		August 2011.
	[RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC		[RFC6351] Perreault, S., "xCard: vCard XML Representation", RFC
	6351, August 2011.		6351, August 2011.
	16.2. Informational References		11.2. Informational References
	[I-D.iab-privacy-considerations]		[I-D.iab-privacy-considerations]
	Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,		Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
	Morris, J., Hansen, M., and R. Smith, "Privacy		Morris, J., Hansen, M., and R. Smith, "Privacy
	Considerations for Internet Protocols", draft-iab-privacy-		Considerations for Internet Protocols", draft-iab-privacy-
	considerations-03 (work in progress), July 2012.		considerations-03 (work in progress), July 2012.
	[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for		[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
	Emergency Context Resolution with Internet Technologies",		Emergency Context Resolution with Internet Technologies",
	RFC 5012, January 2008.		RFC 5012, January 2008.
End of changes. 165 change blocks.
	898 lines changed or deleted		898 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/