Early Review of draft-ietf-anima-rfc8366bis-29
review-ietf-anima-rfc8366bis-29-opsdir-early-wicinski-2026-04-22-00

# Ops-Dir Review Template

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-opsarea-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-anima-rfc8366bis-29

**Reviewer**: Tim Wicinski

**Review Date**: 2026-04-21

**Intended Status**: Standards Track

---

## **Summary**

Choose one:

- **Ready**: No issues found. This document is ready for publication.

The document is readable and well laid out, with examples to assist in
deployment. The document spells out the process of Onboarding (which was
Bootstrapping) devices operationally.

## **Nits**

In reading over the document I found a few minor editorial nits.

- Abstract

The abstract has this sentence fragment:

    This document defines a strategy to securely assign a Pledge to an Owner

While the introduction has this:

    This document defines a strategy to securely assign a candidate device
    (Pledge)

It seems to make sense to me to make the Abstract more in line with the
Introduction, as its read by more people/machines/etc.

- 8.3.  YANG Module

    upon the which protocol is used, such as RFC8995 and variations.

s/upon the which/upon which/

8.5.  Voucher Extensions

   The JSON serialization of Vouchers implicitly accomodates the above,

s/accomodates/accommodates/