RE: Fwd: Complaint to IAB regarding IESG decisions

IETF Chair <chair@ietf.org> Tue, 04 November 2025 13:17 UTC

Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from [10.244.8.124] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id D954F826D58C; Tue, 4 Nov 2025 05:17:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: stephen.farrell@cs.tcd.ie, nick@foobar.org, chris.box.ietf@gmail.com
Subject: RE: Fwd: Complaint to IAB regarding IESG decisions
X-Test-IDTracker: no
X-IETF-IDTracker: 12.53.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <176226225374.512061.18216720813365424873@dt-datatracker-5df8666cb-7l4w5>
Date: Tue, 04 Nov 2025 05:17:33 -0800
Message-ID-Hash: KGF74WD7MXWBJOLHJIOVYCZ7QSTXRR2E
X-Message-ID-Hash: KGF74WD7MXWBJOLHJIOVYCZ7QSTXRR2E
X-MailFrom: chair@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: djb@cr.yp.to, ietf@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: chair@ietf.org
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d5tK-Ut1QZtgSaodWGC2MCgwqcw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

Hi!

-----Original Message-----
From: Stephen Farrell <stephen.farrell@cs.tcd.ie> 
Sent: Thursday, October 30, 2025 5:23 PM
To: Nick Hilliard <nick@foobar.org>; Chris Box <chris.box.ietf@gmail.com>
Cc: djb@cr.yp.to; IETF Discussion List <ietf@ietf.org>
Subject: Re: Fwd: Complaint to IAB regarding IESG decisions


> Hiya,
>
> On 30/10/2025 21:05, Nick Hilliard wrote:
> > 
> > There's enough ambiguity in the text and sentiment of rfc5378 that the 
> > IESG's interpretation of the document could be viewed as both 
> > legalistic and expansionist, and at best arguable.
> > 
> > This is not a defense of djb's general attitude on mailing lists or of 
> > the set of decisions that he's made that have led to his various 
> > claims being dismissed on procedural grounds. There's plenty of scope 
> > in what he's written over the last several months for moderation 
> > engagement of one form or another.
> > 
> > But given the ambiguity in RFC5378, and with due respect to the IESG's 
> > position on this, I am not convinced that attaching a Legend 
> > Instruction per se hits the mark for threatening to revoke posting rights.
> 
> +1

One implicit question raised above is why the repeated use of non-conformant notices that claim derivative rights are withheld could be disruptive.  The IESG position is that this behavior may be disruptive because it creates barriers to participation in the standards process in the following ways:

(a) increased complexity and process ambiguity – the IETF standards process operates on the premise of a defined set of rules to create a level playing field for participation.  New participants or those less familiar with IETF processes are likely to be disproportionately negatively impacted by misleading, inconsistent or false representations of the IETF process, and could feel the need to match what they perceive as the conventions of the community.

(b) increased cost of participation – RFC5378 reminds participants to “consult their own legal advisors if they would like a legal interpretation of their rights or the rights of the IETF Trust [RFC4371] in any Contributions they make.”  Such non-conformant text imposes a burden on participants to check with their legal counsel. 

(c) silencing of risk-adverse participants – participants that lack the resources to assess such non-standard new, non-conformant legal clauses will refrain from participating for fear of liability.  

Please also note the statement text says “_may be_ considered a disruption” (emphasis added) which leaves the decision on taking action on these clauses to the discretion of the administrators (e.g., WG Chairs, non-WG list owners, IETF Discussion List moderators) of the venue who best understand its dynamics.

Regards,
Roman Danyliw
(as IETF Chair)