Last Call: <draft-ietf-bess-mvpn-bidir-03.txt> (MVPN: Using Bidirectional P-Tunnels) to Proposed Standard

The IESG <> Wed, 04 March 2015 14:07 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 7BB411A1A00; Wed, 4 Mar 2015 06:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id i-l-edTYjM3N; Wed, 4 Mar 2015 06:07:12 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 0E8EE1A1A2D; Wed, 4 Mar 2015 06:07:12 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-bess-mvpn-bidir-03.txt> (MVPN: Using Bidirectional P-Tunnels) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.12.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 04 Mar 2015 06:07:12 -0800
Archived-At: <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Mar 2015 14:07:13 -0000

The IESG has received a request from the BGP Enabled Services WG (bess)
to consider the following document:
- 'MVPN: Using Bidirectional P-Tunnels'
  <draft-ietf-bess-mvpn-bidir-03.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2015-03-18. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   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, 6514 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.

The file can be obtained via

IESG discussion can be tracked via

The following IPR Declarations may be related to this I-D: