[Bier] RFC 8279 on Multicast Using Bit Index Explicit Replication (BIER)
rfc-editor@rfc-editor.org Mon, 20 November 2017 20:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F8D12EAC6; Mon, 20 Nov 2017 12:40:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 y70Vx3eh7YM7; Mon, 20 Nov 2017 12:40:51 -0800 (PST)
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 78544120713; Mon, 20 Nov 2017 12:40:30 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E4CECB81B04; Mon, 20 Nov 2017 12:40:27 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bier@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171120204027.E4CECB81B04@rfc-editor.org>
Date: Mon, 20 Nov 2017 12:40:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/N0cZByn_v5FiqHHAZIaUuz95gOo>
Subject: [Bier] RFC 8279 on Multicast Using Bit Index Explicit Replication (BIER)
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 20:40:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8279
Title: Multicast Using Bit Index Explicit
Replication (BIER)
Author: I. Wijnands, Ed.,
E. Rosen, Ed.,
A. Dolganow,
T. Przygienda,
S. Aldrin
Status: Experimental
Stream: IETF
Date: November 2017
Mailbox: ice@cisco.com,
erosen@juniper.net,
andrew.dolganow@nokia.com,
prz@juniper.net,
aldrin.ietf@gmail.com
Pages: 43
Characters: 97283
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bier-architecture-08.txt
URL: https://www.rfc-editor.org/info/rfc8279
DOI: 10.17487/RFC8279
This document specifies a new architecture for the forwarding of
multicast data packets. It provides optimal forwarding of multicast
packets through a "multicast domain". However, it does not require a
protocol for explicitly building multicast distribution trees, nor
does it require intermediate nodes to maintain any per-flow state.
This architecture is known as "Bit Index Explicit Replication"
(BIER). When a multicast data packet enters the domain, the ingress
router determines the set of egress routers to which the packet needs
to be sent. The ingress router then encapsulates the packet in a
BIER header. The BIER header contains a bit string in which each bit
represents exactly one egress router in the domain; to forward the
packet to a given set of egress routers, the bits corresponding to
those routers are set in the BIER header. The procedures for
forwarding a packet based on its BIER header are specified in this
document. Elimination of the per-flow state and the explicit
tree-building protocols results in a considerable simplification.
This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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