Re: [Rfced-future] A voice from the rough (was: Re: Program Last Call Results and Next Steps)
Adrian Farrel <adrian@olddog.co.uk> Mon, 31 January 2022 20:23 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 7EA023A1640 for <rfced-future@ietfa.amsl.com>; Mon, 31 Jan 2022 12:23:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 XEW-ded_j2vU for <rfced-future@ietfa.amsl.com>; Mon, 31 Jan 2022 12:23:41 -0800 (PST)
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 8FF083A163B for <rfced-future@iab.org>; Mon, 31 Jan 2022 12:23:41 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 20VKNb8G005942; Mon, 31 Jan 2022 20:23:37 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EFCDF4604B; Mon, 31 Jan 2022 20:23:36 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E384646048; Mon, 31 Jan 2022 20:23:36 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS; Mon, 31 Jan 2022 20:23:36 +0000 (GMT)
Received: from LAPTOPK7AS653V ([148.252.133.21]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 20VKNZRv011545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 31 Jan 2022 20:23:36 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'John C Klensin' <john-ietf@jck.com>, 'Eliot Lear' <lear@lear.ch>, rfced-future@iab.org
Cc: 'Peter Saint-Andre' <stpeter@stpeter.im>, 'Brian Rosen' <br@brianrosen.net>
References: <A3E21347D5F71C11A30F5C13@PSB>
In-Reply-To: <A3E21347D5F71C11A30F5C13@PSB>
Date: Mon, 31 Jan 2022 20:23:35 -0000
Organization: Old Dog Consulting
Message-ID: <076c01d816e0$6d4d0880$47e71980$@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
Thread-Index: AQGyJFhSbyBatHld1atvW/Vl0ihjB6zJdRFA
Content-Language: en-gb
X-Originating-IP: 148.252.133.21
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-8.6.0.1018-26688.002
X-TM-AS-Result: No--3.608-10.0-31-10
X-imss-scan-details: No--3.608-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-8.6.1018-26688.002
X-TMASE-Result: 10--3.608200-10.000000
X-TMASE-MatchedRID: IeZYkn8zfFrxIbpQ8BhdbHhfkWVrzox1sRSZLc6Y9S6Sa52iu6/jhmUo D5JLGXzAmxUTlTE0MMHugYf75qB+Mj4bsFilIG5UyKTEsCRIdyW0P8vH4t+8S4PLx3vY4vNiB+E vqmMuRzkJAtqLc92TgJe7bp8XEFlcT5MjSVfsjnhHcnWSrPRrNZYaT3cL9WdKbaZMa0fgRtbjLK PupB6SIyuplNNVYofYiZFyvDXEDNjGC5rzrXtPJQvBTB90+he+KZoK1F/O1EnXjO/sp3prhkZUq iaZ+o8n59roDgpclG1j//xD3qmtG3C9PQeexWpx6KjHv0nYqBAx8U5ikIj+4hnXPhnXzURh+m2Y wXqdQTEVGXGIXV4Um2wqxuUUZRhGJGRycaTaKeW253GzzSji4g5QbtEckQMlzvlYLK4togHxdW6 rT4kFIvyWos330qceI5X0xCVZsAg+D3J+ThgLRpKLzY5ZrthjoIcZ8kDSGx3kIvlD0oBsliLywW Z/CAIYyY2rJHIoKXYPYskfob7lO2MFwILfD7YgvmT2VURehloRVuFekDGWud9RlPzeVuQQSiDeF P1/+gLvt3nUS5MECSFDrWxflyZ5vkk7gmoOajYZSUX8zcPGn7zETYfYS4xZAFUQhPJ3sQ7h06w0 q6p9rMGBhC18bzlkj3vTWuLvwC5fXJAkAdwlnJzEQqkMw+XnfK4IN302ya/UiIlnxoPdGMQ5vcy Cjz1IWqMMIIXpy0kUgcBipBCF5xJdrRm5MVelikdH3EQaETXjZOj64c0Q9naMN1ilusKZLdeibs 83IX2P9mAVU4w0EGowq23ynEFc+uP+8o5xUfOeAiCmPx4NwFkMvWAuahr8i2QFaYS1v20qtq5d3 cxkNfAxRSAc0OENVVWK1k62DHIeaMStJtcelbBWPRst3E23QT3FZlEuNCNr+0tolg6JLNu6S4xW kTellExlQIQeRG0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/pPTCFiM_3gX0gLxPDasPOVl9gws>
Subject: Re: [Rfced-future] A voice from the rough (was: Re: Program Last Call Results and Next Steps)
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, 31 Jan 2022 20:23:47 -0000
Hi John, I don’t know how rough rough has to be to be really rough, but I find myself somewhere in the long grass, if not with you, then close enough to be considered not on the fairway. (And I wish we would stop using sporting metaphors that have no meaning to people who don't share our cultural heritage!) Like you, John, I feel I have had my say earlier in the process and that to bring the issues up again would be to relitigate discussions. In any case, I lack the energy to repeat myself to an unwilling audience. Thus, I kept quiet during this last call. I continue to regret the view of clever people who are experts in their field that other fields about which they know little can be solved by a committee of like-minded individuals rather than delegation to an established expert with whom they disagree. I have seen this mode operate to failure in other environments, and no doubt comparisons with the Committee of Public Safety are extreme, but I continue to worry about where this is all going. I do hope this turns out for the best, and I do admire the effort and strength demonstrated by key participants. Adrian -----Original Message----- From: Rfced-future <rfced-future-bounces@iab.org> On Behalf Of John C Klensin Sent: 31 January 2022 19:56 To: Eliot Lear <lear@lear.ch>; rfced-future@iab.org Cc: Peter Saint-Andre <stpeter@stpeter.im>; Brian Rosen <br@brianrosen.net> Subject: [Rfced-future] A voice from the rough (was: Re: Program Last Call Results and Next Steps) --On Monday, January 31, 2022 12:22 +0100 Eliot Lear <lear@lear.ch> wrote: > Dear all, > > Program last call has now closed. > > We received one set of editorial comments from Brian > Carpenter. I want to detail the proposed changes here, and > their disposition for the next draft, which we are asking > Peter to post now. Once posted, we will forward that draft > to the IAB for further processing. >... Eliot, I deliberately deferred sending this note until after the Last Call closed and you wrote your note. It is clear to me that I am in the rough on several issues and will likely be even after the next stages of the process are complete and I do not have any desire to, to use your term, relitigate long-settled issues or otherwise restart the conversation. However, I think it is important to get this view on the record at this point. >From this minority point of view, I believe there are two key points from which we have walked away (or compromised our way away from)... (1) The RFC Series survived and served the community well for nearly a half-century because of some fundamental commonalities (or, if you will, "principles") that provided functional and coherent leadership and operation over those years even as things evolved. One was consistent and clear leadership and, to a significant extent, authority and accountability in the hands of a single individual at a time. Over that period, the individuals who held that role (at least on other than a temporary/interim basis) were either technical publications experts or someone who understood the limitations of his knowledge and was willing and able to reach out to such experts when needed and pay attention to that advice. While there were clearly disadvantages to that approach, it did work and one of the reasons for it is, fwiw, consistent with why the LLC has a single Executive Director with considerable authority rather than being run by a committee or multiple committees with no one person having significant authority or accountability. (2) The IETF's way of doing things, including its working groups, leadership, and management structure, works well because the vast majority of participants are experts in the subject matter to which they try to contribute. People with opinions but no clue are typically swiftly weeded out or simply ignored. However, we tend to assume that, because those mechanisms work well for Internet engineering issues, they will work at least equally well (with the same participants) for entirely unrelated topics. In the particular case of a model built around an RSWG whose participants are IETF participants with the expertise profile of IETF technical participants, I am confident that the RFC Series will evolve in the direction that the consensus of those participants determines... but, because of those expertise and perspective issues, not necessarily in directions that are best for the Internet and its users. As I said, I know I'm in the rough and I hope I'm wrong about where this may lead. But, in case things do not work as well and smoothly as the Program seems to expect, perhaps the above will be useful as both a cautionary note and part of a starting point for whatever might come next. best regards, john -- Rfced-future mailing list Rfced-future@iab.org https://www.iab.org/mailman/listinfo/rfced-future
- [Rfced-future] A voice from the rough (was: Re: P… John C Klensin
- Re: [Rfced-future] A voice from the rough (was: R… Adrian Farrel