IETF Logo Mail Archive

Re: [Rfced-future] Filling the RSCE position (was: Re: Comments on -07)

S Moonesamy <sm+ietf@elandsys.com> Tue, 11 January 2022 07:29 UTC

Return-Path: <sm@elandsys.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 D30043A1C0F for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 23:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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=elandsys.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 HHdPAitMZw8p for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 23:29:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C8033A1C0E for <rfced-future@iab.org>; Mon, 10 Jan 2022 23:29:15 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.195.25]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 20B7Sh5x016706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2022 23:29:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1641886150; x=1641972550; i=@elandsys.com; bh=iWcoea8ew6SiV2qfW+wYnq0K/anQiZKpmxp4dE3wyEU=; h=Date:To:From:Subject:In-Reply-To:References; b=M+Bqpa8XjTEOsi/35qHpl0lV4FkQLDFo/Ibd7O7GZv5YW9kZcwqUIlpOB00is68wH etBO/PjqxaVr4aCBhRtio5EtCekabR3q+sTDPb5LxnCaAI4bwbnLHesugfcs+XnUo7 W74n+LGSr6vV4EKHG/7VsM9UWgev1217FJZQXcuo=
Message-Id: <6.2.5.6.2.20220110231205.07ca1ba8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 10 Jan 2022 23:28:02 -0800
To: John C Klensin <john-ietf@jck.com>, rfced-future@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <2939BCCA4CA75D29739F59D4@PSB>
References: <F0016CA1725A561034951054@PSB> <7D28CA5F-594B-4212-9155-86669654A504@ietf.org> <A1A5EDBA-7598-4E74-ACEE-B7A39A8010F5@kuehlewind.net> <de858e02-a6ff-613b-3d2c-db85d5ea42b1@lear.ch> <CAFB3EA8-11D9-4D55-924A-B66294309869@kuehlewind.net> <2939BCCA4CA75D29739F59D4@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ZY5kG0BLdHG5P33LsvjHcReevwM>
Subject: Re: [Rfced-future] Filling the RSCE position (was: Re: Comments on -07)
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 07:29:20 -0000

Hi John,
At 08:33 AM 03-01-2022, John C Klensin wrote:
>involved before the selection committee is finalized".  We could
>give guidance to the ED (which I assume we could trust Jay to
>accept and follow) or we could request that the Board make such
>a policy, but we basically can't tell the LLC what to do or how
>to manage itself.
>
>So I would go a step further than Mirja: if our intent is to be
>sure the membership of the selection committee is a group
>process rather than selection by an individual, we'd best spell
>that out, at least as clear guidance.

This group is requesting an external party to run a selection 
process.  Details, e.g. the delegation mechanism used within external 
party, is generally left to the external party to decide upon [1].

Regards,
S. Moonesamy

1.  The matter is discussed in Article 5 of the Company Agreement.

v2.23.0 | Report a Bug | By Email