Note: The items listed in this section are woefully out-of-date, yet these works are technically "still in progress". Perhaps "swapped-out" is a better way to put it ;). I hope to update them someday and finish them up, but events may conspire to render it unnecessary, if they havn't already.

• LDAP Association State Diagram (Revision 2.0b, 1999-Dec-14) -- This is a diagram of the state transitions an LDAP association (aka connection) may go through in the act of binding and/or establishing TLS on the association. This revision is intended to map to RFC2251 + (see above for links to the latter two I-Ds), realize, though, that it (still) needs updating in order to reflect how RFC2830 is written (as of May-2000).

LDAPAssociationStateDiagram-1999-12-14
(an html page that simply href's the 60kb .gif image file that is (directly) linked-to below. This is the same link as the title of the parent bullet item above)

LDAPAssociationStateDiagram-1999-12-14 (22kb .pdf)

LDAPAssociationStateDiagram-1999-12-14 (160kb .ps)

LDAPAssociationStateDiagram-1999-12-14 (60kb .gif)

Note also that all the LDAPv3 RFCs (what all constitutes "LDAPv3" now being officially denoted in RFC3377) are being revised in the ldapbis working group, and [RFC2829 + RFC2830 + appropriate portions of other LDAPv3 RFCs] are now ensconsed in this relatively new Internet-Draft..

• LDAP: Authentication Methods and Connection Level Security Mechanism, R. Harrison, INTERNET-DRAFT, 28 June 2003, available as: <draft-ietf-ldapbis-authmeth-06.txt>

It contains up-to-date "LDAP Association State Transition Tables" in its section 5. Ariel Glenn of Columbia University produced the initial draft of those tables. JeffH sez "check it out".

Also, I suppose that I SHOULD update the LDAPAssociationStateDiagram such that it matches draft-ietf-ldapbis-authmeth-06.txt.

• Authorization IDs shouldn't be restricted to being only Distinguished Names. RL "Bob" Morgan, Jeff Hodges. 25-Mar-1998 (updated 9-Nov-1999). -- This doc is a rant about whether authorization IDs must always be presumed to be Distinguished Names in the context of LDAP-based directory services. We argue that they do not, convinced appropriate folks, and so contributed to the course of the draft-ietf-ldapext-authmeth doc.
  
  
• LDAP-based Routing of SMTP Messages: Approach at Stanford University. J. Hodges, B. Bense. INTERNET-DRAFT, March 1997; available as: <draft-ietf-asid-email-routing-su-00.txt>

Note: this doc is officially expired and has been removed from the Internet Drafts repository. I'm working on an update to it and hope/plan to have it done someday ;-). That's why it's in this work in progress section.

• Requirements for Distinguished Names in Autonomous to Loosely-coupled LDAP-based Directory Services. Jeff Hodges. INTERNET-DRAFT, October 1997. Available as: <draft-hodges-ldap-dir-dn-reqs-00.txt>

Note: this doc expired, thus I'm serving it out of my personal repository. I'm also working on an update ot it.