An update on next steps on RFC Editor model evolution.
Ted Hardie <iab-chair@iab.org> Wed, 11 December 2019 21:58 UTC
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2860112004C; Wed, 11 Dec 2019 13:58:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 LlTpn1M15vmE; Wed, 11 Dec 2019 13:58:30 -0800 (PST)
Received: from hardie-macbookpro.roam.corp.google.com (unknown [195.245.140.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id D16A9120025; Wed, 11 Dec 2019 13:58:29 -0800 (PST)
To: ietf@ietf.org, iab@iab.org
From: Ted Hardie <iab-chair@iab.org>
Subject: An update on next steps on RFC Editor model evolution.
Message-ID: <85c77bee-78c2-4592-0d5b-1b2fb00c253d@iab.org>
Date: Wed, 11 Dec 2019 21:58:28 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------C3BBEEB1033BF1867B91DC4C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v5NdQe1PlpXuzsw0sUZv9YcOZeo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2019 21:58:32 -0000
Dear Colleagues, In a series of meetings leading up to and at IETF 106, the Internet technical community was asked about the process to use in considering a further evolution of the RFC Editor model. The apparent consensus of those interactions, as judged by the current RFC Series Editor, was that an open IAB program is the most appropriate vehicle available. The outcomes of each of these meetings and the resulting process proposal is summarized in draft-flanagan-rseme, but one key point is: The program should be modeled closely on an IETF working group [BCP25], using a mailing list to validate consensus among the participants, and adhering to the IETF Note Well [BCP78] [BCP79]. Decisions are expected to be made using rough consensus; consensus will be called by the chairs, and any appeals will be handled by the IAB.[RFC7282]. Like an IETF working group, this program will have completely open participation. At its most recent meeting, which was the first after IETF 106, the IAB agreed to develop a program in line with this proposal. Charter text for community review will be circulated to the rfc-interest@rfc-editor.org <mailto:rfc-interest@rfc-editor.org> mailing list within the next few weeks; we encourage you to subscribe to that list if you wish to participate in the charter discussion. We expect the comment period to span the holiday period into the new year. A separate mailing list will be created for the program once the charter has been finalized. Volunteers to serve as chairs will also be solicited after the charter is final. If you have questions on the process going forward, please do not hesitate to send them to iab@iab.org <mailto:iab@iab.org>. best regards, Ted Hardie for the IAB