Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000029169D
Original Publication Date: 2004-Jun-01
Included in the Prior Art Database: 2004-Jun-17
Document File: 14 page(s) / 27K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

H. Smit: AUTHOR [+2]

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 10% of the total text.

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                      [Page 1]

RFC 3784        IS-IS extensions for Traffic Engineering       June 2004

   The router id is useful for traffic engineering purposes because it

   describes a single address that can always be used to reference a

   particular router.

   Mechanisms and procedures to migrate to the new TLVs are not

   discussed in this document.

2.  Introducing Sub-TLVs

   This document introduces a new way to encode routing information in

   IS-IS.  The new object is called a sub-TLV.  Sub-TLVs are similar to

  ...