draft-ietf-tsvwg-source-quench-02.txt   draft-ietf-tsvwg-source-quench-03.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 September 8, 2011 Updates: 792, 1122, 1812 December 22, 2011
(if approved) (if approved)
Intended status: Standards Track Intended status: Standards Track
Expires: March 11, 2012 Expires: June 24, 2012
Deprecation of ICMP Source Quench messages Deprecation of ICMP Source Quench messages
draft-ietf-tsvwg-source-quench-02.txt draft-ietf-tsvwg-source-quench-03.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 35
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 March 11, 2012. This Internet-Draft will expire on June 24, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 12 skipping to change at page 2, line 12
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. ICMP Source Quench messages . . . . . . . . . . . . . . . . . . 3 2. ICMP Source Quench messages . . . . . . . . . . . . . . . . . . 3
3. Updating RFC 1122 . . . . . . . . . . . . . . . . . . . . . . . 4 3. Updating RFC 1122 . . . . . . . . . . . . . . . . . . . . . . . 4
4. Updating RFC 1812 . . . . . . . . . . . . . . . . . . . . . . . 4 4. Updating RFC 1812 . . . . . . . . . . . . . . . . . . . . . . . 4
5. Clarification for SCTP and DCCP . . . . . . . . . . . . . . . . 5 5. Clarification for UDP, SCTP, and DCCP . . . . . . . . . . . . . 5
6. General Advice to Transport Protocols . . . . . . . . . . . . . 5 6. General Advice to Transport Protocols . . . . . . . . . . . . . 5
7. Changing the status of RFC 1016 to Historic . . . . . . . . . . 5 7. Changing the status of RFC 1016 to Historic . . . . . . . . . . 5
8. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
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) . . . . . . . . . . . . . . . 7 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-01 . . . . . . 8
B.2. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 8 B.2. Changes from draft-ietf-tsvwg-source-quench-00 . . . . . . 8
B.3. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 8 B.3. Changes from draft-gont-tsvwg-source-quench-01 . . . . . . 8
B.4. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 8 B.4. Changes from draft-gont-tsvwg-source-quench-00 . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
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
skipping to change at page 4, line 32 skipping to change at page 4, line 32
A host MUST NOT send ICMP Source Quench messages. A host MUST NOT send ICMP Source Quench messages.
If a Source Quench message is received, the IP layer MAY silently If a Source Quench message is received, the IP layer MAY silently
discard it. discard it.
Section 4.2.3.9 of [RFC1122] is updated as follows: Section 4.2.3.9 of [RFC1122] is updated as follows:
TCP MUST silently discard any received ICMP Source Quench TCP MUST silently discard any received ICMP Source Quench
messages. messages.
The consenus of the TSV WG was that there are no valid reasons for a The consensus of the TSV WG was that there are no valid reasons for a
host to generate or react to an ICMP Source Quench message in the host to generate or react to an ICMP Source Quench message in the
current Internet. Discarding ICMP Source Quench messages at the current Internet. The recommendation that a sender "MUST NOT" send
internet-layer (rather than at the transport layer) is a performance an ICMP Source Quench message is because there is no known valid
optimization that is permitted by this update. reason for a host to generate this message. The only known impact of
a sender ignoring this requirement is that it may necessarily consume
network and endpoint resources. Discarding ICMP Source Quench
messages at the internet-layer (rather than at the transport layer)
is a performance optimization that is permitted by this update.
4. Updating RFC 1812 4. Updating RFC 1812
This document hereby updates Section 4.3.3.3 of [RFC1812] as follows: This document hereby updates Section 4.3.3.3 of [RFC1812] as follows:
A router MUST ignore any ICMP Source Quench messages it receives. A router MUST ignore any ICMP Source Quench messages it receives.
The consenus of the TSV WG was that there are no valid reasons for a The consensus of the TSV WG was that there are no valid reasons for a
router to react to ICMP Source Quench messages in the current router to react to ICMP Source Quench messages in the current
Internet. Internet.
5. Clarification for SCTP and DCCP 5. Clarification for UDP, SCTP, and DCCP
It is understood that SCTP and SCCP did not specify support for UDP did not explicitly specify support for ICMP Source Quench
messages. Hereby we clarify that UDP end-points MUST silently
discard received ICMP Source Quench messages.
It is understood that SCTP and DCCP did not specify support for
processing received ICMP Source Quench messages. Hereby we clarify processing received ICMP Source Quench messages. Hereby we clarify
that DCCP and SCTP end-points MUST silently discard received ICMP that DCCP and SCTP end-points MUST silently discard received ICMP
Source Quench messages. Source Quench messages.
6. General Advice to Transport Protocols 6. General Advice to Transport Protocols
If a Source Quench message is received by any other transport- If a Source Quench message is received by any other transport-
protocol instance (e.g., a UDP-based protocol), it SHOULD be silently protocol instance, it MUST be silently ignored.
ignored.
The TSV WG is not aware of any use that requires processing of these The TSV WG is not aware of any use that requires processing of these
messages, and therefore expects other transports to follow the messages, and therefore expects other transports to follow the
recommendations in Section 3. Note that for IETF-specified recommendations in Section 3. Note that for IETF-specified
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. Changing the status of RFC 1016 to Historic 7. Changing the status of RFC 1016 to Historic
This document requests the RFC Editor to change the status of This document requests the RFC Editor to change the status of
[RFC1016] to "Historic". [RFC1016] to "Historic".
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]. However, as discussed in great detail in [RFC5927] and [CPNI-TCP].
noted in [RFC5927] and [CPNI-TCP], virtually all current versions of
popular TCP implementations already silently ignore ICMP Source Even though sources "MUST NOT" send ICMP Source Quench Message, there
Quench messages. This is also the case for SCTP and DCCP are no known security issues that result from receipt of this message
implementations. because, as noted in [RFC5927] and [CPNI-TCP], virtually all current
versions of popular TCP implementations already silently ignore ICMP
Source Quench messages. This is also the case for SCTP and DCCP
implementations. Receivers should not treat reception as an
exception, error or logged event. Receipt of an ICMP Source Quench
message must not be interpreted as an attempt to attack the receiver.
Silently ignoring ICMP Source Quench messages, as specified in this Silently ignoring ICMP Source Quench messages, as specified in this
document, eliminates the aforementioned attack vector. document, eliminates the aforementioned attack vector.
If deemed necessary, ICMP Source Quench messages could be filtered at If deemed necessary, ICMP Source Quench messages could be filtered at
firewalls. firewalls.
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"
skipping to change at page 8, line 20 skipping to change at page 8, line 31
B.2. Changes from draft-ietf-tsvwg-source-quench-00 B.2. 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.3. Changes from draft-gont-tsvwg-source-quench-01
o Addresses nits and editorial chagnes 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.4. 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:
 End of changes. 14 change blocks. 
21 lines changed or deleted 33 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/