Explicit Route Support in MPLS
draft-davie-mpls-explicit-routes-00

Document Type Expired Internet-Draft (individual)
Last updated 1997-11-26
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-davie-mpls-explicit-routes-00.txt

Abstract

We define an `explicit route' as a route which is explicitly specified as a sequence of hops rather than being determined solely by conventional routing algorithms on a hop by hop basis. Using the explicit route object proposed for use in RSVP [1] and the ability to bind MPLS labels to RSVP flows [2] we describe how explicit routes may be set up in an MPLS environment. The resulting label switched paths may have associated resource reservations, or may be purely best effort.

Authors

Bruce Davie (bsd@cisco.com)
Tony Li (tli@cisco.com)
Yakov Rekhter (yakov@juniper.net)
Eric Rosen (erosen@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)