[Rfced-future] RSWG & AUTH48 (was Re: [admin-discuss] [rfc-i] Public archival of AUTH48 communications)

[Lars Eggert <[e-mail]>]

Hi,

(changing the subject and adjusting the CC a bit.)

On 2022-2-26, at 18:50, John C Klensin <[e-mail]> wrote:
> Or maybe we postpone spending energy on new lists and tooling --
> both of which tend to create inertia for keeping "experiments"
> -- until the RSAB/RSWG are in place and, since AUTH48 is really
> part of the RFC Production process, allow them to define and
> oversee the experiment along with the IESG.

I thought about this a bit, and it's not immediately obvious to me that procedures for AUTH48 handling are under the purview of the RSWG. I could see an argument being made that they are under the purview of the individual streams. There are already minor differences between the streams, for example, the IRSG is in the loop for AUTH48 exchanges or the IRTF stream, but the IESG is not for the IETF stream.

It's true that so far, all streams have used - more or less, see above - the same process for handling AUTH48 processing. If that is intended to be one of the invariants of the RFC series, I agree that any changes would be under the purview of the RSWG, and any changes would then also apply to all streams.

But I could also see a future where one stream would want to revise how AUTH48 should be handled for their documents. If this is something we would like to allow - and personally (with no hats) I think that could be attractive - then I don't see how this could be under the purview of the RSWG, given that they are setting policies for the series (but not the individual streams).

Thanks,
Lars