Level3 MPLS Protocol Architecture
draft-springer-te-level3bcp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vanessa Springer , Craig Pierantozzi | ||
| Last updated | 2000-08-29 | ||
| 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 paper discusses Traffic Engineering with Multi-Protocol Label Switching in the Level3 network. A brief overview of traffic engineering is given followed by constraints affecting Level3's design. The approach Level3 will use, which is LDP edge and an RSVP-TE core, is presented. Several architectures were considered when deciding upon a design. These methods are discussed as well as the reasons they were ultimately refuted.
Authors
Vanessa Springer
Craig Pierantozzi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)