Re: [Gendispatch] draft-rsalz-termlimits

Mark Nottingham <mnot@mnot.net> Wed, 20 October 2021 23:08 UTC

Return-Path: <mnot@mnot.net>
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 2FF3E3A0C1A for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 16:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=RBPtcTk6; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=USGX2SLE
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 PcNWk6lR_0BC for <gendispatch@ietfa.amsl.com>; Wed, 20 Oct 2021 16:08:31 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9199C3A0BB6 for <gendispatch@ietf.org>; Wed, 20 Oct 2021 16:08:31 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 790963200C20; Wed, 20 Oct 2021 19:08:28 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 20 Oct 2021 19:08:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=3 K0NxoloW3Mo+ZXLFfD++BvwXAxJN8ivS5+3VxYnKfM=; b=RBPtcTk6Bs8+xJIm2 whfn5Dr2ICD1wHBp/zpPuDNUiM9CYPyJS1gLWYmQradWj0R5/ZDdnJqR775Xzm13 YH8Rzz3wtgcj0hX252cCAsO4YvwNTI3ReAJJtCUrOouwK21bFqrDHezrEKl6xRJh ZmV+N4HK4JFS3d6P58ncgZsUFrf0NsGQBx1U19eT0cBw283Buf/WxTQr9axe9bIj WUy+7Rm/rTLreTv+AR48PZrvSxMWAuX/BMi8SGooi33j4CeJHUz15kV2TS1n9p+g TpfZwvhIV5dwT6uNnZTLwaj2FShczMTvq9iO/ifqy/jQlpz4M0EiPibxmHTZQrYT NO07g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=3K0NxoloW3Mo+ZXLFfD++BvwXAxJN8ivS5+3VxYnK fM=; b=USGX2SLE7yysqnIcp6c5wi9OA2EFKQC9bApQIGjAHolnvb7OjA0mEZfrp rGk0MhQmkoYxnwaEOiovGxxSmjpO1ZkXiFlDrya9bUlnvtZUl4mgCjWHo8fRRxt+ uBmq6f916n7ICx8uzlvLopOm/BooJ7B+ueGigmm1J5135Xy+QZr5qlPWtYLXJ/Wf 1NO/os71x1WGkB/y1mmjJ+v6QDhAfSVwyuf0+VvEViNkRpKVIEHWBNXoQKKlRMEz nJ/1P8nqsU/vk4kksNFFtFXALp+twbTxFvHMQPkV7RHPAbdBQ9EtRamM+oxaLaH/ zaZ2XPz19AADrXLtleeOGwBvjkFJw==
X-ME-Sender: <xms:bKFwYeD6RmDIyG8ixUkzwwyM1Uexk9cevcLzBf2akNKcyX1Ym8tHVw> <xme:bKFwYYgtFJJaRFzRXQ3jz5wpF411BQlB_zgcRi-i6tXph0hh8A-eZjpuDfcbs1NuP O1OUEMnVOiGjFeUDA>
X-ME-Received: <xmr:bKFwYRnrPzS34yUGT7SOqS_zixwANA3fCGYFrji23dM_FGu-0WPOBEOcFSfHK9fKr2A3cscS8I_UxZ7TjeMSDAE_pvkRqEK9sbhGRlpDejrXdalRSxTAq7QU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvddvhedgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfuhfgjfffgkfhfvffosehtqh hmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothhtihhnghhhrghmuceomhhnohhtsehm nhhothdrnhgvtheqnecuggftrfgrthhtvghrnhepkeduvdeljeegtefhveekhfdtveekle evkeefgeeludeihfdugedvieeuffdttdfhnecuffhomhgrihhnpehivghtfhdrohhrghdp mhhnohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepmhhnohhtsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:bKFwYcz7XlrzlZ08SzZSx4_aTifprOwHeaBPLzruf8wEk6Dosmo83w> <xmx:bKFwYTRC_hScJVicBYnGBvIXrZXZGJe4QU_sDSvOZ53rLPqZcdyoYA> <xmx:bKFwYXaEkwC8etov4eYLSv03h3tjvPTOM3wNvIkmiX7JU_zDbBrCEQ> <xmx:bKFwYUJj-ybGpYwFJNjRexwiwZ9AeZvZOZm6FXMljL3RV-U_-VwVyg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 20 Oct 2021 19:08:26 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CABcZeBMKpJAmUD3xc-b5jcyMKQkZCxJK8jFVxBaL==ZnJRA-2A@mail.gmail.com>
Date: Thu, 21 Oct 2021 10:08:24 +1100
Cc: Barry Leiba <barryleiba=40computer.org@dmarc.ietf.org>, "gendispatch@ietf.org" <gendispatch@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F3221D2-0FE4-4135-B874-3CB77B44B7D6@mnot.net>
References: <4BDF1DD9-9D30-499F-8C26-1E7790F2A729@akamai.com> <CALaySJKYG8ydGrgdSKZY1b28VL2DvwTS_3_40y_eFkHcGjdJXg@mail.gmail.com> <CABcZeBMKpJAmUD3xc-b5jcyMKQkZCxJK8jFVxBaL==ZnJRA-2A@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/HNyRbHSHFLulYEONwSmdnhaCcz8>
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 23:08:37 -0000

+1. Our bench is sometimes *very* thin for ADs.

Regarding the IAB - rather than tweak the rules it might be good for the community to have a re-think about the function that it serves (or thinks it does). Once we have clarity on that we can figure out what the best policies are.

Cheers,


> On 21 Oct 2021, at 6:25 am, 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

--
Mark Nottingham   https://www.mnot.net/