Skip to main content

Telechat Review of draft-ietf-bier-ping-16
review-ietf-bier-ping-16-opsdir-telechat-liu-2025-11-12-01

Request Review of draft-ietf-bier-ping
Requested revision No specific revision (document currently at 21)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2025-11-10
Requested 2025-10-14
Requested by Mohamed Boucadair
Authors Nagendra Kumar Nainar , Carlos Pignataro , Mach Chen , Greg Mirsky
I-D last updated 2026-03-30 (Latest revision 2026-03-30)
Completed reviews Intdir Early review of -08 by Brian Haberman (diff)
Secdir Early review of -08 by David Mandelberg (diff)
Rtgdir Early review of -14 by Dhruv Dhody (diff)
Secdir IETF Last Call review of -16 by David Mandelberg (diff)
Tsvart IETF Last Call review of -16 by Marcus Ihlar (diff)
Genart IETF Last Call review of -16 by Roni Even (diff)
Opsdir Telechat review of -16 by Will (Shucheng) LIU (diff)
Intdir Telechat review of -16 by Brian Haberman (diff)
Assignment Reviewer Will (Shucheng) LIU
State Completed
Request Telechat review on draft-ietf-bier-ping by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/FBpcezi0rzthfpHjxrjigQCyoo8
Reviewed revision 16 (document currently at 21)
Result Has nits
Completed 2025-11-12
review-ietf-bier-ping-16-opsdir-telechat-liu-2025-11-12-01
Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this
Internet-Draft. The scope of the document is clear and it is almost ready. It
defines the BIER OAM packet format and the related mechanisms.

- Document: draft-ietf-bier-ping

- Reviewer: Will LIU

- Review Date: 12/11/2025

---

## Summary

- Has Nits: This document is basically ready for publication but has nits that
should be considered prior to publication.

---

I have few comments:

- In section 3.1, it is mentioned that Hybrid OAM can also be used. I suggest
to clarify this point. Maybe, it can be highlighted in the introduction and
explain which OAM methods (Active, Hybrid, Passive) can be enabled with BIER
OAM.

- I would define the BIER Echo Request/Reply message format in a separate
section to improve readability. Maybe a subsection of section 3.1 could be ok.

- Section 4 covers ping and traceroute operations. Therefore, I suggest to be
more specific and revise the title of the section accordingly.