metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9492: OSPF Application-Specific Link Attributes

In plain English — editorial summary, not part of the RFC

Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications such as Segment Routing (SR) Policy and Loop-Free Alternates (LFAs) that also make use of the link attribute advertisements have been defined. In cases where multiple applications wish to make use of these link attributes, the current advertisements do not support application-specific values for a given attribute, nor do they support indication of which applications are using the advertised value for a given link. This document introduces link attribute advertisements in OSPFv2 and OSPFv3 that address both of these shortcomings. This document obsoletes RFC 8920.

Document record

Document ID
RFC9492
Published
October 2023
Authors
P. Psenak; L. Ginsberg; W. Henderickx; J. Tantsura; J. Drake
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
20
Also known as
—
Obsoletes:
RFC 8920

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/9492-ospf-application-specific-link-attributes