RFC 5302: Domain-Wide Prefix Distribution with Two-Level IS-IS
In plain English — editorial summary, not part of the RFC
This document describes extensions to the Intermediate System to Intermediate System (IS-IS) protocol to support optimal routing within a two-level domain. The IS-IS protocol is specified in ISO 10589, with extensions for supporting IPv4 (Internet Protocol) specified in RFC 1195. This document replaces RFC 2966. This document extends the semantics presented in RFC 1195 so that a routing domain running with both level 1 and level 2 Intermediate Systems (IS) (routers) can distribute IP prefixes between level 1 and level 2, and vice versa. This distribution requires certain restrictions to ensure that persistent forwarding loops do not form. The goal of this domain-wide prefix distribution is to increase the granularity of the routing information within the domain. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5302
- Published
- October 2008
- Authors
- T. Li; H. Smit; T. Przygienda
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 3609Tracing Requirements for Generic TunnelsCurrent
October 2003
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 3077A Link-Layer Tunneling Mechanism for Unidirectional LinksCurrent
March 2001
- RFC 3033The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet ProtocolCurrent
January 2001
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 4654TCP-Friendly Multicast Congestion Control (TFMCC): Protocol SpecificationCurrent
August 2006
- RFC 4570Session Description Protocol (SDP) Source FiltersCurrent
July 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?