4510
PROPOSED STANDARD
Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map
Authors: K. Zeilenga
Date: June 2006
Area: app
Working Group: ldapbis
Stream: IETF
Obsoletes:
RFC 2251
Abstract
The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. This document provides a road map of the LDAP Technical Specification. [STANDARDS-TRACK]
RFC 4510
PROPOSED STANDARD
Errata Exist
Network Working Group K. Zeilenga, Ed.
Request for Comments: 4510 OpenLDAP Foundation
Obsoletes: <a href="./rfc2251">2251</a>, <a href="./rfc2252">2252</a>, <a href="./rfc2253">2253</a>, <a href="./rfc2254">2254</a>, <a href="./rfc2255">2255</a>, June 2006
<a href="./rfc2256">2256</a>, <a href="./rfc2829">2829</a>, <a href="./rfc2830">2830</a>, <a href="./rfc3377">3377</a>, <a href="./rfc3771">3771</a>
Category: Standards Track
<span class="h1">Lightweight Directory Access Protocol (LDAP):</span>
<span class="h1">Technical Specification Road Map</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
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 Notice
Copyright (C) The Internet Society (2006).
Abstract
The Lightweight Directory Access Protocol (LDAP) is an Internet
protocol for accessing distributed directory services that act in
accordance with X.500 data and service models. This document
provides a road map of the LDAP Technical Specification.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. The LDAP Technical Specification</span>
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: The Protocol [<a href="./rfc4511" title=""Lightweight Directory Access Protocol (LDAP): The Protocol"">RFC4511</a>]
LDAP: Directory Information Models [<a href="./rfc4512" title=""Lightweight Directory Access Protocol (LDAP): Directory Information Models"">RFC4512</a>]
LDAP: Authentication Methods and Security Mechanisms [<a href="./rfc4513" title=""Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms"">RFC4513</a>]
LDAP: String Representation of Distinguished Names [<a href="./rfc4514" title=""Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names"">RFC4514</a>]
LDAP: String Representation of Search Filters [<a href="./rfc4515" title=""Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters"">RFC4515</a>]
LDAP: Uniform Resource Locator [<a href="./rfc4516" title=""Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator"">RFC4516</a>]
LDAP: Syntaxes and Matching Rules [<a href="./rfc4517" title=""Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules"">RFC4517</a>]
LDAP: Internationalized String Preparation [<a href="./rfc4518" title=""Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation"">RFC4518</a>]
LDAP: Schema for User Applications [<a href="./rfc4519" title=""Lightweight Directory Access Protocol (LDAP): Schema for User Applications"">RFC4519</a>]
<span class="grey">Zeilenga Standards Track [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
The terms "LDAP" and "LDAPv3" are commonly used to refer informally
to the protocol specified by this technical specification. The LDAP
suite, as defined here, should be formally identified in other
documents by a normative reference to this document.
LDAP is an extensible protocol. Extensions to LDAP may be specified
in other documents. Nomenclature denoting such combinations of
LDAP-plus-extensions is not defined by this document but may be
defined in some future document(s). Extensions are expected to be
truly optional. Considerations for the LDAP extensions described in
<a href="https://www.rfc-editor.org/bcp/bcp118">BCP 118</a>, <a href="./rfc4521">RFC 4521</a> [<a href="./rfc4521" title=""Considerations for LDAP Extensions"">RFC4521</a>] fully apply to this revision of the LDAP
Technical Specification.
IANA (Internet Assigned Numbers Authority) considerations for LDAP
described in <a href="https://www.rfc-editor.org/bcp/bcp64">BCP 64</a>, <a href="./rfc4520">RFC 4520</a> [<a href="./rfc4520" title=""Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)"">RFC4520</a>] apply fully to this revision
of the LDAP technical specification.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions</span>
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 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Relationship to X.500</span>
This technical specification defines LDAP in terms of [<a href="#ref-X.500" title=""The Directory -- Overview of concepts, models and services"">X.500</a>] as an
X.500 access mechanism. An LDAP server MUST act in accordance with
the X.500 (1993) series of International Telecommunication Union -
Telecommunication Standardization (ITU-T) 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.
For example, LDAP can be mapped onto any other directory system so
long as the X.500 data and service models [<a href="#ref-X.501" title=""The Directory -- Models"">X.501</a>][X.511], as used in
LDAP, are not violated in the LDAP interface.
This technical specification explicitly incorporates portions of
X.500(93). Later revisions of X.500 do not automatically apply to
this technical specification.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Relationship to Obsolete Specifications</span>
This technical specification, as defined in <a href="#section-1">Section 1</a>, obsoletes
entirely the previously defined LDAP technical specification defined
in <a href="./rfc3377">RFC 3377</a> (and consisting of RFCs 2251-2256, 2829, 2830, 3771, and
3377 itself). The technical specification was significantly
reorganized.
<span class="grey">Zeilenga Standards Track [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
This document replaces <a href="./rfc3377">RFC 3377</a> as well as <a href="./rfc2251#section-3.3">Section 3.3 of RFC 2251</a>.
[<a href="./rfc4512" title=""Lightweight Directory Access Protocol (LDAP): Directory Information Models"">RFC4512</a>] replaces portions of <a href="./rfc2251">RFC 2251</a>, <a href="./rfc2252">RFC 2252</a>, and <a href="./rfc2256">RFC 2256</a>.
[<a href="./rfc4511" title=""Lightweight Directory Access Protocol (LDAP): The Protocol"">RFC4511</a>] replaces the majority <a href="./rfc2251">RFC 2251</a>, portions of <a href="./rfc2252">RFC 2252</a>, and
all of <a href="./rfc3771">RFC 3771</a>. [<a href="./rfc4513" title=""Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms"">RFC4513</a>] replaces <a href="./rfc2829">RFC 2829</a>, <a href="./rfc2830">RFC 2830</a>, and portions
of <a href="./rfc2251">RFC 2251</a>. [<a href="./rfc4517" title=""Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules"">RFC4517</a>] replaces the majority of <a href="./rfc2252">RFC 2252</a> and
portions of <a href="./rfc2256">RFC 2256</a>. [<a href="./rfc4519" title=""Lightweight Directory Access Protocol (LDAP): Schema for User Applications"">RFC4519</a>] replaces the majority of <a href="./rfc2256">RFC 2256</a>.
[<a href="./rfc4514" title=""Lightweight Directory Access Protocol (LDAP): String Representation of Distinguished Names"">RFC4514</a>] replaces <a href="./rfc2253">RFC 2253</a>. [<a href="./rfc4515" title=""Lightweight Directory Access Protocol (LDAP): String Representation of Search Filters"">RFC4515</a>] replaces <a href="./rfc2254">RFC 2254</a>. [<a href="./rfc4516" title=""Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator"">RFC4516</a>]
replaces <a href="./rfc2255">RFC 2255</a>.
[<a id="ref-RFC4518">RFC4518</a>] is new to this revision of the LDAP technical
specification.
Each document of this specification contains appendices summarizing
changes to all sections of the specifications they replace. <a href="#appendix-A.1">Appendix</a>
<a href="#appendix-A.1">A.1</a> of this document details changes made to <a href="./rfc3377">RFC 3377</a>. <a href="#appendix-A.2">Appendix A.2</a>
of this document details changes made to <a href="./rfc2251#section-3.3">Section 3.3 of RFC 2251</a>.
Additionally, portions of this technical specification update and/or
replace a number of other documents not listed above. These
relationships are discussed in the documents detailing these portions
of this technical specification.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
LDAP security considerations are discussed in each document
comprising the technical specification.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
This document is based largely on <a href="./rfc3377">RFC 3377</a> by J. Hodges and R.
Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
document also borrows from <a href="./rfc2251">RFC 2251</a> by M. Wahl, T. Howes, and S.
Kille, a product of the ASID Working Group.
This document is a product of the IETF LDAPBIS Working Group.
<span class="grey">Zeilenga Standards Track [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC4511">RFC4511</a>] Sermersheim, J., Ed., "Lightweight Directory Access
Protocol (LDAP): The Protocol", <a href="./rfc4511">RFC 4511</a>, June 2006.
[<a id="ref-RFC4512">RFC4512</a>] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Directory Information Models", <a href="./rfc4512">RFC 4512</a>, June
2006.
[<a id="ref-RFC4513">RFC4513</a>] Harrison, R., Ed., "Lightweight Directory Access
Protocol (LDAP): Authentication Methods and Security
Mechanisms", <a href="./rfc4513">RFC 4513</a>, June 2006.
[<a id="ref-RFC4514">RFC4514</a>] Zeilenga, K., Ed., "Lightweight Directory Access
Protocol (LDAP): String Representation of Distinguished
Names", <a href="./rfc4514">RFC 4514</a>, June 2006.
[<a id="ref-RFC4515">RFC4515</a>] Smith, M., Ed. and T. Howes, "Lightweight Directory
Access Protocol (LDAP): String Representation of Search
Filters", <a href="./rfc4515">RFC 4515</a>, June 2006.
[<a id="ref-RFC4516">RFC4516</a>] Smith, M., Ed. and T. Howes, "Lightweight Directory
Access Protocol (LDAP): Uniform Resource Locator", <a href="./rfc4516">RFC</a>
<a href="./rfc4516">4516</a>, June 2006.
[<a id="ref-RFC4517">RFC4517</a>] Legg, S., Ed., "Lightweight Directory Access Protocol
(LDAP): Syntaxes and Matching Rules", <a href="./rfc4517">RFC 4517</a>, June
2006.
[<a id="ref-RFC4518">RFC4518</a>] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Internationalized String Preparation", <a href="./rfc4518">RFC</a>
<a href="./rfc4518">4518</a>, June 2006.
[<a id="ref-RFC4519">RFC4519</a>] Sciberras, A., Ed., "Lightweight Directory Access
Protocol (LDAP): Schema for User Applications", <a href="./rfc4519">RFC</a>
<a href="./rfc4519">4519</a>, June 2006.
[<a id="ref-RFC4520">RFC4520</a>] Zeilenga, K., "Internet Assigned Numbers Authority
(IANA) Considerations for the Lightweight Directory
Access Protocol (LDAP)", <a href="https://www.rfc-editor.org/bcp/bcp64">BCP 64</a>, <a href="./rfc4520">RFC 4520</a>, June 2006.
[<a id="ref-RFC4521">RFC4521</a>] Zeilenga, K., "Considerations for LDAP Extensions", <a href="https://www.rfc-editor.org/bcp/bcp118">BCP</a>
<a href="https://www.rfc-editor.org/bcp/bcp118">118</a>, <a href="./rfc4521">RFC 4521</a>, June 2006.
<span class="grey">Zeilenga Standards Track [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
[<a id="ref-X.500">X.500</a>] International Telecommunication Union -
Telecommunication Standardization Sector, "The
Directory -- Overview of concepts, models and
services", X.500(1993) (also ISO/IEC 9594-1:1994).
[<a id="ref-X.501">X.501</a>] International Telecommunication Union -
Telecommunication Standardization Sector, "The
Directory -- Models", X.501(1993) (also ISO/IEC 9594-
2:1994).
[<a id="ref-X.511">X.511</a>] International Telecommunication Union -
Telecommunication Standardization Sector, "The
Directory: Abstract Service Definition", X.511(1993)
(also ISO/IEC 9594-3:1993).
<span class="grey">Zeilenga Standards Track [Page 5]</span><span id="page-6" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Changes to Previous Documents</span>
This appendix outlines changes this document makes relative to the
documents it replaces (in whole or in part).
<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Changes to <a href="./rfc3377">RFC 3377</a></span>
This document is nearly a complete rewrite of <a href="./rfc3377">RFC 3377</a> as much of the
material of <a href="./rfc3377">RFC 3377</a> is no longer applicable. The changes include
redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
the technical specification.
<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Changes to <a href="./rfc2251#section-3.3">Section 3.3 of RFC 2251</a></span>
The section was modified slightly (the word "document" was replaced
with "technical specification") to clarify that it applies to the
entire LDAP technical specification.
Author's Address
Kurt D. Zeilenga
OpenLDAP Foundation
EMail: [email protected]
<span class="grey">Zeilenga Standards Track [Page 6]</span><span id="page-7" ></span>
<span class="grey"><a href="./rfc4510">RFC 4510</a> LDAP: TS Road Map June 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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
Intellectual Property Rights 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
[email protected].
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Zeilenga Standards Track [Page 7]
Annotations
Select text to annotate