IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 08 January 2022 20:44 UTC

Return-Path: <brian.e.carpenter@gmail.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 66BEF3A0BB3 for <rfced-future@ietfa.amsl.com>; Sat, 8 Jan 2022 12:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.813
X-Spam-Level:
X-Spam-Status: No, score=-2.813 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, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLSDB3iZsPuv for <rfced-future@ietfa.amsl.com>; Sat, 8 Jan 2022 12:44:40 -0800 (PST)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 65D973A0BB5 for <rfced-future@iab.org>; Sat, 8 Jan 2022 12:44:40 -0800 (PST)
Received: by mail-pl1-x633.google.com with SMTP id c3so8664889pls.5 for <rfced-future@iab.org>; Sat, 08 Jan 2022 12:44:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=QRw/VxtbiDFS0AyCXpm8BwEJM9JqwiUPQ6hO66mPIxQ=; b=Zed/jna6XNIYPA6ZvcH2QqZ4CGFC6lQ/vGYREIxJeGtEezPxL34KyqXqXcx29jrU91 Rtf3Qr8PkgTR5glNZX7QJ4CxLgi1PqSzQQEQdy1SOXcdxWUYoKgAtxmPCbNmtmVF9EH+ ol23g/cN8m+wWwIyRgWTyRAY/o+IM6HqZrsaaaWAicLYL3ZnCkReKpJ2NFCXE2IvDfxg WtSTFPCSxcIbed+w3nG5+Hn31H1Roe4++Ps6i2W0Dqn8y4Gs3mn8WRef4TKKLJ/xB7Tl UcOSYeDlfgSqAczioffm356st9wUZlxDJSPYFyguu3GpB7qsMrI+9jOYDHgu/EhXtTAN rcbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QRw/VxtbiDFS0AyCXpm8BwEJM9JqwiUPQ6hO66mPIxQ=; b=13YI4Z0mXAnNTYmguTI/czj4OpgDU9+Y2cVD0a675/HKI7A8QV4h70vxHstIwzE8+X 4pAk4QbXFAp+8a9LWBk9XTHrn+Bv/7spD/TUHIXvBiivzJTaP6PAmgZDpwi4TLl2yw+p TIOj+SxA7+rGmTTvHA/VUNCLptWLDlOX3rQlDwLW5UXJ/XKuvqSZ4Qzke1E6SV1uNTyl 0s9/75NLiGbBS7UyX//Wdyrwz6e+MJgdHIknmFiMjMN6xlT3JsNAHwtZrJVHPlGqcJ72 f/lKJLb+qh32yGnNOU7kpTC+m+5WApYZbj9s7RD3Q48dKPyssyjkFm5FZkNB1tPbPEVj 7V8A==
X-Gm-Message-State: AOAM5304imZVeW8eFRKtMA8yRbtpT1M/dYvjHDsW3r81CO6jEXxvP/JT 4Nlwg6rlCmBMxtY/ku1QqkssDTpewHpsBA==
X-Google-Smtp-Source: ABdhPJxL/EGQXRzgpv5w1MXVRwjpo7f2tcU9GEstQlD+em3kNd7cJJfGUhgy0hKVR6saDiEsxt1Zjw==
X-Received: by 2002:a17:902:854a:b0:149:6297:e90 with SMTP id d10-20020a170902854a00b0014962970e90mr65100363plo.58.1641674678033; Sat, 08 Jan 2022 12:44:38 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:80b2:5c79:2266:e431? ([2406:e003:1071:1701:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id c9sm2679770pfc.61.2022.01.08.12.44.35 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 08 Jan 2022 12:44:37 -0800 (PST)
To: Eliot Lear <lear@lear.ch>, "rfced-future@iab.org" <rfced-future@iab.org>
Cc: John C Klensin <john-ietf@jck.com>
References: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bac74525-c48f-9c04-0ffa-c191d334feab@gmail.com>
Date: Sun, 09 Jan 2022 09:44:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/deV93AeDo1RENV_xVhtcG2P7zZo>
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: Sat, 08 Jan 2022 20:44:45 -0000

> To review, John has proposed that the RSAB be consulted once the ED has 

> a proposed search committee

How about specifying that (for the initial RSCE) the four existing stream
managers should be consulted? That avoids waiting for formal RSAB creation
but has the same effect. For any future RSCE searches, the RSAB will be
available for consultation.

Regards
    Brian

On 08-Jan-22 21:44, 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
> 
>

v2.23.0 | Report a Bug | By Email