[Prev][Next][Index][Thread]

document progression description

-----BEGIN PGP SIGNED MESSAGE-----

There was some confusion recently at the TLS Working Group meeting about
the progression a document
takes through the IETF standards process.  I just read the current
reference, RFC 1602, and here is an explanation as I understand it.  This
is my understanding of what we need to do now the TLS document.

1. the final version of the document (in this case the merger of
draft-ietf-tls-ssl-3-00.txt and draft-ietf-tls-ssl-mods-00.txt) is
presented to the working group for a "working group last call".  The
document is made available by placing it in the internet-drafts directory
at the usual sites.

2. After a WG-defined last call period, the document is presented by the
WG Chair to the responsible
Area Director for considertation as a "Proposed Standard".

3. The IESG will issue a Last Call using the IETF mailing list for this
document.

4. After the IESG Last Call time, the document is, if approved by the
IESG, changed into an RFC, with a number.

[I encourage anyone with corrections to this description to offer them. 
There were 200 people in that meeting, many of whom have more experience
than I with this process.]

-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
Comment: PGP by ViaCrypt

iQCVAgUBMq18m8KmlvJNktGxAQGhIAQAtse/tIsSs0lkS7KL3NDihe2I2vbzbkny
RQ1Hg4AXptEWuGqrASvnUy9TpKlvY3WuZdAgnG33eJvX5lWdKPJqhlLfcg3zlXEi
JlHFocC385eh3V0Q8rw92VHsMVpsC6BqWwqMvtMc2djABppu/k/8JgrkFTl/PEVa
9rPt0/uF55k=
=Qc8D
-----END PGP SIGNATURE-----


               Rodney Thayer <rodney@sabletech.com>       +1 617 332 7292
               Sable Technology Corp, 246 Walnut St., Newton MA 02160 USA
               Fax: +1 617 332 7970           http://www.shore.net/~sable
                           "Developers of communications software"