[Taps] Opsdir last call review of draft-ietf-taps-impl-15

Linda Dunbar via Datatracker <noreply@ietf.org> Thu, 20 April 2023 19:28 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-taps-impl.all@ietf.org, last-call@ietf.org, taps@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <168201889830.60153.5806302388928903438@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Thu, 20 Apr 2023 12:28:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/EnOsmHbNN_cQM82Z5HRY-AFkwpM>
Subject: [Taps] Opsdir last call review of draft-ietf-taps-impl-15

Reviewer: Linda Dunbar
Review result: Has Nits

I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

The draft describes the methods (APIs) for applications to call Transport
services.

It would be nicer if adding a comparison with the existing methods to call
TCP/UDP services, such as on Linux you can call connect() to the TCP-socket, or
use write(), etc.

Thanks,
Linda

[Taps] Opsdir last call review of draft-ietf-taps… Linda Dunbar via Datatracker