LAST CALL: draft-ietf-ldapext-ldap-taxonomy-01.txt

[Mark Wahl <M.Wahl@INNOSOFT.COM>]

The purpose of this message is to initiate an LDAPEXT
working group last call on the Taxonomy of Methods for
LDAP Clients Finding Servers.  This draft will have
the Informational status, as it does not intend to
specify a Internet standard.

WHAT DOCUMENT?

The document in last call is:

      draft-ietf-ldapext-ldap-taxonomy-01.txt

WHAT IS A LAST CALL FOR?

An "Informational" specification is published for the general
information of the Internet community, and does not necessarily
represent an Internet community consensus or recommendation.  
The Informational designation is intended to provide for the 
timely publication of a very broad range of responsible 
informational documents from many sources, subject only to 
editorial considerations and to verification that there has 
been adequate coordination with the standards process.

Documents proposed for Experimental and Informational RFCs 
by IETF Working Groups go through IESG review.  We do a 
Working Group Last Call to ensure that the document has
first had reasonable technical review by the LDAP community,
which believes that all the known outstanding issues have 
been addressed, and is ready to put the document forward 
with informational 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 three
weeks. It will end on Wednesday, January 12, 2000.

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 informational
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 publication
as informational.

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 them and may approve the
document (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 last call to the entire IETF, and after
successful completion the document is published as RFCs
with Informational status.

If the second outcome happens, we go back and address
the issues, putting the document forward again when we
believe they'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.

Please note that some referenced drafts have been 
renamed or published as RFCs.  Reference [4] now indicates 
RFC 2608, references [6], [7], [8] and [9] now indicate RFCs 
2651 through 2654, and reference [13] now indicates
draft-ietf-ldapext-locate-00.txt.

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 Tim Howes.

Read, enjoy, and send your comments in!

Mark Wahl, Directory Product Architect
Innosoft International, Inc.