Actually Joe, the rules clearly allow the case wehre an Independent
Stream I-D disagrees with the IETF rough consensus. Many such have been
published. Some of them were held so that they were not published until
the relevant IETF work was published.
To be explicit, while the IESG can request that the ISE not publish
something, and can provide a note they wish to have included if it is
published, they do not have the power to enforce a do-not-publish if the
ISE disagrees.
And Joe, you have lived aspects of this more closely than I have, so I
am sure you are aware of it.
Yours,
Joel
On 11/4/2019 9:48 PM, Joe Touch wrote:
On Nov 4, 2019, at 6:39 PM, Joel M. Halpern <[email protected]> wrote:
If the authors want to publish it as an RFC so as to comment on other RFCs,
they could approach the Independent Stream Editor. That sort of publication is
one of the explicit purposes of the Independent Stream.
That only happens if the WG and IESG say this is out of scope for the IETF.
I.e., the ISE isn’t an end-run.
IMO, given the fact that this is squarely within TSVWG and there’s no
consensus, the way forward is clear.
Not every ID turns into an RFC, nor should it.
Joe
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
