draft-ietf-ldapbis-roadmap-02.txt   draft-ietf-ldapbis-roadmap-03.txt 
INTERNET-DRAFT Editor: Kurt D. Zeilenga INTERNET-DRAFT Editor: Kurt D. Zeilenga
Intended Category: Standard Track OpenLDAP Foundation Intended Category: Standard Track OpenLDAP Foundation
Expires in six months 1 March 2003 Expires in six months 30 June 2003
Obsoletes: RFC 2251-2256, 2829-2830, 3377 Obsoletes: RFC 2251-2256, 2829-2830, 3377
LDAP: Technical Specification Road Map LDAP: Technical Specification Road Map
<draft-ietf-ldapbis-roadmap-02.txt> <draft-ietf-ldapbis-roadmap-03.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
This document is intended to be published as a Standard Track RFC. This document is intended to be published as a Standard Track RFC.
Distribution of this memo is unlimited. Technical discussion of this Distribution of this memo is unlimited. Technical discussion of this
document will take place on the IETF LDAP Revision Working Group document will take place on the IETF LDAP Revision Working Group
mailing list <ietf-ldapbis@openldap.org>. Please send editorial mailing list <ietf-ldapbis@openldap.org>. Please send editorial
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
Internet-Draft Shadow Directories can be accessed at Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. <http://www.ietf.org/shadow.html>.
Copyright 2003, The Internet Society. All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Please see the Copyright section near the end of this document for Please see the Full Copyright section near the end of this document
more information. for more information.
Abstract Abstract
The Lightweight Directory Access Protocol (LDAP) is an Internet The Lightweight Directory Access Protocol (LDAP) is an Internet
protocol for accessing distributed directory services which act in protocol for accessing distributed directory services which act in
accordance with X.500 data and service models. This document provides accordance with X.500 data and service models. This document provides
a roadmap of the LDAP Technical Specification. a roadmap of the LDAP Technical Specification.
Conventions Conventions
skipping to change at page 2, line 24 skipping to change at page 2, line 24
Directory Access Protocol (LDAP), an Internet Protocol, consists of Directory Access Protocol (LDAP), an Internet Protocol, consists of
this document and the following documents: this document and the following documents:
LDAP: Directory Information Models [Models], LDAP: Directory Information Models [Models],
LDAP: The Protocol [Protocol], LDAP: The Protocol [Protocol],
LDAP: Authentication Methods and Connection Level Security LDAP: Authentication Methods and Connection Level Security
Mechanisms [AuthMeth], Mechanisms [AuthMeth],
LDAP: String Representation of Distinguished Names [LDAPDN], LDAP: String Representation of Distinguished Names [LDAPDN],
LDAP: String Representation of Search Filters [Filters], LDAP: String Representation of Search Filters [Filters],
LDAP: Uniform Resource Locator [LDAPURL], LDAP: Uniform Resource Locator [LDAPURL],
LDAP: Syntaxes [Syntaxes], and LDAP: Syntaxes and Matching Rules [Syntaxes],
LDAP: Internationalized String Preparation [LDAPprep], and
LDAP: User Schema [Schema]. LDAP: User Schema [Schema].
The terms "LDAP" and "LDAPv3" are commonly used to informally refer to The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
the protocol specified by this technical specification. The LDAP the protocol specified by this technical specification. The LDAP
suite, as defined here, should be formally identified in other suite, as defined here, should be formally identified in other
documents by a normative reference to this document. documents by a normative reference to this document.
Extensions to LDAP may be specified in other documents. Nomenclature Extensions to LDAP may be specified in other documents. Nomenclature
denoting such combinations of LDAP-plus-extension(s) is not defined by denoting such combinations of LDAP-plus-extension(s) is not defined by
this document but may be defined in some future document(s). this document but may be defined in some future document(s).
IANA (Internet Assigned Numbers Authority) considerations for LDAP IANA (Internet Assigned Numbers Authority) considerations for LDAP
described in BCP 64 [RFC3383] apply fully to this revision of the LDAP described in BCP 64 [BCP64bis] apply fully to this revision of the
technical specification. LDAP technical specification.
2. Relationship to X.500 2. Relationship to X.500
This technical specification defines LDAP in terms of [X.500] as an 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 access mechanism. An LDAP server MUST act in accordance with
X.500(1993) series of International Telephone Union (ITU) X.500(1993) series of International Telecommunication Union - Telecom
Recommendations when providing the service. However, it is not Standardization (ITU-T) Recommendations when providing the service.
required that an LDAP server make use of any X.500 protocols in However, it is not required that an LDAP server make use of any X.500
providing this service, e.g. LDAP can be mapped onto any other protocols in providing this service, e.g. LDAP can be mapped onto any
directory system so long as the X.500 data and service models other directory system so long as the X.500 data and service models
[X.501][X.511] as used in LDAP is not violated in the LDAP interface. [X.501][X.511] as used in LDAP is not violated in the LDAP interface.
This technical specification explicitly incorporates portions of This technical specification explicitly incorporates portions of
X.500(93). Later revisions of X.500 do not automatically apply. X.500(93). Later revisions of X.500 do not automatically apply.
3. Security Considerations 3. Security Considerations
LDAP security considerations are discussed in each document comprising LDAP security considerations are discussed in each document comprising
the technical specification. the technical specification.
skipping to change at page 3, line 24 skipping to change at page 3, line 24
This technical specification, as defined in Section 1, obsoletes This technical specification, as defined in Section 1, obsoletes
entirely the previously defined LDAP technical specification [RFC3377] entirely the previously defined LDAP technical specification [RFC3377]
(which consists of RFC 2251-2256, RFC 2829-2830 and [RFC3377] itself). (which consists of RFC 2251-2256, RFC 2829-2830 and [RFC3377] itself).
The technical specification was significantly reorganized. The technical specification was significantly reorganized.
This document replaces RFC 3377 as well as Section 3.3 of RFC 2251. This document replaces RFC 3377 as well as Section 3.3 of RFC 2251.
[Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256. [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
[Protocol] replaces the majority RFC 2251 and portions of RFC 2252. [Protocol] replaces the majority RFC 2251 and portions of RFC 2252.
[AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251. [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251.
[Syntax] replaces the majority of RFC 2252 and portions of RFC 2256. [Syntaxes] replaces the majority of RFC 2252 and portions of RFC 2256.
[Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC [Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC
2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255. 2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255.
[LDAPprep] is new to this revision of the LDAP technical
specification.
Each document of this specification contains appendices summarizing Each document of this specification contains appendices summarizing
changes to all sections of the specifications they replace. Appendix changes to all sections of the specifications they replace. Appendix
A.1 of this document details changes made to RFC 3377. Appendix A.2 A.1 of this document details changes made to RFC 3377. Appendix A.2
of this document details changes made to Section 3.3 of RFC 2251. of this document details changes made to Section 3.3 of RFC 2251.
5. Acknowledgments 5. Acknowledgments
This document is based largely on RFC 3377 by J. Hodges and R. This document is based largely on RFC 3377 by J. Hodges and R.
Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
document also borrows from RFC 2251 by M. Wahl, T. Howes, and S. document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
skipping to change at page 4, line 7 skipping to change at page 4, line 9
6. Author's Address 6. Author's Address
Kurt Zeilenga Kurt Zeilenga
E-mail: <kurt@openldap.org> E-mail: <kurt@openldap.org>
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14 (also RFC 2119), March 1997. Requirement Levels", BCP 14 (also RFC 2119), March 1997.
[RFC3383] K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP", draft-
RFC 3383), September 2002. ietf-ldapbis-bcp64-xx.txt, a work in progress.
[Models] K. Zeilenga (editor), "LDAP: Directory Information Models", [Models] Zeilenga, K. (editor), "LDAP: Directory Information
draft-ietf-ldapbis-models-xx.txt, a work in progress. Models", draft-ietf-ldapbis-models-xx.txt, a work in
progress.
[Protocol] J. Sermersheim (editor), "LDAP: The Protocol", [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
draft-ietf-ldapbis-protocol-xx.txt, a work in progress. draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
[AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods and [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
Connection Level Security Mechanisms", Connection Level Security Mechanisms",
draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
[LDAPDN] K. Zeilenga (editor), "LDAP: String Representation of [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a
in progress.
[Filters] M. Smith (editor), LDAPbis WG, "LDAP: String Representation
of Search Filters", draft-ietf-ldapbis-filter-xx.txt, a
work in progress. work in progress.
[LDAPURL] M. Smith (editor), "LDAP: Uniform Resource Locator", [Filters] Smith, M. (editor), LDAPbis WG, "LDAP: String
Representation of Search Filters",
draft-ietf-ldapbis-filter-xx.txt, a work in progress.
[LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
draft-ietf-ldapbis-url-xx.txt, a work in progress. draft-ietf-ldapbis-url-xx.txt, a work in progress.
[Syntaxes] S. Legg (editor), "LDAP: Syntaxes", [Syntaxes] Legg, S. (editor), "LDAP: Syntaxes and Matching Rules",
draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress. draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
[Schema] K. Dally (editor), "LDAP: User Schema", [LDAPprep] Zeilenga, K., "LDAP: Internationalized String
draft-ietf-ldapbis-user-schema-xx.txt, a work in progress. Preparation", draft-ietf-ldapbis-strpro-xx.txt, a work
in progress.
[X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts, [Schema] Dally, K. (editor), "LDAP: User Schema",
Models and Service", 1993. draft-ietf-ldapbis-user-schema-xx.txt, a work in
progress.
[X.501] ITU-T Rec. X.501, "The Directory: Models", 1993. [X.500] International Telecommunication Union -
Telecommunication Standardization Sector, "The Directory
-- Overview of concepts, models and services,"
X.500(1993) (also ISO/IEC 9594-1:1994).
[X.511] ITU-T Rec. X.511, "The Directory: Abstract Service [X.501] International Telecommunication Union -
Definition", 1993. Telecommunication Standardization Sector, "The Directory
-- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
[X.511] International Telecommunication Union -
Telecommunication Standardization Sector, "The
Directory: Abstract Service Definition", X.511(1993).
7.2. Informative References 7.2. Informative References
None. None.
Appendix A. Changes to Previous Documents Appendix A. Changes to Previous Documents
This appendix outlines changes this document makes relative This appendix outlines changes this document makes relative to the
to the documents it replaces (in whole or in part). documents it replaces (in whole or in part).
Appendix A.1. Changes to RFC 3377 Appendix A.1. Changes to RFC 3377
This document is nearly a complete rewrite of RFC 3377 as This document is nearly a complete rewrite of RFC 3377 as much of the
much of the material of RFC 3377 is no longer applicable. material of RFC 3377 is no longer applicable. The changes include
These changes include defining the terms "LDAP" and redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
"LDAPv3" to refer to this revision of the technical the technical specification.
specification.
Appendix A.2. Changes to Section 3.3 of RFC 2251 Appendix A.2. Changes to Section 3.3 of RFC 2251
The section was modified slightly (the word "document" was The section was modified slightly (the word "document" was replaced
replaced with "technical specification") to clarify that it with "technical specification") to clarify that it applies to the
applies to the entire LDAP technical specification. entire LDAP technical specification.
Copyright 2003, The Internet Society. All Rights Reserved. Intellectual Property Rights
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such proprietary
rights by implementors or users of this specification can be obtained
from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed, copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English. 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.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/