[Gendispatch] Re: [procon] dispatching draft-carpenter-rfc7221bis

S Moonesamy <sm+ietf@elandsys.com> Wed, 26 March 2025 10:14 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 52E1712853A4 for <gendispatch@mail2.ietf.org>; Wed, 26 Mar 2025 03:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xm-A_iIhB3-m for <gendispatch@mail2.ietf.org>; Wed, 26 Mar 2025 03:14:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 68E871285393 for <gendispatch@ietf.org>; Wed, 26 Mar 2025 03:14:10 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.145.2]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 52QADsPb012680 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Mar 2025 03:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1742984047; x=1743070447; i=@elandsys.com; bh=mM8g3Y+HNgIBkNx8FjO1ZB3ubp5yK4z7KhVr5it4kjo=; h=Date:To:From:Subject:In-Reply-To:References; b=sSmG3xJciuNxpAjWekJ4+gzYuxhxDIB+Zk1YgUKkCeSVIPmznGYjJrCjGGIY8QHht 9x1FaZtExOeVzj2Jg2wm/8fnbshdoFeDCXJHQcEUwZC4jQ/fIUxFPrLJQwNlx3TCte y3jNQcEom4x7wao7Qws/12GmHrqSXIfXQJCcEZKA=
Message-Id: <6.2.5.6.2.20250326021416.15e67690@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Mar 2025 03:07:19 -0700
To: Carsten Bormann <cabo@tzi.org>, gendispatch@ietf.org, Michael Richardson <mcr+ietf@sandelman.ca>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <1378215.1742979216@dyas>
References: <1212677.1742733409@dyas> <IA1PR17MB6421A795D03F694B92CBF9EDCDA52@IA1PR17MB6421.namprd17.prod.outlook.com> <E86893FA-05FC-48E9-9100-99FFC98C7C80@tzi.org> <1308918.1742898219@dyas> <1B003401-4E91-4087-BA13-3CBBE130C6AC@tzi.org> <1378215.1742979216@dyas>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-ID-Hash: E27YGNFR6N3LW7DKTE7TB4QWYWW26ZOV
X-Message-ID-Hash: E27YGNFR6N3LW7DKTE7TB4QWYWW26ZOV
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: [procon] dispatching draft-carpenter-rfc7221bis
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/JytBGmqgLqu1intY9E9VgEDTPqE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

Hi Michael, Carsten,
At 01:53 AM 26-03-2025, Michael Richardson wrote:
>When it comes to adopting documents, the WG chairs are 100% responsible.
>It's fiat.  THIS PROCESS IS NOT WELL KNOWN.
>Instead, we have a poorly understand (by WG chairs) cargo culting of asking
>people if they support a document.  It does not produce good results, and
>somehoe turns into voting.
>I've even had chairs ask why I didn't +1 my own document.
>(In 2020 several people were surprised that the above was NOT a 
>documented process)

I agree that the process is poorly understood.  Sometimes, there is a 
call for objections to adopting a draft.  That is not one of the 
considerations which RFC 7221 (Section 2.2) suggests.

I have seen authors "vote" on the adoption of their drafts.  There is 
an assumption that the authors of a draft will be in favour of 
adoption of their draft.  The authors are free to "vote".  That vote 
is not supposed to be counted as an expression of support for adoption.

I vaguely recall reading that a new working Chair was paired with 
another working group Chair who has been doing that for a few 
years.  The rationale is that the latter will help the former 
understand the documented process.  Did that happen and did it 
produce the desired results?

>     > I generally knee-jerk when someone argues for replacing a process when
>     > the real problem is that the process isn't even used (or known!) in the
>     > first place.
>
>We are very much in agreement here.

Yes.

Regards,
S. Moonesamy