Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3032,RFC 3270,RFC 3272,RFC 3443,RFC 3469,RFC 3564,RFC 3985,RFC 4182,RFC 4364,RFC 4379,RFC 4448,RFC 4761,RFC 5129

Authors:

L. Andersson
R. Asati

Stream:

IETF

Source:

mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5462

Discuss this RFC: Send questions or comments to the mailing listmpls@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5462

Abstract

The early Multiprotocol Label Switching (MPLS) documents defined theform of the MPLS label stack entry. This includes a three-bit fieldcalled the "EXP field". The exact use of this field was not definedby these documents, except to state that it was to be "reserved forexperimental use".

Although the intended use of the EXP field was as a "Class ofService" (CoS) field, it was not named a CoS field by these earlydocuments because the use of such a CoS field was not considered tobe sufficiently defined. Today a number of standards documentsdefine its usage as a CoS field.

To avoid misunderstanding about how this field may be used, it hasbecome increasingly necessary to rename this field. This documentchanges the name of the field to the "Traffic Class field" ("TCfield"). In doing so, it also updates documents that define thecurrent use of the EXP field. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.