Early Review of draft-ietf-ivy-network-inventory-software-04
review-ietf-ivy-network-inventory-software-04-opsdir-early-xie-2026-08-28-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-ivy-network-inventory-software-04]

- Reviewer: [Chongfeng Xie]

- Review Date: [28 Auguest, 2026]

- Intended Status: [Standards Track]

---

## Summary

Choose one:

- Has Issues: I have some minor concerns about this document that I think
should be resolved before publication.

## General Operational Comments Alignment with RFC 5706bis

>This document defines extension to the base Network Inventory YANG model to
support non-physical network elements (NEs), in general, it has good
operational feasibility, readability, and alignment with RFC5706bis guidelines.
However, the following issue should be considered.

    Section 7 states "This model provides read-only reporting of software
    status and associated timestamps".

   IMHO,a network device contains a vast number of software components. It is
   necessary to clarify whether this model will include all software components
   or only a subset. If the answer is the latter, criteria should be defined to
   determine which components are selected for inclusion.

## Major Issues

List critical problems blocking publication (e.g., protocol flaws, missing
operational safeguards, or lack of manageability considerations). Include
section/paragraph references.

None.

---

## Minor Issues

List non-blocking but important clarifications (e.g., ambiguous terminology or
incomplete examples).

 > Section 5 provides an explanation of the term "Software component," but
 since this term has already been mentioned in Section 1, it is advisable to
 relocate this definition to the first section where it initially appears.
 Furthermore, Sections 4 and 5 could be merged to better focus on the
 introduction of extensions proposed in this draft.

---

## Nits

Optional editorial suggestions (e.g., acronym expansions or grammar fixes).

 > Section 2: "platformos " -> "platformOS".

 > Section 2: "enhanced software information" -> "extended software
 information", I think "extended" is more suitable.

---