Re: [DNSOP] [Ext] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost

Paul Hoffman <paul.hoffman@icann.org> Tue, 30 April 2024 23:06 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 984C0C1654F2 for <dnsop@ietfa.amsl.com>; Tue, 30 Apr 2024 16:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcemYfdCE_z9 for <dnsop@ietfa.amsl.com>; Tue, 30 Apr 2024 16:06:40 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 15455C14F747 for <dnsop@ietf.org>; Tue, 30 Apr 2024 16:06:40 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa4.dc.icann.org (8.18.1.2/8.18.1.2) with ESMTPS id 43UN663S016977 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 30 Apr 2024 16:06:07 -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 Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Tue, 30 Apr 2024 16:06:34 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1258.028; Tue, 30 Apr 2024 16:06:34 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Paul Wouters <paul@nohats.ca>
CC: dnsop <dnsop@ietf.org>
Thread-Topic: [DNSOP] [Ext] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
Thread-Index: AQHamf9cJyDt9qQ2kUys4xI5Z4PfLrF/p0GTgAB56YCAAANigIAABNEAgAE/KiSAAHgmgIAABScAgAABnQA=
Date: Tue, 30 Apr 2024 23:06:34 +0000
Message-ID: <89A57AB9-63F4-4E91-9A57-C343EC197E2F@icann.org>
References: <4907A4B7-1EAE-460D-91E8-4F7D292C7302@icann.org> <8BECB257-E7FF-411C-B0E5-C63D07AE1D6E@nohats.ca>
In-Reply-To: <8BECB257-E7FF-411C-B0E5-C63D07AE1D6E@nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <B28F9B2D1858094393C4612F959652C8@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1011,Hydra:6.0.650,FMLib:17.11.176.26 definitions=2024-04-30_14,2024-04-30_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/rg7dxpXLOrex458p_lZOGvt1TP0>
Subject: Re: [DNSOP] [Ext] Call for Adoption: draft-hardaker-dnsop-rfc8624-bis, must-not-sha1, must-not-ecc-gost
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 30 Apr 2024 23:06:40 -0000

On Apr 30, 2024, at 16:00, Paul Wouters <paul@nohats.ca> wrote:
> 
> On Apr 30, 2024, at 18:42, Paul Hoffman <paul.hoffman@icann.org> wrote:
>> 
>> This cull-because-of-low usage thread incorrectly assumes that the DNS is flat instead of a hierarchy. The last I saw, there are 14 TLDs who use RSASHA1. Advancing this draft as-is means that all of the zones under those TLDs would be completely wiped out as well. Or maybe that's what the WG wants?
> 
> Not wiped out. Being made insecure (versus part of the world only treating them insecure)

Fair point. "Made their efforts to use DNSSEC useless" would have been a better way to say it.

> It’s worth contacting them for timelines of migration away from SHA1, as RFC 8624 is five years old and that already told them to start moving.
> 
> Is that something within the realm of ICANN? Perhaps the DNS Tech Day ?

You ask those questions sounding as if ICANN staff had not already done so.

> Or perhaps a liaison statement from IETF to ICANN ?

Such a statement would be quite a different action than the threat of making all the zones under many TLDs go insecure. This thread is about WG adoption of a draft that would do the latter.

--Paul Hoffman