OSPF Tunnel capability TLVs
draft-eng-nalawade-ospf-tunnel-cap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sandy Eng | ||
| Last updated | 2003-10-22 | ||
| 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
As increasing number of tunnels are deployed in a Provider core, there is a need for improving the efficiency and ease of tunnel establishment. OSPF running as the IGP in a Provider core, can act as the signalling agent for the Tunnel endpoints. OSPF can carry tunnel endpoint information in the intra-AS scope, easing BGP of the extra burden of signalling within the core.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)