[Mod-discuss] Last call review of draft-ietf-modpod-group-processes-10

David Schinazi <dschinazi.ietf@gmail.com> Fri, 12 September 2025 01:48 UTC

Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: mod-discuss@mail2.ietf.org
Delivered-To: mod-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2CB166158A83 for <mod-discuss@mail2.ietf.org>; Thu, 11 Sep 2025 18:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level:
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ALN1Tu_qtr62 for <mod-discuss@mail2.ietf.org>; Thu, 11 Sep 2025 18:48:55 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D0FFE6158A7C for <mod-discuss@ietf.org>; Thu, 11 Sep 2025 18:48:55 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id ca18e2360f4ac-88703c873d5so34737939f.3 for <mod-discuss@ietf.org>; Thu, 11 Sep 2025 18:48:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1757641729; x=1758246529; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=s2QQwcM8HTZ4dWURljcl0Wn9nxS4IAXzftnmyAobzb4=; b=aM6fcnZRQ8WkfodgbNnV6+5YgrHM0NC3hQCj1ACG9ic3ab+CnP1hvXPh9w7IbuKQmu fp7kfhzcI1iIAVEJuUwZAQk5iZy24jDqZ55A0tSwiWqlkl3MH5SD+Kyr7HDSenKTqIHn 7P8cDrIRK1XR1l+Pe7cjLuTMS4KO/fGZjvm29JsFTynCE7xiptkp+6BQVTJf/0J22gm0 9bmv8bIccojS31OzVdT7QQWg6BnpL3JgD1DRaQ8gGhkcpkyWb1l+LBsKzSSWVLtyTJAN fMuz92SgoQocgRJgnLFmafeZV4Eqw6vt0YD9ss2cN22H05uNL5zvVvvOE0X4hUa2g/bS 7Lfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1757641729; x=1758246529; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=s2QQwcM8HTZ4dWURljcl0Wn9nxS4IAXzftnmyAobzb4=; b=NdI1mzV/Bk1LkP0g1Ud1T+tXKgELYcgwQGG/wPYXHMsF3leoB7fVVdFyfwTzqXufHI OE586JA3xSeYa6uamuguGbbyXa8H07Pnp+1KycOuDT6nzdMI5Za9c+6/P9Mlvw4B47gL feQT84BlW5irJscGnD6kfI+M+6tPKtWhAtfRlh2rv1T4gSdHvZs4tmTvlHIL9d2uNmIK Sh6WYkAiXPMOjd9VV9GZLM9G3SuFaY+dehqU1IWkMHQHEk1at1iQeTyzuq3AjVld+x3t 5S7Fwmik81qOX07PoWewV1l7Dj3pew3Fot17UYUTlCt/A/Cfx5wW4teXqinNF944Oath ndbg==
X-Gm-Message-State: AOJu0YydPCmHFMrlrbtGYxVKyZTZRUQtyDCjuD8I/xdpvQ14c3vf62X8 CzVYTiT+5osEbwAu/0+2GHLPSakfo7LuHmOhi0htYDD9+BFNw4zgvUqzTUphUUtRwv8RMLfasE/ Nkb4Pi3QwePnmF3D/HgS7c4OMjUoLwIhfH7AG
X-Gm-Gg: ASbGncvG/xPqdp/J11XeW6FyMxDdxbPtrRHZRoCc2SNlb0Gd42Aox9SzR4KSu6cCNpG CF5sGrUAGClGNs/+86Ryug2aHyeIblxR/Q+c9wobs5pUbZlRAhJwQd8ebMCwsEQKck2ULVEfXHe VV4YNjH0cP4jt4+fLlscv1eDj9or1UiyQcHzMQhOVFQLDmJaBoe/uKmf5avsIV4NitHyc97RTpM o7lMZrhUWS3kWPH9n8pjKz/qSBCdgBm+W0BQUTOSpQGbNFIxJJ/r+RIa6oTwJzk9pcJYxpQwuCr UfdPUSs7D6tG+ySNVGTMHONdbAQD
X-Google-Smtp-Source: AGHT+IFPS8AfN7YfB1SuFPjdiIpFC2uhrS+Vv3iE5yXBOgqYSpbv1YxN6gbNJg6OB+/g5QTUdk91ctIuabiPzUhr6y0=
X-Received: by 2002:a05:6602:483:b0:887:62d2:4622 with SMTP id ca18e2360f4ac-890369e764dmr225481139f.11.1757641729188; Thu, 11 Sep 2025 18:48:49 -0700 (PDT)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 11 Sep 2025 18:48:37 -0700
X-Gm-Features: Ac12FXzxxHYMMRTzbsqYULnB_h_bv2E0isxY8m5O13nWlj3tqelTNVtbEvbX0Qw
Message-ID: <CAPDSy+595bZjjFHVnvhFcYNUbk2h=jU8Uu-kpB7DeGe7dbaurw@mail.gmail.com>
To: Moderation Discussion <mod-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e927c7063e90da6c"
Message-ID-Hash: 3WM75YSOMYOAV5UVLFLE7P6XNK7TIS3N
X-Message-ID-Hash: 3WM75YSOMYOAV5UVLFLE7P6XNK7TIS3N
X-MailFrom: dschinazi.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mod-discuss.ietf.org-0; header-match-mod-discuss.ietf.org-1; header-match-mod-discuss.ietf.org-2; header-match-mod-discuss.ietf.org-3; header-match-mod-discuss.ietf.org-4; header-match-mod-discuss.ietf.org-5; header-match-mod-discuss.ietf.org-6; header-match-mod-discuss.ietf.org-7; header-match-mod-discuss.ietf.org-8; 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: [Mod-discuss] Last call review of draft-ietf-modpod-group-processes-10
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/5_Ey6CpZkWK91uV_Zg832BLI5Zc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mod-discuss>
List-Help: <mailto:mod-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:mod-discuss-owner@ietf.org>
List-Post: <mailto:mod-discuss@ietf.org>
List-Subscribe: <mailto:mod-discuss-join@ietf.org>
List-Unsubscribe: <mailto:mod-discuss-leave@ietf.org>

Hi moderation enthusiasts,

I just did a full read through of draft-ietf-modpod-group-processes-10. I
think the document is incredibly thorough, well-written, and is ready to be
advanced towards publication.

I have a few suggestions that I don't consider to be blocking:

* Section 2.1 (Composition) states <<The moderator team consists of no less
than five individuals>> but doesn't explain what happens if that number
were ever to drop to four due to unfortunately timed resignations. I'd
recommend using text similar to Section 3.1 of RFC 7776 to avoid ambiguity.

* In section 5.1 (Relation to the Ombudsteam), I think we do a good job of
covering communications from the administrators to the Ombudsteam, but I
would suggest adding text about the converse direction. Perhaps something
like this: <<If the Ombudsteam is confidentially notified of unacceptable
behavior on a public forum, they may notify the appropriate administrator
about the concern and suggest a course of action. Administrators are
encouraged to take Ombudsteam concerns into consideration. The Ombudsteam
will clearly communicate whether their proposal is a non-binding suggestion
or a formal Remedy as defined in Section 5 of RFC 7776.>>

* Section 5.3 (Relation to the IRTF) was unclear to me. The IRTF has its
own code of conduct but it still requires mailing list communication to be
respectful and professional. Is the intent of this section to say that IRTF
lists are out of scope for the moderation team? I think that would be a
mistake. The IRSG is primarily responsible for enforcing the IRTF code of
conduct, but I think the moderation team should be able to intervene in the
same way that they can for IETF WGs.

I fully support advancing the document, even if we don't end up reaching
consensus on my suggestions above.

Thanks,
David (writing as an individual)