Skip to main content

IS-IS Application-Specific Link Attributes
RFC 8919

Revision differences

Document history

Date By Action
2022-05-14
(System) Received changes through RFC Editor sync (removed Errata tag (all errata rejected))
2021-07-06
(System) Received changes through RFC Editor sync (added Errata tag)
2020-10-23
(System) IANA registries were updated to include RFC8919
2020-10-22
(System)
Received changes through RFC Editor sync (created alias RFC 8919, 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 8919, 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 (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.', changed pages to 20, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-10-22, changed IESG state to RFC Published)
2020-10-22
(System) RFC published