Requirements for Protecting Control Channels in GMPLS
draft-kim-ccamp-cc-protection-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yong-Hwon Kim | ||
| Last updated | 2003-10-28 | ||
| 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 describes base requirements for protecting control channels(CCs) for GMPLS. It provides guidelines needed in order to switchover an active CC to one of standby CCs when a failure occurs about the active CC. It defines terminology, base concepts, necessities, and considerations that should be noted primarily in order to complete the mechanism of CC protection. This document describes requirements for providing resilience capabilities of control plane in GMPLS whose control channel can be separated from the data channel. This contribution, as a document that proposes the necessity about resilience of control plane like that of transport plane, handles related terminologies, base concepts, possible configurations, necessities and requirements, additional considerations including the relationship with other protocol such as LMP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)