Re: Status of this memo

Keith Moore <moore@network-heretics.com> Tue, 27 April 2021 16:35 UTC

Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E37CD3A160A for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 09:35:42 -0700 (PDT)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_NONE=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=messagingengine.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 DDnMNWY8uiiK for <ietf@ietfa.amsl.com>; Tue, 27 Apr 2021 09:35:38 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DE643A15FF for <ietf@ietf.org>; Tue, 27 Apr 2021 09:35:38 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 22F832127 for <ietf@ietf.org>; Tue, 27 Apr 2021 12:35:33 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 27 Apr 2021 12:35:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=8BiTizi9bPErc+h0bAlgvqbRBBU2xHdYDmnkZhaBc CY=; b=mhQWRXaEsIuMeFYS5mBiVvZoUku0W/1KpyxO08x6TugkWaouijVxZgdPA 2dqIpuBMDhHSa1gtwQpqUzLD+PLtz+cfp35PFrtXy6CWuKvAmIgqQst8behTUTcd wWXkZgjTZlZgWxhZ2L0oli0UnNAeWgcTgbO0qLdQ3pWawt5+MdNmBnwzn6AkQyJ3 lIjWjWE2034ukgVQ44VaBG3Tb+NSwFTFoX8GFCCua5qHfEshnh7IzBHTuz5bkcUZ TB4D6BwBcetTDCn6DqVlJibvfK1Dv9vDl685Rc4XcyIyXZsiHsK6iMv01qizbPwZ GyF5dQBy5bcbI3CCmmmI3VbqDi+kw==
X-ME-Sender: <xms:VD2IYKWAXQWP3v0s1qQjJyNutWncXtjEakWlIREpqOE5ldqOE5iymQ> <xme:VD2IYGkgdkC5n7loajw_3tKjdOor7AJkKd8iWduf41swJ_4yzE46V1GChNqigC_SM Tzd4silaUY67g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvddvtddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesth ekredttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvght fihorhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedthe efgfefgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedvfedr uddvgedruddtrddujedtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:VD2IYOZ6lnl_XZ8iAJQvboFhupl2XBheprhp6yQ0iHsHPlPw8ji1Pw> <xmx:VD2IYBVkaPyRq7Pv8U4D1nRaYZLS_8QjG5aLTSCzFEkJHc7XTt3CrQ> <xmx:VD2IYEk__ffeD-KR1jrzYRZwQglwMV3RDWR9IK1lXzH_65M1rQCyww> <xmx:VD2IYCkb24EdWDkheUvP39gBsBYstuKyHGQzdeLaaaWFwRLyg-wRTg>
Received: from [192.168.1.121] (23-124-10-170.lightspeed.knvltn.sbcglobal.net [23.124.10.170]) by mail.messagingengine.com (Postfix) with ESMTPA for <ietf@ietf.org>; Tue, 27 Apr 2021 12:35:32 -0400 (EDT)
Subject: Re: Status of this memo
To: ietf@ietf.org
References: <376f83f0-89a3-cd0e-1792-c8434bd8a5d2@gmail.com> <9ACE59FA-30B6-475A-AF6B-4B874E4A2788@eggert.org> <1804294246.5904.1619512137931@appsuite-gw2.open-xchange.com> <D653D3B2-7666-409A-B856-2A4B1BA958CA@eggert.org> <3DBB64B1-40B8-4BC3-B66C-7F9B7F395874@akamai.com> <b5210c71-9500-3dba-05d2-4ae1c6ad16e9@network-heretics.com> <CAA=duU1VJs2vCE=uCF=fXO7FNedn9yPAaZWTgcaAiHTexA8uWA@mail.gmail.com> <2c48c55c-fd37-6ced-e025-707eb145a27b@nokia.com> <2D1F890C-1BC3-4E19-85C3-EEA522577275@tzi.org>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <f1281b01-ed96-6350-eb9e-d0207b8d1d7c@network-heretics.com>
Date: Tue, 27 Apr 2021 12:35:31 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <2D1F890C-1BC3-4E19-85C3-EEA522577275@tzi.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lCTly4Tz8VHvjphIYjaXamtCyjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Apr 2021 16:35:43 -0000

On 4/27/21 12:17 PM, Carsten Bormann wrote:

> I think Keith is recollecting some experience with WGs where the chairs used the WG document process to run the show without much regard to the WG’s opinions.

Yes, I've seen that happen.  But I've also seen something subtly 
different happen, which is to ask the WG for "consensus" before there's 
really been time for participants to have informed opinions, and then 
(sometimes) treat that "consensus" as if it were set in stone for the 
lifetime of the WG.

What I've seen repeated at many f2f WG meetings:  "how many people have 
read the draft?" (a few hands raised).   and later: "how many people 
support adoption of this document?"   (many more hands raised).   People 
don't even know what they're expressing an opinion on, but they want to 
get on with it!

IMO consensus is meaningless if obtained prematurely, just as consensus 
is meaningless if the WG leaders effectively dictate the outcome.    I 
don't think we should be asking for "consensus" about anything on 
revision -00 documents.    What seems more appropriate is that as a 
document evolves, there's increasing confidence in the WG that the 
document is approaching the criteria for its intended status.   And any 
indications of the status of the document (to the extent that they're 
necessary) should reflect that degree of confidence or lack thereof.   
But I don't think it's helpful to be too formal about this, so rather 
than try to come up with some scheme to express that level of 
confidence, I recommend that we just wait until after WGLC to claim 
consensus of the WG.

> In that case, I’d say: get new chairs!  We don’t need to make the process capable of coping with this abuse.

It's pretty difficult to get chairs replaced.   It looks bad for the 
people who appointed them.   At best, you might get their AD to have a 
word with them.

Keith