Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification Feedback
RFC 7560, “Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification Feedback”, is an Informational document published in August 2015 by M. Kuehlewind, R. Scheffenegger, B. Briscoe. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7560 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7559 Packet-Loss Resiliency for Router Solicitations
- RFC 7561 Mapping Quality of Service Procedures of Proxy Mobile IPv6 and WLAN
- RFC 7558 Requirements for Scalable DNS-Based Service Discovery / Multicast DNS Extensions
- RFC 7562 Transport Layer Security Authorization Using Digital Transmission Content Protection Certificates
- RFC 7557 Extension Mechanism for the Babel Routing Protocol
- RFC 7563 Extensions to the Proxy Mobile IPv6 Access Network Identifier Option
- RFC 7556 Multiple Provisioning Domain Architecture
- RFC 7564 PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols