7 INTERNET-DRAFT Editor: Kurt D. Zeilenga
8 Intended Category: Standard Track OpenLDAP Foundation
9 Expires in six months 1 March 2003
10 Obsoletes: RFC 2251-2256, 2829-2830, 3377
14 LDAP: Technical Specification Road Map
15 <draft-ietf-ldapbis-roadmap-02.txt>
20 This document is an Internet-Draft and is in full conformance with all
21 provisions of Section 10 of RFC2026.
23 This document is intended to be published as a Standard Track RFC.
24 Distribution of this memo is unlimited. Technical discussion of this
25 document will take place on the IETF LDAP Revision Working Group
26 mailing list <ietf-ldapbis@openldap.org>. Please send editorial
27 comments directly to the author <Kurt@OpenLDAP.org>.
29 Internet-Drafts are working documents of the Internet Engineering Task
30 Force (IETF), its areas, and its working groups. Note that other
31 groups may also distribute working documents as Internet-Drafts.
32 Internet-Drafts are draft documents valid for a maximum of six months
33 and may be updated, replaced, or obsoleted by other documents at any
34 time. It is inappropriate to use Internet-Drafts as reference
35 material or to cite them other than as ``work in progress.''
37 The list of current Internet-Drafts can be accessed at
38 <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
39 Internet-Draft Shadow Directories can be accessed at
40 <http://www.ietf.org/shadow.html>.
42 Copyright 2003, The Internet Society. All Rights Reserved.
44 Please see the Copyright section near the end of this document for
50 The Lightweight Directory Access Protocol (LDAP) is an Internet
51 protocol for accessing distributed directory services which act in
52 accordance with X.500 data and service models. This document provides
53 a roadmap of the LDAP Technical Specification.
58 Zeilenga LDAP: TS Road Map [Page 1]
60 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-02 1 March 2003
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: Directory Information Models [Models],
77 LDAP: The Protocol [Protocol],
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 [Syntaxes], and
84 LDAP: User Schema [Schema].
86 The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
87 the protocol specified by this technical specification. The LDAP
88 suite, as defined here, should be formally identified in other
89 documents by a normative reference to this document.
91 Extensions to LDAP may be specified in other documents. Nomenclature
92 denoting such combinations of LDAP-plus-extension(s) is not defined by
93 this document but may be defined in some future document(s).
95 IANA (Internet Assigned Numbers Authority) considerations for LDAP
96 described in BCP 64 [RFC3383] apply fully to this revision of the LDAP
97 technical specification.
100 2. Relationship to X.500
102 This technical specification defines LDAP in terms of [X.500] as an
103 X.500 access mechanism. An LDAP server MUST act in accordance with
104 X.500(1993) series of International Telephone Union (ITU)
105 Recommendations when providing the service. However, it is not
106 required that an LDAP server make use of any X.500 protocols in
107 providing this service, e.g. LDAP can be mapped onto any other
108 directory system so long as the X.500 data and service models
109 [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-02 1 March 2003
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 [RFC3377] 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 [Syntax] 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 Each document of this specification contains appendices summarizing
145 changes to all sections of the specifications they replace. Appendix
146 A.1 of this document details changes made to RFC 3377. Appendix A.2
147 of this document details changes made to Section 3.3 of RFC 2251.
152 This document is based largely on RFC 3377 by J. Hodges and R.
153 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
154 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
155 Kille, a product of the ASID Working Group.
157 This document is a product of the IETF LDAPBIS Working Group.
163 E-mail: <kurt@openldap.org>
170 Zeilenga LDAP: TS Road Map [Page 3]
172 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-02 1 March 2003
175 7.1. Normative References
177 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
178 Requirement Levels", BCP 14 (also RFC 2119), March 1997.
180 [RFC3383] K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also
181 RFC 3383), September 2002.
183 [Models] K. Zeilenga (editor), "LDAP: Directory Information Models",
184 draft-ietf-ldapbis-models-xx.txt, a work in progress.
186 [Protocol] J. Sermersheim (editor), "LDAP: The Protocol",
187 draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
189 [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods and
190 Connection Level Security Mechanisms",
191 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
193 [LDAPDN] K. Zeilenga (editor), "LDAP: String Representation of
194 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
197 [Filters] M. Smith (editor), LDAPbis WG, "LDAP: String Representation
198 of Search Filters", draft-ietf-ldapbis-filter-xx.txt, a
201 [LDAPURL] M. Smith (editor), "LDAP: Uniform Resource Locator",
202 draft-ietf-ldapbis-url-xx.txt, a work in progress.
204 [Syntaxes] S. Legg (editor), "LDAP: Syntaxes",
205 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
207 [Schema] K. Dally (editor), "LDAP: User Schema",
208 draft-ietf-ldapbis-user-schema-xx.txt, a work in progress.
210 [X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts,
211 Models and Service", 1993.
213 [X.501] ITU-T Rec. X.501, "The Directory: Models", 1993.
215 [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service
219 7.2. Informative References
226 Zeilenga LDAP: TS Road Map [Page 4]
228 INTERNET-DRAFT draft-ietf-ldapbis-roadmap-02 1 March 2003
231 Appendix A. Changes to Previous Documents
233 This appendix outlines changes this document makes relative
234 to the documents it replaces (in whole or in part).
237 Appendix A.1. Changes to RFC 3377
239 This document is nearly a complete rewrite of RFC 3377 as
240 much of the material of RFC 3377 is no longer applicable.
241 These changes include defining the terms "LDAP" and
242 "LDAPv3" to refer to this revision of the technical
246 Appendix A.2. Changes to Section 3.3 of RFC 2251
248 The section was modified slightly (the word "document" was
249 replaced with "technical specification") to clarify that it
250 applies to the entire LDAP technical specification.
253 Copyright 2003, The Internet Society. All Rights Reserved.
255 This document and translations of it may be copied and furnished to
256 others, and derivative works that comment on or otherwise explain it
257 or assist in its implementation may be prepared, copied, published and
258 distributed, in whole or in part, without restriction of any kind,
259 provided that the above copyright notice and this paragraph are
260 included on all such copies and derivative works. However, this
261 document itself may not be modified in any way, such as by removing
262 the copyright notice or references to the Internet Society or other
263 Internet organizations, except as needed for the purpose of
264 developing Internet standards in which case the procedures for
265 copyrights defined in the Internet Standards process must be followed,
266 or as required to translate it into languages other than English.
268 The limited permissions granted above are perpetual and will not be
269 revoked by the Internet Society or its successors or assigns.
271 This document and the information contained herein is provided on an
272 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET
273 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
274 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
275 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
276 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
282 Zeilenga LDAP: TS Road Map [Page 5]