draft-ietf-ldapbis-roadmap-08.txt   rfc4510.txt 
INTERNET-DRAFT Editor: Kurt D. Zeilenga Network Working Group K. Zeilenga, Ed.
Intended Category: Standard Track OpenLDAP Foundation Request for Comments: 4510 OpenLDAP Foundation
Expires in six months 30 September 2005 2256, 2829, 2830, 3377, 3771
Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771 Category: Standards Track
Lightweight Directory Access Protocol (LDAP): Lightweight Directory Access Protocol (LDAP):
Technical Specification Road Map Technical Specification Road Map
<draft-ietf-ldapbis-roadmap-08.txt>
Status of this Memo
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>.
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware have
been or will be disclosed, and any of which he or she becomes aware
will be disclosed, in accordance with Section 6 of BCP 79.
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 Status of This Memo
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/shadow.html Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2005). All Rights Reserved. Copyright Notice
Please see the Full Copyright section near the end of this document Copyright (C) The Internet Society (2006).
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 that act in
accordance with X.500 data and service models. This document provides accordance with X.500 data and service models. This document
a roadmap of the LDAP Technical Specification. provides a road map 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 1. The LDAP Technical Specification
The technical specification detailing version 3 of the Lightweight The technical specification detailing version 3 of the Lightweight
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: The Protocol [Protocol], LDAP: The Protocol [RFC4511]
LDAP: Directory Information Models [Models], LDAP: Directory Information Models [RFC4512]
LDAP: Authentication Methods and Connection Level Security LDAP: Authentication Methods and Security Mechanisms [RFC4513]
Mechanisms [AuthMeth], LDAP: String Representation of Distinguished Names [RFC4514]
LDAP: String Representation of Distinguished Names [LDAPDN], LDAP: String Representation of Search Filters [RFC4515]
LDAP: String Representation of Search Filters [Filters], LDAP: Uniform Resource Locator [RFC4516]
LDAP: Uniform Resource Locator [LDAPURL], LDAP: Syntaxes and Matching Rules [RFC4517]
LDAP: Syntaxes and Matching Rules [Syntaxes], LDAP: Internationalized String Preparation [RFC4518]
LDAP: Internationalized String Preparation [LDAPprep], and LDAP: Schema for User Applications [RFC4519]
LDAP: User Schema [Schema]. The terms "LDAP" and "LDAPv3" are commonly used to refer informally
to the protocol specified by this technical specification. The LDAP
The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
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.
LDAP is an extensible protocol. Extensions to LDAP may be specified LDAP is an extensible protocol. Extensions to LDAP may be specified
in other documents. Nomenclature denoting such combinations of in other documents. Nomenclature denoting such combinations of
LDAP-plus-extension(s) is not defined by this document but may be LDAP-plus-extensions is not defined by this document but may be
defined in some future document(s). Extensions are expected to be defined in some future document(s). Extensions are expected to be
truly optional. truly optional. Considerations for the LDAP extensions described in
BCP 118, RFC 4521 [RFC4521] fully apply to this revision of the LDAP
Technical Specification.
IANA (Internet Assigned Numbers Authority) considerations for LDAP IANA (Internet Assigned Numbers Authority) considerations for LDAP
described in BCP 64 [BCP64bis] apply fully to this revision of the described in BCP 64, RFC 4520 [RFC4520] apply fully to this revision
LDAP technical specification. of the LDAP technical specification.
1.1. 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].
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 Telecommunication Union - Telecom the X.500 (1993) series of International Telecommunication Union -
Standardization (ITU-T) Recommendations when providing the service. Telecommunication Standardization (ITU-T) Recommendations when
However, it is not required that an LDAP server make use of any X.500 providing the service. However, it is not required that an LDAP
protocols in providing this service, e.g. LDAP can be mapped onto any server make use of any X.500 protocols in providing this service.
other directory system so long as the X.500 data and service models For example, LDAP can be mapped onto any other directory system so
[X.501][X.511] as used in LDAP is not violated in the LDAP interface. long as the X.500 data and service models [X.501][X.511], as used in
LDAP, are 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 to X.500(93). Later revisions of X.500 do not automatically apply to
this technical specification. this technical specification.
3. Relationship to Obsolete Specifications 3. Relationship to Obsolete Specifications
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 defined
(which consists of RFC 2251-2256, RFC 2829-2830, RFC 3771, and RFC in RFC 3377 (and consisting of RFCs 2251-2256, 2829, 2830, 3771, and
3377 itself). The technical specification was significantly 3377 itself). The technical specification was significantly
reorganized. 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. [RFC4512] replaces portions of RFC 2251, RFC 2252, and RFC 2256.
[Protocol] replaces the majority RFC 2251, portions of RFC 2252, and [RFC4511] replaces the majority RFC 2251, portions of RFC 2252, and
all of RFC 3771. [AuthMeth] replaces RFC 2829, RFC 2830, and portions all of RFC 3771. [RFC4513] replaces RFC 2829, RFC 2830, and portions
of RFC 2251. [Syntaxes] replaces the majority of RFC 2252 and of RFC 2251. [RFC4517] replaces the majority of RFC 2252 and
portions of RFC 2256. [Schema] replaces the majority of RFC 2256. portions of RFC 2256. [RFC4519] replaces the majority of RFC 2256.
[LDAPDN] replaces RFC 2253. [Filters] replaces RFC 2254. [LDAPURL] [RFC4514] replaces RFC 2253. [RFC4515] replaces RFC 2254. [RFC4516]
replaces RFC 2255. replaces RFC 2255.
[LDAPprep] is new to this revision of the LDAP technical [RFC4518] is new to this revision of the LDAP technical
specification. 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.
Additionally, portions of this technical specification update and/or Additionally, portions of this technical specification update and/or
replace a number of other documents not listed above. These replace a number of other documents not listed above. These
relationships are discussed in the documents detailings these portions relationships are discussed in the documents detailing these portions
of this technical specification. of this technical specification.
4. Security Considerations 4. Security Considerations
LDAP security considerations are discussed in each document comprising
the technical specification.
5. IANA Considerations
No actions. LDAP security considerations are discussed in each document
comprising the technical specification.
[[Note to RFC Editor: this section may be removed prior to
publication.]]
6. Acknowledgments 5. Acknowledgements
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.
Kille, a product of the ASID Working Group. Kille, a product of the ASID Working Group.
This document is a product of the IETF LDAPBIS Working Group. This document is a product of the IETF LDAPBIS Working Group.
7. Author's Address 6. Normative References
Kurt D. Zeilenga
OpenLDAP Foundation
Email: Kurt@OpenLDAP.org
8. References
[[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn where
possible.]]
8.1. Normative References
[RFC2119] Bradner, S., "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, RFC 2119, March 1997.
[BCP64bis] Zeilenga, K., "IANA Considerations for LDAP", [RFC4511] Sermersheim, J., Ed., "Lightweight Directory Access
draft-ietf-ldapbis-bcp64-xx.txt, a work in progress. Protocol (LDAP): The Protocol", RFC 4511, June 2006.
[Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", [RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol
draft-ietf-ldapbis-protocol-xx.txt, a work in progress. (LDAP): Directory Information Models", RFC 4512, June
2006.
[Models] Zeilenga, K. (editor), "LDAP: Directory Information [RFC4513] Harrison, R., Ed., "Lightweight Directory Access
Models", draft-ietf-ldapbis-models-xx.txt, a work in Protocol (LDAP): Authentication Methods and Security
progress. Mechanisms", RFC 4513, June 2006.
[AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and [RFC4514] Zeilenga, K., Ed., "Lightweight Directory Access
Connection Level Security Mechanisms", Protocol (LDAP): String Representation of Distinguished
draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. Names", RFC 4514, June 2006.
[LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of [RFC4515] Smith, M., Ed. and T. Howes, "Lightweight Directory
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a Access Protocol (LDAP): String Representation of Search
work in progress. Filters", RFC 4515, June 2006.
[Filters] Smith, M. (editor), LDAPbis WG, "LDAP: String [RFC4516] Smith, M., Ed. and T. Howes, "Lightweight Directory
Representation of Search Filters", Access Protocol (LDAP): Uniform Resource Locator", RFC
draft-ietf-ldapbis-filter-xx.txt, a work in progress. 4516, June 2006.
[LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator", [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol
draft-ietf-ldapbis-url-xx.txt, a work in progress. (LDAP): Syntaxes and Matching Rules", RFC 4517, June
2006.
[Syntaxes] Legg, S. (editor), "LDAP: Syntaxes and Matching Rules", [RFC4518] Zeilenga, K., "Lightweight Directory Access Protocol
draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress. (LDAP): Internationalized String Preparation", RFC
4518, June 2006.
[LDAPprep] Zeilenga, K., "LDAP: Internationalized String [RFC4519] Sciberras, A., Ed., "Lightweight Directory Access
Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work Protocol (LDAP): Schema for User Applications", RFC
in progress. 4519, June 2006.
[Schema] Dally, K. (editor), "LDAP: User Schema", [RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority
draft-ietf-ldapbis-user-schema-xx.txt, a work in (IANA) Considerations for the Lightweight Directory
progress. Access Protocol (LDAP)", BCP 64, RFC 4520, June 2006.
[RFC4521] Zeilenga, K., "Considerations for LDAP Extensions", BCP
118, RFC 4521, June 2006.
[X.500] International Telecommunication Union - [X.500] International Telecommunication Union -
Telecommunication Standardization Sector, "The Directory Telecommunication Standardization Sector, "The
-- Overview of concepts, models and services," Directory -- Overview of concepts, models and
X.500(1993) (also ISO/IEC 9594-1:1994). services", X.500(1993) (also ISO/IEC 9594-1:1994).
[X.501] International Telecommunication Union - [X.501] International Telecommunication Union -
Telecommunication Standardization Sector, "The Directory Telecommunication Standardization Sector, "The
-- Models," X.501(1993) (also ISO/IEC 9594-2:1994). Directory -- Models", X.501(1993) (also ISO/IEC 9594-
2:1994).
[X.511] International Telecommunication Union - [X.511] International Telecommunication Union -
Telecommunication Standardization Sector, "The Telecommunication Standardization Sector, "The
Directory: Abstract Service Definition", X.511(1993) Directory: Abstract Service Definition", X.511(1993)
(also ISO/IEC 9594-3:1993). (also ISO/IEC 9594-3:1993).
8.2. Informative References
None.
Appendix A. Changes to Previous Documents Appendix A. Changes to Previous Documents
This appendix outlines changes this document makes relative to the This appendix outlines changes this document makes relative 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 A.1. Changes to RFC 3377
This document is nearly a complete rewrite of RFC 3377 as much of the This document is nearly a complete rewrite of RFC 3377 as much of the
material of RFC 3377 is no longer applicable. The changes include material of RFC 3377 is no longer applicable. The changes include
redefining the terms "LDAP" and "LDAPv3" to refer to this revision of redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
the technical specification. the technical specification.
Appendix A.2. Changes to Section 3.3 of RFC 2251 A.2. Changes to Section 3.3 of RFC 2251
The section was modified slightly (the word "document" was replaced The section was modified slightly (the word "document" was replaced
with "technical specification") to clarify that it applies to the with "technical specification") to clarify that it applies to the
entire LDAP technical specification. entire LDAP technical specification.
Intellectual Property Rights Author's Address
Kurt D. Zeilenga
OpenLDAP Foundation
EMail: Kurt@OpenLDAP.org
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be found on the procedures with respect to rights in RFC documents can be
in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this specification such proprietary rights by implementers or users of this
can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Acknowledgement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an Funding for the RFC Editor function is provided by the IETF
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Administrative Support Activity (IASA).
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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. 41 change blocks. 
149 lines changed or deleted 129 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/