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

Warren Kumari <warren@kumari.net> Mon, 04 March 2019 16:34 UTC

Return-Path: <warren@kumari.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 5405912D84C for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 08:34:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 JOmIPz0QuRyn for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 08:34:41 -0800 (PST)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B4151295EC for <dnsop@ietf.org>; Mon, 4 Mar 2019 08:34:41 -0800 (PST)
Received: by mail-wr1-x432.google.com with SMTP id g12so6267511wrm.5 for <dnsop@ietf.org>; Mon, 04 Mar 2019 08:34:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hhNjyw7NIJVpPMh0F+Jdgp20w8rFZMlOwny7/WCFY+s=; b=K7YnGdxSamuk8DbAChnGrzXf3GvHfSDkP/4GF77t2NMDr++8768H6yJ4ofcI9qfHd8 dtE6hAJ/gwYW0ko4hI9w67lUUZ2cxwFOIGXInLZn+LOM5HAqbuoB/d+X3cYKVdGzRv4r ZujH7AaNnfz+wWNFFxVml+4ha0vilo7UCNSDzwG55eHim+1QVdkgVgpGkPijPX23tY+F NAWnoeAL64DU/yVFzD1ZNc4rhb+IrE+Clt07lPIUu97poPA89snlo/1gygaanRszEsef 9kOYM65rYBbo3qfd/EysTQT4zBQlHG3GrfSVLuuAEhMHnlpAwjEqYQpZBxeBZC6Vemo/ Rfzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hhNjyw7NIJVpPMh0F+Jdgp20w8rFZMlOwny7/WCFY+s=; b=mvZMGSraPtvZ1nxWE4tKozUKkbRh5TcPnxMu+dFjRc4UWVmxrqkrhttGVfk5Cs4Yv+ l/0ASuNPjLNgllEZhz2K9nup09kPTb+oM4rwzGVGRhvktkELffwxR849Fai37gq0lcD8 YaGe4WhzGuIXcHuM9ceZr0uWo0jqIjDPSM3Psbv2dT1ro3HkxbesWTYz33gRysuGitu9 w5n49AVJ3RCQc6j+8m3D3pX39WkDg+EaPB3jXB+7l91wHAV3P9QhVdSY+CfUr6rzfNzl 0u33uVZmzMFeHY/l+rSOFMivwxIpUvnOWNGg0YdZN/jJGNCnjQPc6MuQZX8DSWn57o3B wTEA==
X-Gm-Message-State: APjAAAUyu9tTNp1W5zHYFOYpZZpgI3EyNEl5UX+LO9mphKXHi38eC/SX fX3NjEYWfMk9UoikxOACclBzgFjInH8EEtb3lP7AZesT
X-Google-Smtp-Source: APXvYqwM9vfUHNMGe7aWk6l5peuudq42mJjloBYscYL3B+Vhu9r2WrjtQZjy3DwYqWK1TvfE1/kevJAkyGUWcBj6+hM=
X-Received: by 2002:a5d:4585:: with SMTP id p5mr14365851wrq.178.1551717279215; Mon, 04 Mar 2019 08:34:39 -0800 (PST)
MIME-Version: 1.0
References: <155008617010.9548.7174990317415826094.idtracker@ietfa.amsl.com> <D48A348E-A4C0-470F-BE55-B9441AF8F5ED@powerdns.com> <CAHw9_iLVfL4icD_AsPF6fQf=EWPvb1FvBQPVpAicFMracVALag@mail.gmail.com> <alpine.LRH.2.21.1903041103110.9251@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1903041103110.9251@bofh.nohats.ca>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 4 Mar 2019 11:34:03 -0500
Message-ID: <CAHw9_iJE89H2B39pTucWFuAUmNeFNr8QTeOFMPWpqi55mYp57g@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Cc: Peter van Dijk <peter.van.dijk@powerdns.com>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000384ce90583475523"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Bo7H4Xj7RMbKB5k1LswZrplJuKs>
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:34:44 -0000

On Mon, Mar 4, 2019 at 11:05 AM Paul Wouters <paul@nohats.ca> wrote:

> 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.
>
>
That works for me too...
W



> Paul
>


-- 
I don't think the execution is relevant when it was obviously a bad idea in
the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair of
pants.
   ---maf