< draft-ietf-ecrit-additional-data-18.txt		draft-ietf-ecrit-additional-data-19.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: August 14, 2014 Nokia Solutions and Networks		Expires: August 15, 2014 Nokia Solutions and Networks
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	R. Gellens		R. Gellens
	Qualcomm Technologies, Inc.		Qualcomm Technologies, Inc.
	J. Winterbottom		J. Winterbottom
	February 10, 2014		February 11, 2014
	Additional Data related to an Emergency Call		Additional Data related to an Emergency Call
	draft-ietf-ecrit-additional-data-18.txt		draft-ietf-ecrit-additional-data-19.txt
	Abstract		Abstract
	When an emergency call is sent to a Public Safety Answering Point		When an emergency call is sent to a Public Safety Answering Point
	(PSAP), the device that sends it, as well as any application service		(PSAP), the device that sends it, as well as any application service
	provider in the path of the call, or access network provider through		provider in the path of the call, or access network provider through
	which the call originated may have information about the call, the		which the call originated may have information about the call, the
	caller or the location which the PSAP may be able to use. This		caller or the location which the PSAP may be able to use. This
	document describes data structures and a mechanism to convey such		document describes data structures and a mechanism to convey such
	data to the PSAP. The mechanism uses a Uniform Resource Identifier		data to the PSAP. The mechanism uses a Uniform Resource Identifier
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on August 14, 2014.		This Internet-Draft will expire on August 15, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 21, line 43 ¶		skipping to change at page 21, line 43 ¶
	3.3.5. Device/Service Specific Additional Data Structure		3.3.5. Device/Service Specific Additional Data Structure
	Data Element: Device/service specific additional data structure		Data Element: Device/service specific additional data structure
	Use: Optional		Use: Optional
	XML Element: <DeviceSpecificData>		XML Element: <DeviceSpecificData>
	Description: A URI representing additional data whose schema is		Description: A URI representing additional data whose schema is
	specific to the device or service which created it. An example is		specific to the device or service which created it. (For example,
	the Vehicular Emergency Data Set (VEDS) structure for a vehicle		a medical device or medical device monitoring service may have a
	telematics device. The URI, when dereferenced, MUST yield a data		defined set of medical data.) The URI, when dereferenced, MUST
	structure defined by the Device/service specific additional data		yield a data structure defined by the Device/service specific
	type value. Different data may be created by each classification;		additional data type value. Different data may be created by each
	e.g., a telematics created VEDS data set.		classification; e.g., a medical device created 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 59, line 49 ¶		skipping to change at page 59, line 49 ¶
	Name: Element Name of enclosing block.		Name: Element Name of enclosing block.
	Reference: The document that describes the block		Reference: The document that describes the block
	The initial set of values are listed in Figure 24.		The initial set of values are listed in Figure 24.
	+--------------+------------+		+--------------+------------+
	| Token | Reference |		| Token | Reference |
	+--------------+------------+		+--------------+------------+
	| ProviderInfo | [This RFC] |		| ProviderInfo | [This RFC] |
	| ServiceInfo | [This RFC] |		| ServiceInfo | [This RFC] |
	| DeviceInfo | [This RFC] |		| DeviceInfo | [This RFC] |
	| Subscriber | [This RFC] |		| Subscriber | [This RFC] |
	| Comment | [This RFC] |		| Comment | [This RFC] |
	+--------------+------------+		+--------------+------------+
	Figure 24: Additional Data Blocks Registry.		Figure 24: Additional Data Blocks Registry.
	9.2. 'EmergencyCallData' Purpose Parameter Value		9.2. 'EmergencyCallData' Purpose Parameter Value
	This document defines the 'EmergencyCallData' value for the "purpose"		This document defines the 'EmergencyCallData' value for the "purpose"
	parameter of the Call-Info header field. The Call-Info header and		parameter of the Call-Info header field. The Call-Info header and
End of changes. 6 change blocks.
	12 lines changed or deleted		12 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/