[Tsv-art] Tsvart last call review of draft-ietf-dnsop-no-response-issue-14

David Black via Datatracker <noreply@ietf.org> Tue, 17 December 2019 16:48 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: David Black via Datatracker <noreply@ietf.org>
To: tsv-art@ietf.org
Cc: last-call@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-no-response-issue.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: David Black <david.black@dell.com>
Message-ID: <157660133788.26408.6337624144697419872@ietfa.amsl.com>
Date: Tue, 17 Dec 2019 08:48:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/pV-Fyg8jPJ2j1MHV_HYCwHdpD5M>
Subject: [Tsv-art] Tsvart last call review of draft-ietf-dnsop-no-response-issue-14

Reviewer: David Black
Review result: Ready

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.

I did not see any transport-related issues that require attention.

Some of the tests described in this draft use multiple DNS queries, but
in all cases, the multiple queries are sequential in that the client performing
the request waits for the response (or lack thereof) to a query before
proceeding to the next query.  With at most one outstanding DNS query
at a time, such tests should not cause congestion problems.

[Tsv-art] Tsvart last call review of draft-ietf-d… David Black via Datatracker