RFC 3630 (rfc3630) - Page 1 of 14
Traffic Engineering (TE) Extensions to OSPF Version 2
Alternative Format: Original Text Document
Network Working Group D. Katz
Request for Comments: 3630 K. Kompella
Updates: 2370 Juniper Networks
Category: Standards Track D. Yeung
Procket Networks
September 2003
Traffic Engineering (TE) Extensions to OSPF Version 2
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This document describes extensions to the OSPF protocol version 2 to
support intra-area Traffic Engineering (TE), using Opaque Link State
Advertisements.
1. Introduction
This document specifies a method of adding traffic engineering
capabilities to OSPF Version 2 [1]. The architecture of traffic
engineering is described in [5]. The semantic content of the
extensions is essentially identical to the corresponding extensions
to IS-IS [6]. It is expected that the traffic engineering extensions
to OSPF will continue to mirror those in IS-IS.
The extensions provide a way of describing the traffic engineering
topology (including bandwidth and administrative constraints) and
distributing this information within a given OSPF area. This
topology does not necessarily match the regular routed topology,
though this proposal depends on Network LSAs to describe multi-access
links. This document purposely does not say how the mechanisms
described here can be used for traffic engineering across multiple
OSPF areas; that task is left to future documents. Furthermore, no
changes have been made to the operation of OSPFv2 flooding; in
Katz, et al. Standards Track
