- RFC 1274
-
"The COSINE and Internet
X.500 Schema". P. Barker and S. Kille. November
1991. Status: Proposed Standard.
- RFC 2079
-
"Definition
of an X.500 Attribute Type and an Object Class to Hold Uniform
Resource Identifiers (URIs)". M. Smith. January
1997. Status: Proposed Standard.
- RFC 2247
-
"Using Domains in LDAP/X.500 Distinguished
Names". S. Kille et al. January 1998. Status:
Proposed Standard.
- RFC 2251
-
"Lightweight
Directory Access Protocol (v3)". M. Wahl, T. Howes,
and S. Kille. December 1997. Status: Proposed Standard.
- RFC 2252
-
"Lightweight Directory Access Protocol (v3):
Attribute Syntax Definitions". M. Wahl et al.
December 1997. Status: Proposed Standard.
- RFC 2253
-
"Lightweight Directory Access Protocol (v3): UTF-8
String Representation of Distinguished Names". M.
Wahl, S. Kille, and T. Howes. December 1997. Status: Proposed
Standard.
- RFC 2254
-
"The String
Representation of LDAP Search Filters". T. Howes.
December 1997. Status: Proposed Standard.
- RFC 2255
-
"The
LDAP URL
Format". T. Howes and M. Smith. December 1997.
Status: Proposed Standard.
- RFC 2256
-
"A Summary of the X.500(96) User Schema for use with
LDAPv3". M. Wahl. December
1997. Status: Proposed Standard.
- RFC 2293
-
"Representing Tables and Subtrees in the X.500
Directory". S. Kille. March 1998. Status: Proposed
Standard.
- RFC 2294
-
"Representing the O/R Address Hierarchy in the X.500
Directory Information Tree". S. Kille. March 1998.
Status: Proposed Standard.
- RFC 2307
-
"An Approach for Using LDAP
as a Network Information Service". L. Howard. March
1998. Status: Experimental.
- RFC 2377
-
"Naming Plan for Internet Directory-Enabled
Applications". A. Grimstad et al. September 1998.
Status: Informational.
- RFC 2589
-
"Lightweight Directory Access Protocol (v3):
Extensions for Dynamic Directory
Services". Y. Yaacovi, M. Wahl, and T. Genovese. May
1999. Status: Proposed Standard.
- RFC 2596
-
"Use of Language Codes in LDAP". M.
Wahl and T. Howes. May 1999. Status: Proposed Standard.
- RFC 2649
-
"An LDAP Control and Schema for Holding Operation
Signatures". B. Greenblatt and P. Richard. August
1999. Status: Experimental.
- RFC 2696
-
"LDAP Control Extension for Simple Paged Results
Manipulation". C. Weider et al. September 1999.
Status: Informational.
- RFC 2713
-
"Schema for
Representing Java™ Objects in an LDAP
Directory". V. Ryan, S. Seligman, and R. Lee.
October 1999. Status: Informational.
- RFC 2714
-
"Schema for Representing CORBA Object References
in an LDAP Directory". V. Ryan, R. Lee, and S.
Seligman. October 1999. Status: Informational.
- RFC 2798
-
"Definition of the inetOrgPerson LDAP Object
Class". M. Smith. April 2000. Status: Informational.
- RFC 2829
-
"Authentication Methods
for LDAP". M. Wahl et al. May 2000. Status: Proposed
Standard.
- RFC 2830
-
"Lightweight
Directory Access Protocol (v3): Extension for Transport Layer
Security". J. Hodges, R. Morgan, and M. Wahl. May
2000. Status: Proposed Standard.
- RFC 2849
-
"The LDAP Data Interchange
Format (LDIF)—Technical Specification". G.
Good. June 2000. Status: Proposed Standard.
- RFC 2891
-
"LDAP Control Extension for Server Side Sorting
of Search Results". T. Howes, M. Wahl, and A.
Anantha. August 2000. Status: Proposed Standard.
- RFC 3045
-
"Storing
Vendor Information in the LDAP root DSE". M.
Meredith. January 2001. Status: Informational.
- RFC 3062
-
"LDAP Password
Modify Extended Operation". K. Zeilenga. February
2001. Status: Proposed Standard.
- RFC 3088
-
"OpenLDAP Root Service: An experimental LDAP
referral service". K. Zeilenga. April 2001. Status:
Experimental.
- RFC 3112
-
"LDAP
Authentication Password Schema". K. Zeilenga. May
2001. Status: Experimental.
- RFC 3296
-
"Named
Subordinate References in Lightweight Directory Access Protocol
(LDAP) Directories". K. Zeilenga. July 2002. Status:
Proposed Standard.
- RFC 3377
-
"Lightweight Directory Access Protocol (v3):
Technical Specification". J.
Hodges and R. Morgan. September 2002. Status: Proposed Standard.
- RFC 3383
-
"Internet Assigned
Numbers Authority (IANA) Considerations for the Lightweight Directory
Access Protocol (LDAP)". K. Zeilenga. September
2002. Status: Best Common Practices.
Internet-Drafts (I-Ds) are temporary by
nature, although this often does not stop vendors from implementing
parts or all of the functionality that a draft outlines. The I-Ds
listed here are included for their relevance to topics covered in one
or more chapters in this book. The absence of an I-D from this list
should not be interpreted to mean it may or may not be relevant in
future LDAP deployments.