RFC 3784 (rfc3784) - Page 1 of 13


Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)



Alternative Format: Original Text Document



Network Working Group                                            H. Smit
Request for Comments: 3784                              Procket Networks
Category: Informational                                            T. Li
                                                               June 2004


           Intermediate System to Intermediate System (IS-IS)
                Extensions for Traffic Engineering (TE)

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   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.

1.  Introduction

   The IS-IS protocol is specified in ISO 10589 [1], with extensions for
   supporting IPv4 specified in RFC 1195 [3].  Each Intermediate System
   (IS) (router) advertises one or more IS-IS Link State Protocol Data
   Units (LSPs) with routing information.  Each LSP is composed of a
   fixed header and a number of tuples, each consisting of a Type, a
   Length, and a Value.  Such tuples are commonly known as TLVs, and are
   a good way of encoding information in a flexible and extensible
   format.

   This document contains the design of new TLVs to replace the existing
   IS Neighbor TLV, IP Reachability TLV, and to include additional
   information about the characteristics of a particular link to an IS-
   IS LSP.  The characteristics described in this document are needed
   for Traffic Engineering [4] (TE).  Secondary goals include increasing
   the dynamic range of the IS-IS metric and improving the encoding of
   IP prefixes.




Smit & Li                    Informational