The Addition of Explicit Congestion Notification (ECN) to IP

The Addition of Explicit Congestion Notification (ECN) to IP (2001)

Cached

Download Links

by K. K. Ramakrishnan , Sally Floyd , David Black , Group K. Ramakrishnan

Citations:

BibTeX

@MISC{Ramakrishnan01theaddition,
    author = {K. K. Ramakrishnan and Sally Floyd and David Black and Group K. Ramakrishnan},
    title = {The Addition of Explicit Congestion Notification (ECN) to IP},
    year = {2001}
}

Years of Citing Articles

Bookmark

OpenURL

Abstract

This memo specifies the incorporation of ECN (Explicit Congestion Notification) to TCP and IP, including ECN's use of two bits in the IP header. Table of Contents 1.

Citations

1933	Random early detection gateways for congestion avoidance - Floyd, Jacobson - 1993
1092	Key words for use in RFCs to Indicate Requirement Levels - Bradner - 1997
678	Transmission control protocol - Postel - 1981
601	Receiver-driven layered multicast - McCanne, Jacobson, et al. - 1996
477	TCP and explicit congestion notification - Floyd - 1994
444	Internet protocol - Postel - 1981
368	A proposal to add Explicit Congestion Notification (ECN - Ramakrishnan, Floyd - 1999
291	binary feedback scheme for congestion avoidance in computer networks - Ramakrishnan, Jain - 1990
193	IP authentication header - Atkinson - 1995
151	Key words for use in RFCs to indicate requirement levels. RFC 2119 (Best Current Practice - Bradner - 1997
134	Modified TCP Congestion Avoidance Algorithm, end2end internet mailing list - Jacobson
130	TCP congestion control with a misbehaving receiver - Savage, Cardwell, et al. - 1999
122	Promoting the Use of End-to-End Congestion - Floyd, Fall - 1999
110	The Internet IP security domain of interpretation for ISAKMP - Piper - 1998
108	Definition of the differentiated services field - Nichols, Blake, et al. - 1998
67	Type of Service - Almquist - 1992
27	Generic Routing Encapsulation over IPv4 networks.” RFC 1702 - Hanks, Li, et al. - 1994
26	Receiver driven layered multicast - McCanne, Jacobson, et al. - 1996
26	Differentiated Services and Tunnels - Black - 2000
22	Incremental updating of the Internet checksum - Mallory, Kullberg - 1990
20	Generic Routing Encapsulation (GRE - Farinacci, Li, et al.
17	An Architecture for Differentiated Services - Weiss - 1998
14	RFC2780] IANA Allocation Guidelines For Values - Bradner, Paxson - 2000
6	IP Encapsulating Security Payload", RFC 2406 - Kent, Atkinson - 1998
6	Analyzing Explicit Congestion Notification (ECN) benefits for TCP - Krishnan - 1998
5	Physical Link Security Type of Service", RFC 1455 - Eastlake - 1993
4	Dynamics of Random Early Detection", SIGCOMM '97 - Lin, Morris - 1997
4	A Proposal to Incorporate ECN - Ramakrishnan, S, et al. - 1999
4	the one-bit implementation an ECN-capable data sender would have to unambiguously indicate to the receiver or receivers whether each packet had been sent as ECN-Capable or as non-ECN-Capable. One possibility would be for the sender to indicate in the tran - Thus - 1999
2	Ramakrishnan TeraOptic Networks, Inc. Phone: +1 (408) 666-8650 Email: kk@teraoptic.com Sally Floyd Phone - K
2	01748 Phone: +1 (508) 435-1000 x75140 Email: black_david@emc.com This draft was created in - Hopkinton - 2001
1	Key words for use in RFCs to Indicate Requirement Ramakrishnan and Floyd Proposed Standard [Page 37] draft-ietf-tsvwg-ecn-00 - Bradner - 1997
1	Two Tunneling Protocol "L2TP - Layer - 1999
1	Proposed Standard [Page 38] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November 2000 [PPTP - Ramakrishnan, Floyd - 1996
1	Point-to-Point Tunneling Protocol (PPTP)", RFC 2637 - Zorn - 1999
1	Definition Ramakrishnan and Floyd Proposed Standard [Page 39] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November - Nichols, Blake, et al. - 1998
1	Hadi Salim and Uvaiz Ahmed, "Performance Evaluation of Explicit Congestion Notification (ECN - Jamal - 2000
1	Header Checksum Recalculation IPv4 header checksum recalculation is an issue with some high-end router architectures using an output-buffered switch, since most if not all of the header manipulation is performed on the input side of the switch, while the - IPv4 - 2000
1	Proposed Standard [Page 41] draft-ietf-tsvwg-ecn-02 Addition of ECN to IP February 2001 [RFC 2119 - Ramakrishnan, Black - 1997
1	Proposed Standard [Page 43] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November 2000 Thus for this case of an ECN-capable transport, the consequence of this change to the ECN field is no worse than dropping the packet. 18.1.5. Changes with No Functiona - Ramakrishnan, Floyd
1	Proposed Standard [Page 45] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November 2000 19.1. Implications for the Network and for Competing Flows The CE bit of the ECN field is only used by routers as an indication of congestion during periods of *modera - Ramakrishnan, Floyd
1	use two bits in the IP header? Given the need for an ECT indication in the IP header, there still remains the question of whether the ECT (ECN-Capable Transport) and CE (Congestion Experienced) indications should have been overloaded on a single bit. This - Why
1	Proposed Standard [Page 51] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November 2000 In summary, while the one-bit implementation could be a possible implementation, it has the following significant limitations relative to the two-bit implementation. F - Ramakrishnan, Floyd
1	Proposed Standard [Page 53] draft-ietf-tsvwg-ecn-00 Addition of ECN to IP November 2000 - Ramakrishnan, Floyd - 2000
1	Proposed Standard [Page 42] draft-ietf-tsvwg-ecn-02 Addition of ECN to IP February 2001 [SCWA99 - Ramakrishnan, Black - 1999
1	Proposed Standard [Page 44] draft-ietf-tsvwg-ecn-01 Addition of ECN to IP November 2000 Packets with a spoofed IP source address of the TCP data sender could include the CWR bit set. Again, to be accepted, such a packet would have to have a valid sequence - Ramakrishnan, Black
1	Proposed Standard [Page 46] draft-ietf-tsvwg-ecn-02 Addition of ECN to IP February 2001 Packets with a spoofed IP source address of the TCP data sender could include the CWR bit set. Again, to be accepted, such a packet would have to have a valid sequence - Ramakrishnan, Black
1	Proposed Standard [Page 48] draft-ietf-tsvwg-ecn-01 Addition of ECN to IP November 2000 19.2. Implications for the Subverted Flow When a source indicates that it is ECN-capable, there is an expectation that the routers in the network that are capable of p - Ramakrishnan, Black
1	RFC 1455 have been obsoleted by "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers" [RFC2474] in which bits 6 and 7 of the DS field are listed as Currently Unused (CU). RFC 2780 [RFC2780] specified ECN as an - RFC
1	to RFC 2474, routers were not permitted to modify bits in either the DSCP or ECN field of packets forwarded through them, and hence routers that comply only with RFCs prior to 2474 should have no Ramakrishnan, Floyd, Black Proposed Standard [Page 57] draf - Prior