IETF Logo Mail Archive

Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program

Mark Nottingham <mnot@mnot.net> Mon, 30 March 2020 21:12 UTC

Return-Path: <mnot@mnot.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 C47183A03EE; Mon, 30 Mar 2020 14:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=11cLtEJL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FVhGGVsJ
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-nSQHMnV2yg; Mon, 30 Mar 2020 14:12:26 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1C673A08B1; Mon, 30 Mar 2020 14:03:30 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EC8B85C00E6; Mon, 30 Mar 2020 17:03:29 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 30 Mar 2020 17:03:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=p Z9k3uKdgP6NUdskD0yLxZ+j8dpcFVFZdVkTLtrx8QI=; b=11cLtEJLxISr6Zahg KIXLMUztiJVX1IhN7ZjXDgBf+JpYF17j/hstV8mUOjUB6uN/k8phGkXtOvy/LQvH 9ZReb331s0PWntzKp3T6H0fKuvs5Q5XD54iSwj5BHQzpYwQFR3LsiSRi0SSEY5AK UpGe0h8U5yavN/DA77YyMPFOWdWUtk4RlFPHcCBcsstyU1N2jOm+CTUiO7YOu1kP 52Ln11qZ0LzEcIINO8J7tRlnsu3F1kB75wxxVTBpO3n0AEqFVf5VLrrM4mwdzC9d 12M6y/ZS9opBMSdTLMQAi0doIg3OgDqBNZ4Svd17OIhrP1ZFs4U00v53AuqlsoQr KbsGg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm2; bh=pZ9k3uKdgP6NUdskD0yLxZ+j8dpcFVFZdVkTLtrx8 QI=; b=FVhGGVsJS09q8gumdbthAwjUx+0qJlxHgW9BWhYHZZmjVZBJqW4yAa5NU 75FopicckLzMmKkqUAlRvW1QUkYVqDG/5rkQH6Pj9r7po1tUlsjzJ9gtiziT8QT1 CLz0mjUbmw/e9X2WGg0gETTiD3xii5PZ+JNAtLZTlbSjTXxNoB0kkVKj7qEIKilo Ym1zwffOjIw6urR2YB3/nkZ6hhvBIl3Sg0zseMfUW/1l1dWN4kvGy06jxJZT9F4y hrDC2q79ZWb+Y1K/xE0Ex5HUJxf0gTL/zNgf8HjAlmYZuO/PaxaxozMCjfAeLbOD xS4fV6ARNU42GR0jkJiMl7V/2YNcw==
X-ME-Sender: <xms:oF6CXiWe0kp5GGu3KTnP19uPGzl4zlZNu5w4nL-jPoB78EzzCuWooQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrudeihedgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrih hnpehmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddvhedunecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhoth drnhgvth
X-ME-Proxy: <xmx:oF6CXpSgeDZzs24-Sy2ZtxFW9jqLE3EJLpwpGd4DkUkCRtKROz6bvg> <xmx:oF6CXi24kV9ioAGROke9lHkbGnkYkkfnPKl_wzn_gUodydONGgcF4Q> <xmx:oF6CXvWr0BUvp2kFHQzo5Q1BLqGu1uqGtOYc-mS5fc6k7ZErAX1MAw> <xmx:oV6CXprIBfFG5EoQjx0-fWSKGy7DOiuwxC64nDDSO-gNqokyxMAwxQ>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 95241306CA3D; Mon, 30 Mar 2020 17:03:26 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <ad40f5c1-5551-3e3e-9bc3-164ec3368b68@gmail.com>
Date: Tue, 31 Mar 2020 08:03:24 +1100
Cc: Wes Hardaker <wjhns1@hardakers.net>, Michael StJohns <msj@nthpermutation.com>, rfced-future@iab.org, IAB <iab@iab.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <16726C73-09AB-4F61-8C00-8224E3EF6F1B@mnot.net>
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <CAA=duU0_pr_56HTR5vZg+AK981rkvGrMGFFi-UHgW4L=6=6mwg@mail.gmail.com> <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com> <0E6D83F8D11D8C1B9B7237B7@PSB> <73C27FFD-BD81-4CF3-9D9D-845DE9544A36@cisco.com> <097a60d7-2229-b849-1ca3-1f6d298cceed@nthpermutation.com> <yblpncthb1n.fsf@w7.hardakers.net> <ad40f5c1-5551-3e3e-9bc3-164ec3368b68@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/HufwFdJFDUQtNuGcSAjHBAjGI7o>
Subject: Re: [Rfced-future] [IAB] Welcome to the RFC Editor Future Development Program
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, 30 Mar 2020 21:12:31 -0000

> On 31 Mar 2020, at 7:37 am, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> what are the basic principles
> of the RFC series and its Editor's role? I'm not sure that has really ever been
> properly written down as a separate "mission statement" or whatever.


One thing that occurred to me recently is that, while this program is defined with the following scope:

>  Discussion of changes to how the RFC Editor function is managed, staffed, and overseen are all within scope. 

It isn't said whether discussion of the RFC Series itself (and potential changes to it) are in scope. Defining the principles of the series seems like it's more the latter than the former.

Could we (Eliot?) come to some determination about whether the latter is in scope or not for this program? I suspect having that well understood -- either way it goes -- will help considerably.

Cheers,

--
Mark Nottingham   https://www.mnot.net/

v2.23.0 | Report a Bug | By Email