Re: [Rfced-future] Scope and IETF 108 proposals

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 28 June 2020 23:50 UTC

Return-Path: <jmh@joelhalpern.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 43E973A0FBF for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 16:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H4=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 (1024-bit key) header.d=joelhalpern.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 gK8QzxluoRHs for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 16:50:37 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 34E173A0F97 for <rfced-future@iab.org>; Sun, 28 Jun 2020 16:50:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 49w6nT08kbz6GD4m for <rfced-future@iab.org>; Sun, 28 Jun 2020 16:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1593388237; bh=tVIViBvInXvmwINOo7Kv6i0AHdcoCUTRfxJcK6E74so=; h=Subject:To:References:From:Date:In-Reply-To:From; b=R3UICh2TCiIUZPIluFmxHvD2vT93xWa9DAWPQNmyfLrqvGgb8k8hBJzCcGv2NciKs TPd+Ecj3LdtGZbPP/4hx41HoNyrsDzidyAkONlNVym4KH2mD7w6NhIF5Cra5/Die7A CBr7mkArmRXt3J2YRwSLmXTLxTIpig82qprg7pMc=
X-Quarantine-ID: <195ltK8_m5_E>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 49w6nS4NZBz6GBpY for <rfced-future@iab.org>; Sun, 28 Jun 2020 16:50:36 -0700 (PDT)
To: rfced-future@iab.org
References: <62A4C70D-419A-4DE3-8A54-60EB2B064EF2@brianrosen.net> <8c626e3e-1700-46fe-90b3-26b9c1296788@www.fastmail.com> <1b6cf5e6-2c16-d839-08dd-d005d4fdbc60@gmail.com> <3678427d-6496-45c7-bd1b-14d7f860c971@www.fastmail.com> <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com> <cfd9512d-b61e-4438-9ce3-102f6ddaebe7@www.fastmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <befe8914-996a-d4f0-f9ef-cc49d882839c@joelhalpern.com>
Date: Sun, 28 Jun 2020 19:50:35 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <cfd9512d-b61e-4438-9ce3-102f6ddaebe7@www.fastmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/YkRHS_8w_-nEsRFOikkonyVcuRQ>
Subject: Re: [Rfced-future] Scope and IETF 108 proposals
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: Sun, 28 Jun 2020 23:50:38 -0000

In my view, the reason we need a person to do this is that leadership by 
committee is essential equivalent to a recipe for disaster.  And I do 
think we want leadership.

Yours,
joel

On 6/28/2020 7:47 PM, Martin Thomson wrote:
> On Sat, Jun 27, 2020, at 13:01, Nevil Brownlee wrote:
>> I've updated my Internet Draft to include a suggestion of what an RSEB
>> (RFC Series Editorial Board) could be structured. Take a look at
>> https://www.ietf.org/id/draft-brownlee-rfc-series-and-rse-changes-01.html
> 
> This is very much not what I had in mind.  We should not insist on having a role that depends on finding an individual with a rare and difficult combination of attributes.  And I don't think that you can support that function by taking a program with open participation and consensus processes and reduce that to 5 people (+stream manager ex officio) who are responsible for approving strategy.
> 
> Perhaps you can start by explaining why you think we need to have an individual perform these functions.
>