PathErr Message Triggered MPLS and GMPLS LSP Reroute
draft-berger-mpls-gmpls-lsp-reroute-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lou Berger , Dimitri Papadimitriou , JP Vasseur | ||
| Last updated | 2010-01-05 (Latest revision 2008-07-07) | ||
| Replaced by | draft-ietf-mpls-gmpls-lsp-reroute | ||
| 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-mpls-gmpls-lsp-reroute | |
| 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 describes how Resource ReserVation Protocol (RSVP) PathErr Messages may be used to trigger rerouting of Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) without first removing LSP state or resources. Such LSP rerouting may desirable in a number of cases including, for example, soft-preemption and graceful shutdown. This document describes the usage of existing Standards Track mechanisms and defines no new formats or mechanisms. It relies on mechanisms already defined as part of RSVP-TE and simply describes a sequence of actions to be executed.
Authors
Lou Berger
Dimitri Papadimitriou
JP Vasseur
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)