RFC 9479: IS-IS Application-Specific Link Attributes

Existing traffic-engineering-related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case…

Read RFC 9479 on the RFC Editor

Outgoing relationships (16 related RFCs)

Obsoletes — RFC 8919: IS-IS Application-Specific Link Attributes
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5305: IS-IS Extensions for Traffic Engineering
Normative reference — RFC 5304: IS-IS Cryptographic Authentication
Normative reference — RFC 5310: IS-IS Generic Cryptographic Authentication
Normative reference — RFC 5307: IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Normative reference — RFC 6119: IPv6 Traffic Engineering in IS-IS
Normative reference — RFC 8570: IS-IS Traffic Engineering (TE) Metric Extensions
Normative reference — RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
Normative reference — RFC 7370: Updates to the IS-IS TLV Codepoints Registry
Informative reference — RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels
Informative reference — RFC 5286: Basic Specification for IP Fast Reroute: Loop-Free Alternates
Informative reference — RFC 9256: Segment Routing Policy Architecture
Informative reference — RFC 7855: Source Packet Routing in Networking (SPRING) Problem Statement and Requirements

Incoming relationships (3 related RFCs)

Normatively referenced by — RFC 9843: IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints
Normatively referenced by — RFC 9885: Multi-Part TLVs in IS-IS
Informatively referenced by — RFC 9933: Carrying SR-Algorithm in Path Computation Element Communication Protocol (PCEP)