Bit Index Explicit Replication (BIER) Ping and Trace
draft-ietf-bier-ping-21

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-ping@ietf.org, gunter@vandevelde.cc, mankamana mishra <mankamis@cisco.com>, mankamis@cisco.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'BIER Ping and Trace' to Proposed Standard (draft-ietf-bier-ping-16.txt)

The IESG has approved the following document:
- 'BIER Ping and Trace'
  (draft-ietf-bier-ping-16.txt) as Proposed Standard

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 Ketan
Talaulikar.

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

Ballot Text

Technical Summary

   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.

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? 

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?

Yes, some part of it has been implemented by vendors who support BIER in some form.

Personnel

   The Document Shepherd for this document is Mankamana Prasad Mishra. The
   Responsible Area Director is Gunter Van de Velde.

IANA Note

  WG authors need to respond to the IANA review questions

RFC Editor Note