Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updates:

RFC 3032,RFC 3038,RFC 3209,RFC 3811,RFC 4182,RFC 4928,RFC 5331,RFC 5586,RFC 5921,RFC 5960,RFC 6391,RFC 6478,RFC 6790

Updated by:

RFC 9017

Authors:

K. Kompella
L. Andersson
A. Farrel

Stream:

IETF

Source:

mpls (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Some MPLS labels have been allocated for specific purposes. A blockof labels (0-15) has been set aside to this end; these labels are commonlycalled "reserved labels". They will be called "special-purpose labels" in this document.

As there are only 16 of these special-purpose labels, caution isneeded in the allocation of new special-purpose labels; yet, at thesame time, forward progress should be allowed when one is called for.

This memo defines new procedures for the allocation andretirement of special-purpose labels, as well as a method to extendthe special-purpose label space and a description of how to handleextended special-purpose labels in the data plane.Finally, this memo renames the IANAregistry for special-purpose labels to "Special-Purpose MPLS Label Values" andcreates a new registry called the "Extended Special-Purpose MPLS Label Values" registry.

This document updates a number of previous RFCs that use the term"reserved label". Specifically, this document updates RFCs 3032,3038, 3209, 3811, 4182, 4928, 5331, 5586,5921, 5960, 6391, 6478, and 6790.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.