6 INTERNET-DRAFT Editor: Kurt D. Zeilenga
7 Intended Category: Standard Track OpenLDAP Foundation
8 Expires in six months 10 February 2005
9 Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771
13 Lightweight Directory Access Protocol (LDAP):
14 Technical Specification Road Map
15 <draft-ietf-ldapbis-roadmap-07.txt>
21 This document is intended to be published as a Standard Track RFC.
22 Distribution of this memo is unlimited. Technical discussion of this
23 document will take place on the IETF LDAP Revision Working Group
24 mailing list <ietf-ldapbis@openldap.org>. Please send editorial
25 comments directly to the author <Kurt@OpenLDAP.org>.
27 By submitting this Internet-Draft, I accept the provisions of Section
28 4 of RFC 3667. By submitting this Internet-Draft, I certify that any
29 applicable patent or other IPR claims of which I am aware have been
30 disclosed, or will be disclosed, and any of which I become aware will
31 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.
37 Internet-Drafts are draft documents valid for a maximum of six months
38 and may be updated, replaced, or obsoleted by other documents at any
39 time. It is inappropriate to use Internet-Drafts as reference material
40 or to cite them other than as "work in progress."
42 The list of current Internet-Drafts can be accessed at
43 http://www.ietf.org/1id-abstracts.html
45 The list of Internet-Draft Shadow Directories can be accessed at
46 http://www.ietf.org/shadow.html
49 Copyright (C) The Internet Society (2005). All Rights Reserved.
51 Please see the Full Copyright section near the end of this document
57 Zeilenga LDAP: TS Road Map [Page 1]
59 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
64 The Lightweight Directory Access Protocol (LDAP) is an Internet
65 protocol for accessing distributed directory services which act in
66 accordance with X.500 data and service models. This document provides
67 a roadmap of the LDAP Technical Specification.
72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
74 document are to be interpreted as described in BCP 14 [RFC2119].
77 1. The LDAP Technical Specification
79 The technical specification detailing version 3 of the Lightweight
80 Directory Access Protocol (LDAP), an Internet Protocol, consists of
81 this document and the following documents:
83 LDAP: The Protocol [Protocol],
84 LDAP: Directory Information Models [Models],
85 LDAP: Authentication Methods and Connection Level Security
86 Mechanisms [AuthMeth],
87 LDAP: String Representation of Distinguished Names [LDAPDN],
88 LDAP: String Representation of Search Filters [Filters],
89 LDAP: Uniform Resource Locator [LDAPURL],
90 LDAP: Syntaxes and Matching Rules [Syntaxes],
91 LDAP: Internationalized String Preparation [LDAPprep], and
92 LDAP: User Schema [Schema].
94 The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
95 the protocol specified by this technical specification. The LDAP
96 suite, as defined here, should be formally identified in other
97 documents by a normative reference to this document.
99 LDAP is an extensible protocol. Extensions to LDAP may be specified
100 in other documents. Nomenclature denoting such combinations of
101 LDAP-plus-extension(s) is not defined by this document but may be
102 defined in some future document(s). Extensions are expected to be
105 IANA (Internet Assigned Numbers Authority) considerations for LDAP
106 described in BCP 64 [BCP64bis] apply fully to this revision of the
107 LDAP technical specification.
113 Zeilenga LDAP: TS Road Map [Page 2]
115 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
118 2. Relationship to X.500
120 This technical specification defines LDAP in terms of [X.500] as an
121 X.500 access mechanism. An LDAP server MUST act in accordance with
122 X.500(1993) series of International Telecommunication Union - Telecom
123 Standardization (ITU-T) Recommendations when providing the service.
124 However, it is not required that an LDAP server make use of any X.500
125 protocols in providing this service, e.g. LDAP can be mapped onto any
126 other directory system so long as the X.500 data and service models
127 [X.501][X.511] as used in LDAP is not violated in the LDAP interface.
129 This technical specification explicitly incorporates portions of
130 X.500(93). Later revisions of X.500 do not automatically apply to
131 this technical specification.
134 3. Security Considerations
136 LDAP security considerations are discussed in each document comprising
137 the technical specification.
140 4. Relationship to Obsolete Specifications
142 This technical specification, as defined in Section 1, obsoletes
143 entirely the previously defined LDAP technical specification [RFC3377]
144 (which consists of RFC 2251-2256, RFC 2829-2830, RFC 3771, and RFC
145 3377 itself). The technical specification was significantly
148 This document replaces RFC 3377 as well as Section 3.3 of RFC 2251.
149 [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
150 [Protocol] replaces the majority RFC 2251, portions of RFC 2252, and
151 all of RFC 3771. [AuthMeth] replaces RFC 2829, RFC 2830, and portions
152 of RFC 2251. [Syntaxes] replaces the majority of RFC 2252 and
153 portions of RFC 2256. [Schema] replaces the majority of RFC 2256.
154 [LDAPDN] replaces RFC 2253. [Filters] replaces RFC 2254. [LDAPURL]
157 [LDAPprep] is new to this revision of the LDAP technical
160 Each document of this specification contains appendices summarizing
161 changes to all sections of the specifications they replace. Appendix
162 A.1 of this document details changes made to RFC 3377. Appendix A.2
163 of this document details changes made to Section 3.3 of RFC 2251.
165 Additionally, portions of this technical specification update and/or
169 Zeilenga LDAP: TS Road Map [Page 3]
171 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
174 replace a number of other documents not listed above. These
175 relationships are discussed in the documents detailings these portions
176 of this technical specification.
181 This document is based largely on RFC 3377 by J. Hodges and R.
182 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
183 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
184 Kille, a product of the ASID Working Group.
186 This document is a product of the IETF LDAPBIS Working Group.
194 Email: Kurt@OpenLDAP.org
199 [[Note to the RFC Editor: please replace the citation tags used in
200 referencing Internet-Drafts with tags of the form RFCnnnn where
204 7.1. Normative References
206 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
207 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
209 [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
210 draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.
212 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
213 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
215 [Models] Zeilenga, K. (editor), "LDAP: Directory Information
216 Models", draft-ietf-ldapbis-models-xx.txt, a work in
219 [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
220 Connection Level Security Mechanisms",
221 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
225 Zeilenga LDAP: TS Road Map [Page 4]
227 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
230 [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
231 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a
234 [Filters] Smith, M. (editor), LDAPbis WG, "LDAP: String
235 Representation of Search Filters",
236 draft-ietf-ldapbis-filter-xx.txt, a work in progress.
238 [LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
239 draft-ietf-ldapbis-url-xx.txt, a work in progress.
241 [Syntaxes] Legg, S. (editor), "LDAP: Syntaxes and Matching Rules",
242 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
244 [LDAPprep] Zeilenga, K., "LDAP: Internationalized String
245 Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work
248 [Schema] Dally, K. (editor), "LDAP: User Schema",
249 draft-ietf-ldapbis-user-schema-xx.txt, a work in
252 [X.500] International Telecommunication Union -
253 Telecommunication Standardization Sector, "The Directory
254 -- Overview of concepts, models and services,"
255 X.500(1993) (also ISO/IEC 9594-1:1994).
257 [X.501] International Telecommunication Union -
258 Telecommunication Standardization Sector, "The Directory
259 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
261 [X.511] International Telecommunication Union -
262 Telecommunication Standardization Sector, "The
263 Directory: Abstract Service Definition", X.511(1993)
264 (also ISO/IEC 9594-3:1993).
267 7.2. Informative References
272 Appendix A. Changes to Previous Documents
274 This appendix outlines changes this document makes relative to the
275 documents it replaces (in whole or in part).
281 Zeilenga LDAP: TS Road Map [Page 5]
283 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
286 Appendix A.1. Changes to RFC 3377
288 This document is nearly a complete rewrite of RFC 3377 as much of the
289 material of RFC 3377 is no longer applicable. The changes include
290 redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
291 the technical specification.
294 Appendix A.2. Changes to Section 3.3 of RFC 2251
296 The section was modified slightly (the word "document" was replaced
297 with "technical specification") to clarify that it applies to the
298 entire LDAP technical specification.
302 Intellectual Property Rights
304 The IETF takes no position regarding the validity or scope of any
305 Intellectual Property Rights or other rights that might be claimed to
306 pertain to the implementation or use of the technology described in
307 this document or the extent to which any license under such rights
308 might or might not be available; nor does it represent that it has
309 made any independent effort to identify any such rights. Information
310 on the procedures with respect to rights in RFC documents can be found
311 in BCP 78 and BCP 79.
313 Copies of IPR disclosures made to the IETF Secretariat and any
314 assurances of licenses to be made available, or the result of an
315 attempt made to obtain a general license or permission for the use of
316 such proprietary rights by implementers or users of this specification
317 can be obtained from the IETF on-line IPR repository at
318 http://www.ietf.org/ipr.
320 The IETF invites any interested party to bring to its attention any
321 copyrights, patents or patent applications, or other proprietary
322 rights that may cover technology that may be required to implement
323 this standard. Please address the information to the IETF at
330 Copyright (C) The Internet Society (2005). This document is subject
331 to the rights, licenses and restrictions contained in BCP 78, and
332 except as set forth therein, the authors retain all their rights.
337 Zeilenga LDAP: TS Road Map [Page 6]
339 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-07 10 February 2005
342 This document and the information contained herein are provided on an
343 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
344 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
345 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
346 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
347 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
348 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
393 Zeilenga LDAP: TS Road Map [Page 7]