TRansparent Interconnection of Lots of Links : Explicit Congestion Notification Support
RFC 9600, “TRansparent Interconnection of Lots of Links : Explicit Congestion Notification Support”, is a Proposed Standard document published in August 2024 by D. Eastlake 3rd, B. Briscoe. The canonical text is published by the RFC Editor.
Abstract
Explicit Congestion Notification (ECN) allows a forwarding element to notify downstream devices, including the destination, of the onset of congestion without having to drop packets. This can improve network efficiency through better congestion control without packet drops. This document extends ECN to TRansparent Interconnection of Lots of Links (TRILL) switches, including integration with IP ECN, and provides for ECN marking in the TRILL header extension flags word (RFC 7179).
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9600 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9599 Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
- RFC 9601 Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
- RFC 9598 Internationalized Email Addresses in X.509 Certificates
- RFC 9602 Segment Routing over IPv6 Segment Identifiers in the IPv6 Addressing Architecture
- RFC 9597 CBOR Web Token Claims in COSE Headers
- RFC 9603 Path Computation Element Communication Protocol Extensions for IPv6 Segment Routing
- RFC 9596 CBOR Object Signing and Encryption "typ" Header Parameter
- RFC 9604 Carrying Binding Label/SID in PCE-Based Networks