Re: [Last-Call] Question for the IESG

S Moonesamy <sm+ietf@elandsys.com> Tue, 11 October 2022 14:57 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 957B2C159A32 for <last-call@ietfa.amsl.com>; Tue, 11 Oct 2022 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_BBDn3dCwek for <last-call@ietfa.amsl.com>; Tue, 11 Oct 2022 07:57:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD6BC14F606 for <last-call@ietf.org>; Tue, 11 Oct 2022 07:56:50 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.86.241]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 29BEuZLa003340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Oct 2022 07:56:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1665500207; x=1665586607; i=@elandsys.com; bh=k5pGr7WHb46Mt/j6XMozoEd/TaTAXUbqh2zRndYFbVk=; h=Date:To:From:Subject:In-Reply-To:References; b=FNw7m7uKMtbmUOZujLwZla4EUW1wrrwR3saeJpa+Mh9xTBmcWrFShpQ7P0BA7nWKB d6uQUc8h+BWNZrrw2Be1P6X+DrpvDh5iwq5qxf/sB9b1oADmCQ8L/OvXJ7GrwEEa1b 8LNMPpcwJ/QOXRmTr9AUPclJ0T9D8bBeNcEAHY5M=
Message-Id: <6.2.5.6.2.20221011054550.0d95bee0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Oct 2022 07:54:36 -0700
To: John C Klensin <john-ietf@jck.com>, last-call@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <E07D908383FCC3EF63B6E49F@PSB>
References: <CFE25E25-D131-468E-9923-80350D6216F3@ietf.org> <33dcb391-6304-2a04-0041-ae8a0d9ee107@lounge.org> <118166719.778795.1665054336024@email.ionos.com> <CABcZeBOebDewrhpbntMHWLuF5iNd9WWUwKSTams-zbxEhtYe=w@mail.gmail.com> <1590543408.1336232.1665076691164@email.ionos.com> <E07D908383FCC3EF63B6E49F@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/S5wDW9UdgDL1n-pO7JJd0MZvGxU>
Subject: Re: [Last-Call] Question for the IESG
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Oct 2022 14:57:20 -0000

Hi John,
At 03:02 PM 06-10-2022, John C Klensin wrote:
>I am asking because, while I think parts of it have been very
>helpful and should be considered going forward, I am probably at
>least as sick of the scale and tone of some of the discussion as
>I infer at least some IESG members are. I also agree with those
>who have suggested that parts of the discussion itself have been
>at least as unpleasant, divisive, and disruptive than anything
>Dan (or anyone else, at least anyone not in the leadership)
>could manage on their own.   I'm trying to lay the foundation
>for a way forward that is more closely focused on the rather
>specific criteria that I understand (and have understood since
>2003-2004) BCP 83 to be about.  Or, to put it differently to
>allow asking if a PR-action against [removed] is the right decision
>whether or not the IESG wrote the optimal description of why
>action should be taken and why.
>
>And, fwiw, if, for some of us including myself, endorsing the
>PR-action will be taken as an endorsement of the current IESG
>statement and the methods and reasons for getting to this point,
>then it might feel that the endorsement/ approval is too
>expensive in terms of, e.g., the precedents that might be set.
>
>I am sure some will feel that moving in that direction would be
>letting the IESG off the hook for some of what appears in the
>description Lars circulated, but I believe that the IETF would
>better off if we could treat that as a separate question,
>perhaps even one that, for some community members reflecting on
>some IESG members, should be discussed with the Nomcom.

I have read the various comments on the thread.  The topics are, to 
put it mildly, quite controversial.

I looked up the definition of the word "censorship".  The American 
Library Association defines the "censorship" as "the suppression of 
ideas and information that some individuals, groups, or government 
officials find objectionable or dangerous".  It is the first time, if 
I am not mistaken, that a draft was removed from the I-D public 
repository.  The removal is not compliant with BCP 83.

BCP 83 is not listed in the "Note Well".  That does not negate the 
fact that it is part of the IETF statute book.  The criteria set in 
2004 in that BCP is open to interpretation.  There is a barrier to 
prevent misuse; the BCP requires an Area Director to make a judgement 
call.  The BCP includes an avenue to anyone who wants to contest the 
"PR-action", i.e. the appeals process.

BCP 83 lists the following case: a participant has engaged in what 
amounts to a "denial-of-service" attack to disrupt the 
consensus-driven process.  That is different from some of the points 
raised in the sub-threads (on this mailing list).

I am a bit curious about whether you will receive a reply to the question.

Regards,
S. Moonesamy