Skip to main content

Multipoint Label Distribution Protocol In-Band Signaling in a VPN Context
draft-wijnands-mpls-mldp-vpn-in-band-signaling-00

Document Type Replaced Internet-Draft (individual)
Authors IJsbrand Wijnands , Nicolai Leymann , Paul Hitchen , Wim Henderickx
Last updated 2013-09-10 (Latest revision 2011-10-07)
Replaced by draft-wijnands-l3vpn-mldp-vrf-in-band-signaling
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-wijnands-l3vpn-mldp-vrf-in-band-signaling
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

Sometimes an IP multicast distribution tree (MDT) traverses both MPLS-enabled and non-MPLS-enabled regions of a network. Typically the MDT begins and ends in non-MPLS regions, but travels through an MPLS region. In such cases, it can be useful to begin building the MDT as a pure IP MDT, then convert it to an MPLS Multipoint LSP (Label Switched Path) when it enters an MPLS-enabled region, and then convert it back to a pure IP MDT when it enters a non-MPLS-enabled region. [I-D.ietf-mpls-mldp-in-band-signaling] specifies the procedures for building such a hybrid MDT, using Protocol Independent Multicast (PIM) as the control protocol in the non-MPLS region of the network, and using Multipoint Extensions to Label Distribution Protocol (mLDP) in the MPLS region. This document extends those procedures so that they will work when the links between the MPLS and non-MPLS regions are [RFC4364] interfaces. While these procedures do not provide a good general multicast VPN solution, they are useful in certain specific situations.

Authors

IJsbrand Wijnands
Nicolai Leymann
Paul Hitchen
Wim Henderickx

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