Re: [art] Call for Consensus: Re: On BCP 190

John C Klensin <john-ietf@jck.com> Tue, 20 August 2019 16:38 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 256E212096D for <art@ietfa.amsl.com>; Tue, 20 Aug 2019 09:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 CsRcei0rlgQH for <art@ietfa.amsl.com>; Tue, 20 Aug 2019 09:38:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A533120106 for <art@ietf.org>; Tue, 20 Aug 2019 09:38:04 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1i078w-000L1J-UX; Tue, 20 Aug 2019 12:37:58 -0400
Date: Tue, 20 Aug 2019 12:37:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ben Campbell <ben@nostrum.com>
cc: Mark Nottingham <mnot@mnot.net>, Jacob Hoffman-Andrews <jsha@letsencrypt.org>, Adam Roach <adam@nostrum.com>, Devon O'Brien <devon.obrien@gmail.com>, ART Area <art@ietf.org>
Message-ID: <C68CC002B6882808607F9F25@PSB>
In-Reply-To: <52942FE2-6C74-4E45-A077-B3004A3FC6D3@nostrum.com>
References: <58BF6171-03BB-4F83-940F-3A101EFDD67F@mnot.net> <CAN3x4Q=Jo1uBvfCG6CSrociYgdG+E4jq+4cB1txPjgboth2q9g@mail.gmail.com> <372FA049-7B33-4981-A0E0-41BD454CB770@mnot.net> <CAN3x4QmJsfx48MdhcBB+XWX+vfv=skSR2Z6kNPBWGVobvzNuFA@mail.gmail.com> <004601d5450d$62b33220$28199660$@acm.org> <CAN3x4Q=XR+=ugv6HEmOgsA6v64GkQ+4u-Hk+OBQ0Lp9jn-Cy=A@mail.gmail.com> <D154BA24-5027-4FAF-8779-CBA5533D24A1@mnot.net> <3000e948-14e6-80d2-e8e6-766d309c361c@nostrum.com> <ed64dc0e-5b71-63ec-cbac-85673c51109a@nostrum.com> <301DF34E4C5601BCA4D2BCBF@PSB> <A27BC0BC-B60A-44AD-B75B-859C71B0706A@mnot.net> <E02E5D4BA18EF0155B0EAE95@PSB> <52942FE2-6C74-4E45-A077-B3004A3FC6D3@nostrum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/1LPo9jix-FgiP8CejXEFxi5y1cU>
Subject: Re: [art] Call for Consensus: Re: On BCP 190
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2019 16:38:06 -0000


--On Tuesday, August 20, 2019 10:30 -0500 Ben Campbell
<ben@nostrum.com> wrote:

> Commenting on just one point (I am agnostic on the others):
> 
>> On Aug 20, 2019, at 5:55 AM, John C Klensin
>> <john-ietf@jck.com> wrote:
>> 
>> Mark,
>> 
>> Happy to wait, but a few comments going forward:
>> 
>> * For Adam, there is some question in my mind about whether it
>> is desirable to clear a Discuss based on a plan about a
>> document that has not been written yet, that has no firm
>> schedule, etc.
> 
> In this case, I think Adam is saying that we don't have
> consensus that the draft in question is really wrong.
> 
> It could take months to years to figure out what we really
> want BCP190 to say. I agree with Adam that we should not hold
> current work hostage to that. Holding up work due to
> non-critical externalities is a very good way to kill momentum.
> 
> […]

Then we are very much in agreement.  A different way of
expressing the concern about protocol-restricting documents that
are treated as requirements is that other work gets held up
while we try to converge on protocol models, philosophy of
protocols, or other externalities that become critical only if
we make them critical... and doing that is generally a bad idea.
Holding up work that way not only kills momentum, but may cause
critical people to simply give up and go away while others
debate the angel population of the heads of various pins.

best,
    john