Re: [DNSOP] Current DNS standards, drafts & charter

Martin Hoffmann <martin@opennetlabs.com> Mon, 26 March 2018 16:24 UTC

Return-Path: <martin@opennetlabs.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 D98371270B4 for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 09:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
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 44R72dEsRORR for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 09:24:46 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2a04:b900::1:0:0:10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECFD5124B17 for <dnsop@ietf.org>; Mon, 26 Mar 2018 09:24:45 -0700 (PDT)
Received: by dicht.nlnetlabs.nl (Postfix, from userid 58) id DF2288531; Mon, 26 Mar 2018 18:24:43 +0200 (CEST)
Received: from smaug.local.partim.de (unknown [84.245.51.209]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 6D1CF852F; Mon, 26 Mar 2018 18:24:43 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=none header.from=opennetlabs.com
Date: Mon, 26 Mar 2018 18:24:43 +0200
From: Martin Hoffmann <martin@opennetlabs.com>
To: bert hubert <bert.hubert@powerdns.com>
Cc: dnsop@ietf.org
Message-ID: <20180326182443.76cff724@smaug.local.partim.de>
In-Reply-To: <20180326154645.GB24771@server.ds9a.nl>
References: <20180326154645.GB24771@server.ds9a.nl>
Organization: Open Netlabs
X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/pyfDookwuObyZAnw8a8d4vc-8qQ>
Subject: Re: [DNSOP] Current DNS standards, drafts & charter
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 26 Mar 2018 16:24:48 -0000

bert hubert wrote:
> 
> I've been looking at the amount of DNS out there, and I think we can
> do several things with them. I've also concluded that the mediocrity
> of DNS implementations outside of the well-known ones can not be
> fully blamed on "stupid programmers". The fact that we've offered the
> world 1000-2000 pages to read, with no guideline where to start, is
> also very likely to have contributed.

The thing that trips me up implementing DNS without intimate
knowledge of the assorted RFCs isn't the amount of them -- 2000
pages isn't all that bad if you come from SIP. Rather, it is that
important details are hidden all over the document base, often
in unexpected places. As an example, the SOA minumum field is
(re)defined in RFC 2308 which nominally talks about negative
caching, something I'd probably ignore if I implement a
simple authoritative server.

So, I'll step on that mine: What really would help new
implementers is a 1034bis.

Kind regards,
Martin