Last Call: <draft-ietf-bier-ping-16.txt> (BIER Ping and Trace) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 03 October 2025 13:36 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-bier-ping-16.txt> (BIER Ping and Trace) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <175949859129.3122999.8661237833876062626@dt-datatracker-6c6cdf7f94-h6rnn>
Date: Fri, 03 Oct 2025 06:36:31 -0700
Message-ID-Hash: VX5TIZVHWSBWQX4E7UNVCPYOARMIXEQW
CC: bier-chairs@ietf.org, bier@ietf.org, draft-ietf-bier-ping@ietf.org, gunter@vandevelde.cc, mankamis@cisco.com
Reply-To: last-call@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0ZxX4fOwHdbdUZkxMsOKgNemIk8>

The IESG has received a request from the Bit Indexed Explicit Replication WG
(bier) to consider the following document: - 'BIER Ping and Trace'
  <draft-ietf-bier-ping-16.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2025-10-17. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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 the mechanism and basic BIER OAM packet
   format that can be used to perform failure detection and isolation on
   the BIER data plane.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bier-ping/


The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/3692/

Last Call: <draft-ietf-bier-ping-16.txt> (BIER Pi… The IESG