Early Review of draft-ietf-ivy-entitlement-inventory-04
review-ietf-ivy-entitlement-inventory-04-opsdir-early-barguil-2026-08-02-01

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-entitlement-inventory-04
- Reviewer: Samier Barguil
- Review Date: 3-Aug-2026
- Intended Status: Standards Track

---

## Summary

The Internet-Draft "A YANG Data Model for Entitlement Inventory" defines a
standardized framework for managing software-based entitlements—such as
licenses, tokens, and service credentials—within a network inventory. The model
is designed to represent the complex relationships between organizational
entitlements, the technical functions (capabilities) of network assets, and the
operational constraints these entitlements impose.

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

## General Operational Comments Alignment with RFC 5706bis

The draft aligns with IETF guidelines for operations and management through the
following sections: Operational and Security Considerations: It includes
dedicated sections for both, covering management plane security, data
sensitivity, and operational lifecycle tasks

        - Read-Only Model Design: In alignment with best practices for
        inventory reporting, the model is entirely read-only (config false),
        acknowledging that write access to the underlying state is managed by
        external systems.

        - Data Sensitivity and Access Control: It identifies commercially
        sensitive data (like SKUs and contract periods) and mandates the use of
        the Network Configuration Access Control Model (NACM) to restrict
        access to authorized personnel.

        - Scalability: It addresses potential performance bottlenecks in
        large-scale deployments by recommending specific caching and validation
        strategies

## Nits

Optional editorial suggestions

Spacing Errors:

        "Internet- Drafts": Found in Section 1 (extra space after the hyphen).
        "as- a-service": Found in the Introduction
        "basic-capability- description": Found in Section 3.2
        "pay-as-you- grow": Found in Section 3.3
        "inventory- yang": Found in the mailing list link in the header

Examples:

        - Because the document is an I-D with fixed pagination, the JSON code
        blocks are frequently interrupted by page headers and footers  This is
        visible in almost every major example. While the internal logic of the
        JSON appears correct, these interruptions mean the code cannot be
        copied directly and used without manually stripping out the IETF
        document headers and footers.

        - Incomplete Fragments: In some excerpts, such as Section 4.2.3 (Basic
        Structure), the JSON block appears to end abruptly in the text view
        with an opening brace or tag that is not closed until a subsequent page.

        - Whitespace and Indentation: The draft uses standard JSON indentation,
        but there are minor inconsistencies in spacing around hyphens in key
        names in the descriptive text (e.g., "basic-capability- description")
        which might lead to confusion if a user tries to type them manually
        based on the prose rather than copying the code blocks [3.2].

Spelling Inconsistency:

        - The word "modelled" (British spelling) is used in Section 1.1,
        whereas "modeled" (American spelling, the IETF standard) is used in
        Section 2 and Section 3.