Re: [DNSOP] [Ext] Call for Adoption: draft-hoffman-dnssec-iana-cons

Stephen Farrell <stephen.farrell@cs.tcd.ie> Mon, 04 January 2021 13:04 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 515C33A0D14 for <dnsop@ietfa.amsl.com>; Mon, 4 Jan 2021 05:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level:
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 bXbobAgFRHuQ for <dnsop@ietfa.amsl.com>; Mon, 4 Jan 2021 05:04:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7360C3A0CF5 for <dnsop@ietf.org>; Mon, 4 Jan 2021 05:04:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0083CBE47; Mon, 4 Jan 2021 13:03:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhaBvzW8OiJz; Mon, 4 Jan 2021 13:03:57 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E9D57BE56; Mon, 4 Jan 2021 13:03:16 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1609765397; bh=kwlENlcKXxHd58vcnDlFVkJeAtKA33lRk2nxRNCnL9U=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=FPkUWa6dwrt19B2J9fwuG1B5Dqa5I/aPBh8ScNj4Za5gq7/ACgqcKYAl9Zz5BPKtM Q0EIXdaSID5WjL3wEflt/FOhNKBHjxm8pTTVrDHFOlNrpLPLNGVsIaUH0ylySHifhj 6LOcgUdqLyXn7437Pnp7sgqwV2Fl2wK0TbJ433Ow=
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>, Paul Hoffman <paul.hoffman@icann.org>
Cc: dnsop <dnsop@ietf.org>
References: <CADZyTkn1QuvjencR8+wVtQ9bzQHJT9JXXNku1LPr3YRmRt4KQg@mail.gmail.com> <2E8229BE-E764-4C29-A258-8C469717E38A@nohats.ca> <CABcZeBMr5Muijx5V7Se1UcxTB9DbAzF1iXZb7_FzEGfw982x8w@mail.gmail.com> <65e3288d-bdfe-ff10-2fbc-63a5d2dd9508@cs.tcd.ie> <797AAE77-2D50-4189-81D8-44BA495146F5@icann.org> <546e60c6-b109-8552-dfb4-7d3ba2ecbc71@cs.tcd.ie> <E58B4013-9491-43ED-83C9-250FF7647570@icann.org> <0746397c-ed85-429c-ff6e-a4a559520e86@cs.tcd.ie> <487928351.1557.1609759876775@appsuite-gw1.open-xchange.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <60ba1f68-b07f-7a06-539f-60ce442ffbff@cs.tcd.ie>
Date: Mon, 04 Jan 2021 13:03:15 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <487928351.1557.1609759876775@appsuite-gw1.open-xchange.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="JkI8F1uDqNfi2Mvz1S5ZLHecWEMpFUOvV"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZnUsd0f5iDXIUlHkxRjU4oh-H5E>
Subject: Re: [DNSOP] [Ext] Call for Adoption: draft-hoffman-dnssec-iana-cons
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, 04 Jan 2021 13:04:07 -0000

Hiya,

On 04/01/2021 11:31, Vittorio Bertola wrote:
> We could ask the proponents of new algorithms for information on
> current or expected usage. 

WRT GOST, we're not really talking about an algorithm but
rather a national crypto standards scheme that selects sets
of algorithms. For such things, whether from Russia or the
US or anywhere, I think it's quite fair to ask "how has
version N deployment gone?" as part of considering how to
handle version N+1. Indeed, it'd seem wrong not to ask and
get an answer.

And "how to handle" isn't always "adoption" but could as
I said result in deprecating version N if nobody really
cares about it - in such a case that'd help implementers
and better reflect reality.

Cheers,
S.



> However, if adoption is relevant to any
> kind of decision on what to do with an algorithm proposal, this
> should better be formalized somewhere and applied evenly to all
> algorithms that may appear in the future. Personally, I think that
> some expectation of adoption would be useful not to clutter the list
> of algorithms, but the threshold should be quite low.