HTTP/1.1 process

The procedure for standards track is outlined in:

    http://www.apps.ietf.org/apps/procedures.html#7

> 1. The WG achieves consensus that an Internet-Draft is ready to be
>    published as a standard

I think we've done that. If you disagree, please let me know ASAP.

> 2. The WG chair informs the ADs that the WG asks for it to be
>   published (NOTE: The WG chair, not the document author!), in E-mail
>   with CC to the iesg-secretary. The WG will not update the document
>   after this point, unless there are problems found later on, in
>   which case the process must be restarted at this point.

That's what my previous message was about.

> 3. The ADs review the document, or have it reviewed, and either
>    accepts it or asks the WG to make revisions to it.
> 4. If the ADs accept it, the AD tells the iesg-secretary to put out
>   an IETF Last Call (generally 2 weeks) on the document. Under some
>   circumstances and at AD discretion, the IETF Last Call may occur in
>   parallel with AD review.

I think we'll likely see this happen immediately.

We'll need to be prepared to respond to comments that occur during
IETF Last Call. It's not out of the question that we'll need to change
the document -- AND EVEN THE PROTOCOL -- before we reach Proposed
Standard. So, it's not over until it's over; we're not Proposed
Standard until the IESG vote, which will likely be at or after
Montreal.  We want to move forward in the process as rapidly as
possible, but not at the expense of standardizing something that
really won't work.

Anyway, that's where we are in the process. I want to thank everyone
personally for all of the careful attention, hard work, and dedication
that has gone into producing this.

Larry

Received on Monday, 10 June 1996 09:22:08 UTC