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

Peter Saint-Andre <stpeter@stpeter.im> Tue, 11 January 2022 01:47 UTC

Return-Path: <stpeter@stpeter.im>
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 798B33A09E0 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 17:47:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.812
X-Spam-Level:
X-Spam-Status: No, score=-2.812 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, NICE_REPLY_A=-0.714, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=JQ7lwv4L; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=DQaN/551
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 9PgtD2EkmNEY for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 17:46:58 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E73ED3A09DF for <rfced-future@iab.org>; Mon, 10 Jan 2022 17:46:57 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 93BF75C014B; Mon, 10 Jan 2022 20:46:54 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 10 Jan 2022 20:46:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h= message-id:date:mime-version:from:to:cc:references:subject :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=+ Po9Psh58SyJywfIaUZ55Khg2Mm/1VOeVtkqw0EUwS8=; b=JQ7lwv4LhlWetrfHU hqI2G8o53SWc9pu746STP/HX93Vwbu665dcZkRtxvvaROefXY6KdptALtgZ/RXSj Wloett4xI0NotmdDXjF9JTBlZVCnZH/qEwy6TXVLRzzG+ZzmEjaGwp/3OiY+95Fj y0148m1TcmGKikTrWyP02lRCcfOTOsR/NZTtkz7eW/w0Cu8SXq+l3F8/xG+6Urz6 0tfiVcij/sdRsDrMpoBFFuw0Uw8peYnsDPWU0vun2jfTVfeIIUfQVAN5/HGcQq2w xB3iv5XxIh5/Lptgcf1e1RnbrT0wyioSjvC63Yi9sSnCwlKtpuG5I8i+Ic2plIA0 y3lEA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=+Po9Psh58SyJywfIaUZ55Khg2Mm/1VOeVtkqw0EUw S8=; b=DQaN/5510l/fviGHCFUac63LVfAnN8RFSjaeYA+4nWhSApfOEHcPcHm50 ZkxbBu8PfK+TwXYf4ufkmtFksz1uGaB6a4Amhn1qW8XIEexO4OZvjGWpZQJN/B1L iWrW/p9TLq3fTBawAH1Qc7YXJT/UDNWjz2Y3HXk/MGw4fqVarDE0XMZBs/371hdO lw/PzH06c2gQDRVqXSLml0cyioQIoluH1SombIRLfUUxS5GQYCiCDdqAQq51rpbn VnNSIWwfss44Bivz1lZhXy5rWKlTo3KFIhcAXLNl4Hgp2n6lusfbE6YBdwumX6a1 sLRWBXI5Aqf84o9lB5xo/tYsbypvQ==
X-ME-Sender: <xms:juHcYaMTdwQmvEFmQYVUZo69V7fmQ22AD5RDF5BfqdJigEsE0HWYuQ> <xme:juHcYY_qkZ70amg5b_lDF7GXVXgftQmOo3MoFmBWVRWzFx9YW_7Ft_DsNxsaaEGoZ SzSeREpiSDKlnTLcQ>
X-ME-Received: <xmr:juHcYRSxEdIh2TODXCnIeCrC_jGHTD8wm2dxSnNk6cSqy8YFJ2q79i6PVrNsVjrqg0Qh21ZBP6OnZX8Cy0O8ohOnlvSbJnmA4jkNPLg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrudehvddgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfhffvfhfujggtgfesthekredttdefjeenucfhrhhomheprfgvthgv rhcuufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqne cuggftrfgrthhtvghrnhepudejteehtedujeekvedvfedvleeghfffveeiveffleefgeel tdehvdfgueegtdfhnecuffhomhgrihhnpehirggsrdhorhhgnecuvehluhhsthgvrhfuih iivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshhtphgvthgvrhesshhtphgvthgv rhdrihhm
X-ME-Proxy: <xmx:juHcYavJ8zH5VoW_E18YSNNoUzof8v4HEGOoeUGCSUtN7gXn9WiDJw> <xmx:juHcYSdE5Ls4z3dUHZiN7Hb-FDGFnMRRQ3V4jNpJh5GhqiSo5CF6ug> <xmx:juHcYe2qRjxixf70FJSavnPj95egSYFhp_4sE08JNwuuIGaMRLjTmQ> <xmx:juHcYS6hLnaUPbl4ymSNgEDnU7oq9KatN_GD3GN-QKEiPls-5PtzVA>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 10 Jan 2022 20:46:53 -0500 (EST)
Message-ID: <800bde92-f8ae-a622-c02a-8140d5b9a177@stpeter.im>
Date: Mon, 10 Jan 2022 18:46:52 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
From: Peter Saint-Andre <stpeter@stpeter.im>
To: Eric Rescorla <ekr@rtfm.com>, Eliot Lear <lear@lear.ch>
Cc: "rfced-future@iab.org" <rfced-future@iab.org>, Russ Housley <housley@vigilsec.com>
References: <a1d634a5-dad4-7bfc-ed6f-08e00fb31446@lear.ch> <C6C07861-A0EF-4C74-A5EC-A6D6ADD4F367@vigilsec.com> <4427b157-8ad9-9152-28ae-5db750932d66@lear.ch> <CABcZeBOXXVe8sMzUt8VtZBR2oOoSOdV--1J6_pvmdfGTt-j3RQ@mail.gmail.com> <1539b2df-ef80-ca11-fea8-e88cd60b142a@stpeter.im>
In-Reply-To: <1539b2df-ef80-ca11-fea8-e88cd60b142a@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/IeecXCxZa9f33WeA7Pm55eRQmjk>
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: Tue, 11 Jan 2022 01:47:03 -0000

Proposed text for Section 5.1...

OLD

    The IETF LLC will form a selection committee, including members from
    the community, that will be responsible for making a recommendation
    to the IETF LLC for the RSCE role.  The selection committee will take
    into account the definition of the role as well as any other
    information that the committee deems necessary or helpful in making
    its decision.  The IETF LLC is responsible for contracting or
    employment of the RSCE.

NEW

    Responsibility for making a recommendation to the IETF LLC regarding
    the RSCE role will lie with a selection committee.  The IETF LLC will
    propose an initial slate of members for this committee, making sure
    to include members from the community, and consult with the stream
    representatives regarding the final membership of the committee.  In
    making its recommendation for the role of RSCE, the selection
    committee will take into account the definition of the role as well
    as any other information that the committee deems necessary or
    helpful in making its decision.  The IETF LLC is responsible for
    contracting or employment of the RSCE.

On 1/10/22 6:36 PM, Peter Saint-Andre wrote:
> +1
> 
> On 1/10/22 1:26 PM, Eric Rescorla wrote:
>> This seems fine to me.
>>
>> -Ekr
>>
>>
>> On Mon, Jan 10, 2022 at 12:23 PM Eliot Lear <lear@lear.ch 
>> <mailto:lear@lear.ch>> wrote:
>>
>>     I'm beginning to see a rough consensus here.  Are there other views?
>>
>>     Eliot
>>
>>     On 10.01.22 20:59, Russ Housley wrote:
>>      > 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
>>     <mailto: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
>>      >>
>>      >>
>>      >>
>>      >
>>     --     Rfced-future mailing list
>>     Rfced-future@iab.org <mailto:Rfced-future@iab.org>
>>     https://www.iab.org/mailman/listinfo/rfced-future
>>     <https://www.iab.org/mailman/listinfo/rfced-future>
>>
>>
>