[rfc-i] Proposed Program Description for RFC Editor evolution program
Ted Hardie <ted.ietf@gmail.com> Thu, 19 December 2019 17:20 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 228641208CE for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 19 Dec 2019 09:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level:
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.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 UY8rQIMBlDkh for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 19 Dec 2019 09:20:06 -0800 (PST)
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 5A0531207FC for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 19 Dec 2019 09:20:06 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6AF88F40716; Thu, 19 Dec 2019 09:19:46 -0800 (PST)
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 13B5CF40716 for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 09:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0Nv_OHDb5u2U for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 09:19:43 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) by rfc-editor.org (Postfix) with ESMTPS id C30D3F4070F for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 09:19:43 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id z8so6571450ioh.0 for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 09:20:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Iol15cCyNeqSDEK4ia7ND6f6eakpudkGOlKAtpBX8kM=; b=IML4vKA0kZ9HGfmXcOzXDEznQNaEI5IoOIxbsBVhR36mEUOVbc7969LOJbJDjNrnWR DfmiTWSxKCVLPm0A+c54cRuD049wWKYfgtRjJmdHiNxIl2pcw6orTyaOC5xKeUUAHyRk LMvx3MewUnfwbh0mrC9MxflLEj404Yf5Qy64GpV9VQKia2OQhh7loVG02ATAgqHy5eBR kjx0hUmLklWacVUEmkqPzqMaNnFjYMJdsbMQ8tRvi6oRP+7ZS8Xh4PCR1YdGWYF01BHf kMU5OCXTsNhlw2YY2rp1lN0h1gHf9+WfpXfTcUlpEzDnvdMmvbXoFSofzVVMorJapoqx IQMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Iol15cCyNeqSDEK4ia7ND6f6eakpudkGOlKAtpBX8kM=; b=sfxymxaxEJ8F/5YiOHZYDp+VYKtwnKyE+3sBd/hOR+z7Vhiur/fj40+EKs4VNmhCyH 5i2qQ75Csy32nguc6Zd4Wit33MnGibEGdHUkFMNwJbzU8MbbvvaGHxN70qUaAq22OYxR NggqVRAyByEGFzzSqDN0SqQThUjqCEx1H7YKg8tGn4wlBTmD5OapdtDS5B0sJENnv/sI 7RMG5fzGP8gk07CXz/Tu15ZEv6M+ISybhAN6pEEZcZ8OQ60AKp/Kg03zYtlCKR28NTtG 05TPzsB0nM3VW68aRUy9MnYmd0v7ckHXtoUKBW9Q9svtNSa/Dj/6FhVJhSOz+npmrj77 DtyA==
X-Gm-Message-State: APjAAAVDmFU9+Ysy1PbmJny3Fhpm0E+y9M1wN+zgoZ6C/2paBQnH4Z9e lxsW9EliyqD52NapZXwgDNsky5NzHYI3bvpnwEuRPFPM
X-Google-Smtp-Source: APXvYqxSO12WHW8V5ZxUESq/34W/jtccE8jhJT/r842kwqhzpJD5T4RNGuGj0VWpL1VgKVI/ZiZUl1+Yt/is8pODSBY=
X-Received: by 2002:a5d:8854:: with SMTP id t20mr6648909ios.121.1576776001016; Thu, 19 Dec 2019 09:20:01 -0800 (PST)
MIME-Version: 1.0
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 19 Dec 2019 09:19:34 -0800
Message-ID: <CA+9kkMBFgdFdT3CLYWDvK5QN7xQOnMo+SQLG0_yueqhthcd+bg@mail.gmail.com>
To: RFC Interest <rfc-interest@rfc-editor.org>, Internet Architecture Board <iab@iab.org>
Subject: [rfc-i] Proposed Program Description for RFC Editor evolution 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="===============0710311469372977549=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
The IAB is seeking feedback on the proposed program description below. While we would prefer public discussion on this list, comments may also be sent to iab@iab.org. regards, Ted Hardie for the IAB Evolving the RFC Editor Model Purpose This program is intended to foster discussion and consensus on potential changes to the RFC Editor model. Discussion of changes to how the RFC Editor function is managed, staffed, and overseen are all within scope. After the group has come to rough consensus, it will document its output in one or more RFCs. Program Description During the period between IETF 105 and IETF 106, the RFC Series Editor convened a number of meetings to assess how best to conduct a community discussion and consensus process for the evolution of the RFC Editor model. During that process, an IAB program was identified as the most appropriate vehicle for the discussion, provided it allowed for open participation and used a rough consensus model for decision making. The working methods below are intended to capture the output of those meetings. This program has no predetermined constraints on the decisions of the group. Updates to or retention of the oversight model, management, and the roles involved in the RFC Editor function are all within scope. Because the focus of the discussions leading up to the creation of the program were on the RFC Series Editor role, there is a presumption that the group’s discussion will start with that. Working Methods The program is modeled on an IETF working group and uses its mailing list to develop and validate consensus among the participants. Participants must adhere to the IETF participation policies set out in the Note Well [Note Well <https://ietf.org/about/note-well/>]. Decisions are made using rough consensus as determined by the chairs. One or more design teams may be set up during the course of the program, but their output must be considered and validated according to the usual consensus process. Design team output has no special standing. Participants may appeal consensus calls to the IAB[RFC7282]. In addition to chairs, the program will have an IAB program lead. That lead will act as a liaison between the chairs and the IAB for logistical and other formal matters. All members of the IAB, including the liaison, may also participate in the group as ordinary members. Members This program is open to participation by anyone.
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- Re: [rfc-i] Proposed Program Description for RFC … Ted Hardie
- Re: [rfc-i] Proposed Program Description for RFC … Brian E Carpenter
- [rfc-i] Proposed Program Description for RFC Edit… Ted Hardie
- Re: [rfc-i] Proposed Program Description for RFC … Phillip Hallam-Baker
- Re: [rfc-i] Proposed Program Description for RFC … Brian E Carpenter
- Re: [rfc-i] Proposed Program Description for RFC … Robert Sparks
- Re: [rfc-i] Proposed Program Description for RFC … Phillip Hallam-Baker