Re: [Gendispatch] draft-rsalz-termlimits

Rob Sayre <sayrer@gmail.com> Wed, 20 October 2021 20:02 UTC

Return-Path: <sayrer@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 A665B3A0C1A for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 13:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=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 Rjnhgjiwr8qh for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 13:02:14 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 E53013A0E22 for <gendispatch@ietf.org>; Wed, 20 Oct 2021 13:02:13 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id s3so23508276ild.0 for <gendispatch@ietf.org>; Wed, 20 Oct 2021 13:02:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NtGS7GiR7nsXG7F6QFss+w8HFFryYvtHCVz27nBiPjQ=; b=ehmsVeVJIouVGkPFpKjdx1eiO/qAwps63S9JFhBukIg+nz2tf2DEOK6MXUI9WG4G0c Juxm27PzZrm1r5ylvxEFQrqSB5kl/bkGh3uIlnOtMUtCTeqf6NAq0Qtvh6tA4MvtPiFv MmfrlbjAfxxgpo8a62/g/G2VpZbYYEBfzBlY5T1aTXqzth3CXv7zTHYWOKMM881KYgPO fM6NoMJImRpZPGKpzI6YBsPQEU7ZEGufebR95QLYEYA6FQV/2iOLL4CQn3sTPSkno46/ y01CcD8JZV1NFm6E7dRM0/VpHNRNUkuTY3Y6aiTsUhJBEnLZdS+37sh5nAcTL9NF2pc1 cElg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NtGS7GiR7nsXG7F6QFss+w8HFFryYvtHCVz27nBiPjQ=; b=HxMr1qDWxsMWknUOL0vkVEljIgZozoSHOX8QWTIbOPhkSzuXINpd3xSxODBw3f+iz6 Tn6hid4mXD7vjYRYefaUgHU4OQFFKp6D8PDKIfntNSPeZEYpkKosbkwoUUnXBD7lkCuY klcFjy5SwGoSdk5teDsEli5WM6TCBCZ2aRBlg2gJtGNqJfnRNUmLWeVV7l/c/gSbLcCP nLoQZ7bxHCMPqSc8eNSW3d99gIGJGfaTzVrPYg8mruS3gFvPQw/7t8f7t8uJBbpS75/g PkunOqkw8hUh5wbk8+xqKBLgXsCVWUQ7seF8HzjZpBVCyW7QERpssPJcdsWw0vJBGjuy Yuag==
X-Gm-Message-State: AOAM531WfH8RsocYbzM3Y/ihc4g6fXur1/8QOR6uQB1gwzJNAkyyr04z xg1QyIAbSBpVnqfxOpl5E6Tb/qO7kISbcvrpuCw=
X-Google-Smtp-Source: ABdhPJwYHzSAkP7oXOMk/CuNjqr/Af61Y1Q72l2ZzeDmwdTYHy3weQtX8w/cV/QX6333Cv/dfk/pD/JTv3NUcqc+2aQ=
X-Received: by 2002:a05:6e02:216f:: with SMTP id s15mr738647ilv.259.1634760132629; Wed, 20 Oct 2021 13:02:12 -0700 (PDT)
MIME-Version: 1.0
References: <4BDF1DD9-9D30-499F-8C26-1E7790F2A729@akamai.com> <CALaySJKYG8ydGrgdSKZY1b28VL2DvwTS_3_40y_eFkHcGjdJXg@mail.gmail.com> <CABcZeBMKpJAmUD3xc-b5jcyMKQkZCxJK8jFVxBaL==ZnJRA-2A@mail.gmail.com>
In-Reply-To: <CABcZeBMKpJAmUD3xc-b5jcyMKQkZCxJK8jFVxBaL==ZnJRA-2A@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Wed, 20 Oct 2021 13:02:01 -0700
Message-ID: <CAChr6Sy5q-TV5ZnDm5+uGSE7Fy04KhmaFMw6wv3cKwVL+KCGYw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Barry Leiba <barryleiba=40computer.org@dmarc.ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ffa53105cece40d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/cDot8YIvcE9WYcEuPhSrSC2S9Mw>
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 20:02:19 -0000

I mostly agree with Barry as well. I also find that the people who get
reappointed or agree to serve again tend to be pretty cool folks, so I'm
not sure term limits solve a problem. However, I'm not against it either,
really.

thanks,
Rob


On Wed, Oct 20, 2021 at 12:26 PM Eric Rescorla <ekr@rtfm.com> wrote:

> I mostly agree with Barry. Specifically, Barry raises two points:
>
> 1. In exceptional cases a candidate needs to be appointed for a third
> term. I've seen this as well though I think it wouldn't be fatal if we
> limited to two terms.
> 2. That often you want to pick an active AD or an IAB member as IETF
> Chair. I think this is the strongest point and it would be quite bad to
> make this more difficult.
>
> I am more sympathetic to the IAB case: there are always a lot of IAB
> candidates and I don't think that having it be common practice for ADs to
> go right to the IAB is that great.
>
> -Ekr
>
>
>
> I
>
> On Wed, 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
>>
> --
> Gendispatch mailing list
> Gendispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/gendispatch
>