Telechat Review of draft-ietf-dnsop-no-response-issue-17
review-ietf-dnsop-no-response-issue-17-intdir-telechat-pignataro-2020-03-22-00

Request Review of draft-ietf-dnsop-no-response-issue
Requested rev. no specific revision (document currently at 18)
Type Telechat Review
Team Internet Area Directorate (intdir)
Deadline 2020-04-07
Requested 2020-03-16
Requested by √Čric Vyncke
Authors Mark Andrews, Ray Bellis
Draft last updated 2020-03-22
Completed reviews Tsvart Last Call review of -14 by David Black (diff)
Secdir Last Call review of -14 by Catherine Meadows (diff)
Genart Last Call review of -14 by Wassim Haddad (diff)
Opsdir Last Call review of -14 by Dan Romascanu (diff)
Intdir Telechat review of -17 by Carlos Pignataro (diff)
Assignment Reviewer Carlos Pignataro
State Completed
Review review-ietf-dnsop-no-response-issue-17-intdir-telechat-pignataro-2020-03-22
Posted at https://mailarchive.ietf.org/arch/msg/int-dir/wfKo4vDmFJwPa1HeDY9wxP2JdEA
Reviewed rev. 17 (document currently at 18)
Review result Ready with Nits
Review completed: 2020-03-22

Review
review-ietf-dnsop-no-response-issue-17-intdir-telechat-pignataro-2020-03-22

I am an assigned INT directorate reviewer for this Internet-Draft.  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 http://www.ietf.org/iesg/directorate.html.

I hope these comments are clear and useful.

Document: draft-ietf-dnsop-no-response-issue
Reviewer: Carlos Pignataro
Intended Status: BCP

This is a very comprehensive and well written document, for which I have no concerns from an Internet Directorate perspective.

This document is effectively Ready, modulo a couple of Nits for the author's consideration:

 A Common Operational Problem in DNS Servers - Failure To Communicate.

Is there an extraneous "." at the end of the title?

   o  administrative or technical contacts listed in the registration
      information for the parent domain of the name of the misbehaving
      server, or for zones   for which the name server is authoritative
 
Spacing at "zones   for" -> "zones for"

Thanks,

Carlos Pignataro.