[DNSOP] Opsdir last call review of draft-ietf-dnsop-no-response-issue-14

Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 17 January 2020 06:58 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A41C1207FC; Thu, 16 Jan 2020 22:58:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, dnsop@ietf.org, draft-ietf-dnsop-no-response-issue.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Dan Romascanu <dromasca@gmail.com>
Message-ID: <157924428555.27912.12115721742179552376@ietfa.amsl.com>
Date: Thu, 16 Jan 2020 22:58:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/eZ1mUU7pqiOv23YWPMcUzQ4vE8Q>
Subject: [DNSOP] Opsdir last call review of draft-ietf-dnsop-no-response-issue-14
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2020 06:58:06 -0000

Reviewer: Dan Romascanu
Review result: Ready

I apologize for the late review. Notifications still seem not to work, and I
was not aware about this assignment until recently. I hope it does not come too
late.

This document identifies a number of common kinds of DNS queries to which some
servers either fail to respond or else respond incorrectly. It also suggests
test procedures for zone operators to apply to identify and remediate the
problems caused by misbehaving (non-compliant) servers. Operators are principal
users of this document, so it's relevant for them. The document is a BCP, so a
full RFC 5706 review does not apply.

I am not a DNS expert, and I suspect that a proper review was / will be made on
all DNS-related details. I found the document a little bit difficult to read
because of the lack of expansions and references of many acronyms, but I guess
that DNS experts are familiar with most or all of them.

Sections 8 and 9 are very useful for operators and I recommend focusing on
these. The sections provide a number of recommendations for testing procedures
to be performed at first operation and later periodically, and means to
mitigate issues.

This document is Ready from an OPS perspective.