Link Viability Constraints Requirements for GMPLS-enabled Networks
draft-ashwood-ccamp-gmpls-constraint-reqts-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Don Fedyk | ||
| Last updated | 2005-07-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
This draft describes requirements for connecting a pure photonic sub-domain to a GMPLS-based Label Switch Router. One of the main requirements is to avoid advertising all the physical properties of the underlying optical hardware while still peering with standard GMPLS. This draft discusses the requirements for abstracting the optical topology and the implications of various abstract models. This draft discusses possible extensions to [OSPF-TE] [GMPLS- Routing] and [ISIS-TE] for use by GMPLS networks that require additional constraints to be considered in the computation of viable paths.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)