Re: [DNSOP] More private algorithms for DNSSEC

Paul Wouters <paul@nohats.ca> Mon, 21 March 2022 07:43 UTC

Return-Path: <paul@nohats.ca>
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 05C173A1967 for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 00:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=nohats.ca
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 zW86bR50V7hV for <dnsop@ietfa.amsl.com>; Mon, 21 Mar 2022 00:43:45 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.85]) (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 1676F3A1950 for <dnsop@ietf.org>; Mon, 21 Mar 2022 00:43:36 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4KMRSP5X6Bz3T0; Mon, 21 Mar 2022 08:43:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1647848613; bh=vNXbyu/sZQ3YR3hTm61UEbVrhHO9W96EXkhP5jwUlv0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=mMicL9J/xxHQvT7WUb5aWWjf0iadip1YRQAeiRMxM+So5dytaFbaV/Cb5ZT/r85W0 NjIFAKfuamjcdY8iaJPXt1ZghgIJw7StkidachPEDJuxJFHXITJXICgxLAusRRis9/ cqVOG1+YiwOAKYkKHsmO9Y7dQcQr5xwvy9tkhdlQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id fNkYUSYc2wI6; Mon, 21 Mar 2022 08:43:32 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 21 Mar 2022 08:43:32 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 8DB852CDF94; Mon, 21 Mar 2022 03:43:31 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8A7C12CDF93; Mon, 21 Mar 2022 03:43:31 -0400 (EDT)
Date: Mon, 21 Mar 2022 03:43:31 -0400
From: Paul Wouters <paul@nohats.ca>
To: Paul Hoffman <paul.hoffman@icann.org>
cc: dnsop WG <dnsop@ietf.org>
In-Reply-To: <5C105C71-B18C-4366-94F5-E8D60970109C@icann.org>
Message-ID: <1b2cf9b2-5d0-647-83d8-f4284bff9042@nohats.ca>
References: <5C105C71-B18C-4366-94F5-E8D60970109C@icann.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/oQdgULLojMqIO6ANw-7vAZNvmcY>
Subject: Re: [DNSOP] More private algorithms for DNSSEC
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: Mon, 21 Mar 2022 07:43:56 -0000

On Sun, 20 Mar 2022, Paul Hoffman wrote:

> Greetings again. I have created a new, very short draft to add more private use algorithms to DNSSEC.
>   https://datatracker.ietf.org/doc/draft-hoffman-more-private-algs/
> The abstract says:
>   RFC 4034 allocates one value in the IANA registry for DNSSEC
>   algorithm numbers for private algorithms.  That may be too few for
>   experimentation where multiple yet-to-be-assigned algorithms are
>   used.  This document assigns seven more values for this use case.
>
> That's about it. This is quite low priority for now, but might become more important as people start to experiment with multiple pre-standard post-quantum algorithms at the same time.

I agree with the draft that this is a good idea and will become a
requirement in the near future.

I would like to see some more clarity in the IANA Considerations
section that just lists the value there and the values requested,
with a link to the actual Registry discussed.

Paul