Re: [DNSOP] [internet-drafts@ietf.org] New Version Notification for draft-hardaker-dnsop-intentionally-temporary-insec-00.txt
Wes Hardaker <wjhns1@hardakers.net> Thu, 25 February 2021 18:44 UTC
Return-Path: <wjhns1@hardakers.net>
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 3D1F33A1E86 for <dnsop@ietfa.amsl.com>; Thu, 25 Feb 2021 10:44:45 -0800 (PST)
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=unavailable 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 GwoVM0VN1YHJ for <dnsop@ietfa.amsl.com>; Thu, 25 Feb 2021 10:44:44 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25C003A1EA6 for <dnsop@ietf.org>; Thu, 25 Feb 2021 10:44:43 -0800 (PST)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 457DB27BD5; Thu, 25 Feb 2021 10:44:43 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>, dnsop <dnsop@ietf.org>
References: <yblzgzxceqt.fsf@w7.hardakers.net> <e6cf46e1-b88f-e5c1-d30e-ed8045ec76fe@nic.cz> <CAHbrMsBAZEL7_E8rJ8wWQ17679xJeeHaJkk-POEbELNT55=UOw@mail.gmail.com>
Date: Thu, 25 Feb 2021 10:44:43 -0800
In-Reply-To: <CAHbrMsBAZEL7_E8rJ8wWQ17679xJeeHaJkk-POEbELNT55=UOw@mail.gmail.com> (Ben Schwartz's message of "Tue, 23 Feb 2021 13:20:38 -0500")
Message-ID: <yblpn0o9eck.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gKYK5uXUh31Ra15waNc9pVt4FrI>
Subject: Re: [DNSOP] [internet-drafts@ietf.org] New Version Notification for draft-hardaker-dnsop-intentionally-temporary-insec-00.txt
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: Thu, 25 Feb 2021 18:44:51 -0000
Ben Schwartz <bemasc=40google.com@dmarc.ietf.org> writes: > I also think that this is not appropriate as a Best Practice. I would suggest > reversing this draft to make it operational guidance to implementers about how to > enable compliance with RFC 6781 Section 4.1.4. Thanks for the feedback from both of you. I think I could certainly argue it could be considered best practice (IE, it is best practice to update your algorithm -- it's time to move away from RSASHA1), and if this is the only way you can pull it off.... But, let's assume we want to remove the notion of "best practice", then it leaves what to publish it as. Maybe informational would leave everyone more comfortable? -- Wes Hardaker USC/ISI
- [DNSOP] [internet-drafts@ietf.org] New Version No… Wes Hardaker
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Vladimír Čunát
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Ben Schwartz
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Wes Hardaker
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Ben Schwartz
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Viktor Dukhovni
- Re: [DNSOP] [internet-drafts@ietf.org] New Versio… Matthew Pounsett