RFC 9600: TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support

Explicit Congestion Notification (ECN) allows a forwarding element to notify downstream devices, including the destination, of the onset of congestion without…

Read RFC 9600 on the RFC Editor

Outgoing relationships (13 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Normative reference — RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
Normative reference — RFC 7567: IETF Recommendations Regarding Active Queue Management
Normative reference — RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Normative reference — RFC 7780: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Normative reference — RFC 8311: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation
Normative reference — RFC 7179: Transparent Interconnection of Lots of Links (TRILL): Header Extension
Normative reference — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Informative reference — RFC 6040: Tunnelling of Explicit Congestion Notification
Informative reference — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Informative reference — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)

Incoming relationships (1 related RFC)

Normatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP