Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal

"StJohns, Michael" <msj@nthpermutation.com> Tue, 19 September 2023 22:32 UTC

Return-Path: <msj@nthpermutation.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975E8C14F5E0 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 15:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.904
X-Spam-Level:
X-Spam-Status: No, score=-6.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HAS8oo-McLqH for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 15:32:47 -0700 (PDT)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5B31C1519AD for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 15:32:47 -0700 (PDT)
Received: by mail-ed1-x52e.google.com with SMTP id 4fb4d7f45d1cf-52a250aa012so7620163a12.3 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 15:32:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1695162766; x=1695767566; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=toPM3uM0HKsMW3X8TVhadXwle+wiYp2As+VF/VqKIC8=; b=D+yiFtO/NjkU/ycOYZzqiCpQRgBdyBUOgFritXD3WmGcZG/9/pcFvSssa8cgA73I7w I0xyDDbVUe9TKqD6oFc+Vxkhyuqiv11eyKZOoSutaICItKtEVY22N6ULv5+LExZEG/6l Cue72r7ezlVw4tfjFNKnEOQzgArCTdtfWWoA/j7ZiKVxjEx0+SFqzUAmgK8FqYAjLHt0 IzUxK/K0wdcQzMJL79wj1yM822x0puJw24ZsAUJAiHLOYPSU5aeYn9/xPdLUqH6Wk0bG DVNnTtVh6Icd+2V2AOVZ5kxuYKXRwwb/jRc9LMbTJT69BEO3YGJ1TiIY6yrL1m7NppS8 PS3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695162766; x=1695767566; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=toPM3uM0HKsMW3X8TVhadXwle+wiYp2As+VF/VqKIC8=; b=Okbw85j1R4nyHAZJhK4iAR4WZDgIpgo1okMYx3enkgS4chUvnGVEV8M1Gi01XxKUDQ l8UFSgN9T7MHZPOjCwkax2Ln1EhT1LkhjSD69I2gBg1NEOOSA71VZsQrtvQHZlhM6P1Q ThrvbsIua5R81qYGxyQaU7u/d5d17T/fsNzLBkAet1YmTXFt2heE1VqbP/59v9m6lr0E YVBC6QiZ2u2PcgSAUzrWgYiJs6tEvk0sPA/FJiN7OeHEN0BKeGzn6S11hfpP0wkZaPeN tRpBNYCKmbYsmBP7RJ4l1UQHFT1u59HOCvl1mjP9/FPJZRLbtphIpxizeztKiHgZt8cS 4rUg==
X-Gm-Message-State: AOJu0YzDsrW99ENP/expiNALArjRU6uhbXligHqO2qZ8OQCtS5CTNNXK FSx0ouiio11VH+NFIMtxEb2lkV7oSjBBVUEUgoV3ZDYDFK2sOdEZ
X-Google-Smtp-Source: AGHT+IG5OvOtuzq42noJIndYoqZpNhebGApf2XXnLT9o47zb5D6mOk9VnvjxTrmolpWYpV6tY4pqinLKAW2fGvsWb9Q=
X-Received: by 2002:aa7:cb94:0:b0:52f:fa53:9fb6 with SMTP id r20-20020aa7cb94000000b0052ffa539fb6mr615408edt.10.1695162765390; Tue, 19 Sep 2023 15:32:45 -0700 (PDT)
MIME-Version: 1.0
References: <169510712484.33106.6003546482401163584@ietfa.amsl.com> <d0ed47c1-f6ee-e7f3-4a51-718213703a16@nthpermutation.com> <3695da8c-4b67-4ecd-83aa-46f41314811f@betaapp.fastmail.com>
In-Reply-To: <3695da8c-4b67-4ecd-83aa-46f41314811f@betaapp.fastmail.com>
From: "StJohns, Michael" <msj@nthpermutation.com>
Date: Tue, 19 Sep 2023 18:32:34 -0400
Message-ID: <CANeU+ZB56fJ-dnskg+FQ6-gSNq5z_JDV1fXaANL7cyMP7mG+BA@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: ietf-nomcom@ietf.org
Content-Type: multipart/alternative; boundary="00000000000077c75f0605bdd68b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/cYs1pGe0V5b73XeJavmxrOlo4lY>
Subject: Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2023 22:32:51 -0000

Hi Martin -

It’s not so much the need for 8713 surgery as, if you move the chair
position to this year, you’ll be adding two positions to be filled this
year and subtracting one position to be filled next year - or a difference
year to year of three positions the be filled.

I haven’t taken a look at the total nominal open positions year to year,
but if we started out balanced before this year, next year will fill three
less than you will fill for this Nomcom, and the following year will be two
more than next year and every other subsequent year will be two more than
the opposite year until another reorg happens or you extend an AD term to
three years.  Giving the chair or one of the ADs a three year term will
move the difference down to 1 year to year and equalize the Nomcom
workload.

Mike






On Tue, Sep 19, 2023 at 17:18 Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Sep 20, 2023, at 03:14, Michael StJohns wrote:
> > These sections somewhat interact, and somewhat conflict with section 3.5
> > so I think any of 1+, 2, or 3 years would work.
>
> Thanks for the deeper analysis Mike.  I think we are in the process of
> exploring the limitations of RFC 8713 here, but I think that this is not so
> complex.  The NomCom has been asked to fill the position and the IESG has
> expressed a preference (but preference only) for 2 years.  If that is
> acceptable, using whatever criteria you like, that is enough for me.
>
> (I'm detecting an underlying desire to do some major surgery to RFC 8713,
> but that's a longer term initiative.)
>
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom
>