Re: [http-state] Initiating WG Last Call: draft-ietf-httpstate-cookie-08

(FYI)

On 11.05.2010 18:21, =JeffH wrote:
> The purpose of this message is to initiate an HTTPSTATE
> Working Group Last Call on the "HTTP State Management
> Mechanism" Internet Draft.
>
>
> WHAT DOCUMENT?
>
> The document in last call is:
>
> draft-ietf-httpstate-cookie-08
>
> <http://www.ietf.org/id/draft-ietf-httpstate-cookie-08.txt>
>
> <http://tools.ietf.org/html/draft-ietf-httpstate-cookie-08>
>
>
> Issue tracker at:
>
> <http://trac.tools.ietf.org/wg/httpstate/trac/query?component=cookie>
>
>
> WHAT IS A LAST CALL FOR?
>
> The purpose of the Working Group Last Call (WGLC) is to
> ensure that the working group has reached consensus on the
> document, believes that all the known outstanding issues
> have been addressed, and is ready to put the document
> forward for consideration as an RFC at Proposed Standard
> maturity level.
>
> During the last call, any comments on the documents are
> collected and discussed on the http-state@ietf.org
> mailing list.
>
>
> HOW LONG DOES IT LAST?
>
> The last call starts today and will last approximately
> three weeks. It will end on Monday, 31-May-2010 2359h PDT
> (UTC: Tuesday, June 1, 2010 at 0659h).
>
>
> WHAT'S THE NEXT STEP?
>
> After the last call completes, there are three possible
> outcomes:
>
> 1) No changes are required and we request our ADs to put
> forward the document to the IESG for proposed standard
> status.
>
> 2) Minor changes agreed to on the list are required, and
> the document is revised. We then ask our ADs to put
> forward the revised document to the IESG for proposed
> standard status.
>
> 3) Major issues are raised and no consensus is reached on
> the list. In this case, we slink back and discuss things
> until consensus is reached, at which time another working
> group last call will be issued.
>
> Assuming we achieve outcome 1) or 2), and that the ADs
> agree with our assessment, the next stop for the document
> is with the IESG. The IESG reads it and may approve the
> documents (with or without changes), or send the document
> back to the working group to have major issues addressed.
>
> If the first outcome happens, the document is put forward
> for a two-week IETF-wide Last Call, and after successful
> completion the document is published as an RFC at proposed
> standard maturity level.
>
> If the second outcome happens, we go back and address
> the issues, putting the document forward again when we
> believe we're ready.
>
>
> WHAT SHOULD I DO?
>
> You should read the document, making sure that 1) there
> are no problems or deficiencies or outstanding issues that
> need to be resolved; and 2) that there are no typos,
> formatting problems, grammatical errors, etc.
>
> Any substantive problems you find, you should send to the
> list. Any minor problems (typos, etc.) you may send to the
> list or just to the authors. If, for some reason, you have
> comments you don't want to send to the entire list, you may
> send them to me.
>
> Read, enjoy, and send your comments in!
>
> _______________________________________________
> http-state mailing list
> http-state@ietf.org
> https://www.ietf.org/mailman/listinfo/http-state
>

Received on Wednesday, 19 May 2010 09:10:31 UTC