< draft-ietf-ecrit-additional-data-04.txt		draft-ietf-ecrit-additional-data-05.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft NeuStar		Internet-Draft NeuStar
	Intended status: Standards Track H. Tschofenig		Intended status: Standards Track H. Tschofenig
	Expires: January 17, 2013 Nokia Siemens Networks		Expires: April 25, 2013 Nokia Siemens Networks
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	July 16, 2012		October 22, 2012
	Additional Data related to an Emergency Call		Additional Data related to an Emergency Call
	draft-ietf-ecrit-additional-data-04.txt		draft-ietf-ecrit-additional-data-05.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 service provider in		(PSAP), the device that sends it, as well as any service provider in
	the path of the call, or access network may have information about		the path of the call, or access network through which the call
	the call which the PSAP may be able to use. This document describes		originated may have information about the call which the PSAP may be
	an XML data structure that contains this kind of information in a		able to use. This document describes an XML data structure to
	standardized form. A Uniform Resource Identifier (URI) that points		contains such data and a Uniform Resource Identifier (URI) for
	to the structure can be included in the SIP signaling with the call,		conveying the data to the PSAP. The URI may point to either an
	or the data may be included in the body of a SIP message.		external resource, or the body of the SIP message.
	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 17, 2013.		This Internet-Draft will expire on April 25, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
	3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 8		3. Call-Info Specification . . . . . . . . . . . . . . . . . . . 7
	4. Data Provider Information . . . . . . . . . . . . . . . . . . 10		4. Data Provider Information . . . . . . . . . . . . . . . . . . 9
	4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 10		4.1. Data Provider String . . . . . . . . . . . . . . . . . . . 9
	4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 10		4.2. Data Provider ID . . . . . . . . . . . . . . . . . . . . . 9
	4.3. Type of Data Provider ID . . . . . . . . . . . . . . . . . 11		4.3. Data Provider ID Series . . . . . . . . . . . . . . . . . 10
	4.4. Data Provider Contact URI . . . . . . . . . . . . . . . . 12		4.4. Type of Data Provider . . . . . . . . . . . . . . . . . . 10
	4.5. Data Provider Languages(s) Supported . . . . . . . . . . . 12		4.5. Data Provider Contact URI . . . . . . . . . . . . . . . . 11
	4.6. vCARD of Data Provider . . . . . . . . . . . . . . . . . . 13		4.6. Data Provider Languages(s) Supported . . . . . . . . . . . 12
	4.7. Subcontractor Principal . . . . . . . . . . . . . . . . . 13		4.7. xCard of Data Provider . . . . . . . . . . . . . . . . . . 12
	4.8. Subcontractor Priority . . . . . . . . . . . . . . . . . . 14		4.8. Subcontractor Principal . . . . . . . . . . . . . . . . . 13
	4.9. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 14		4.9. Subcontractor Priority . . . . . . . . . . . . . . . . . . 14
			4.10. addDataProviderInfo XML Schema . . . . . . . . . . . . . . 15
	5. Service Information . . . . . . . . . . . . . . . . . . . . . 16		5. Service Information . . . . . . . . . . . . . . . . . . . . . 16
	5.1. Service Environment . . . . . . . . . . . . . . . . . . . 16		5.1. Service Environment . . . . . . . . . . . . . . . . . . . 16
	5.2. Service Delivered by Provider to End User . . . . . . . . 16		5.2. Service Delivered by Provider to End User . . . . . . . . 16
	5.3. Service Mobility Environment . . . . . . . . . . . . . . . 18		5.3. Service Mobility Environment . . . . . . . . . . . . . . . 18
	5.4. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 19		5.4. addCallSvcInfo XML Schema . . . . . . . . . . . . . . . . 19
	6. Device Information . . . . . . . . . . . . . . . . . . . . . . 20		6. Device Information . . . . . . . . . . . . . . . . . . . . . . 20
	6.1. Device Classification . . . . . . . . . . . . . . . . . . 20		6.1. Device Classification . . . . . . . . . . . . . . . . . . 20
	6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 22		6.2. Device Manufacturer . . . . . . . . . . . . . . . . . . . 22
	6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 22		6.3. Device Model Number . . . . . . . . . . . . . . . . . . . 22
	6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 23		6.4. Unique Device Identifier . . . . . . . . . . . . . . . . . 23
	6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 23		6.5. Type of Device Identifier . . . . . . . . . . . . . . . . 23
	6.6. Device/Service Specific Additional Data Structure . . . . 24		6.6. Device/Service Specific Additional Data Structure . . . . 24
	6.7. Device/Service Specific Additional Data Structure Type . . 25		6.7. Device/Service Specific Additional Data Structure Type . . 25
	6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 25		6.8. addDataDevInfo XML Schema . . . . . . . . . . . . . . . . 26
	7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 27		7. Owner/Subscriber Information . . . . . . . . . . . . . . . . . 27
	7.1. vCARD for Subscriber's Data . . . . . . . . . . . . . . . 27		7.1. xCard for Subscriber's Data . . . . . . . . . . . . . . . 27
	7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 27		7.2. addCallSub XML Schema . . . . . . . . . . . . . . . . . . 28
	8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 29		8. Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
	9. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 30		8.1. Comment . . . . . . . . . . . . . . . . . . . . . . . . . 29
	10. Security Considerations . . . . . . . . . . . . . . . . . . . 31		8.2. Comment XML Schema . . . . . . . . . . . . . . . . . . . . 30
	11. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 32		9. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33		10. Main Telephone Number . . . . . . . . . . . . . . . . . . . . 32
	12.1. Registry creation . . . . . . . . . . . . . . . . . . . . 33		11. Security Considerations . . . . . . . . . . . . . . . . . . . 33
	12.1.1. Additional Call Data Blocks Registry . . . . . . . . 33		12. Privacy Considerations . . . . . . . . . . . . . . . . . . . . 34
	12.1.2. Additional Call Data Service Delivered Registry . . . 33		13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35
	12.1.3. Additional Call Data Device Classification		13.1. Registry creation . . . . . . . . . . . . . . . . . . . . 35
	Registry . . . . . . . . . . . . . . . . . . . . . . 34		13.1.1. Additional Call Data Blocks Registry . . . . . . . . 35
	12.1.4. Additional Call Data Device ID Type Registry . . . . 35		13.1.2. Service Provider Type . . . . . . . . . . . . . . . . 35
	12.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 36		13.1.3. Additional Call Data Blocks Registry . . . . . . . . 36
	12.3. URN Sub-Namespace Registration for provided-by		13.1.4. Additional Call Data Service Delivered Registry . . . 37
	Registry Entry . . . . . . . . . . . . . . . . . . . . . . 36		13.1.5. Additional Call Data Device Classification
	12.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 36		Registry . . . . . . . . . . . . . . . . . . . . . . 38
	12.4.1. MIME Content-type Registration for		13.1.6. Additional Call Data Device ID Type Registry . . . . 39
	'application/addDataProviderInfo+xml' . . . . . . . . 36		13.2. 'emergencyCallData' Purpose Parameter Value . . . . . . . 39
	12.4.2. MIME Content-type Registration for		13.3. URN Sub-Namespace Registration for provided-by
	'application/addCallSvcInfo+xml' . . . . . . . . . . 38		Registry Entry . . . . . . . . . . . . . . . . . . . . . . 39
	12.4.3. MIME Content-type Registration for		13.4. MIME Registrations . . . . . . . . . . . . . . . . . . . . 40
	'application/addDataDevInfo+xml' . . . . . . . . . . 39		13.4.1. MIME Content-type Registration for
	12.4.4. MIME Content-type Registration for		'application/addDataProviderInfo+xml' . . . . . . . . 40
	'application/addCallSub+xml' . . . . . . . . . . . . 40		13.4.2. MIME Content-type Registration for
	12.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 41		'application/addCallSvcInfo+xml' . . . . . . . . . . 41
	12.5.1. Registration for		13.4.3. MIME Content-type Registration for
	urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 41		'application/addDataDevInfo+xml' . . . . . . . . . . 42
	12.5.2. Registration for		13.4.4. MIME Content-type Registration for
	urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 42		'application/addCallSub+xml' . . . . . . . . . . . . 43
	12.5.3. Registration for		13.4.5. MIME Content-type Registration for
	urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 43		'application/addCallComment+xml' . . . . . . . . . . 45
	12.5.4. Registration for urn:ietf:params:xml:ns:addCallSub . 44		13.5. URN Sub-Namespace Registration . . . . . . . . . . . . . . 46
	12.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 45		13.5.1. Registration for
	12.7. VCard Parameter Value Registration . . . . . . . . . . . . 46		urn:ietf:params:xml:ns:addDataProviderInfo . . . . . 46
	13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47		13.5.2. Registration for
	14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48		urn:ietf:params:xml:ns:addCallSvcInfo . . . . . . . . 47
	14.1. Normative References . . . . . . . . . . . . . . . . . . . 48		13.5.3. Registration for
	14.2. Informational References . . . . . . . . . . . . . . . . . 48		urn:ietf:params:xml:ns:addDataDevInfo . . . . . . . . 47
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 50		13.5.4. Registration for urn:ietf:params:xml:ns:addCallSub . 48
			13.5.5. Registration for
			urn:ietf:params:xml:ns:addCallComment . . . . . . . . 49
			13.6. Schema Registrations . . . . . . . . . . . . . . . . . . . 50
			13.7. VCard Parameter Value Registration . . . . . . . . . . . . 51
			14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 52
			15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 53
			15.1. Normative References . . . . . . . . . . . . . . . . . . . 53
			15.2. Informational References . . . . . . . . . . . . . . . . . 53
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 55
	1. Introduction		1. Introduction
	As communications devices increasingly utilize the Internet to		This document extends the basic signaling of an emergency call as
	interconnect and communicate, users will expect to use such devices		described in [RFC6443] and [I-D.ietf-ecrit-phonebcp] in order to
	to request help. The Internet Protocol suite provides many		carry additional data which may be useful to an entity handling the
	advantages but also requires re-thinking of the traditional emergency		call. This data is "additional" to the basic signaling used in
	calling architecture. The IETF emergency services architecture, as		processing the call. Four general categories of such data are
	described in [RFC6443] and [I-D.ietf-ecrit-phonebcp], offers a much		defined, for the caller, the location, the call, and the PSAP. An
	richer communication exchange and thereby better situational		XML data structure is defined for such data, and a means of conveying
	awareness for call takers. The richness comes in various forms,		the data by including a Uniform Resource Identifier (URI) in the SIP
	including the multi-media communication capabilities (via voice,		signaling which resolves to the data. The data itself may reside on
	video, instant messaging, and real-time text), but also via more		an external resource, or may be contained within the BODY of the SIP
	extensive flow of information. Sharing information between various		message.
	actors will enable more intelligent decision making and therefore
	better response in case of an emergency. A pre-requisite is to offer
	the technical capabilities to let call takers to gain access to this
	information stored elsewhere (granted that they are authorized to
	access it).
	In general, there are four types of data exchanged:		In general, there are three types of data exchanged:
	Data Associated with a Call: While information is carried in the		Data Associated with a Call: While information is carried in the
	call setup procedure itself (as part of the SIP headers as well as		call setup procedure itself (as part of the SIP headers as well as
	in the body of the SIP message, there is additional data known by		in the body of the SIP message), there is additional data known by
	the device making the call, or a service provider in the path of		the device making the call, or a service provider in the path of
	the call including contact data, subscriber data, service data and		the call including contact data, subscriber data, service data and
	device data.		device data.
	Data Associated with a Location: Location information is available		Data Associated with a Location: There may be data that is specific
	via the PIDF-LO element, which includes civic and geospatial		to the location not available in the location data structure
	location, information about the entity that provided the data,		(PIDF-LO [RFC4119]) itself, such as floor plan, tenant and
	information about how the location was obtained (as expressed by		building owner contact data, HVAC status, etc.
	the <method> element, see Section 2.2.3 of [RFC4119], and the
	values registered in
	http://www.iana.org/assignments/method-tokens/method-tokens.xml),
	and which entity or organization supplied location information
	(beyond the domain information that can be inferred from a signing
	certificate) available via the <provided-by> element. However,
	there may be data that is specific to the location not available
	in the PIDF, such as floor plan, tenant and building owner contact
	data, HVAC status, etc.
	Data Associated with a Caller: This is personal data about a caller,		Data Associated with a Caller: This is personal data about a caller,
	including medical information and emergency contact data.		such as medical information and emergency contact data.
	Data associated with a PSAP: When a PSAP handles a call it develops
	information about the call, which must be passed to subsequent
	PSAPs, dispatchers and/or responders.
	When an emergency call is sent to a PSAP, while there is a rich set		When an emergency call is sent to a PSAP, while there is a rich set
	of data in the SIP message used for the call setup, the device, as		of data in the SIP message used for the call setup, the device, as
	well as any other service provider in the path may have even more		well as any service provider in the path may have even more
	information useful for a PSAP. This information may include the		information that may be useful for a PSAP. This information may
	identity and contact information of the service provider, subscriber		include the identity and contact information of the service provider,
	identity and contact information, the type of service the provider		subscriber identity and contact information, the type of service the
	offers, what kind of device is being used, etc. Some data is device		provider offers, what kind of device is being used, etc. Some data
	or service dependent data. For example, a car telematics system or		is device or service dependent data. For example, a car telematics
	service may have crash information. A medical monitoring device may		system or service may have crash information. A medical monitoring
	have sensor data. While the details of the information may vary by		device may have sensor data. While the details of the information
	device or service, there needs to be a common way to send such data		may vary by device or service, there needs to be a common way to send
	to a PSAP.		such data to a PSAP.
	This document focuses only on the data that can be obtained about a		This document focuses only four types of additional data associated
	call and a mechanism for transporting it in an existing SIP header		with an emergent call and a mechanism for transporting it in an
	field, the Call-Info header, which is specified in Section 20.9 of		existing SIP header field, the Call-Info header, which is specified
	[RFC3261]. For this purpose a new token, namely 'emergencyCallData'		in Section 20.9 of [RFC3261]. For this purpose a new token, namely
	is defined to be carried in the "purpose" parameter. If the		'emergencyCallData' is defined to be carried in the "purpose"
	"purpose" parameter is set to 'emergencyCallData' then the Call-Info		parameter. If the "purpose" parameter is set to 'emergencyCallData'
	header contains a HTTPS URL that points to a service and data		then the Call-Info header contains a HTTPS URL that points to a
	structure with information about the call or is a CID that allows the		service and data structure with information about the call or is a
	data structure itself to be placed in the body of the message.		CID that allows the data structure itself to be placed in the body of
	Section 8 shows a SIP INVITE example containing such a Call-Info		the message. Section 9 shows a SIP INVITE example containing such a
	header using the purpose parameter.		Call-Info header using the purpose parameter.
	Besides a service provider in the path of a call, the access network		Besides a service provider in the path of a call, the access network
	(which in the IETF emergency call architecture provides location in		(which in the IETF emergency call architecture provides location in
	the form of a PIDF-LO [RFC4119]) also has similar information that		the form of a PIDF-LO [RFC4119]) also has similar information that
	would be valuable to the PSAP. This information is not specific to		may be valuable to the PSAP. This information is not specific to the
	the location itsef, but rather would provide descriptive information		location itsef, but rather would provide descriptive information
	having to do with the immediate circumstances about the provision of		having to do with the immediate circumstances about the provision of
	the location (who the access network is, how to contact that entity,		the location (who the access network is, how to contact that entity,
	what kind of service the access network provides, possibly subscriber		what kind of service the access network provides, possibly subscriber
	data, etc.). This data is similar in nearly every respect with the		data, etc.). This data is similar in nearly every respect with the
	data known by services providers in the path of the call. For this		data known by services providers in the path of the call. For this
	reason, this document describes a "provided-by" namespace per		reason, this document describes a "provided-by" namespace per
	[RFC4119] for passing information known to the access network.		[RFC4119] for passing information known to the access network.
	The data is defined as a series of "blocks" that represent a class of		The data is defined as a series of "blocks" that represent a class of
	information. Each of the blocks is a MIME type, and an extensible		information. Each of the blocks is a MIME type, and an extensible
	skipping to change at page 8, line 5 ¶		skipping to change at page 6, line 11 ¶
	device or service dependent data. Thus the common Additional Data		device or service dependent data. Thus the common Additional Data
	about a Call defined by this document contains a 'hook', in the form		about a Call defined by this document contains a 'hook', in the form
	of a URI, for a device or service dependent data structure.		of a URI, for a device or service dependent data structure.
	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].
			In the data block definitions, the "Use:" values are specified as one
			of:
			Mandatory which means they MUST be present in the data structure.
			Conditional which means they MUST be present unless the specified
			condition is met, in which case the they MAY be present.
			Optional which means they MAY be present.
	3. Call-Info Specification		3. Call-Info Specification
	The Additional Data about a Call is information specific to a call		The Additional Data about a Call is information specific to a call
	known by the device that sends it or a service provider in the path		known by the device that sends it or a service provider in the path
	of a call or in the access network the call originates in. The		of a call or in the access network the call originates in. The
	Additional Data about a Call is a set of information blocks. Each		Additional Data about a Call is a set of information blocks. Each
	block is a MIME type, and any set of blocks may be included in the		block is a MIME type, and any set of blocks may be included in the
	set.		set.
	Two mechanisms are provided to transport the data set, namely		Two mechanisms are provided to transport the data set, namely
	1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE		1. A URI to the data set MAY be inserted in a SIP INVITE or MESSAGE
	transaction with a Call-Info header containing a purpose of		transaction with a Call-Info header containing a purpose of
	"emergencyCallData". If the data is provided by reference, it		"emergencyCallData". The Call-info header with
	may be retrieved with an HTTPS Get from the URI. The URI MUST		purpose='emergencyCallData' MUST only be sent on an emergency
	specify an HTTPS scheme, and TLS protection for the data MUST be		call, which can be ascertained by the presence of an emergency
	negotiated.		service urn in a Route header of a SIP message. If the data is
			provided by reference, it may be retrieved with an HTTPS Get from
			the URI. The URI MUST specify an HTTPS scheme, and TLS
			protection for the data MUST be negotiated.
	2. The data may be supplied by value in a SIP INVITE or MESSAGE		2. The data may be supplied by value in a SIP INVITE or MESSAGE
	message. In this case, Content Indirection (CID) [RFC2392] is		message. In this case, Content Indirection (CID) [RFC2392] is
	used, with the CID URL pointing to the body of the message.		used, with the CID URL pointing to the body of the message.
	More than one Call-Info header with an emergencyCallData purpose can		More than one Call-Info header with an emergencyCallData purpose can
	be expected, but at least one MUST be provided. The device MUST		be expected, but at least one MUST be provided. The device MUST
	provide one if no service provider is in the path of the call. The		provide one if no service provider is in the path of the call. The
	device MAY insert one if it uses a service provider, and any		device MAY insert one if it uses a service provider. Any service
	intermediary service provider SHOULD insert its own. When there are		provider in the path of the call MUST insert its own. For example, a
	multiple intermediaries, each intermediary SHOULD each insert one.		device, a telematics service provider in the call path, as well as
	For example, a device may provide one, a telematics service provider		the mobile carrier handling the call will each provide one. There
	may provide one and the mobile carrier handling the call may provide		may be circumstances where there is a service provider who is unaware
	one. There may be circumstances where there is a service provider		that the call is an emergency call and cannot reasonably be expected
	who is unaware that the call is an emergency call and cannot		to determine that it is an emergency call. In that case, that
	reasonably be expected to determine that it is an emergency call. In		service provider is not expected to provide emergencyCallData.
	that case, that service provider is not expected to provide
	emergencyCallData.
	Note: The access network MAY supply additional data as well. For		Note: The access network MAY supply additional data as well. For
	this purpose, this document defines a namespace and adds the		this purpose, this document defines a namespace and adds the
	namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].		namespace to the "provided-by" registry defined by PIDF-LO [RFC4119].
	In regions where callers can elect to suppress certain personally		In regions where callers can elect to suppress certain personally
	identifying information, the network or PSAP functionality can		identifying information, the network or PSAP functionality can
	inspect privacy flags within the SIP headers to determine what		inspect privacy flags within the SIP headers to determine what
	information may be passed, stored, or displayed to comply with local		information may be passed, stored, or displayed to comply with local
	policy or law.		policy or law.
	Additional data about a call is defined as a series of MIME objects,		Additional data about a call is defined as a series of MIME objects,
	each with an XML data structure contained inside. MIME-multipart is		each with an XML data structure contained inside. MIME-multipart is
	used to enclose the XML documents and the sections below define them.		used to enclose the XML documents and the sections below define them.
	When additional data is passed by value, the CID URL points to one of		When additional data is passed by value, the CID URL points one
	the blocks, and a link is provided in each of the other blocks to		block. Multiple URIs must be used within a Call-Info header to point
	link to the next block. When additional data is provided by		to each of the blocks. When additional data is provided by
	reference, the data is retrieved with an HTTP Get operation, which		reference, the data is retrieved with an HTTP Get operation, which
	returns a multi-part MIME header and a set of MIME blocks threaded		returns a multi-part MIME header and a set of MIME blocks defined by
	with the links. A registry of allowed types is created by this		this document. A registry of allowed types is created by this
	document. Every block MUST be one of the types in the registry.		document. Every block MUST be one of the types in the registry.
	4. Data Provider Information		4. Data Provider Information
	This block is intended to be provided by any service provider in the		This block is intended to be provided by any service provider in the
	path of the call or the access network provider. It includes		path of the call or the access network provider. It includes
	identification and contact information. This block SHOULD be		identification and contact information. This block SHOULD be
	provided for every service provider in the path of the call, and the		provided for every service provider in the path of the call, and the
	access network provider. Devices also use this block to provide		access network provider. Devices MAY use this block to provide
	identifying information. The MIME type is "addDataProviderInfo+xml".		identifying information. The MIME type is "addDataProviderInfo+xml".
	4.1. Data Provider String		4.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 about the identity of the		Reason for Need: Inform the call taker of the identity of the entity
	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.
	4.2. Data Provider ID		4.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 would not typically use		would be a "NENA Company ID". Devices SHOULD NOT use this
	this element.		element.
	Reason for Need: Inform the call taker about the identity of the		Reason for Need: Inform the call taker of the identity of the entity
	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 lead to a wealth of information.		the Data Provider ID can be useful.
	4.3. Type of Data Provider ID		4.3. Data Provider ID Series
	Data Element: Type of Data Provider ID		Data Element: Data Provider ID Series
			Use: Conditional. If Data Provider ID is provided, Data Provider ID
			Series is required.
			XML Element: <ProviderIDSeries>
			Description: Identifies the issuer of the the ProviderId. A
			registry will reflect the following valid entries:
			* NENA
			* EENA
			Reason for Need: Identifies how to interpret the Data Provider ID.
			How Used by Call Taker: Determines which provider ID registry to
			consult for more information
			4.4. Type of Data Provider
			Data Element: Type of Data Provider ID
	Use: Conditional. If Data Provider ID is provided, Type of Data		Use: Conditional. If Data Provider ID is provided, Type of Data
	Provider ID is required.		Provider ID is required.
	XML Element: <TypeOfProviderID>		XML Element: <TypeOfProviderID>
	Description: Identifies the type of data provider id being supplied		Description: Identifies the type of data provider id being supplied
	in the ProviderId data element. A registry will reflect the		in the ProviderId data element. A registry will reflect the
	following valid entries:		following valid entries:
	* Access Provider		* Access Infrastructure Provider
	* Origination Network Provider		* Service Provider
	* ServiceProviderSubcontractor		* Service Provider Subcontractor
			* Telematics Provider
			* Relay Provider
	* Other		* Other
	Reason for Need: Identifies how to interpret the Data Provider ID.		Reason for Need: Identifies what kind of data provider this is.
	How Used by Call Taker: Determines which provider ID registry to		How Used by Call Taker: To decide who to contact when further
	consult for more information		information is needed
	4.4. Data Provider Contact URI		4.5. Data Provider Contact URI
	Data Element: Data Provider Contact URI		Data Element: Data Provider Contact URI
	Use: Required		Use: Required
	XML Element: <ContactURI>		XML Element: <ContactURI>
	Description: For a service provider the contact SHOULD be a contact		Description: For a service provider the contact SHOULD be a contact
	URI. This must be a SIP URI. If a telephone number is the		URI. This MUST be a SIP URI. If a telephone number is the
	contact address it should be provided in the form of		contact address it should be provided in the form of
	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.
	4.5. Data Provider Languages(s) Supported		4.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: Provided by's alpha 2-character code as defined in ISO		Description: The language used by the entity at the Data Provider
	639-1:2002		Contact URI as an alpha 2-character code as defined in ISO 639-
	(http://www.iso.org/iso/catalogue_detail?csnumber=22109) Codes for		1:2002 (http://www.iso.org/iso/catalogue_detail?csnumber=22109)
	the representation of names of languages -- Part 1: Alpha-2 code		Codes for the representation of names of languages -- Part 1:
	Multiple instances of this element may occur. Order is		Alpha-2 code Multiple instances of this element may occur. Order
	significant; preferred language should appear first. This data is		is significant; preferred language should appear first. This data
	required if a Data Provider Contact URI is provided. The content		is required if a Data Provider Contact URI is provided. The
	must reflect the languages supported at the contact URI.		content must reflect the languages supported at the contact URI.
	Reason for Need: Information needed to determine if emergency		Reason for Need: Information needed to determine if emergency
	service authority can communicate with the service provider or if		service authority can communicate with the service provider or if
	an interpreter will be needed.		an interpreter will be needed.
	How Used by Call Taker: If call taker cannot speak language(s)		How Used by Call Taker: If call taker cannot speak language(s)
	supported by the service provider, a translation service will need		supported by the service provider, a translation service will need
	to be added to the conversation.		to be added to the conversation.
	4.6. vCARD of Data Provider		4.7. xCard of Data Provider
	Data Element: vCARD 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 vCard this specification uses		on each TEL. For encoding of the xCard this specification uses
	the XML-based encoding specified in [RFC6351].		the XML-based encoding specified in [RFC6351].
	and is hereinafter referred to as "xCard"		and is hereinafter referred to as "xCard"
	Reason for Need: Information needed to determine additional contact		Reason for Need: Information needed to determine additional contact
	information.		information.
	How Used by Call Taker: Assists call taker by providing additional		How Used by Call Taker: Assists call taker by providing additional
	contact information that may not be included in the SIP invite or		contact information that may not be included in the SIP invite or
	the PIDF-LO.		the PIDF-LO.
	4.7. Subcontractor Principal		4.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 an access
	provider or origination network, this element contains the		Description: If the data provider is a subcontractor to another
	DataProviderString of the access provider or origination network		provider such as an access infrastructure provider or telematics
	to indicate which provider the subcontractor is working for. This		provider, this element contains the DataProviderString of the
	data is required if the Data Provider type is subcontractor.		service provider to indicate which provider the subcontractor is
			working for. This data is required if the Data Provider type is
			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.
	4.8. Subcontractor Priority		4.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.
	4.9. addDataProviderInfo XML Schema		4.10. addDataProviderInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:addDataProviderInfo"		targetNamespace="urn:ietf:params:xml:ns:addDataProviderInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:ad="urn:ietf:params:xml:ns:addDataProviderInfo"		xmlns:ad="urn:ietf:params:xml:ns:addDataProviderInfo"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	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:simpleType name="iso3166a2">		<xs:simpleType name="iso3166a2">
	<xs:restriction base="xs:token">		<xs:restriction base="xs:token">
	<xs:pattern value="[A-Z]{2}"/>		<xs:pattern value="[A-Z]{2}"/>
	</xs:restriction>		</xs:restriction>
	</xs:simpleType>		</xs:simpleType>
	<xs:element name="addDataProviderInfo">		<xs:element name="addDataProviderInfo">
	<xs:complexType>		<xs:complexType>
	<xs:sequence>		<xs:sequence>
	<xs:element name="DataProviderString"		<xs:element name="DataProviderString"
	type="xs:string" minOccurs="1" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="ProviderID"		<xs:element name="ProviderID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="TypeOfProvider"		<xs:element name="ProviderIdSeries"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="ContactURI" type="xs:anyURI"		<xs:element name="TypeOfProvider"
			type="xs:string" minOccurs="0" maxOccurs="1"/>
			<xs:element name="ContactURI" type="xs:anyURI"
	minOccurs="1" maxOccurs="1"/>		minOccurs="1" maxOccurs="1"/>
	<xs:element name="Language" type="ad:iso3166a2"		<xs:element name="Language" type="ad:iso3166a2"
	minOccurs="0" maxOccurs="unbounded" />		minOccurs="0" maxOccurs="unbounded" />
	<xs:element name="DataProviderContact"		<xs:element name="DataProviderContact"
	type="vc:vcards" minOccurs="0" maxOccurs="1">		type="xc:vcard" minOccurs="0" maxOccurs="1">
	<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1">
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
	Figure 1: addDataProviderInfo XML Schema		Figure 1: addDataProviderInfo XML Schema
	5. Service Information		5. Service Information
	This block describes the service that the service provider provides		This block describes the service that the service provider provides
	skipping to change at page 17, line 48 ¶		skipping to change at page 17, line 48 ¶
	Mobile, Unknown		Mobile, Unknown
	* Relay Service: a type of service where there is a human 3rd		* Relay Service: a type of service where there is a human 3rd
	party agent who provides some kind of additional assistance to		party agent who provides some kind of additional assistance to
	the caller. Includes sign language relay and telematics		the caller. Includes sign language relay and telematics
	services which provide a service assistant on the call.		services which provide a service assistant on the call.
	* Remote (off premise extension)		* Remote (off premise extension)
	There can be more than one value returned. For example, a VoIP		There can be more than one value returned. For example, a VoIP
	prison telephone service is a reasonable combination.		inmate telephone service is a reasonable combination.
	Reason for Need: Knowing the type of service may assist the PSAP		Reason for Need: Knowing the type of service may assist the PSAP
	with the handling of the call.		with the handling of the call.
	How Used by Call Taker: Call takers often use this information to		How Used by Call Taker: Call takers often use this information to
	determine what kinds of questions to ask callers, and how much to		determine what kinds of questions to ask callers, and how much to
	rely on supportive information. An emergency call from a prison		rely on supportive information. An emergency call from a prison
	is treated differently that a call from a sensor device. As the		is treated differently that a call from a sensor device. As the
	information is not always available, and the registry is not all		information is not always available, and the registry is not all
	encompassing, this is at best advisory information, but since it		encompassing, this is at best advisory information, but since it
	skipping to change at page 19, line 7 ¶		skipping to change at page 19, line 7 ¶
	but may move between calls		but may move between calls
	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.
	5.4. addCallSvcInfo XML Schema		5.4. addCallSvcInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:addCallSvcInfo"		targetNamespace="urn:ietf:params:xml:ns:addCallSvcInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:addCallSvcInfo"		xmlns:svc="urn:ietf:params:xml:ns:addCallSvcInfo"
	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="addCallSvcInfo">		<xs:element name="addCallSvcInfo">
	<xs:complexType>		<xs:complexType>
	<xs:sequence>		<xs:sequence>
	<xs:element name="SvcEnvironment"		<xs:element name="SvcEnvironment"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcDelByProvider"		<xs:element name="SvcDelByProvider"
	type="xs:string" minOccurs="0" maxOccurs="unbounded"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SvcMobility"		<xs:element name="SvcMobility"
	type="xs:string" minOccurs="0" maxOccurs="unbounded"/>		type="xs:string" minOccurs="1" maxOccurs="1"/>
	<xs:element name="Link"		<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1">		type="xs:string" minOccurs="0" maxOccurs="1">
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
	Figure 2: addCallSvcInfo XML Schema		Figure 2: addCallSvcInfo XML Schema
	6. Device Information		6. 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 type is		device is being used, and by the device itself. The mime type is
	"addDataDevInfo+xml".		"addDataDevInfo+xml".
	6.1. Device Classification		6.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 2 Additional Data Associated with a Caller 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 about the		service provider. This information describes the the device, not
	device, not how it is being used. This data element defines the		how it is being used. This data element defines the kind of
	kind of device making the emergency call. A registry will reflect		device making the emergency call. A registry will reflect the
	the following valid entries:		following valid entries:
	* Cordless handset		* Cordless handset
	* Fixed phone		* Fixed phone
	* Mobile handset		* Mobile handset
	* ATA - analog terminal adapter		* ATA (analog terminal adapter)
	* Satellite phone		* Satellite phone
	* Stationary computing device (alarm system, data sensor)		* Stationary computing device (alarm system, data sensor)
	* Guardian devices		* Guardian devices
	* Desktop PC		* Desktop PC
	* Laptop computing device		* Laptop computing device
	skipping to change at page 21, line 38 ¶		skipping to change at page 21, line 38 ¶
	* Internet tablet		* Internet tablet
	* Gaming console		* Gaming console
	* Video phone		* Video phone
	* Other text device		* Other text device
	* Not Available		* Not Available
	Reason for Need: The device classification describes the capability		Reason for Need: The device classification implies the capability of
	of the calling device and assists in identifying the meaning of		the calling device and assists in identifying the meaning of the
	the emergency call location information that is being presented.		emergency call location information that is being presented. For
	For example, does the device require human intervention to		example, does the device require human intervention to initiate a
	initiate a call or is this call the result of programmed		call or is this call the result of programmed instructions? Does
	instructions?. Does the calling device have the ability to update		the calling device have the ability to update location or
	location or condition changes? Is this device interactive or a		condition changes? Is this device interactive or a one-way
	one-way reporting device?		reporting device?
	How Used by Call Taker: May assist with location of caller. For		How Used by Call Taker: May assist with location of caller. For
	example, a cordless handset may be outside or next door. May		example, a cordless handset may be outside or next door. May
	provide calltaker some context about the caller, the capabilities		provide calltaker some context about the caller, the capabilities
	of the device used for the call or the environment the device is		of the device used for the call or the environment the device is
	being used in.		being used in.
	6.2. Device Manufacturer		6.2. Device Manufacturer
	Data Element: Device Manufacturer		Data Element: Device Manufacturer
	skipping to change at page 23, line 16 ¶		skipping to change at page 23, line 16 ¶
	management.		management.
	6.4. Unique Device Identifier		6.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 identify the specific device making the		Description: String that identifies the specific device making the
	call or creating an event.		call or creating an event.
	Reason for Need: Uniquely identifies the device as opposed to any		Reason for Need: Uniquely identifies the device as opposed to any
	signaling identifiers encountered in the call signaling stream.		signaling identifiers encountered in the call signaling stream.
	How Used by Call Taker: Probably not used by calltaker they would		How Used by Call Taker: Probably not used by calltaker they would
	need to refer to management for investigation.		need to refer to management for investigation.
	6.5. Type of Device Identifier		6.5. Type of Device Identifier
	skipping to change at page 23, line 39 ¶		skipping to change at page 23, line 39 ¶
	Use: Conditional: must be provided if DeviceID is provided		Use: Conditional: must be provided if DeviceID is provided
	XML Element: <TypeOfDeviceID>		XML Element: <TypeOfDeviceID>
	Description: Identifies the type of device identifier being		Description: Identifies the type of device identifier being
	generated in the unique device identifier data element. A		generated in the unique device identifier data element. A
	registry will reflect the following valid entries:		registry will reflect the following valid entries:
	* MEID (CDMA)		* MEID (CDMA)
	* ESN (Electronic Serial Number - superseded by MEID)		* ESN (Electronic Serial Number -- superseded by MEID)
	* MAC (Media Access Control) Address - any IEEE device with an		* MAC (Media Access Control) Address -- IEEE-delegated address of
	Ethernet, Wi-Fi connection		any of the interfaces of the device with a MAC address (e.g.,
			Ethernet, WiFi)
	* WiMAX has a device certificate		* WiMAX device certificate subject unique identifier
	* IMEI (International Mobile Equipment Identifier - GSM)		* IMEI (International Mobile Equipment Identifier - GSM)
	* Unique Device Identifier (Unique identifier for medical		* Unique Device Identifier (UDI) assigned by US FD for medical
	devices)		devices
	* RFID (Radio Frequency Identification)		* RFID (Radio Frequency Identification)
	* Sensors (types to be identified in a future document version)		* Sensors (types to be identified in a future document version)
	* Manufacturer Serial Number		* Manufacturer Serial Number
	* Other		* Other
	Reason for Need: Identifies how to interpret the Unique Device		Reason for Need: Identifies how to interpret the Unique Device
	skipping to change at page 24, line 39 ¶		skipping to change at page 24, line 39 ¶
	Use: Optional		Use: Optional
	XML Element: <devicespecificSchema>		XML Element: <devicespecificSchema>
	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; i.e., telematics creates VEDS		be created by each classification; e.g., telematics creates VEDS
	data set - can be different types of data depending on device.		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.
	skipping to change at page 25, line 29 ¶		skipping to change at page 25, line 29 ¶
	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 will allow for 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
	will assist in emergency response.		may assist in emergency response.
	How Used by Call Taker: This data element will allow 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.
	6.8. addDataDevInfo XML Schema		6.8. addDataDevInfo XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo"		targetNamespace="urn:ietf:params:xml:ns:addDataDevInfo"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:svc="urn:ietf:params:xml:ns:addDataDevInfo"		xmlns:svc="urn:ietf:params:xml:ns:addDataDevInfo"
	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 26, line 32 ¶		skipping to change at page 26, line 35 ¶
	<xs:element name="DeviceModelNr"		<xs:element name="DeviceModelNr"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="UniqueDeviceID"		<xs:element name="UniqueDeviceID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="TypeOfDeviceID"		<xs:element name="TypeOfDeviceID"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xsd:element name="devicespecificType"		<xsd:element name="devicespecificType"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xsd:element name="devicespecificSchema"		<xsd:element name="devicespecificSchema"
	type="xsd:anyURI" minOccurs="0" maxOccurs="1"/>		type="xsd:anyURI" minOccurs="0" maxOccurs="1"/>
	<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1">
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
	Figure 3: addDataDevInfo XML Schema		Figure 3: addDataDevInfo XML Schema
	7. Owner/Subscriber Information		7. 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 type is "addCallSub+xml".		The mime type is "addCallSub+xml".
	7.1. vCARD for Subscriber's Data		7.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; i.e., 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
	skipping to change at page 28, line 4 ¶		skipping to change at page 28, line 6 ¶
	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.
	7.2. addCallSub XML Schema		7.2. addCallSub XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	targetNamespace="urn:ietf:params:xml:ns:addCallSub"		targetNamespace="urn:ietf:params:xml:ns:addCallSub"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:sub="urn:ietf:params:xml:ns:addCallSub"		xmlns:sub="urn:ietf:params:xml:ns:addCallSub"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"		xmlns:xml="http://www.w3.org/XML/1998/namespace"
	xmlns:vc="urn:ietf:params:xml:ns:vcard-4.0"		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0"
	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="addCallSub">		<xs:element name="addCallSub">
	<xs:complexType>		<xs:complexType>
	<xs:sequence>		<xs:sequence>
	<xs:element name="SubscriberData"		<xs:element name="SubscriberData"
	type="vc:vcards" minOccurs="0" maxOccurs="1">		type="xc:vcard" minOccurs="0" maxOccurs="1">
	<xs:element name="Link"
	type="xs:string" minOccurs="0" maxOccurs="1">
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	</xs:element>		</xs:element>
	</xs:schema>		</xs:schema>
	Figure 4: addCallSub XML Schema		Figure 4: addCallSub XML Schema
	8. Example		8. Comment
			This block Provides a mechanism for the data provider to supply
			extra, human readable information to the PSAP. It is not intended
			for a general purpose extension mechanism
			8.1. Comment
			Data Element: Comment
			Use: Optional
			XML Element: <Comment>
			Description: Human readable text providing additional information to
			the PSAP.
			Reason for Need: Explanatory information for values in the data
			structure
			How Used by Call Taker: To interpret the data provided
			8.2. Comment XML Schema
			<?xml version="1.0"?>
			<xs:schema
			targetNamespace="urn:ietf:params:xml:ns:addCallComment"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			xmlns:sub="urn:ietf:params:xml:ns:addCallComment"
			xmlns:xml="http://www.w3.org/XML/1998/namespace"
			elementFormDefault="qualified" attributeFormDefault="unqualified">
			<xs:import namespace="http://www.w3.org/XML/1998/namespace"
			schemaLocation="http://www.w3.org/2001/xml.xsd"/>
			<xs:element name="addCallComment">
			<xs:complexType>
			<xs:sequence>
			<xs:element name="Comment"
			type="xs:string" minOccurs="0" maxOccurs="1">
			</xs:sequence>
			</xs:complexType>
			</xs:element>
			</xs:schema>
			Figure 5: Comment XML Schema
			9. Example
	INVITE sips:bob@biloxi.example.com SIP/2.0		INVITE sips:bob@biloxi.example.com SIP/2.0
	Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9		Via: SIPS/2.0/TLS pc33.atlanta.example.com;branch=z9hG4bK74bf9
	Max-Forwards: 70		Max-Forwards: 70
	To: Bob <sips:bob@biloxi.example.com>		To: Bob <sips:bob@biloxi.example.com>
	From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl		From: Alice <sips:alice@atlanta.example.com>;tag=9fxced76sl
	Call-ID: 3848276298220188511@atlanta.example.com		Call-ID: 3848276298220188511@atlanta.example.com
	Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,		Call-Info: <http://wwww.example.com/alice/photo.jpg> ;purpose=icon,
	<http://www.example.com/alice/> ;purpose=info,		<http://www.example.com/alice/> ;purpose=info,
	<cid:1234567890@atlanta.example.com> ;purpose=emergencyCallData		<cid:1234567890@atlanta.example.com> ;purpose=emergencyCallData
	skipping to change at page 30, line 5 ¶		skipping to change at page 32, line 5 ¶
	Content-Type: application/addDataProviderinfo+xml		Content-Type: application/addDataProviderinfo+xml
	Content-ID: <1234567890@atlanta.example.com>		Content-ID: <1234567890@atlanta.example.com>
	...Additional Data goes here		...Additional Data goes here
	--boundary1--		--boundary1--
	Example: Attaching Additional Data via CID to a SIP INVITE		Example: Attaching Additional Data via CID to a SIP INVITE
	9. Main Telephone Number		10. Main Telephone Number
	In a vCard, used extensively in this document, there is no way to		In a xCard, used extensively in this document, 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 vCard in additional		parameter called "main". It can be used in any xCard in additional
	data.		data.
	10. Security Considerations		11. 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.		critical information securely are more daunting. The provider may
			enforce any policy it wishes to use, but PSAPs and responder agencies
	The Call-info header with purpose='emergencyCallData' MUST only be		should deploy a PKI so that providers of additional data can check
	sent on an emergency call, which can be ascertained by the presence		the certificate of the client and decide the appropriate policy to
	of an emergency service urn in a Route header of a SIP message.		enforce based on that certificate.
	<how recipient validates credentials of sender>
	<how sender validates credentials of recipient>		Ideally, the PSAP and emergency responders will be given credentials
			signed by an authority trusted by the data provider. In most
			circumstances, nationally recognized credentials would be sufficient,
			and if the emergency services arranges a PKI, data providers could be
			provisioned with the root CA public key for a given nation. Some
			nations are developing a PKI for this, and related, purposes. Since
			calls could be made from devices where the device and/or the service
			provider(w) are not local to the emergency authorities, globally
			recognized credentials are useful. This might be accomplished by
			extending the notion of the "forest guide" described in [RFC5222] to
			allow the forest guide to provide the credential of the PKI root for
			areas that it has coverage information for, but standards for such a
			mechanism are not yet available. In its absence, the data provider
			will need to obtain the root CA credentials for any areas it is
			willing to provide additional data by out of band means. With the
			credential of the root CA for a national emergency services PKI, the
			data provider server can validate the credentials of an entity
			requesting additional data by reference.
	<how sender validates credentials of anyone requesting device		The data provider also needs a credential that can be verified by the
	dependent data>		emergency services to know that it is receiving data from the right
			server. The emergency authorities could provide credentials,
			distinguishable from credentials it provides to emergency responders
			and PSAPs, which could be used to validate data providers. This
			would be extensible to global credential validation using the forest
			guide as above. In the absence of such credentials, the emergency
			authorities could maintain a list of local data providers'
			credentials provided to it out of band. At a minimum, the emergency
			authorities could obtain a credential from the DNS entry of the
			domain in the Addional Data URI to at least validate that the server
			is known to the domain providing the URI.
	11. Privacy Considerations		Data provided by devices by reference have similar credential
			validation issues to service providers, and the solutions are the
			same.
	[Editor's Note: The privacy considerations outlined in		12. Privacy Considerations
	[I-D.iab-privacy-considerations] need to be addressed here in a
	future version of this document.
	There is much private data in this information. Local regulations		There is much private data in this information. Local regulations
	may govern what data must be provided in emergency calls, but in		may govern what data must be provided in emergency calls, but in
	general, the emergency call system is often aided by the kinds of		general, the emergency call system is often aided by the kinds of
	information described in this document. There is a tradeoff between		information described in this document. There is a tradeoff between
	the privacy considerations and the utility of the data. Certainly,		the privacy considerations and the utility of the data. Certainly,
	if the data cannot be protected, due to failure of the TLS mechanisms		if the data cannot be protected, due to failure to establish (by TLS)
	described here, data not required by regulation SHOULD not be sent.		a secure connection to the data provider, data SHOULD NOT be sent
			unless specifically required by regulation.
	12. IANA Considerations		13. IANA Considerations
	12.1. Registry creation		13.1. Registry creation
	12.1.1. Additional Call Data Blocks Registry		This document creates a new registry called 'Emergency Call
			Additional Data'. The following subregistries are created in
			Emergency Call Additional Data:
	This document creates a new registry called 'Additional Call Data		13.1.1. Additional Call Data Blocks Registry
			This document creates a new subregistry called 'Provider ID Series'.
			As defined in [RFC5226], this registry operates under "Expert Review"
			rules. The expert should determine that the entity requesting a new
			value is a legitimate issuer of service provider IDs suitable for use
			in Additional Call Data.
			The content of this registry includes:
			Name: The identifier which will be used in the ProviderIDSeries
			element
			Source: The full name of the organization issuing the identifiers
			URL: A URL to the organization for further information
			The values defined are:
			+-----------+-----------+--------------+--------------+
			| Name | Source | URL |
			+-----------+--------------------------+--------------+
			| NENA | North American Emergency | www.nena.org |
			| | Number Association | |
			| EENA | European Emergency | www.eena.org |
			| | Number Association | |
			+-----------+--------------------------+--------------+
			RFC Editor Note:
			replace XXXX in the table above with this documents RFC number
			13.1.2. Service Provider Type
			This document creates a new subregistry called 'Service Provider
			Type'. As defined in [RFC5226], this registry operates under "Expert
			Review". The expert should determine that the proposed new value is
			distinct from existing values and appropriate for use in the
			TypeOfServicerProvider element
			The content of this registry includes:
			Name: Value to be used in TypeOfServiceProvider.
			Description: A short description of the type of service provider
			The values defined are:
			+------------------------------+------------------------------------+
			| Name | Description |
			+------------------------------+------------------------------------+
			|Access Infrastructure Provider| Access network service provider |
			|Service Provider | Calling or Origination telecom SP |
			|Service Provider Subcontractor| A contractor to another kind of SP |
			|Telematics Provider | A sensor based SP, especially |
			| | vehicle based |
			|Relay Provider | A interpretation SP, for example, |
			| | video relay for sign language |
			| | interpretors |
			|Other | Any other type of service provider |
			+------------------------------+------------------------------------+
			RFC Editor Note:
			replace XXXX in the table above with this documents RFC number
			13.1.3. Additional Call Data Blocks Registry
			This document creates a new subregistry called 'Additional Call Data
	Blocks'. As defined in [RFC5226], this registry operates under		Blocks'. As defined in [RFC5226], this registry operates under
	"Expert Review" and "Specification Required" rules.		"Expert Review" and "Specification Required" rules.
	The content of this registry includes:		The content of this registry includes:
	Name: Element Name of enclosing block.		Name: Element Name of enclosing block.
	Reference: The document that describes the block		Reference: The document that describes the block
	The values defined are:		The values defined are:
	+---------------------+-----------+		+---------------------+-----------+
	| Name | Reference |		| Name | Reference |
	+---------------------+-----------+		+---------------------+-----------+
	| addDataProviderInfo | RFCXXXX |		| addDataProviderInfo | RFCXXXX |
	| addCallSvcInfo | RFCXXXX |		| addCallSvcInfo | RFCXXXX |
	| addCallSvcInfo | RFCXXXX |		| addCallSvcInfo | RFCXXXX |
	| addCallSub | RFCXXXX |		| addCallSub | RFCXXXX |
			| addCallComment | RFCXXXX |
	+---------------------+-----------+		+---------------------+-----------+
	RFC Editor Note:		RFC Editor Note:
	replace XXXX in the table above with this documents RFC number		replace XXXX in the table above with this documents RFC number
	12.1.2. Additional Call Data Service Delivered Registry		13.1.4. Additional Call Data Service Delivered Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Service Delivered'. As defined in [RFC5226], this registry operates		Service Delivered'. As defined in [RFC5226], this registry operates
	under "Expert Review" rules.		under "Expert Review" rules.
	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.
	skipping to change at page 34, line 36 ¶		skipping to change at page 38, line 5 ¶
	| | that are supported by a monitoring |		| | that are supported by a monitoring |
	| | service provider or automatically |		| | service provider or automatically |
	| | open a two-way communication path |		| | open a two-way communication path |
	| POTS | Wireline: Plain Old Telephone Service |		| POTS | Wireline: Plain Old Telephone Service |
	| VOIP | VoIP Telephone Service: A type of |		| VOIP | VoIP Telephone Service: A type of |
	| | service that offers communication |		| | service that offers communication |
	| | over internet protocol, such as Fixed|		| | over internet protocol, such as Fixed|
	| | Nomadic, Mobile, ... |		| | Nomadic, Mobile, ... |
	+--------+-------+--------------------------------+		+--------+-------+--------------------------------+
	12.1.3. Additional Call Data Device Classification Registry		13.1.5. Additional Call Data Device Classification Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Device Classification'. As defined in [RFC5226], this registry		Device Classification'. As defined in [RFC5226], this registry
	operates under "Expert Review" rules.		operates under "Expert Review" rules.
	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.
	skipping to change at page 35, line 36 ¶		skipping to change at page 39, line 5 ¶
	| 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 |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	12.1.4. Additional Call Data Device ID Type Registry		13.1.6. Additional Call Data Device ID Type Registry
	This document creates a new registry called 'Additional Call Data		This document creates a new registry called 'Additional Call Data
	Device ID Type'. As defined in [RFC5226], this registry operates		Device ID Type'. As defined in [RFC5226], this registry operates
	under "Expert Review" rules.		under "Expert Review" rules.
	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 the type of device id.		Description: Short description identifying the type of device id.
	skipping to change at page 36, line 20 ¶		skipping to change at page 39, line 34 ¶
	| 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 (medical) |		| UDI | Unique Device Identifier (medical) |
	| RFID | Radio Frequency Identification |		| RFID | Radio Frequency Identification |
	| Sense | Sensors (types to be identified ) |		| Sense | Sensors (types to be identified ) |
	| SN | Manufacturer Serial Number |		| SN | Manufacturer Serial Number |
	| Other | Other |		| Other | Other |
	+--------+----------------------------------------+		+--------+----------------------------------------+
	12.2. 'emergencyCallData' Purpose Parameter Value		13.2. 'emergencyCallData' Purpose Parameter Value
	This document defines the 'emergencyCallData' value for the "purpose"		This document defines the 'emergencyCallData' value for the "purpose"
	parameter of the Call-Info header field. The Call-Info header and		parameter of the Call-Info header field. The Call-Info header and
	the corresponding registry for the 'purpose' parameter was		the corresponding registry for the 'purpose' parameter was
	established with RFC 3261 [RFC3261].		established with RFC 3261 [RFC3261].
	Header Parameter New		Header Parameter New
	Field Name Value Reference		Field Name Value Reference
	---------- --------- ----------------- ---------		---------- --------- ----------------- ---------
	Call-Info purpose emergencyCallData [This RFC]		Call-Info purpose emergencyCallData [This RFC]
	12.3. URN Sub-Namespace Registration for provided-by Registry Entry		13.3. URN Sub-Namespace Registration for provided-by Registry Entry
	This section registers the namespace specified in ??? in the		This section registers the namespace specified in ??? in the
	provided-by registry established by RFC 4119.		provided-by registry established by RFC 4119.
	12.4. MIME Registrations		13.4. MIME Registrations
	12.4.1. MIME Content-type Registration for 'application/		13.4.1. MIME Content-type Registration for 'application/
	addDataProviderInfo+xml'		addDataProviderInfo+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: addDataProviderInfo+xml		MIME subtype name: addDataProviderInfo+xml
	skipping to change at page 37, line 4 ¶		skipping to change at page 40, line 19 ¶
	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: addDataProviderInfo+xml		MIME subtype name: addDataProviderInfo+xml
	Mandatory parameters: none		Mandatory parameters: none
	Optional parameters: charset		Optional parameters: charset
	Indicates the character encoding of enclosed XML.		Indicates the character encoding of enclosed XML.
	Encoding considerations:		Encoding considerations:
	Uses XML, which can employ 8-bit characters, depending on the		Uses XML, which can employ 8-bit characters, depending on the
	character encoding used. See Section 3.2 of RFC 3023 [RFC3023].		character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
	Security considerations:		Security considerations:
	This content type is designed to carry the data provider		This content type is designed to carry the data provider
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 10 and Section 11 for		this information. Please refer to Section 11 and Section 12 for
	more information.		more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	skipping to change at page 37, line 36 ¶		skipping to change at page 41, line 4 ¶
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Personal 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>
	12.4.2. MIME Content-type Registration for 'application/		13.4.2. MIME Content-type Registration for 'application/
	addCallSvcInfo+xml'		addCallSvcInfo+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: addCallSvcInfo+xml		MIME subtype name: addCallSvcInfo+xml
	skipping to change at page 38, line 36 ¶		skipping to change at page 41, line 47 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry the service information,		This content type is designed to carry the service information,
	which is a sub-category of additional data about an emergency		which is a sub-category of additional data about an emergency
	call.		call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 10 and Section 11 for		this information. Please refer to Section 11 and Section 12 for
	more information.		more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Personal 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>
	12.4.3. MIME Content-type Registration for 'application/		13.4.3. MIME Content-type Registration for 'application/
	addDataDevInfo+xml'		addDataDevInfo+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: addDataDevInfo+xml		MIME subtype name: addDataDevInfo+xml
	skipping to change at page 39, line 45 ¶		skipping to change at page 43, line 14 ¶
	Security considerations:		Security considerations:
	This content type is designed to carry the device information		This content type is designed to carry the device information
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 10 and Section 11 for		this information. Please refer to Section 11 and Section 12 for
	more information.		more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Personal 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>
	12.4.4. MIME Content-type Registration for 'application/addCallSub+xml'		13.4.4. MIME Content-type Registration for 'application/addCallSub+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: addCallSub+xml		MIME subtype name: addCallSub+xml
	Mandatory parameters: none		Mandatory parameters: none
	Optional parameters: charset		Optional parameters: charset
	Indicates the character encoding of enclosed XML.		Indicates the character encoding of enclosed XML.
	Encoding considerations:		Encoding considerations:
	Uses XML, which can employ 8-bit characters, depending on the		Uses XML, which can employ 8-bit characters, depending on the
	character encoding used. See Section 3.2 of RFC 3023 [RFC3023].		character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
	Security considerations:		Security considerations:
	This content type is designed to carry owner/subscriber		This content type is designed to carry owner/subscriber
	information, which is a sub-category of additional data about an		information, which is a sub-category of additional data about an
	emergency call.		emergency call.
	Since this data contains personal information appropriate		Since this data contains personal information appropriate
	precautions have to be taken to limit unauthorized access,		precautions have to be taken to limit unauthorized access,
	inappropriate disclosure to third parties, and eavesdropping of		inappropriate disclosure to third parties, and eavesdropping of
	this information. Please refer to Section 10 and Section 11 for		this information. Please refer to Section 11 and Section 12 for
	more information.		more information.
	Interoperability considerations: None		Interoperability considerations: None
	Published specification: [TBD: This specification]		Published specification: [TBD: This specification]
	Applications which use this media type: Emergency Services		Applications which use this media type: Emergency Services
	Additional information:		Additional information:
	Magic Number: None		Magic Number: None
	File Extension: .xml		File Extension: .xml
	Macintosh file type code: 'TEXT'		Macintosh file type code: 'TEXT'
	Personal 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>
	12.5. URN Sub-Namespace Registration		13.4.5. MIME Content-type Registration for 'application/
			addCallComment+xml'
	12.5.1. Registration for urn:ietf:params:xml:ns:addDataProviderInfo		This specification requests the registration of a new MIME type
			according to the procedures of RFC 4288 [RFC4288] and guidelines in
			RFC 3023 [RFC3023].
			MIME media type name: application
			MIME subtype name: addCallComment+xml
			Mandatory parameters: none
			Optional parameters: charset
			Indicates the character encoding of enclosed XML.
			Encoding considerations:
			Uses XML, which can employ 8-bit characters, depending on the
			character encoding used. See Section 3.2 of RFC 3023 [RFC3023].
			Security considerations:
			This content type is designed to carry a comment, which is a sub-
			category of additional data about an emergency call.
			This data may contain personal information. Appropriate
			precautions may have to be taken to limit unauthorized access,
			inappropriate disclosure to third parties, and eavesdropping of
			this information. Please refer to Section 11 and Section 12 for
			more information.
			Interoperability considerations: None
			Published specification: [TBD: This specification]
			Applications which use this media type: Emergency Services
			Additional information:
			Magic Number: None
			File Extension: .xml
			Macintosh file type code: 'TEXT'
			Person and email address for further information: Hannes
			Tschofenig, Hannes.Tschofenig@gmx.net
			Intended usage: LIMITED USE
			Author: This specification is a work item of the IETF ECRIT
			working group, with mailing list address <ecrit@ietf.org>.
			Change controller: The IESG <ietf@ietf.org>
			13.5. URN Sub-Namespace Registration
			13.5.1. Registration for urn:ietf:params:xml:ns:addDataProviderInfo
	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:addDataProviderInfo		URI: urn:ietf:params:xml:ns:addDataProviderInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 42, line 24 ¶		skipping to change at page 47, line 5 ¶
	Data Provider Information</title>		Data Provider Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Data Provider Information</h2>		<h2>Data Provider Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	12.5.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo		13.5.2. Registration for urn:ietf:params:xml:ns:addCallSvcInfo
	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:addCallSvcInfo		URI: urn:ietf:params:xml:ns:addCallSvcInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 43, line 24 ¶		skipping to change at page 47, line 36 ¶
	Service Information</title>		Service Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Service Information</h2>		<h2>Service Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	12.5.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo		13.5.3. Registration for urn:ietf:params:xml:ns:addDataDevInfo
	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:addDataDevInfo		URI: urn:ietf:params:xml:ns:addDataDevInfo
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 44, line 24 ¶		skipping to change at page 48, line 24 ¶
	Device Information</title>		Device Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2>Device Information</h2>		<h2>Device Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	12.5.4. Registration for urn:ietf:params:xml:ns:addCallSub		13.5.4. Registration for urn:ietf:params:xml:ns:addCallSub
	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:addCallSub		URI: urn:ietf:params:xml:ns:addCallSub
	Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as		Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
	delegated by the IESG <iesg@ietf.org>.		delegated by the IESG <iesg@ietf.org>.
	XML:		XML:
	skipping to change at page 45, line 24 ¶		skipping to change at page 49, line 24 ¶
	Owner/Subscriber Information</title>		Owner/Subscriber Information</title>
	</head>		</head>
	<body>		<body>
	<h1>Namespace for Additional Data related to an Emergency Call</h1>		<h1>Namespace for Additional Data related to an Emergency Call</h1>
	<h2> Owner/Subscriber Information</h2>		<h2> Owner/Subscriber Information</h2>
	<p>See [TBD: This document].</p>		<p>See [TBD: This document].</p>
	</body>		</body>
	</html>		</html>
	END		END
	12.6. Schema Registrations		13.5.5. Registration for urn:ietf:params:xml:ns:addCallComment
	This specification registers four schemas, as per the guidelines in		This section registers a new XML namespace, as per the guidelines in
			RFC 3688 [RFC3688].
			URI: urn:ietf:params:xml:ns:addCallComment
			Registrant Contact: IETF, ECRIT working group, <ecrit@ietf.org>, as
			delegated by the IESG <iesg@ietf.org>.
			XML:
			BEGIN
			<?xml version="1.0"?>
			<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
			"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
			<html xmlns="http://www.w3.org/1999/xhtml">
			<head>
			<meta http-equiv="content-type"
			content="text/html;charset=iso-8859-1"/>
			<title>Namespace for Additional Emergency Call Data:Comment</title>
			</head>
			<body>
			<h1>Namespace for Additional Data related to an Emergency Call</h1>
			<h2> Comment</h2>
			<p>See [TBD: This document].</p>
			</body>
			</html>
			END
			13.6. Schema Registrations
			This specification registers five schemas, as per the guidelines in
	RFC 3688 [RFC3688].		RFC 3688 [RFC3688].
	URI:		URI:
	urn:ietf:params:xml:schema:additional-data:addDataProviderInfo		urn:ietf:params:xml:schema:additional-data:addDataProviderInfo
	Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as		Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
	delegated by the IESG (iesg@ietf.org).		delegated by the IESG (iesg@ietf.org).
	XML: The XML schema can be found in Figure 1.		XML: The XML schema can be found in Figure 1.
	skipping to change at page 46, line 14 ¶		skipping to change at page 50, line 41 ¶
	XML: The XML schema can be found in Figure 3.		XML: The XML schema can be found in Figure 3.
	URI: urn:ietf:params:xml:schema:additional-data:addCallSub		URI: urn:ietf:params:xml:schema:additional-data:addCallSub
	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 4.		XML: The XML schema can be found in Figure 4.
	12.7. VCard Parameter Value Registration		URI: urn:ietf:params:xml:schema:additional-data:addCallComment
			Registrant Contact: IETF, ECRIT Working Group (ecrit@ietf.org), as
			delegated by the IESG (iesg@ietf.org).
			XML: The XML schema can be found in Figure 5.
			13.7. VCard Parameter Value Registration
	This document registers a new value in the vCARD Parameter Values		This document registers a new value in the vCARD Parameter Values
	registry as defined by [RFC6350] with the following template:		registry as defined by [RFC6350] with the following template:
	Value: main		Value: main
	Purpose: The main telephone number, typically of an enterprise, as		Purpose: The main telephone number, typically of an enterprise, as
	opposed to a direct dial number of an individual employee		opposed to a direct dial number of an individual employee
	Conformance: This value can be used with the "TYPE" parameter		Conformance: This value can be used with the "TYPE" parameter
	applied on the "TEL" property.		applied on the "TEL" property.
	Example(s):		Example(s):
	TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-9000		TEL;VALUE=uri;TYPE="main,voice";PREF=1:tel:+1-418-656-9000
	13. Acknowledgments		14. Acknowledgments
	This work was originally started in NENA and has benefitted from a		This work was originally started in NENA and has benefitted from a
	large number of participants in NENA standardization efforts,		large number of participants in NENA standardization efforts,
	originally in the Long Term Definition Working Group, the Data		originally in the Long Term Definition Working Group, the Data
	Technical Committee and most recently the Additional Data working		Technical Committee and most recently the Additional Data working
	group. The authors are grateful for the initial work and extended		group. The authors are grateful for the initial work and extended
	comments provided by the many NENA participants.		comments provided by the many NENA participants.
	14. References		15. References
	14.1. Normative References		15.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource		[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
	Locators", RFC 2392, August 1998.		Locators", RFC 2392, August 1998.
	[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media		[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
	Types", RFC 3023, January 2001.		Types", RFC 3023, January 2001.
	skipping to change at page 48, line 42 ¶		skipping to change at page 53, line 42 ¶
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,		[RFC6350] Perreault, S., "vCard Format Specification", RFC 6350,
	August 2011.		August 2011.
	[RFC6351] Perreault, S., "xCard: vCard XML Representation",		[RFC6351] Perreault, S., "xCard: vCard XML Representation",
	RFC 6351, August 2011.		RFC 6351, August 2011.
	14.2. Informational References		15.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",		Considerations for Internet Protocols",
	draft-iab-privacy-considerations-03 (work in progress),		draft-iab-privacy-considerations-03 (work in progress),
	July 2012.		July 2012.
	[I-D.ietf-ecrit-phonebcp]		[I-D.ietf-ecrit-phonebcp]
	Rosen, B. and J. Polk, "Best Current Practice for		Rosen, B. and J. Polk, "Best Current Practice for
	Communications Services in support of Emergency Calling",		Communications Services in support of Emergency Calling",
	draft-ietf-ecrit-phonebcp-20 (work in progress),		draft-ietf-ecrit-phonebcp-20 (work in progress),
	September 2011.		September 2011.
			[RFC5222] Hardie, T., Newton, A., Schulzrinne, H., and H.
			Tschofenig, "LoST: A Location-to-Service Translation
			Protocol", RFC 5222, August 2008.
	[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.
	Authors' Addresses		Authors' Addresses
	Brian Rosen		Brian Rosen
	NeuStar		NeuStar
	470 Conrad Dr.		470 Conrad Dr.
	Mars, PA 16046		Mars, PA 16046
End of changes. 126 change blocks.
	304 lines changed or deleted		570 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/