Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard

Paul Wouters <paul@nohats.ca> Mon, 04 March 2019 16:05 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 CD253130FC7 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 08:05:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S0eOyH1OHg_P for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 08:05:26 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 2248B12F1AC for <dnsop@ietf.org>; Mon, 4 Mar 2019 08:05:26 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 44ClH72yN4zCqr; Mon, 4 Mar 2019 17:05:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1551715523; bh=UGTUSfdsSx7VXT70HWSUpO/+rlZ/NMIxKYdGr2RdmmI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=QVMZXsIL6WKIstGQfLdzzTI4QlSppCdIKdse4hiEY9MErGHS+kxgFAhYYaI5odaJY aJZwB8AypR2ypNssbagvaVhj2H+Jud6s88b1EOxXyYegTL8J9Bq56gX4+lF4x8BipH BmKFKqHamPmCGPIk4WQ65D/efkp+C01JneNk+xrY=
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 aUEK7V7oQaBh; Mon, 4 Mar 2019 17:05:22 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 4 Mar 2019 17:05:21 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id CB1EA5E4BA8; Mon, 4 Mar 2019 11:05:20 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca CB1EA5E4BA8
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C3DA7411601C; Mon, 4 Mar 2019 11:05:20 -0500 (EST)
Date: Mon, 4 Mar 2019 11:05:20 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Warren Kumari <warren@kumari.net>
cc: Peter van Dijk <peter.van.dijk@powerdns.com>, dnsop <dnsop@ietf.org>
In-Reply-To: <CAHw9_iLVfL4icD_AsPF6fQf=EWPvb1FvBQPVpAicFMracVALag@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1903041103110.9251@bofh.nohats.ca>
References: <155008617010.9548.7174990317415826094.idtracker@ietfa.amsl.com> <D48A348E-A4C0-470F-BE55-B9441AF8F5ED@powerdns.com> <CAHw9_iLVfL4icD_AsPF6fQf=EWPvb1FvBQPVpAicFMracVALag@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9Fjr6Qqu3K_mL-vt4u2_YO-XefI>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-algorithm-update-05.txt> (Algorithm Implementation Requirements and Usage Guidance for DNSSEC) to Proposed Standard
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: Mon, 04 Mar 2019 16:05:29 -0000

On Mon, 4 Mar 2019, Warren Kumari wrote:

> So, my plan is to 1: ask the authors to please swap the Y to an N as below and 2: progress the document with the hope that this
> section will survive the publication process. 

But I do not hope that.

> The March telechats are often really full - ADs who are leaving the IESG try and get old / stuck work finished and off their
> plate - and so this would likely only show up on the 2019-04-11 telechat -- so if anyone really objects to this being (attempted
> to be) left in, please shout.

I think it should not be in the document. For one, it will be quickly
outdated information over the years as implementations release new
versions. Second, it will lead to people putting these sections in for
marketing. I think RFCs should avoid naming products whenever possible.

I'm happy to do a new rev that includes an improved "remove me" note to
IANA and the pdns update.

Paul