RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments

This memo specifies an integrated routing protocol, based on the OSI Intra-Domain IS-IS Routing Protocol, which may be used as an interior gateway protocol…

Read RFC 1195 on the RFC Editor

Incoming relationships (65 related RFCs)

Showing 50 of 65 related RFCs.

Updated by, Informatively referenced by — RFC 5304: IS-IS Cryptographic Authentication
Updated by, Informatively referenced by — RFC 1349: Type of Service in the Internet Protocol Suite
Updated by — RFC 5302: Domain-Wide Prefix Distribution with Two-Level IS-IS
Normatively referenced by — RFC 5310: IS-IS Generic Cryptographic Authentication
Normatively referenced by — RFC 6325: Routing Bridges (RBridges): Base Protocol Specification
Normatively referenced by — RFC 5120: M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)
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 5316: ISIS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
Normatively referenced by — RFC 7981: IS-IS Extensions for Advertising Router Information
Normatively referenced by — RFC 6039: Issues with Existing Cryptographic Protection Methods for Routing Protocols
Normatively referenced by — RFC 9182: A YANG Network Data Model for Layer 3 VPNs
Normatively referenced by — RFC 5073: IGP Routing Protocol Extensions for Discovery of Traffic Engineering Node Capabilities
Normatively referenced by — RFC 6439: Routing Bridges (RBridges): Appointed Forwarders
Normatively referenced by — RFC 7357: Transparent Interconnection of Lots of Links (TRILL): End Station Address Distribution Information (ESADI) Protocol
Normatively referenced by — RFC 4971: Intermediate System to Intermediate System (IS-IS) Extensions for Advertising Router Information
Normatively referenced by — RFC 7178: Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Support
Normatively referenced by — RFC 5303: Three-Way Handshake for IS-IS Point-to-Point Adjacencies
Normatively referenced by — RFC 5306: Restart Signaling for IS-IS
Normatively referenced by — RFC 7180: Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
Normatively referenced by — RFC 6213: IS-IS BFD-Enabled TLV
Normatively referenced by — RFC 6326: Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
Normatively referenced by — RFC 4972: Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership
Normatively referenced by — RFC 6327: Routing Bridges (RBridges): Adjacency
Normatively referenced by — RFC 5029: Definition of an IS-IS Link Attribute Sub-TLV
Normatively referenced by — RFC 6412: Terminology for Benchmarking Link-State IGP Data-Plane Route Convergence
Normatively referenced by — RFC 7096: Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)
Normatively referenced by — RFC 9130: YANG Data Model for the IS-IS Protocol
Normatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Normatively referenced by — RFC 9843: IGP Flexible Algorithms: Bandwidth, Delay, Metrics, and Constraints
Normatively referenced by — RFC 6396: Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
Normatively referenced by — RFC 8706: Restart Signaling for IS-IS
Normatively referenced by — RFC 9346: IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering
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 6413: Benchmarking Methodology for Link-State IGP Data-Plane Route Convergence
Normatively referenced by — RFC 9666: Area Proxy for IS-IS
Normatively referenced by — RFC 4450: Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents
Normatively referenced by — RFC 7645: The Keying and Authentication for Routing Protocol (KARP) IS-IS Security Analysis
Normatively referenced by — RFC 8196: IS-IS Autoconfiguration
Informatively referenced by — RFC 1812: Requirements for IP Version 4 Routers
Informatively referenced by — RFC 5305: IS-IS Extensions for Traffic Engineering
Informatively referenced by — RFC 9256: Segment Routing Policy Architecture
Informatively referenced by — RFC 1930: Guidelines for creation, selection, and registration of an Autonomous System (AS)
Informatively referenced by — RFC 8345: A YANG Data Model for Network Topologies
Informatively referenced by — RFC 7490: Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)
Informatively referenced by — RFC 6551: Routing Metrics Used for Path Calculation in Low-Power and Lossy Networks
Informatively referenced by — RFC 7177: Transparent Interconnection of Lots of Links (TRILL): Adjacency
Informatively referenced by — RFC 5565: Softwire Mesh Framework
Informatively referenced by — RFC 4110: A Framework for Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)
Informatively referenced by — RFC 6518: Keying and Authentication for Routing Protocols (KARP) Design Guidelines