[rfc-i] Welcome to the RFC Editor Future Development Program

Eliot Lear <lear@cisco.com> Tue, 31 March 2020 22:51 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8532C3A0C41; Tue, 31 Mar 2020 15:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.549
X-Spam-Level:
X-Spam-Status: No, score=-0.549 tagged_above=-999 required=5 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=cisco.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 0al9b2SP13It; Tue, 31 Mar 2020 15:51:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEBC93A0C3F; Tue, 31 Mar 2020 15:51:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BA839F40737; Tue, 31 Mar 2020 15:51:53 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id AEF4AF4073D for <rfc-interest@rfc-editor.org>; Sun, 29 Mar 2020 23:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRsKQ8ZpA2F6 for <rfc-interest@rfc-editor.org>; Sun, 29 Mar 2020 23:51:55 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by rfc-editor.org (Postfix) with ESMTPS id 7CCB7F4073B for <rfc-interest@rfc-editor.org>; Sun, 29 Mar 2020 23:51:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8814; q=dns/txt; s=iport; t=1585551117; x=1586760717; h=from:mime-version:date:subject:message-id:to; bh=NR6DT93eWhunDcWa3u1z503mSCYeDyZBnLqb7Nq7OOA=; b=AKoxOxYV52yo0jORL28dQ6LZ0uTDA60nn5NtQi2467jdfXhI7gdcqhPt 5ezJUegVMwWUmH0YDtfD/d8o6+q5iSleBoWjsf5sT95VzKBClRI088gPQ b49lTL+oyHsqqU6dNEcUMprEbGaodqQwAZv5F0bW0M9NUWYMNELOjT5nZ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DgAgC2lYFe/xbLJq1mHAEBAQEBBwEBEQEEBAEBgXuDFVQhEoREiQKHaJNihiSBZwoBAQEMAQEYAQoMBAEBhxs4EwIDAQELAQEFAQEBAgEFBG2FVgyFeAEhS2gCKV0HgwsBgnwPnQSNXDV1X1OFS4RBHQaBOIxLggCBOAwUgh+DUwGBJ4NRMoIsBJcUmVGCRgSCUpQ/HYJMiDCQcKdogzQCBAYFAhWBaSKBWDMaCBsVOyoBgkI9EhgNjikXiGSFQAM/A40JgkEBAQ
X-IronPort-AV: E=Sophos;i="5.72,323,1580774400"; d="scan'208,217";a="24815020"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Mar 2020 06:51:55 +0000
Received: from ams3-vpn-dhcp5419.cisco.com (ams3-vpn-dhcp5419.cisco.com [10.61.85.42]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 02U6prnl000368 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Mar 2020 06:51:54 GMT
From: Eliot Lear <lear@cisco.com>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Mon, 30 Mar 2020 08:51:53 +0200
Message-Id: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com>
To: rfced-future@iab.org
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.85.42, ams3-vpn-dhcp5419.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
X-Mailman-Approved-At: Tue, 31 Mar 2020 15:51:52 -0700
Subject: [rfc-i] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5939998824276666949=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

[Bcc: rfc-interest just this once: if you want to join the program mailing list, you can click here <https://www.iab.org/mailman/listinfo/rfced-future>.]

Greetings and welcome to the new RFC Editor Future Development Program.

Last year, the RFC Editor held a number of sessions to discuss how the RFC editor program might evolve. This program was chartered to foster discussion and consensus on possible changes. Such changes could include the role of the RFC editor, the role of others, the structure means by which the RFC editor and those others are overseen, and any necessary accountability mechanisms, just to name a few aspects.  A number of others were discussed last year, and I’m sure those will come up again.

What if anything changes is entirely up to the community, as this is being run under an IAB open program, and it will be IETF community members who put forward both problem statements and proposed solutions.

Your chair has no particular agenda with regard to what the outcome of this work should be.  On the other hand, with people having passionate views on this subject, my only agenda is to try to make the experience positive for everyone.  Please help me in that endeavor, and in doing so we will reach for the broadest consensus.

Regarding working methods, our program charter says that we will operate similar to an IETF working group.  Those procedures are spelled out in RFC 2418 Section 3, and I propose to stay congruent with them so that there are no surprises.  

With this having been said, I propose to proceed as follows:

Open up “the floor” for short problem statements that people think we need to address. We should be clear on what we see as problems and their scope.
See if we can get agreement on those.
Open up “the floor” for proposals on how to solve those problems.
See if we can get agreement on those.
For (1) and (3) we can provide some structure to facilitate comparison and discussion, if that is the wish of the group.  This in itself is a discussion point I invite you to address.

The pace of this work will depend very much on how fast we come to consensus on both the problems and the solutions.  The timing of meetings will be driven by the group.  We can address that in more detail in due course.

Do people find this agreeable?  Otherwise, please feel free to propose alternatives that the group can consider.

Eliot

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest