< draft-ietf-tsvwg-source-quench-03.txt		draft-ietf-tsvwg-source-quench-04.txt >
	Transport Area Working Group (tsvwg) F. Gont		Transport Area Working Group (tsvwg) F. Gont
	Internet-Draft UTN/FRH		Internet-Draft UTN/FRH
	Updates: 792, 1122, 1812 December 22, 2011		Obsoletes: 1016 (if approved) January 19, 2012
			Updates: 792, 1122, 1812
	(if approved)		(if approved)
	Intended status: Standards Track		Intended status: Standards Track
	Expires: June 24, 2012		Expires: July 22, 2012
	Deprecation of ICMP Source Quench messages		Deprecation of ICMP Source Quench messages
	draft-ietf-tsvwg-source-quench-03.txt		draft-ietf-tsvwg-source-quench-04.txt
	Abstract		Abstract
	This document formally deprecates the use of ICMP Source Quench		This document formally deprecates the use of ICMP Source Quench
	messages by transport protocols, formally updating RFC 792, RFC 1122,		messages by transport protocols, formally updating RFC 792, RFC 1122,
	and RFC 1812. Additionally, it requests that the status of RFC 1016		and RFC 1812. Additionally, it requests that the status of RFC 1016
	be changed to "Historic".		be changed to "Historic".
	Status of this Memo		Status of this Memo
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 36 ¶
	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 24, 2012.		This Internet-Draft will expire on July 22, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 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
	skipping to change at page 2, line 26 ¶		skipping to change at page 2, line 27 ¶
	9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6		9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
	10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6		10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
	11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6		11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
	11.1. Normative References . . . . . . . . . . . . . . . . . . . 6		11.1. Normative References . . . . . . . . . . . . . . . . . . . 6
	11.2. Informative References . . . . . . . . . . . . . . . . . . 7		11.2. Informative References . . . . . . . . . . . . . . . . . . 7
	Appendix A. Survey of support of ICMP Source Quench in some		Appendix A. Survey of support of ICMP Source Quench in some
	popular TCP/IP implementations . . . . . . . . . . . . 7		popular TCP/IP implementations . . . . . . . . . . . . 7
	Appendix B. Changes from previous versions of the draft (to		Appendix B. Changes from previous versions of the draft (to
	be removed by the RFC Editor before publishing		be removed by the RFC Editor before publishing
	this document as an RFC) . . . . . . . . . . . . . . . 8		this document as an RFC) . . . . . . . . . . . . . . . 8
	B.1. Changes from draft-ietf-tsvwg-source-quench-01 . . . . . . 8		B.1. Changes from draft-ietf-tsvwg-source-quench-03 . . . . . . 8
	B.2. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 8		B.2. Changes from draft-ietf-tsvwg-source-quench-02 . . . . . . 8
	B.3. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 8		B.3. Changes from draft-ietf-tsvwg-source-quench-01 . . . . . . 8
	B.4. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 8		B.4. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 8
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8		B.5. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 8
			B.6. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 8
			Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	The ICMP specification [RFC0792] defined the ICMP Source Quench		The ICMP specification [RFC0792] defined the ICMP Source Quench
	message (type 4, code 0), which was meant as a mechanism for		message (type 4, code 0), which was meant as a mechanism for
	congestion control. ICMP Source Quench has been known to be an		congestion control. ICMP Source Quench has been known to be an
	ineffective (and unfair) antidote for congestion, and generation of		ineffective (and unfair) antidote for congestion, and generation of
	ICMP Source Quench messages by routers has been formally deprecated		ICMP Source Quench messages by routers has been formally deprecated
	by [RFC1812] since 1995. However, reaction to ICMP Source Quench		by [RFC1812] since 1995. However, reaction to ICMP Source Quench
	messages in transport protocols has never been formally deprecated.		messages in transport protocols has never been formally deprecated.
	skipping to change at page 6, line 27 ¶		skipping to change at page 6, line 27 ¶
	9. IANA Considerations		9. IANA Considerations
	IANA is requested to mark ICMP type 4 (Source Quench) as "Deprecated"		IANA is requested to mark ICMP type 4 (Source Quench) as "Deprecated"
	in de ICMP Parameters registry [ICMPPARREG] with a reference to this		in de ICMP Parameters registry [ICMPPARREG] with a reference to this
	document.		document.
	10. Acknowledgements		10. Acknowledgements
	The author of this document would like to thank (in alphabetical		The author of this document would like to thank (in alphabetical
	order) Fred Baker, David Black, Scott Bradner, James Carlson, Antonio		order) Fred Baker, David Black, Scott Bradner, James Carlson, Antonio
	De Simone, Gorry Fairhurst, Alfred Hoenes, Mahesh Jethanandani,		De Simone, Wesley Eddy, Gorry Fairhurst, Alfred Hoenes, Mahesh
	Carlos Pignataro, Anantha Ramaiah, Randall Stewart, Dan Wing, and		Jethanandani, Carlos Pignataro, Anantha Ramaiah, Randall Stewart, Dan
	Andrew Yourtchenko, for providing valuable feedback on earlier		Wing, and Andrew Yourtchenko, for providing valuable feedback on
	versions of this document.		earlier versions of this document.
	This document has benefited from discussions within the TCPM Working		This document has benefited from discussions within the TCPM Working
	Group while working on [RFC5927].		Group while working on [RFC5927].
	11. References		11. References
	11.1. Normative References		11.1. Normative References
	[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,		[RFC0792] Postel, J., "Internet Control Message Protocol", STD 5,
	RFC 792, September 1981.		RFC 792, September 1981.
	[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,		[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
	RFC 793, September 1981.		RFC 793, September 1981.
	[RFC1016] Prue, W. and J. Postel, "Something a host could do with
	source quench: The Source Quench Introduced Delay
	(SQuID)", RFC 1016, July 1987.
	[RFC1122] Braden, R., "Requirements for Internet Hosts -		[RFC1122] Braden, R., "Requirements for Internet Hosts -
	Communication Layers", STD 3, RFC 1122, October 1989.		Communication Layers", STD 3, RFC 1122, October 1989.
	[RFC1812] Baker, F., "Requirements for IP Version 4 Routers",		[RFC1812] Baker, F., "Requirements for IP Version 4 Routers",
	RFC 1812, June 1995.		RFC 1812, June 1995.
	[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.
	[RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion		[RFC5681] Allman, M., Paxson, V., and E. Blanton, "TCP Congestion
	skipping to change at page 7, line 39 ¶		skipping to change at page 7, line 34 ¶
	[Linux] The Linux Project, "http://www.kernel.org".		[Linux] The Linux Project, "http://www.kernel.org".
	[NetBSD] The NetBSD Project, "http://www.netbsd.org".		[NetBSD] The NetBSD Project, "http://www.netbsd.org".
	[OpenBSD] The OpenBSD Project, "http://www.openbsd.org".		[OpenBSD] The OpenBSD Project, "http://www.openbsd.org".
	[OpenSolaris]		[OpenSolaris]
	OpenSolaris, "http://www.opensolaris.org".		OpenSolaris, "http://www.opensolaris.org".
			[RFC1016] Prue, W. and J. Postel, "Something a host could do with
			source quench: The Source Quench Introduced Delay
			(SQuID)", RFC 1016, July 1987.
	[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition		[RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
	of Explicit Congestion Notification (ECN) to IP",		of Explicit Congestion Notification (ECN) to IP",
	RFC 3168, September 2001.		RFC 3168, September 2001.
	[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control		[RFC4443] Conta, A., Deering, S., and M. Gupta, "Internet Control
	Message Protocol (ICMPv6) for the Internet Protocol		Message Protocol (ICMPv6) for the Internet Protocol
	Version 6 (IPv6) Specification", RFC 4443, March 2006.		Version 6 (IPv6) Specification", RFC 4443, March 2006.
	[RFC5927] Gont, F., "ICMP Attacks against TCP", RFC 5927, July 2010.		[RFC5927] Gont, F., "ICMP Attacks against TCP", RFC 5927, July 2010.
	skipping to change at page 8, line 16 ¶		skipping to change at page 8, line 16 ¶
	Quench messages meant for TCP connections. This behavior has been		Quench messages meant for TCP connections. This behavior has been
	implemented in, at least, Linux [Linux] since 2004, and in FreeBSD		implemented in, at least, Linux [Linux] since 2004, and in FreeBSD
	[FreeBSD], NetBSD [NetBSD], OpenBSD [OpenBSD], and Solaris 10 since		[FreeBSD], NetBSD [NetBSD], OpenBSD [OpenBSD], and Solaris 10 since
	2005. Additionally, OpenSolaris [OpenSolaris] has always shipped		2005. Additionally, OpenSolaris [OpenSolaris] has always shipped
	with support for ICMP Source Quench messages disabled.		with support for ICMP Source Quench messages disabled.
	Appendix B. Changes from previous versions of the draft (to be removed		Appendix B. Changes from previous versions of the draft (to be removed
	by the RFC Editor before publishing this document as an		by the RFC Editor before publishing this document as an
	RFC)		RFC)
	B.1. Changes from draft-ietf-tsvwg-source-quench-01		B.1. Changes from draft-ietf-tsvwg-source-quench-03
			o Added 'Obsoletes' metadata, and moved the reference to [RFC1016]
			from the 'Normative References' to the 'Informative References'.
			B.2. Changes from draft-ietf-tsvwg-source-quench-02
			o Clarifies the requirements language.
			B.3. Changes from draft-ietf-tsvwg-source-quench-01
	o Changes deprecation of ICMP SQ from "SHOULD NOT" to "MUST NOT" in		o Changes deprecation of ICMP SQ from "SHOULD NOT" to "MUST NOT" in
	response of feedback from Scott Bradner and the TSV WG.		response of feedback from Scott Bradner and the TSV WG.
	B.2. Changes from draft-ietf-tsvwg-source-quench-00		B.4. Changes from draft-ietf-tsvwg-source-quench-00
	o Discusses the motivation for deprecating ICMP Source Quench		o Discusses the motivation for deprecating ICMP Source Quench
	messages (as suggested by Anantha Ramaiah).		messages (as suggested by Anantha Ramaiah).
	o Incorporates IANA considerations such that ICMP Source Quench		o Incorporates IANA considerations such that ICMP Source Quench
	messages are deprecated in the corresponding registry.		messages are deprecated in the corresponding registry.
	B.3. Changes from draft-gont-tsvwg-source-quench-01		B.5. Changes from draft-gont-tsvwg-source-quench-01
	o Addresses nits and editorial changes suggested by Gorry Fairhurst.		o Addresses nits and editorial changes suggested by Gorry Fairhurst.
	o Added the status of Solaris and OpenSolaris to Appendix A.		o Added the status of Solaris and OpenSolaris to Appendix A.
	o Document resubmitted as draft-ietf.		o Document resubmitted as draft-ietf.
	B.4. Changes from draft-gont-tsvwg-source-quench-00		B.6. Changes from draft-gont-tsvwg-source-quench-00
	o This revision reflects the recent discussion about ICMP Source		o This revision reflects the recent discussion about ICMP Source
	Quench messages on the tsvwg mailing-list. A detailed list of the		Quench messages on the tsvwg mailing-list. A detailed list of the
	changes is available at:		changes is available at:
	http://www.ietf.org/mail-archive/web/tsvwg/current/msg10407.html		http://www.ietf.org/mail-archive/web/tsvwg/current/msg10407.html
	Author's Address		Author's Address
	Fernando Gont		Fernando Gont
	Universidad Tecnologica Nacional / Facultad Regional Haedo		Universidad Tecnologica Nacional / Facultad Regional Haedo
End of changes. 13 change blocks.
	22 lines changed or deleted		34 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/