IETF Last Call Review of draft-ietf-ippm-ioam-integrity-yang-05
review-ietf-ippm-ioam-integrity-yang-05-genart-lc-even-2026-04-14-00

Request Review of draft-ietf-ippm-ioam-integrity-yang
Requested revision No specific revision (document currently at 08)
Type IETF Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2026-04-23
Requested 2026-04-09
Authors Justin Iurman , Tianran Zhou
I-D last updated 2026-08-13 (Latest revision 2026-05-08)
Completed reviews Yangdoctors Early review of -04 by Qiufang Ma (diff)
Genart IETF Last Call review of -05 by Roni Even (diff)
Yangdoctors IETF Last Call review of -06 by Qiufang Ma (diff)
Intdir IETF Last Call review of -06 by Satoru Matsushima (diff)
Secdir IETF Last Call review of -06 by Corey Bonnell (diff)
Assignment Reviewer Roni Even
State Completed
Request IETF Last Call review on draft-ietf-ippm-ioam-integrity-yang by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/fN4gw-YA6wsihSwcAVhPkB-EypM
Reviewed revision 05 (document currently at 08)
Result Ready w/nits
Completed 2026-04-14
review-ietf-ippm-ioam-integrity-yang-05-genart-lc-even-2026-04-14-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-ippm-ioam-integrity-yang-??
Reviewer: Roni Even
Review Date: 2026-04-14
IETF LC End Date: 2026-04-23
IESG Telechat date: 2026-04-30

Summary:
The document is ready for publication as a standard track RFC.
One editorial question: I am wondering why not add in the main text references
to the appendix, for example in section 3.2 reference the example in appendix C

Major issues:

Minor issues:

Nits/editorial comments: