Re: [Gendispatch] draft-rsalz-termlimits

Bob Hinden <bob.hinden@gmail.com> Wed, 20 October 2021 19:43 UTC

Return-Path: <bob.hinden@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 623DD3A0DE8 for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 12:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8eUz2RHYghh4 for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 12:43:23 -0700 (PDT)
Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) (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 EA3993A0CAC for <gendispatch@ietf.org>; Wed, 20 Oct 2021 12:43:22 -0700 (PDT)
Received: by mail-oi1-x22b.google.com with SMTP id t4so10973623oie.5 for <gendispatch@ietf.org>; Wed, 20 Oct 2021 12:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=IDOpqT8H6hT4EzRM1wvA9PBhcJ/sl6mlOrOgMKjiSt4=; b=KuB5ARp2x4lP5pjqs2c+Z2zlv/IiW56FcVj6ooT+vd3yrsIzI3A7dDKdOzQFCukrVi tO7pp9VD+BpbCnlqvATJ9YnRyDjO4uWBpKL4yzdaoLd0octLIHoz3JpF6NNEKlSrSrnI Xs6IY779yXLoMCINf4Gu3mzLpCWoyHf3rN6DLcC0qyhEqeIGWikFGF3QWc6f/K4cWqDl 9ksX6Xv8wwnbg5cEUAF26Ph+Pr0YOOwcWnuNuAMQHiTB+yAzvZkSZsQPk1vEhGY5R5js fsg59CW3tuDFco2gPbk5UuPVG81G1V3lBh5sIdTIAJBUdeH51irTUa+Pa/aVGylwhtgo yilQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=IDOpqT8H6hT4EzRM1wvA9PBhcJ/sl6mlOrOgMKjiSt4=; b=X79BSjxow8onFWpfR62PQ5EYvDqocXy3iLV5z5KlzlduLPqcw14Agc+m+BJNnfi2Uk QS+RDuSgJkrSfxwjUgUFv1bN964C7woZv7L7vQyeeLsIYP5nLAwejOFjzvZUADO1Kv2+ ahvmOKQIhF4NCVkhngNokZ8roV3tzZLD5XJJgxLt1qGUa+ioFkef9R36SCioiZ50Suyd l/djx3lV6KjVbbmjrtHzwQHXRwRRDjL5q8Z+AuYHJnDptD4iW9eMaPcsnFnYhAKq5S5F 8uwEVShTmeic56KhJFNAyKR/3IRMtoY4TPxATFvIxurrZichq0qjAsclXfw+uFWQWXO5 1BZg==
X-Gm-Message-State: AOAM530fmBB/DeqlTIZqUFw8w5Shf1qb0yNbmaIKDu4PrejmtlVrjweX c/gHJiYdHungDFwWF3DDh3E=
X-Google-Smtp-Source: ABdhPJyS71IZJIGHfxos2rdR9HmLONd7uTGJigBspQOL0K/FIEyA4MTlyXOLVi4u2FpnAoYrncWqfg==
X-Received: by 2002:aca:d68d:: with SMTP id n135mr778179oig.144.1634759000244; Wed, 20 Oct 2021 12:43:20 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:659:b59a:3cb2:d105:2bb6? ([2601:647:5a00:659:b59a:3cb2:d105:2bb6]) by smtp.gmail.com with ESMTPSA id s206sm619169oia.33.2021.10.20.12.43.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Oct 2021 12:43:19 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <53A1649E-0E10-449D-9EC0-87A6FDCD07B2@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2D4A3543-49E6-4D00-85A5-6DEBFAF55D41"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Wed, 20 Oct 2021 12:43:16 -0700
In-Reply-To: <CALaySJKYG8ydGrgdSKZY1b28VL2DvwTS_3_40y_eFkHcGjdJXg@mail.gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>
To: Barry Leiba <barryleiba=40computer.org@dmarc.ietf.org>
References: <4BDF1DD9-9D30-499F-8C26-1E7790F2A729@akamai.com> <CALaySJKYG8ydGrgdSKZY1b28VL2DvwTS_3_40y_eFkHcGjdJXg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/7VLa4AmvNUsmAUH6Y-VcXCIRXdc>
Subject: Re: [Gendispatch] draft-rsalz-termlimits
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: Wed, 20 Oct 2021 19:43:28 -0000

I agree about hard term limits, but think the selection bar should go way up for more than two terms.  Related, I think doing a second term as an AD (and other positions too) should be encouraged.

I think people should not move directly from one leadership group (IESG, IAB, LLC, Trust) to another.   At least one year being a regular IETF participant provides a lot of perspective.   Otherwise we get an inbred (so to speak) leadership who may loose site of what it is like to be a regular IETF participant.   Note, I purposely didn’t include w.g. chair in my list.

The IETF Chair is different, I agree it’s good to have a person who has served recently as an AD.  I think that should be the exception to moving between leadership positions.  However, I don’t think an IETF chair should be appointed to the IAB, LLC, or Trust directly when their term ends.

Bob




> On Oct 20, 2021, at 10:23 AM, Barry Leiba <barryleiba=40computer.org@dmarc.ietf.org> wrote:
> 
> Rich, thanks for bringing this to discussion.
> 
> First: I am very strongly *against* hard term limits, as it places
> unreasonable limitations on the appointment process.  In a public
> voting system, it's antidemocratic, artificially eliminating the
> ability to vote for whom one thinks is best.  In our NomCom system, it
> restricts the NomCom from considering excellent candidates who have
> been doing well and can be expected to continue that way.  And it
> would make it impossible for a NomCom to re-appoint an excellent AD
> (say), when there are no good alternatives, ending us up with a bad
> choice because it's the best the NomCom had to work with.
> 
> Second, I am very strongly *for* soft term limit guidance.
> Specifically saying that NomComs MUST consider more than two terms to
> be atypical and more than three to be truly exceptional, and [etc,
> etc, wording like that with further explanation] would absolutely get
> my support.  But NomComs *have* to have options to deal with
> situations where re-appointing someone for a third (or fourth) term
> really *is* the right thing *in this case*.
> 
> Third, while I appreciate the desire not to have ADs move straight to
> the IAB or vice-versa, and while a one-year gap before making the move
> is not unreasonable, the issue is more of a challenge for someone
> moving into the IETF Chair role.  Here are two reasons why:
> 
> - It's critical for an IETF Chair to have experience as an AD.  And,
> while Lars's experience is older and he is doing and will do fine,
> we've generally had more recent ADs step into the IETF Chair position.
> I would not want to limit the NomCom by saying that they can't appoint
> a sitting AD as the next IETF Chair.
> 
> - The IETF Chair is only appointed every two years.  An AD who wants
> the IETF Chair position would have to step down at least a year ahead,
> and an AD whose term is in sync with the IETF Chair appointment would
> have to step down at least two years ahead.  Given that a one-term
> IETF Chair is likely to get a second term, that could move to four
> years ahead.  Now we have an AD who might have been a great choice for
> IETF Chair, but has to wait four years -- and be four years away from
> the AD experience -- before she will really be considered by the
> NomCom (especially if we should also move in the direction of JCK's
> proposal).
> 
> So *if* we should go in the direction Rich proposes, I would want to
> see an exception for IETF Chair appointments.
> 
> But, really, I'd much rather see us move toward giving NomComs very
> clear and strong guidance on what the community expects, but leave
> them the option to do what needs to be done as the situation might
> require.
> 
> Barry
> 
> --
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch