A Framework for Fast Reroute with Bit Index Explicit Replication (BIER-FRR)
draft-ietf-bier-frr-11

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, bier-chairs@ietf.org, bier@ietf.org, draft-ietf-bier-frr@ietf.org, gunter@vandevelde.cc, rfc-editor@rfc-editor.org, zhang.zheng@zte.com.cn
Subject: Document Action: 'BIER Fast ReRoute' to Informational RFC (draft-ietf-bier-frr-06.txt)

The IESG has approved the following document:
- 'BIER Fast ReRoute'
  (draft-ietf-bier-frr-06.txt) as Informational RFC

This document is the product of the Bit Indexed Explicit Replication Working
Group.

The IESG contact persons are Gunter Van de Velde, Jim Guichard and John
Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-frr/

Ballot Text

Technical Summary

   This document describes a mechanism for Fast Reroute (FRR) in Bit
   Index Explicit Replication (BIER) networks.  The proposed solution
   enhances the resiliency of BIER by providing a method to quickly
   reroute traffic in the event of a link or node failure, thereby
   minimizing packet loss and service disruption.  The document details
   the procedures for detecting failures and selecting backup paths
   within the BIER domain, ensuring that multicast traffic continues to
   reach its intended destinations without requiring per-flow state or
   additional signaling.  This FRR mechanism is designed to integrate
   seamlessly with existing BIER operations, offering a robust solution
   for improving network reliability.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

There was no controversy. Overall WG consensus on the usefulness of the work

Document Quality

   Are there existing implementations of the protocol?  Have a 
   significant number of vendors indicated their plan to
   implement the specification?  Are there any reviewers that
   merit special mention as having done a thorough review,
   e.g., one that resulted in important changes or a
   conclusion that the document had no substantive issues?  If
   there was a MIB Doctor, Media Type, or other Expert Review,
   what was its course (briefly)?  In the case of a Media Type
   Review, on what date was the request posted?

Informational document.
An implementation of Tunnel-Based BIER-FRR has been documented in
https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=9361548
The other parts have no implementations.

Personnel

   The Document Shepherd for this document is Zheng Zhang. The Responsible
   Area Director is Gunter Van de Velde.

RFC Editor Note