IETF Logo Mail Archive

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

Martin Thomson <mt@lowentropy.net> Sun, 28 June 2020 23:47 UTC

Return-Path: <mt@lowentropy.net>
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 18DA73A07E3 for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 16:47:33 -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_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=lowentropy.net header.b=L64r5Rgf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=G5RnZ4e5
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 E-zUFpAkkLU8 for <rfced-future@ietfa.amsl.com>; Sun, 28 Jun 2020 16:47:31 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A72923A07D6 for <rfced-future@iab.org>; Sun, 28 Jun 2020 16:47:31 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id A26488FE for <rfced-future@iab.org>; Sun, 28 Jun 2020 19:47:30 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Sun, 28 Jun 2020 19:47:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=Uun5VwOlCfLc/O32GbG63L4R8mK/tyi srgW2lp5VeY8=; b=L64r5RgfX9vNeQGiClIYaIbZ1qlSq7i6vmD82VG8xADbjvR dSwHGZbiDsEORxtnk+G/JOMsaydQA+A48OmaTnm+f6cu7qFpkL6P0SHuFQfoaTJs XWp0r/VkW+MfylEt/BYANORss2IBVYomj3kJ3jzRKcoebdcwDeewpeZh7veFsVkZ Tfmfkw+A9ZFudMYmpuFmhSxoy6hfF9SDCgdkfUclOY1BXmosWU7AYfBLTrHPK9op RLa690amlQAsIwNS4A51mLuzI8JFXks2PlU6CvbHryPPrT0Tol/i62gWGr2VMGTe zZdzwkZpuTZ2yvolwg4MnBRHRy6MHcz2QM4ao9w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=Uun5Vw OlCfLc/O32GbG63L4R8mK/tyisrgW2lp5VeY8=; b=G5RnZ4e5cooYLg/linq4VJ EBNkM0hAjRrF9qz6Le5qpVgLPcNfgIy7Yacu4yPbmjVR81JodVP2Zv+Y2nArrNsw Q0mEf6IR+Rx3D/t/HYDdLbeqdqhLETuaYLMqMVxPtPuOLnruNcnIe7MSNKhtzNKb 3WCEKSot+MYoZQ4p0q3y0dkBV+gbEJlz+xQ30kdmwuY8umLETqLa22PEZCHwbE1a S/tuokE5dAx37Hq6/WOZMIXPo4ltmn9HGGf6kB6chCxr5uRj0xIwFT4cqrI4e2qH /oXW4iwrJ/7KcMZXZXbNz60E3tt6/K8WtPeb7TLHaa28B5uvNNS/9KoTrUiaFijA ==
X-ME-Sender: <xms:Eiz5XqMDYxbcpQHh0cuD7HTw8V6ehcR90nkHjRyRPfaXAPdS29bdFA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudeljedgvdeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpefhiedttdeviefhjeejgf evfeeuudfggfekveekheeugeegleevkeevkedthfeuieenucffohhmrghinhepihgvthhf rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:Eiz5Xo8ap3lDzoQ1N-xnUROpUcK3K9R8vIa7cfj8db30V1e_g8V6bg> <xmx:Eiz5XhQhN2MO04fU0ZWNq_KFRrLY8jcp7xw40vjzw80phLNobiqC9A> <xmx:Eiz5Xqt5hOHSbUtjEFtyn34zoen1LvmS_tvJj9F9aoKWJnNKKmNoVQ> <xmx:Eiz5Xh80g5SXMae49-2WZ-9yP47kMcMhEMH9mr386rO0IYYnOVdAEA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id E739BE00CE; Sun, 28 Jun 2020 19:47:29 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-543-gda70334-fm-20200618.004-gda703345
Mime-Version: 1.0
Message-Id: <cfd9512d-b61e-4438-9ce3-102f6ddaebe7@www.fastmail.com>
In-Reply-To: <CACOFP=iAzB+hrtZcu4yaDv9mpmxSybGTc-cugWC2Hv==-zTTdg@mail.gmail.com>
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>
Date: Mon, 29 Jun 2020 09:47:08 +1000
From: Martin Thomson <mt@lowentropy.net>
To: rfced-future@iab.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/YZwsS4P0bBxcgciEp0IHG1xKEd4>
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:47:33 -0000

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.

v2.23.0 | Report a Bug | By Email