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

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Tue, 19 September 2023 10:19 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 D3FC7C15C524 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 03:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.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 lnRWCBnpUgZP for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 03:19:41 -0700 (PDT)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 15662C151536 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 03:19:41 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id af79cd13be357-76dbe263c68so244303485a.0 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 03:19:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695118780; x=1695723580; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=safKN9LW1AVAmCWwZI+zzAZyjXHVbwTUiedEoNzqOHg=; b=RvgNBPXsd6gsOcc7RMSHLCUcZeCiGdxTBgc8hbEfSoUcC9DSsQDOC0diBPXFemOuGh MG7jl67meCbF4CODnvNfFFc87UAmQjiC6QA+SZjr6xdsn+zdkqh68ygng4Pc/72yjuFO G1oDW+00tkE5DIl++d2p+9sF+14k16KqYB3aja1CjwoDSc79PC/Zp1YG57lOwLMXvSlC FdTbuG52gkHLCqTex79I9X0yEnUNqURkURmfBACpi9mJOp1l6sfXzIQyEkZWLC7i8qI9 f5iuXGZqYDFYLBj2cr0j1DsZstnPU8LHWwlTg8mAhCyzrO0UuJsMig54XWCV8wfGhNvG XxvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695118780; x=1695723580; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=safKN9LW1AVAmCWwZI+zzAZyjXHVbwTUiedEoNzqOHg=; b=UQnBgyEv0vOWevZKKOJ4kc+EukNulc7tbFYodKqUAYdvyb49aPcEjukqtG7B/EKhHP 5mg+Xa+C9/jTvbHcnKD5vQsj8mfDi4S9IM3BjkkRXlOkeBQlzct7gZO7Ru8d0rw78zHi 2Yl4/AiRfuuE3aFpw6YeG5zQ/mI3k8f7jx4QwLFrxDEdx8e96r3yDezdLidKiSROitVo 97+QF7gK62maQEAIHLN5mlvrAhEK5jqesnSoqr4CpB03Kx0G/yqokhydGQPiU1/sgquX SiTj2MPLwRJmLmGhfYPPSXePAH6y2WZayvmA6xyugDhyAKnZGvq2K3j6qPSsCUKRUg6x 3ohA==
X-Gm-Message-State: AOJu0YyLfQbtZ+quwjkMOrXaMGyVZTgnoGXrepRUwbgd/g6doakpjzcq n9wnDxBBHo/KQR1IxEKuV5ZzMNPOA1g=
X-Google-Smtp-Source: AGHT+IG3CkLNQ+rh+wLti1/0ZhYR0mscoEKcntcYzwU7FkXjLD3Aq3FopoznpoCseLT6HQzyaC0ATQ==
X-Received: by 2002:a05:620a:4486:b0:76f:bb9:a4c1 with SMTP id x6-20020a05620a448600b0076f0bb9a4c1mr2700393qkp.18.1695118779565; Tue, 19 Sep 2023 03:19:39 -0700 (PDT)
Received: from smtpclient.apple (146-115-101-80.s7246.c3-0.arl-cbr1.sbo-arl.ma.cable.rcncustomer.com. [146.115.101.80]) by smtp.gmail.com with ESMTPSA id u15-20020a05620a120f00b0076f1d8b1c2dsm3867501qkj.12.2023.09.19.03.19.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Sep 2023 03:19:39 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Tue, 19 Sep 2023 06:19:28 -0400
Message-Id: <531E8702-FB7D-4C12-A77D-9F787E50BF42@gmail.com>
References: <7ce45a73-06c3-ad3c-9960-c0ac59161278@it.aoyama.ac.jp>
Cc: ietf-nomcom@ietf.org
In-Reply-To: <7ce45a73-06c3-ad3c-9960-c0ac59161278@it.aoyama.ac.jp>
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
X-Mailer: iPhone Mail (20G81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/g-sv2InES1L83V4uWYdaRMhvl7I>
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 10:19:44 -0000

I also support a reset to 2 years.

Best regards,
Kathleen 

Sent from my mobile device

> On Sep 19, 2023, at 4:22 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
> 
> I support this proposal (to reset the term). It's simply what makes most sense.
> 
> Regards,   Martin.
> 
>> On 2023-09-19 16:05, NomCom Chair 2023 wrote:
>> All,
>> In discussions of the process for replacing Lars as IETF chair, it was observed that the IETF chair role is exceptional. With the vacancy coming at the March IETF, it is possible that the term could be reset.
>> According to Section 3.5 of RFC 8713, when filling a vacancy of precisely one year, the new term is a single year. Though this does not apply in this case, a vacancy that occurs after the meeting results in a term that is almost three years.
>> For other positions, it is necessary to ensure that the usual cadence of replacements remains synchronised with other appointments to the same position. The IETF chair has no such need.
>> In requesting that the NomCom fill this vacancy, the IESG have expressed a preference for a two year term. However, this would deviate from the documented process.
>> The question therefore:
>>     Should the cycle of appointments for IETF chair (GEN AD) be reset?
>> If the term is reset in 2024, someone selected for IETF chair would have a two year term. Subsequent IETF chairs would then be selected for 2026 and subsequent even-numbered years thereafter, or until a similar reset occurs.
>> The NomCom would like to solicit community feedback on this suggestion.  Input on this process is welcome over the next month at ietf-nomcom@ietf.org, ending on 2023-10-20.  As the responsible body for RFC 8713, the IESG will be responsible for judging consensus and whether this process variation is acceptable to the community.
>> If the community does not reach consensus, the rules in RFC 8713 will be followed strictly. The next IETF chair will be seated for one year.  The possibility of term variation will be made known to prospective nominees as part of the upcoming call for nominations.
>> Martin Thomson
>> nomcom-chair-2023@ietf.org
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom