IETF Logo Mail Archive

Re: [DNSOP] Paul Wouters' Discuss on draft-ietf-dnsop-nsec3-guidance-08: (with DISCUSS and COMMENT)

Paul Wouters <paul@nohats.ca> Tue, 24 May 2022 21:38 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 2037DC2B5A91; Tue, 24 May 2022 14:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id veP7EhVyqga3; Tue, 24 May 2022 14:38:13 -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 74921C2B551D; Tue, 24 May 2022 14:37:56 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4L76xY5dm1z38Y; Tue, 24 May 2022 23:37:53 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1653428273; bh=wtBfdYTwcdG/QJg7i5W1SXY47eMr3Oe2pLKPe7lG3no=; h=From:Date:Subject:Cc:To; b=qZlE5QENWzWp7zfSyJ93pbAuMH1iCoPnzcusNpF7hVjyYYkCa0s8UigvdlecjP2+r M7HBUEijys1wt5cc2TnREJZk7thGGf8zOu19hF5tjcd9x6sU5XoNYgqNdyizkoBney mhrk7H1h+AMchegNVogJWJ9tAKbqU581sowhl0lI=
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 ilGKfhL_Zp_x; Tue, 24 May 2022 23:37:53 +0200 (CEST)
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; Tue, 24 May 2022 23:37:52 +0200 (CEST)
Received: from smtpclient.apple (unknown [193.110.157.208]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id D2D7F3736C6; Tue, 24 May 2022 17:37:51 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Paul Wouters <paul@nohats.ca>
Mime-Version: 1.0 (1.0)
Date: Tue, 24 May 2022 17:37:50 -0400
Message-Id: <A922FB84-9E2C-46FC-B7BA-83F6B0DDB4FC@nohats.ca>
Cc: Paul Wouters via Datatracker <noreply@ietf.org>, The IESG <iesg@ietf.org>, Paul Wouters <paul.wouters@aiven.io>, draft-ietf-dnsop-nsec3-guidance@ietf.org, dnsop-chairs@ietf.org, DNSOP@ietf.org, tjw.ietf@gmail.com
To: Wes Hardaker <wjhns1@hardakers.net>
X-Mailer: iPhone Mail (19E258)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QqmjMwwJh6WDIXlEMbRZWeJlfJY>
Subject: Re: [DNSOP] Paul Wouters' Discuss on draft-ietf-dnsop-nsec3-guidance-08: (with DISCUSS and COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
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, 24 May 2022 21:38:17 -0000

Thanks for the changes Wes. Looks good to me.

I didn’t see in this email whether an Update: clause will be added ? Perhaps this was discussed elsewhere ?

Paul

Sent using a virtual keyboard on a phone

> On May 24, 2022, at 12:58, Wes Hardaker <wjhns1@hardakers.net> wrote:
>

v2.23.0 | Report a Bug | By Email