Re: Want to be on the IESG?

John C Klensin <john-ietf@jck.com> Wed, 06 October 2021 00:42 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6D03A0DE0 for <ietf@ietfa.amsl.com>; Tue, 5 Oct 2021 17:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 c-WnJpEZO4ys for <ietf@ietfa.amsl.com>; Tue, 5 Oct 2021 17:42:53 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A1EA3A0D61 for <ietf@ietf.org>; Tue, 5 Oct 2021 17:42:50 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1mXv1E-000KhT-01; Tue, 05 Oct 2021 20:42:48 -0400
Date: Tue, 05 Oct 2021 20:42:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Want to be on the IESG?
Message-ID: <C9FBA8D0B5C67204AE60805D@PSB>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FuMAecwSsohIlFSQFZOnwJDkA00>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2021 00:42:58 -0000


--On Monday, October 4, 2021 20:56 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>> and probably others.  There are reasons, some of them valid,
>> for not doing any of this. But not doing anything is going to
>> lead to increasing ossification as we've already seen in the
>> surveys and such.  And we know the IETF hates ossification.
> 
> Here's one, in case someone wants: impose an N year gap
> between memberships of the IESG and IAB except to allow
> one transition from IESG to IAB. IOW, when you exit the
> IESG or IAB you can't be on the IESG or IAB for N years
> (modulo the exception above). That might cause a crisis
> in a short enough while, and maybe we need one of those.

Stephen,

Proposed before, including in the direction of IESG-> IAB
transfers which you would allow but that I suggest has often not
worked out well.  The problem is that the two bodies have very
different types of responsibilities, authority, and ways of
doing work.  Some people have made the shift well but many
others have treated the IAB as a nice place to retire while
remaining a visible part of the leadership, as a body more
characterized by individual fiefdoms than one that needs to work
together, and/or one that exercises the same level of authority
as the IESG is seen as exercising but with a different topic
range.  IMO at least (having served on both bodies and made the
IESG-> IAB transition, albeit long ago), none of those three
behaviors are good for the community.  There is also a
Nomcom-related reason: service on the IESG is not a particularly
good basis for evaluating someone for an IAB position or vice
versa, especially if they have already held those positions for
four or six years.   For those reasons and others, forcing
someone stepping down (of being removed from) the IESG or IAB to
spend some time as an IETF participant doing technical work in
the trenches would be a good idea even though I would set N at
two or possibly one.  Conversely, if any significant harm would
be done by having relevant people out of the leadership for a
couple of years, we have bigger problems that I hope there is a
plan about addressing.

best,
   john