OSPF Application-Specific Link Attributes
RFC 8920, “OSPF Application-Specific Link Attributes”, is a Proposed Standard document published in October 2020 by P. Psenak, L. Ginsberg, W. Henderickx, J. Tantsura, J. Drake. It has been obsoleted by RFC 9492 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
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 (e.g., Segment Routing Policy and Loop-Free Alternates) 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 new link attribute advertisements in OSPFv2 and OSPFv3 that address both of these shortcomings.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8920 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8919 IS-IS Application-Specific Link Attributes
- RFC 8921 Dynamic Service Negotiation: The Connectivity Provisioning Negotiation Protocol
- RFC 8918 Invalid TLV Handling in IS-IS
- RFC 8922 A Survey of the Interaction between Security Protocols and Transport Services
- RFC 8917 The LoST-Validation Straightforward-Naming Authority PoinTeR Application Service Tag
- RFC 8923 A Minimal Set of Transport Services for End Systems
- RFC 8916 A YANG Data Model for the Multicast Source Discovery Protocol
- RFC 8924 Service Function Chaining Operations, Administration, and Maintenance Framework