"Routing IPv6 with IS-IS", Christian Hopps, 5-Oct-07. ( bytes)

This draft specifies a method for exchanging IPv6 routing information using the IS-IS routing protocol. The described method utilizes 2 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.

"Point-to-point operation over LAN in link-state routing protocols", Naiming Shen, 20-Apr-06. ( bytes)

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.

"IS-IS extensions for Traffic Engineering", Tony Li, Henk Smit, 7-Apr-08. ( bytes)

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 (LSP) Data Units. This information describes additional details regarding the state of the network that are useful for traffic engineering computations.

"Simplified Extension of LSP Space for IS-IS", Les Ginsberg, Stefano Previdi, Mike Shand, Danny McPherson, 5-Dec-07. ( bytes)

This draft describes a simplified method for extending the LSP space beyond the 256 Link State PDU (LSP) limit defined in [ISO 10589]. This method is intended as a preferred replacement for the method defined in [RFC 3786].

"IS-IS Generic Cryptographic Authentication", Manav Bhatia, 7-Nov-07. ( bytes)

This document proposes an extension to 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 3567. Although this document has been written specifically for using HMAC construct along with the SHA family of cryptographic hash functions, the method described in this document is generic and can be used to extend IS-IS to support any cryptographic hash function in the future.

"Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", Kireeti Kompella, Yakov Rekhter, 7-Apr-08. ( bytes)

This document specifies encoding of extensions to the IS-IS routing protocol in support of Generalized Multi-Protocol Label Switching (GMPLS).

"Dynamic Hostname Exchange Mechanism for IS-IS", Danny McPherson, Naiming Shen, 8-Apr-08. ( bytes)

Currently, there does not exist a simple and dynamic mechanism for routers running IS-IS to learn about symbolic hostnames. This document defines a new TLV which allows the IS-IS routers to flood their name-to-systemID mapping information across the IS-IS network. The intention of this document is to provide an update to [RFC 2763].

"Restart Signaling for Intermediate System to Intermediate System (IS-IS)", Mike Shand, Les Ginsberg, 1-Nov-07. ( bytes)

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 LSP database synchronization with its neighbors and a mechanism to optimize LSP database synchronization, while minimizing transient routing disruption when a router starts.

"Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication", Tony Li, Randall Atkinson, 17-Mar-08. ( bytes)

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.

"Domain-wide Prefix Distribution with Two-Level IS-IS", Tony Li, Henk Smit, Tony Przygienda, 25-Apr-08. ( bytes)

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 insure 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.

"IS-IS Multi-Instance", Stefano Previdi, Les Ginsberg, Mike Shand, David Ward, Abhay Roy, 18-Feb-08. ( bytes)

This draft describes a mechanism that allows a single router to share one or more links among multiple IS-IS routing protocol instances. Multiple instances allow the isolation of resources associated with each instance. Routers will form instance specific adjacencies, exchange instance specific routing updates and compute paths utilizing instance specific LSDB information. Each PDU will contain a new TLV identifying the instance to which the PDU belongs. This allows a network operator to deploy multiple IS-IS instances in parallel, using the same set of links when required and still have the capability of computing instance specific paths. This draft does not address the forwarding paradigm that needs to be used in order to ensure data PDUs are forwarded according to the paths computed by a specific instance.

"IS-IS BFD Enabled TLV", Christian Hopps, Les Ginsberg, 23-Mar-08. ( bytes)

This document describes a TLV for use in the IS-IS routing protocol that allows for the proper use of the Bidirectional Forwarding Detection protocol (BFD). There exist certain scenarios in which IS-IS will not react appropriately to a BFD detected forwarding plane failure without use of either this TLV or some other method.

"Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) Point-to-Point Adjacencies", Dave Katz, Rajesh Saluja, 17-Apr-08. ( bytes)

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.

Return to Internet-Draft directory.

Return to IETF home page.