7 INTERNET-DRAFT Editor: Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 15 February 2004
10 Obsoletes: RFC 2251-2256, 2829-2830, 3377
14 Lightweight Directory Access Protocol (LDAP):
15 Technical Specification Road Map
16 <draft-ietf-ldapbis-roadmap-04.txt>
21 This document is an Internet-Draft and is in full conformance with all
22 provisions of Section 10 of RFC2026.
24 This document is intended to be published as a Standard Track RFC.
25 Distribution of this memo is unlimited. Technical discussion of this
26 document will take place on the IETF LDAP Revision Working Group
27 mailing list <ietf-ldapbis@openldap.org>. Please send editorial
28 comments directly to the author <Kurt@OpenLDAP.org>.
30 Internet-Drafts are working documents of the Internet Engineering Task
31 Force (IETF), its areas, and its working groups. Note that other
32 groups may also distribute working documents as Internet-Drafts.
33 Internet-Drafts are draft documents valid for a maximum of six months
34 and may be updated, replaced, or obsoleted by other documents at any
35 time. It is inappropriate to use Internet-Drafts as reference
36 material or to cite them other than as ``work in progress.''
38 The list of current Internet-Drafts can be accessed at
39 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
40 Internet-Draft Shadow Directories can be accessed at
41 <http://www.ietf.org/shadow.html>.
43 Copyright (C) The Internet Society (2004). All Rights Reserved.
45 Please see the Full Copyright section near the end of this document
51 The Lightweight Directory Access Protocol (LDAP) is an Internet
52 protocol for accessing distributed directory services which act in
53 accordance with X.500 data and service models. This document provides
54 a roadmap of the LDAP Technical Specification.
58 Zeilenga LDAP: TS Road Map [Page 1]
60 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-04 15 February 2004
65 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
66 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
67 document are to be interpreted as described in BCP 14 [RFC2119].
70 1. The LDAP Technical Specification
72 The technical specification detailing version 3 of the Lightweight
73 Directory Access Protocol (LDAP), an Internet Protocol, consists of
74 this document and the following documents:
76 LDAP: The Protocol [Protocol],
77 LDAP: Directory Information Models [Models],
78 LDAP: Authentication Methods and Connection Level Security
79 Mechanisms [AuthMeth],
80 LDAP: String Representation of Distinguished Names [LDAPDN],
81 LDAP: String Representation of Search Filters [Filters],
82 LDAP: Uniform Resource Locator [LDAPURL],
83 LDAP: Syntaxes and Matching Rules [Syntaxes],
84 LDAP: Internationalized String Preparation [LDAPprep], and
85 LDAP: User Schema [Schema].
87 The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
88 the protocol specified by this technical specification. The LDAP
89 suite, as defined here, should be formally identified in other
90 documents by a normative reference to this document.
92 Extensions to LDAP may be specified in other documents. Nomenclature
93 denoting such combinations of LDAP-plus-extension(s) is not defined by
94 this document but may be defined in some future document(s).
96 IANA (Internet Assigned Numbers Authority) considerations for LDAP
97 described in BCP 64 [BCP64bis] apply fully to this revision of the
98 LDAP technical specification.
101 2. Relationship to X.500
103 This technical specification defines LDAP in terms of [X.500] as an
104 X.500 access mechanism. An LDAP server MUST act in accordance with
105 X.500(1993) series of International Telecommunication Union - Telecom
106 Standardization (ITU-T) Recommendations when providing the service.
107 However, it is not required that an LDAP server make use of any X.500
108 protocols in providing this service, e.g. LDAP can be mapped onto any
109 other directory system so long as the X.500 data and service models
110 [X.501][X.511] as used in LDAP is not violated in the LDAP interface.
114 Zeilenga LDAP: TS Road Map [Page 2]
116 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-04 15 February 2004
119 This technical specification explicitly incorporates portions of
120 X.500(93). Later revisions of X.500 do not automatically apply.
123 3. Security Considerations
125 LDAP security considerations are discussed in each document comprising
126 the technical specification.
129 4. Relationship to Obsolete Specifications
131 This technical specification, as defined in Section 1, obsoletes
132 entirely the previously defined LDAP technical specification [RFC3377]
133 (which consists of RFC 2251-2256, RFC 2829-2830 and RFC 3377 itself).
134 The technical specification was significantly reorganized.
136 This document replaces RFC 3377 as well as Section 3.3 of RFC 2251.
137 [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
138 [Protocol] replaces the majority RFC 2251 and portions of RFC 2252.
139 [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251.
140 [Syntaxes] replaces the majority of RFC 2252 and portions of RFC 2256.
141 [Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC
142 2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255.
144 [LDAPprep] is new to this revision of the LDAP technical
147 Each document of this specification contains appendices summarizing
148 changes to all sections of the specifications they replace. Appendix
149 A.1 of this document details changes made to RFC 3377. Appendix A.2
150 of this document details changes made to Section 3.3 of RFC 2251.
152 Additionally, portions of this technical specification update and/or
153 replace documents not listed above. These relationships are discussed
154 in the documents detailings these portions of this technical
160 This document is based largely on RFC 3377 by J. Hodges and R.
161 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
162 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
163 Kille, a product of the ASID Working Group.
165 This document is a product of the IETF LDAPBIS Working Group.
170 Zeilenga LDAP: TS Road Map [Page 3]
172 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-04 15 February 2004
178 E-mail: <kurt@openldap.org>
183 7.1. Normative References
185 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
186 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
188 [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP", draft-
189 ietf-ldapbis-bcp64-xx.txt, a work in progress.
191 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
192 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
194 [Models] Zeilenga, K. (editor), "LDAP: Directory Information
195 Models", draft-ietf-ldapbis-models-xx.txt, a work in
198 [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
199 Connection Level Security Mechanisms",
200 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
202 [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
203 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a
206 [Filters] Smith, M. (editor), LDAPbis WG, "LDAP: String
207 Representation of Search Filters",
208 draft-ietf-ldapbis-filter-xx.txt, a work in progress.
210 [LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
211 draft-ietf-ldapbis-url-xx.txt, a work in progress.
213 [Syntaxes] Legg, S. (editor), "LDAP: Syntaxes and Matching Rules",
214 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
216 [LDAPprep] Zeilenga, K., "LDAP: Internationalized String
217 Preparation", draft-ietf-ldapbis-strprep-xx.txt, a work
220 [Schema] Dally, K. (editor), "LDAP: User Schema",
221 draft-ietf-ldapbis-user-schema-xx.txt, a work in
226 Zeilenga LDAP: TS Road Map [Page 4]
228 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-04 15 February 2004
231 [X.500] International Telecommunication Union -
232 Telecommunication Standardization Sector, "The Directory
233 -- Overview of concepts, models and services,"
234 X.500(1993) (also ISO/IEC 9594-1:1994).
236 [X.501] International Telecommunication Union -
237 Telecommunication Standardization Sector, "The Directory
238 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
240 [X.511] International Telecommunication Union -
241 Telecommunication Standardization Sector, "The
242 Directory: Abstract Service Definition", X.511(1993).
245 7.2. Informative References
250 Appendix A. Changes to Previous Documents
252 This appendix outlines changes this document makes relative to the
253 documents it replaces (in whole or in part).
256 Appendix A.1. Changes to RFC 3377
258 This document is nearly a complete rewrite of RFC 3377 as much of the
259 material of RFC 3377 is no longer applicable. The changes include
260 redefining the terms "LDAP" and "LDAPv3" to refer to this revision of
261 the technical specification.
264 Appendix A.2. Changes to Section 3.3 of RFC 2251
266 The section was modified slightly (the word "document" was replaced
267 with "technical specification") to clarify that it applies to the
268 entire LDAP technical specification.
272 Intellectual Property Rights
274 The IETF takes no position regarding the validity or scope of any
275 intellectual property or other rights that might be claimed to pertain
276 to the implementation or use of the technology described in this
277 document or the extent to which any license under such rights might or
278 might not be available; neither does it represent that it has made any
282 Zeilenga LDAP: TS Road Map [Page 5]
284 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-04 15 February 2004
287 effort to identify any such rights. Information on the IETF's
288 procedures with respect to rights in standards-track and
289 standards-related documentation can be found in BCP-11. Copies of
290 claims of rights made available for publication and any assurances of
291 licenses to be made available, or the result of an attempt made to
292 obtain a general license or permission for the use of such proprietary
293 rights by implementors or users of this specification can be obtained
294 from the IETF Secretariat.
296 The IETF invites any interested party to bring to its attention any
297 copyrights, patents or patent applications, or other proprietary
298 rights which may cover technology that may be required to practice
299 this standard. Please address the information to the IETF Executive
306 Copyright (C) The Internet Society (2004). All Rights Reserved.
308 This document and translations of it may be copied and furnished to
309 others, and derivative works that comment on or otherwise explain it
310 or assist in its implementation may be prepared, copied, published and
311 distributed, in whole or in part, without restriction of any kind,
312 provided that the above copyright notice and this paragraph are
313 included on all such copies and derivative works. However, this
314 document itself may not be modified in any way, such as by removing
315 the copyright notice or references to the Internet Society or other
316 Internet organizations, except as needed for the purpose of
317 developing Internet standards in which case the procedures for
318 copyrights defined in the Internet Standards process must be followed,
319 or as required to translate it into languages other than English.
338 Zeilenga LDAP: TS Road Map [Page 6]