Optical Network Failure Recovery Requirements
draft-czezowski-optical-recovery-reqs-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Peter Czezowski , Toshio Soumiya , Richard Rabbat | ||
Last updated | 2003-03-04 | ||
Replaced by | draft-rabbat-optical-recovery-reqs | ||
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-rabbat-optical-recovery-reqs | |
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 draft describes requirements for control plane-based recovery from data plane failures in pre-OTN networks. pre-OTN networks are transport networks that have a GMPLS-based control plane and various transport plane technologies (such as Optical Cross Connects and Optical Add/Drop Multiplexers, etc.) An important feature of these networks is recovery from failures - using either a protection or restoration scheme. Achieving recovery under strict time constraints is a difficult problem. Shared mesh-based recovery is especially desirable for reducing spare capacity ratios and achieving flexible recovery scenarios. Following a brief overview and consideration of the requirements, they are presented in an itemized list in section 3.4 of this document.
Authors
Peter Czezowski
Toshio Soumiya
Richard Rabbat
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)