Re: [Rfced-future] A broader look (was: Re: RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12])

Carsten Bormann <cabo@tzi.org> Thu, 17 March 2022 06:53 UTC

Return-Path: <cabo@tzi.org>
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 5808C3A0BB9; Wed, 16 Mar 2022 23:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 8J8tnqLKe96m; Wed, 16 Mar 2022 23:53:27 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7283D3A0BBA; Wed, 16 Mar 2022 23:53:24 -0700 (PDT)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KJyXK43q1zDCfc; Thu, 17 Mar 2022 07:53:21 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6BB1E96BFA7AF6DD2A44748B@PSB>
Date: Thu, 17 Mar 2022 07:53:21 +0100
Cc: "Salz, Rich" <rsalz@akamai.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, rfced-future@iab.org, Internet Architecture Board <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
Content-Transfer-Encoding: quoted-printable
Message-Id: <54BD3D47-D6B6-42FA-BE87-3E9B771337F7@tzi.org>
References: <BY5PR11MB41963ABAE51BC46E205087BDB50B9@BY5PR11MB4196.namprd11.prod.outlook.com> <134294e0-5bd5-9b22-2d95-f6032e67f516@stpeter.im> <7D016D6C-ACCE-4431-BC83-905ECB885B5F@kuehlewind.net> <bf702de8-a876-3d9f-23d8-4ba49f86bd05@gmail.com> <E8C97678-AD00-402B-9646-DEFF6E76263D@ietf.org> <d4ac965c-65b1-e909-864c-cb14e27a3b0f@stpeter.im> <040d9aac-04be-2bef-fad4-b41f2af271e9@gmail.com> <B87EBCF2-16FB-4A22-86FF-20603200E749@ietf.org> <e012452a-61d1-f499-f19e-6d3ff9863901@gmail.com> <4AD933FC-4032-4A10-92DD-A34ADEDD557F@eggert.org> <CANMZLAZmrdxQuGT=W36gUf3gEd3d1C_0c-hfdO2-gpFUOQf7sg@mail.gmail.com> <AB5E3E46-D450-4E21-B67B-D639F67734AE@eggert.org> <e4b25205-af63-aff5-dbcc-9a16aa86b07d@lear.ch> <C2E0E777CD125A1439F4AACD@PSB> <3dabfc01-dfb6-0398-a9a1-5e9ee7e98dc8@gmail.com> <1C58527559239E9A8A6B4E05@PSB> <ECFE6F9B-C659-43B7-8FBF-62E29D4EE476@akamai.com> <6BB1E96BFA7AF6DD2A44748B@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/poX4Ytf7jggTN6mhO_x_ktXUYrM>
Subject: Re: [Rfced-future] A broader look (was: Re: RFC Editor liaison to the IAB? [was: Re: Comment on draft-iab-rfcefdp-rfced-model-12])
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: Thu, 17 Mar 2022 06:53:32 -0000

On 14. Mar 2022, at 17:12, John C Klensin <john-ietf@jck.com> wrote:
> 
> Several recent discussions have left me concerned that we have
> not had a sufficient appreciation of the degree to which the new
> Model is an experiment without much precedent. 

And it is all waterfall design.

With a lot of wishful thinking (process confabulation, i.e., based on what some people think they and other people *should* be doing as opposed to what they are or will be actually doing).

Software projects that are set up this way usually fail spectacularly.
Fortunately, the new process will be run by humans, so we still have a chance that we will iterate out of the tarpits (and/or that people simply will ignore pieces of process to instead do the right thing).

This is all water under the bridge.
But we really have to be careful that we don’t ossify in a failed designed-in-a-vacuum state without a chance to get back to a process of continuous improvement.
The fact that the AUTH48 tweak (as just one placeholder for recent attempts to continue doing continuous improvement) was all but shouted down when subjected to unstructured discussion does not make me very hopeful, though.

Grüße, Carsten