[procon] Re: 2418bis - Document Editor

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 02 July 2026 19:33 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: procon@mail2.ietf.org
Delivered-To: procon@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E88D310CEC893 for <procon@mail2.ietf.org>; Thu, 2 Jul 2026 12:33:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1783020836; bh=1xf/pqGadv1LcfUF/HMXUbxQ1875b7PjI10d12SCW3Q=; h=From:To:cc:Subject:In-Reply-To:References:Date; b=BWHZK43gaGttU3FyFon7WStu1wKFxbXaqdRWcgQaeCx7mN5hD3jEghs0YPYZ2GzLa Fze1/W7ccnmx8+cBZNYu+fxvj12nEUBcYlZFgMbW6ZqCi9o41Hhpk2S5eVNXLRkVDo CdIUdrnchpVcJ9dfrzQw8/EakGOYbUQr1im5IAwQ=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 ClxIRE7GgAIH for <procon@mail2.ietf.org>; Thu, 2 Jul 2026 12:33:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id E3D9410CEC2EA for <procon@ietf.org>; Thu, 2 Jul 2026 12:33:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 3282C1800F; Thu, 02 Jul 2026 15:33:22 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id 112pasCIZ4Rs; Thu, 2 Jul 2026 15:33:20 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1783020799; bh=8yuXW3xzwzke1LeL50F4UhwHuGDcci43GVdaz0SWwug=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=g09aAUOzuQYtGL3KPRaj/DXnSEzeAVfLqaiwCN2ZOPyfwktBZXZAeJG1uu90qRBOF PWEKGBo3DRO7QkouON4kgV6IwLRHqDDsr6GlMeLg9N5CovjcZowO+runKcCOl3doyl SfpYevYkyODZbk0Y3OtUk1CRL186DmhPCZBmeNF+DAFoMyKJkMh6r6fY+SkWN4c9qB 24VQIWD5pZ8IbpYaiXY+sXvmFSV8KP1Lam0DLaTvlMhmz00c7AIDMlg9QZfr82B75Z WkI4gOfGuK77CPRyhZvfUREEdWDSo5xfeNawU/I9KQE8UeiW1nHwAM1yiVxO+GhniR gcGykYghdWhbg==
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 794BA18011; Thu, 02 Jul 2026 15:33:19 -0400 (EDT)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 75B0F180; Thu, 02 Jul 2026 15:33:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
In-Reply-To: <MN2PR17MB40311C9CAFE5CDAD6D79EE2ACDF52@MN2PR17MB4031.namprd17.prod.outlook.com>
References: <c2f570fa-55ff-4773-8959-667cbf720438@gmail.com> <MN2PR17MB4031E5604CAD82209F7E73F1CDF52@MN2PR17MB4031.namprd17.prod.outlook.com> <6991.1783012103@obiwan.sandelman.ca> <MN2PR17MB40311C9CAFE5CDAD6D79EE2ACDF52@MN2PR17MB4031.namprd17.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 02 Jul 2026 15:33:19 -0400
Message-ID: <21675.1783020799@obiwan.sandelman.ca>
Message-ID-Hash: O4QJMTVK7IKCT7MHDYIR647OHAPVQASD
X-Message-ID-Hash: O4QJMTVK7IKCT7MHDYIR647OHAPVQASD
X-MailFrom: mcr+ietf@sandelman.ca
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
CC: Process Enthusiasts <procon@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [procon] Re: 2418bis - Document Editor
List-Id: "Discussion of consolidating process documents and changes to the standards process per IETF 121 ALLDISPATCH." <procon.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/procon/Jwq_w1vyeeVOibnpNkc1TYpyYTo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/procon>
List-Help: <mailto:procon-request@ietf.org?subject=help>
List-Owner: <mailto:procon-owner@ietf.org>
List-Post: <mailto:procon@ietf.org>
List-Subscribe: <mailto:procon-join@ietf.org>
List-Unsubscribe: <mailto:procon-leave@ietf.org>

Our charter says:
    > "making understanding of these processes and procedures" (less)
    > "unwieldy".

Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
    > That is not our charter[1].  I do not know if the Document Editor is
    > part of the “Guidelines for WG adoption”, but it does not seem like it.

I don't see it matters if it's part of WG adoption or not.
Appointing a Document Editor is a WG chair function/privilege.

**Do you disagree?**


It does not seem to well stated in 2418, or 2418bis, and I looked at 2026
just to be sure it wasn't mentioned there.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

**       My working hours and your working hours may be different.         **
** Please do not feel obligated to reply outside your normal working hours **