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

Paul Vixie <paul@redbarn.org> Tue, 27 March 2018 21:33 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 02DBA127867 for <dnsop@ietfa.amsl.com>; Tue, 27 Mar 2018 14:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 Nq-GIKO6Ol4U for <dnsop@ietfa.amsl.com>; Tue, 27 Mar 2018 14:33:11 -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 D531A12DA51 for <dnsop@ietf.org>; Tue, 27 Mar 2018 14:33:11 -0700 (PDT)
Received: from [10.1.10.176] (50-255-33-26-static.hfc.comcastbusiness.net [50.255.33.26]) (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 A7E937594C; Tue, 27 Mar 2018 21:33:09 +0000 (UTC)
Message-ID: <5ABAB891.3010306@redbarn.org>
Date: Tue, 27 Mar 2018 14:33:05 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 5.0.24 (Windows/20180302)
MIME-Version: 1.0
To: Matthew Pounsett <matt@conundrum.com>
CC: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>, Suzanne Woolf <suzworldwide@gmail.com>, dnsop <dnsop@ietf.org>
References: <20180326154645.GB24771@server.ds9a.nl> <CA3D81B6-164F-4607-A7E6-B999B90C4DA8@gmail.com> <5852643C-B414-4C3E-A1B9-553054D3DD46@isc.org> <CAAiTEH8aA3J1j4iUQDisDHiUJXopykKkssuhOK=v+iVV_XZWyA@mail.gmail.com>
In-Reply-To: <CAAiTEH8aA3J1j4iUQDisDHiUJXopykKkssuhOK=v+iVV_XZWyA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HK0CE0kyehPxWrUE_wdLbsMtbFk>
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: Tue, 27 Mar 2018 21:33:15 -0000

i see no purpose in change documents, which would add to the set of 
things a new implementer would have to know to read, and then to read.

rather, we should focus on a DNSOP document set that specifies a minimum 
subset of DNS which is considered by the operational community to be 
mandatory to implement. any implementer can remove anything else and 
still be checklist-compatible when customers are baking things off.

if someone wants to implement iquery or WKS let that be crazy rather 
than broken -- on-the-wire patterns still described, code points still 
reserved, but unlikely to find anybody to actually interoperate with.

vixie

re:

Matthew Pounsett wrote:
>
>
> On 27 March 2018 at 03:49, Ondřej Surý <ondrej@isc.org
> <mailto:ondrej@isc.org>> wrote:
>
>
>     Again, from experience from dnsext, I would strongly suggest that
>     any work in this area is split into CHANGE documents and REWRITE
>     documents, with strict scope. Documents rewriting existing RFCs
>     while adding more stuff at the same time tend to not reach the
>     finish line.
>
> Does this include combining documents?  For example, it would probably
> make sense to combine some of the clarifications documents into any
> rewrite of 1034/1035.
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
P Vixie