Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model

Eliot Lear <lear@lear.ch> Thu, 10 March 2022 15:49 UTC

Return-Path: <lear@lear.ch>
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 C06AD3A139E; Thu, 10 Mar 2022 07:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level:
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 8khzQoNlT-yQ; Thu, 10 Mar 2022 07:49:28 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 495A03A138E; Thu, 10 Mar 2022 07:49:24 -0800 (PST)
Received: from [IPV6:2001:420:c0c0:1011::9] ([IPv6:2001:420:c0c0:1011:0:0:0:9]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 22AFnLaw688847 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Thu, 10 Mar 2022 16:49:21 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1646927362; bh=+2OTSWD11WUAiQN5+pYni7UtbHrk+IrYsy1B5f3ydhI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=cQinfLFhIUqTCNU4m4DxU90ojuv/qaGsS8HeUHlZdcNbsAtYxrYZXeYu9dcQY4yTc 5LJQo3u5Sb87FIwIOeyvrwsmpQrIuBAZyTGqkgY7m2iPQYp5PaZrKEJpd6iTYhn6fK XhUuXZoOEFnCTkp2QfT4SgWqiFQrj7p8RuLGxQnI=
Message-ID: <c059e4d2-99a1-3148-16d4-c789673575df@lear.ch>
Date: Thu, 10 Mar 2022 16:49:20 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.2
Content-Language: en-US
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: rfced-future@iab.org, IAB IAB <iab@iab.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@stpeter.im>
References: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com> <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch> <CAL0qLwZnaZ2J=7YnOS96h42135w6NrEdn-Obj7QOWwwRxDj1vg@mail.gmail.com>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <CAL0qLwZnaZ2J=7YnOS96h42135w6NrEdn-Obj7QOWwwRxDj1vg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------pit00uR1XCNZOMOAFlTxdjNP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/d8ITW-UvVVvm5lBKv7ltkjXxOqQ>
Subject: Re: [Rfced-future] Comments on draft-iab-rfcefdp-rfced-model
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, 10 Mar 2022 15:49:33 -0000

On 10.03.22 16:37, Murray S. Kucherawy wrote:
> On Wed, Mar 9, 2022 at 11:10 PM Eliot Lear <lear@lear.ch> wrote:
>
>     The philosophy behind CONCERNs is that they should be rare, and
>     that the
>     community really should be taking responsibility for the content of a
>     document.  Thus, unless something truly rises to a threat to a
>     stream or
>     the long term health of the series, the RSAB should stay out of the
>     way.  Those two CONCERN criteria are sufficiently broad to permit
>     members to act if the policy truly looks like it will cause harm
>     in some
>     way.
>
>
> If we are to think of the RSWG as a typical working group (which the 
> document otherwise suggests is how we should think of it), then I 
> can't discount the possibility that something might be handed to the 
> RSAB that is not really ready for consideration, for whatever reason.  
> As I read what you're saying here, this proposal presumes that can't 
> (or won't) happen.

I think the way to look at it is risk-based, and that authority is 
balanced such that the risks of authority abuse by the RSAB are 
prioritized certain classes of errors made by the community.

Eliot


> I'm thinking defensively here; what do we do when it does happen?  It 
> seems to me the RSAB needs a path to deal with such a situation, and 
> they don't with "CONCERN" constrained the way it is here.
>
> -MSK