IETF Logo Mail Archive

Re: [Rfced-future] Issue 151: Consultation / Approval for RSCE Selection committee

Russ Housley <housley@vigilsec.com> Mon, 10 January 2022 19:59 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C90D83A10A9 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:59:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BBrrhKXdTNTX for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:59:11 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 859273A10A7 for <rfced-future@iab.org>; Mon, 10 Jan 2022 11:59:11 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id DFDAB11EE1F; Mon, 10 Jan 2022 14:59:09 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id D453211CEC6; Mon, 10 Jan 2022 14:59:09 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <C6C07861-A0EF-4C74-A5EC-A6D6ADD4F367@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F9109100-0C44-463C-829C-B8662FF2E424"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Mon, 10 Jan 2022 14:59:09 -0500
In-Reply-To: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>
To: Eliot Lear <lear@lear.ch>
References: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KxU0cgP-KziDV3sldenhSJXj6Rg>
Subject: Re: [Rfced-future] Issue 151: Consultation / Approval for RSCE Selection committee
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 19:59:16 -0000

I agree with the suggest that Brian made about consulting with the four stream managers.  It does not need to be a prolonged consultation.

Russ

> On Jan 8, 2022, at 3:44 AM, Eliot Lear <lear@lear.ch> wrote:
> 
> Hi,
> 
> I've opened a separate issue on the discussion that John Klensin initiated regarding how the selection committee has formed.  At this time, I would like to ask if others believe that there is a concern.  If not, we will not make any changes.
> 
> To review, John has proposed that the RSAB be consulted once the ED has a proposed search committee.  I suggested that the consultation could occur earlier.  Jay pointed out that any such change would delay hiring of the RSCE and didn't think the change was necessary, as he is consulting this group.
> 
> One way forward might be that we put together a proposal in the RSWG to address this point, so that we can get on with the hiring.  That would of course require rough consensus and approval.
> 
> Another way forward might be that the text doesn't become operative until after the RSWG and RSAB are formed.
> 
> There may be other ways forward.  Please indicate your preference.
> 
> Eliot
> 
> 
>

v2.23.0 | Report a Bug | By Email