[ippm] Intdir telechat review of draft-ietf-ippm-otwamp-on-lag-07

Timothy Winters via Datatracker <noreply@ietf.org> Mon, 20 November 2023 15:47 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Timothy Winters via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: draft-ietf-ippm-otwamp-on-lag.all@ietf.org, ippm@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170049526769.34564.15492349481960153939@ietfa.amsl.com>
Reply-To: Timothy Winters <tim@qacafe.com>
Date: Mon, 20 Nov 2023 07:47:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/A20KP5JsSoQH11UkwLCsACNxhog>
Subject: [ippm] Intdir telechat review of draft-ietf-ippm-otwamp-on-lag-07

Reviewer: Timothy Winters
Review result: Ready

Reviewer: Timothy Winters
Review result: Ready

I am an assigned INT directorate reviewer for draft-ietf-ippm-otwamp-on-lag.
These comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherd(s) should treat these comments just
like they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received. For more
details on the INT Directorate, see
<https://datatracker.ietf.org/group/intdir/about/>.

The document is well written and easy to follow.  I did note that the
new micro TWAMP Session-Sender packet format is over UDP with a specified
payload which allows for the potential of IP fragmentation.  After re-reading
OWAMP Payload padding size is part of the session setup as a user might want to
measure the impact of packet delay based on packet size.  Therefore, I don't
have any concerns about this document.

Based on my review, if I was on the IESG I would ballot as No Objection.

[ippm] Intdir telechat review of draft-ietf-ippm-… Timothy Winters via Datatracker