Use of IGP Metric as a second TE Metric
draft-lefaucheur-te-metric-igp-01
Document | Type |
Expired Internet-Draft
(tewg WG)
Expired & archived
|
|
---|---|---|---|
Author | François Le Faucheur | ||
Last updated | 2001-11-13 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
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 draft describes a common practice on how the existing IGP Metric can be used as an alternative metric to the TE Metric for Constraint Based Routing of MPLS TE Tunnels. This effectively results in the ability to perform Constraint Based Routing with optimization of one metric (e.g. link bandwidth) for some TE Tunnels (e.g. Data Trunks) while optimizing another metric (e.g. propagation delay) for some other TE Tunnels with different requirements (e.g. Voice Trunks). No protocol extensions or modifications are required. This text documents current router implementations and deployment practices.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)