RFC 5129: Explicit Congestion Marking in MPLS

RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may…

Read RFC 5129 on the RFC Editor

Outgoing relationships (1 related RFC)

Updates — RFC 3032: MPLS Label Stack Encoding

Incoming relationships (15 related RFCs)

Updated by, Normatively referenced by — RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
Normatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Normatively referenced by — RFC 8100: Diffserv-Interconnection Classes and Practice
Normatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Normatively referenced by — RFC 9599: Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
Normatively referenced by — RFC 9435: Considerations for Assigning a New Recommended Differentiated Services Code Point (DSCP)
Normatively referenced by — RFC 9601: Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a Shim
Informatively referenced by — RFC 6040: Tunnelling of Explicit Congestion Notification
Informatively referenced by — RFC 7657: Differentiated Services (Diffserv) and Real-Time Communication
Informatively referenced by — RFC 5559: Pre-Congestion Notification (PCN) Architecture
Informatively referenced by — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Informatively referenced by — RFC 6077: Open Research Issues in Internet Congestion Control
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 5704: Uncoordinated Protocol Development Considered Harmful