Advertising a Router's Local Addresses in OSPF TE Extensions
draft-raggarwa-ospf-te-node-addr-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rahul Aggarwal , Kireeti Kompella | ||
| Last updated | 2003-10-07 | ||
| 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
This document describes procedures that enhance OSPF Traffic Engineering (TE) extensions for advertising a router's local addresses. This is needed to enable other routers in a network to compute traffic engineered MPLS LSPs to a given router's local addresses. Currently, the only addresses belonging to a router that are advertised in TE LSAs are the router's local addresses on links enabled for TE, and the Router ID.
Authors
Rahul Aggarwal
Kireeti Kompella
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)