draft-ietf-tsvwg-source-quench-05.txt   draft-ietf-tsvwg-source-quench-06.txt 
Transport Area Working Group (tsvwg) F. Gont Transport Area Working Group (tsvwg) F. Gont
Internet-Draft UTN-FRH / SI6 Networks Internet-Draft UTN-FRH / SI6 Networks
Updates: 792, 1122, 1812 February 22, 2012 Updates: 792, 1122, 1812 February 25, 2012
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: August 25, 2012 Expires: August 28, 2012
Deprecation of ICMP Source Quench messages Deprecation of ICMP Source Quench messages
draft-ietf-tsvwg-source-quench-05.txt draft-ietf-tsvwg-source-quench-06.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. and RFC 1812.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 25, 2012. This Internet-Draft will expire on August 28, 2012.
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 25 skipping to change at page 2, line 25
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
11.1. Normative References . . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . 8 popular TCP/IP implementations . . . . . . . . . . . . 8
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-04 . . . . . . 8 B.1. Changes from draft-ietf-tsvwg-source-quench-05 . . . . . . 8
B.2. Changes from draft-ietf-tsvwg-source-quench-03 . . . . . . 8 B.2. Changes from draft-ietf-tsvwg-source-quench-04 . . . . . . 8
B.3. Changes from draft-ietf-tsvwg-source-quench-02 . . . . . . 9 B.3. Changes from draft-ietf-tsvwg-source-quench-03 . . . . . . 8
B.4. Changes from draft-ietf-tsvwg-source-quench-01 . . . . . . 9 B.4. Changes from draft-ietf-tsvwg-source-quench-02 . . . . . . 9
B.5. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 9 B.5. Changes from draft-ietf-tsvwg-source-quench-01 . . . . . . 9
B.6. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 9 B.6. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 9
B.7. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 9 B.7. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 9
B.8. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 9 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
skipping to change at page 5, line 40 skipping to change at page 5, line 40
transports, this document formally deprecates reaction to ICMP Source transports, this document formally deprecates reaction to ICMP Source
Quench messages, and that generation of ICMP Source Quench messages Quench messages, and that generation of ICMP Source Quench messages
has been deprecated for both hosts and routers. Therefore, future has been deprecated for both hosts and routers. Therefore, future
applications can not expect to receive these messages. applications can not expect to receive these messages.
7. Recommendation Regarding RFC 1016 7. Recommendation Regarding RFC 1016
RFC 1016 [RFC1016] described an experimental approach to ICMP Source RFC 1016 [RFC1016] described an experimental approach to ICMP Source
Quench message handling in hosts that was being thought about in Quench message handling in hosts that was being thought about in
1987. The IETF notes that RFC 1016 has never been on the IETF 1987. The IETF notes that RFC 1016 has never been on the IETF
standards-track, but for clarity and avoidance of doubt, the note standards-track, but for clarity and avoidance of doubt, we note that
that the approach described in RFC 1016 [RFC1016] MUST NOT be the approach described in RFC 1016 [RFC1016] MUST NOT be implemented.
implemented.
8. Security Considerations 8. Security Considerations
ICMP Source Quench messages could be leveraged for performing blind ICMP Source Quench messages could be leveraged for performing blind
throughput-reduction attacks against TCP and similar protocols. This throughput-reduction attacks against TCP and similar protocols. This
attack vector, along with possible countermeasures, has been attack vector, along with possible countermeasures, has been
discussed in great detail in [RFC5927] and [CPNI-TCP]. Silently discussed in great detail in [RFC5927] and [CPNI-TCP]. Silently
ignoring ICMP Source Quench messages, as specified in this document, ignoring ICMP Source Quench messages, as specified in this document,
eliminates the aforementioned attack vector. eliminates the aforementioned attack vector.
skipping to change at page 8, line 36 skipping to change at page 8, line 36
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-04 B.1. Changes from draft-ietf-tsvwg-source-quench-05
o Fixes minor writeo in Section 7.
B.2. Changes from draft-ietf-tsvwg-source-quench-04
o Removes request to move RFC 1016 to "Historic" status. o Removes request to move RFC 1016 to "Historic" status.
o Updates the Security Considerations section. o Updates the Security Considerations section.
B.2. Changes from draft-ietf-tsvwg-source-quench-03 B.3. Changes from draft-ietf-tsvwg-source-quench-03
o Added 'Obsoletes' metadata, and moved the reference to [RFC1016] o Added 'Obsoletes' metadata, and moved the reference to [RFC1016]
from the 'Normative References' to the 'Informative References'. from the 'Normative References' to the 'Informative References'.
B.3. Changes from draft-ietf-tsvwg-source-quench-02 B.4. Changes from draft-ietf-tsvwg-source-quench-02
o Clarifies the requirements language. o Clarifies the requirements language.
B.4. Changes from draft-ietf-tsvwg-source-quench-01 B.5. 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.5. Changes from draft-ietf-tsvwg-source-quench-00 B.6. 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.6. Changes from draft-gont-tsvwg-source-quench-01 B.7. 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.7. Changes from draft-gont-tsvwg-source-quench-00 B.8. 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
UTN-FRH / SI6 Networks UTN-FRH / SI6 Networks
 End of changes. 13 change blocks. 
21 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/