RFC 5120: M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)

This document describes an optional mechanism within Intermediate System to Intermediate Systems (IS-ISs) used today by many ISPs for IGP routing within their…

Read RFC 5120 on the RFC Editor

Outgoing relationships (6 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
Normative reference — RFC 3692: Assigning Experimental and Testing Numbers Considered Useful
Informative reference — RFC 3784: Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)
Informative reference — RFC 3567: Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication

Incoming relationships (26 related RFCs)

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 8667: IS-IS Extensions for Segment Routing
Normatively referenced by — RFC 9552: Distribution of Link-State and Traffic Engineering Information Using BGP
Normatively referenced by — RFC 6822: IS-IS Multi-Instance
Normatively referenced by — RFC 6213: IS-IS BFD-Enabled TLV
Normatively referenced by — RFC 9085: Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing
Normatively referenced by — RFC 6329: IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging
Normatively referenced by — RFC 8202: IS-IS Multi-Instance
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 9692: RIFT: Routing in Fat Trees
Normatively referenced by — RFC 7775: IS-IS Route Preference for Extended IP and IPv6 Reachability
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 9658: Multipoint LDP Extensions for Multi-Topology Routing
Normatively referenced by — RFC 9885: Multi-Part TLVs in IS-IS
Informatively referenced by — RFC 8402: Segment Routing Architecture
Informatively referenced by — RFC 6550: RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
Informatively referenced by — RFC 7177: Transparent Interconnection of Lots of Links (TRILL): Adjacency
Informatively referenced by — RFC 8939: Deterministic Networking (DetNet) Data Plane: IP
Informatively referenced by — RFC 7297: IP Connectivity Provisioning Profile (CPP)
Informatively referenced by — RFC 9843: IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints
Informatively 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
Informatively referenced by — RFC 6420: PIM Multi-Topology ID (MT-ID) Join Attribute