RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5462
- Published
- February 2009
- Authors
- L. Andersson; R. Asati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5467GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs)Obsoleted
March 2009
- RFC 5455Diffserv-Aware Class-Type Object for the Path Computation Element Communication ProtocolCurrent
March 2009
- RFC 5449OSPF Multipoint Relay (MPR) Extension for Ad Hoc NetworksCurrent
February 2009
- RFC 5444Generalized Mobile Ad Hoc Network (MANET) Packet/Message FormatUpdated
February 2009
- RFC 5443LDP IGP SynchronizationUpdated
March 2009
- RFC 5441A Backward-Recursive PCE-Based Computation (BRPC) Procedure to Compute Shortest Constrained Inter-Domain Traffic Engineering Label Switched PathsCurrent
April 2009
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 5439An Analysis of Scaling Issues in MPLS-TE Core NetworksCurrent
February 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?