RFC 9666: Area Proxy for IS-IS

Link-state routing protocols have hierarchical abstraction already built into them. However, when lower levels are used for transit, they must expose their…

Read RFC 9666 on the RFC Editor

Outgoing relationships (19 related RFCs)

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 8402: Segment Routing Architecture
Normative reference — RFC 1195: Use of OSI IS-IS for routing in TCP/IP and dual environments
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 5120: M-ISIS: Multi Topology (MT) Routing in Intermediate System to Intermediate Systems (IS-ISs)
Normative reference — RFC 5308: Routing IPv6 with IS-IS
Normative reference — RFC 6119: IPv6 Traffic Engineering in IS-IS
Normative reference — RFC 8667: IS-IS Extensions for Segment Routing
Normative reference — RFC 7981: IS-IS Extensions for Advertising Router Information
Normative reference — RFC 9352: IS-IS Extensions to Support Segment Routing over the IPv6 Data Plane
Normative reference — RFC 8491: Signaling Maximum SID Depth (MSD) Using IS-IS
Normative reference — RFC 5301: Dynamic Hostname Exchange Mechanism for IS-IS
Normative reference — RFC 9667: Dynamic Flooding on Dense Graphs
Informative reference — RFC 8126: Guidelines for Writing an IANA Considerations Section in RFCs
Informative reference — RFC 7120: Early IANA Allocation of Standards Track Code Points

Incoming relationships (1 related RFC)

Normatively referenced by — RFC 9717: A Routing Architecture for Satellite Networks