Skip to main content

OSPF Application-Specific Link Attributes
RFC 9492

Revision differences

Document history

Date By Action
2023-10-10
(System)
Received changes through RFC Editor sync (created alias RFC 9492, changed abstract to 'Existing traffic-engineering-related link attribute advertisements have been defined and are used …
Received changes through RFC Editor sync (created alias RFC 9492, changed abstract to '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.', changed pages to 20, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2023-10-10, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-lsr-rfc8920bis and RFC 8920)
2023-10-10
(System) RFC published