datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Multipoint Label Distribution Protocol In-Band Signaling in a VRF Context
draft-wijnands-l3vpn-mldp-vrf-in-band-signaling-01

Document type: Replaced Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-02-22 (latest revision 2012-10-17)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-l3vpn-mldp-vrf-in-band-signaling
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-wijnands-l3vpn-mldp-vrf-in-band-signaling-01.txt

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. Other documents specify the procedures for building such a hybrid MDT, using Protocol Independent Multicast (PIM) 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 to handle the case where the link connecting the two regions is a "Virtual Routing and Forwarding Table" (VRF) link, as defined in the "BGP IP/MPLS VPN" specifications. However, this document is primarily aimed at particular use cases where VRFs are used to support multicast applications other than Multicast VPN.

Authors

IJsbrand Wijnands <ice@cisco.com>
Paul Hitchen <paul.hitchen@bt.com>
Nicolai Leymann <n.leymann@telekom.de>
Wim Henderickx <wim.henderickx@alcatel-lucent.com>
arkadiy.gulko@thomsonreuters.com <arkadiy.gulko@thomsonreuters.com>

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