RFC 8919
IS-IS Application-Specific Link Attributes, October 2020
- 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 list lsr@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 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 that address both of these shortcomings.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.