Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Obsoleted by:

RFC 9479

Authors:

L. Ginsberg
P. Psenak
S. Previdi
W. Henderickx
J. Drake

Stream:

IETF

Source:

lsr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Existing traffic-engineering-related link attribute advertisementshave been defined and are used in RSVP-TE deployments. Since theoriginal RSVP-TE use case was defined, additional applications (e.g.,Segment Routing Policy and Loop-Free Alternates) that also make useof the link attribute advertisements have been defined. In caseswhere multiple applications wish to make use of these linkattributes, the current advertisements do not supportapplication-specific values for a given attribute, nor do theysupport indication of which applications are using the advertisedvalue for a given link. This document introduces new link attributeadvertisements that address both of these shortcomings.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.