Optical Channel Concatenation -- Need and Requirements
draft-damle-optical-channel-concatenation-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rajendra Damle | ||
| Last updated | 2001-06-26 | ||
| 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 contribution identifies the need and requirements for concatenating optical channels to create multiple high bandwidth payload channels. To maximize the benefits of standardization, the concatenation methodolgy should be independant of framing protocols e.g., SONET, GFP, OCh etc.) as well as payload types (e.g., Packet, Cell, Byte Stream).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)