draft-ietf-ldapbis-roadmap-01.txt   draft-ietf-ldapbis-roadmap-02.txt 
INTERNET-DRAFT Editor: Kurt D. Zeilenga INTERNET-DRAFT Editor: Kurt D. Zeilenga
Intended Category: Standard Track OpenLDAP Foundation Intended Category: Standard Track OpenLDAP Foundation
Expires in six months 4 November 2002 Expires in six months 1 March 2003
Obsoletes: RFC 2251-2256, 2829-2830, 3377 Obsoletes: RFC 2251-2256, 2829-2830, 3377
LDAP: Technical Specification Road Map LDAP: Technical Specification Road Map
<draft-ietf-ldapbis-roadmap-01.txt> <draft-ietf-ldapbis-roadmap-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
This document is intended to be published as a Standard Track RFC. This document is intended to be published as a Standard Track RFC.
Distribution of this memo is unlimited. Technical discussion of this Distribution of this memo is unlimited. Technical discussion of this
document will take place on the IETF LDAP Revision Working Group document will take place on the IETF LDAP Revision Working Group
mailing list <ietf-ldapbis@openldap.org>. Please send editorial mailing list <ietf-ldapbis@openldap.org>. Please send editorial
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. The list of <http://www.ietf.org/ietf/1id-abstracts.txt>. The list of
Internet-Draft Shadow Directories can be accessed at Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. <http://www.ietf.org/shadow.html>.
Copyright 2002, The Internet Society. All Rights Reserved. Copyright 2003, The Internet Society. All Rights Reserved.
Please see the Copyright section near the end of this document for Please see the Copyright section near the end of this document for
more information. more information.
Abstract Abstract
The Lightweight Directory Access Protocol (LDAP) is an Internet The Lightweight Directory Access Protocol (LDAP) is an Internet
protocol for accessing distributed directory services which act in protocol for accessing distributed directory services which act in
accordance with X.500 data and service models. This document provides accordance with X.500 data and service models. This document provides
a roadmap of the LDAP Technical Specification. a roadmap of the LDAP Technical Specification.
skipping to change at page 3, line 5 skipping to change at page 3, line 5
This technical specification defines LDAP in terms of [X.500] as an This technical specification defines LDAP in terms of [X.500] as an
X.500 access mechanism. An LDAP server MUST act in accordance with X.500 access mechanism. An LDAP server MUST act in accordance with
X.500(1993) series of International Telephone Union (ITU) X.500(1993) series of International Telephone Union (ITU)
Recommendations when providing the service. However, it is not Recommendations when providing the service. However, it is not
required that an LDAP server make use of any X.500 protocols in required that an LDAP server make use of any X.500 protocols in
providing this service, e.g. LDAP can be mapped onto any other providing this service, e.g. LDAP can be mapped onto any other
directory system so long as the X.500 data and service models directory system so long as the X.500 data and service models
[X.501][X.511] as used in LDAP is not violated in the LDAP interface. [X.501][X.511] as used in LDAP is not violated in the LDAP interface.
This technical specification explicitly incorporates portions of
X.500(93). Later revisions of X.500 do not automatically apply.
3. Security Considerations 3. Security Considerations
LDAP security considerations are discussed in each document comprising LDAP security considerations are discussed in each document comprising
the technical specification. the technical specification.
4. Relationship to Obsolete Specifications 4. Relationship to Obsolete Specifications
This technical specification, as defined in Section 1, obsoletes This technical specification, as defined in Section 1, obsoletes
entirely the previously defined LDAP technical specification [RFC3377] entirely the previously defined LDAP technical specification [RFC3377]
(which consists of RFC 2251-2256, RFC 2829-2830 and [RFC3377] itself). (which consists of RFC 2251-2256, RFC 2829-2830 and [RFC3377] itself).
The technical specification was significantly reorganized. The technical specification was significantly reorganized.
This document replaces RFC 3377 as well as Section 3.3 of RFC 2251. This document replaces RFC 3377 as well as Section 3.3 of RFC 2251.
[Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256. [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256.
[Protocol] replaces the majority RFC 2251 and portions of RFC 2252. [Protocol] replaces the majority RFC 2251 and portions of RFC 2252.
[AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251. [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251.
[Syntax] replaces the majority of RFC 2252 and portions of RFC 2256. [Syntax] replaces the majority of RFC 2252 and portions of RFC 2256.
[Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC [Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC
2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255. 2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255.
Each document of this specification contains appendices detailing Each document of this specification contains appendices summarizing
changes to all sections of the specifications they replace. Appendix changes to all sections of the specifications they replace. Appendix
A.1 of this document details changes made to RFC 3377. Appendix A.2 A.1 of this document details changes made to RFC 3377. Appendix A.2
of this document details changes made to Section 3.3 of RFC 2251. of this document details changes made to Section 3.3 of RFC 2251.
5. Acknowledgments 5. Acknowledgments
This document is based largely on RFC 3377 by J. Hodges and R. This document is based largely on RFC 3377 by J. Hodges and R.
Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The
document also borrows from RFC 2251 by M. Wahl, T. Howes, and S. document also borrows from RFC 2251 by M. Wahl, T. Howes, and S.
Kille, a product of the ASID Working Group. Kille, a product of the ASID Working Group.
This document is a product of the IETF LDAPBIS Working Group.
6. Author's Address 6. Author's Address
Kurt Zeilenga Kurt Zeilenga
E-mail: <kurt@openldap.org> E-mail: <kurt@openldap.org>
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
skipping to change at page 4, line 49 skipping to change at page 5, line 7
[X.511] ITU-T Rec. X.511, "The Directory: Abstract Service [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service
Definition", 1993. Definition", 1993.
7.2. Informative References 7.2. Informative References
None. None.
Appendix A. Changes to Previous Documents Appendix A. Changes to Previous Documents
This appendix outlines changes this document makes relative to the This appendix outlines changes this document makes relative
documents it replaces (in whole or in part). to the documents it replaces (in whole or in part).
Appendix A.1. Changes to RFC 3377 Appendix A.1. Changes to RFC 3377
This document is nearly a complete rewrite of RFC 3377 as much of the This document is nearly a complete rewrite of RFC 3377 as
material of RFC 3377 is no longer applicable. These changes include much of the material of RFC 3377 is no longer applicable.
defining the terms "LDAP" and "LDAPv3" to refer to this revision of These changes include defining the terms "LDAP" and
the technical specification. "LDAPv3" to refer to this revision of the technical
specification.
Appendix A.2. Changes to Section 3.3 of RFC 2251 Appendix A.2. Changes to Section 3.3 of RFC 2251
The section was modified slightly (the word "document" was replaced The section was modified slightly (the word "document" was
with "technical specification") to clarify that it applies to the replaced with "technical specification") to clarify that it
entire LDAP technical specification. applies to the entire LDAP technical specification.
Copyright 2002, The Internet Society. All Rights Reserved. Copyright 2003, The Internet Society. All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/