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

Michael StJohns <msj@nthpermutation.com> Fri, 11 March 2022 19:11 UTC

Return-Path: <msj@nthpermutation.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 D5FE23A10EC for <rfced-future@ietfa.amsl.com>; Fri, 11 Mar 2022 11:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20210112.gappssmtp.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 v56j1apFTPbA for <rfced-future@ietfa.amsl.com>; Fri, 11 Mar 2022 11:11:40 -0800 (PST)
Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE95D3A10E6 for <rfced-future@iab.org>; Fri, 11 Mar 2022 11:11:39 -0800 (PST)
Received: by mail-qk1-x72d.google.com with SMTP id q4so7741132qki.11 for <rfced-future@iab.org>; Fri, 11 Mar 2022 11:11:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=KxOAyZZAUItpW9fWiiTcaNxCBO6zhOsk01mSZb9ldPA=; b=YZB0S+3LrbP7y2wWaMsil9R8m3I3BPCDfFqGVdIVzOS41nrsUQzh+3LxlL/XJOgI2T 1kv/bB5xJZPELikvk2b9DbkJk5f3mrN+uLO/gKv/qfQLXbhwA9HZ3o8M+ISBpvH7byi/ 3U05VZ2/aotVYavAdDRAzqdZn8zOTSxhCey4FAv7dIJtytL3/FtgWV4a8aFOdu+n4bQy GQgOLw/jFMoPVzMAGhNtIhbNgZYssn08xSA6VfhgI/w+szPZKG5BwTIU9zFlUYosg4kJ 6Hj2lMIxwJAzOpYixkCC/5f7cbSwxH3qpn7ln+qQ56Zu0toa6+fy6fZ2MocMmxStzHT6 cHHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=KxOAyZZAUItpW9fWiiTcaNxCBO6zhOsk01mSZb9ldPA=; b=RhOu4b09HJUo10f3YBvVtKzkJyjWtc3X7f/xqzqcH5uuZl+sMw8OSekJe8W1K8ExrH XvAoBeKdoBJWSX/SUI9wJN3oajzVJQkjd8hSiQW0TRRYu6oof9xRhcSBWMSzh6srGF3e BMs+kFtBPhfcqhtMipNzy4BbWL+yk7p3lDeVMObHlFvEJTYnmINk5l5I8a+VcbJSFC3n rTD6nVAssZzmpSjV6vEJEuQfZB6idfQwVyYVjmNM3AbOoeuE5Y4nyRwOK+aca1rgfK5o dDsKbAVmMHBG8FVpvpdhxWiEVLepwYXmkqgsXiQ8+Nm3n7CbVwHk5xSptcgVGKTf5tDr IHZA==
X-Gm-Message-State: AOAM532j+ewEUcRJCL0hBUw5rEooZ/tvtCwkiRkia/gnhhLmipiaGvu4 K8ch9Qamu5PJqDRCgnSDP+45KbMfW1DNSUWp
X-Google-Smtp-Source: ABdhPJwzbQKJCEKr7cpwuiVdajPzyruRCQXY2f9kf/RBsxjgWdIvA8oSqrWHQc2YFeRFZkd+6K9CRA==
X-Received: by 2002:a37:a54b:0:b0:67b:309c:e9e1 with SMTP id o72-20020a37a54b000000b0067b309ce9e1mr7643741qke.178.1647025897376; Fri, 11 Mar 2022 11:11:37 -0800 (PST)
Received: from [192.168.1.23] (pool-108-51-200-187.washdc.fios.verizon.net. [108.51.200.187]) by smtp.gmail.com with ESMTPSA id r12-20020a05620a03cc00b0067d370e414esm4029387qkm.15.2022.03.11.11.11.36 for <rfced-future@iab.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Mar 2022 11:11:36 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------1e1coWjQBaRRaZCFLjeGBbRj"
Message-ID: <50286473-556a-f469-4447-130e2e9807b3@nthpermutation.com>
Date: Fri, 11 Mar 2022 14:11:35 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-US
To: rfced-future@iab.org
References: <CAL0qLwbHobErxtCxiMCtYtqByJJhWF79XAwtw2jV9DNte1OuUQ@mail.gmail.com> <e3e01de3-8b69-852a-7dca-cb0e9735ce4a@lear.ch> <CAL0qLwZnaZ2J=7YnOS96h42135w6NrEdn-Obj7QOWwwRxDj1vg@mail.gmail.com> <c059e4d2-99a1-3148-16d4-c789673575df@lear.ch> <CAL0qLwZkaebQmmQdfKsW7oCd58X5DRWY6_QpUaVUueZAyGVA6g@mail.gmail.com> <797efdc3-e674-504e-80e0-fa2b48923bb1@stpeter.im> <CAL0qLwauRS-G+_OcKPx-bRB0EpDKyib+XysWLTBRBka1CqQkmg@mail.gmail.com> <caaea09f-92cc-beae-2a4f-5df4cbf6ad7f@stpeter.im>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <caaea09f-92cc-beae-2a4f-5df4cbf6ad7f@stpeter.im>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/sDJ-67Tpn82IQYaaEHqNsSnPEuQ>
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: Fri, 11 Mar 2022 19:11:44 -0000

On 3/10/2022 8:35 PM, Peter Saint-Andre wrote:
>> OK.  I didn't read (a) and (b) as being covered by the current 
>> proposal as presented, but thanks for clarifying.
>>
>> If possible, I'd suggest this be made more explicit; a later 
>> iteration of the IAB, RSAB, RSWG, etc., might not automatically 
>> inherit that context.
>
> We did go back and forth on many aspects of this document, trying to 
> strike the right balance between helpful direction and too much 
> detail. This seems like another spot where that balance might be 
> important. If we mention now that Factors A and B are good reasons for 
> an RSAB member to raise a CONCERN, but we don't mention Factors C and 
> D, how should a future RSAB member proceed? Could someone file an 
> appeal if an RSAB member invokes Factor D?
>
> As I see it, the RSAB member would need to make a case that a proposal 
> would cause serious harm to a stream or the Series; as long as they 
> can make a plausible or reasonable argument for that, I don't see why 
> we need to tie their hands now.


"An RSAB member voted CONCERN (or not YES)"  can be evaluated on an 
objective basis - they did or they didn't.

"An RSAB member voted CONCERN for a good reason" can only be evaluated 
on a subjective basis and each individual hearing the reason may have a 
different idea of what's reasonable.  In the end *someone* has to decide 
what reasonable is, and AFAICT with the model, that's through the 
appeals process - the RSWG participants* may comment on what they 
believe to be reasonable, but that set of comments is not controlling on 
the appeals process.

Put another way, we can write down any (many?) constraints we want on 
the RSAB voting process, but unless the criteria for the constraint is 
objective and can be evaluated by each participant in the exact same 
way, all the constraint really does is push the objective evaluation 
problem to the appeals process.

In any event, if I were an RSAB member I would vote CONCERN if I had an 
issue, even if the issue was brought up and ignored in the RSWG because 
the RSAB has a different job from the RSWG and different 
responsibilities.  Right now, the RSWG has to convince 3 RSAB members to 
vote YES to progress the document, CONCERNS are not blocking except as 
they are not YES votes.  If there are 3 RSAB members with CONCERNs (e.g. 
only two YES votes out of 5), I would find it hard to believe that the 
appeals process would not take notice of this and fail to override what 
are essentially NO votes.


*The RSWG will be a group consisting of a varying number of participants 
with varying interests.  They will have a mechanism for establishing 
consensus within that group to advance a document, and - I would expect 
- any pushback on publishing a consensus document would get from them a 
general sense of unreasonableness related to that consensus.  Note that 
these both the request to publish and the pushback on a CONCERN will 
derive from the exact same process and shouldn't be given double 
consideration in the appeals process.

Sorry - all of this is a long way of saying that the vote "CONCERN" is 
the important part and the member can cast that for whatever reason THEY 
think is plausible and reasonable regardless of any external opinion.  
Whatever the RSAB member says next ends up needing to be evaluated in 
the appeals process - "plausible" and "reasonable" are subjective issues 
that can't be resolved mechanically.   In any event, if there are three 
YES votes for a document the appeals process will never be invoked - at 
least by the RSWG.

Later, Mike

ps - thought questions:  Has the IAB ever resolved an appeal in a manner 
that directed the IESG to approve the publication of a document?   Or 
for that matter ISOC directing the IAB?