No Subject

I'd say that OMG's RFP process is even more proactive with RFIs-- the
process takes time as a measure of sanity, IMHO ;)

-steve


http://www.ietf.org/tao.html#RFCs_and_I_Ds
http://src.doc.ic.ac.uk/computing/internet/rfc/rfc2026.txt


4.  THE INTERNET STANDARDS TRACK

   Specifications that are intended to become Internet Standards evolve
   through a set of maturity levels known as the "standards track".
   These maturity levels -- "Proposed Standard", "Draft Standard", and
   "Standard" -- are defined and discussed in section 4.1.

6.2  Advancing in the Standards Track

   A specification shall remain at the Proposed Standard level for at
   least six (6) months.

   A specification shall remain at the Draft Standard level for at least
   four (4) months, or until at least one IETF meeting has occurred,
   whichever comes later.

   These minimum periods are intended to ensure adequate opportunity for
   community review without severely impacting timeliness.  These
   intervals shall be measured from the date of publication of the
   corresponding RFC(s), or, if the action does not result in RFC
   publication, the date of the announcement of the IESG approval of the
   action.




-steve


To unsubscribe send a note to majordomo@cs.fiu.edu with the body of the message
being: unsubscribe cadse-orb