Re: [DNSOP] Secdir last call review of draft-ietf-dnsop-no-response-issue-14

Tim Wicinski <tjw.ietf@gmail.com> Fri, 20 December 2019 09:09 UTC

Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8621200E0; Fri, 20 Dec 2019 01:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSbb51-9sfUW; Fri, 20 Dec 2019 01:09:50 -0800 (PST)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A94412004A; Fri, 20 Dec 2019 01:09:47 -0800 (PST)
Received: by mail-oi1-x235.google.com with SMTP id k4so4147958oik.2; Fri, 20 Dec 2019 01:09:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r46wqgYqq0aEDB0EQX08kk54hVTE63l0dqWzKcNs20w=; b=q/+jyMrGommIvG6hLDlTn7A67brwhnSt1LW4cosGu1Tj+bDdAhjAj3MwHR4ETCplHu /tP7RjRqu+/W13o8L0/Dmq9wU2UmiLBIu68sGMKFm7M4kI1bj+R8Nt6uVSY+7QcTMgoJ 06UFF/VuHNfzIvYZaUArSwJmjLoAcg97FmNP7TmYDbKCrHgiIw2GON73X6wcXPylfKwa KWMOUhi894BOxMjY2hKExJoZityZ8p8jm7WtmKwvSr/w7+jZR+U3g9mHFYxer1re0YKH Fte37CZq3EWhR4uWLoW5Eb0+19Yg/+RG5GawssJ7AK7Pmze8tkD/QrtbW14PA61D1TLP zCJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r46wqgYqq0aEDB0EQX08kk54hVTE63l0dqWzKcNs20w=; b=hhxVpw/KN0RtG3odzKMejRtlR8HYpCVh89j3+S4flpltSoM4An5r5/XVQ8eCqFsuo1 I/rpYOIPut3gkBcFI6iLKhDfards1YiVpzMjGRJfTPQ4GJsmWU4NJ6jAPLxjirjtIuiE QYh8dnw+2RbKkSq3mzQY/Ru+52xX1QllITgHaARcQMThEa0H4l5UQaUvSYMtAxrZid86 qeovtSes4PRV30p4HgBV5GcrAd2d6FXPEM4E7MSbe+am+FAAg9arOEehfmJ/b1pZHTmJ NbyAEkxbxH0jWvGFfUB2qMoY/n/HyOBLAbUvpn2DxcJpE27TVJhm/55vuosxL/8j6FBQ 01yQ==
X-Gm-Message-State: APjAAAUNZHlWKWDBsIGBDeb/FouZhKFdM3RQDdeLqu5quipuU9M4FEzn XN7GlCJeshGv4F4QuCUqeG5/bbNY6gt+aK4nkEC0lw==
X-Google-Smtp-Source: APXvYqwlmZd6PG6Ut1r3THE49DGJ4M9lgAEDq5Ur5w+aX5ZqUfFfP9Ugx8nZwtQAAdLFLvpMdkSF+MhmFt1NkIycjbw=
X-Received: by 2002:aca:cf58:: with SMTP id f85mr3553742oig.6.1576832986099; Fri, 20 Dec 2019 01:09:46 -0800 (PST)
MIME-Version: 1.0
References: <157677069055.27346.2427467441228883400@ietfa.amsl.com>
In-Reply-To: <157677069055.27346.2427467441228883400@ietfa.amsl.com>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 20 Dec 2019 04:09:35 -0500
Message-ID: <CADyWQ+FcSTkN-VktKUgmULPJOnO4_EA0Z95b5_TzCd_qWQSQSw@mail.gmail.com>
To: Catherine Meadows <catherine.meadows@nrl.navy.mil>
Cc: dnsop <dnsop@ietf.org>, draft-ietf-dnsop-no-response-issue.all@ietf.org
Content-Type: multipart/alternative; boundary="00000000000001b55f059a1f0a29"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6-NM4plLAKhmv9xEAzzwSMhQrXU>
Subject: Re: [DNSOP] Secdir last call review of draft-ietf-dnsop-no-response-issue-14
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 20 Dec 2019 09:09:52 -0000

Catherine

Appreciate the  feedback.  The authors have other issues to address, and
we'll add this to the queue.

Thanks
Tim

On Thu, Dec 19, 2019 at 10:51 AM Catherine Meadows via Datatracker <
noreply@ietf.org> wrote:

> Reviewer: Catherine Meadows
> Review result: Has Nits
>
> This draft concerns maintaining the correctness of DNS servers.  It lists
> the
> common mistakes that noncompliant servers make in responding to queries and
> gives the correct ones.  It also gives a set of tests operators can give to
> their servers ensure compliance, as well as directions for applying the
> tests.
>
> One of the main security issues  discussed is the fact that many servers
> are
> configured not to respond to queries outside of their scope because these
> are
> construed as an attack, when in fact these are legal queries that should be
> responded too (generally with a message saying that these are not
> supported)
> and that failure to respond can give be misinterpreted as packet loss,
> given an
> incorrect picture of the state of the network.   The document also
> discusses
> the security implications of such misleading responses.
>
> The document also warns about security risks of testing, and of removing
> non-compliant servers, and alternative means of handling these situations.
>
> All of the above information is summed up in the security considerations
> section , and most of it is discussed at more detail in the document
> itself.
>
> I think that the authors have done an excellent job of identifying and
> explaining security issues, and I consider the document Ready except for
> one
> nit.  In the places where the security considerations section sums up
> issues
> that are discussed in more depth in the document itself (e. g. the first ,
> on
> the fact that none of the tests should cause any harm to a
> protocol-compliant
> server), it would be useful to have a pointer to the section of sections
> where
> this information appears.
>
>