Doug Royer wrote:
Dave Crocker wrote:
...
To elaborate:
Is is ever valid for a working group to want to post a new draft late
in the
game, very near -- or even during -- and IETF meeting? The answer is
clearly yes, which is why working groups route around the IETF's
arbitrary
deadline in the manner that Ned cites.
So the early deadline rule does not even fix the problem it supposedly
attacks.
Yes.
Often people do not read the drafts until right before an IETF
meeting. Most issues are raised right before an IETF meeting. I think it
would be great to be able to submit fixes that will make the meeting
more productive. It does no good to discuss text that almost everyone
already knows has problems.
As Eliot pointed out, discussing text that has changed since half the
people in the room read it doesn't work either. I really don't believe
that the submission deadline was created in order to prevent abuse
of process - it was created to ensure that everyone in the room is
actually discussing the same thing. Our meetings (unlike those of some
standards groups) aren't drafting sessions - the idea is to clarify
substantive issues, but wordsmithing and actual consensus happens on
the list in our process.
A good time to discuss this issue will be when we have an automatic
I-D submission tool according to draft-ietf-tools-draft-submission.
Until then, we need the deadline in any case, to release staff resources
to prepare for the meeting.
Brian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf