[spring] SPRING Chairs observation on WG calls for consensus

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 14 March 2022 20:14 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28193A14FE for <spring@ietfa.amsl.com>; Mon, 14 Mar 2022 13:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 WUG5Nx6zw5MY for <spring@ietfa.amsl.com>; Mon, 14 Mar 2022 13:14:45 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 41DF73A14F8 for <spring@ietf.org>; Mon, 14 Mar 2022 13:14:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4KHSSN4ng9z1pNDJ for <spring@ietf.org>; Mon, 14 Mar 2022 13:14:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1647288884; bh=g0ShgouO8GKv8QTjAx+R755hlQ/ByJxSHVOJ2Hp+syA=; h=Date:From:Subject:To:From; b=dCh5HOIK0zeAvwxC+4aoVsCYwK8Ck3BY2d17vzyLaaP2XCwX/ti7yg2Dyiz5GCf/X cujCJJmmo0EDpT1AeURnxuFPX6cLn3qZo0nLf9SfZ7ysMnHRDxlgF2wKX5jifuMyJp rZDCLeUds2GW10mIBgQI5hMSFirKP5Q5jtEe28fo=
X-Quarantine-ID: <S5U2H0mi2r8S>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4KHSSN1dQvz1pMJs for <spring@ietf.org>; Mon, 14 Mar 2022 13:14:43 -0700 (PDT)
Message-ID: <fe08a4e9-fc0d-e803-13ee-b55adb658bdf@joelhalpern.com>
Date: Mon, 14 Mar 2022 16:14:42 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
From: "Joel M. Halpern" <jmh@joelhalpern.com>
To: "spring@ietf.org" <spring@ietf.org>
Content-Language: en-US
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/72u_OAlUg_nTh372mEvSEcUw1i8>
Subject: [spring] SPRING Chairs observation on WG calls for consensus
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2022 20:14:50 -0000

In discussion with chairs of other routing working groups, it was noted 
that there is sometimes confusion or misunderstanding about what is 
sought when the chairs conduct adoption calls and WG last calls.

The top line is that we are looking for working group support and review.

In the case of adoption we are looking for whether the working group 
considers the document a good starting point for the problem, whether 
working group participants want to work on the problem, and whether 
there is enough active participation to support and review the work.
This is also why we find "+1" response to be unhelpful in judging this.

For working group last call, we are looking for whether the working 
group thinks the document is in good enough shape to be sent to the IESG 
and the IETF community.

In particular, we assume that the authors of a document are in support 
of it.  What is of interest to us when we issue these calls is about the 
opinion of the rest of the working group.  Working group adoption and 
completion requires that more than just the author team supports the 
work.  It needs broad working group support and review.

Yours,
Bruno, Jim, and Joel