RFC 5305: IS-IS Extensions for Traffic Engineering

This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support Traffic Engineering (TE). This document…

Read RFC 5305 on the RFC Editor

Outgoing relationships (7 related RFCs)

Obsoletes, Informative reference — RFC 3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5302: Domain-Wide Prefix Distribution with Two-Level IS-IS
Informative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
Informative reference — RFC 5304: IS-IS Cryptographic Authentication
Informative reference — RFC 2702: Requirements for Traffic Engineering Over MPLS

Incoming relationships (52 related RFCs)

Showing 50 of 52 related RFCs.

Updated by — RFC 5307: IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Updated by, Normatively referenced by — RFC 8918: Invalid TLV Handling in IS-IS
Normatively referenced by — RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
Normatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normatively referenced by — RFC 7176: Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
Normatively referenced by — RFC 5308: Routing IPv6 with IS-IS
Normatively referenced by — RFC 6119: IPv6 Traffic Engineering in IS-IS
Normatively referenced by — RFC 7780: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Normatively referenced by — RFC 7356: IS-IS Flooding Scope Link State PDUs (LSPs)
Normatively referenced by — RFC 6001: Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)
Normatively referenced by — RFC 7981: IS-IS Extensions for Advertising Router Information
Normatively referenced by — RFC 7308: Extended Administrative Groups in MPLS Traffic Engineering (MPLS-TE)
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 7446: Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks
Normatively referenced by — RFC 8668: Advertising Layer 2 Bundle Member Link Attributes in IS-IS
Normatively referenced by — RFC 6823: Advertising Generic Information in IS-IS
Normatively referenced by — RFC 7180: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Normatively referenced by — RFC 6326: Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
Normatively referenced by — RFC 6373: MPLS Transport Profile (MPLS-TP) Control Plane Framework
Normatively referenced by — RFC 5311: Simplified Extension of Link State PDU (LSP) Space for IS-IS
Normatively referenced by — RFC 7810: IS-IS Traffic Engineering (TE) Metric Extensions
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9479: IS-IS Application-Specific Link Attributes
Normatively referenced by — RFC 9843: IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints
Normatively referenced by — RFC 8233: Extensions to the Path Computation Element Communication Protocol (PCEP) to Compute Service-Aware Label Switched Paths (LSPs)
Normatively referenced by — RFC 8919: IS-IS Application-Specific Link Attributes
Normatively referenced by — RFC 9346: IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 9857: Advertisement of Segment Routing Policies Using BGP - Link State
Normatively referenced by — RFC 5330: A Link-Type sub-TLV to Convey the Number of Traffic Engineering Label Switched Paths Signalled with Zero Reserved Bandwidth across a Link
Normatively referenced by — RFC 7775: IS-IS Route Preference for Extended IP and IPv6 Reachability
Normatively referenced by — RFC 9439: Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics
Normatively referenced by — RFC 9502: IGP Flexible Algorithm in IP Networks
Normatively referenced by — RFC 9666: Area Proxy for IS-IS
Normatively referenced by — RFC 7813: IS-IS Path Control and Reservation
Normatively referenced by — RFC 8196: IS-IS Autoconfiguration
Normatively referenced by — RFC 9885: Multi-Part TLVs in IS-IS
Informatively referenced by — RFC 8231: Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE
Informatively referenced by — RFC 9256: Segment Routing Policy Architecture
Informatively referenced by — RFC 7490: Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)
Informatively referenced by — RFC 8667: IS-IS Extensions for Segment Routing
Informatively referenced by — RFC 5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Informatively referenced by — RFC 5443: LDP IGP Synchronization
Informatively referenced by — RFC 7491: A PCE-Based Architecture for Application-Based Network Operations
Informatively referenced by — RFC 5817: Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks
Informatively referenced by — RFC 8795: YANG Data Model for Traffic Engineering (TE) Topologies
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 6107: Procedures for Dynamically Signaled Hierarchical Label Switched Paths
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks
Informatively referenced by — RFC 6825: Traffic Engineering Database Management Information Base in Support of MPLS-TE/GMPLS
Informatively referenced by — RFC 5468: Performance Analysis of Inter-Domain Path Computation Methodologies