< draft-ietf-ecrit-additional-data-26.txt		draft-ietf-ecrit-additional-data-27.txt >
	ECRIT R. Gellens		ECRIT R. Gellens
	Internet-Draft Qualcomm Technologies, Inc.		Internet-Draft Qualcomm Technologies, Inc.
	Intended status: Standards Track B. Rosen		Intended status: Standards Track B. Rosen
	Expires: June 10, 2015 NeuStar		Expires: June 18, 2015 NeuStar
	H. Tschofenig		H. Tschofenig
	(no affiliation)		(no affiliation)
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	J. Winterbottom		J. Winterbottom
	(no affiliation)		(no affiliation)
	December 7, 2014		December 15, 2014
	Additional Data related to an Emergency Call		Additional Data Related to an Emergency Call
	draft-ietf-ecrit-additional-data-26.txt		draft-ietf-ecrit-additional-data-27.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 June 10, 2015.		This Internet-Draft will expire on June 18, 2015.
	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 53, line 30 ¶		skipping to change at page 53, line 30 ¶
	<xs:element name="EmergencyCallData.SubscriberInfo"		<xs:element name="EmergencyCallData.SubscriberInfo"
	type="sub:SubscriberInfoType"/>		type="sub:SubscriberInfoType"/>
	<xs:complexType name="SubscriberInfoType">		<xs:complexType name="SubscriberInfoType">
	<xs:complexContent>		<xs:complexContent>
	<xs:sequence>		<xs:sequence>
	<xs:element name="DataProviderReference"		<xs:element name="DataProviderReference"
	type="xs:token" minOccurs="1" maxOccurs="1"/>		type="xs:token" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SubscriberData"		<xs:element name="SubscriberData"
	type="xc:vcardType"		type="xc:vcardType"
	minOccurs="0" maxOccurs="1" />		minOccurs="0" maxOccurs="1" />
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	<xs:attribute name="privacyRequested" type="xs:boolean"		<xs:attribute name="privacyRequested" type="xs:boolean"
	use="required"/>		use="required"/>
	</xs:complexContent>		</xs:complexContent>
	</xs:complexType>		</xs:complexType>
	skipping to change at page 80, line 24 ¶		skipping to change at page 80, line 24 ¶
	[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,		[RFC3204] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
	F., Watson, M., and M. Zonoun, "MIME media types for ISUP		F., Watson, M., and M. Zonoun, "MIME media types for ISUP
	and QSIG Objects", RFC 3204, December 2001.		and QSIG Objects", RFC 3204, December 2001.
	[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,		[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
	A., Peterson, J., Sparks, R., Handley, M., and E.		A., Peterson, J., Sparks, R., Handley, M., and E.
	Schooler, "SIP: Session Initiation Protocol", RFC 3261,		Schooler, "SIP: Session Initiation Protocol", RFC 3261,
	June 2002.		June 2002.
	[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
	Extensions to the Session Initiation Protocol (SIP) for
	Asserted Identity within Trusted Networks", RFC 3325,
	November 2002.
	[RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail		[RFC3459] Burger, E., "Critical Content Multi-purpose Internet Mail
	Extensions (MIME) Parameter", RFC 3459, January 2003.		Extensions (MIME) Parameter", RFC 3459, January 2003.
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.		January 2004.
	[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object		[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
	Format", RFC 4119, December 2005.		Format", RFC 4119, December 2005.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	skipping to change at page 81, line 19 ¶		skipping to change at page 81, line 15 ¶
	[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,		[RFC7303] Thompson, H. and C. Lilley, "XML Media Types", RFC 7303,
	July 2014.		July 2014.
	12.2. Informational References		12.2. Informational References
	[I-D.gellens-slim-negotiating-human-language]		[I-D.gellens-slim-negotiating-human-language]
	Gellens, R., "Negotiating Human Language in Real-Time		Gellens, R., "Negotiating Human Language in Real-Time
	Communications", draft-gellens-slim-negotiating-human-		Communications", draft-gellens-slim-negotiating-human-
	language (work in progress), October 2014.		language (work in progress), October 2014.
			[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
			Extensions to the Session Initiation Protocol (SIP) for
			Asserted Identity within Trusted Networks", RFC 3325,
			November 2002.
	[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,		[RFC3840] Rosenberg, J., Schulzrinne, H., and P. Kyzivat,
	"Indicating User Agent Capabilities in the Session		"Indicating User Agent Capabilities in the Session
	Initiation Protocol (SIP)", RFC 3840, August 2004.		Initiation Protocol (SIP)", RFC 3840, August 2004.
	[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC		[RFC3966] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC
	3966, December 2004.		3966, December 2004.
	[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for		[RFC5012] Schulzrinne, H. and R. Marshall, "Requirements for
	Emergency Context Resolution with Internet Technologies",		Emergency Context Resolution with Internet Technologies",
	RFC 5012, January 2008.		RFC 5012, January 2008.
End of changes. 7 change blocks.
	11 lines changed or deleted		11 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/