1 INTERNET-DRAFT Editor: Kurt D. Zeilenga
2 Intended Category: Standard Track OpenLDAP Foundation
3 Expires in six months 24 October 2004
4 Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771
9 Lightweight Directory Access Protocol (LDAP):
10 Technical Specification Road Map
11 <draft-ietf-ldapbis-roadmap-06.txt>
19 This document is intended to be published as a Standard Track RFC.
20 Distribution of this memo is unlimited. Technical discussion of this
21 document will take place on the IETF LDAP Revision Working Group
22 mailing list <ietf-ldapbis@openldap.org>. Please send editorial
23 comments directly to the author <Kurt@OpenLDAP.org>.
26 By submitting this Internet-Draft, I accept the provisions of Section
27 4 of RFC 3667. By submitting this Internet-Draft, I certify that any
28 applicable patent or other IPR claims of which I am aware have been
29 disclosed, or will be disclosed, and any of which I become aware will
30 be disclosed, in accordance with RFC 3668.
33 Internet-Drafts are working documents of the Internet Engineering Task
34 Force (IETF), its areas, and its working groups. Note that other
35 groups may also distribute working documents as Internet-Drafts.
38 Internet-Drafts are draft documents valid for a maximum of six months
39 and may be updated, replaced, or obsoleted by other documents at any
40 time. It is inappropriate to use Internet-Drafts as reference material
41 or to cite them other than as "work in progress."
44 The list of current Internet-Drafts can be accessed at
45 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
46 Internet-Draft Shadow Directories can be accessed at
47 <http://www.ietf.org/shadow.html>.
50 Copyright (C) The Internet Society (2004). All Rights Reserved.
53 Please see the Full Copyright section near the end of this document
62 Zeilenga LDAP: TS Road Map [Page 1]
63 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
70 The Lightweight Directory Access Protocol (LDAP) is an Internet
71 protocol for accessing distributed directory services which act in
72 accordance with X.500 data and service models. This document provides
73 a roadmap of the LDAP Technical Specification.
80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
82 document are to be interpreted as described in BCP 14 [RFC2119].
86 1. The LDAP Technical Specification
89 The technical specification detailing version 3 of the Lightweight
90 Directory Access Protocol (LDAP), an Internet Protocol, consists of
91 this document and the following documents:
94 LDAP: The Protocol [Protocol],
95 LDAP: Directory Information Models [Models],
96 LDAP: Authentication Methods and Connection Level Security
97 Mechanisms [AuthMeth],
98 LDAP: String Representation of Distinguished Names [LDAPDN],
99 LDAP: String Representation of Search Filters [Filters],
100 LDAP: Uniform Resource Locator [LDAPURL],
101 LDAP: Syntaxes and Matching Rules [Syntaxes],
102 LDAP: Internationalized String Preparation [LDAPprep], and
103 LDAP: User Schema [Schema].
106 The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
107 the protocol specified by this technical specification. The LDAP
108 suite, as defined here, should be formally identified in other
109 documents by a normative reference to this document.
112 LDAP is an extensible protocol. Extensions to LDAP may be specified
113 in other documents. Nomenclature denoting such combinations of
114 LDAP-plus-extension(s) is not defined by this document but may be
115 defined in some future document(s). Extensions are expected to be
119 IANA (Internet Assigned Numbers Authority) considerations for LDAP
120 described in BCP 64 [BCP64bis] apply fully to this revision of the
121 LDAP technical specification.
128 Zeilenga LDAP: TS Road Map [Page 2]
129 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
133 2. Relationship to X.500
136 This technical specification defines LDAP in terms of [X.500] as an
137 X.500 access mechanism. An LDAP server MUST act in accordance with
138 X.500(1993) series of International Telecommunication Union - Telecom
139 Standardization (ITU-T) Recommendations when providing the service.
140 However, it is not required that an LDAP server make use of any X.500
141 protocols in providing this service, e.g. LDAP can be mapped onto any
142 other directory system so long as the X.500 data and service models
143 [X.501][X.511] as used in LDAP is not violated in the LDAP interface.
146 This technical specification explicitly incorporates portions of
147 X.500(93). Later revisions of X.500 do not automatically apply.
151 3. Security Considerations
154 LDAP security considerations are discussed in each document comprising
155 the technical specification.
159 4. Relationship to Obsolete Specifications
162 This technical specification, as defined in Section 1, obsoletes
163 entirely the previously defined LDAP technical specification [RFC3377]
164 (which consists of RFC 2251-2256, RFC 2829-2830, RFC 3771, and RFC
165 3377 itself). The technical specification was significantly
169 This document replaces RFC 3377 as well as Section 3.3 of RFC 2251.
170 [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
171 [Protocol] replaces the majority RFC 2251, portions of RFC 2252, and
172 all of RFC 3771. [AuthMeth] replaces RFC 2829, RFC 2830, and portions
173 of RFC 2251. [Syntaxes] replaces the majority of RFC 2252 and
174 portions of RFC 2256. [Schema] replaces the majority of RFC 2256.
175 [LDAPDN] replaces RFC 2253. [Filters] replaces RFC 2254. [LDAPURL]
179 [LDAPprep] is new to this revision of the LDAP technical
183 Each document of this specification contains appendices summarizing
184 changes to all sections of the specifications they replace. Appendix
185 A.1 of this document details changes made to RFC 3377. Appendix A.2
186 of this document details changes made to Section 3.3 of RFC 2251.
189 Additionally, portions of this technical specification update and/or
190 replace a number of other documents not listed above. These
195 Zeilenga LDAP: TS Road Map [Page 3]
196 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
200 relationships are discussed in the documents detailings these portions
201 of this technical specification.
208 This document is based largely on RFC 3377 by J. Hodges and R.
209 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
210 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
211 Kille, a product of the ASID Working Group.
214 This document is a product of the IETF LDAPBIS Working Group.
222 E-mail: <kurt@openldap.org>
229 [[Note to the RFC Editor: please replace the citation tags used in
230 referencing Internet-Drafts with tags of the form RFCnnnn.]]
234 7.1. Normative References
237 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
238 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
241 [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
242 draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.
245 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
246 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
249 [Models] Zeilenga, K. (editor), "LDAP: Directory Information
250 Models", draft-ietf-ldapbis-models-xx.txt, a work in
254 [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
255 Connection Level Security Mechanisms",
256 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
259 [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
260 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a
266 Zeilenga LDAP: TS Road Map [Page 4]
267 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
271 [Filters] Smith, M. (editor), LDAPbis WG, "LDAP: String
272 Representation of Search Filters",
273 draft-ietf-ldapbis-filter-xx.txt, a work in progress.
276 [LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
277 draft-ietf-ldapbis-url-xx.txt, a work in progress.
280 [Syntaxes] Legg, S. (editor), "LDAP: Syntaxes and Matching Rules",
281 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
284 [LDAPprep] Zeilenga, K., "LDAP: Internationalized String
285 Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work
289 [Schema] Dally, K. (editor), "LDAP: User Schema",
290 draft-ietf-ldapbis-user-schema-xx.txt, a work in
294 [X.500] International Telecommunication Union -
295 Telecommunication Standardization Sector, "The Directory
296 -- Overview of concepts, models and services,"
297 X.500(1993) (also ISO/IEC 9594-1:1994).
300 [X.501] International Telecommunication Union -
301 Telecommunication Standardization Sector, "The Directory
302 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
305 [X.511] International Telecommunication Union -
306 Telecommunication Standardization Sector, "The
307 Directory: Abstract Service Definition", X.511(1993)
308 (also ISO/IEC 9594-3:1993).
312 7.2. Informative References
319 Appendix A. Changes to Previous Documents
322 This appendix outlines changes this document makes relative to the
323 documents it replaces (in whole or in part).
327 Appendix A.1. Changes to RFC 3377
330 This document is nearly a complete rewrite of RFC 3377 as much of the
331 material of RFC 3377 is no longer applicable. The changes include
336 Zeilenga LDAP: TS Road Map [Page 5]
337 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
341 redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
342 the technical specification.
346 Appendix A.2. Changes to Section 3.3 of RFC 2251
349 The section was modified slightly (the word "document" was replaced
350 with "technical specification") to clarify that it applies to the
351 entire LDAP technical specification.
356 Intellectual Property Rights
359 The IETF takes no position regarding the validity or scope of any
360 Intellectual Property Rights or other rights that might be claimed to
361 pertain to the implementation or use of the technology described in
362 this document or the extent to which any license under such rights
363 might or might not be available; nor does it represent that it has
364 made any independent effort to identify any such rights. Information
365 on the procedures with respect to rights in RFC documents can be found
366 in BCP 78 and BCP 79.
369 Copies of IPR disclosures made to the IETF Secretariat and any
370 assurances of licenses to be made available, or the result of an
371 attempt made to obtain a general license or permission for the use of
372 such proprietary rights by implementers or users of this specification
373 can be obtained from the IETF on-line IPR repository at
374 http://www.ietf.org/ipr.
377 The IETF invites any interested party to bring to its attention any
378 copyrights, patents or patent applications, or other proprietary
379 rights that may cover technology that may be required to implement
380 this standard. Please address the information to the IETF at
389 Copyright (C) The Internet Society (2004). This document is subject
390 to the rights, licenses and restrictions contained in BCP 78, and
391 except as set forth therein, the authors retain all their rights.
394 This document and the information contained herein are provided on an
395 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
396 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
397 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
402 Zeilenga LDAP: TS Road Map [Page 6]
403 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-06 24 October 2004
407 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
408 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
409 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
458 Zeilenga LDAP: TS Road Map [Page 7]