[Taps] Intdir telechat review of draft-ietf-taps-arch-18

Bernie Volz via Datatracker <noreply@ietf.org> Fri, 25 August 2023 14:35 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Bernie Volz via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: draft-ietf-taps-arch.all@ietf.org, last-call@ietf.org, taps@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <169297410123.51837.11105355383814735906@ietfa.amsl.com>
Reply-To: Bernie Volz <bevolz@gmail.com>
Date: Fri, 25 Aug 2023 07:35:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/57jIbw1BM9ZoTDagpNAsETk5zEY>
Subject: [Taps] Intdir telechat review of draft-ietf-taps-arch-18

Reviewer: Bernie Volz
Review result: Ready

I am an assigned INT directorate reviewer for draft-ietf-taps-arch. 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/.

Based on my review, if I was on the IESG I would ballot this document as NO
OBJECTION.

The document is well written and seems complete.

I have only a few minor nits:

- In section 4.1.4:

“If successful, the Rendezvous call returns a Connection object to represent
the established peer-to-peer connection.”

Doesn’t sound very asynchronous, especially because of “established” which
implies it could take some time?

- In section 1.4, the last entry (Transport Services System) is missing period
at end on sentence.

[Taps] Intdir telechat review of draft-ietf-taps-… Bernie Volz via Datatracker