OSPF TE Only Option
draft-venkata-ospf-te-only-option-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Venkata Naidu | ||
| Last updated | 2002-04-04 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
OSPF is a link state routing protocol used for IP-network topology discovery using different types of Link State Advertisements. The resulting Link State Database (LSDB) is used to compute IP address forwarding table based on shortest-path criteria. OSPF has been extended to support Traffic Engineering, QoS in packet and non-packet networks. These has been a serious concern regarding scalability and convergence of information in large networks. This memo documents an optional OSPF capability to support TE only functionality. This OSPF TE Only option is to support existing and future Traffic Engineering extensions for packet and/or non-packet networks with out exchanging any hop-by-hop routing information. This is accomplished by exchanging T-bit option in OSPF Hello packets. This gives flexibility of supporting larger TE areas, increased scalability and improved convergence.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)