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

[Mirja Kuehlewind <[e-mail]>]

If we would keep using the IAB stream (and I’m not stating any opinion here; just trying to outline what that could mean process-wise), I think we still need some kind of IAB approval, because I think the IAB wants to retain some control about what happens on their stream. However, I think we could easy define something like the IAB can only not-approve based on formal procedural problems but cannot rejecting based on the content that already has community consensus at that point. Yes, it would be an additional process step but I think we can make that very light-weight. However, these are only my personal initial thoughts and it would probably be good to also check with the rest of the IAB if that is considered an option.

P.S.: The IAB reviews all IAB documents to some extend (workshop report are usually written by IAB members) but during approval of those documents everybody understands that we don’t need to have consensus on the content of the document but are rather approving on the basis that the document is considered appropriate and ready for publication.


> On 25. Jun 2021, at 16:43, Joel M. Halpern <[e-mail]> wrote:
> 
> 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 <[e-mail]> 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 <[e-mail]>
>>> 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
>>> [e-mail]
>>> https://www.iab.org/mailman/listinfo/rfced-future
>