RSVP extensions for gmpls restoration signaling
draft-shimano-imajuku-gmpls-restoration-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Katsuhiro Shimano , Wataru Imajuku | ||
| Last updated | 2003-03-05 | ||
| 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
There are some efforts to categorize restoration schemes [Restoration-analysis]. We consider that pre-planned restoration has some advantages, for instance, enhancing the quickness to reduce downtime, extensions to recovery classes, risk management, and totally integrated distributed control. This document describes some requirements and extended properties for message objects on RSVP-TE [RSVP-GMPLS], LSR procedures, and pre-planned GMPLS restoration. We append a procedure to the recovery steps for working and restoration setup. Some objects are additionally required with respect to establishing working LSPs and reservation of restoration LSPs. This document shows that restoration activation is also needed and clarifies the required properties.
Authors
Katsuhiro Shimano
Wataru Imajuku
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)