Extensions to GMPLS RSVP-TE for Bidirectional Lightpath with the Same Wavelength
draft-xu-rsvpte-bidir-wave-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Sugang Xu , Hiroaki Harai , Daniel King | ||
Last updated | 2007-11-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
For bidirectional lightpaths provisioning, in the case of optical nodes that do not support wavelength conversion, it would be necessary to use the same wavelength along the route on each direction. In certain optical network scenarios, the use of the same wavelength on both directions would be advantageous. For instance, some ROADMs may add/drop the same wavelength simultaneously. In other cases, the users' optical end nodes are equipped with fixed-wavelength transponders. This document describes extensions to RSVP-TE signaling for bidirectional wavelength lightpaths that require the same wavelength on both directions. By using an LSP_ATTRIBUTES object defined in [RFC4420], the extensions enable the new type lightpaths to support the low cost configuration at users' optical end nodes.
Authors
Sugang Xu
Hiroaki Harai
Daniel King
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)