< draft-ietf-ecrit-data-only-ea-08.txt		draft-ietf-ecrit-data-only-ea-09.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft NeuStar, Inc.		Internet-Draft NeuStar, Inc.
	Intended status: Standards Track H. Schulzrinne		Intended status: Standards Track H. Schulzrinne
	Expires: January 25, 2015 Columbia U.		Expires: April 30, 2015 Columbia U.
	H. Tschofenig		H. Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	July 24, 2014		October 27, 2014
	Data-Only Emergency Calls		Data-Only Emergency Calls
	draft-ietf-ecrit-data-only-ea-08.txt		draft-ietf-ecrit-data-only-ea-09.txt
	Abstract		Abstract
	RFC 6443 'Framework for Emergency Calling Using Internet Multimedia'		RFC 6443 'Framework for Emergency Calling Using Internet Multimedia'
	describes how devices use the Internet to place emergency calls and		describes how devices use the Internet to place emergency calls and
	how Public Safety Answering Points (PSAPs) can handle Internet		how Public Safety Answering Points (PSAPs) can handle Internet
	multimedia emergency calls natively. The exchange of multimedia		multimedia emergency calls natively. The exchange of multimedia
	traffic typically involves a SIP session establishment starting with		traffic typically involves a SIP session establishment starting with
	a SIP INVITE that negotiates various parameters for that session.		a SIP INVITE that negotiates various parameters for that session.
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 25, 2015.		This Internet-Draft will expire on April 30, 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 4, line 14 ¶		skipping to change at page 4, line 14 ¶
	3. Architectural Overview		3. Architectural Overview
	This section illustrates two envisioned usage modes; targeted and		This section illustrates two envisioned usage modes; targeted and
	location-based emergency alert routing.		location-based emergency alert routing.
	1. Emergency alerts containing only data are targeted to a		1. Emergency alerts containing only data are targeted to a
	intermediary recipient responsible for evaluating the next steps.		intermediary recipient responsible for evaluating the next steps.
	These steps could include:		These steps could include:
	1. Sending an alert containing only data toward a Public Safety		1. Sending a call containing only data toward a Public Safety
	Answering Point (PSAP);		Answering Point (PSAP);
	2. Establishing a third-party initiated emergency call towards a		2. Establishing a third-party initiated emergency call towards a
	PSAP that could include audio, video, and data.		PSAP that could include audio, video, and data.
	2. Emergency alerts targeted to a Service URN used for IP-based		2. Emergency alerts may be targeted to a Service URN used for IP-
	emergency calls where the recipient is not known to the		based emergency calls where the recipient is not known to the
	originator. In this scenario, the alert may contain only data		originator. In this scenario, the alert may contain only data
	(e.g., a CAP, Geolocation header and one or more Call-Info		(e.g., a CAP, Geolocation header and one or more Call-Info
	headers containing Additional Data		headers containing Additional Data
	[I-D.ietf-ecrit-additional-data] in a SIP MESSAGE).		[I-D.ietf-ecrit-additional-data] in a SIP MESSAGE).
	Figure 1 shows a deployment variant where a sensor, is pre-configured		Figure 1 shows a deployment variant where a sensor, is pre-configured
	(using techniques outside the scope of this document) to issue an		(using techniques outside the scope of this document) to issue an
	alert to an aggregator that processes these messages and performs		alert to an aggregator that processes these messages and performs
	whatever steps are necessary to appropriately react on the alert.		whatever steps are necessary to appropriately react on the alert.
	For example, a security firm may use different sensor inputs to		For example, a security firm may use different sensor inputs to
	skipping to change at page 21, line 20 ¶		skipping to change at page 21, line 20 ¶
	[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance		[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
	for the Session Initiation Protocol", RFC 6442, December		for the Session Initiation Protocol", RFC 6442, December
	2011.		2011.
	[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for		[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
	Communications Services in Support of Emergency Calling",		Communications Services in Support of Emergency Calling",
	BCP 181, RFC 6881, March 2013.		BCP 181, RFC 6881, March 2013.
	[I-D.ietf-ecrit-additional-data]		[I-D.ietf-ecrit-additional-data]
	Rosen, B., Tschofenig, H., Marshall, R., Randy, R., and J.		Randy, R., Rosen, B., Tschofenig, H., Marshall, R., and J.
	Winterbottom, "Additional Data related to an Emergency		Winterbottom, "Additional Data related to an Emergency
	Call", draft-ietf-ecrit-additional-data-22 (work in		Call", draft-ietf-ecrit-additional-data-24 (work in
	progress), April 2014.		progress), October 2014.
	[I-D.rosen-ecrit-addldata-subnot]		[I-D.rosen-ecrit-addldata-subnot]
	Rosen, B., "Updating Additional Data related to an		Rosen, B., "Updating Additional Data related to an
	Emergency Call using Subscribe/ Notify", draft-rosen-		Emergency Call using Subscribe/ Notify", draft-rosen-
	ecrit-addldata-subnot-01 (work in progress), November		ecrit-addldata-subnot-01 (work in progress), November
	2013.		2013.
	13.2. Informative References		13.2. Informative References
	[I-D.ietf-ecrit-trustworthy-location]		[I-D.ietf-ecrit-trustworthy-location]
	Tschofenig, H., Schulzrinne, H., and B. Aboba,		Tschofenig, H., Schulzrinne, H., and B. Aboba,
	"Trustworthy Location", draft-ietf-ecrit-trustworthy-		"Trustworthy Location", draft-ietf-ecrit-trustworthy-
	location-13 (work in progress), June 2014.		location-14 (work in progress), July 2014.
	[RFC4474] Peterson, J. and C. Jennings, "Enhancements for		[RFC4474] Peterson, J. and C. Jennings, "Enhancements for
	Authenticated Identity Management in the Session		Authenticated Identity Management in the Session
	Initiation Protocol (SIP)", RFC 4474, August 2006.		Initiation Protocol (SIP)", RFC 4474, August 2006.
	[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private		[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
	Extensions to the Session Initiation Protocol (SIP) for		Extensions to the Session Initiation Protocol (SIP) for
	Asserted Identity within Trusted Networks", RFC 3325,		Asserted Identity within Trusted Networks", RFC 3325,
	November 2002.		November 2002.
End of changes. 9 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/