< draft-ietf-ecrit-data-only-ea-03.txt		draft-ietf-ecrit-data-only-ea-04.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft NeuStar, Inc.		Internet-Draft NeuStar, Inc.
	Intended status: Experimental H. Schulzrinne		Intended status: Experimental H. Schulzrinne
	Expires: September 13, 2012 Columbia U.		Expires: May 13, 2013 Columbia U.
	H. Tschofenig		H. Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	March 12, 2012		November 9, 2012
	Data-Only Emergency Calls		Data-Only Emergency Calls
	draft-ietf-ecrit-data-only-ea-03.txt		draft-ietf-ecrit-data-only-ea-04.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 45 ¶		skipping to change at page 1, line 45 ¶
	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 September 13, 2012.		This Internet-Draft will expire on May 13, 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
	skipping to change at page 2, line 37 ¶		skipping to change at page 2, line 37 ¶
	6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13		6. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 15		7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
	8.1. Registration of the 'application/cap+xml' MIME type . . . 17		8.1. Registration of the 'application/cap+xml' MIME type . . . 17
	8.2. IANA Registration for 425 Response Code . . . . . . . . . 18		8.2. IANA Registration for 425 Response Code . . . . . . . . . 18
	8.3. IANA Registration of New AlertMsg-Error Header Field . . . 18		8.3. IANA Registration of New AlertMsg-Error Header Field . . . 18
	8.4. IANA Registration for the SIP AlertMsg-Error Codes . . . . 19		8.4. IANA Registration for the SIP AlertMsg-Error Codes . . . . 19
	9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20		9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21		10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 21
	10.1. Normative References . . . . . . . . . . . . . . . . . . . 21		10.1. Normative References . . . . . . . . . . . . . . . . . . . 21
	10.2. Informative References . . . . . . . . . . . . . . . . . . 22		10.2. Informative References . . . . . . . . . . . . . . . . . . 21
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 23
	1. Introduction		1. Introduction
	RFC 6443 [RFC6443] describes how devices use the Internet to place		RFC 6443 [RFC6443] describes how devices use the Internet to place
	emergency calls and how Public Safety Answering Points (PSAPs) can		emergency calls and how Public Safety Answering Points (PSAPs) can
	handle Internet multimedia emergency calls natively. The exchange of		handle Internet multimedia emergency calls natively. The exchange of
	multimedia traffic typically involves a SIP session establishment		multimedia traffic typically involves a SIP session establishment
	starting with a SIP INVITE that negotiates various parameters for		starting with a SIP INVITE that negotiates various parameters for
	that session.		that session.
	skipping to change at page 19, line 12 ¶		skipping to change at page 19, line 12 ¶
	Header Name compact Reference		Header Name compact Reference
	----------------- ------- ---------		----------------- ------- ---------
	AlertMsg-Error [this doc]		AlertMsg-Error [this doc]
	2. In the portion titled "Header Field Parameters and Parameter		2. In the portion titled "Header Field Parameters and Parameter
	Values", add		Values", add
	Predefined		Predefined
	Header Field Parameter Name Values Reference		Header Field Parameter Name Values Reference
	----------------- ------------------- ---------- ---------		----------------- ------------------- ---------- ---------
	AlertMsg-Error code yes [this doc]		AlertMsg-Error code yes [this doc]
	8.4. IANA Registration for the SIP AlertMsg-Error Codes		8.4. IANA Registration for the SIP AlertMsg-Error Codes
	This document creates a new registry for SIP, called "AlertMsg-Error		This document creates a new registry for SIP, called "AlertMsg-Error
	Codes". AlertMsg-Error codes provide reason for the error discovered		Codes". AlertMsg-Error codes provide reason for the error discovered
	by recipients, categorized by action to be taken by error recipient.		by recipients, categorized by action to be taken by error recipient.
	The initial values for this registry are shown below.		The initial values for this registry are shown below.
	Registry Name: AlertMsg-Error Codes		Registry Name: AlertMsg-Error Codes
	skipping to change at page 21, line 36 ¶		skipping to change at page 21, line 36 ¶
	[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,		for the Session Initiation Protocol", RFC 6442,
	December 2011.		December 2011.
	[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.
	[RFC3311] Rosenberg, J., "The Session Initiation Protocol (SIP)
	UPDATE Method", RFC 3311, October 2002.
	[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,		[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C.,
	and D. Gurle, "Session Initiation Protocol (SIP) Extension		and D. Gurle, "Session Initiation Protocol (SIP) Extension
	for Instant Messaging", RFC 3428, December 2002.		for Instant Messaging", RFC 3428, December 2002.
	[RFC6086] Holmberg, C., Burger, E., and H. Kaplan, "Session
	Initiation Protocol (SIP) INFO Method and Package
	Framework", RFC 6086, January 2011.
	[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
	Event Notification", RFC 3265, June 2002.
	[RFC3903] Niemi, A., "Session Initiation Protocol (SIP) Extension
	for Event State Publication", RFC 3903, October 2004.
	[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax		[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", STD 68, RFC 5234, January 2008.		Specifications: ABNF", STD 68, RFC 5234, January 2008.
	[I-D.ietf-ecrit-additional-data]		[I-D.ietf-ecrit-additional-data]
	Rosen, B., Tschofenig, H., and R. Marshall, "Additional		Rosen, B., Tschofenig, H., and R. Marshall, "Additional
	Data related to an Emergency Call",		Data related to an Emergency Call",
	draft-ietf-ecrit-additional-data-02 (work in progress),		draft-ietf-ecrit-additional-data-05 (work in progress),
	October 2011.		October 2012.
	10.2. Informative References		10.2. Informative References
	[I-D.ietf-atoca-requirements]
	Rosen, B., Schulzrinne, H., Tschofenig, H., and S.
	Norreys, "Requirements, Terminology and Framework for
	Exigent Communications", draft-ietf-atoca-requirements-02
	(work in progress), October 2011.
	[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 Information",		"Trustworthy Location",
	draft-ietf-ecrit-trustworthy-location-02 (work in		draft-ietf-ecrit-trustworthy-location-04 (work in
	progress), May 2011.		progress), October 2012.
	[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. 11 change blocks.
	30 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/