[Mod-discuss] Re: Moderator Team Procedures - For Community Input

S Moonesamy <sm+ietf@elandsys.com> Sat, 24 October 2026 06:46 UTC

Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 35C0446 for <mod-discuss@ietf.org>; Sat, 24 Oct 2026 06:46:57 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=fail ("headers rsa verify failed") header.d=elandsys.com header.s=mail header.b=V5TQm9BV; dmarc=none; spf=pass (mx.ietf.org: domain of sm@elandsys.com designates 2001:470:f329:1::1 as permitted sender) smtp.mailfrom=sm@elandsys.com
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.104.145]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.15.2) with ESMTPSA id 69O6kRWM010085 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Oct 2026 23:46:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1792824401; x=1792910801; i=@elandsys.com; bh=WhLVHoO6A8W2QIGs0A/X2/tgYlxerdumKZZ0rW2tGI8=; h=Date:To:From:Subject:In-Reply-To:References; b=V5TQm9BVe7WccoelB/Y4KvHWqyCrkFEYBEjCflmbDpw/lLrij2dH3wp169sf4uKAv bW1zWEW7Nfzz58M459bs1pat0oJ58a1KVrclbM5818OoXlBXWktUoqH3xSK8IhPLP8 f4yMXDNAhT0Xq0H3RcDxWjVE3TOZNqSUlIhmUty0=
Message-Id: <202610240646.69O6kRWM010085@mx.elandsys.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 23 Oct 2026 23:35:40 -0700
To: Simon Josefsson <simon@josefsson.org>, Bron Gondwana <brong@fastmailteam.com>, mod-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <87mrs4z2vu.fsf@josefsson.org>
References: <364e7c73-6146-4f86-9bf6-db5443c42e4a@app.fastmail.com> <875wystxt2.fsf@josefsson.org> <49fcb7e4-11e6-4929-ae2a-996216f8fa54@app.fastmail.com> <87mrs4z2vu.fsf@josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
X-Spamd-Bar: ------------
Message-ID-Hash: MU6DPLDS2QXM4ETEQ3ZFOYICD7X5SS3S
X-Message-ID-Hash: MU6DPLDS2QXM4ETEQ3ZFOYICD7X5SS3S
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; 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; header-match-mod-discuss.ietf.org-9; header-match-mod-discuss.ietf.org-10; header-match-mod-discuss.ietf.org-11; header-match-mod-discuss.ietf.org-12; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [Mod-discuss] Re: Moderator Team Procedures - For Community Input
List-Id: Discussion list for IETF moderation policies and practices <mod-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mod-discuss/yfFtWpiL35RwES8HMK0uFgpDWQg>
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 Simon, Bron,
At 11:29 AM 23-10-2026, Simon Josefsson wrote:
>Bron Gondwana <brong=40fastmailteam.com@dmarc.ietf.org> writes:
> > The IESG has a policy on it. They have declared that they find it
> > disruptive to have legal claims about message content which are
> > incompatible with the notewell being made in messages to IETF forums.
> > It distracts from the purpose of creating high quality technical
> > documents which is the IETF's mission; hence it's in scope.
>
>The IESG may have policies on many things.  That doesn't mean you need
>to censor discussion that doesn't follow the policy.  This all seems
>like a continuation of a personal conflict, and I don't think it helps
>the IETF to continue to pursue it.

The IAB took a decision in July 2026.  Here's an extract from it:

   "The appellant's argument regarding RFC 5378 is responsive to a claim that
    the IESG did not make. RFC 5378 was cited by the IESG only to establish
    that the message was a contribution, not as the source of the 
AD's discretion
    over confidentiality."

 From what I understand, this message to the mod-discuss mailing list 
would be considered as a "Contribution" under the current IPR 
rules.  It's debatable whether the content has any value.  There are 
companies who take up that question in the appropriate venue.  And 
this is what the "IETF" does: 
https://www.ietf.org/media/documents/Nugent-Declaration-10multipleI-Ds-PerkinsCoie-RequestDate05.09.2024-Signed-23May2024.pdf

The text which was disputed is displayed at the bottom of this web 
page: 
https://datatracker.ietf.org/group/iesg/appeals/artifact/316  It did 
not prevent the IESG from taking its decision.

The discussion seems like a personal disagreement as Simon Josefsson 
noted.  It would be easier, in my opinion, to drop the IESG statement 
from the list of "disruptive things" instead of determining whether 
IESG statements are part of IETF best current practices.  If an IESG 
member has a strong opinion on including it, he/she will the 
opportunity to insist that the statement has to be added to the list 
of "disruptive things".

Regards,
S. Moonesamy