Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
John C Klensin <john-ietf@jck.com> Mon, 30 March 2020 16:07 UTC
Return-Path: <john-ietf@jck.com>
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 2859C3A1888 for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 09:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=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 R2Wz2O6Q_yUc for <rfced-future@ietfa.amsl.com>; Mon, 30 Mar 2020 09:07:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E261E3A1871 for <rfced-future@iab.org>; Mon, 30 Mar 2020 09:07:34 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1jIwwl-000KRv-DY; Mon, 30 Mar 2020 12:07:31 -0400
Date: Mon, 30 Mar 2020 12:07:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "Andrew G. Malis" <agmalis@gmail.com>
cc: rfced-future@iab.org
Message-ID: <0E6D83F8D11D8C1B9B7237B7@PSB>
In-Reply-To: <D6A290EE-72E5-46A7-BA25-085CC2AAE35C@cisco.com>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/ZP2IylhmuRkazTPJpwYuV8WD4DM>
Subject: Re: [Rfced-future] 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 16:07:47 -0000
Eliot, Responding to your first note but with your exchange with Andrew very much in mind... --On Monday, March 30, 2020 08:51 +0200 Eliot Lear <lear=40cisco.com@dmarc.ietf.org> wrote: >... > 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. >... My hypothesis is close to Andy's, reinforced by the discussions at IETF 102 and 105 and the reports from the meetings that brought this Program about: Very little is broken and the community (including and in addition to that of active IETF participants) wants a unified RFC Series with an Independent Stream, an RSE who is appropriately qualified from a technical publications management standpoint, and who manages the Series and sets editorial policy independently and from a high professional level, consulting the community as appropriate. If that is the case, then the answer to Andy's question would be that the only thing that has been broken over the last 18 months or so is that the IAB and/or RSOC lost track of the "independent" and "professional" parts and started trying to set policies and manage the series themselves and, as a possible unintended consequence, treating the RSE as contractor who could easily be replaced. On a slightly different topic, the issues associated with the 2020-2021 Nomcom and what, if any, changes are needed to the eligibility requirements for the future are still very active on the IETF and eligibility-discuss lists (in addition to many other issues, of course). For those of us who can only put in a limited number of hours a week on IETF-related work, paying careful attention to both sets of threads might be nearly impossible. Much as I hate to see this process delayed, would it be sensible to postpone active discussions here for a week or two in the hope that the other ones will settle down? best, john
- [Rfced-future] Welcome to the RFC Editor Future D… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Andrew G. Malis
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Eliot Lear
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Lucy Lynch
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Wes Hardaker
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Wes Hardaker
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Eliot Lear
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John C Klensin
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Eliot Lear
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Joel M. Halpern
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Jari Arkko
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Adrian Farrel
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Adrian Farrel
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Brian E Carpenter
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John C Klensin
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Stephen Farrell
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Joel M. Halpern
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Michael StJohns
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… jmh.direct@joelhalpern.com
- [Rfced-future] AUTH48 and editing before approval… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… Carsten Bormann
- Re: [Rfced-future] AUTH48 and editing before appr… Michael StJohns
- Re: [Rfced-future] AUTH48 and editing before appr… Eliot Lear
- Re: [Rfced-future] AUTH48 and editing before appr… Ted Lemon
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Andrew G. Malis
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- [Rfced-future] Up level [Re: AUTH48 and editing b… Brian E Carpenter
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] AUTH48 and editing before appr… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Larry Masinter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Carsten Bormann
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Joel M. Halpern
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Julian Reschke
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… Russ Housley
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Brian E Carpenter
- Re: [Rfced-future] Welcome to the RFC Editor Futu… Carsten Bormann
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John R. Levine
- Re: [Rfced-future] AUTH48 and editing before appr… John C Klensin
- Re: [Rfced-future] AUTH48 and editing before appr… Christian Huitema
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John C Klensin
- Re: [Rfced-future] Welcome to the RFC Editor Futu… John Levine
- Re: [Rfced-future] [IAB] Welcome to the RFC Edito… Mark Nottingham