MVPN: Using Bidirectional P-Tunnels

Document Type Replaced Internet-Draft (bess WG)
Last updated 2014-10-22 (latest revision 2014-06-02)
Replaces draft-rosen-l3vpn-mvpn-bidir
Replaced by draft-ietf-bess-mvpn-bidir
Stream IETF
Intended RFC status Proposed Standard
Expired & archived
plain text pdf html
Stream WG state WG Consensus: Waiting for Write-Up Mar 2014 Dec 2014
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2015-07-21)
IESG IESG state Replaced by draft-ietf-bess-mvpn-bidir
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


A set of prior RFCs specify procedures for supporting multicast in BGP/MPLS IP VPNs. These procedures allow customer multicast data to travel across a service provider's backbone network through a set of multicast tunnels. The tunnels are advertised in certain BGP multicast "auto-discovery" routes, by means of a BGP attribute known as the "Provider Multicast Service Interface (PMSI) Tunnel attribute". Encodings have been defined that allow the PMSI Tunnel attribute to identify bidirectional (multipoint-to-multipoint) multicast distribution trees. However, the prior RFCs do not provide all the necessary procedures for using bidirectional tunnels to support multicast VPNs. This document updates RFCs 6513 and 6625 by specifying those procedures. In particular, it specifies the procedures for assigning customer multicast flows (unidirectional or bidirectional) to specific bidirectional tunnels in the provider backbone, for advertising such assignments, and for determining which flows have been assigned to which tunnels.


Eric Rosen (
IJsbrand Wijnands (
Yiqun Cai (
Arjen Boers (

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