Upstream Label Set Support in RSVP-TE extensions
draft-oki-ccamp-upstream-labelset-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eiji Oki | ||
| Last updated | 2002-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 document describes extensions to GMPLS RSVP-TE signaling required to support a upstream label set when a bidirectional path is set up. In the existing drafts on GMPLS RSVP-TE signaling, a upstream label for the upstream path has to be reserved at an intermediate node before Path message is transmitted to the next-hop node. On the other hand, a label set that includes one or more labels for the downstream path is carried by Path message and then Resv message reserves a label at each interme- diate node on the route or a source node. This document proposes the way to support the upstream label set as is the case of the Label Set for downstream.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)