Bit Indexed Explicit Replication (bier) Internet Drafts


      
 BGP Extensions for BIER
 
 draft-ietf-bier-idr-extensions-10.txt
 Date: 13/06/2023
 Authors: Xiaohu Xu, Mach Chen, Keyur Patel, IJsbrand Wijnands, Tony Przygienda, Zhaohui Zhang
 Working Group: Bit Indexed Explicit Replication (bier)
Bit Index Explicit Replication (BIER) is a new multicast forwarding architecture which doesn't require an explicit tree-building protocol and doesn't require intermediate routers to maintain any multicast state. BIER is applicable in a multi-tenant data center network environment for efficient delivery of Broadcast, Unknown-unicast and Multicast (BUM) traffic while eliminating the need for maintaining a huge amount of multicast state in the underlay. This document describes BGP extensions for advertising the BIER-specific information.
 Operations,Administration and Maintenance (OAM) Requirements for Bit Index Explicit Replication (BIER) Layer
 
 draft-ietf-bier-oam-requirements-14.txt
 Date: 11/02/2024
 Authors: Greg Mirsky, Nagendra Nainar, Mach Chen, Santosh Pallagatti
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes a list of functional requirements toward Operations, Administration and Maintenance (OAM) toolset in Bit Index Explicit Replication (BIER) layer of a network.
 Path Maximum Transmission Unit Discovery (PMTUD) for Bit Index Explicit Replication (BIER) Layer
 
 draft-ietf-bier-path-mtu-discovery-16.txt
 Date: 05/11/2023
 Authors: Greg Mirsky, Tony Przygienda, Andrew Dolganow
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes Path Maximum Transmission Unit Discovery (PMTUD) in Bit Indexed Explicit Replication (BIER) layer.
 Performance Measurement (PM) with Marking Method in Bit Index Explicit Replication (BIER) Layer
 
 draft-ietf-bier-pmmm-oam-15.txt
 Date: 11/01/2024
 Authors: Greg Mirsky, Lianshu Zheng, Mach Chen, Giuseppe Fioccola
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes the applicability of a hybrid performance measurement method for packet loss and packet delay measurements of a multicast service through a Bit Index Explicit Replication domain.
 BIER Ping and Trace
 
 draft-ietf-bier-ping-13.txt
 Date: 27/01/2024
 Authors: Nagendra Nainar, Carlos Pignataro, Mach Chen, Greg Mirsky
 Working Group: Bit Indexed Explicit Replication (bier)
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 the mechanism and basic BIER OAM packet format that can be used to perform failure detection and isolation on the BIER data plane.
 BGP Link-State extensions for BIER
 
 draft-ietf-bier-bgp-ls-bier-ext-17.txt
 Date: 17/03/2024
 Authors: Ran Chen, Zhaohui Zhang, Vengada Govindan, IJsbrand Wijnands
 Working Group: Bit Indexed Explicit Replication (bier)
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 bitstring 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. BGP Link-State (BGP-LS) enables the collection of various topology informations from the network, and the topology informations are used by the controller to calculate the fowarding tables and then propagate them onto the BFRs(instead of having each node to calculate on its own) and that can be for both inter-as and intra-as situations. This document specifies extensions to the BGP Link-state address- family in order to advertise the BIER informations.
 EVPN BUM Using BIER
 
 draft-ietf-bier-evpn-14.txt
 Date: 02/01/2024
 Authors: Zhaohui Zhang, Tony Przygienda, Ali Sajassi, Jorge Rabadan
 Working Group: Bit Indexed Explicit Replication (bier)
This document specifies protocols and procedures for forwarding broadcast, unknown unicast, and multicast (BUM) traffic of Ethernet VPNs (EVPN) using Bit Index Explicit Replication (BIER).
 BIER Penultimate Hop Popping
 
 draft-ietf-bier-php-11.txt
 Date: 06/02/2024
 Authors: Zhaohui Zhang
 Working Group: Bit Indexed Explicit Replication (bier)
Bit Index Explicit Replication (BIER) can be used as provider tunnel for Multicast Virtual Private Network (MVPN), Global Table Multicast or Ethernet Virtual Private Network (EVPN). It is possible that not all routers in the provider network support BIER and there are various methods to handle BIER-incapable transit routers. However those methods assume the MVPN/EVPN Provider Edges (PEs) are BIER- capable. This document specifies a method to allow BIER-incapable routers to act as MVPN/EVPN PEs with BIER as the transport, by having the upstream BIER Forwarding Router (BFR) that is connected directly or indirectly via a tunnel to a BIER-incapable PE remove the BIER header and send the payload to the PE.
 A YANG data model for Tree Engineering for Bit Index Explicit Replication (BIER-TE)
 
 draft-ietf-bier-te-yang-06.txt
 Date: 23/01/2024
 Authors: Zheng Zhang, Cui(Linda) Wang, Ran Chen, fangwei hu, Mahesh Sivakumar, chenhuanan
 Working Group: Bit Indexed Explicit Replication (bier)
This document defines a YANG data model for Tree Engineering for Bit Index Explicit Replication (BIER-TE) configuration and operation.
 OSPFv3 Extensions for BIER
 
 draft-ietf-bier-ospfv3-extensions-07.txt
 Date: 01/12/2022
 Authors: Peter Psenak, Nagendra Nainar, IJsbrand Wijnands
 Working Group: Bit Indexed Explicit Replication (bier)
Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. BIER architecture uses MPLS or other encapsulation to steer the multicast traffic towards the receivers. This document describes the OSPFv3 protocol extensions required for BIER with MPLS encapsulation. Support for other encapsulation types is outside the scope of this document. The use of multiple encapsulation types is outside the scope of this document.
 BIER Prefix Redistribute
 
 draft-ietf-bier-prefix-redistribute-06.txt
 Date: 04/03/2024
 Authors: Zheng Zhang, Bo Wu, Zhaohui Zhang, IJsbrand Wijnands, Yisong Liu, Hooman Bidgoli
 Working Group: Bit Indexed Explicit Replication (bier)
This document defines a BIER proxy function to support a single BIER sub-domain over multiple underlay routing protocol regions (Autonomous Systems or IGP areas). A new BIER proxy range sub-TLV is defined to redistribute BIER BFR-id information across the routing regions.
 Tethering A BIER Router To A BIER incapable Router
 
 draft-ietf-bier-tether-05.txt
 Date: 16/02/2024
 Authors: Zhaohui Zhang, Nils Warnke, IJsbrand Wijnands, Daniel Awduche
 Working Group: Bit Indexed Explicit Replication (bier)
This document specifies optional procedures to optimize the handling of Bit Index Explicit Replication (BIER) incapable routers, by attaching (tethering) a BIER router to a BIER incapable router.
 M-LDP Signaling Through BIER Core
 
 draft-ietf-bier-mldp-signaling-over-bier-03.txt
 Date: 22/10/2023
 Authors: Hooman Bidgoli, Jayant Kotalwar, IJsbrand Wijnands, Mankamana Mishra, Zhaohui Zhang, Eddie Leyton
 Working Group: Bit Indexed Explicit Replication (bier)
Consider an end-to-end Multipoint LDP (mLDP) network, where it is desirable to deploy BIER in a segment of this network. It might be desirable to deploy BIER with minimal disruption to the mLDP network or a redesign of the network. This document describes a procedure needed for mLDP tunnels to be signaled over and stitched through a BIER core, allowing LDP routers to run traditional mLDP services through a BIER core.
 BIER BFD
 
 draft-ietf-bier-bfd-05.txt
 Date: 13/02/2024
 Authors: Quan Xiong, Greg Mirsky, fangwei hu, Chang Liu
 Working Group: Bit Indexed Explicit Replication (bier)
Point to multipoint (P2MP) BFD is designed to verify multipoint connectivity. This document specifies the application of P2MP BFD in BIER network.
 BIER (Bit Index Explicit Replication) Redundant Ingress Router Failover
 
 draft-ietf-bier-source-protection-05.txt
 Date: 08/10/2023
 Authors: Zheng Zhang, Greg Mirsky, Quan Xiong, Yisong Liu, Huanan Li
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes a failover in the Bit Index Explicit Replication domain with a redundant ingress router.
 Supporting BIER in IPv6 Networks (BIERin6)
 
 draft-ietf-bier-bierin6-09.txt
 Date: 17/03/2024
 Authors: Zheng Zhang, Zhaohui Zhang, IJsbrand Wijnands, Mankamana Mishra, Hooman Bidgoli, Gyan Mishra
 Working Group: Bit Indexed Explicit Replication (bier)
BIER is a multicast forwarding architecture that does not require per-flow state inside the network yet still provides optimal replication. This document describes how the existing BIER encapsulation specified in RFC 8296 works in a non-MPLS IPv6 network, which is referred to as BIERin6. Specifically, like in an IPv4 network, BIER can work over L2 links directly or over tunnels. In case of IPv6 tunneling, a new IP "Next Header" type is to be assigned for BIER.
 OSPF Extensions for BIER-TE
 
 draft-ietf-bier-te-ospf-10.txt
 Date: 01/02/2024
 Authors: Huaimo Chen, Mike McBride, Zheng Zhang, Aijun Wang, Gyan Mishra, Yanhe Fan
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes OSPFv2 and OSPFv3 extensions for distributing the BitPositions configured on a Bit-Forwarding Router (BFR) with MPLS and non-MPLS encapsulation for "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) in a BIER-TE domain.
 IS-IS Extensions for BIER-TE
 
 draft-ietf-bier-te-isis-09.txt
 Date: 07/01/2024
 Authors: Huaimo Chen, Mike McBride, Aijun Wang, Gyan Mishra, Yanhe Fan, Lei Liu, Xufeng Liu
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes IS-IS extensions for distributing the BitPositions configured on a Bit-Forwarding Router (BFR) in a "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) domain.
 OSPFv3 Extensions for BIER-TE
 
 draft-ietf-bier-te-ospfv3-07.txt
 Date: 06/01/2024
 Authors: Huaimo Chen, Mike McBride, Aijun Wang, Gyan Mishra, Yanhe Fan, Lei Liu, Xufeng Liu
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes OSPFv3 extensions for distributing the BitPositions configured on a Bit-Forwarding Router (BFR) in a "Bit Index Explicit Replication Traffic Engineering" (BIER-TE) domain.
 LSR Extensions for BIER non-MPLS Encapsulation
 
 draft-ietf-bier-lsr-non-mpls-extensions-03.txt
 Date: 07/02/2024
 Authors: Senthil Dhanaraj, Gang Yan, IJsbrand Wijnands, Peter Psenak, Zhaohui Zhang, Jingrong Xie
 Working Group: Bit Indexed Explicit Replication (bier)
Bit Index Explicit Replication (BIER) is an architecture that provides multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast related per-flow state. BIER can be supported in MPLS and non-MPLS networks. This document updates RFC8296 and specifies the required extensions to the IS-IS, OSPFv2 and OSPFv3 protocols for supporting BIER in non- MPLS networks using BIER non-MPLS encapsulation.
 Multicast/BIER As A Service
 
 draft-ietf-bier-multicast-as-a-service-03.txt
 Date: 06/02/2024
 Authors: Zhaohui Zhang, Eric Rosen, Daniel Awduche, Greg Shepherd, Zheng Zhang, Gyan Mishra
 Working Group: Bit Indexed Explicit Replication (bier)
This document describes a framework for providing multicast as a service via Bit Index Explicit Replication (BIER) [RFC7279], and specifies a few enhancements to [draft-ietf-bier-idr-extensions] [RFC8279] [RFC8401] [RFC8444] to enable multicast/BIER as a service.
 BIER Fast ReRoute
 
 draft-ietf-bier-frr-04.txt
 Date: 01/02/2024
 Authors: Huaimo Chen, Mike McBride, Steffen Lindner, Michael Menth, Aijun Wang, Gyan Mishra
 Working Group: Bit Indexed Explicit Replication (bier)
BIER is a scalable multicast overlay that utilizes a routing underlay, e.g., IP, to build up its Bit Index Forwarding Tables (BIFTs). This document proposes Fast Reroute for BIER (BIER-FRR). It protects BIER traffic after detecting the failure of a link or node in the core of a BIER domain until affected BIFT entries are recomputed after reconvergence of the routing underlay. BIER-FRR is applied locally at the point of local repair (PLR) and does not introduce any per-flow state. The document specifies nomenclature for BIER-FRR and gives examples for its integration in BIER forwarding. Furthermore, it presents operation modes for BIER-FRR. Link and node protection may be chosen as protection level. Moreover, the backup strategies tunnel-based BIER-FRR and LFA-based BIER-FRR are defined and compared.


data-group-menu-data-url="/group/groupmenu.json"> Skip to main content

Bit Indexed Explicit Replication (bier)

WG Name Bit Indexed Explicit Replication
Acronym bier
Area Routing Area (rtg)
State Active
Charter charter-ietf-bier-02 Approved
Document dependencies
Additional resources Wiki, Zulip Stream
Personnel Chairs Greg Shepherd, Tony Przygienda
Area Director Gunter Van de Velde
Delegates Jeff Tantsura, Zheng Zhang
Secretary Zheng Zhang
Mailing list Address bier@ietf.org
To subscribe https://www.ietf.org/mailman/listinfo/bier
Archive https://mailarchive.ietf.org/arch/browse/bier/
Chat Room address https://zulip.ietf.org/#narrow/stream/bier

Charter for Working Group

The BIER (Bit Index Explicit Replication) Working Group has defined
an architecture [RFC 8279] for multicast forwarding that uses an
encapsulation [RFC 8296] that can be used on MPLS or Ethernet transport.
The BIER-WG is now chartered to produce Standards Track RFCs, including
the status update for RFCs 8279 and 8296.

The BIER working group's original charter required the publication of an
Informational RFC describing the benefits, problems, and trade-offs for
using BIER instead of traditional multicast forwarding mechanisms as well
as an analysis of the impact and benefit of the BIER data-plane to the
overall Internet architecture. The WG did not produce this RFC, but the
goals of that milestone have nevertheless been reached; i.e., the industry
has demonstrated interest in deploying BIER and the trade-offs are now well
understood. Therefore, BIER is proceeding with work on the Standards Track.

The focus of the BIER-WG is on deployment: transition, partial deployments,
applicability and management.

First and primarily, the BIER-WG will complete its work on:

1) Transition Mechanisms and Partial Deployments: The WG will
describe how BIER can be introduced in existing multicast
networks to shift multicast delivery, either end-to-end or in part
of a network, from mechanisms such as PIM, ng-MVPN, etc. BIER
operation in networks where not all routers are BIER capable
or have other BIER support constraints should be addressed. How
to handle routers supporting BIER with different BitStringLengths
and encapsulations should be addressed. Each new mechanism should
include an applicability statement that clearly describes its
utility and distinctions from already standardized mechanisms.

2) Applicability Statements: The WG will continue to work on
documents describing how BIER can be applied, as has been done
for MVPN in draft-ietf-bier-mvpn. A document describing
applicability to EVPN should be published.

3) Use Case: The WG will produce one use-case document that clearly
articulates the potential benefits of BIER for different use-cases.

4) Manageability and OAM: The WG will describe how OAM will work in
a BIER domain and what simplifications BIER offers for managing the
multicast traffic. A strong preference will be given to extensions to
existing protocols.

5) Management models: The WG will work on YANG models to manage BIER.

6) Link-State Routing and BGP extensions: The BIER-WG has already
defined the basic information needed to set up the BIER
forwarding tables via advertisements in OSPFv2 and ISIS; the
extensions to OSPFv3 will be specified. Additional extensions
may be needed - for example, to support constraining the topology
on which a particular BIER sub-domain operates. Any necessary extensions
to the IGP will be specified by the WG as Standards Track, in
cooperation with the LSR WG. The BIER-WG shall also specify the
extensions to support BIER for BGP when used as an IGP (see RFC
7938) and to provide BIER-specific information in BGP-LS, in
cooperation with IDR.

The BIER-WG is additionally chartered to start Standards Track work on:
7) BIER in IPv6 : A mechanism to use BIER natively in IPv6 may be
standardized if coordinated with the 6MAN WG and with understood
applicability.
8) Forwarding Plane Mechanisms for BIER Traffic Engineering: definition of
how the new BIER forwarding plane structures (e.g. BIFT) can be used to
support engineered multicast trees. No control-plane work will be
done in BIER-WG.

The BIER-WG will serve as a forum to discuss how BIER can be applied.
The BIER-WG will coordinate and collaborate with other WGs as needed. Specific
expected interactions include:
* mpls on the associated MPLS-based OAM mechanisms,
* lsr on OSPF and ISIS extensions to flood BIER-related information,
* babel on Babel extensions to support BIER,
* bess and idr on BGP extensions to flood BIER-related information and the
applicability of existing BGP-based mechanisms for providing multicast group
membership information,
* pim and mboned on the applicability of and extensions to PIM, IGMP, and MLD to
support BIER operations and transition,
* pce on extensions to program BIER forwarding on the BFIRs,and
* teas on architecture and control-plane mechanisms to use BIER-TE forwarding mechanisms.

Milestones

Date Milestone Associated documents
Mar 2019 WGLC BIER-TE drafts
Nov 2018 Publish document(s) solidifying BAR/IPA complexity
Nov 2018 Progress YANG BIER drafts to WGLC
Nov 2018 Target feasibility and solution selection for IPv6 encap
Jul 2018 WGLC: draft-ietf-bier-evpn
Jul 2018 Publish as proposed standard: draft-ietf-bier-use-cases
Jul 2018 Publish as proposed standard:draft-ietf-bier-ping
Jul 2018 Publish as proposed standard: draft-ietf-bier-pmmm-oam
Jul 2018 Publish as proposed standard: draft-ietf-bier-path-mtu-discovery
Jul 2018 Publish as proposed standard: draft-ietf-bier-oam-requirements
Mar 2018 IETF 101 discuss and target mechanisms for BIER transition
Mar 2018 IETF 101 discuss BIER-TE documents adoption
Mar 2018 WG call for adoption: draft-hfa-bier-pim-signaling
Mar 2018 WGLC: draft-ietf-bier-bgp-ls-bier-ext
Mar 2018 WGLC: draft-ietf-bier-idr-extensions
Mar 2018 Shepherd/IESG queue: draft-ietf-bier-use-cases
Mar 2018 Shepherd/IESG queue: draft-ietf-bier-ping
Mar 2018 Shepherd/IESG queue: draft-ietf-bier-pmmm-oam
Mar 2018 Shepherd/IESG queue: draft-ietf-bier-path-mtu-discovery
Mar 2018 Shepherd/IESG queue: draft-ietf-bier-oam-requirements
Mar 2018 Published as proposed standard: draft-ietf-bier-isis-extensions
Mar 2018 Published as proposed standard: draft-ietf-bier-ospf-bier-extensions
Mar 2018 Published as proposed standard: draft-ietf-bier-mvpn