RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field

The early Multiprotocol Label Switching (MPLS) documents defined the form of the MPLS label stack entry. This includes a three-bit field called the "EXP…

Read RFC 5462 on the RFC Editor

Outgoing relationships (14 related RFCs)

Updates, Normative reference — RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)
Updates, Normative reference — RFC 3032: MPLS Label Stack Encoding
Updates, Normative reference — RFC 3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
Updates, Normative reference — RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
Updates, Normative reference — RFC 3270: Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
Updates, Normative reference — RFC 4761: Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
Updates, Normative reference — RFC 4448: Encapsulation Methods for Transport of Ethernet over MPLS Networks
Updates, Normative reference — RFC 3443: Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
Updates, Normative reference — RFC 5129: Explicit Congestion Marking in MPLS
Updates, Normative reference — RFC 3272: Overview and Principles of Internet Traffic Engineering
Updates, Normative reference — RFC 3469: Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
Updates, Normative reference — RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
Updates, Normative reference — RFC 4182: Removing a Restriction on the use of MPLS Explicit NULL
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels

Incoming relationships (32 related RFCs)

Normatively referenced by — RFC 6513: Multicast in MPLS/BGP IP VPNs
Normatively referenced by — RFC 5586: MPLS Generic Associated Channel
Normatively referenced by — RFC 8660: Segment Routing with the MPLS Data Plane
Normatively referenced by — RFC 6374: Packet Loss and Delay Measurement for MPLS Networks
Normatively referenced by — RFC 9012: The BGP Tunnel Encapsulation Attribute
Normatively referenced by — RFC 5960: MPLS Transport Profile Data Plane Architecture
Normatively referenced by — RFC 8296: Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks
Normatively referenced by — RFC 8666: OSPFv3 Extensions for Segment Routing
Normatively referenced by — RFC 8964: Deterministic Networking (DetNet) Data Plane: MPLS
Normatively referenced by — RFC 9830: Advertising Segment Routing Policies in BGP
Normatively referenced by — RFC 8957: Synonymous Flow Label Framework
Normatively referenced by — RFC 9604: Carrying Binding Label/SID in PCE-Based Networks
Normatively referenced by — RFC 5824: Requirements for Supporting Customer Resource ReSerVation Protocol (RSVP) and RSVP Traffic Engineering (RSVP-TE) over a BGP/MPLS IP-VPN
Normatively referenced by — RFC 9790: IANA Registry and Processing Recommendations for the First Nibble Following a Label Stack
Normatively referenced by — RFC 5994: Application of Ethernet Pseudowires to MPLS Transport Networks
Normatively referenced by — RFC 9899: Extensions to the YANG Data Model for Access Control Lists (ACLs)
Normatively referenced by — RFC 9994: MPLS Network Action (MNA) Sub-Stack Specification Including In-Stack Network Actions and Data
Informatively referenced by — RFC 9256: Segment Routing Policy Architecture
Informatively referenced by — RFC 8029: Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
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 6424: Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels
Informatively referenced by — RFC 7110: Return Path Specified Label Switched Path (LSP) Ping
Informatively referenced by — RFC 5704: Uncoordinated Protocol Development Considered Harmful
Informatively referenced by — RFC 7325: MPLS Forwarding Compliance and Performance Requirements
Informatively referenced by — RFC 5695: MPLS Forwarding Benchmarking Methodology for IP Flows
Informatively referenced by — RFC 6601: Generic Connection Admission Control (GCAC) Algorithm Specification for IP/MPLS Networks
Informatively referenced by — RFC 6178: Label Edge Router Forwarding of IPv4 Option Packets
Informatively referenced by — RFC 7487: Configuration of Proactive Operations, Administration, and Maintenance (OAM) Functions for MPLS-Based Transport Networks Using RSVP-TE
Informatively referenced by — RFC 7190: Use of Multipath with MPLS and MPLS Transport Profile (MPLS-TP)
Informatively referenced by — RFC 9871: BGP Color-Aware Routing (CAR)