Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
Adrian Farrel <adrian@olddog.co.uk> Tue, 31 March 2020 21:29 UTC
Return-Path: <adrian@olddog.co.uk>
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 007F73A08F4 for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 14:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[MAY_BE_FORGED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Ru_tUlqk5HY2 for <rfced-future@ietfa.amsl.com>; Tue, 31 Mar 2020 14:29:18 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D5ED3A08F5 for <rfced-future@iab.org>; Tue, 31 Mar 2020 14:29:18 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id 02VLTD3Q029150; Tue, 31 Mar 2020 22:29:13 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id AC4B72203B; Tue, 31 Mar 2020 22:29:13 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 9751F2203A; Tue, 31 Mar 2020 22:29:13 +0100 (BST)
Received: from LAPTOPK7AS653V (81-174-206-152.bbplus.pte-ag2.dyn.plus.net [81.174.206.152] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 02VLTCuB030815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Mar 2020 22:29:12 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, 'Eliot Lear' <lear=40cisco.com@dmarc.ietf.org>, rfced-future@iab.org
References: <97B63B78-0D49-4007-B8A2-101FB7849C0F@cisco.com> <e1876470-c6aa-da6a-5282-5fe2a4d8d893@cs.tcd.ie> <0e4d01d607a1$93d95030$bb8bf090$@olddog.co.uk> <6e64b538-ad4b-5b54-3c1d-acc4b987a19c@cs.tcd.ie>
In-Reply-To: <6e64b538-ad4b-5b54-3c1d-acc4b987a19c@cs.tcd.ie>
Date: Tue, 31 Mar 2020 22:29:12 +0100
Organization: Old Dog Consulting
Message-ID: <0e5801d607a3$6c84bb30$458e3190$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQE1+R8uCRV9Abm7PvYymWtFQE+BqAGI0LbWAd/gHrMCrqEwv6lymTqQ
X-Originating-IP: 81.174.206.152
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-25326.003
X-TM-AS-Result: No--24.871-10.0-31-10
X-imss-scan-details: No--24.871-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25326.003
X-TMASE-Result: 10--24.870900-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbPVY7U3NX8JgpvDLLlsAH/0fDTiy/l/JKV8g kdmvvg/2L/qYgc9m5+P21ZTKBNQQO237z/25P5od9m9PbNihg7AL8TGleseLPH9nRLJB1yYQnyx gj7PVNzoeGZguMEuTyFLyRswcCV1JOQIin5EspQaBVj0DhF8PTgILzOoe9wbaOF0RIPSotdMT5O E0Sj2y4aa+zcSQem1Aa57FGJiDWLxdTHExsvPfnpCYtcHXhxbaf6iC0fNopZkurUcwuzZNE5IH3 UK+7vM/nrvMfSSMM+ojkSBBXO80zzrbb61Qqr4lCLNfGU4dffiCjlNkELBqNLobGHR5ejtrIycc KU/UgpsWsLL/8WJrNTF7BC4yGqFZAxYKB0LOn5q8coKUcaOOvalHaQwZyzDt3oD51KVDoVtlTEa s7VhA3e1CGOxU0BKtSoQVCcsY4Qb6+7mjV+YfuRW/bMMiDpHhVsuPqg+sAtn+9LofIdYpC6zz7j 3QUvuEZEweJO8a2MUnLlOhkhy6Ec7MSRQ9Hxg6nVTWWiNp+v8FcnqPYTPUhxRGQfPV64jhQTf6i dMd+ws6NU1+zwxTwvekW5IOib8wt2Ln7lGU7t3svUCLoWsu670ETfjOvlQDnG0dBE+DEE38716R h+7y7M4mKTc46PEG8p0Rh62NW+e1VfXpZHDU6lBSWz5Zgb/DSHr6Bej+MHJECoESVr1FLoHJBI4 J1p3fB4Co4PVKNKlXvSsCKIWH8UiO8gy3/5KMThh/2J+QysUJ2MLcsMaGgVY9yet6QEd80FZnVE QqwNOLWLLn+hKixttipd417Rgft9RcmRnBKHWeAiCmPx4NwFkMvWAuahr8m5N2YHMD0b8MyrfP9 j+C1d934/rDAK3zUc1+O1X9AzE=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/_K8gefg7pHhDK3woV5NMEhyqrac>
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: Tue, 31 Mar 2020 21:29:20 -0000
OK, thanks. I'll accept "misinterpretation of unfortunate juxtaposition of words" A -----Original Message----- From: Stephen Farrell <stephen.farrell@cs.tcd.ie> Sent: 31 March 2020 22:22 To: adrian@olddog.co.uk; 'Eliot Lear' <lear=40cisco.com@dmarc.ietf.org>; rfced-future@iab.org Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program Hiya, On 31/03/2020 22:15, Adrian Farrel wrote: > Stephen, I see a problem with you "calling consensus" on those > earlier discussions post facto, as it were. Sorry, that wasn't my intent. I had thought it might be a non-controversial part of all this but that just goes to show how little I know;-) > It may be a fine thing to > do to revisit the discussion, but assuming that that decision has > already been made is troublesome. Nothing I said indicated any decision had been made. I guess you're reading too much between the lines maybe? > FWIW, I disagree quite strongly with the idea that someone who has > editorial and production experience should not be involved in the > day-to-day management of the people who are responsible for > substantial work conforming to the leadership that that person gives. I fully agree the RSE needs to be involved. But I think the language in the current RFC makes the RSE accountable for the day-to-day performance of RPC staff. (I'd need to go check.) So I do think that is something to revise and please note that I only said revise, I didn't say how one might revise, and nor did I say how I would want things revised! Cheers, S. > > > Best, Adrian -----Original Message----- From: Rfced-future > <rfced-future-bounces@iab.org> On Behalf Of Stephen Farrell Sent: 31 > March 2020 22:03 To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>; > rfced-future@iab.org Subject: Re: [Rfced-future] Welcome to the RFC > Editor Future Development Program > > > Hi Eliot, > > I'm sure this'll not get forgotten but just to get it on the > table... > > In earlier discussions there seemed to be relatively broad agreement > that the idea that the RSE should be responsible for the day-to-day > performance of the RPC was outdated, esp. now that we have the LLC. > > So I think revising that part of the RSE role description is > something that should be part of this. > > Cheers, S. > > On 30/03/2020 07:51, Eliot Lear wrote: >> [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 >> >> >> >
- [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