I agree that the principle of avoiding interference is
a general one that could be captured in this document.
And I think this document had better be consistent in
its application of principles.
I will observe that as the documents are currently
structured, the definitions of the individual streams discuss
the details of handling those (inter)dependencies. Therefore,
I believe your last sentence belongs as a comment on
independent@xxxxxxxx and specifically on the document
draft-klensin-rfc-independent .
If this document is to capture *all* the "specifically"s
of document stream interdependence, we will also have to
capture the expectation that the IETF stream will not interfere
with the IAB stream, and so on. I don't think that's
effectively achievable or even maintainable in this document.
Leslie.
Brian E Carpenter wrote:
Although I'm an IAB member, I'd rather make my one comment
on this draft in public.
I think it misses one point that should be mentioned. The
easiest way to explain it is to suggest new text:
4.4. Avoiding interference between publication streams
Although diversity of views and alternative solutions are
common and will commonly be published, it would be highly
undesirable for documents published in the different streams
to interfere actively with each other, for example
by specifying incompatible extensions to the same protocol
or alternative uses for the same parameter value.
For this reason, the procedures adopted for the four streams
will include appropriate checks and balances to avoid such
interference. Specifically, this will include a procedure
(currently documented in [RFC3932]) to avoid Independent
Submissions actively interfering with IETF Documents.
Brian
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf