Skip to main content

IETF Last Call Review of draft-ietf-ippm-ioam-data-integrity-16
review-ietf-ippm-ioam-data-integrity-16-tsvart-lc-nishida-2026-03-07-00

Request Review of draft-ietf-ippm-ioam-data-integrity
Requested revision No specific revision (document currently at 20)
Type IETF Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2026-03-10
Requested 2026-02-24
Authors Frank Brockners , Shwetha Bhandari , Tal Mizrahi , Justin Iurman
I-D last updated 2026-09-10 (Latest revision 2026-07-18)
Completed reviews Secdir Early review of -07 by Benjamin Kaduk (diff)
Secdir IETF Last Call review of -12 by Benjamin Kaduk (diff)
Tsvart IETF Last Call review of -16 by Yoshifumi Nishida (diff)
Tsvart Telechat review of -17 by Yoshifumi Nishida (diff)
Intdir Telechat review of -19 by Daniel Migault (diff)
Assignment Reviewer Yoshifumi Nishida
State Completed
Request IETF Last Call review on draft-ietf-ippm-ioam-data-integrity by Transport Area Review Team Assigned
Posted at https://mailarchive.ietf.org/arch/msg/tsv-art/_UWgg7UxQyKUk2aPu0HPw_fr_2w
Reviewed revision 16 (document currently at 20)
Result Almost ready
Completed 2026-03-07
review-ietf-ippm-ioam-data-integrity-16-tsvart-lc-nishida-2026-03-07-00
This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Summary: This document is almost ready for publication as a Proposed
         Standard document. I don't see critical concerns in this draft from
         transport view point, but I believe it will be better to address the
         following points.

1: While each packet's chain looks self-contained within that single packet, it
would be good to mention that
   the mechanism will not be affected by packet reordering or duplication.

2: Section 7.2 states "Inappropriate use of this Integrity Protection Method
may overload nodes and cause service degradation or failure,"
   which implicitly acknowledges risks for Dos attacks. I think this point
   should be addressed.

3: The Validator looks a single point of trust and failure. I think the draft
should clarify what operational controls are
   recommended for protecting the Validator. For example, would it be
   beneficial to deploy multiple Validators?