IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Tue, 11 January 2022 06:13 UTC

Return-Path: <lear@lear.ch>
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 D15FB3A18CE for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 22:13:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level:
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 ZpjLG2JJ0fyY for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 22:13:34 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 F18C63A18CD for <rfced-future@iab.org>; Mon, 10 Jan 2022 22:13:32 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::3] ([IPv6:2001:420:c0c0:1011:0:0:0:3]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 20B6DRPr126156 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Tue, 11 Jan 2022 07:13:28 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1641881610; bh=hnq2Uyx7P5MjeM6UzX8VgKBQLHwKJHdG8yLsWKhb7WE=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=PxK8Z9vEXthMhGnIK6t7mG4nj6+/V59I3C4Wwmp8nTazWgtNTJ4UodSSRBCVdRpl+ fDaDJJZiDYrWAynUpklVRXfNw7EGRoVhVc23dtLa5fLbIN1KklcGAS7J6l137vIcRr TvTRHpcg6e4r0z1dQ6YrApydjfhDhg1EPyLEupRs=
Message-ID: <a4c25845-bcbc-b417-04d0-5338b0c74708@lear.ch>
Date: Tue, 11 Jan 2022 07:13:25 +0100
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
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>
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> <800bde92-f8ae-a622-c02a-8140d5b9a177@stpeter.im>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <800bde92-f8ae-a622-c02a-8140d5b9a177@stpeter.im>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------ERs45l1FkYD9NTXZE0lXIHb1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/hQpZuYVDzFzcRjEUPl9zTz4yxwk>
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 06:13:39 -0000

Peter,

I think your text captures the issue, modulo two points:

>    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.

I think that "will" must become a "should" or "is requested to", because 
we do not dictate to the LLC in this document and we shouldn't start here.

Also, if your intent was to capture John's point about having a 
diversity of perspectives on the committee, I don't think you quite got 
there.  You could change that line to something like:

> including people with {diverse/different} perspectives,

To answer an earlier point from Eric about whether that parameter can be 
tested, then, the RSAB can then ask the question, “How do these people 
hold diverse perspectives?” and provide feedback on the answer.

Eliot

v2.23.0 | Report a Bug | By Email