IETF Logo Mail Archive

Re: [DNSOP] [Ext] Murray Kucherawy's No Objection on draft-ietf-dnsop-dnssec-iana-cons-04: (with COMMENT)

Paul Hoffman <paul.hoffman@icann.org> Sun, 03 October 2021 16:39 UTC

Return-Path: <paul.hoffman@icann.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 5424B3A07F0; Sun, 3 Oct 2021 09:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 6mE1CqRKTygg; Sun, 3 Oct 2021 09:39:47 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 74AB73A07F3; Sun, 3 Oct 2021 09:39:47 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa3.lax.icann.org (8.16.0.43/8.16.0.43) with ESMTPS id 193Gdg4u032019 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 3 Oct 2021 16:39:43 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.922.13; Sun, 3 Oct 2021 09:39:41 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0922.013; Sun, 3 Oct 2021 09:39:41 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "Murray S. Kucherawy" <superuser@gmail.com>
CC: The IESG <iesg@ietf.org>, dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] Murray Kucherawy's No Objection on draft-ietf-dnsop-dnssec-iana-cons-04: (with COMMENT)
Thread-Index: AQHXuA5iZ0wQ9agWUUysVf2t/Qq//qvB78KA
Date: Sun, 03 Oct 2021 16:39:41 +0000
Message-ID: <52AEFA9E-5F08-45BF-8825-F50F43C86AF5@icann.org>
References: <163323498843.11274.9452563933880073914@ietfa.amsl.com>
In-Reply-To: <163323498843.11274.9452563933880073914@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_8539D7C5-7C4C-41B5-994C-82F3384A3907"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.391, 18.0.790 definitions=2021-10-03_07:2021-10-01, 2021-10-03 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qOH4Wv_8JMpaCBEmM9KN1CQzzDo>
Subject: Re: [DNSOP] [Ext] Murray Kucherawy's No Objection on draft-ietf-dnsop-dnssec-iana-cons-04: (with COMMENT)
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: Sun, 03 Oct 2021 16:39:54 -0000

On Oct 2, 2021, at 9:23 PM, Murray Kucherawy via Datatracker <noreply@ietf.org> wrote:
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> In Security Considerations, it says:
> 
>   Security decisions about
>   which algorithms are safe and not safe should be made by reading the
>   security literature, not by looking in IANA registries.
> 
> Should this document request addition of a note to this effect on the registry page itself?

I don't think so, because it is true of every IANA registry page that lists crypto algorithms. Or, if you feel such a notice should be this registry, it should probably be in every similar registry, and that could be enacted by a separate Internet Draft that lists the myriad crypto algorthms.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email