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

Paul Vixie <paul@redbarn.org> Mon, 26 March 2018 16:31 UTC

Return-Path: <paul@redbarn.org>
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 595A5126CC4 for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 09:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 f-0HnTerBXKV for <dnsop@ietfa.amsl.com>; Mon, 26 Mar 2018 09:31:51 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC9F3120724 for <dnsop@ietf.org>; Mon, 26 Mar 2018 09:31:51 -0700 (PDT)
Received: from [IPv6:2001:559:8000:c9:4ca8:bd4c:848b:7427] (unknown [IPv6:2001:559:8000:c9:4ca8:bd4c:848b:7427]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id A6A4B7594C; Mon, 26 Mar 2018 16:31:51 +0000 (UTC)
Message-ID: <5AB92075.9090506@redbarn.org>
Date: Mon, 26 Mar 2018 09:31:49 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Martin Hoffmann <martin@opennetlabs.com>
CC: bert hubert <bert.hubert@powerdns.com>, dnsop@ietf.org
References: <20180326154645.GB24771@server.ds9a.nl> <20180326182443.76cff724@smaug.local.partim.de>
In-Reply-To: <20180326182443.76cff724@smaug.local.partim.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mlPn38UnCp9etMGG2eaIZ8YuQeQ>
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:31:53 -0000


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

i sympathize with this view, but here's my worry:

> That having been said, a stronger document set written today would
> not be able to put all of the DNS genies back into their bottles. Too
> many implementations have guessed differently when presented with a
> loose specification, and interoperability today is a moving, organic
> target. When I periodically itch to rewrite the specification from
> scratch, I know there are too many things that must be said that also
> cannot be said. It’s as though, in a discussion of the meaning of
> some bit pattern, a modern description of the protocol—written with
> full perspective on all that has been done in the DNS field—would
> have to say, “It could mean x but some implementations will think it
> means y so you must be cautious.”

(https://queue.acm.org/detail.cfm?id=1242499)

what this means is, it's a difficult task.

-- 
P Vixie