Considerations on the development of an Optical Control Plane
draft-freeland-octrl-cons-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daran Freeland | ||
| Last updated | 2001-01-12 | ||
| 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
Work on extensions to IP control protocols for reuse in the control plane of optical transport networks has now been underway for around a year in the MPLS and IPO groups. Recent discussions have however highlighted a lack of defined requirements that should be met by candidate protocols being considered for the optical control plane. Indeed, there have been several requests for carriers to submit their requirements. This draft provides one view of some (but by no means all) of these requirements. A protocol independent approach is taken, and the authors recommend that the design of any particular facet of an optical control plane should take into account the considerations made in this document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)