RFC 6119: IPv6 Traffic Engineering in IS-IS

This document specifies a method for exchanging IPv6 traffic engineering information using the IS-IS routing protocol. This information enables routers in an…

Read RFC 6119 on the RFC Editor

Outgoing relationships (5 related RFCs)

Normative reference — RFC 5305: IS-IS Extensions for Traffic Engineering
Normative reference — RFC 5304: IS-IS Cryptographic Authentication
Normative reference — RFC 4202: Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Normative reference — RFC 5307: IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)
Normative reference — RFC 5308: Routing IPv6 with IS-IS

Incoming relationships (13 related RFCs)

Normatively referenced by — RFC 7752: North-Bound Distribution of Link-State and Traffic Engineering (TE) Information Using BGP
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 8668: Advertising Layer 2 Bundle Member Link Attributes in 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 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 9666: Area Proxy for IS-IS
Normatively referenced by — RFC 9885: Multi-Part TLVs in IS-IS
Informatively referenced by — RFC 7490: Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks