Re: [Rfced-future] Filling the RSCE position (was: Re: Comments on -07)
Eliot Lear <lear@lear.ch> Mon, 03 January 2022 14:52 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 B97913A096B; Mon, 3 Jan 2022 06:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.603
X-Spam-Level:
X-Spam-Status: No, score=-1.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, 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 746zzphohjZx; Mon, 3 Jan 2022 06:52:08 -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 BF0893A096E; Mon, 3 Jan 2022 06:52:05 -0800 (PST)
Received: from [192.168.0.129] (77-58-147-26.dclient.hispeed.ch [77.58.147.26]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 203Epr8Y2463789 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 3 Jan 2022 15:51:56 +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=1641221518; bh=ncziDl0uFcUqnhK6iEKvlUcmcNMR0aIwzEVBmGaSMtg=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=r7cphHCGiJeOx7kWzyCaiyS8QWp5ZqBRUTjeBYJy+HGEgRrX8o0FqiQCfCbTxkRcB Yt0+wD8NvCk4b62ynQDpf0S7G9Wh1IXdkVrspAJZMlYD6hpqZtHUKokzQuHnApVQiu 666P19YQE5wFkUJRNKu/ak+8cOad5Gxy7AeSdrYw=
Message-ID: <de858e02-a6ff-613b-3d2c-db85d5ea42b1@lear.ch>
Date: Mon, 03 Jan 2022 15:51:45 +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: Mirja Kuehlewind <ietf@kuehlewind.net>, Jay Daley <exec-director@ietf.org>, John C Klensin <john-ietf@jck.com>
Cc: rfced-future@iab.org, Michael StJohns <msj@nthpermutation.com>
References: <F0016CA1725A561034951054@PSB> <7D28CA5F-594B-4212-9155-86669654A504@ietf.org> <A1A5EDBA-7598-4E74-ACEE-B7A39A8010F5@kuehlewind.net>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <A1A5EDBA-7598-4E74-ACEE-B7A39A8010F5@kuehlewind.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------CN6jvs600aPZm0G7s9jq2XNe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/KPZ0tSIcDU8x4iLigp9CaHlNx0o>
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: Mon, 03 Jan 2022 14:52:14 -0000
Hi Mirja, On 03.01.22 14:43, Mirja Kuehlewind wrote: > This is the text in draft: > > "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.” > [snip] > However, I would also like to note that th text says the LCC Board > forms the selection committee and not the ED. While these are > internals on how the LLC Board manages itself, I would assume that’s > rather a job for the LLC Board chair with approval of the whole > (community-selected) board than the ED. This issue was discussed and > confirmed (changing responsibility from the ED to the whole LLC board > in GitHub issue #40). Yes, that was indeed Issue 40 which you opened in April and was closed after we discussed it in detail and came to a conclusion in July. However, by design, the text above does *not* refer to the board, but rather to the LLC. The sentiment that carried the day at the time was perhaps best summarized by Martin Thomson: > Split the difference and say the LLC is responsible, this would likely > fall to the Executive Director, but no need to explicitly specify that (See the notes <https://notes.ietf.org/notes-ietf-111-rfcefdp#>). It's not that the LLC board DOES decide or that the ED decides on the RSCE position, but rather it is for the the LLC board to decide whether to delegate that decision. What I am drawing from all of this, by the way, is the importance of closing this document, because people really are losing context of the decisions that have been made. The chairs will have more to say on that shortly. Eliot
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Michael StJohns
- [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Jay Daley
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Jay Daley
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Eliot Lear
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 Martin J. Dürst
- Re: [Rfced-future] Comments on -07 Ole Jacobsen
- Re: [Rfced-future] Comments on -07 Martin J. Dürst
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Comments on -07 Salz, Rich
- [Rfced-future] Filling the RSCE position (was: Re… John C Klensin
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Comments on -07 John C Klensin
- Re: [Rfced-future] Comments on -07 Martin Thomson
- Re: [Rfced-future] Comments on -07 Martin Thomson
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… Eric Rescorla
- Re: [Rfced-future] Comments on -07 Michael StJohns
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Stephen Farrell
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Eric Rescorla
- Re: [Rfced-future] Filling the RSCE position (was… Jay Daley
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… Eliot Lear
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… Mirja Kuehlewind
- Re: [Rfced-future] Filling the RSCE position (was… Lars Eggert
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Filling the RSCE position (was… Peter Saint-Andre
- Re: [Rfced-future] Comments on -07 Peter Saint-Andre
- Re: [Rfced-future] Filling the RSCE position (was… S Moonesamy
- Re: [Rfced-future] Filling the RSCE position (was… John C Klensin
- Re: [Rfced-future] Filling the RSCE position (was… S Moonesamy