BIER -- "Bit Indexed Explicit Replication discussion list"

 

About BIER
English (USA)

There is a need to simplify network operations for multicast services. Current solutions require a tree-building control plane, which maintains end-to-end tree state per flow, impacting router state capacity and network convergence times. Multi-point tree building protocols are often considered complex to deploy and debug and include mechanics from legacy use-cases and/or assumptions which may no longer apply to the current deployments. When multicast services are transiting a provider network through an overlay, the core network has a choice to either aggregate customer state into a minimum set of core states resulting in flooding traffic to unwanted network end-points, or to map per-customer, per-flow tree state directly into the provider core state amplifying the network-wide state problem.

This mailing list is for a discussion of this topic and the coordination of a potential BoF on the subject of a new architecture for the forwarding of multicast data packets. The goal is to provide optimal forwarding of multicast packets through a "multicast domain" without requiring an explicit tree-building protocol, nor requiring 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. Elimination of the per-flow state and the explicit tree-building protocols results in a considerable simplification.
BIER may require extensions to IGPs and BGP in addition to the architecture and encapsulation descriptions. For this reason it is expected that BIER will require a dedicated working group which will focus on the overall architecture and shepherd the work toward consensus in the various other location where work is needed.

To see the collection of prior postings to the list, visit the BIER Archives or BIER MHonArc Archives.

Using BIER
To post a message to all the list members, send email to bier@ietf.org.

You can subscribe to the list, or change your existing subscription, in the sections below.

Subscribing to BIER

Subscribe to BIER by filling out the following form. You will be sent email requesting confirmation, to prevent others from gratuitously subscribing you. This is a private list, which means that the list of members is not available to non-members.

    Your email address:  
    Your name (optional):  
    You may enter a privacy password below. This provides only mild security, but should prevent others from messing with your subscription. Do not use a valuable password as it will occasionally be emailed back to you in cleartext.

    If you choose not to enter a password, one will be automatically generated for you, and it will be sent to you once you've confirmed your subscription. You can always request a mail-back of your password when you edit your personal options. Once a month, your password will be emailed to you as a reminder.
    Pick a password:  
    Reenter password to confirm:  
    Which language do you prefer to display your messages? English (USA)  
    Would you like to receive list mail batched in a daily digest? No Yes
BIER Subscribers
(The subscribers list is only available to the list members.)

Enter your address and password to visit the subscribers list:

Address: Password:   

To unsubscribe from BIER, get a password reminder, or change your subscription options enter your subscription email address:

If you leave the field blank, you will be prompted for your email address


BIER list run by gjshep at gmail.com
BIER administrative interface (requires authorization)
Overview of all ietf.org mailing lists

Delivered by Mailman
version 2.1.22
Python Powered GNU's Not Unix