|
|
|
|
|
|
|
|
|
|
| Last Update: May 26, 2010
|
|
|
|
|
|
|
|
|
|
|
| | |
RFC2973
10/2000
(8 p.)
pdf(2p)
|
R. Balay
D. Katz
J. Parker |
|
IS-IS Mesh Groups |
This document describes a mechanism to reduce redundant packet
transmissions for the Intermediate System to Intermediate System
(IS-IS) Routing protocol, as described in ISO 10589. The described
mechanism can be used to reduce the flooding of Link State PDUs
(Protocol Data Units) (LSPs) in IS-IS topologies. The net effect is
to engineer a flooding topology for LSPs which is a subset of the
physical topology. This document serves to document the existing
behavior in deployed implementations.
The document describes behaviors that are backwards compatible with
implementations that do not support this feature.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3277
04/2002
(6 p.)
pdf(2p)
|
D. McPherson |
|
IS-IS Transient Blackhole Avoidance |
|
This document describes a simple, interoperable mechanism that can be
employed in Intermediate System to Intermediate System (IS-IS)
networks in order to decrease the data loss associated with
deterministic blackholing of packets during transient network
conditions. The mechanism proposed here requires no IS-IS protocol
changes and is completely interoperable with the existing IS-IS
specification.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3358
08/2002
(4 p.)
pdf(2p)
|
T. Przygienda |
|
Optional Checksums in IS-IS |
|
This document describes an optional extension to the Intermediate
System to Intermediate System (ISIS) protocol, used today by several
Internet Service Proviers (ISPs) for routing within their clouds.
ISIS is an interior gateway routing protocol developed originally by
OSI and used with IP extensions as Interior Gateway Protocol (IGP).
ISIS originally does not provide Complete Sequence Numbers Protocol
Data (CSNP) and Partial Sequence Numbers Protocol Data Unit (PSNP)
checksums, relying on the underlying layers to verify the integrity
of information provided. Experience with the protocol shows that
this precondition does not always hold and scenarios can be imagined
that impact protocol functionality. This document introduces a new
optional Type, Length and Value (TLV) providing checksums.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3359
08/2002
(5 p.)
pdf(2p)
|
T. Przygienda |
|
Reserved Type, Length and Value (TLV) Codepoints in IS-IS |
|
This document describes implementation codepoints within Intermediate
System to Intermediate System (IS-IS) used today by several ISPs for
routing within their clouds. IS-IS is an interior gateway routing
protocol developed originally by OSI and used with IP extensions as
Interior Gateway Protocol (IGP). This document summarizes all Table,
Length and Value (TLV) codepoints that are being used by the protocol
and its pending extensions.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3719
02/2004
(15 p.)
pdf(2p)
|
J. Parker |
|
Recommendations for Interoperable Networks using IS-IS |
|
This document discusses a number of differences between the
Intermediate System to Intermediate System (IS-IS) protocol as
described in ISO 10589 and the protocol as it is deployed today.
These differences are discussed as a service to those implementing,
testing, and deploying the IS-IS Protocol. A companion document
discusses differences between the protocol described in RFC 1195 and
the protocol as it is deployed today for routing IP traffic.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC3787
05/2004
(11 p.)
pdf(2p)
|
J. Parker |
|
Recommendations for Interoperable IP Networks using IS-IS |
|
This document discusses a number of differences between the
Intermediate System to Intermediate System (IS-IS) protocol used to
route IP traffic as described in RFC 1195 and the protocol as it is
deployed today. These differences are discussed as a service to
those implementing, testing, and deploying the IS-IS Protocol to
route IP traffic. A companion document describes the differences
between the protocol described in ISO 10589 and current practice.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC4444
04/2006
(103 p.)
pdf(2p)
|
J. Parker |
|
Management Information Base for IS-IS |
|
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
Specifically, this document describes a MIB for the Intermediate
System to Intermediate System (IS-IS) Routing protocol when it is
used to construct routing tables for IP networks.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC4971
07/2007
(9 p.)
pdf(2p)
|
JP. Vasseur
N. Shen
R. Aggarwal |
|
IS-IS Extensions for Advertising Router Information |
|
This document defines a new optional Intermediate System to
Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple
sub-TLVs, which allows a router to announce its capabilities within
an IS-IS level or the entire routing domain.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5120
02/2008
(14 p.)
pdf(2p)
|
T. Przygienda
N. Shen
N. Sheth |
|
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 clouds. This document describes how to run,
within a single IS-IS domain, a set of independent IP topologies that
we call Multi-Topologies (MTs). This MT extension can be used for a
variety of purposes, such as an in-band management network "on top"
of the original IGP topology, maintaining separate IGP routing
domains for isolated multicast or IPv6 islands within the backbone,
or forcing a subset of an address space to follow a different
topology.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5130
02/2008
(8 p.)
pdf(2p)
|
S. Previdi
M. Shand
C. Martin |
|
A Policy Control Mechanism in IS-IS Using Administrative Tags |
|
This document describes an extension to the IS-IS protocol to add
operational capabilities that allow for ease of management and
control over IP prefix distribution within an IS-IS domain. This
document enhances the IS-IS protocol by extending the information
that an Intermediate System (IS) router can place in Link State
Protocol (LSP) Data Units for policy use. This extension will
provide operators with a mechanism to control IP prefix distribution
throughout multi-level IS-IS domains.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5301
10/2008
(6 p.)
pdf(2p)
|
D. McPherson
N. Shen |
|
Dynamic Hostname Exchange Mechanism for IS-IS |
|
RFC 2763 defined a simple and dynamic mechanism for routers running
IS-IS to learn about symbolic hostnames. RFC 2763 defined a new TLV
that allows the IS-IS routers to flood their name-to-systemID mapping
information across the IS-IS network.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5302
10/2008
(16 p.)
pdf(2p)
|
T. Li
H. Smit
T. Przygienda |
|
Domain-Wide Prefix Distribution with Two-Level IS-IS |
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.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5303
10/2008
(11 p.)
pdf(2p)
|
D. Katz
R. Saluja
D. Eastlake 3rd |
|
Three-Way Handshake for IS-IS Point-to-Point Adjacencies |
The IS-IS routing protocol (Intermediate System to Intermediate
System, ISO 10589) requires reliable protocols at the link layer for
point-to-point links. As a result, it does not use a three-way
handshake when establishing adjacencies on point-to-point media.
This paper defines a backward-compatible extension to the protocol
that provides for a three-way handshake. It is fully interoperable
with systems that do not support the extension.
Additionally, the extension allows the robust operation of more than
256 point-to-point links on a single router.
This extension has been implemented by multiple router vendors; this
paper is provided to the Internet community in order to allow
interoperable implementations to be built by other vendors.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5304
10/2008
(11 p.)
pdf(2p)
|
T. Li
R. Atkinson |
|
IS-IS Cryptographic Authentication |
This document describes the authentication of Intermediate System to
Intermediate System (IS-IS) Protocol Data Units (PDUs) using the
Hashed Message Authentication Codes - Message Digest 5 (HMAC-MD5)
algorithm as found in RFC 2104. IS-IS is specified in International
Standards Organization (ISO) 10589, with extensions to support
Internet Protocol version 4 (IPv4) described in RFC 1195. The base
specification includes an authentication mechanism that allows for
multiple authentication algorithms. The base specification only
specifies the algorithm for cleartext passwords. This document
replaces RFC 3567.
This document proposes an extension to that specification that allows
the use of the HMAC-MD5 authentication algorithm to be used in
conjunction with the existing authentication mechanisms.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5305
10/2008
(17 p.)
pdf(2p)
|
T. Li
H. Smit |
|
IS-IS Extensions for Traffic Engineering |
|
This document describes extensions to the Intermediate System to
Intermediate System (IS-IS) protocol to support Traffic Engineering
(TE). This document extends the IS-IS protocol by specifying new
information that an Intermediate System (router) can place in Link
State Protocol Data Units (LSP). This information describes
additional details regarding the state of the network that are useful
for traffic engineering computations.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5306
10/2008
(22 p.)
pdf(2p)
|
M. Shand
L. Ginsberg |
|
Restart Signaling for IS-IS |
This document describes a mechanism for a restarting router to signal
to its neighbors that it is restarting, allowing them to reestablish
their adjacencies without cycling through the down state, while still
correctly initiating database synchronization.
This document additionally describes a mechanism for a restarting
router to determine when it has achieved Link State Protocol Data
Unit (LSP) database synchronization with its neighbors and a
mechanism to optimize LSP database synchronization, while minimizing
transient routing disruption when a router starts. This document
obsoletes RFC 3847.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5308
10/2008
(7 p.)
pdf(2p)
|
C. Hopps |
|
Routing IPv6 with IS-IS |
|
This document specifies a method for exchanging IPv6 routing
information using the IS-IS routing protocol. The described method
utilizes two new TLVs: a reachability TLV and an interface address
TLV to distribute the necessary IPv6 information throughout a routing
domain. Using this method, one can route IPv6 along with IPv4 and
OSI using a single intra-domain routing protocol.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5309
10/2008
(10 p.)
pdf(2p)
|
N. Shen
A. Zinin |
|
Point-to-Point Operation over LAN in Link State Routing Protocols |
|
The two predominant circuit types used by link state routing
protocols are point-to-point and broadcast. It is important to
identify the correct circuit type when forming adjacencies, flooding
link state database packets, and representing the circuit
topologically. This document describes a simple mechanism to treat
the broadcast network as a point-to-point connection from the
standpoint of IP routing.
|
|
|
| |
| List |
Status: | Informational |
|
|
|
|
|
|
|
|
| | |
RFC5310
02/2009
(12 p.)
pdf(2p)
|
M. Bhatia
V. Manral
T. Li
R. Atkinson
R. White
M. Fanto |
|
IS-IS Generic Cryptographic Authentication |
|
This document proposes an extension to Intermediate System to
Intermediate System (IS-IS) to allow the use of any cryptographic
authentication algorithm in addition to the already-documented
authentication schemes, described in the base specification and RFC
5304. IS-IS is specified in International Standards Organization
(ISO) 10589, with extensions to support Internet Protocol version 4
(IPv4) described in RFC 1195.
|
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
| | |
RFC5311
02/2009
(12 p.)
pdf(2p)
|
D. McPherson
L. Ginsberg
S. Previdi
M. Shand |
|
|
| |
| List |
Status: | Proposed Standard |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
