IETF Logo Mail Archive

[DNSOP]Re: [Ext] Re: Questions before adopting must-not-sha1

Kim Davies <kim.davies@iana.org> Wed, 08 May 2024 20:24 UTC

Return-Path: <kim.davies@iana.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 C84ADC1840C2 for <dnsop@ietfa.amsl.com>; Wed, 8 May 2024 13:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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 oXV2X0T3DqXj for <dnsop@ietfa.amsl.com>; Wed, 8 May 2024 13:24:14 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1:81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2565DC180B7D for <dnsop@ietf.org>; Wed, 8 May 2024 13:24:14 -0700 (PDT)
Received: from KIDA-8939.local (unknown [10.32.60.188]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.lax.icann.org (Postfix) with ESMTPS id 5AEFAE1725; Wed, 8 May 2024 20:24:13 +0000 (UTC)
Date: Wed, 08 May 2024 13:24:12 -0700
From: Kim Davies <kim.davies@iana.org>
To: John Levine <johnl@taugh.com>
Message-ID: <ZjvfbC5NTYUX1FIy@KIDA-8939.local>
References: <856DB748-7D07-4FFF-90B6-CB087588A41A@strandkip.nl> <20240501171246.74AE389D40DD@ary.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20240501171246.74AE389D40DD@ary.local>
Message-ID-Hash: YJWYJZAXGP3WJNDYAVMLM6TMLB6IVAQF
X-Message-ID-Hash: YJWYJZAXGP3WJNDYAVMLM6TMLB6IVAQF
X-MailFrom: kim.davies@iana.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: dnsop@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP]Re: [Ext] Re: Questions before adopting must-not-sha1
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iKCEx0X3aG9UBetcv54PzDljjwc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Quoting John Levine on Wednesday May 01, 2024:
> 
> We all know the people at IANA who run .INT. If we can't persuade them
> that this has becomes a problem that needs to be fixed, how urgent is
> it likely to be?

No persuasion necessary. There has been an ongoing project to update
the signing approach for all zones maintained on ICANN infrastructure,
which includes .INT. I asked the team and the implementation for .INT is
planned to happen over the next month.

kim

v2.46.0 | Report a Bug | By Email | System Status