Offline Traffic Engineering in a Large ISP Setting
draft-liljenstolpe-tewg-cwbcp-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Christopher Liljenstolpe | ||
| Last updated | 2002-12-11 | ||
| 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 is in response to a request made by the Traffic Engineering Working Group for a set of traffic engineering practices from a sample of the ISP engineering community. It reflects the current traffic engineering principles and practices that Cable & Wireless uses for its global 'packet' networks (including IP and MPLS) at the time of publication. It will also identify some of the history that has lead to the specific principles and practices as well as some of the trade-offs between these methods and other possible approaches. It is not intended to be a detailed engineering guide or 'how-to' document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)