Skip to main content

Early Review of draft-ietf-rtgwg-vrrp-bfd-p2p-03
review-ietf-rtgwg-vrrp-bfd-p2p-03-opsdir-early-p-2026-07-09-00

Request Review of draft-ietf-rtgwg-vrrp-bfd-p2p
Requested revision No specific revision (document currently at 05)
Type Early Review
Team Ops Directorate (opsdir)
Deadline 2026-07-10
Requested 2026-06-19
Requested by Yingzhen Qu
Authors Nitish Gupta , Aditya Dogra , Colin Docherty , Jeff Tantsura
I-D last updated 2026-08-11 (Latest revision 2026-08-11)
Completed reviews Opsdir Early review of -03 by Michael P (diff)
Rtgdir Early review of -03 by Zhaohui (Jeffrey) Zhang (diff)
Secdir Early review of -03 by Paul Wouters (diff)
Comments
Preparation for WGLC.
Assignment Reviewer Michael P
State Completed
Request Early review on draft-ietf-rtgwg-vrrp-bfd-p2p by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/gC_sGdTciHUUGNc_XymPTK89kQc
Reviewed revision 03 (document currently at 05)
Result Has nits
Completed 2026-07-09
review-ietf-rtgwg-vrrp-bfd-p2p-03-opsdir-early-p-2026-07-09-00
Hi,

I have been selected as the Operational Directorate (opsdir) reviewer for this
Internet-Draft.

The Operational Directorate reviews all operational and management-related
Internet-Drafts to ensure alignment with operational best practices and that
adequate operational considerations are covered.

A complete set of _"Guidelines for Considering Operations and Management in
IETF Specifications"_ can be found at
https://datatracker.ietf.org/doc/draft-ietf-opsawg-rfc5706bis/.

While these comments are primarily for the Operations and Management Area
Directors (Ops ADs), the authors should consider them alongside other feedback
received.

- Document: draft-ietf-rtgwg-vrrp-bfd-p2p-03

- Reviewer: Michael P

- Review Date: 2026-07-09

- Intended Status: Standards Track

---

## Summary

Choose one:

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

---

Thank you for the effort that has gone into this document and for including an
Operational Considerations section. This document is well written, with samples
being particularly useful to readers and explains the motivation and solution
well.

A minor suggestion is to include brief definitions, similar to the introduction
of RFC 9568, to help new readers.

Similarly, while it contains an Operational Considerations, I'd suggest
slightly more detail. For example, "desirable not to interface VRRP with BFD
for determining the health of VRRP Active" could include the reasoning behind
this suggestion specifically.

I also think it's worth highlighting the extensive Operational Issues section
in RFC 9568 and Operational Considerations in RFC 5880, even just as pointers
as they are relevant here too. These are not strictly necessary as RFC 9568 and
RFC 5880 are normative references, but I think it would help.