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

S Moonesamy <sm+ietf@elandsys.com> Thu, 17 March 2022 22:56 UTC

Return-Path: <sm@elandsys.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 6F4B93A1709 for <rfced-future@ietfa.amsl.com>; Thu, 17 Mar 2022 15:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.707
X-Spam-Level:
X-Spam-Status: No, score=-6.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 v2V2atSfeeIb for <rfced-future@ietfa.amsl.com>; Thu, 17 Mar 2022 15:56:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D2A93A094C for <rfced-future@iab.org>; Thu, 17 Mar 2022 15:56:01 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.51.100]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 22HMtQH2007877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Mar 2022 15:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1647557758; x=1647644158; i=@elandsys.com; bh=XdMlBj+p/uSTxCJ3UEQX1J9QpzsZsAWaOqTF5O6QOHU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gjGSuUhosptUh1chwD/bfALSMoq5yMimDhtFKb/6V/d6aipBphK10vbAhMiQ2GzOV I/M8/e0BhsncDKiLCk/OJr7M+wSyFIhcX1H4L+bX84wXbNr2Cc5WWZELoIfUZYOVBH TV1F3EdO7gxwSewxwbV9IhBDrEIVyY3W1wWR1M8g=
Message-Id: <6.2.5.6.2.20220317011817.07be8d90@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Mar 2022 15:52:32 -0700
To: John C Klensin <john-ietf@jck.com>, rfced-future@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Cc: Peter Saint-Andre <stpeter@stpeter.im>
In-Reply-To: <6BB1E96BFA7AF6DD2A44748B@PSB>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/gj3svtRaQlh6cpvfNlyggDatIPA>
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 22:56:07 -0000

Hi John,

I trimmed the Cc.

At 09:12 AM 14-03-2022, John C Klensin wrote:
>So, now we are creating an RSWG that is sort of like an IETF WG
>except where it isn't and an RSAB that is sort of like -- well,
>I don't know what it is sort of like unless it is IAB-lite.  We
>are eliminating a key (even if sometimes problematic) role and
>oversight authority in the RSE -- a role that was based in
>technical publications knowledge and experience -- replacing
>part of it with committees, the majority of whose participants
>are unlikely to have that knowledge and experience, an advisory
>function whose parameters will have to be sorted out over time,
>and giving vastly more authority to the LLC and its leadership.
>Every one of those changes may be desirable and reflect the need
>to solve real problems but, because of the extent of the changes
>and the degree to which we are going into territory we think we
>understand (but may not), it is an experiment and the other old
>IETF metaphor is a question: "what could possibly go wrong?".

The current (soon to be obsoleted) model was described as "running 
code".  The proposal which came out of this Internet Architecture 
Board program is a mishmash of ideas borrowed from the IETF 
model.  The authority given to the IETF Administration LLC is a side 
effect of a previous decision taken by the IETF.

If the proposal is an experiment, shouldn't it be categorized as 
"experimental" instead of "informational"?

Regards,
S. Moonesamy