The cut-off period before IETF meetings has (IMHO) some value to help people read an digest stable documents that will be discussed face-to-face.
I'm afraid this is another case where we're trying to use processes to control the uncontrollable. A document is either stable or it isn't. If it isn't stable and is being actively revised those changes are going to happen irrespective of whether or not they get posted to some archive. All this rule does is insure that everyone sees stale data in the archive in such cases. And even if you think having groups consider stale data is a good thing, it doesnt' even accomplish that. Over the years I've gotten many notices to the effect of "revision didn't make the cutoff, please go do this other place for the latest revision". Alternately, there's the slide listing the revisions that have already been made. In my experience the only useful thing the cutoff has done is to provide a neat example Sieve script for RFC 5260.
However, some I-Ds are beyond WG last call and are going through other review cycles. Why should updates to these be barred?
And for that matter why have a cutoff for new drafts? If there's was ever a problem with people creating new documents and bringing them to the attention of the group during the meeting I sure wasn't aware of it. And since we now reopon the gates during the week, the only meeting that's actually protected by this is monday morning slot.
For example, I have an I-D that has just completed IESG review. The updates are relatively simple and I would like to submit them and get the IESG to clear their Discusses. Apparently I cannot do this until July 27th. can anyone see a reason why this should be the case?
Almost certainly because enforcing the restriction on documents under consideration by the group would require that the posting facility be aware of document statuses at the group level. AFAIK that's not information that's centrally tracked at this time. IMO the draft cutoff does a lot more harm than good and should be absolished. And if groups need to have rules about late changes or new documents why not leave that to the groups themselves? Ned _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf