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

Matthew Pounsett <matt@conundrum.com> Sat, 31 March 2018 21:41 UTC

Return-Path: <matt@conundrum.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 C57D61241F3 for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 14:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.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 ixnvtx9YaCXt for <dnsop@ietfa.amsl.com>; Sat, 31 Mar 2018 14:41:48 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 C76E9120725 for <dnsop@ietf.org>; Sat, 31 Mar 2018 14:41:48 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id m134-v6so15163274itb.3 for <dnsop@ietf.org>; Sat, 31 Mar 2018 14:41:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+lQAT2aTYL5VRXIZKaU2CVdQlno1yzc9/4LZ7Zr7FZ0=; b=gv0DIdxPNk/1q+lE4BbJs1HdAZeT8RXHjqpgqiwGUNgwZlJCTs8PPKOZF1DWP2mE7l +f/b71iYpOKiF10lqvxH6WxQxYf+A9drF+PeVRpf3OjlwLdDVE9SZzlcO8ThqMjvQUFW fE6GFJm0K5gF7/F0S87n5zidBH+vKHuDcnohaMfX4xri08nsV16kjk5CEBpHn2rpMPeZ Oc6cjXrktgbev2oGvs4b0F/Ee95KCRyQc8p9tEWUwMhmx3yfxEqvFGM8kehFlnjvaTUR W1Aoag4Y2pYnw21RifNlrF7TDFtyfdyqnj84gOkXA5JflzaSWCgKJUj8FR4KBsYSPbYs WWHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+lQAT2aTYL5VRXIZKaU2CVdQlno1yzc9/4LZ7Zr7FZ0=; b=Ki2Yq2Z4+ye1wgS45jRg6Vm9RHpLAN13SOKId2n8PIRu8y7dOHG/bvufekKqf78odV b2zVATmdV7GK2Xv09eXq02i8oEOUHeYpo8YxeGQVRTLKQHMTloIomVaV10njGoVTLmhW FIwxmLpOkL2SLP1i9yRwScifRC7N3Jt+UZpkyH5ORfMXRPwqPG4NrmD/uSx+uwoGbRI0 vNSXXfmgl41fHmuTffR1MGa7ZO3BdJpSR1nTX11J0BLMVlnBObHkfCKIHSn0QN6Qjm/n tm/wLyj6ZpZsSV+1HD/ikzPySQW2lELpItPl8N1wb747d7EYS53Fqf+aIMPMQyIxJie0 9sKQ==
X-Gm-Message-State: ALQs6tBTZwHy3cO31o7EUndooVHtQX36iLXZAelD387eydYUaCsZd2nb D+DHWWtnP2wJ/DwEj2q3j5VnAl+tPsEyhqXyu7Yt62KU
X-Google-Smtp-Source: AIpwx48q0Oyj/EsHeDkUBINOWxFce7q7eFnmKOFEHe3SJ9wSb4+irq8bvhw5osnhaIG7BnuCWeAHKy7sCu4h88kpE5Y=
X-Received: by 2002:a24:cd45:: with SMTP id l66-v6mr8081962itg.151.1522532507850; Sat, 31 Mar 2018 14:41:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.2.112.197 with HTTP; Sat, 31 Mar 2018 14:41:47 -0700 (PDT)
In-Reply-To: <5ABFFD35.1020502@redbarn.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> <5ABAB891.3010306@redbarn.org> <CAAiTEH94S9VE0_QNEmUvVEkvxtBi2hoWo3DUVENJbEiXM+kkHw@mail.gmail.com> <5ABADEFE.30806@redbarn.org> <CAAiTEH9=rmhmRqCQyEbBFKF3BgKbe8bx+G3eAqhdqKEC55eA4A@mail.gmail.com> <5ABBE389.5020008@redbarn.org> <CAAiTEH8bLcvfnhB3=Hzds=q8ppMQOZw6vXY7h3CO-MdYW3BFCg@mail.gmail.com> <5ABFFD35.1020502@redbarn.org>
From: Matthew Pounsett <matt@conundrum.com>
Date: Sat, 31 Mar 2018 17:41:47 -0400
Message-ID: <CAAiTEH8Q=QxZcDn+r26H1rGc_X+U-2dgveDvtKcmVk6fqLmAyA@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: Ondřej Surý <ondrej@isc.org>, Suzanne Woolf <suzworldwide@gmail.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004a2f420568bc3988"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/K1z6dr1odHK-fmCJC6IHq0riLAk>
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: Sat, 31 Mar 2018 21:41:51 -0000

On 31 March 2018 at 17:27, Paul Vixie <paul@redbarn.org> wrote:

>
>
>>
>> I think the RFC series as a whole needs to contain both, but I'm not
>> saying that both should exist simultaneously for any given set of
>> documents within the RFC series.
>>
>
> i think you are.


I'm really not.


>
>
> I think we've reached a point where the time series for DNS has
>> become so complex and convoluted that it's time for a reset to make
>> it readable again.  We can then carry on patching that with
>> time-series documents if we want, but the rewrite will give us a new
>> baseline that's coherent and complete, which we don't have today.
>>
>
> there's a carrier wave in that time series, which has its own wave form.
> at the end of each epoch, we'll be back where we are today, without a
> coherent or complete document set. we'd be moving from failing to plan, to
> planning to fail. let's make a better move.
>

That's a pretty cynical view.  Do you not think the specifications being
written today are better than they used to be?

to achieve the goals you stated earlier, there would have to be both the
> time series of changes, and the timeless document full of lineouts. bert's
> "DNS Illustrated" github site is an example of the latter, and a starting
> point for it, if we wish.


If we had a better baseline, and if our Updates documents were clearer
about what they change in older documents, that line-out would be a pretty
trivial document to maintain, and might not even be necessary.