At 12:45 PM 5/10/2005 -0400, Thomas Narten wrote:
Total time between IESG approval and publication, 5 1/2 months.
And to get to Margaret's other points, I agree that these delays damage the IETF. It contributes to the perception that we are too slow, causes additional confusion about a document's true status, etc.
Implementors and other SDOs need access to the final RFCs in a timely fashion.
so do customers who feel an ID isn't sufficiently stable to specify as a customer requirement (for an RFP, for example)
I have already had a customer get so frustrated with the IETF process they wrote an extension themselves into H.323 and got it ratified in 9 months (H.460.14) and our effort (that was first presented at the Adelaide meeting) just went to the IESG for review 5 years and 2 months later.
Thomas
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf
cheers, James
*******************
Truth is not to be argued... it is to be presented.Alas, few *truths* exist without the math.
...all else is a matter of perspective
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf