Re: [rsab] RSAB Chair Selection Process

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Thu, 18 April 2024 16:46 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: rsab@ietfa.amsl.com
Delivered-To: rsab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2AFDC15109C for <rsab@ietfa.amsl.com>; Thu, 18 Apr 2024 09:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=kuehlewind.net
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 76I-tFJK--24 for <rsab@ietfa.amsl.com>; Thu, 18 Apr 2024 09:45:59 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6211BC14F68C for <RSAB@rfc-editor.org>; Thu, 18 Apr 2024 09:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: Content-Type:Content-Transfer-Encoding:Content-ID:Content-Description: In-Reply-To:References; bh=/Jh68SuuH4XKbOTJELh6IFONQzL92z9jWzCxcjDtkvg=; t=1713458759; x=1713890759; b=DKGmreQTbUCisRcGHGY/9EwpkIBfFBhNWILlDa8u5rclLGd yxe46bfJLUUURV0gRxIemBdMYohTnBDW2d937WjgZTntCNrvr723sTRuZ/Jaaii9TrBY9ueTLSVjE 96u+Rh5RY4p8e5lWIEiDDKnPV5Cc1ZDYOSDjDQCFK41O64IxOM5ghl2HHa7XOLoDjcv8LZhvV5Qn3 nv01cOZ3Kmvr6zM39W5y9uKzsp+Jf+CdGQARQdduMQ2cXVFe6oCE81tuHg5+TiOpCwHcIxgosgJff 1+e3g0QtaeXkfE22AAoTVwdZpTVAhyF5qV2k7gB/q5i9j1O2rtTzVtwH3OvDdSHw==;
Received: from dslb-002-207-003-144.002.207.pools.vodafone-ip.de ([2.207.3.144] helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rxUtZ-0002n5-5s; Thu, 18 Apr 2024 18:45:57 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <1D49B36C-A617-4301-972F-54C710A951D9@amsl.com>
Date: Thu, 18 Apr 2024 18:45:46 +0200
Cc: RSAB@rfc-editor.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E64F7F3E-9612-4048-9857-AE76925E2CE5@kuehlewind.net>
References: <1D49B36C-A617-4301-972F-54C710A951D9@amsl.com>
To: Cindy Morgan <cmorgan@amsl.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1713458759;719787bb;
X-HE-SMSGID: 1rxUtZ-0002n5-5s
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/H3jUVHTGtHC7cdRv0o1lTBfLwuo>
Subject: Re: [rsab] RSAB Chair Selection Process
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Approval Board \(RSAB\)" <rsab.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rsab>, <mailto:rsab-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rsab/>
List-Post: <mailto:rsab@rfc-editor.org>
List-Help: <mailto:rsab-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rsab>, <mailto:rsab-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2024 16:46:04 -0000

Thanks Cindy!

Just one comment: I’m find to hand over at 120 but we could also hand over right after the selection is done. Actually I don’t think there is a lot to handover, so anytime the new chair wants to start is fine! As such we can also decide this when the new chair selection is done.

Or, Cindy, do you think we need some kind of meeting to officially minute the chair selection? I would think just announcing it officially to the respective lists should enough?



> On 17. Apr 2024, at 19:35, Cindy Morgan <cmorgan@amsl.com> wrote:
> 
> Hi all,
> 
> It is time to kick off the RSAB Chair selection process for this year.
> 
> If no one has any objections to this by the end of next week (2024-04-26), I suggest using the same process we used last year as outlined below.
> 
> Proposal:
> 
> • Monday 2024-04-29: I send email to the RSAB list soliciting 
>   nominations (or self-nominations) for RSAB Chair. Nominations will 
>   come directly to me.
> 
> • Monday 2024-05-13: Deadline to submit nominations.
> 
> • Tuesday 2024-05-14:
> 
>   - I send the list of candidates who have confirmed their nomination 
>     to the RSAB list.
> 
>   - I set up a thread off list (or on a new list) that includes voting 
>     RSAB members, minus any chair candidates. Discussion of the 
>     candidates commences on that thread. 
> 
> • Tuesday 2024-05-21: I send out an e-vote. E-vote closes once all 
>   non-recused voting members have voted.
> 
> • New Chair term begins at IETF 120
> 
> For context, RFC 9280 says:
> 
> 3.1.2.5. Chair
> 
>    The RSAB shall annually choose a chair from among its members using 
>    a method of its choosing.  If the chair position is vacated during 
>    the chair's term, the RSAB chooses a new chair from among its 
>    members.
> 
> Thanks,
> Cindy
> 
> -- 
> RSAB mailing list
> RSAB@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rsab