Re: [DNSOP] Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice

Warren Kumari <warren@kumari.net> Tue, 10 March 2020 13:55 UTC

Return-Path: <warren@kumari.net>
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 DE19F3A1303 for <dnsop@ietfa.amsl.com>; Tue, 10 Mar 2020 06:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 1lrIUarjIRbA for <dnsop@ietfa.amsl.com>; Tue, 10 Mar 2020 06:55:44 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 8C42A3A0F21 for <dnsop@ietf.org>; Tue, 10 Mar 2020 06:55:37 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id q9so4293998lfc.10 for <dnsop@ietf.org>; Tue, 10 Mar 2020 06:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JOitEPXbE3HQpVcLB57oBVCMdxsV5KNt9zCNDRUUesM=; b=C3Uj1sSaoc8kSSM295FudrR0Z2zBqQMJmvRuhzFYzM93frAoHzFuYK3WJa9ulLQJbJ LA4o9GvTxPwTmsypyDAyHKBW/fTniYv934Jj6+UW9W3rKFZfMOsvh8yOGIqTJgIqZ/aG 0eyf8fZU4L0Gale4NMMIeJ0hkkkgkeqbthTBPxRIGFr7l5upYotu/zjn7cdG3jW7Frif HOLEfvJ0Y3wN/sbnIej4B4zbw1NyAtcqnPDMXPEC3YnImpbhpHeFqATawNBKOq5ZRRvZ 4Bt6vtBTCdqiwPj8iJqOKCquXZwLlQGw8MOmqTwlCOTaRaOXUboqrNTkI7kTyI+yiSKH C2Iw==
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=JOitEPXbE3HQpVcLB57oBVCMdxsV5KNt9zCNDRUUesM=; b=eqTYguZHlnSJ2AtjqK3M8q+wLXgE5+RgGIAs71X+baNEwvmPC8TKAK/Kj0AR1Zb9M2 OtDySMTpfE1NS2sWvMcofrWojFLSsTdhGqE4eeRekmH0tsgCIHQEgqlQgiGz/6lQinbL sSVFmYzlJ/JR2p+60EWYQMazZXbVo8YHJN1K1Q/z8IX8vwQqj4k6AaD47wO2Y4va6LnY s1ADzFzrjCOufkB+BmlNu7nE1+s3ZN9Xhrv20rn/oumFCoau418cTpC3CNxoh2ZhjtpN SXBVtKUv78l7RF/Iv53E0HzktZzKMtSQIuKRIM1uATh+VDDLMqWxGOHsw2/aqAUc0veA kHxg==
X-Gm-Message-State: ANhLgQ0wr2IaXGk5i0k39p702HXAOtpo+a8ZN+786uOpOGaQHtP5g1PW LAVzqSGfTF1zVqVAX+Y7aJDgQHwy1hNrAQG4HmoMhg==
X-Google-Smtp-Source: ADFU+vviQg2jUO+cdHTP9Nt0z0X/icNmfhwL+82/0ZDIIeCQhPfJgnrI0LYC++qbT0xIhuOGv1oxTV2TyR6XFRoqbzs=
X-Received: by 2002:a19:40d1:: with SMTP id n200mr11619667lfa.88.1583848525211; Tue, 10 Mar 2020 06:55:25 -0700 (PDT)
MIME-Version: 1.0
References: <157559763911.16433.13149772616705852561.idtracker@ietfa.amsl.com> <CAHw9_iJusBODpYOgmZ7q7mhED7wz9_PsF2nZSYN+DWyUBSVPRw@mail.gmail.com>
In-Reply-To: <CAHw9_iJusBODpYOgmZ7q7mhED7wz9_PsF2nZSYN+DWyUBSVPRw@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 10 Mar 2020 09:54:48 -0400
Message-ID: <CAHw9_iK1ndqiDpR3uTRo5YbYmqWG_mE5Jxx5LS2qU0rSX33FAg@mail.gmail.com>
To: draft-ietf-dnsop-no-response-issue@ietf.org
Cc: DNSOP-Chairs <dnsop-chairs@ietf.org>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/C2jYIuVjc92YWkEOzF3V-RS9KSM>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-no-response-issue-14.txt> (A Common Operational Problem in DNS Servers - Failure To Communicate.) to Best Current Practice
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: Tue, 10 Mar 2020 13:55:55 -0000

On Thu, Dec 19, 2019 at 8:28 PM Warren Kumari <warren@kumari.net> wrote:
>
> [ Note: CC list edited ]
>
> Hi there authors,
>
> During the IETF LC Stephane supported the document (an important
> document, worthy of publication), but noted that:
> 1: the document only deals with auth servers and that it should be
> more explicit and

So, finally a new version, but from what I can see, you didn't address
the above, nor did you add an Acknowledgements section.

I'm putting it back in Revised ID needed; please address the comments,
or I will be forced to send it back to the WG....

W

> 2: that Section 3 is confusing, and that Matt had provided some text
> which helps make this better --
> https://mailarchive.ietf.org/arch/msg/dnsop/_Nq8PAVOapIVal2BS7P-jlWmnuc
>
> Having reread section 3 (and Matt's suggestions) I agree with Stephane
> on both of these - I also think that addressing these should be quite
> easy (I don't think it requires a "restructuring"), especially as Matt
> has provided suggested text...
> I'd appreciate if you can address these, and SHOUT LOUDLY once you've
> had a chance to do so (or let me know how else you'd like to handle
> this).
>
> I also think that it would be worth adding an Acknowledgements section...
>
> Thanks,
> W
>
>
>
> On Thu, Dec 5, 2019 at 9:00 PM The IESG <iesg-secretary@ietf.org> wrote:
> >
> >
> > The IESG has received a request from the Domain Name System Operations WG
> > (dnsop) to consider the following document: - 'A Common Operational Problem
> > in DNS Servers - Failure To Communicate.'
> >   <draft-ietf-dnsop-no-response-issue-14.txt> as Best Current Practice
> >
> > The IESG plans to make a decision in the next few weeks, and solicits final
> > comments on this action. Please send substantive comments to the
> > last-call@ietf.org mailing lists by 2019-12-19. Exceptionally, comments may
> > be sent to iesg@ietf.org instead. In either case, please retain the beginning
> > of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    The DNS is a query / response protocol.  Failing to respond to
> >    queries, or responding incorrectly, causes both immediate operational
> >    problems and long term problems with protocol development.
> >
> >    This document identifies a number of common kinds of queries to which
> >    some servers either fail to respond or else respond incorrectly.
> >    This document also suggests procedures for zone operators to apply to
> >    identify and remediate the problem.
> >
> >    The document does not look at the DNS data itself, just the structure
> >    of the responses.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-ietf-dnsop-no-response-issue/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-ietf-dnsop-no-response-issue/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > The document contains these normative downward references.
> > See RFC 3967 for additional information:
> >     rfc6840: Clarifications and Implementation Notes for DNS Security (DNSSEC) (Proposed Standard - IETF stream)
> >     rfc3225: Indicating Resolver Support of DNSSEC (Proposed Standard - IETF stream)
> >     rfc7766: DNS Transport over TCP - Implementation Requirements (Proposed Standard - IETF stream)
> >     rfc4035: Protocol Modifications for the DNS Security Extensions (Proposed Standard - IETF stream)
> >
> >
> >
>
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
>    ---maf



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf