Re: [DNSOP] Is DNSSEC a Best Current Practice?

Tim Wicinski <tjw.ietf@gmail.com> Fri, 11 March 2022 10:31 UTC

Return-Path: <tjw.ietf@gmail.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 23AF43A0F46 for <dnsop@ietfa.amsl.com>; Fri, 11 Mar 2022 02:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fh8XFFN6ciB1 for <dnsop@ietfa.amsl.com>; Fri, 11 Mar 2022 02:31:39 -0800 (PST)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 541AF3A0F40 for <dnsop@ietf.org>; Fri, 11 Mar 2022 02:31:39 -0800 (PST)
Received: by mail-lf1-x12d.google.com with SMTP id 3so14270809lfr.7 for <dnsop@ietf.org>; Fri, 11 Mar 2022 02:31:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uKYpcGWd633pAnW+CfHwOLARQtUxfyp0jBVRooymGV0=; b=mcVhFu03xuM20Z3/Z17+HCtH3O3RKeQwon8t7hPohlScAXWrfGewN816zc6I1zV9t9 ElSWs1RyUEzasrPCoWw1Nw7zSwLglKAtM91wIbXHejS+Ysge5Ak9ku0ODD2aqiHAw0Ce eLp2EzhUz7FibUwaYACQobVYen9ZxGIeBQu3nrGxyqEPPxRULFK5O07EcbXNY/l0kljQ X5p2ji9Vk6uxZb+zq3ccrJqViujZDdkDZ2owlNMZiBejkMGkN1eL2bxCJPN5lYLWg1d6 sxxWJfp7HnFy8003KcizN1OCE//vwkofKdC6tVJw6RGaPHq9+5rQrMbK0vdjKwhxBCQ/ pmpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uKYpcGWd633pAnW+CfHwOLARQtUxfyp0jBVRooymGV0=; b=5hByElST4KK+Jm86dNuYLpuvwPYjwQ3jvxFrjv2PzLQkNOiel5GFny8lRDWuHDpM5g ZiSlrUcs1gIwRYLyKcqpQR9rcWJHdlkaVRZUSPY2Zd4sqSIYL3LUQExsUOmcX7JYei08 wK80VtyLjsgue0PwLsbxSrVrWO/5Dl7aDUfO905YWMg/VL2Jm9TnUS+Y3aGO6kzEnTJU MH+7hQakkky5iF9LPB8rPjno9EUiaRJ2RRRoIvIacginbEab6qi1+zWhURwFBjm3T3Nf HzorPVGMu8ZVdmvR67GLhatp0HiVSRgF9W3Ud2GigP2TRdR6BPtzVpUFBWQW7iRqZn0Z mOmA==
X-Gm-Message-State: AOAM531ZH2JGbe8/RDLbciPoIm315cmmdAWEBneusjEeKnpDbcwY5Fcx /wO9av+m8sWcv1szgQPcy61Mavl8ZqbtStjOhLbT0Rwl
X-Google-Smtp-Source: ABdhPJw8uWyYErR1FDH6w7wFzMk7i6V2THDEljHinKP6x+4zg35j0IlIsCC9Y1w+F/A3qptKJlFR59oU3FyPYtaE1oM=
X-Received: by 2002:ac2:5581:0:b0:448:39c8:37f0 with SMTP id v1-20020ac25581000000b0044839c837f0mr5522661lfg.162.1646994696984; Fri, 11 Mar 2022 02:31:36 -0800 (PST)
MIME-Version: 1.0
References: <88A0AA7A-01B8-4C7E-9A9A-1FB29C9FB18B@icann.org> <20220311.114445.338879450243418596.yasuhiro@jprs.co.jp> <CADyWQ+GWrjjSxb2cvLHL0Juvx95iaO__p_8--NqwwmMCTz61vw@mail.gmail.com> <42aa1418-48d7-25c5-c1b0-04811a6fe024@redbarn.org>
In-Reply-To: <42aa1418-48d7-25c5-c1b0-04811a6fe024@redbarn.org>
From: Tim Wicinski <tjw.ietf@gmail.com>
Date: Fri, 11 Mar 2022 05:31:25 -0500
Message-ID: <CADyWQ+H58Ak+Y_7gSyz2UD9SWUJOhnMbYrHeDsktWvX2Hi1Umw@mail.gmail.com>
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dc5ba305d9eed5eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/NnEtO-EA4nT8PjD4BpZVT9xZNB8>
Subject: Re: [DNSOP] Is DNSSEC a 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: Fri, 11 Mar 2022 10:31:44 -0000

On Fri, Mar 11, 2022 at 4:49 AM Paul Vixie <paul@redbarn.org> wrote:

>
>
> Tim Wicinski wrote on 2022-03-11 01:38:
> > ... for several years now I have
> > felt those two need to be republished with all
> > the updated text from the many updates (28 for 1035, 18 for 1034) in new
> > documents.  This does not include any other
> > changes, and it feels like a thankless task.
> not just thankless but useless. a correctness preserving rewrite, from
> scratch, should be performed every few decades. (we're overdue.) a goal
> should be readability which will require NOT reusing most of the
> original text or including the updated text. we often didn't know or
> otherwise misstated our implications. every material statement made by
> any prior DNS specification or update to the specification should be
> enumerated and checked off as its then-modern meaning is incorporated.
>
> i'll offer to join a team to work on this when i eventually retire, if
> it hasn't been recently enough done at that time. so, i think, should
> other guilty parties.
>
> --
> P Vixie
>

I agree with you Paul on rewriting. I was trying to comment that even the
idea
of publishing a version of those documents with the updates as a
-00/starting point
felt thankless.

But walking through the specifications ? indeed.

tim