RFC 3540: Robust Explicit Congestion Notification (ECN) Signaling with Nonces

In plain English — editorial summary, not part of the RFC

This note describes the Explicit Congestion Notification (ECN)-nonce, an optional addition to ECN that protects against accidental or malicious concealment of marked packets from the TCP sender. It improves the robustness of congestion control by preventing receivers from exploiting ECN to gain an unfair share of network bandwidth. The ECN-nonce uses the two ECN-Capable Transport (ECT)codepoints in the ECN field of the IP header, and requires a flag in the TCP header. It is computationally efficient for both routers and hosts. This memo defines an Experimental Protocol for the Internet community.

Document record

Document ID

RFC3540

Published

June 2003

Authors

N. Spring; D. Wetherall; D. Ely

Status

HISTORIC

Stream

IETF

Area

wit

Pages

13

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3540

Topics

• ECN
• explicit congestion notification
• TCP
• transmission control protocol

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3522The Eifel Detection Algorithm for TCPCurrent

  April 2003

• RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted

  April 2003

• RFC 3649HighSpeed TCP for Large Congestion WindowsCurrent

  December 2003

• RFC 3390Increasing TCP's Initial WindowCurrent

  November 2002

• RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent

  March 2004

• RFC 3782The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted

  April 2004

• RFC 3168The Addition of Explicit Congestion Notification (ECN) to IPUpdated

  September 2001

• RFC 3042Enhancing TCP's Loss Recovery Using Limited TransmitCurrent

  January 2001

Also filed under

• HISTORIC
• 2003
• IETF stream
• wit area