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

[Eliot Lear <[e-mail]>]

Hi Adrian,

On 23.06.21 11:57, Adrian Farrel wrote:
> Suppose a new stream published something that impeded in some way IETF work? I'm sure it is not our intent to open up a channel for end runs or subversion

Assuming that the stream is exclusively for use for documents that are 
approved via the process we are now defining, then the ultimate step is 
for the RSAB to approve the document.  As part of that process, other 
stream manager representatives get a shot at raising CONCERNs.  In a 
sense, therefore, a check is built in. Indeed the document already says 
the following:

>    Notices will always be sent to the rfc-interest mailing list.  The
>    RSAB and RSWG should also send notices to other communities that may
>    be interested in or impacted by a proposal as they see fit, following
>    policies for those fora as appropriate.

And so this allows each stream to apply whatever conflict resolution 
process they would choose in order to determine whether a CONCERN should 
be raised.

And of course, as you pretty much laid out a cornerstone of continuous 
consultation (that I have put to annoyingly apt alliteration), hopefully 
such concerns can be addressed.   But need we say more?

Eliot