< draft-ietf-ecrit-additional-data-10.txt		draft-ietf-ecrit-additional-data-11.txt >
	ECRIT B. Rosen		ECRIT B.R. Rosen
	Internet-Draft NeuStar		Internet-Draft NeuStar
	Intended status: Standards Track H. Tschofenig		Intended status: Standards Track H. Tschofenig
	Expires: January 16, 2014 Nokia Siemens Networks		Expires: January 30, 2014 Nokia Siemens Networks
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	R. Gellens		R. Gellens
	Qualcomm Technologies, Inc.		Qualcomm Technologies, Inc.
	J. Winterbottom		J. Winterbottom
			July 31, 2013
	July 15, 2013
	Additional Data related to an Emergency Call		Additional Data related to an Emergency Call
	draft-ietf-ecrit-additional-data-10.txt		draft-ietf-ecrit-additional-data-11.txt
	Abstract		Abstract
	When an emergency call is sent to a Public Safety Answering Point		When an emergency call is sent to a Public Safety Answering Point
	(PSAP), the device that sends it, as well as any application service		(PSAP), the device that sends it, as well as any application service
	provider in the path of the call, or access network provider through		provider in the path of the call, or access network provider through
	which the call originated may have information about the call, the		which the call originated may have information about the call, the
	caller or the location which the PSAP may be able to use. This		caller or the location which the PSAP may be able to use. This
	document describes data structures and a mechanism to convey such		document describes data structures and a mechanism to convey such
	data to the PSAP. The mechanism uses a Uniform Resource Identifier		data to the PSAP. The mechanism uses a Uniform Resource Identifier
	(URI), which may point to either an external resource or an object in		(URI), which may point to either an external resource or an object in
	the body of the SIP message. The mechanism thus allows the data to		the body of the SIP message. The mechanism thus allows the data to
	be passed by reference (when the URI points to an external resource)		be passed by reference (when the URI points to an external resource)
	or by value (when it points into the body of the message). This		or by value (when it points into the body of the message). This
	follows the tradition of prior emergency services standardization		follows the tradition of prior emergency services standardization
	work where data can be conveyed by value within the call signaling		work where data can be conveyed by value within the call signaling
	(i.e., in body of the SIP message) and also by reference.		(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 January 16, 2014.
			This Internet-Draft will expire on January 30, 2014.
	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/
	(http://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6		3. Data Structures . . . . . . . . . . . . . . . . . . . . . . . 6
	3.1. Data Provider Information . . . . . . . . . . . . . . . . 7		3.1. Data Provider Information . . . . . . . . . . . . . . . . 6
	3.1.1. Data Provider String . . . . . . . . . . . . . . . . 7		3.1.1. Data Provider String . . . . . . . . . . . . . . . . . 7
	3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . 8		3.1.2. Data Provider ID . . . . . . . . . . . . . . . . . . . 7
	3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 8		3.1.3. Data Provider ID Series . . . . . . . . . . . . . . . 7
	3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 9		3.1.4. Type of Data Provider . . . . . . . . . . . . . . . . 8
	3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 9		3.1.5. Data Provider Contact URI . . . . . . . . . . . . . . 8
	3.1.6. Data Provider Languages(s) Supported . . . . . . . . 10		3.1.6. Data Provider Languages(s) Supported . . . . . . . . . 9
	3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . 10		3.1.7. xCard of Data Provider . . . . . . . . . . . . . . . . 9
	3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 11		3.1.8. Subcontractor Principal . . . . . . . . . . . . . . . 10
	3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . 11		3.1.9. Subcontractor Priority . . . . . . . . . . . . . . . . 10
	3.1.10. emergencyCall.ProviderInfo Example . . . . . . . . . 12		3.1.10. emergencyCall.ProviderInfo Example . . . . . . . . . . 11
	3.2. Service Information . . . . . . . . . . . . . . . . . . . 14		3.2. Service Information . . . . . . . . . . . . . . . . . . . 13
	3.2.1. Service Environment . . . . . . . . . . . . . . . . . 14		3.2.1. Service Environment . . . . . . . . . . . . . . . . . 13
	3.2.2. Service Delivered by Provider to End User . . . . . . 15		3.2.2. Service Delivered by Provider to End User . . . . . . 14
	3.2.3. Service Mobility Environment . . . . . . . . . . . . 16		3.2.3. Service Mobility Environment . . . . . . . . . . . . . 16
	3.2.4. emergencyCall.SvcInfo Example . . . . . . . . . . . . 17		3.2.4. emergencyCall.SvcInfo Example . . . . . . . . . . . . 16
	3.3. Device Information . . . . . . . . . . . . . . . . . . . 17		3.3. Device Information . . . . . . . . . . . . . . . . . . . . 16
	3.3.1. Device Classification . . . . . . . . . . . . . . . . 17		3.3.1. Device Classification . . . . . . . . . . . . . . . . 17
	3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 18		3.3.2. Device Manufacturer . . . . . . . . . . . . . . . . . 18
	3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 19		3.3.3. Device Model Number . . . . . . . . . . . . . . . . . 19
	3.3.4. Unique Device Identifier . . . . . . . . . . . . . . 19		3.3.4. Unique Device Identifier . . . . . . . . . . . . . . . 19
	3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 19		3.3.5. Type of Device Identifier . . . . . . . . . . . . . . 19
	3.3.6. Device/Service Specific Additional Data Structure . . 20		3.3.6. Device/Service Specific Additional Data Structure . . 20
	3.3.7. Device/Service Specific Additional Data Structure		3.3.7. Device/Service Specific Additional Data Structure Type 21
	Type . . . . . . . . . . . . . . . . . . . . . . . . 21		3.3.8. Choosing between defining a new type of block or new type
	3.3.8. Choosing between defining a new type of block or new		of device/service specific additional data . . . . . . 21
	type of device/service specific additional data . . . 21		3.3.9. emergencyCall.DevInfo Example . . . . . . . . . . . . 22
	3.3.9. emergencyCall.DevInfo Example . . . . . . . . . . . . 22		3.4. Owner/Subscriber Information . . . . . . . . . . . . . . . 22
	3.4. Owner/Subscriber Information . . . . . . . . . . . . . . 22		3.4.1. xCard for Subscriber's Data . . . . . . . . . . . . . 22
	3.4.1. xCard for Subscriber's Data . . . . . . . . . . . . . 22		3.4.2. emergencyCall.SubInfo Example . . . . . . . . . . . . 23
	3.4.2. emergencyCall.SubInfo Example . . . . . . . . . . . . 23		3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 25
	3.5. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 25		3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 26
	3.5.1. Comment . . . . . . . . . . . . . . . . . . . . . . . 25		3.5.2. emergencyCall.Comment Example . . . . . . . . . . . . 26
	3.5.2. emergencyCall.Comment Example . . . . . . . . . . . . 26		4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 26
	4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 26		4.1. Transmitting Blocks using the Call-Info Header . . . . . . 28
	4.1. Transmitting Blocks using the Call-Info Header . . . . . 28
	4.2. Transmitting Blocks by Reference using the Provided-By		4.2. Transmitting Blocks by Reference using the Provided-By
	Element . . . . . . . . . . . . . . . . . . . . . . . . . 28		Element . . . . . . . . . . . . . . . . . . . . . . . . . 29
	4.3. Transmitting Blocks by Value using the Provided-By		4.3. Transmitting Blocks by Value using the Provided-By Element 29
	Element . . . . . . . . . . . . . . . . . . . . . . . . . 29		4.4. The Content-Disposition Parameter . . . . . . . . . . . . 30
	4.4. The Content-Disposition Parameter . . . . . . . . . . . . 30
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 31		5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
	6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 34		6. XML Schemas . . . . . . . . . . . . . . . . . . . . . . . . . 35
	6.1. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 34		6.1. emergencyCall.ProviderInfo XML Schema . . . . . . . . . . 35
	6.2. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . 36		6.2. emergencyCall.SvcInfo XML Schema . . . . . . . . . . . . . 36
	6.3. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . 36		6.3. emergencyCall.DevInfo XML Schema . . . . . . . . . . . . . 37
	6.4. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . 37		6.4. emergencyCall.SubInfo XML Schema . . . . . . . . . . . . . 38
	6.5. emergencyCall.Comment XML Schema . . . . . . . . . . . . 38		6.5. emergencyCall.Comment XML Schema . . . . . . . . . . . . . 39
	6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . 39		6.6. Provided-By XML Schema . . . . . . . . . . . . . . . . . . 40
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 41		7. Security Considerations . . . . . . . . . . . . . . . . . . . 42
	8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 42		8. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 43
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
	9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 44		9.1. Registry creation . . . . . . . . . . . . . . . . . . . . 45
	9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 44		9.1.1. Provider ID Series Registry . . . . . . . . . . . . . 45
	9.1.2. Service Provider Type Registry . . . . . . . . . . . 45		9.1.2. Service Provider Type Registry . . . . . . . . . . . . 46
	9.1.3. Service Delivered Registry . . . . . . . . . . . . . 45		9.1.3. Service Delivered Registry . . . . . . . . . . . . . . 46
	9.1.4. Device Classification Registry . . . . . . . . . . . 45		9.1.4. Device Classification Registry . . . . . . . . . . . . 47
	9.1.5. Device ID Type Type Registry . . . . . . . . . . . . 46		9.1.5. Device ID Type Type Registry . . . . . . . . . . . . . 47
	9.1.6. Device/Service Data Type Registry . . . . . . . . . . 46		9.1.6. Device/Service Data Type Registry . . . . . . . . . . 47
	9.1.7. Additional Data Blocks Registry . . . . . . . . . . . 47		9.1.7. Additional Data Blocks Registry . . . . . . . . . . . 48
	9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 47		9.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 48
	9.3. URN Sub-Namespace Registration for provided-by Registry		9.3. URN Sub-Namespace Registration for provided-by Registry Entr 49
	Entry . . . . . . . . . . . . . . . . . . . . . . . . . . 48		9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 49
	9.4. MIME Registrations . . . . . . . . . . . . . . . . . . . 48
	9.4.1. MIME Content-type Registration for		9.4.1. MIME Content-type Registration for
	'application/emergencyCall.ProviderInfo+xml' . . . . 48		'application/emergencyCall.ProviderInfo+xml' . . . . . 49
	9.4.2. MIME Content-type Registration for		9.4.2. MIME Content-type Registration for
	'application/emergencyCall.SvcInfo+xml' . . . . . . . 49		'application/emergencyCall.SvcInfo+xml' . . . . . . . 50
	9.4.3. MIME Content-type Registration for		9.4.3. MIME Content-type Registration for
	'application/emergencyCall.DevInfo+xml' . . . . . . . 50		'application/emergencyCall.DevInfo+xml' . . . . . . . 51
	9.4.4. MIME Content-type Registration for		9.4.4. MIME Content-type Registration for
	'application/emergencyCall.SubInfo+xml' . . . . . . . 51		'application/emergencyCall.SubInfo+xml' . . . . . . . 52
	9.4.5. MIME Content-type Registration for		9.4.5. MIME Content-type Registration for
	'application/emergencyCall.Comment+xml' . . . . . . . 52		'application/emergencyCall.Comment+xml' . . . . . . . 52
			9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 53
	9.5. URN Sub-Namespace Registration . . . . . . . . . . . . . 53
	9.5.1. Registration for		9.5.1. Registration for
	urn:ietf:params:xml:ns:emergencyCallAddlData . . . . 53		urn:ietf:params:xml:ns:emergencyCallAddlData . . . . . 53
	9.5.2. Registration for		9.5.2. Registration for
	urn:ietf:params:xml:ns:emergencyCallProviderInfo . . 53		urn:ietf:params:xml:ns:emergencyCallProviderInfo . . . 54
	9.5.3. Registration for		9.5.3. Registration for
	urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . 54		urn:ietf:params:xml:ns:emergencyCall.SvcInfo . . . . . 55
	9.5.4. Registration for		9.5.4. Registration for
	urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . 55		urn:ietf:params:xml:ns:emergencyCall.DevInfo . . . . . 55
	9.5.5. Registration for		9.5.5. Registration for
	urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . 56		urn:ietf:params:xml:ns:emergencyCall.SubInfo . . . . . 56
	9.5.6. Registration for		9.5.6. Registration for
	urn:ietf:params:xml:ns:emergencyCall.Comment . . . . 56		urn:ietf:params:xml:ns:emergencyCall.Comment . . . . . 57
	9.6. Schema Registrations . . . . . . . . . . . . . . . . . . 57		9.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 57
	9.7. VCard Parameter Value Registration . . . . . . . . . . . 58		9.7. VCard Parameter Value Registration . . . . . . . . . . . . 58
	10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58		10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 58
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59		11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 59
	11.1. Normative References . . . . . . . . . . . . . . . . . . 59		11.1. Normative References . . . . . . . . . . . . . . . . . . 59
	11.2. Informational References . . . . . . . . . . . . . . . . 60		11.2. Informational References . . . . . . . . . . . . . . . . 60
	Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . 61		Appendix A. XML Schema for vCard/xCard . . . . . . . . . . . . . . 60
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 83		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 81
	1. Introduction		1. Introduction
	When an IP-based emergency call is initiated a rich set of data from		When an IP-based emergency call is initiated a rich set of data from
	multiple data sources is conveyed to the Public Safety Answering		multiple data sources is conveyed to the Public Safety Answering
	Point (PSAP). This data includes information about the calling party		Point (PSAP). This data includes information about the calling party
	identity, the multimedia capabilities of the device, the emergency		identity, the multimedia capabilities of the device, the emergency
	service number, location information, and meta-data about the sources		service number, location information, and meta-data about the sources
	of the data. The device, the access network provider, and any		of the data. The device, the access network provider, and any
	service provider in the call path have even more information useful		service provider in the call path may have even more information
	for a PSAP call taker. This document extends the basic set of data		useful for a PSAP. This document extends the basic set of data
	communicated with an IP-based emergency call providing call takers		communicated with an IP-based emergency call, as described in
	and the PSAP organization valuable insight and increased situational		[RFC6443] and [RFC6881], in order to carry additional data which may
	awareness.		be useful to an entity or call taker handling the call. This data is
			"additional" to the basic information found in the emergency call
			signaling used.
	In general, there are three categories of data communicated in an		In general, there are three categories of data communicated in an
	emergency call:		emergency call:
	Data Associated with a Location: Location data is conveyed in the		Data Associated with a Location: Location data is conveyed in the
	Presence Information Data Format Location Object (PIDF-LO) data		Presence Information Data Format Location Object (PIDF-LO) data
	structure originally defined in RFC 4119 [RFC4119] and extended by		structure originally defined in RFC 4119 [RFC4119] and extended by
	RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location		RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location
	information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for		information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for
	geodetic location information), and		geodetic location information), and [I-D.ietf-geopriv-relative-
	[I-D.ietf-geopriv-relative-location] (for relative location).		location] (for relative location). There may be data that is
	There may be data that is specific to the location not available		specific to the location not available in the location data
	in the location data structure itself, such as floor plans, tenant		structure itself, such as floor plans, tenant and building owner
	and building owner contact data, heating, ventilation and air		contact data, heating, ventilation and air conditioning (HVAC)
	conditioning (HVAC) status, etc.		status, etc.
	Data Associated with a Call: While information is carried in the		Data Associated with a Call: While information is carried in the call
	call setup procedure itself (as part of the SIP headers as well as		setup procedure itself (as part of the SIP headers as well as in
	in the body of the SIP message), there is additional data known by		the body of the SIP message), there is additional data known by
	the device making the call, and the service provider along the		the device making the call, and the service provider along the
	path of the call. This information may include the service		path of the call. This information may include the service
	provider contact information, subscriber identity and contact		provider contact information, subscriber identity and contact
	information, the type of service the service provider and the		information, the type of service the service provider and the
	access network provider offer, what kind of device is being used,		access network provider offer, what kind of device is being used,
	etc. Some data is device or service dependent data. For example,		etc. Some data is device or service dependent data. For example,
	a car telematics system may have crash information. A medical		a car telematics system may have crash information. A medical
	monitoring device may have sensor data.		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 but defines extension points for other data		associated with the call but defines extension points for other data
	to be added via other specifications.		to be added via other specifications.
	For interoperability, there needs to be a common way for the		For interoperability, there needs to be a common way for the
	information conveyed to a PSAP to be encoded and identified.		information conveyed to a PSAP to be encoded and identified.
	Identification allows emergency services authorities to know during		Identification allows emergency services authorities to know during
	call processing which types of data are present and to determine if		call processing which types of data are present and to determine if
	skipping to change at page 6, line 4 ¶		skipping to change at page 5, line 29 ¶
	separation between the two.		separation between the two.
	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 an XML structure with an associated Multipurpose Internet		blocks is an XML structure with an associated Multipurpose Internet
	Mail Extensions (MIME) type for encapsulation, and an extensible set		Mail Extensions (MIME) type for encapsulation, and an extensible set
	of these types constitute the data set. A registry is defined to		of these types constitute the data set. A registry is defined to
	list the block types that may be included.		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).		service provider to refer to an Application Service Provider (ASP). A
	A Voice Service Provider (VSP) is a special type of ASP. With the		Voice Service Provider (VSP) is a special type of ASP. With the term
	term "Access Network Provider" we refer to the Internet Access		"Access Network Provider" we refer to the Internet Access Provider
	Provider (IAP) and the Internet Service Provider (ISP) without		(IAP) and the Internet Service Provider (ISP) without further
	further distinguishing these two entities, since the difference		distinguishing these two entities, since the difference between the
	between the two is not relevant for this document. Note that the		two is not relevant for this document. Note that the roles of ASP
	roles of ASP and access network provider may be provided by a single		and access network provider may be provided by a single company.
	company.
	In the data block definitions, see Section 3, the values for the		In the data block definitions, see Section 3, the values for the
	"Use:" label are specified as one of:		"Use:" label are specified as one of:
	'Required': 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.
	vCard is a data format for representing and exchanging a variety of		vCard is a data format for representing and exchanging a variety of
	information about individuals and other entities. For applications		information about individuals and other entities. For applications
	that use XML the format defined in vCard is not immediately		that use XML the format defined in vCard is not immediately
	applicable. For this purpose an XML-based encoding of the		applicable. For this purpose an XML-based encoding of the
	information elements defined in the vCard specification has been		information elements defined in the vCard specification has been
	defined and the name of that specification is xCard. Since the term		defined and the name of that specification is xCard. Since the term
	vCard is more familiar to most readers we use the term xCard and		vCard is more familiar to most readers we use the term xCard and
	vCard interchangeable but it would be accurate to use the term vCard		vCard interchangeable but it would be accurate to use the term vCard
	only.		only.
	3. Data Structures		3. Data Structures
	This section defines the following five data structures, each as a		This section defines the following five data structures, each as a
	data block. For each block we define the MIME type, and the XML data		data block. For each block we define the MIME type, and the XML data
	structure. The five data structures are:		structure. The five data structures are:
	'Data Provider': This block supplies name and contact information		'Data Provider': This block supplies name and contact information for
	for the entity that created the data. Section 3.1 provides the		the entity that created the data. Section 3.1 provides the
	details.		details.
	'Service Information': This block supplies information about the		'Service Information': This block supplies information about the
	service. The description can be found in Section 3.2.		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 information can be found in		device placing the call. Device information can be found in
	Section 3.3.		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. Details can be found in		of the device or about the subscriber. Details can be found in
	Section 3.4.		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. This simple		readable text to the PSAP or emergency responders. This simple
	structure is defined in Section 3.5.		structure is defined in Section 3.5.
	Note that the xCard format is re-used in some of the data structures		Note that the xCard format is re-used in some of the data structures
	to provide contact information. In an xCard there is no way to		to provide contact information. In an xCard there is no way to
	specify a "main" telephone number. These numbers are useful to		specify a "main" telephone number. These numbers are useful to
	emergency responders who are called to a large enterprise. This		emergency responders who are called to a large enterprise. This
	document adds a new property value to the "tel" property of the TYPE		document adds a new property value to the "tel" property of the TYPE
	parameter called "main". It can be used in any xCard in additional		parameter called "main". It can be used in any xCard in additional
	data.		data.
	skipping to change at page 7, line 37 ¶		skipping to change at page 7, line 8 ¶
	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".
	3.1.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.
	3.1.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.
	3.1.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 ProviderId. A registry
	Description: Identifies the issuer of the ProviderId. A registry
	will reflect the following valid entries:		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
	3.1.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 with an initial set of		in the ProviderId data element. A registry with an initial set of
	values is shown in Figure 1.		values is shown in Figure 1.
	+------------------------------+------------------------------------+		+------------------------------+------------------------------------+
	| Token | Description |		| Token | Description |
	+------------------------------+------------------------------------+		+------------------------------+------------------------------------+
	|Access Network Provider | Access network service provider |		|Access Network Provider | Access network service provider |
	|Service Provider | Calling or Origination telecom SP |		|Service Provider | Calling or Origination telecom SP |
	|Service Provider Subcontractor| A contractor to another kind of SP |		|Service Provider Subcontractor| A contractor to another kind of SP |
	|Telematics Provider | A sensor based SP, especially |		|Telematics Provider | A sensor based SP, especially |
	skipping to change at page 9, line 37 ¶		skipping to change at page 8, line 48 ¶
	|Expert Advice Provider | An SP giving expert advice |		|Expert Advice Provider | An SP giving expert advice |
	|Emergency Modality Translation| An emergency call specific |		|Emergency Modality Translation| An emergency call specific |
	| | modality translation service |		| | modality translation service |
	| | e.g. for sign language |		| | e.g. for sign language |
	|Relay Provider | A interpretation SP, for example, |		|Relay Provider | A interpretation SP, for example, |
	| | video relay for sign language |		| | video relay for sign language |
	| | interpreting |		| | interpreting |
	|Other | Any other type of service provider |		|Other | Any other type of service provider |
	+------------------------------+------------------------------------+		+------------------------------+------------------------------------+
	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
	3.1.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 contact
	URI. This MUST be a SIP URI. If a telephone number is the		address it should be provided in the form of
	contact address it should be provided in the form of
	sip:telephonenumber@serviceprovider:user=phone. If the call is		sip:telephonenumber@serviceprovider:user=phone. If the call is
	from a device, this would reflect the contact information of the		from a device, this would reflect the contact information of the
	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.
	3.1.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 --
	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
	service authority can communicate with the service provider or if		authority can communicate with the service provider or if an
	an interpreter will be needed.		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.
	3.1.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
	on each TEL. For encoding of the xCard this specification uses		on each TEL. For encoding of the xCard this specification uses
	the XML-based encoding specified in [RFC6351]. and is hereinafter		the XML-based encoding specified in [RFC6351]. and is hereinafter
	referred to as "xCard"		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.
	3.1.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.
	3.1.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.
	3.1.10. emergencyCall.ProviderInfo Example		3.1.10. 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>urn:nena:companyid:ID123</ad:ProviderID>		<ad:ProviderID>urn:nena:companyid: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>
	<ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI>		<ad:ContactURI>sip:voip-provider@example.com</ad:ContactURI>
	skipping to change at page 14, line 18 ¶		skipping to change at page 13, line 47 ¶
	<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
	3.2. Service Information		3.2. Service Information
	This block describes the service that the service provider provides		This block describes the service that the service provider provides
	to the caller. It SHOULD be included by all SPs in the path of the		to the caller. It SHOULD be included by all SPs in the path of the
	call. The mime subtype is "application/emergencyCall.SvcInfo+xml".		call. The mime subtype is "application/emergencyCall.SvcInfo+xml".
	3.2.1. Service Environment		3.2.1. Service Environment
	Data Element: Service Environment		Data Element: Service Environment
	Use: Required
	XML Element: <SvcEnvironment>		Use: Required
			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'.
	Reason for Need: To assist in determining equipment and manpower		Reason for Need: To assist in determining equipment and manpower
	requirements.		requirements.
	How Used by Call Taker: Information may be used to assist in		How Used by Call Taker: Information may be used to assist in
	determining equipment and manpower requirements for emergency		determining equipment and manpower requirements for emergency
	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.
	3.2.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 cannot be		subscribed to. The implied mobility of this service cannot be
	relied upon. A registry with an initial set of values is defined		relied upon. A registry with an initial set of values is defined
	in Figure 3.		in Figure 3.
	+--------+----------------------------------------+		+--------+----------------------------------------+
	| Name | Description |		| Name | Description |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	| Wrless | Wireless Telephone Service: Includes |		| Wrless | Wireless Telephone Service: Includes |
	| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |		| | Satellite, CDMA, GSM, Wi-Fi, WiMAX, |
	| | LTE (Long Term Evolution) |		| | LTE (Long Term Evolution) |
	skipping to change at page 16, line 8 ¶		skipping to change at page 15, line 44 ¶
	| Remote | Off premise extension |		| Remote | Off premise extension |
	| Relay | Relay Service: a type of service where |		| Relay | Relay Service: a type of service where |
	| | there is a human 3rd party agent who |		| | there is a human 3rd party agent who |
	| | provides some kind of additional |		| | provides some kind of additional |
	| | assistance to the caller. Includes |		| | assistance to the caller. Includes |
	| | sign language relay and telematics |		| | sign language relay and telematics |
	| | services which provide a service |		| | services which provide a service |
	| | assistant on the call. |		| | assistant on the call. |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	Figure 3: Service Delivered by Provider to End User Registry
	More than one value MAY be returned. For example, a VoIP inmate		More than one value MAY be returned. For example, a VoIP inmate
	telephone service is a reasonable combination.		telephone service is a reasonable combination.
	Reason for Need: Knowing the type of service may assist the PSAP		Reason for Need: Knowing the type of service may assist the PSAP with
	with the handling of the call.		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.
	3.2.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
	mobility of the caller. As the service provider may not know the		of the caller. As the service provider may not know the
	characteristics of the actual access network used, the value not		characteristics of the actual access network used, the value not
	be relied upon. A registry will reflect the following initial		be relied upon. A registry will reflect the following initial
	valid entries:		valid entries:
	* Mobile: the device should be able to move at any time		* Mobile: the device should be able to move at any time
	* Fixed: the device is not expected to move unless the service is		* Fixed: the device is not expected to move unless the service is
	relocated		relocated
	* Nomadic: the device is not expected to change its point of		* Nomadic: the device is not expected to change its point of
	attachment while on a call		attachment while on a call
	* Unknown: no information is known about the service mobility		* Unknown: no information is known about the service mobility
	environment for the device		environment for the device
	Reason for Need: Knowing the service provider's belief of mobility		Reason for Need: Knowing the service provider's belief of mobility
	may assist the PSAP with the handling of the call.		may assist the PSAP with the handling of the call.
	How Used by Call Taker: To determine whether to assume the location		How Used by Call Taker: To determine whether to assume the location
	of the caller might change.		of the caller might change.
	3.2.4. emergencyCall.SvcInfo Example		3.2.4. 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
	3.3. Device Information		3.3. Device Information
	This block provides information about the device used to place the		This block provides information about the device used to place the
	call. It should be provided by any service provider that knows what		call. It should be provided by any service provider that knows what
	device is being used, and by the device itself. The mime subtype is		device is being used, and by the device itself. The mime subtype is
	"application/emergencyCall.DevInfo+xml".		"application/emergencyCall.DevInfo+xml".
	3.3.1. Device Classification		3.3.1. Device Classification
	Data Element: Device Classification		Data Element: Device Classification
	Use: Optional		Use: Optional
	XML Element: <DeviceClassification>		XML Element: <DeviceClassification>
	Description: This data element defines the kind of device making the		Description: This data element defines the kind of device making the
	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. The registry with the initial set of		making the emergency call. The registry with the initial set of
	skipping to change at page 18, line 32 ¶		skipping to change at page 18, line 36 ¶
	| PDA | Personal digital assistant |		| PDA | Personal digital assistant |
	| PND | Personal navigation device) |		| PND | Personal navigation device) |
	| SmrtPhn| Smart phone |		| SmrtPhn| Smart phone |
	| Itab | Internet tablet |		| Itab | Internet tablet |
	| Game | Gaming console |		| Game | Gaming console |
	| Video | Video phone |		| Video | Video phone |
	| Text | Other text device |		| Text | Other text device |
	| NA | Not Available |		| NA | Not Available |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	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 the calltaker some context about the caller, the		provide the calltaker some context about the caller, the
	capabilities of the device used for the call or the environment		capabilities of the device used for the call or the environment
	the device is being used in.		the device is being used in.
	3.3.2. Device Manufacturer		3.3.2. Device Manufacturer
	Data Element: Device Manufacturer		Data Element: Device Manufacturer
	Use: Optional
	XML Element: <DeviceMfgr>		Use: Optional
			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 the calltaker, but by		How Used by Call Taker: Probably not used by the calltaker, but by
	PSAP management.		PSAP management.
	3.3.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 the calltaker, but by		How Used by Call Taker: Probably not used by the calltaker, but by
	PSAP management.		PSAP management.
	3.3.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 the calltaker they		How Used by Call Taker: Probably not used by the calltaker they would
	would need to refer to management for investigation.		need to refer to management for investigation.
	3.3.5. Type of Device Identifier		3.3.5. Type of Device Identifier
	Data Element: Type of Device Identifier
	Use: Conditional: must be provided if the DeviceID is provided		Data Element: Type of Device Identifier
	XML Element: <TypeOfDeviceID>		Use: Conditional: must be provided if the DeviceID is provided
	Description: Identifies the type of device identifier being		XML Element: <TypeOfDeviceID>
	generated in the unique device identifier data element. A		Description: Identifies the type of device identifier being generated
	registry with an initial set of values can be seen in Figure 6.		in the unique device identifier data element. A registry with an
			initial set of values can be seen in Figure 6.
	+--------+----------------------------------------+		+--------+----------------------------------------+
	| Token | Description |		| Token | Description |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	| MEID | Mobile Equipment Identifier (CDMA) |		| MEID | Mobile Equipment Identifier (CDMA) |
	| ESN | Electronic Serial Number(GSM) |		| ESN | Electronic Serial Number(GSM) |
	| MAC | Media Access Control Address (IEEE) |		| MAC | Media Access Control Address (IEEE) |
	| WiMAX | Device Certificate Unique ID |		| WiMAX | Device Certificate Unique ID |
	| IMEI | International Mobile Equipment ID (GSM)|		| IMEI | International Mobile Equipment ID (GSM)|
	| UDI | Unique Device Identifier |		| UDI | Unique Device Identifier |
	| RFID | Radio Frequency Identification |		| RFID | Radio Frequency Identification |
	| SN | Manufacturer Serial Number |		| SN | Manufacturer Serial Number |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	Figure 6: Registry with Device Identifier Types		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.
	3.3.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.
	3.3.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
	describe the type of data that can be retrieved from the Device/		describe the type of data that can be retrieved from the Device/
	service specific additional data structure. Initial values are:		service specific additional data structure. Initial values are:
	* IEEE 1512 - USDOT Model for traffic incidents		* IEEE 1512 - USDOT Model for traffic incidents
	* VEDS		* VEDS
	Reason for Need: This data element allows identification of		Reason for Need: This data element allows identification of
	externally defined schemas, which may have additional data that		externally defined schemas, which may have additional data that
	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.
	3.3.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 DevInfo block can be used		service specific additional data URL the DevInfo block can be used
	and a new type for it defined . The data passed would likely be the		and a new type for it defined . The data passed would likely be the
	same in both cases. Considerations for choosing which mechanism to		same in both cases. Considerations for choosing which mechanism to
	register under include:		register under include:
	Applicability: Information which will be carried by many kinds of		Applicability: Information which will be carried by many kinds of
	devices or services are more appropriately defined as separate		devices or services are more appropriately defined as separate
	blocks.		blocks.
	Privacy: Information which may contain private data may be better		Privacy: Information which may contain private data may be better
	sent in the DevInfo block, rather than a new block so that		sent in the DevInfo block, rather than a new block so that
	implementations are not tempted to send the data by value, and		implementations are not tempted to send the data by value, and
	thus having more exposure to the data than forcing the data to be		thus having more exposure to the data than forcing the data to be
	retrieved via the URL in DevInfo.		retrieved via the URL in DevInfo.
	Size: Information which may be very may be better sent in the		Size: Information which may be very may be better sent in the DevInfo
	DevInfo block, rather than a new block so that implementations are		block, rather than a new block so that implementations are not
	not tempted to send the data by value. Conversely, data which is		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).
	3.3.9. emergencyCall.DevInfo Example		3.3.9. 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 7: emergencyCallDevInfo Example
	3.4. Owner/Subscriber Information		3.4. Owner/Subscriber Information
	This block describes the owner of the device (if provided by the		This block describes the owner of the device (if provided by the
	device) or the subscriber information, if provided by a service		device) or the subscriber information, if provided by a service
	provider. The contact location is not necessarily the location of		provider. The contact location is not necessarily the location of
	the caller or incident, but is rather the nominal contact address.		the caller or incident, but is rather the nominal contact address.
	The mime subtype is "application/emergencyCall.Subscriber+xml".		The mime subtype is "application/emergencyCall.Subscriber+xml".
	3.4.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.
	3.4.2. emergencyCall.SubInfo Example		3.4.2. 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>
	<surname>Perreault</surname>		<surname>Perreault</surname>
	skipping to change at page 25, line 31 ¶		skipping to change at page 25, line 55 ¶
	<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
	3.5. Comment		3.5. Comment
	This block provides a mechanism for the data provider to supply		This block provides a mechanism for the data provider to supply
	extra, human readable information to the PSAP. It is not intended		extra, human readable information to the PSAP. It is not intended for
	for a general purpose extension mechanism. The mime subtype is		a general purpose extension mechanism. The mime subtype is
	"application/emergencyCall.Comment+xml"		"application/emergencyCall.Comment+xml"
	3.5.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
	3.5.2. emergencyCall.Comment Example		3.5.2. emergencyCall.Comment Example
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<sub:emergencyCall.Comment		<sub:emergencyCall.Comment
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"		xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<sub:Comment xml:lang="en">This is an example text.</sub:Comment>		<sub:Comment xml:lang="en">This is an example text.</sub:Comment>
	</sub:emergencyCall.Comment>		</sub:emergencyCall.Comment>
	Figure 9: EmergencyCall.Comment Example
	4. Transport		4. Transport
	This section defines how to convey additional data to an emergency		This section defines how to convey additional data to an emergency
	service provider. Two different means are specified: the first uses		service provider. Two different means are specified: the first uses
	the call signaling; the second uses the <provided-by> element of a		the call signaling; the second uses the <provided-by> element of a
	PIDF-LO [RFC4119].		PIDF-LO [RFC4119].
	1. First, the ability to embed a Uniform Resource Identifier (URI)		1. First, the ability to embed a Uniform Resource Identifier (URI)
	in an existing SIP header field, the Call-Info header, is		in an existing SIP header field, the Call-Info header, is
	defined. The URI points to the additional data structure. The		defined. The URI points to the additional data structure. The
	Call-Info header is specified in Section 20.9 of [RFC3261]. This		Call-Info header is specified in Section 20.9 of [RFC3261]. This
	document adds a new token with the value 'emergencyCallData' for		document adds a new compound token starting with the value
	the Call-Info "purpose" parameter. If the "purpose" parameter is		'emergencyCallData' for the Call-Info "purpose" parameter. If
	set to 'emergencyCallData' then the Call-Info header contains		the "purpose" parameter is set to a value starting with
	either an HTTPS URL pointing to an external resource or a CID		'emergencyCallData', then the Call-Info header contains either an
	(content indirection) URI that allows the data structure to be		HTTPS URL pointing to an external resource or a CID (content
	placed in the body of the SIP message. The "purpose" parameter		indirection) URI that allows the data structure to be placed in
	also contains an indication of what kind of data is available at		the body of the SIP message. The "purpose" parameter also
	the URI. As the data is conveyed using a URI in the SIP		indicates the kind of data (by its MIME type) that is available
			at the URI. As the data is conveyed using a URI in the SIP
	signaling, the data itself may reside on an external resource, or		signaling, the data itself may reside on an external resource, or
	may be contained within the body of the SIP message. When the		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		URI refers to data at an external resource, the data is said to
	be passed by reference. When the URI refers to data contained		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		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		by value. A PSAP or emergency responder is able to examine the
	type of data provided and selectively inspect the data it is		type of data provided and selectively inspect the data it is
	interested in, while forwarding all of it (the values or		interested in, while forwarding all of it (the values or
	references) to downstream entities. To be conveyed in a SIP body		references) to downstream entities. To be conveyed in a SIP
	additional data about a call is defined as a series of MIME		body, additional data about a call is defined as a series of MIME
	objects, each with an XML data structure contained inside. As		objects. Each block defined in this document is an XML data
	usual, whenever more than one MIME part is included in the body		structure identified by its MIME type. (Blocks defined by others
	of a message, MIME-multipart (i.e., 'multipart/mixed') encloses		may be encoded in XML or not, as identified by their MIME
	them all. This document defines the XML schemas and MIME types		registration.) As usual, whenever more than one MIME part is
	used for each block. When additional data is passed by value in		included in the body of a message, MIME-multipart (i.e.,
	the SIP signaling, each CID URL points to one block in the body.		'multipart/mixed') encloses them all. This document defines a
			set of XML schemas and MIME types used for each block defined
			here. 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 URIs are used within a Call-Info header field (or
	multiple Call-Info header fields) to point to multiple blocks.		multiple Call-Info header fields) to point to multiple blocks.
	When additional data is provided by reference (in SIP signaling		When additional data is provided by reference (in SIP signaling
	or Provided-By), each HTTPS URL references one block; the data is		or Provided-By), each HTTPS URL references one block; the data is
	retrieved with an HTTPS GET operation, which returns one of the		retrieved with an HTTPS GET operation, which returns one of the
	blocks as an XML object.		blocks as an object (the blocks defined here are returned as XML
			objects).
	2. Second, the ability to embed additional data structures in the		2. Second, the ability to embed additional data structures in the
	<provided-by> element of a PIDF-LO [RFC4119] is defined. Besides		<provided-by> element of a PIDF-LO [RFC4119] is defined. Besides
	a service provider in the call path, the access network provider		a service provider in the call path, the access network provider
	may also have similar information that may be valuable to the		may also have similar information that may be valuable to the
	PSAP. The access network provider may provide location in the		PSAP. The access network provider may provide location in the
	form of a PIDF-LO from a location server via a location		form of a PIDF-LO from a location server via a location
	configuration protocol. The data structures described in this		configuration protocol. The data structures described in this
	document are not specific to the location itself, but rather		document are not specific to the location itself, but rather
	provides descriptive information having to do with the immediate		provides descriptive information having to do with the immediate
	circumstances about the provision of the location (who the access		circumstances about the provision of the location (who the access
	network is, how to contact that entity, what kind of service the		network is, how to contact that entity, what kind of service the
	access network provides, subscriber information, etc.). This		access network provides, subscriber information, etc.). This
	data is similar in nearly every respect to the data known by		data is similar in nearly every respect to the data known by
	service providers in the path of the call. When the access		service providers in the path of the call. When the access
	network provider and service provider are separate entities, the		network provider and service provider are separate entities, the
	access network does not participate in the application layer		access network does not participate in the application layer
	skipping to change at page 27, line 44 ¶		skipping to change at page 28, line 34 ¶
	PIDF-LO is a mechanism for the access network provider to supply		PIDF-LO is a mechanism for the access network provider to supply
	the information about the entity or organization that supplied		the information about the entity or organization that supplied
	this location information. For this reason, this document		this location information. For this reason, this document
	describes a namespace per RFC 4119 for inclusion in the		describes a namespace per RFC 4119 for inclusion in the
	<provided-by> element of a PIDF-LO for adding information known		<provided-by> element of a PIDF-LO for adding information known
	to the access network provider.		to the access network provider.
	One or more blocks of data registered in the Emergency Call		One or more blocks of data registered in the Emergency Call
	Additional Data registry, as defined in Section 9.1, may be included		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 referenced in the SIP signaling (using the Call-Info header field)
	or in the <provided-by> element of a PIDF-LO. Every block must be		or in the <provided-by> element of a PIDF-LO. Every block must be one
	one of the types in the registry. Since the data of an emergency		of the types in the registry. Since the data of an emergency call
	call may come from multiple sources, the data itself needs		may come from multiple sources, the data itself needs information
	information describing the source. Consequently, each entity adding		describing the source. Consequently, each entity adding additional
	additional data MUST supply the "Data Provider" block. All other		data MUST supply the "Data Provider" block. All other blocks are
	blocks are optional, but each entity SHOULD supply any blocks where		optional, but each entity SHOULD supply any blocks where it has at
	it has at least some of the information in the block.		least some of the information in the block.
	4.1. Transmitting Blocks using the Call-Info Header		4.1. Transmitting Blocks using the Call-Info Header
	A URI to a block MAY be inserted in a SIP request or response method		A URI to a block MAY be inserted in a SIP request or response method
	(most often INVITE or MESSAGE) with a Call-Info header field		(most often INVITE or MESSAGE) with a Call-Info header field
	containing a purpose of "emergencyCallData" together with the type of		containing a purpose value starting with 'emergencyCallData' and the
	data available at the URI. The type of data is denoted by including		type of data available at the URI. The type of data is denoted by
	the root of the MIME type (not including the emergencyCall prefix and		including the root of the MIME type (not including the
	the +xml suffix) with a "." separator. For example, when referencing		'emergencyCall' prefix and any suffix such as '+xml') with a '.'
	a block with MIME type 'application/emergencyCall.ProviderInfo+xml',		separator. For example, when referencing a block with MIME type
	the 'purpose' parameter is set to 'emergencyCallData.ProviderInfo'.		'application/emergencyCall.ProviderInfo+xml', the 'purpose' parameter
	An example "Call-Info" header field for this would be:		is set to 'emergencyCallData.ProviderInfo'. An example "Call-Info"
			header field for this would be:
	Call-Info: https://www.example.com/23sedde3;		Call-Info: https://www.example.com/23sedde3;
	purpose="emergencyCallData.ProviderInfo"		purpose="emergencyCallData.ProviderInfo"
	The Call-info header with purpose='emergencyCallData' MUST only be		A Call-info header with a purpose value starting with
	sent on an emergency call, which can be ascertained by the presence		'emergencyCallData' MUST only be sent on an emergency call, which can
	of an emergency service urn in a Route header of a SIP message.		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		If the data is provided by reference, an HTTPS URI MUST be included
	and consequently Transport Layer Security (TLS) protection is applied		and consequently Transport Layer Security (TLS) protection is applied
	for protecting the retrieval of the information.		for protecting the retrieval of the information.
	The data may also be supplied by value in a SIP message. In this		The data may also be supplied by value in a SIP message. In this
	case, Content Indirection (CID) [RFC2392] is used, with the CID URL		case, Content Indirection (CID) [RFC2392] is used, with the CID URL
	referencing the MIME body part.		referencing the MIME body part.
	More than one Call-Info header with an emergencyCallData purpose can		More than one Call-Info header with a purpose value starting with
	be expected, but at least one MUST be provided. The device MUST		'emergencyCallData' can be expected, but at least one MUST be
	provide one if it knows no service provider is in the path of the		provided. The device MUST provide one if it knows no service
	call. The device MAY insert one if it uses a service provider. Any		provider is in the path of the call. The device MAY insert one if it
	service provider in the path of the call MUST insert its own. For		uses a service provider. Any service provider in the path of the
	example, a device, a telematics service provider in the call path, as		call MUST insert its own. For example, a device, a telematics
	well as the mobile carrier handling the call will each provide one.		service provider in the call path, as well as the mobile carrier
	There may be circumstances where there is a service provider who is		handling the call will each provide one. There may be circumstances
	unaware that the call is an emergency call and cannot reasonably be		where there is a service provider who is unaware that the call is an
	expected to determine that it is an emergency call. In that case,		emergency call and cannot reasonably be expected to determine that it
	that service provider is not expected to provide emergencyCallData.		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		4.2. Transmitting Blocks by Reference using the Provided-By Element
	The 'emergencyCallDataReference' element is used to transmit an		The 'emergencyCallDataReference' element is used to transmit an
	additional data block by reference within a 'Provided-By' element of		additional data block by reference within a 'Provided-By' element of
	a PIDF-LO. The 'emergencyCallDataReference' element has two		a PIDF-LO. The 'emergencyCallDataReference' element has two
	attributes: 'ref' to specify the URL, and 'purpose' to indicate the		attributes: 'ref' to specify the URL, and 'purpose' to indicate the
	type of data block referenced. The value of 'ref' is an HTTPS URL		type of data block referenced. The value of 'ref' is an HTTPS URL
	that resolves to a data structure with information about the call.		that resolves to a data structure with information about the call.
	The value of 'purpose' is the same as used in a 'Call-Info' header		The value of 'purpose' is the same as used in a 'Call-Info' header
	field (as specified in Section 4.1).		field (as specified in Section 4.1).
	For example, to reference a block with MIME type 'application/		For example, to reference a block with MIME type 'application/
	skipping to change at page 29, line 22 ¶		skipping to change at page 30, line 4 ¶
	For example, to reference a block with MIME type 'application/		For example, to reference a block with MIME type 'application/
	emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to		emergencyCall.ProviderInfo+xml', the 'purpose' parameter is set to
	'emergencyCallData.ProviderInfo'. An example		'emergencyCallData.ProviderInfo'. An example
	'emergencyCallDataReference' element for this would be:		'emergencyCallDataReference' element for this would be:
	<emergencyCallDataReference ref="https://www.example.com/23sedde3"		<emergencyCallDataReference ref="https://www.example.com/23sedde3"
	purpose="emergencyCallData.ProviderInfo"/>		purpose="emergencyCallData.ProviderInfo"/>
	4.3. Transmitting Blocks by Value using the Provided-By Element		4.3. Transmitting Blocks by Value using the Provided-By Element
	It is RECOMMENDED that access networks supply the data specified in		It is RECOMMENDED that access networks supply the data specified in
	this document by reference, but they MAY provide the data by value.		this document by reference, but they MAY provide the data by value.
	The 'emergencyCallDataValue' element is used to transmit an		The 'emergencyCallDataValue' element is used to transmit an
	additional data block by value within a 'Provided-By' element of a		additional data block by value within a 'Provided-By' element of a
	PIDF-LO. The 'emergencyCallDataValue' element has one attribute:		PIDF-LO. The 'emergencyCallDataValue' element has one attribute:
	'purpose' to indicate the type of data block contained. The value of		'purpose' to indicate the type of data block contained. The value of
	'purpose' is the same as used in a 'Call-Info' header field (as		'purpose' is the same as used in a 'Call-Info' header field (as
	specified in Section 4.1, and in Section 4.1). The same XML		specified in Section 4.1, and in Section 4.1). The same XML
	structure as would be wrapped in the corresponding MIME type is		structure as would be contained in the corresponding MIME type body
	placed inside the emergencyCallDataValue element.		part is placed inside the 'emergencyCallDataValue' element.
	For example:		For example:
	<provided-by		<provided-by
	xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData">		xmlns="urn:ietf:params:xml:ns:emergencyCallAddlData">
	<emergencyCallData>		<emergencyCallData>
	<byRef purpose="emergencyCallData.SvcInfo"		<byRef purpose="emergencyCallData.SvcInfo"
	ref="https://example.com/ref2"/>		ref="https://example.com/ref2"/>
	<sub:emergencyCall.Comment		<sub:emergencyCall.Comment
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment">		xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.Comment">
	skipping to change at page 30, line 12 ¶		skipping to change at page 30, line 40 ¶
	purpose="emergencyCallData.ProviderInfo">		purpose="emergencyCallData.ProviderInfo">
	<ProviderID>Test</ProviderID>		<ProviderID>Test</ProviderID>
	<ProviderIDSeries>NENA</ProviderIDSeries>		<ProviderIDSeries>NENA</ProviderIDSeries>
	<TypeOfProviderID>Access Infrastructure Provider		<TypeOfProviderID>Access Infrastructure Provider
	</TypeOfProviderID>		</TypeOfProviderID>
	<ContactURI>sip:15555550987@burf.example.com;user=phone		<ContactURI>sip:15555550987@burf.example.com;user=phone
	</ContactURI>		</ContactURI>
	</emergencyCallDataValue>		</emergencyCallDataValue>
	</provided-by>		</provided-by>
	Example Provided-By by Value.
	4.4. The Content-Disposition Parameter		4.4. The Content-Disposition Parameter
	RFC 5621 [RFC5621] discusses the handling of message bodies in SIP.		RFC 5621 [RFC5621] discusses the handling of message bodies in SIP.
	It updates and clarifies handling originally defined in RFC 3261		It updates and clarifies handling originally defined in RFC 3261
	[RFC3261] based on implementation experience. While RFC 3261 did not		[RFC3261] based on implementation experience. While RFC 3261 did not
	mandate support for 'multipart' message bodies 'multipart/mixed' MIME		mandate support for 'multipart' message bodies 'multipart/mixed' MIME
	bodies are, however, used by many extensions (including additional		bodies are, however, used by many extensions (including additional
	data) today. For example, adding a PIDF-LO, SDP, and additional data		data) today. For example, adding a PIDF-LO, SDP, and additional data
	in body of a SIP message requires a 'multipart' message body.		in body of a SIP message requires a 'multipart' message body.
	skipping to change at page 30, line 37 ¶		skipping to change at page 31, line 18 ¶
	type or disposition type it does not understand. If the 'handling'		type or disposition type it does not understand. If the 'handling'
	parameter has the value "optional", the UAS ignores the message body.		parameter has the value "optional", the UAS ignores the message body.
	If the 'handling' parameter has the value "required", the UAS returns		If the 'handling' parameter has the value "required", the UAS returns
	a 415 (Unsupported Media Type) response. The 'by-reference'		a 415 (Unsupported Media Type) response. The 'by-reference'
	disposition type allows a SIP message to contain a reference to the		disposition type allows a SIP message to contain a reference to the
	body part, and the SIP UA processes the body part according to the		body part, and the SIP UA processes the body part according to the
	reference. This is the case for the Call-info header containing a		reference. This is the case for the Call-info header containing a
	Content Indirection (CID) URL.		Content Indirection (CID) URL.
	As an example, a SIP message indicates the Content-Disposition		As an example, a SIP message indicates the Content-Disposition
	parameter in the body of the SIP message as shown in Figure 10.		parameter in the body of the SIP message as shown in Figure 11.
	Content-Type: application/sdp		Content-Type: application/sdp
	...Omit Content-Disposition here; defaults are ok		...Omit Content-Disposition here; defaults are ok
	...SDP goes here		...SDP goes here
	--boundary1		--boundary1
	Content-Type: application/pidf+xml		Content-Type: application/pidf+xml
	Content-ID: <target123@atlanta.example.com>		Content-ID: <target123@atlanta.example.com>
	skipping to change at page 31, line 4 ¶		skipping to change at page 31, line 30 ¶
	Content-Type: application/sdp		Content-Type: application/sdp
	...Omit Content-Disposition here; defaults are ok		...Omit Content-Disposition here; defaults are ok
	...SDP goes here		...SDP goes here
	--boundary1		--boundary1
	Content-Type: application/pidf+xml		Content-Type: application/pidf+xml
	Content-ID: <target123@atlanta.example.com>		Content-ID: <target123@atlanta.example.com>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	...PIDF-LO goes here		...PIDF-LO goes here
	--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>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	...Additional data goes here		...Additional data goes here
	--boundary1--		--boundary1--
	Figure 10: Example for use of the Content-Disposition Parameter in
	SIP.
	5. Examples		5. Examples
	This section provides three examples of communicating additional		This section provides three examples of communicating additional
	data. In Figure 11 additional data is communicated in a SIP INVITE		data. In Figure 12 additional data is communicated in a SIP INVITE
	per value. In Figure 12 we illustrate how additional data is added		per value. In Figure 13 we illustrate how additional data is added
	by a SIP proxy per reference. Finally, an example for including		by a SIP proxy per reference. Finally, an example for including
	additional data in the <Provided-By> element of a PIDF-LO is		additional data in the <Provided-By> element of a PIDF-LO is
	illustrated.		illustrated.
	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
	skipping to change at page 32, line 25 ¶		skipping to change at page 33, line 4 ¶
	--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>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	...Additional data goes here		...Additional data goes here
	--boundary1--		--boundary1--
	Figure 11: Example: Attaching Additional Data via CID to a SIP
	INVITE.
	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,
	<https://www.example.com/abc123456/>		<https://www.example.com/abc123456/>
	;purpose=emergencyCallData.ProviderInfo		;purpose=emergencyCallData.ProviderInfo
	skipping to change at page 33, line 4 ¶		skipping to change at page 33, line 25 ¶
	Geolocation-Routing: no		Geolocation-Routing: no
	Accept: application/sdp, application/pidf+xml,		Accept: application/sdp, application/pidf+xml,
	application/emergencyCallProviderinfo+xml		application/emergencyCallProviderinfo+xml
	CSeq: 31862 INVITE		CSeq: 31862 INVITE
	Contact: <sips:alice@atlanta.example.com>		Contact: <sips:alice@atlanta.example.com>
	Content-Type: multipart/mixed; boundary=boundary1		Content-Type: multipart/mixed; boundary=boundary1
	Content-Length: ...		Content-Length: ...
	--boundary1		--boundary1
	Content-Type: application/sdp		Content-Type: application/sdp
	...SDP goes here		...SDP goes here
	--boundary1		--boundary1
	Content-Type: application/pidf+xml		Content-Type: application/pidf+xml
	Content-ID: <target123@atlanta.example.com>		Content-ID: <target123@atlanta.example.com>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	...PIDF-LO goes here		...PIDF-LO goes here
	--boundary1--		--boundary1--
	Figure 12: Example: Attaching Additional Data per Reference in a SIP
	INVITE.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<presence xmlns="urn:ietf:params:xml:ns:pidf"		<presence xmlns="urn:ietf:params:xml:ns:pidf"
	xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"		xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
	xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"		xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"
	xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"		xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
	entity="pres:alice@atlanta.example.com">		entity="pres:alice@atlanta.example.com">
	<dm:device id="target123-1">		<dm:device id="target123-1">
	<gp:geopriv>		<gp:geopriv>
	<gp:location-info>		<gp:location-info>
	<civicAddress		<civicAddress
	skipping to change at page 34, line 25 ¶		skipping to change at page 35, line 4 ¶
	<emergencyCall.ProviderInfo		<emergencyCall.ProviderInfo
	xmlns="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo">		xmlns="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo">
	<DataProviderString>University of California, Irvine		<DataProviderString>University of California, Irvine
	</DataProviderString>		</DataProviderString>
	<ProviderID>urn:nena:companyid:uci</ProviderID>		<ProviderID>urn:nena:companyid:uci</ProviderID>
	<ProviderIDSeries>NENA</ProviderIDSeries>		<ProviderIDSeries>NENA</ProviderIDSeries>
	<TypeOfProvider>Other</TypeOfProvider>		<TypeOfProvider>Other</TypeOfProvider>
	<ContactURI>tel:+1 9498245222</ContactURI>		<ContactURI>tel:+1 9498245222</ContactURI>
	<Language>EN</Language>		<Language>EN</Language>
	</emergencyCall.ProviderInfo>		</emergencyCall.ProviderInfo>
	<emergencyCall.Comment		<emergencyCall.Comment
	xmlns="urn:ietf:params:xml:ns:emergencyCall.Comment">		xmlns="urn:ietf:params:xml:ns:emergencyCall.Comment">
	<Comment xml:lang="en">This is an example text.</Comment>		<Comment xml:lang="en">This is an example text.</Comment>
	</emergencyCall.Comment>		</emergencyCall.Comment>
	</emergencyCallDataValue>		</emergencyCallDataValue>
	</provided-by>		</provided-by>
	</gp:geopriv>		</gp:geopriv>
	<dm:deviceID>mac:1234567890ab</dm:deviceID>		<dm:deviceID>mac:1234567890ab</dm:deviceID>
	<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>		<dm:timestamp>2013-07-09T20:57:29Z</dm:timestamp>
	</dm:device>		</dm:device>
	</presence>		</presence>
	Figure 13: Example: Including Additional Data via the Provided-By
	Element in a PIDF-LO.
	6. XML Schemas		6. XML Schemas
	This section defines the XML schemas of the five data blocks.		This section defines the XML schemas of the five data blocks.
	Additionally, the Provided-By schema is specified.		Additionally, the Provided-By schema is specified.
	6.1. emergencyCall.ProviderInfo XML Schema		6.1. emergencyCall.ProviderInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"		targetNamespace="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:pi="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"		xmlns:pi="urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	elementFormDefault="qualified"		elementFormDefault="qualified"
	attributeFormDefault="unqualified">		attributeFormDefault="unqualified">
	skipping to change at page 36, line 4 ¶		skipping to change at page 36, line 53 ¶
	<xs:element name="DataProviderContact"		<xs:element name="DataProviderContact"
	type="xc:vcardType" minOccurs="0"		type="xc:vcardType" minOccurs="0"
	maxOccurs="1"/>		maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 14: emergencyCall.ProviderInfo XML Schema
	6.2. emergencyCall.SvcInfo XML Schema		6.2. emergencyCall.SvcInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"		targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"		xmlns:svc="urn:ietf:params:xml:ns:emergencyCall.SvcInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	skipping to change at page 36, line 39 ¶		skipping to change at page 37, line 35 ¶
	<xs:element name="Link"		<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 15: emergencyCall.SvcInfo XML Schema
	6.3. emergencyCall.DevInfo XML Schema		6.3. emergencyCall.DevInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"		targetNamespace="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:dev="urn:ietf:params:xml:ns:emergencyCall.DevInfo"		xmlns:dev="urn:ietf:params:xml:ns:emergencyCall.DevInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:element name="emergencyCall.DevInfo" type="dev:DevInfoType"/>		<xs:element name="emergencyCall.DevInfo" type="dev:DevInfoType"/>
	<xs:complexType name="DevInfoType">		<xs:complexType name="DevInfoType">
	<xs:sequence>		<xs:sequence>
	<xs:element name="DeviceClassification"		<xs:element name="DeviceClassification"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="DeviceMfgr"		<xs:element name="DeviceMfgr"
	skipping to change at page 37, line 33 ¶		skipping to change at page 38, line 41 ¶
	<xs:element name="DeviceSpecificType"		<xs:element name="DeviceSpecificType"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 16: emergencyCall.DevInfo XML Schema
	6.4. emergencyCall.SubInfo XML Schema		6.4. emergencyCall.SubInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"		targetNamespace="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"		xmlns:sub="urn:ietf:params:xml:ns:emergencyCall.SubInfo"
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	skipping to change at page 38, line 19 ¶		skipping to change at page 39, line 32 ¶
	<xs:element name="SubscriberData" type="xc:vcardType"		<xs:element name="SubscriberData" type="xc:vcardType"
	minOccurs="0" maxOccurs="1" />		minOccurs="0" maxOccurs="1" />
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 17: emergencyCall.SubInfo XML Schema
	6.5. emergencyCall.Comment XML Schema		6.5. emergencyCall.Comment XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"		targetNamespace="urn:ietf:params:xml:ns:emergencyCall.Comment"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:com="urn:ietf:params:xml:ns:emergencyCall.Comment"		xmlns:com="urn:ietf:params:xml:ns:emergencyCall.Comment"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	elementFormDefault="qualified" attributeFormDefault="unqualified">		elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	skipping to change at page 39, line 4 ¶		skipping to change at page 40, line 33 ¶
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	<xs:complexType name="CommentSubType">		<xs:complexType name="CommentSubType">
	<xs:simpleContent>		<xs:simpleContent>
	<xs:extension base="xs:string">		<xs:extension base="xs:string">
	<xs:attribute ref="xml:lang"/>		<xs:attribute ref="xml:lang"/>
	</xs:extension>		</xs:extension>
	</xs:simpleContent>		</xs:simpleContent>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 18: EmergencyCall.Comment XML Schema
	6.6. Provided-By XML Schema		6.6. Provided-By XML Schema
	This section defines the Provided-By schema.		This section defines the Provided-By schema.
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace=		targetNamespace=
	"urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"		"urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"		xmlns:ad="urn:ietf:params:xml:ns:pidf:geopriv10:emergencyCallData"
	skipping to change at page 40, line 52 ¶		skipping to change at page 42, line 37 ¶
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 19: Provided-By XML Schema
	7. Security Considerations		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
	skipping to change at page 42, line 26 ¶		skipping to change at page 44, line 7 ¶
	protection regulation world-wide has, however, decided to create		protection regulation world-wide has, however, decided to create
	exceptions for emergency services since the drawbacks of disclosing		exceptions for emergency services since the drawbacks of disclosing
	personal data in comparison to the benefit for the emergency caller		personal data in comparison to the benefit for the emergency caller
	are often towards the latter. Hence, the data protection rights of		are often towards the latter. Hence, the data protection rights of
	individuals are often waived for emergency situations. There are,		individuals are often waived for emergency situations. There are,
	however, still various countries that offer some degree of anonymity		however, still various countries that offer some degree of anonymity
	for the caller towards PSAP call takers.		for the caller towards PSAP call takers.
	The functionality defined in this document, however, far exceeds the		The functionality defined in this document, however, far exceeds the
	amount of information sharing found in the Plain old telephone system		amount of information sharing found in the Plain old telephone system
	(POTS). For this reason there are additional privacy threats to		(POTS). For this reason there are additional privacy threats to
	consider, which are described in more detail in		consider, which are described in more detail in [I-D.iab-privacy-
	[I-D.iab-privacy-considerations].		considerations].
	Stored Data Compromise: First, there is an increased risk of stored		Stored Data Compromise: First, there is an increased risk of stored
	data compromise since additional data is collected and stored in		data compromise since additional data is collected and stored in
	databases. Without adequate measures to secure stored data from		databases. Without adequate measures to secure stored data from
	unauthorized or inappropriate access at access network operators,		unauthorized or inappropriate access at access network operators,
	service providers, end devices, as well as PSAPs individuals are		service providers, end devices, as well as PSAPs individuals are
	exposed to potential financial, reputational, or physical harm.		exposed to potential financial, reputational, or physical harm.
	Misattribution: If the personal data collected and conveyed is		Misattribution: If the personal data collected and conveyed is
	incorrect or inaccurate then this may lead to misattribution.		incorrect or inaccurate then this may lead to misattribution.
	Misattribution occurs when data or communications related to one		Misattribution occurs when data or communications related to one
	individual are attributed to another.		individual are attributed to another.
	Identification: By the nature of the additional data and its		Identification: By the nature of the additional data and its
	capability to provide much richer information about the caller,		capability to provide much richer information about the caller,
	the call, and the location the calling party is identified in a		the call, and the location the calling party is identified in a
	much better way. Some users may feel uncomfortable with this		much better way. Some users may feel uncomfortable with this
	degree of information sharing even in emergency services		degree of information sharing even in emergency services
	situations.		situations.
	Secondary Use: Furthermore, there is the risk of secondary use.		Secondary Use: Furthermore, there is the risk of secondary use.
	Secondary use is the use of collected information about an		Secondary use is the use of collected information about an
	individual without the individual's consent for a purpose		individual without the individual's consent for a purpose
	different from that for which the information was collected. The		different from that for which the information was collected. The
	stated purpose of the additional data is for emergency services		stated purpose of the additional data is for emergency services
	purposes but theoretically the same information could be used for		purposes but theoretically the same information could be used for
	any other call as well. Additionally, parties involved in the		any other call as well. Additionally, parties involved in the
	emergency call may retain the obtained information and may re-use		emergency call may retain the obtained information and may re-use
	it for other, non-emergency services purposes.		it for other, non-emergency services purposes.
	Disclosure: When the data defined in this document is not properly		Disclosure: When the data defined in this document is not properly
	security (while in transit with traditional communication security		security (while in transit with traditional communication security
	techniques, and while at rest using access control mechanisms)		techniques, and while at rest using access control mechanisms)
	there is the risk of disclosure, which is the revelation of		there is the risk of disclosure, which is the revelation of
	information about an individual that affects the way others judge		information about an individual that affects the way others judge
	the individual.		the individual.
	To mitigate these privacy risks the following countermeasures can be		To mitigate these privacy risks the following countermeasures can be
	taken.		taken.
	In regions where callers can elect to suppress certain personally		In regions where callers can elect to suppress certain personally
	skipping to change at page 43, line 50 ¶		skipping to change at page 45, line 35 ¶
	years have shown data breaches are not not uncommon and are often		years have shown data breaches are not not uncommon and are often
	caused by lack of proper access control frameworks, software bugs		caused by lack of proper access control frameworks, software bugs
	(buffer overflows), or missing input parsing (SQL injection attacks).		(buffer overflows), or missing input parsing (SQL injection attacks).
	The risks of data breaches is increased with the obligation for		The risks of data breaches is increased with the obligation for
	emergency services to retain emergency call related data for extended		emergency services to retain emergency call related data for extended
	periods, e.g., several years are the norm.		periods, e.g., several years are the norm.
	Finally, it is also worth to highlight the nature of the SIP		Finally, it is also worth to highlight the nature of the SIP
	communication architecture, which introduces additional complications		communication architecture, which introduces additional complications
	for privacy. Some forms of data can be sent by value in the SIP		for privacy. 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		signaling or by value (URL in SIP signaling). When data is sent by
	value, all intermediaries have access to the data. As such, these		value, all intermediaries have access to the data. As such, these
	intermediaries may also introduce additional privacy risk.		intermediaries may also introduce additional privacy risk.
	Therefore, in situations where the conveyed information raises		Therefore, in situations where the conveyed information raises
	privacy concerns and intermediaries are involved transmitting a		privacy concerns and intermediaries are involved transmitting a
	reference is more appropriate (assuming proper access control		reference is more appropriate (assuming proper access control
	policies are available for distinguishing the different entities		policies are available for distinguishing the different entities
	dereferencing the reference). Without access control policies any		dereferencing the reference). Without access control policies any
	party in possession of the reference is able to resolve the reference		party in possession of the reference is able to resolve the reference
	and to obtain the data, including intermediaries.		and to obtain the data, including intermediaries.
	9. IANA Considerations		9. IANA Considerations
	9.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 sub-registries are created in		Additional Data'. The following sub-registries are created in
	Emergency Call Additional Data:		Emergency Call Additional Data:
	skipping to change at page 44, line 22 ¶		skipping to change at page 46, line 4 ¶
	9. IANA Considerations		9. IANA Considerations
	9.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 sub-registries are created in		Additional Data'. The following sub-registries are created in
	Emergency Call Additional Data:		Emergency Call Additional Data:
	9.1.1. Provider ID Series Registry		9.1.1. Provider ID Series Registry
	This document creates a new sub-registry called 'Additional Call Data		This document creates a new sub-registry 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 initial set of values is listed in Figure 20.		The initial set of values is listed in Figure 21.
	+-----------+--------------------------+----------------------+		+-----------+--------------------------+----------------------+
	| Name | Source | URL |		| Name | Source | URL |
	+-----------+--------------------------+----------------------+		+-----------+--------------------------+----------------------+
	| NENA | National Emergency | http://www.nena.org |		| NENA | National Emergency | http://www.nena.org |
	| | Number Association | |		| | Number Association | |
	| EENA | European Emergency | http://www.eena.org |		| EENA | European Emergency | http://www.eena.org |
	| | Number Association | |		| | Number Association | |
	+-----------+--------------------------+----------------------+		+-----------+--------------------------+----------------------+
	Figure 20: Provider ID Series Registry
	9.1.2. Service Provider Type Registry		9.1.2. Service Provider Type Registry
	This document creates a new sub-registry called 'Service Provider		This document creates a new sub-registry called 'Service Provider
	Type'. As defined in [RFC5226], this registry operates under "Expert		Type'. As defined in [RFC5226], this registry operates under "Expert
	Review". The expert should determine that the proposed new value is		Review". The expert should determine that the proposed new value is
	distinct from existing values and appropriate for use in the		distinct from existing values and appropriate for use in the
	TypeOfServicerProvider element		TypeOfServicerProvider element
	The content of this registry includes:		The content of this registry includes:
	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 initial set of values is defined in Figure 1.		The initial set of values is defined in Figure 1.
	9.1.3. Service Delivered Registry		9.1.3. Service Delivered Registry
	This document creates a new sub-registry called 'Service Delivered'.		This document creates a new sub-registry called 'Service Delivered'.
	As defined in [RFC5226], this registry operates under "Expert Review"		As defined in [RFC5226], this registry operates under "Expert Review"
	rules. The expert should consider whether the proposed service is		rules. The expert should consider whether the proposed service is
	unique from existing services and the definition of the service will		unique from existing services and the definition of the service will
	be clear to implementors and PSAPS/responders.		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 initial set of values are defined in Figure 3.		The initial set of values are defined in Figure 3.
	9.1.4. Device Classification Registry		9.1.4. Device Classification Registry
	This document creates a new sub-registry called 'Device		This document creates a new sub-registry called 'Device
	Classification'. As defined in [RFC5226], this registry operates		Classification'. 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 class is unique from existing classes and the definition of		proposed class is unique from existing classes and the definition of
	the class will be clear to implementors and PSAPS/responders.		the class 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 device classification.		Name: Enumeration token of the device classification.
	Description: Short description identifying the device type.		Description: Short description identifying the device type.
	The initial set of values are defined in Figure 5.		The initial set of values are defined in Figure 5.
	9.1.5. Device ID Type Type Registry		9.1.5. Device ID Type Type Registry
	This document creates a new sub-registry called 'Additional Call Data		This document creates a new sub-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 initial set of values are defined in Figure 6.		The initial set of values are defined in Figure 6.
	9.1.6. Device/Service Data Type Registry		9.1.6. Device/Service Data Type Registry
	This document creates a new sub-registry called 'Device/Service Data		This document creates a new sub-registry called 'Device/Service Data
	Type Registry'. As defined in [RFC5226], this registry operates		Type Registry'. As defined in [RFC5226], this registry operates
	under "Expert Review" and "Specification Required" rules. The expert		under "Expert Review" and "Specification Required" rules. The expert
	should ascertain that the proposed type is well understood, and		should ascertain that the proposed type is well understood, and
	provides information useful to PSAPs and responders. The		provides information useful to PSAPs and responders. The
	specification must contain a complete description of the data, and a		specification must contain a complete description of the data, and a
	precise format specification suitable to allow interoperable		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 initial set of values are listed in Figure 21.		The initial set of values are listed in Figure 22.
	+---------+----------------------------------------+----------------+		+---------+----------------------------------------+----------------+
	| Token | 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 |
	+---------+----------------------------------------+----------------+		+---------+----------------------------------------+----------------+
	Figure 21: Device/Service Data Type Registry
	9.1.7. Additional Data Blocks Registry		9.1.7. Additional Data Blocks Registry
	This document creates a new sub-registry called 'Additional Data		This document creates a new sub-registry called 'Additional Data
	Blocks' in the purpose registry established by RFC 3261 [RFC3261].		Blocks' in the purpose registry established by RFC 3261 [RFC3261].
	As defined in [RFC5226], this registry operates under "Expert Review"		As defined in [RFC5226], this registry operates under "Expert Review"
	and "Specification Required" rules. The expert is responsible for		and "Specification Required" rules. The expert is responsible for
	verifying that the document contains a complete and clear		verifying that the document contains a complete and clear
	specification and the proposed functionality does not obviously		specification and the proposed functionality does not obviously
	duplicate existing functionality.		duplicate existing functionality.
	The content of this registry includes:		The content of this registry includes:
	Name: Element Name of enclosing block.		Name: Element Name of enclosing block.
	Reference: The document that describes the block		Reference: The document that describes the block
	The initial set of values are listed in Figure 22.		The initial set of values are listed in Figure 23.
	+--------------+------------+		+--------------+------------+
	| Token | Reference |		| Token | Reference |
	+--------------+------------+		+--------------+------------+
	| ProviderInfo | [This RFC] |		| ProviderInfo | [This RFC] |
	| SvcInfo | [This RFC] |		| SvcInfo | [This RFC] |
	| DevInfo | [This RFC] |		| DevInfo | [This RFC] |
	| Subscriber | [This RFC] |		| Subscriber | [This RFC] |
	| Comment | [This RFC] |		| Comment | [This RFC] |
	+--------------+------------+		+--------------+------------+
	Figure 22: Additional Data Blocks Registry
	9.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
	---------- --------- ----------------- ---------		---------- --------- ----------------- ---------
	skipping to change at page 48, line 23 ¶		skipping to change at page 49, line 28 ¶
	9.4. MIME Registrations		9.4. MIME Registrations
	9.4.1. MIME Content-type Registration for 'application/		9.4.1. MIME Content-type Registration for 'application/
	emergencyCall.ProviderInfo+xml'		emergencyCall.ProviderInfo+xml'
	This specification requests the registration of a new MIME type		This specification requests the registration of a new MIME type
	according to the procedures of RFC 4288 [RFC4288] and guidelines in		according to the procedures of RFC 4288 [RFC4288] and guidelines in
	RFC 3023 [RFC3023].		RFC 3023 [RFC3023].
	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
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See Section
	Section 3.2 of RFC 3023 [RFC3023].		3.2 of RFC 3023 [RFC3023].
	Security considerations: This content type is designed to carry		Security considerations: This content type is designed to carry
	the data provider information, which is a sub-category of		the data provider information, which is a sub-category of
	additional data about an emergency call. Since this data contains		additional data about an emergency call. Since this data contains
	personal information appropriate precautions have to be taken to		personal information appropriate precautions have to be taken to
	limit unauthorized access, inappropriate disclosure to third		limit unauthorized access, inappropriate disclosure to third
	parties, and eavesdropping of this information. Please refer to		parties, and eavesdropping of this information. Please refer to
	Section 7 and Section 8 for more information.		Section 7 and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
			Additional information: Magic Number: None File Extension: .xml
			Macintosh file type code: 'TEXT'
	Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.2. MIME Content-type Registration for 'application/		9.4.2. MIME Content-type Registration for 'application/
	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
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See Section
	Section 3.2 of RFC 3023 [RFC3023].		3.2 of RFC 3023 [RFC3023].
	Security considerations: This content type is designed to carry		Security considerations: This content type is designed to carry
	the service information, which is a sub-category of additional		the service information, which is a sub-category of additional
	data about an emergency call. Since this data contains personal		data about an emergency call. Since this data contains personal
	information appropriate precautions have to be taken to limit		information appropriate precautions have to be taken to limit
	unauthorized access, inappropriate disclosure to third parties,		unauthorized access, inappropriate disclosure to third parties,
	and eavesdropping of this information. Please refer to Section 7		and eavesdropping of this information. Please refer to Section 7
	and Section 8 for more information.		and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
			Intended usage: LIMITED USE
	Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.3. MIME Content-type Registration for 'application/		9.4.3. MIME Content-type Registration for 'application/
	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
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See Section
	Section 3.2 of RFC 3023 [RFC3023].		3.2 of RFC 3023 [RFC3023].
	Security considerations: This content type is designed to carry		Security considerations: This content type is designed to carry
	the device information information, which is a sub-category of		the device information information, which is a sub-category of
	additional data about an emergency call. Since this data contains		additional data about an emergency call. Since this data contains
	personal information appropriate precautions have to be taken to		personal information appropriate precautions have to be taken to
	limit unauthorized access, inappropriate disclosure to third		limit unauthorized access, inappropriate disclosure to third
	parties, and eavesdropping of this information. Please refer to		parties, and eavesdropping of this information. Please refer to
	Section 7 and Section 8 for more information.		Section 7 and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.4. MIME Content-type Registration for 'application/		9.4.4. MIME Content-type Registration for 'application/
	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
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See Section
	Section 3.2 of RFC 3023 [RFC3023].		3.2 of RFC 3023 [RFC3023].
	Security considerations: This content type is designed to carry		Security considerations: This content type is designed to carry
	owner/subscriber information, which is a sub-category of		owner/subscriber information, which is a sub-category of
	additional data about an emergency call. Since this data contains		additional data about an emergency call. Since this data contains
	personal information appropriate precautions have to be taken to		personal information appropriate precautions have to be taken to
	limit unauthorized access, inappropriate disclosure to third		limit unauthorized access, inappropriate disclosure to third
	parties, and eavesdropping of this information. Please refer to		parties, and eavesdropping of this information. Please refer to
	Section 7 and Section 8 for more information.		Section 7 and Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.4.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
	Optional parameters: charset Indicates the character encoding of		Optional parameters: charset Indicates the character encoding of
	enclosed XML.		enclosed XML.
	Encoding considerations: Uses XML, which can employ 8-bit		Encoding considerations: Uses XML, which can employ 8-bit
	characters, depending on the character encoding used. See		characters, depending on the character encoding used. See Section
	Section 3.2 of RFC 3023 [RFC3023].		3.2 of RFC 3023 [RFC3023].
	Security considerations: This content type is designed to carry a		Security considerations: This content type is designed to carry a
	comment, which is a sub-category of additional data about an		comment, which is a sub-category of additional data about an
	emergency call. This data may contain personal information.		emergency call. This data may contain personal information.
	Appropriate precautions may have to be taken to limit unauthorized		Appropriate precautions may have to be taken to limit unauthorized
	access, inappropriate disclosure to third parties, and		access, inappropriate disclosure to third parties, and
	eavesdropping of this information. Please refer to Section 7 and		eavesdropping of this information. Please refer to Section 7 and
	Section 8 for more information.		Section 8 for more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information: Magic Number: None File Extension: .xml		Additional information: Magic Number: None File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Person and email address for further information: Hannes		Person and email address for further information: Hannes
	Tschofenig, Hannes.Tschofenig@gmx.net		Tschofenig, Hannes.Tschofenig@gmx.net
	Intended usage: LIMITED USE		Intended usage: LIMITED USE
	Author: This specification is a work item of the IETF ECRIT		Author: This specification is a work item of the IETF ECRIT
	working group, with mailing list address <ecrit@ietf.org>.		working group, with mailing list address <ecrit@ietf.org>.
	Change controller: The IESG <ietf@ietf.org>		Change controller: The IESG <ietf@ietf.org>
	9.5. URN Sub-Namespace Registration		9.5. URN Sub-Namespace Registration
	9.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:
	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>
	skipping to change at page 54, line 8 ¶		skipping to change at page 54, line 28 ¶
	</body>		</body>
	</html>		</html>
	END		END
	9.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:
	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>
	skipping to change at page 54, line 39 ¶		skipping to change at page 55, line 10 ¶
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.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">
	<head>		<head>
	skipping to change at page 55, line 25 ¶		skipping to change at page 55, line 41 ¶
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.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:
	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>
	skipping to change at page 56, line 11 ¶		skipping to change at page 56, line 29 ¶
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.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:
	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>
	skipping to change at page 56, line 42 ¶		skipping to change at page 57, line 10 ¶
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	9.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:
	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>
	skipping to change at page 57, line 36 ¶		skipping to change at page 57, line 46 ¶
	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 14.		XML: The XML schema can be found in Figure 15.
	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 15.		XML: The XML schema can be found in Figure 16.
	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 16.		XML: The XML schema can be found in Figure 17.
	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 6.4.		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-
	skipping to change at page 58, line 28 ¶		skipping to change at page 58, line 34 ¶
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Section 6.5.		XML: The XML schema can be found in Section 6.5.
	9.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
	applied on the "TEL" property.		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-900
	00		0
	10. 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 many NENA participants, including Delaine		comments provided by many NENA participants, including Delaine
	Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James		Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James
	skipping to change at page 59, line 15 ¶		skipping to change at page 59, line 18 ¶
	11. References		11. References
	11.1. Normative 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.
	[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,		[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
	F., Watson, M., and M. Zonoun, "MIME media types for ISUP		F., Watson, M. and M. Zonoun, "MIME media types for ISUP
	and QSIG Objects", RFC 3204, December 2001.		and QSIG Objects", RFC 3204, December 2001.
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M. and E. Schooler,
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		"SIP: Session Initiation Protocol", RFC 3261, June 2002.
	June 2002.
	[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private		[RFC3325] Jennings, C., Peterson, J. and M. Watson, "Private
	Extensions to the Session Initiation Protocol (SIP) for		Extensions to the Session Initiation Protocol (SIP) for
	Asserted Identity within Trusted Networks", RFC 3325,		Asserted Identity within Trusted Networks", RFC 3325,
	November 2002.		November 2002.
	[RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail		[RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail
	Extensions (MIME) Parameter", RFC 3459, January 2003.		Extensions (MIME) Parameter", RFC 3459, January 2003.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.		January 2004.
	skipping to change at page 60, line 12 ¶		skipping to change at page 60, line 9 ¶
	[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.
	11.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", Internet-Draft
	considerations-03 (work in progress), July 2012.		draft-iab-privacy-considerations-03, July 2012.
	[I-D.ietf-geopriv-relative-location]		[I-D.ietf-geopriv-relative-location]
	Thomson, M., Rosen, B., Stanley, D., Bajko, G., and A.		Thomson, M., Rosen, B., Stanley, D., Bajko, G. and A.
	Thomson, "Relative Location Representation", draft-ietf-		Thomson, "Relative Location Representation", Internet-
	geopriv-relative-location-05 (work in progress), June		Draft draft-ietf-geopriv-relative-location-06, July 2013.
	2013.
	[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.
	[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location		[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
	Format for Presence Information Data Format Location		Format for Presence Information Data Format Location
	Object (PIDF-LO)", RFC 5139, February 2008.		Object (PIDF-LO)", RFC 5139, February 2008.
	[RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.		[RFC5222] Hardie, T., Newton, A., Schulzrinne, H. and H. Tschofenig,
	Tschofenig, "LoST: A Location-to-Service Translation		"LoST: A Location-to-Service Translation Protocol", RFC
	Protocol", RFC 5222, August 2008.		5222, August 2008.
	[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig, "GEOPRIV		[RFC5491] Winterbottom, J., Thomson, M. and H. Tschofenig, "GEOPRIV
	Presence Information Data Format Location Object (PIDF-LO)		Presence Information Data Format Location Object (PIDF-LO)
	Usage Clarification, Considerations, and Recommendations",		Usage Clarification, Considerations, and Recommendations",
	RFC 5491, March 2009.		RFC 5491, March 2009.
	[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.		[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H. and M. Thomson,
	Thomson, "Dynamic Extensions to the Presence Information		"Dynamic Extensions to the Presence Information Data
	Data Format Location Object (PIDF-LO)", RFC 5962,		Format Location Object (PIDF-LO)", RFC 5962, September
	September 2010.		2010.
	[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC		[RFC5985] Barnes, M., "HTTP-Enabled Location Delivery (HELD)", RFC
	5985, September 2010.		5985, September 2010.
	[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,		[RFC6443] Rosen, B., Schulzrinne, H., Polk, J. and A. Newton,
	"Framework for Emergency Calling Using Internet		"Framework for Emergency Calling Using Internet
	Multimedia", RFC 6443, December 2011.		Multimedia", RFC 6443, December 2011.
	[RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B., and		[RFC6848] Winterbottom, J., Thomson, M., Barnes, R., Rosen, B. and
	R. George, "Specifying Civic Address Extensions in the		R. George, "Specifying Civic Address Extensions in the
	Presence Information Data Format Location Object (PIDF-		Presence Information Data Format Location Object (PIDF-
	LO)", RFC 6848, January 2013.		LO)", RFC 6848, January 2013.
	[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for		[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
	Communications Services in Support of Emergency Calling",		Communications Services in Support of Emergency Calling",
	BCP 181, RFC 6881, March 2013.		BCP 181, RFC 6881, March 2013.
	Appendix A. XML Schema for vCard/xCard		Appendix A. XML Schema for vCard/xCard
	This section contains the vCard/xCard XML schema version of the Relax		This section contains the vCard/xCard XML schema version of the Relax
	NG schema defined in RFC 6351 [RFC6351] for simplified use with the		NG schema defined in RFC 6351 [RFC6351] for simplified use with the
	XML schemas defined in this document. The schema in RFC 6351		XML schemas defined in this document. The schema in RFC 6351
	[RFC6351] is the normative source and this section is informative		[RFC6351] is the normative source and this section is informative
	only.		only.
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"		<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	elementFormDefault="qualified"		elementFormDefault="qualified"
	targetNamespace="urn:ietf:params:xml:ns:vcard-4.0"		targetNamespace="urn:ietf:params:xml:ns:vcard-4.0"
	skipping to change at page 83, line 32 ¶		skipping to change at page 81, line 48 ¶
	<xs:attribute name="name" use="required"/>		<xs:attribute name="name" use="required"/>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
	Authors' Addresses		Authors' Addresses
	Brian Rosen		Brian Rosen
	NeuStar		NeuStar
	470 Conrad Dr.		470 Conrad Dr.
	Mars, PA 16046		Mars, PA 16046
	US		US
	Phone: +1 724 382 1051		Phone: +1 724 382 1051
	Email: br@brianrosen.net		Email: br@brianrosen.net
	Hannes Tschofenig		Hannes Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	Linnoitustie 6		Linnoitustie 6
	Espoo 02600		Espoo, 02600
	Finland		Finland
	Phone: +358 (50) 4871445		Phone: +358 (50) 4871445
	Email: Hannes.Tschofenig@gmx.net		Email: Hannes.Tschofenig@gmx.net
	URI: http://www.tschofenig.priv.at		URI: http://www.tschofenig.priv.at
	Roger Marshall		Roger Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	2401 Elliott Avenue		2401 Elliott Avenue
	Seattle, WA 98121		Seattle, WA 98121
	US		US
	Phone: +1 206 792 2424		Phone: +1 206 792 2424
	Email: rmarshall@telecomsys.com		Email: rmarshall@telecomsys.com
	URI: http://www.telecomsys.com		URI: http://www.telecomsys.com
	Randall Gellens		Randall Gellens
	Qualcomm Technologies, Inc.		Qualcomm Technologies, Inc.
	5775 Morehouse Drive		5775 Morehouse Drive
	San Diego, CA 92121		San Diego, CA 92121
	US		US
	Email: rg+ietf@qti.qualcomm.com		Email: rg+ietf@qti.qualcomm.com
	James Winterbottom		James Winterbottom
	AU		AU
	Email: a.james.winterbottom@gmail.com		Email: a.james.winterbottom@gmail.com
End of changes. 318 change blocks.
	531 lines changed or deleted		477 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/