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 field". The exact use of this field was not defined by these documents, except to state that it was to be "reserved for experimental use".
Although the intended use of the EXP field was as a "Class of Service" (CoS) field, it was not named a CoS field by these early documents because the use of such a CoS field was not considered to be sufficiently defined. Today a number of standards documents define its usage as a CoS field.
To avoid misunderstanding about how this field may be used, it has become increasingly necessary to rename this field. This document changes the name of the field to the "Traffic Class field" ("TC field"). In doing so, it also updates documents that define the current use of the EXP field. [STANDARDS-TRACK]
updates
- rfc-3032 — MPLS Label Stack Encoding
- rfc-3270 — Multi-Protocol Label Switching (MPLS) Support of Differentiated Services
- rfc-3272 — Overview and Principles of Internet Traffic Engineering
- rfc-3443 — Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks
- rfc-3469 — Framework for Multi-Protocol Label Switching (MPLS)-based Recovery
- rfc-3564 — Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering
- rfc-3985 — Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
- rfc-4182 — Removing a Restriction on the use of MPLS Explicit NULL
- rfc-4364 — BGP/MPLS IP Virtual Private Networks (VPNs)
- rfc-4379 — Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
- rfc-4448 — Encapsulation Methods for Transport of Ethernet over MPLS Networks
- rfc-4761 — Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling
- rfc-5129 — Explicit Congestion Marking in MPLS