RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP

The purpose of this document is to guide the design of congestion notification in any lower-layer or tunnelling protocol that encapsulates IP. The aim is for…

Read RFC 9599 on the RFC Editor

Outgoing relationships (37 related RFCs)

Updates, Normative reference — RFC 3819: Advice for Internet Subnetwork Designers
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Normative reference — RFC 6040: Tunnelling of Explicit Congestion Notification
Normative reference — RFC 5129: Explicit Congestion Marking in MPLS
Normative reference — RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Normative reference — RFC 7141: Byte and Packet Congestion Notification
Normative reference — RFC 9600: TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support
Informative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Informative reference — RFC 4301: Security Architecture for the Internet Protocol
Informative reference — RFC 2784: Generic Routing Encapsulation (GRE)
Informative reference — RFC 2003: IP Encapsulation within IP
Informative reference — RFC 2473: Generic Packet Tunneling in IPv6 Specification
Informative reference — RFC 4380: Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)
Informative reference — RFC 3931: Layer Two Tunneling Protocol - Version 3 (L2TPv3)
Informative reference — RFC 2661: Layer Two Tunneling Protocol "L2TP"
Informative reference — RFC 2983: Differentiated Services and Tunnels
Informative reference — RFC 7348: Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks
Informative reference — RFC 8300: Network Service Header (NSH)
Informative reference — RFC 7567: IETF Recommendations Regarding Active Queue Management
Informative reference — RFC 7323: TCP Extensions for High Performance
Informative reference — RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
Informative reference — RFC 7637: NVGRE: Network Virtualization Using Generic Routing Encapsulation
Informative reference — RFC 7780: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Informative reference — RFC 2637: Point-to-Point Tunneling Protocol (PPTP)
Informative reference — RFC 7713: Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements
Informative reference — RFC 8311: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation
Informative reference — RFC 8926: Geneve: Generic Network Virtualization Encapsulation
Informative reference — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Informative reference — RFC 9300: The Locator/ID Separation Protocol (LISP)
Informative reference — RFC 2884: Performance Evaluation of Explicit Congestion Notification (ECN) in IP Networks
Informative reference — RFC 6633: Deprecation of ICMP Source Quench Messages
Informative reference — RFC 8084: Network Transport Circuit Breakers
Informative reference — RFC 8087: The Benefits of Using Explicit Congestion Notification (ECN)
Informative reference — RFC 8257: Data Center TCP (DCTCP): TCP Congestion Control for Data Centers
Informative reference — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informative reference — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 9600: TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) Support
Normatively referenced by — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim