Reoptimization of MPLS Traffic Engineering loosely routed LSP
draft-vasseur-ccamp-loose-path-reopt-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | JP Vasseur , Yuichi Ikejiri | ||
| Last updated | 2011-01-10 (Latest revision 2004-07-09) | ||
| Replaced by | RFC 4736 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-ccamp-loose-path-reopt | |
| 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 defines a mechanism for the reoptimization of loosely routed MPLS Traffic Engineering LSPs. A loosely routed LSP follows a path specified as a combination of strict and loose hop(s) that contains at least one loose hop and zero or more strict hop(s).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)