Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 25 June 2021 14:43 UTC

Return-Path: <jmh@joelhalpern.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 E1E233A1ABF for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 07:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level:
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.338, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 Wvp2vN0NQZrp for <rfced-future@ietfa.amsl.com>; Fri, 25 Jun 2021 07:43:51 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 655F63A1ABD for <rfced-future@iab.org>; Fri, 25 Jun 2021 07:43:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4GBKWW16GSz6GDyJ; Fri, 25 Jun 2021 07:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1624632231; bh=36RcHbZFfJlLOzT7svlqF00GLy+FwoRrtrXvWCKVAiM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Bfu4kdZuMeK37ZGg0xXeX0+MCOpgRMm8SbdMvfhgP7p+4Jmaa9uaT0tcc0GhfoYm5 QLN1oCw4QmupnokcI9n0aH7muTiU2hxfJj1Wwqd9PBd82sg7HUqZvzD3J+odJ2p2Gs xnDiW6Pm8C/atvqh4KOv4CKAGijUfrg7kUhTkO1Q=
X-Quarantine-ID: <Bmaa4V_pAsqh>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4GBKWV4CTFz6G9t2; Fri, 25 Jun 2021 07:43:50 -0700 (PDT)
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: rfced-future@iab.org
References: <3f4c264e-4639-4d6b-cf22-0a2be503decc@joelhalpern.com> <3D3EC062-7B1A-43C4-99D5-A204A4565ECE@ietf.org> <cf2921d8-fd1f-d9c9-da72-ff760eda347c@lear.ch> <3b4b6d91-64e3-d0d7-bcbc-284f29a46fb7@joelhalpern.com> <9fdeb823-9470-00a8-b1b1-91630b996c8c@gmail.com> <351774DB-C6DC-439F-9B5C-FB427EC9F6FE@ietf.org> <ac1aea74-da8e-405d-2a73-fbc6fc97ce24@gmail.com> <D1D7247E-6F03-475A-88F4-50E45A8B6F0E@eggert.org> <0a778f3b-c32e-abba-6e7f-305387adf3ad@it.aoyama.ac.jp> <0d91a5c0-8dd5-cbe8-2ff9-c5b3fed3cbb2@gmail.com> <CDE14B2F-558D-4864-A9E4-66EEEA07B504@kuehlewind.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <c9111b13-e93d-c2f0-9339-517ab728252f@joelhalpern.com>
Date: Fri, 25 Jun 2021 10:43:49 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <CDE14B2F-558D-4864-A9E4-66EEEA07B504@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/lQBsbTFv3Nabkr2YeNc6PDdRvgc>
Subject: Re: [Rfced-future] Consensus check: Issue 22 – new stream for RFC Editor
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, 25 Jun 2021 14:43:56 -0000

There are a lot of nuances that matter here.

I could probably live with declaring thatt RSWG / RSAB documents are on 
the IAB stream if the RFC that said that also said that the IAB could 
not make any substantive changes to the document and did not have the 
right to refuse to progress the document.

All the other cases you cite are ones where the IAB chooses to not 
review.  This is somewhat different.

Yours,
Joel

On 6/25/2021 4:59 AM, Mirja Kuehlewind wrote:
> The IAB doesn’t necessarily need to label all IAB documents as IAB “opinions” but all IAB documents need IAB approval. However, such things as workshop reports or also documents published by the RSE are usually not seen as an outcome of the IAB and we often even add a clause to the abstract that explicitly says that the document does not reflect IAB opinions. For things that do reflect an IAB opinion when usually even add the list of names of IAB members at the time of approval, to make clear whose opinions are reflected given the IAB also changes all the time (any thereby potentially also its opinions).
> 
> Mirja
> 
> P.S.: As a small side note an a statement that Jay made. The stream mangers do discuss procedures with the RPC but usually the managers would go back to their stream approval body and double-check, e.g. that’s what is currently happening for the terminology guidance. So for me, the stream manager is really just the dedicated contact person here, while the stream “owner” is the approval body.
> 
> 
> 
> 
>> On 24. Jun 2021, at 22:35, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> On 24-Jun-21 20:57, Martin J. Dürst wrote:
>>> Hello Lars, others,
>>>
>>> On 2021-06-24 17:46, Lars Eggert wrote:
>>>> Hi,
>>>>
>>>> On 2021-6-24, at 7:57, Brian E Carpenter <brian.e.carpenter@gmail.com>
>> wrote:
>>>>> As somebody else said, this stream by its very nature is going to be special and even self-referential. The notion we have of a stream being a
>> client of the RFC Series just doesn't apply, so the normal notion of a stream manager doesn't apply**. But surely we need someone to act as progress chaser and nit resolver when a document has left the RSAB and is inside the RPC? And who will that be if it's not the RSEA?
>>>>
>>>> I still remain unconvinced that we even need a new stream. I may be in
>> the rough, but I would be OK with using the IAB stream and leaving the IAB a role here.
>>>
>>> What would that role be exactly? Giving the label "IAB stream" to these
>>
>>> documents without actually being able to approve or decline any of them?
>>
>> I think that's exactly the problem. The IAB stream labels documents as
>> representing the IAB's opinion, and would imply that the IAB is
>> approving the RSAB's opinion, which is not the new model at all.
>>
>>    Brian
>>
>> -- 
>> Rfced-future mailing list
>> Rfced-future@iab.org
>> https://www.iab.org/mailman/listinfo/rfced-future
>