RFC 7560

Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback, August 2015

Canonical URL:
https://www.rfc-editor.org/rfc/rfc7560.txt
File formats:
Plain TextPDF
Status:
INFORMATIONAL
Authors:
M. Kuehlewind, Ed.
R. Scheffenegger
B. Briscoe
Stream:
IETF
Source:
tcpm (tsv)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC7560

Discuss this RFC: Send questions or comments to tcpm@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

Explicit Congestion Notification (ECN) is a mechanism where network nodes can mark IP packets, instead of dropping them, to indicate congestion to the endpoints. An ECN-capable receiver will feed this information back to the sender. ECN is specified for TCP in such a way that it can only feed back one congestion signal per Round-Trip Time (RTT). In contrast, ECN for other transport protocols, such as RTP/UDP and SCTP, is specified with more accurate ECN feedback. Recent new TCP mechanisms (like Congestion Exposure (ConEx) or Data Center TCP (DCTCP)) need more accurate ECN feedback in the case where more than one marking is received in one RTT. This document specifies requirements for an update to the TCP protocol to provide more accurate ECN feedback.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×