> The time to move from approved > > I-D to RFC is often a significant percentage (perhaps averaging 20% > of more?) of the time required to develop and publish a specification. Let's say that it averages 4 months to go from IESG approval to RFC publication. (I'm choosing that number because it is big enough to indicate a problem, but small enough not to insult the RFC Editor.) Using your estimate of 20% for this step, that means that working groups average 16 months to do their part of the work, from start to finish. However that does not match either general impression or that statistics that were produced awhile back. If we averaged 16 months for working groups to go from start to finish, we would not have serious and consistent complaints that the IETF is too slow. So the actual, incremental delay for the RFC publication process is probably no worse than 10% and I wouldn't be surprised if the real statistic were more like 5%. As much as it is worth trying to make everything better, it is difficult to see a 5 or 10% overhead to the process as being one of our strategic problems. d/ --- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf