Extensions to RSVP-TE for Supporting Multiple Protection and Restoration Types
draft-suemura-gmpls-restoration-signaling-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yoshihiko Suemura | ||
| Last updated | 2002-02-27 | ||
| 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 proposes extensions to RSVP-TE for supporting multiple protection/restoration types (LSP Protection Types) in end-to-end protection/restoration. We propose the LSP Protection Type field to be defined in the Protection Object. Another aim of this document is prevention of an unintended connection for extra traffic when traffic from a failed working LSP is switched over to a backup LSP. We address this issue and propose a 3-way switchover signaling procedure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)