Skip to main content

Early Review of draft-ietf-netmod-rfc8407bis-24
review-ietf-netmod-rfc8407bis-24-opsdir-early-fioccola-2025-05-02-00

Request Review of draft-ietf-netmod-rfc8407bis
Requested revision No specific revision (document currently at 28)
Type Early Review
Team Ops Directorate (opsdir)
Deadline 2025-05-04
Requested 2025-04-13
Requested by Mahesh Jethanandani
Authors Andy Bierman , Mohamed Boucadair , Qin Wu
I-D last updated 2025-06-05 (Latest revision 2025-06-05)
Completed reviews Yangdoctors IETF Last Call review of -11 by Xufeng Liu (diff)
Yangdoctors Early review of -24 by Xufeng Liu (diff)
Opsdir Early review of -24 by Giuseppe Fioccola (diff)
Dnsdir IETF Last Call review of -24 by Ralf Weber (diff)
Genart IETF Last Call review of -24 by Christer Holmberg (diff)
Tsvart IETF Last Call review of -25 by Dr. Joseph D. Touch (diff)
Dnsdir Telechat review of -25 by Ralf Weber (diff)
Secdir Telechat review of -25 by Yoav Nir (diff)
Assignment Reviewer Giuseppe Fioccola
State Completed
Request Early review on draft-ietf-netmod-rfc8407bis by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/68dj-The9alrRWCLxif5PAT4UiU
Reviewed revision 24 (document currently at 28)
Result Has nits
Completed 2025-05-02
review-ietf-netmod-rfc8407bis-24-opsdir-early-fioccola-2025-05-02-00
This document provides guidelines for authors and reviewers of YANG module
documents. It obsoletes RFC 8407 and also updates RFC 8126. I think that it is
clear and well-written.

However, I have few suggestions:

- I would include in section 1 more information about the motivations behind
the changes proposed in the document. Some are due to errors, others are
consequential to the YANG implementation experience, and so on. Maybe the long
list of section 1.1 can be split into categories. It is just to provide
additional context for readers.

- In section 2.4, the meaning of the uppercase usage of the key words could be
further explained. Since this document provides guidelines for YANG Data
Models, I think that a sentence to clarify the implications of the normative
terminology would help in this case. For example, if the normative terminology
is needed to establish the level of compliance of every IETF YANG Data Models
with these guidelines, it is good to highlight this point in section 2.

- I would point out in section 3.5.1 that, in addition to service, network and
device models, other types of YANG modules are possible and have been defined
covering layering relationships, e.g. between underlay networks and overlay
services.

- I'm wondering whether it can be useful in section 4 to provide some
recommendations about the typical structure and ordering while writing a YANG
data model.