1 2 3 4 5 6 7 Network Working Group K. Zeilenga, Ed. 8 Request for Comments: 4510 OpenLDAP Foundation 9 Obsoletes: 2251, 2252, 2253, 2254, 2255, June 2006 10 2256, 2829, 2830, 3377, 3771 11 Category: Standards Track 12 13 14 Lightweight Directory Access Protocol (LDAP): 15 Technical Specification Road Map 16 17 Status of This Memo 18 19 This document specifies an Internet standards track protocol for the 20 Internet community, and requests discussion and suggestions for 21 improvements. Please refer to the current edition of the "Internet 22 Official Protocol Standards" (STD 1) for the standardization state 23 and status of this protocol. Distribution of this memo is unlimited. 24 25 Copyright Notice 26 27 Copyright (C) The Internet Society (2006). 28 29 Abstract 30 31 The Lightweight Directory Access Protocol (LDAP) is an Internet 32 protocol for accessing distributed directory services that act in 33 accordance with X.500 data and service models. This document 34 provides a road map of the LDAP Technical Specification. 35 36 1. The LDAP Technical Specification 37 38 The technical specification detailing version 3 of the Lightweight 39 Directory Access Protocol (LDAP), an Internet Protocol, consists of 40 this document and the following documents: 41 42 LDAP: The Protocol [RFC4511] 43 LDAP: Directory Information Models [RFC4512] 44 LDAP: Authentication Methods and Security Mechanisms [RFC4513] 45 LDAP: String Representation of Distinguished Names [RFC4514] 46 LDAP: String Representation of Search Filters [RFC4515] 47 LDAP: Uniform Resource Locator [RFC4516] 48 LDAP: Syntaxes and Matching Rules [RFC4517] 49 LDAP: Internationalized String Preparation [RFC4518] 50 LDAP: Schema for User Applications [RFC4519] 51 52 53 54 55 56 57 58 Zeilenga Standards Track [Page 1] 59 61 RFC 4510 LDAP: TS Road Map June 2006 62 63 64 The terms "LDAP" and "LDAPv3" are commonly used to refer informally 65 to the protocol specified by this technical specification. The LDAP 66 suite, as defined here, should be formally identified in other 67 documents by a normative reference to this document. 68 69 LDAP is an extensible protocol. Extensions to LDAP may be specified 70 in other documents. Nomenclature denoting such combinations of 71 LDAP-plus-extensions is not defined by this document but may be 72 defined in some future document(s). Extensions are expected to be 73 truly optional. Considerations for the LDAP extensions described in 74 BCP 118, RFC 4521 [RFC4521] fully apply to this revision of the LDAP 75 Technical Specification. 76 77 IANA (Internet Assigned Numbers Authority) considerations for LDAP 78 described in BCP 64, RFC 4520 [RFC4520] apply fully to this revision 79 of the LDAP technical specification. 80 81 1.1. Conventions 82 83 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 84 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 85 document are to be interpreted as described in BCP 14 [RFC2119]. 86 87 2. Relationship to X.500 88 89 This technical specification defines LDAP in terms of [X.500] as an 90 X.500 access mechanism. An LDAP server MUST act in accordance with 91 the X.500 (1993) series of International Telecommunication Union - 92 Telecommunication Standardization (ITU-T) Recommendations when 93 providing the service. However, it is not required that an LDAP 94 server make use of any X.500 protocols in providing this service. 95 For example, LDAP can be mapped onto any other directory system so 96 long as the X.500 data and service models [X.501][X.511], as used in 97 LDAP, are not violated in the LDAP interface. 98 99 This technical specification explicitly incorporates portions of 100 X.500(93). Later revisions of X.500 do not automatically apply to 101 this technical specification. 102 103 3. Relationship to Obsolete Specifications 104 105 This technical specification, as defined in Section 1, obsoletes 106 entirely the previously defined LDAP technical specification defined 107 in RFC 3377 (and consisting of RFCs 2251-2256, 2829, 2830, 3771, and 108 3377 itself). The technical specification was significantly 109 reorganized. 110 111 112 113 114 115 Zeilenga Standards Track [Page 2] 116 118 RFC 4510 LDAP: TS Road Map June 2006 119 120 121 This document replaces RFC 3377 as well as Section 3.3 of RFC 2251. 122 [RFC4512] replaces portions of RFC 2251, RFC 2252, and RFC 2256. 123 [RFC4511] replaces the majority RFC 2251, portions of RFC 2252, and 124 all of RFC 3771. [RFC4513] replaces RFC 2829, RFC 2830, and portions 125 of RFC 2251. [RFC4517] replaces the majority of RFC 2252 and 126 portions of RFC 2256. [RFC4519] replaces the majority of RFC 2256. 127 [RFC4514] replaces RFC 2253. [RFC4515] replaces RFC 2254. [RFC4516] 128 replaces RFC 2255. 129 130 [RFC4518] is new to this revision of the LDAP technical 131 specification. 132 133 Each document of this specification contains appendices summarizing 134 changes to all sections of the specifications they replace. Appendix 135 A.1 of this document details changes made to RFC 3377. Appendix A.2 136 of this document details changes made to Section 3.3 of RFC 2251. 137 138 Additionally, portions of this technical specification update and/or 139 replace a number of other documents not listed above. These 140 relationships are discussed in the documents detailing these portions 141 of this technical specification. 142 143 4. Security Considerations 144 145 LDAP security considerations are discussed in each document 146 comprising the technical specification. 147 148 5. Acknowledgements 149 150 This document is based largely on RFC 3377 by J. Hodges and R. 151 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The 152 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S. 153 Kille, a product of the ASID Working Group. 154 155 This document is a product of the IETF LDAPBIS Working Group. 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 Zeilenga Standards Track [Page 3] 173 175 RFC 4510 LDAP: TS Road Map June 2006 176 177 178 6. Normative References 179 180 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 181 Requirement Levels", BCP 14, RFC 2119, March 1997. 182 183 [RFC4511] Sermersheim, J., Ed., "Lightweight Directory Access 184 Protocol (LDAP): The Protocol", RFC 4511, June 2006. 185 186 [RFC4512] Zeilenga, K., "Lightweight Directory Access Protocol 187 (LDAP): Directory Information Models", RFC 4512, June 188 2006. 189 190 [RFC4513] Harrison, R., Ed., "Lightweight Directory Access 191 Protocol (LDAP): Authentication Methods and Security 192 Mechanisms", RFC 4513, June 2006. 193 194 [RFC4514] Zeilenga, K., Ed., "Lightweight Directory Access 195 Protocol (LDAP): String Representation of Distinguished 196 Names", RFC 4514, June 2006. 197 198 [RFC4515] Smith, M., Ed. and T. Howes, "Lightweight Directory 199 Access Protocol (LDAP): String Representation of Search 200 Filters", RFC 4515, June 2006. 201 202 [RFC4516] Smith, M., Ed. and T. Howes, "Lightweight Directory 203 Access Protocol (LDAP): Uniform Resource Locator", RFC 204 4516, June 2006. 205 206 [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol 207 (LDAP): Syntaxes and Matching Rules", RFC 4517, June 208 2006. 209 210 [RFC4518] Zeilenga, K., "Lightweight Directory Access Protocol 211 (LDAP): Internationalized String Preparation", RFC 212 4518, June 2006. 213 214 [RFC4519] Sciberras, A., Ed., "Lightweight Directory Access 215 Protocol (LDAP): Schema for User Applications", RFC 216 4519, June 2006. 217 218 [RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority 219 (IANA) Considerations for the Lightweight Directory 220 Access Protocol (LDAP)", BCP 64, RFC 4520, June 2006. 221 222 [RFC4521] Zeilenga, K., "Considerations for LDAP Extensions", BCP 223 118, RFC 4521, June 2006. 224 225 226 227 228 229 Zeilenga Standards Track [Page 4] 230 232 RFC 4510 LDAP: TS Road Map June 2006 233 234 235 [X.500] International Telecommunication Union - 236 Telecommunication Standardization Sector, "The 237 Directory -- Overview of concepts, models and 238 services", X.500(1993) (also ISO/IEC 9594-1:1994). 239 240 [X.501] International Telecommunication Union - 241 Telecommunication Standardization Sector, "The 242 Directory -- Models", X.501(1993) (also ISO/IEC 9594- 243 2:1994). 244 245 [X.511] International Telecommunication Union - 246 Telecommunication Standardization Sector, "The 247 Directory: Abstract Service Definition", X.511(1993) 248 (also ISO/IEC 9594-3:1993). 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 Zeilenga Standards Track [Page 5] 287 289 RFC 4510 LDAP: TS Road Map June 2006 290 291 292 Appendix A. Changes to Previous Documents 293 294 This appendix outlines changes this document makes relative to the 295 documents it replaces (in whole or in part). 296 297 A.1. Changes to RFC 3377 298 299 This document is nearly a complete rewrite of RFC 3377 as much of the 300 material of RFC 3377 is no longer applicable. The changes include 301 redefining the terms "LDAP" and "LDAPv3" to refer to this revision of 302 the technical specification. 303 304 A.2. Changes to Section 3.3 of RFC 2251 305 306 The section was modified slightly (the word "document" was replaced 307 with "technical specification") to clarify that it applies to the 308 entire LDAP technical specification. 309 310 Author's Address 311 312 Kurt D. Zeilenga 313 OpenLDAP Foundation 314 315 EMail: Kurt (a] OpenLDAP.org 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 Zeilenga Standards Track [Page 6] 344 346 RFC 4510 LDAP: TS Road Map June 2006 347 348 349 Full Copyright Statement 350 351 Copyright (C) The Internet Society (2006). 352 353 This document is subject to the rights, licenses and restrictions 354 contained in BCP 78, and except as set forth therein, the authors 355 retain all their rights. 356 357 This document and the information contained herein are provided on an 358 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 359 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 360 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 361 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 362 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 363 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 364 365 Intellectual Property 366 367 The IETF takes no position regarding the validity or scope of any 368 Intellectual Property Rights or other rights that might be claimed to 369 pertain to the implementation or use of the technology described in 370 this document or the extent to which any license under such rights 371 might or might not be available; nor does it represent that it has 372 made any independent effort to identify any such rights. Information 373 on the procedures with respect to rights in RFC documents can be 374 found in BCP 78 and BCP 79. 375 376 Copies of IPR disclosures made to the IETF Secretariat and any 377 assurances of licenses to be made available, or the result of an 378 attempt made to obtain a general license or permission for the use of 379 such proprietary rights by implementers or users of this 380 specification can be obtained from the IETF on-line IPR repository at 381 http://www.ietf.org/ipr. 382 383 The IETF invites any interested party to bring to its attention any 384 copyrights, patents or patent applications, or other proprietary 385 rights that may cover technology that may be required to implement 386 this standard. Please address the information to the IETF at 387 ietf-ipr (a] ietf.org. 388 389 Acknowledgement 390 391 Funding for the RFC Editor function is provided by the IETF 392 Administrative Support Activity (IASA). 393 394 395 396 397 398 399 400 Zeilenga Standards Track [Page 7] 401 403
Indexes created Mon Sep 14 00:24:24 UTC 2026