Skip to main content

Using mLDP through a Backbone where there is no Route to the Root
draft-wijnands-mpls-mldp-recurs-fec-01

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors IJsbrand Wijnands , Eric C. Rosen , Maria Napierala , Nicolai Leymann
Last updated 2010-04-16
Replaced by draft-ietf-mpls-mldp-recurs-fec
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mpls-mldp-recurs-fec
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 control protocol used for constructing Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths ("MP LSPs") contains a field that identifies the address of a "root node". Intermediate nodes are expected to be able to look up that address in their routing tables. However, if the route to the root node is a BGP route, and the intermediate nodes are part of a BGP-free core, this is not possible. This document specifies procedures which enable a MP LSP to be constructed through a BGP-free core. In these procedures, the root node address is temporarily replaced by an address which is known to the intermediate nodes.

Authors

IJsbrand Wijnands
Eric C. Rosen
Maria Napierala
Nicolai Leymann

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