Re: [Gendispatch] some thoughts about ietf communication

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 29 July 2021 22:15 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583393A0A88 for <gendispatch@ietfa.amsl.com>; Thu, 29 Jul 2021 15:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBenZgI-N2o0 for <gendispatch@ietfa.amsl.com>; Thu, 29 Jul 2021 15:15:38 -0700 (PDT)
Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D75673A0A84 for <gendispatch@ietf.org>; Thu, 29 Jul 2021 15:15:37 -0700 (PDT)
Received: by mail-yb1-f176.google.com with SMTP id q15so12663667ybu.2 for <gendispatch@ietf.org>; Thu, 29 Jul 2021 15:15:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q891vrA/ADszEH3wgmIqIqBjQTwGaynb0ZoocVdwgcA=; b=IHT3mhaRlvbm6i0fGiiyL8IKtdSdIRCpf9TZ9kf0V0AOnwLkLr3WW+0AZKuhug1N82 m+9jbBPJDvflzqQFCMnyz75wvXpV4Gk50O6W8RT9fFbL37avZBMSazmoiXlDJsQtcZmU X67jG57GwLfHMKL4JVSWNqJBkZe/oDdnNSG4M5xG5SROH9rK44JFV9FTX6zH4KK6nWu3 mO276SZYyIMR3FRI5bNVyC28YKP6f403QJUKc+NGDMVaopc+kwiKNNwthRqyRfKbZ85U 7xb3eGziYdUSVOPsFyS3IYzwnmRLorP25CRB22SmGqZIw5ki+Ppgqlg0yDgtK1He/YdW C2bQ==
X-Gm-Message-State: AOAM533ywL4H2RCRDKsn6oCbxaa0bE7o0IITq8OLEH0mU75lH/A6sKuQ m+882OpZc2Ileb7B17zSOIStsySdFyCKgmLFnTU=
X-Google-Smtp-Source: ABdhPJzbAldN1SsHdOp576rdTBRmCdIJknbyC2dqeKVLcw8p3ZXiiPu6W+d8zX45Zmurcp9Il0qkzc1PO2HhTifakhs=
X-Received: by 2002:a25:af81:: with SMTP id g1mr9523128ybh.172.1627596936904; Thu, 29 Jul 2021 15:15:36 -0700 (PDT)
MIME-Version: 1.0
References: <ee2a840d-1837-1e06-647e-1251295c94bb@lear.ch> <eaf283db-ce73-dc6e-3ba1-64b830f0f726@joelhalpern.com>
In-Reply-To: <eaf283db-ce73-dc6e-3ba1-64b830f0f726@joelhalpern.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 29 Jul 2021 18:15:26 -0400
Message-ID: <CAMm+LwiuZj+GsUYvHsfDXrkD82a-eEr7fRoBgiFQbXf0V6sh4Q@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: Eliot Lear <lear@lear.ch>, GENDISPATCH List <gendispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004301e205c84a71a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/C-95LkqKvummYHeyDn5cSxvJOXs>
Subject: Re: [Gendispatch] some thoughts about ietf communication
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 22:15:43 -0000

On Thu, Jul 29, 2021 at 11:15 AM Joel M. Halpern <jmh@joelhalpern.com>
wrote:

> I may be misreading this, but it seems that it misses one important
> purpose for the plenary.
>
> Sometimes, the community has concerns that need to be expressed, whether
> the leadership thinks the issue is important or not.  That is why, even
> though it is usually vacuous, I consider the open mic portion of the
> plenary to be important.
>

Sometimes there are issues that have to be raised in public BECAUSE the
IESG doesn't want to talk about them.

Like that time that the chair of a working group who was also an AD in
another area flagrantly abused their power by refusing to recognize WG
consensus on a draft he personally opposed and filibustered the issue for
over a year by referring it to a cabal for review and nobody on the IESG
dared to acknowledge the situation because the WG chair might retaliate in
IESG.

If the only venue for talking truth to power is the law courts, that is
where it is going to be taken.


Since then, a number of reforms have prevented a repeat. SECDIR and GENART
reviews explicitly state that they are not privileged and should be treated
as other comments. The referral of a WG item to a directorate should never
have been allowed then, it would be much harder to justify today. Another
important reform is that with the exception of GENAREA which is
traditionally chaired by IETF Chair, members of the IESG are not WG chairs.
And there is a general expectation that AD tenure is limited to two terms
with three being exceptional.