Skip to main content

BIER Use Cases
draft-ietf-bier-use-cases-09

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
Authors Nagendra Kumar Nainar , Rajiv Asati , Mach Chen , Xiaohu Xu , Andrew Dolganow , Tony Przygienda , Arkadiy Gulko , Dom Robinson , Vishal Arya , Caitlin Bestler
Last updated 2019-08-04 (Latest revision 2019-01-31)
Replaces draft-kumar-bier-use-cases
RFC stream Internet Engineering Task Force (IETF)
Formats
Additional resources Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Other - see Comment Log
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain any multicast related per- flow state. BIER also does not require any explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a "Bit-Forwarding Ingress Router" (BFIR), and leaves the BIER domain at one or more "Bit-Forwarding Egress Routers" (BFERs). The BFIR router adds a BIER header to the packet. The BIER header contains a bit-string in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by setting the bits that correspond to those routers in the BIER header. This document describes some of the use cases for BIER.

Authors

Nagendra Kumar Nainar
Rajiv Asati
Mach Chen
Xiaohu Xu
Andrew Dolganow
Tony Przygienda
Arkadiy Gulko
Dom Robinson
Vishal Arya
Caitlin Bestler

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)