... rathole.
Last I checked, independent individual submissions were not
part of this discussion.
Leslie.
Brian E Carpenter wrote:
Bert,
Wijnen, Bert (Bert) wrote:
I think we have a Potential requirement that individual submissions
be separate from IETF submitted documents and that those individual
submissions do not belong in the "IETF Technical Publication process"
Or to word it positive:
Potential requirement: Only IETF submitted documents (i.e. through
the IESG, IAB or IRTF) are part of the IETF Publication Process
Personal comments:
Since you raise it, I'd like to take a slightly different cut.
Your statement isn't really a requirement, in fact.
There are good reasons to have a publication process that bypasses
IESG approval - it's one of the checks and balances in our system.
In fact, it has its own built-in check and balance, RFC 3932.
However, as the need for RFC 3932 shows, it's really illusory to
pretend that it's completely separate from the IETF community and
its processes. So I would suggest a new process.
1. There should be a process by which technical specifications that have
not been submitted for approval by the IESG are published.
2. They may not be standards track or BCP.
3. They must be published first as I-Ds.
4. The IETF establishes an independent review board (IRB) for such
documents, whose reviews shall be published.
5. If the IRB wishes to publish a draft, it must submit it to the IESG, not
for approval, but for review according to the criteria in RFC 3932
(non conflict with IETF work).
6. In the event the the IESG recommends against publication and the IRB
decides to publish, a note written by the IESG must be included.
7. After that the draft goes to the technical publisher just like
an IESG-approved draft.
Brian
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
_______________________________________________
Techspec mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/techspec
