[bess] RFC 7740 on Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress Replication
rfc-editor@rfc-editor.org Sat, 23 January 2016 00:28 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3260C1B2E1B; Fri, 22 Jan 2016 16:28:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.909
X-Spam-Level:
X-Spam-Status: No, score=-105.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FS_REPLICA=0.994, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 aZGT2cPnor9L; Fri, 22 Jan 2016 16:28:47 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id AB66F1B2DEB; Fri, 22 Jan 2016 16:28:12 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 64E0F180206; Fri, 22 Jan 2016 16:26:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160123002653.64E0F180206@rfc-editor.org>
Date: Fri, 22 Jan 2016 16:26:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/oRJ1tsNisvYvb9Nchtq2SS_ky_U>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
Subject: [bess] RFC 7740 on Simulating Partial Mesh of Multipoint-to-Multipoint (MP2MP) Provider Tunnels with Ingress Replication
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2016 00:28:49 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7740
Title: Simulating Partial Mesh of Multipoint-to-Multipoint
(MP2MP) Provider Tunnels with Ingress Replication
Author: Z. Zhang, Y. Rekhter, A. Dolganow
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: zzhang@juniper.net,
andrew.dolganow@alcatel-lucent.com
Pages: 8
Characters: 18252
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bess-mvpn-bidir-ingress-replication-04.txt
URL: https://www.rfc-editor.org/info/rfc7740
DOI: http://dx.doi.org/10.17487/RFC7740
RFC 6513 ("Multicast in MPLS/BGP IP VPNs") describes a method to
support bidirectional customer multicast flows using a partial mesh
of Multipoint-to-Multipoint (MP2MP) tunnels. This document specifies
how a partial mesh of MP2MP tunnels can be simulated using Ingress
Replication. This solution enables a service provider to use Ingress
Replication to offer transparent bidirectional multicast service to
its VPN customers.
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