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

Viktor Dukhovni <ietf-dane@dukhovni.org> Sat, 12 March 2022 05:53 UTC

Return-Path: <ietf-dane@dukhovni.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 ADCD83A1352 for <dnsop@ietfa.amsl.com>; Fri, 11 Mar 2022 21:53:13 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 nMRrXEBIyG3y for <dnsop@ietfa.amsl.com>; Fri, 11 Mar 2022 21:53:12 -0800 (PST)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (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 2D3613A1338 for <dnsop@ietf.org>; Fri, 11 Mar 2022 21:53:11 -0800 (PST)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 7DB0EE3ECC; Sat, 12 Mar 2022 00:53:10 -0500 (EST)
Date: Sat, 12 Mar 2022 00:53:10 -0500
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: dnsop@ietf.org
Message-ID: <Yiw1RqS6VskwLjcV@straasha.imrryr.org>
Reply-To: dnsop@ietf.org
References: <88A0AA7A-01B8-4C7E-9A9A-1FB29C9FB18B@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <88A0AA7A-01B8-4C7E-9A9A-1FB29C9FB18B@icann.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gHEv9Ko8JfoJe-26RFs81ujZ99Y>
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: Sat, 12 Mar 2022 05:53:14 -0000

On Thu, Mar 10, 2022 at 06:54:07PM +0000, Paul Hoffman wrote:

> Greetings again. My motivation here is kinda trivial, but I've heard
> it is a common complaint. When writing a about DNSSEC, I need to
> reference the RFC. But it's three RFCs (4033, 4034, and 4035), and
> possibly another (6840). It would be awfully nice to refer to "DNSSEC"
> with a single reference like "BCP 250".

I'm on board for a DNSSEC BCP document.  I've effectively been working
on this for some time.  Hence e.g. the NSEC3 iteration draft and an
upcoming APNIC guest post on ZSK best-practice.

Would be nice to publish more accessible text on the correct handling of
ENTs and wildcards (as e.g. malpracticed by NameCheap).

At least TLSA non-response has mostly gone away as an issue, NSEC3
iterations have come down quite significantly.  Also algorithms 5 and 7
have each lost ~93% of their peak deployment levels.

So communicating (and repeatedly nagging) best-practice does appear to
translate to operational changes, even if the time scale is ~2 years in
some cases.

-- 
    Viktor.