INTERNET-DRAFT                              Editor: Kurt D. Zeilenga
Intended Category: Standard Track                OpenLDAP Foundation
Expires: 21 August 2002                             21 February
Expires in six months                                4 November 2002
Obsoletes: RFC 2251-2256, 2829-2830, LDAPTS 3377

                  LDAP: Technical Specification Road Map
                   <draft-ietf-ldapbis-roadmap-00.txt>
                   <draft-ietf-ldapbis-roadmap-01.txt>

Status of this Memo

  This document is an Internet-Draft and is in full conformance with all
  provisions of Section 10 of RFC2026.

  This document is intended to be published as a Standard Track RFC.
  Distribution of this memo is unlimited.  Technical discussion of this
  document will take place on the IETF LDAP Revision Working Group
  mailing list <ietf-ldapbis@openldap.org>.  Please send editorial
  comments directly to the author <Kurt@OpenLDAP.org>.

  Internet-Drafts are working documents of the Internet Engineering Task
  Force (IETF), its areas, and its working groups.  Note that other
  groups may also distribute working documents as Internet-Drafts.
  Internet-Drafts are draft documents valid for a maximum of six months
  and may be updated, replaced, or obsoleted by other documents at any
  time.  It is inappropriate to use Internet-Drafts as reference
  material or to cite them other than as ``work in progress.''

  The list of current Internet-Drafts can be accessed at
  <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
  Internet-Draft Shadow Directories can be accessed at
  <http://www.ietf.org/shadow.html>.

  Copyright 2002, The Internet Society.  All Rights Reserved.

  Please see the Copyright section near the end of this document for
  more information.

Abstract

  The Lightweight Directory Access Protocol (LDAP) is an Internet
  protocol for accessing distributed directory services which act in
  accordance with X.500 data and service models.  This document provides
  a roadmap of the LDAP Technical Specification.

Conventions

  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
  document are to be interpreted as described in BCP 14 [RFC2119].

1. The LDAP Technical Specification

  The technical specification detailing version 3 of the Lightweight
  Directory Access Protocol (LDAP), an Internet Protocol, consists of
  this document and the following documents:

      LDAP: Directory Information Models [Models],
      LDAP: The Protocol [Protocol],
      LDAP: Authentication Methods and Connection Level Security
            Mechanisms [AuthMeth],
      LDAP: String Representation of Distinguished Names [LDAPDN],
      LDAP: String Representation of Search Filters [Filters],
      LDAP: Uniform Resource Locator [LDAPURL],
      LDAP: Syntaxes [Syntaxes], and
      LDAP: User Schema [Schema].

  The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
  the protocol specified by this technical specification.  The LDAP
  protocol
  suite, as defined here, should be formally identified in other
  documents by a normative reference to this document.

  Extensions to LDAP may be specified in other documents.  Nomenclature
  denoting such combinations of LDAP-plus-extension(s) is not defined by
  this document but may be defined in some future document(s).

  IANA (Internet Assigned Numbers Authority) considerations for LDAP [LDAPIANA]
  described in BCP 64 [RFC3383] apply fully to this revision of the LDAP
  technical specification.

2. Relationship to X.500

  This technical specification defines LDAP in terms of [X.500] as an
  X.500 access mechanism.  An LDAP server MUST act in accordance with
  X.500(1993) series of ITU recommendations International Telephone Union (ITU)
  Recommendations when providing the service.  However, it is not
  required that an LDAP server make use of any X.500 protocols in
  providing this service, e.g. LDAP can be mapped onto any other
  directory system so long as the X.500 data and service model models
  [X.501][X.511] as used in LDAP is not violated in the LDAP interface.

3. Security Considerations

  LDAP security considerations are discussed in each document comprising
  the technical specification.

4. Relationship to Obsolete Specifications

  This technical specification, as defined in Section 1, obsoletes
  entirely the previously defined LDAP technical specification [LDAPTS] [RFC3377]
  (which consists of RFC 2251-2256, RFC 2829-2830 and [LDAPTS] [RFC3377] itself).
  The technical specification was significantly reorganized.

  This document replaces replaces [LDAPTS] RFC 3377 as well as Section 3.3 of RFC 2251.
  [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
  [Protocol] replaces the majority RFC 2251 and portions of RFC 2252.
  [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251.
  [Syntax] replaces the majority of RFC 2252 and portions of RFC 2256.
  [Schema] replaces the majority of RFC 2256.  [LDAPDN] replaces RFC
  2253.  [Filters] replaces RFC 2254.  [LDAPURL] replaces RFC 2255.

  Each document of this specification contains appendices detailing
  changes to all sections of the specifications they replace.  Appendix
  A.1 of this document details changes made to [LDAPTS]. RFC 3377.  Appendix A.2
  of this document details changes made to Section 3.3 of RFC 2251.

5. Acknowledgments

  This document is based largely on [LDAPTS] RFC 3377 by J. Hodges and R.
  Morgan, a product of the LDAP Extensions LDAPBIS and LDAPEXT Working Group. Groups.  The
  document also borrows from [RFC2251] RFC 2251 by M. Wahl, T. Howes, and S.
  Kille, a product of the ASID Working Group.

6. Author's Address

  Kurt Zeilenga
  E-mail: <kurt@openldap.org>

7. References

7.1. Normative References

  [RFC2119]  S. Bradner, "Key words for use in RFCs to Indicate
             Requirement Levels", BCP 14 (also RFC 2119, 2119), March 1997.

  [RFC3383]  K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also
             RFC 3383), September 2002.

  [Models]   K. Zeilenga (editor), "LDAP: Directory Information Models",
             draft-ietf-ldapbis-models-xx.txt, a work in progress.

  [Protocol] J. Sermersheim (editor), "LDAP: The Protocol",
             draft-ietf-ldapbis-protocol-xx.txt, a work in progress.

  [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods and
             Connection Level Security Mechanisms",
             draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.

  [LDAPDN]   K. Zeilenga (editor), "LDAP: String Representation of
             Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
             in progress.

  [Filters]  M. Smith (editor), LDAPbis WG, "LDAP: String Representation
             of Search Filters", draft-ietf-ldapbis-filter-xx.txt, a
             work in progress.

  [LDAPURL]  M. Smith (editor), "LDAP: Uniform Resource Locator",
             draft-ietf-ldapbis-url-xx.txt, a work in progress.

  [Syntaxes] K. Dally S. Legg (editor), "LDAP: Syntaxes",
             draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.

  [Schema]   K. Dally (editor), "LDAP: User Schema",
             draft-ietf-ldapbis-user-schema-xx.txt, a work in progress.

  [LDAPIANA] K. Zeilenga, "IANA Considerations for LDAP",
  draft-ietf-ldapbis-xx.txt (a work in progress).

  [X.500]    ITU-T Rec. X.500, "The Directory: Overview of Concepts,
  Models and Service", 1993.

  [X.501]    ITU-T Rec. X.501, "The Directory: Models", 1993.

  [X.511]    ITU-T Rec. X.511, "The Directory: Abstract Service
  Definition", 1993.

7.2. Informative References

  [RFC2251]  M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access
  Protocol (v3)", RFC 2251, December 1997.

  [LDAPTS]   J. Hodges, R.L. Morgan, "Lightweight Directory Access
  Protocol (v3): Technical Specification",
  draft-ietf-ldapbis-ldapv3-ts-xx.txt.

  None.

Appendix A.  Changes to Previous Documents

  This appendix outlines changes this document makes relative to the
  documents it replaces (in whole or in part).

Appendix A.1. Changes to [LDAPTS] RFC 3377

  This document is nearly a complete rewrite of [LDAPTS] RFC 3377 as much of the
  material of [LDAPTS] RFC 3377 is no longer applicable.  These changes include
  defining the term terms "LDAP" in addition to "LDAPv3" and using "LDAP" in
  favor of "LDAPv3" for consistency with the remainder to refer to this revision of
  the technical specification.

Appendix A.2. Changes to Section 3.3 of RFC 2251

  The section was modified slightly (the word "document" was replaced
  with "technical specification") to clarify that it applies to the
  entire LDAP technical specification.

Copyright 2002, The Internet Society.  All Rights Reserved.

  This document and translations of it may be copied and furnished to
  others, and derivative works that comment on or otherwise explain it
  or assist in its implementation may be prepared, copied, published and
  distributed, in whole or in part, without restriction of any kind,
  provided that the above copyright notice and this paragraph are
  included on all such copies and derivative works.  However, this
  document itself may not be modified in any way, such as by removing
  the copyright notice or references to the Internet Society or other
  Internet organizations, except as needed for the  purpose of
  developing Internet standards in which case the procedures for
  copyrights defined in the Internet Standards process must be followed,
  or as required to translate it into languages other than English.

  The limited permissions granted above are perpetual and will not be
  revoked by the Internet Society or its successors or assigns.

  This document and the information contained herein is provided on an
  "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
  ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
  INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
  INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
  WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.