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

Michael StJohns <msj@nthpermutation.com> Mon, 10 January 2022 01:23 UTC

Return-Path: <msj@nthpermutation.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 2E3443A0FB5 for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 17:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20210112.gappssmtp.com
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 KlVroWP_NcRX for <rfced-future@ietfa.amsl.com>; Sun, 9 Jan 2022 17:23:04 -0800 (PST)
Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA7663A0F5E for <rfced-future@iab.org>; Sun, 9 Jan 2022 17:23:04 -0800 (PST)
Received: by mail-qv1-xf34.google.com with SMTP id kl12so1143791qvb.5 for <rfced-future@iab.org>; Sun, 09 Jan 2022 17:23:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=MyyzVctW52HbotlCmSOAEBTGNsWt7cEbiRbVvGbYMAw=; b=1k8hbyNANG9TmrXBTW54ZtqPVZpMMqQ9Qmz64IxPtnLmqO4ocDzm6ALm/z0BqVQLDu i5d7rq31IYZabYLUKrY2vC9nfiLjlK72f4OocsQiul17xzkkcKGyIibOy84ZCzvT8rW3 p0H55ZkFlniyMSYCMLBj8LVJFBxxWRlFuq7x7PLX2EUhkQWemh1xHpfP/+pn1fyIU8Qy k2HdIws2jVT36xjQpCvmUfihxsQkQ5MU41WrKxy6oXPH0lyzHclBTc+9VA5Jf3R9j49i Z+qJLbPOnfcaUianCSMK1KF12KoX/Wsuko+aFMXptW7IB1SvLfkEGk7a7OqBRPzR4XyD v9YA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=MyyzVctW52HbotlCmSOAEBTGNsWt7cEbiRbVvGbYMAw=; b=jaei116anxuvTmS93b+dLhG21Sz+JWmEG/8pcbiVZqSUCh+J99tuYOcnqwPJZVuYkZ /uvqWauQH+EWTBMPNuS0QRtGNgvFyFmc+aRUknAFFWJexK1T18hwalOeyRW7FRiTx2AS 49YGerLPxGFQzAa/tua04P0y2PQzZt0dRroMP+tCjTBfRaicq9XWIES/5av8ZAorIfyl GbT9zfnXSoBEMIwQWnA3lKGIoQixZHQ97upyP6WUFr3mvK3OcEv4SFFdX9qC0kMADm+h 37D9i9j6mswaFB0LBlhftKsx2X1vKlIKiT8qvDNYDvfQ21YwokrOAlGsFA3BkRwFcS3d iXEg==
X-Gm-Message-State: AOAM532FAhu9q6K8ZNyVa6I2Mgf9X8RmyUmnxOUz/0n8rrO0X/ihc2/2 GHULVsAsuBSsCKg9KIOWi/tq/Zfp0v/ZwmZBNMA=
X-Google-Smtp-Source: ABdhPJyBvBr07gNiHYlTHveHcJOxt5l0Eu8FdcslZsKRos1o0rV6iFVxfybmmor/aLpzsUiW5k0xiA==
X-Received: by 2002:a05:6214:508d:: with SMTP id kk13mr67175735qvb.43.1641777782301; Sun, 09 Jan 2022 17:23:02 -0800 (PST)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id t5sm3545341qtp.60.2022.01.09.17.23.01 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 09 Jan 2022 17:23:01 -0800 (PST)
Message-ID: <c603b53d-4dad-b81e-402d-248222eba0f4@nthpermutation.com>
Date: Sun, 09 Jan 2022 20:23:01 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: rfced-future@iab.org
References: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/9ITNVWBAI8YeJTMuhioW6sjuREk>
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 01:23:07 -0000

On 1/8/2022 3:44 AM, Eliot Lear 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
>
>
I'd like to resolve this in favor of having the RSAB (or initially the 
stream managers as I think Brian suggested) having the option to chime 
in with the LLC formation of the selection committee.  Doing so covers 
the case where we end up with the possibility of a volunteer RSCE where 
there isn't a lot for the LLC to do on the back end (e.g., 
contracting).  Long term we've told the LLC to focus on the business 
aspects of the IETF, and having at least the possibility of non-LLC 
input into the pre-selection process seems to me to make some sense 
regardless of whether the RSCE is hired or a volunteer.

I don't think this needs to be any more formal than an hour long chat 
between the RSAB and the ED/LLC Board on the ED's general approach to 
the process.  And then letting that go forward.  E.g. less specificity 
is a plus.

Later, Mike