RFC 7582 on Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels
rfc-editor@rfc-editor.org Wed, 15 July 2015 05:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88A491A7014; Tue, 14 Jul 2015 22:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s12IU6qVe37F; Tue, 14 Jul 2015 22:51:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 46D2D1A7022; Tue, 14 Jul 2015 22:51:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 66ACB180470; Tue, 14 Jul 2015 22:48:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7582 on Multicast Virtual Private Network (MVPN): Using Bidirectional P-Tunnels
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150715054816.66ACB180470@rfc-editor.org>
Date: Tue, 14 Jul 2015 22:48:16 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/ECuTqJlB9RWjudbpB1UJAaF3RPo>
Cc: bess@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2015 05:51:59 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7582
Title: Multicast Virtual Private Network (MVPN):
Using Bidirectional P-Tunnels
Author: E. Rosen, IJ. Wijnands,
Y. Cai, A. Boers
Status: Standards Track
Stream: IETF
Date: July 2015
Mailbox: erosen@juniper.net,
ice@cisco.com,
yiqunc@microsoft.com,
arjen@boers.com
Pages: 34
Characters: 79244
Updates: RFC 6513, RFC 6514, RFC 6625
I-D Tag: draft-ietf-bess-mvpn-bidir-04.txt
URL: https://www.rfc-editor.org/info/rfc7582
DOI: http://dx.doi.org/10.17487/RFC7582
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.
This document is a product of the BGP Enabled Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC