RFC 7988 on Ingress Replication Tunnels in Multicast VPN
rfc-editor@rfc-editor.org Fri, 07 October 2016 04:47 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA0712944C; Thu, 6 Oct 2016 21:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Level:
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 l09SPfCe2Vqs; Thu, 6 Oct 2016 21:47:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0DAF129506; Thu, 6 Oct 2016 21:47:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D8DC2B8111A; Thu, 6 Oct 2016 21:47:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7988 on Ingress Replication Tunnels in Multicast VPN
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161007044742.D8DC2B8111A@rfc-editor.org>
Date: Thu, 06 Oct 2016 21:47:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HwF_Zdf8IVJNhLKtm-mWbR3z_M4>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 07 Oct 2016 04:47:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7988
Title: Ingress Replication Tunnels in Multicast VPN
Author: E. Rosen, Ed.,
K. Subramanian,
Z. Zhang
Status: Standards Track
Stream: IETF
Date: October 2016
Mailbox: erosen@juniper.net,
karthik@sproute.com,
zzhang@juniper.net
Pages: 23
Characters: 55979
Updates: RFC 6513, RFC 6514
I-D Tag: draft-ietf-bess-ir-05.txt
URL: https://www.rfc-editor.org/info/rfc7988
DOI: http://dx.doi.org/10.17487/RFC7988
RFCs 6513, 6514, and other RFCs describe procedures by which a Service
Provider may offer Multicast VPN (MVPN) service to its customers.
These procedures create point-to-multipoint (P2MP) or
multipoint-to-multipoint (MP2MP) trees across the Service Provider's
backbone. One type of P2MP tree that may be used is known as an
"Ingress Replication (IR) tunnel". In an IR tunnel, a parent node
need not be directly connected to its child nodes. When a parent node
has to send a multicast data packet to its n child nodes, it does not
use Layer 2 multicast, IP multicast, or MPLS multicast to do so.
Rather, it makes n individual copies, and then unicasts each copy,
through an IP or MPLS unicast tunnel, to exactly one child node.
While the prior MVPN specifications allow the use of IR tunnels, those
specifications are not always very clear or explicit about how the
MVPN protocol elements and procedures are applied to IR tunnels. This
document updates RFCs 6513 and 6514 by adding additional details that
are specific to the use of IR 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/retrieve/bulk
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