Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

M. Kuehlewind, Ed.
R. Scheffenegger
B. Briscoe

Stream:

IETF

Source:

tcpm (wit)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7560

Discuss this RFC: Send questions or comments to the mailing listtcpm@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7560

Abstract

Explicit Congestion Notification (ECN) is a mechanism where networknodes can mark IP packets, instead of dropping them, to indicatecongestion to the endpoints. An ECN-capable receiver will feed thisinformation back to the sender. ECN is specified for TCP in such away that it can only feed back one congestion signal per Round-TripTime (RTT). In contrast, ECN for other transport protocols, such asRTP/UDP and SCTP, is specified with more accurate ECN feedback.Recent new TCP mechanisms (like Congestion Exposure (ConEx) or DataCenter TCP (DCTCP)) need more accurate ECN feedback in the case wheremore than one marking is received in one RTT. This documentspecifies requirements for an update to the TCP protocol to providemore accurate ECN feedback.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.