RFC 8556 on Multicast VPN Using Bit Index Explicit Replication (BIER)
rfc-editor@rfc-editor.org Mon, 08 April 2019 21:24 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 E6070120089; Mon, 8 Apr 2019 14:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 9-698eGUBG4w; Mon, 8 Apr 2019 14:23:59 -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 5A5AA120013; Mon, 8 Apr 2019 14:23:59 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3F3E5B81DFE; Mon, 8 Apr 2019 14:23:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8556 on Multicast VPN Using Bit Index Explicit Replication (BIER)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bier@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190408212356.3F3E5B81DFE@rfc-editor.org>
Date: Mon, 08 Apr 2019 14:23:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/fGDVg2mTy1V0efABTk8IGDzOkQ0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Mon, 08 Apr 2019 21:24:01 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8556 Title: Multicast VPN Using Bit Index Explicit Replication (BIER) Author: E. Rosen, Ed., M. Sivakumar, T. Przygienda, S. Aldrin, A. Dolganow Status: Standards Track Stream: IETF Date: April 2019 Mailbox: erosen52@gmail.com, sivakumar.mahesh@gmail.com, prz@juniper.net, aldrin.ietf@gmail.com, andrew.dolganow@nokia.com Pages: 17 Characters: 38070 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bier-mvpn-11.txt URL: https://www.rfc-editor.org/info/rfc8556 DOI: 10.17487/RFC8556 The Multicast Virtual Private Network (MVPN) specifications require the use of multicast tunnels ("P-tunnels") that traverse a service provider's backbone network. The P-tunnels are used for carrying multicast traffic across the backbone. A variety of P-tunnel types are supported. Bit Index Explicit Replication (BIER) is a new architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. This document specifies the protocol and procedures that allow MVPN to use BIER as the method of carrying multicast traffic over a service provider's backbone network. This document is a product of the Bit Indexed Explicit Replication 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