CR-LDP Extensions for Interworking with RSVP-TE
draft-wright-mpls-er-interwork-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sandra Ballarte , Tim Pearson , Gregory Wright | ||
| Last updated | 2000-03-14 | ||
| 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
The development of two explicit routing protocols RSVP-TE[RSVP-TE] and CR-LDP[CR-LDP] within MPLS has created the need to allow interworking between the two MPLS. Explict routed (ER) label switch paths do not have a prior knowledge of the ER signaling method in use within the various links comprising a domain. In an integrated environment an ER path may crisscross between RSVP-TE and CR-LDP nodes numerous times. This document describes the procedures for the establishment of an RSVP-TE originated LSP transiting or terminating within a CR-LDP domain and the procedures for the establishment of a CR-LDP originated LSP terminating within an RSVP-TE domain.
Authors
Sandra Ballarte
Tim Pearson
Gregory Wright
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)