"IPv6 Traffic Engineering in IS-IS", Jon Harrison, 26-Jun-08. ( bytes)

This document specifies a method for exchanging IPv6 Traffic Engineering information using the IS-IS routing protocol. The described method uses three new TLVs, together with two new sub-TLVs of the Extended IS Reachability TLV. The information distributed allows a CSPF algorithm to calculate traffic engineered routes using IPv6 addresses.

"Simplified Extension of LSP Space for IS-IS", Les Ginsberg, Stefano Previdi, Mike Shand, Danny McPherson, 18-Nov-08. ( bytes)

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

"IS-IS Generic Cryptographic Authentication", Manav Bhatia, 18-Nov-08. ( bytes)

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. Although this document has been written specifically for using the Hashed Message Authentication Code (HMAC) construct along with the Secure Hash Algorithm (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.

"Advertising Generic Information in IS-IS", Les Ginsberg, Stefano Previdi, Mike Shand, 20-Jun-08. ( bytes)

This draft describes the manner in which generic application information (i.e. information not directly related to the operation of the IS-IS protocol) SHOULD be advertised in IS-IS LSPs and defines guidelines which SHOULD be used when flooding such information.

"IS-IS Multi-Instance", Stefano Previdi, Les Ginsberg, Mike Shand, David Ward, Abhay Roy, 29-Oct-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.

Return to Internet-Draft directory.

Return to IETF home page.