Re: LAST CALL: draft-ietf-ldapext-ldap-java-api-05.txt

[howes@netscape.com (Tim Howes)]

One slight correction to this last call. It should also
include draft-ietf-ldapext-ldap-java-api-asynch-ext-00.txt.
This draft includes some additional mandatory to implement
API calls that were broken out from the other draft.

Please read and comment on both drafts.     -- Tim

Tim Howes wrote:
> 
> The purpose of this message is to initiate the LDAPEXT
> working group last call on the LDAPv3 Java API specification
> document.
> 
> WHAT DOCUMENT?
> 
> The LDAPv3 Java API document in last call is:
> 
>         draft-ietf-ldapext-ldap-java-api-05.txt
> 
> WHAT IS A LAST CALL FOR?
> 
> The purpose of the working group last call 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 proposed standard status.
> 
> During the last call, any comments on the documents are
> collected and discussed on the mailing list.
> 
> HOW LONG DOES IT LAST?
> 
> The last call starts today and will last approximately two
> weeks. It will end on Monday, June 28, 1999.
> 
> 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 documents to the IESG for proposed standard
> status.
> 
> 2) Minor changes agreed to on the list are required, and
> the documents are revised. We then ask our ADs to put
> forward the revised documents 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 documents
> is with the IESG. The IESG reads them and may approve the
> documents (with or without changes), or send the documents
> back to the working group to have major issues addressed.
> 
> If the first outcome happens, the documents are put forward
> for a two-week last call to the entire IETF, and after
> successful completion the documents are published as RFCs
> with proposed standard status.
> 
> If the second outcome happens, we go back and address
> the issues, putting the documents forward again when we
> believe they're ready.
> 
> WHAT SHOULD I DO?
> 
> You should read the documents, 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 or my co-chair Mark Wahl.
> 
> Read, enjoy, and send your comments in!
>             -- Tim