Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Obsoletes:

RFC 8920

Authors:

P. Psenak, Ed.
L. Ginsberg
W. Henderickx
J. Tantsura
J. Drake

Stream:

IETF

Source:

lsr (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

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 suchas Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) thatalso make use of the link attribute advertisements have been defined. In cases where 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 link attributeadvertisements in OSPFv2 and OSPFv3 that address both of theseshortcomings.

This document obsoletes RFC 8920.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.