Keith: The current IETF Standards Process has become essentially a one-step process. The goal, as I believe is stated in the document, is gather some benefit from implementation and deployment experience. We are not getting that today. When we do get it, the document recycles at the same maturity level due to problems that are not addressed in this proposal, must commonly dependencies on documents that are not ready to advance. So, the reader cannot tell when a document has the benefit of implementation and deployment experience. My reading of the comments on earlier proposals was to focus on one problem in the document, so the handling of the dependency problem and others was removed. I'm pleased to work on them in the future if this document gains rough consensus. Russ On Sep 2, 2011, at 4:37 PM, Keith Moore wrote: > Honestly, the thing that is the most broken about this draft is the idea that there's something wrong with our process because few drafts make it to full standard, so the solution is to short-circuit the process. The transition from Draft to Full Standard is the least of the problems with our process. And the sooner we stop trying to fix irrelevancies, the better. > > Keith
<<attachment: smime.p7s>>
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf