draft-ietf-ldapbis-roadmap-04.txt   draft-ietf-ldapbis-roadmap-05.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 15 February 2004 Expires in six months 4 June 2004
Obsoletes: RFC 2251-2256, 2829-2830, 3377 Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771
Lightweight Directory Access Protocol (LDAP): Lightweight Directory Access Protocol (LDAP):
Technical Specification Road Map Technical Specification Road Map
<draft-ietf-ldapbis-roadmap-04.txt> <draft-ietf-ldapbis-roadmap-05.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all
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
comments directly to the author <Kurt@OpenLDAP.org>. comments directly to the author <Kurt@OpenLDAP.org>.
By submitting this Internet-Draft, I accept the provisions of Section
4 of RFC 3667. By submitting this Internet-Draft, I certify that any
applicable patent or other IPR claims of which I am aware have been
disclosed, and any of which I become aware will be disclosed, in
accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
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
material or to cite them other than as ``work in progress.'' 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 (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Please see the Full Copyright section near the end of this document Please see the Full Copyright section near the end of this document
for more information. for 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
skipping to change at page 2, line 33 skipping to change at page 2, line 40
LDAP: Uniform Resource Locator [LDAPURL], LDAP: Uniform Resource Locator [LDAPURL],
LDAP: Syntaxes and Matching Rules [Syntaxes], LDAP: Syntaxes and Matching Rules [Syntaxes],
LDAP: Internationalized String Preparation [LDAPprep], and LDAP: Internationalized String Preparation [LDAPprep], and
LDAP: User Schema [Schema]. LDAP: User Schema [Schema].
The terms "LDAP" and "LDAPv3" are commonly used to informally refer to The terms "LDAP" and "LDAPv3" are commonly used to informally refer to
the protocol specified by this technical specification. The LDAP the protocol specified by this technical specification. The LDAP
suite, as defined here, should be formally identified in other suite, as defined here, should be formally identified in other
documents by a normative reference to this document. documents by a normative reference to this document.
Extensions to LDAP may be specified in other documents. Nomenclature LDAP is an extensible protocol. Extensions to LDAP may be specified
denoting such combinations of LDAP-plus-extension(s) is not defined by in other documents. Nomenclature denoting such combinations of
this document but may be defined in some future document(s). LDAP-plus-extension(s) is not defined by this document but may be
defined in some future document(s). Extensions are expected to be
truly optional.
IANA (Internet Assigned Numbers Authority) considerations for LDAP IANA (Internet Assigned Numbers Authority) considerations for LDAP
described in BCP 64 [BCP64bis] apply fully to this revision of the described in BCP 64 [BCP64bis] apply fully to this revision of the
LDAP technical specification. LDAP technical specification.
2. Relationship to X.500 2. Relationship to X.500
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 Telecommunication Union - Telecom X.500(1993) series of International Telecommunication Union - Telecom
skipping to change at page 3, line 17 skipping to change at page 3, line 28
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 RFC 3377 itself). (which consists of RFC 2251-2256, RFC 2829-2830, RFC 3377, RFC 3771
The technical specification was significantly reorganized. itself). 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, portions of RFC 2252, and
[AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251. all of RFC 3771. [AuthMeth] replaces RFC 2829, RFC 2830, and portions
[Syntaxes] replaces the majority of RFC 2252 and portions of RFC 2256. of RFC 2251. [Syntaxes] replaces the majority of RFC 2252 and
[Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC portions of RFC 2256. [Schema] replaces the majority of RFC 2256.
2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255. [LDAPDN] replaces RFC 2253. [Filters] replaces RFC 2254. [LDAPURL]
replaces RFC 2255.
[LDAPprep] is new to this revision of the LDAP technical [LDAPprep] is new to this revision of the LDAP technical
specification. specification.
Each document of this specification contains appendices summarizing 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.
Additionally, portions of this technical specification update and/or Additionally, portions of this technical specification update and/or
skipping to change at page 4, line 12 skipping to change at page 4, line 22
This document is a product of the IETF LDAPBIS 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
[[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn.]]
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14 (also RFC 2119), March 1997. Requirement Levels", BCP 14 (also RFC 2119), March 1997.
[BCP64bis] Zeilenga, K., "IANA Considerations for LDAP", draft- [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
ietf-ldapbis-bcp64-xx.txt, a work in progress. draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.
[Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol",
draft-ietf-ldapbis-protocol-xx.txt, a work in progress. draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
[Models] Zeilenga, K. (editor), "LDAP: Directory Information [Models] Zeilenga, K. (editor), "LDAP: Directory Information
Models", draft-ietf-ldapbis-models-xx.txt, a work in Models", draft-ietf-ldapbis-models-xx.txt, a work in
progress. progress.
[AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
Connection Level Security Mechanisms", Connection Level Security Mechanisms",
skipping to change at page 5, line 43 skipping to change at page 6, line 15
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 replaced
with "technical specification") to clarify that it applies to the with "technical specification") to clarify that it applies to the
entire LDAP technical specification. entire LDAP technical specification.
Intellectual Property Rights Intellectual Property Rights
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain Intellectual Property Rights or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; nor does it represent that it has
effort to identify any such rights. Information on the IETF's made any independent effort to identify any such rights. Information
procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be found
standards-related documentation can be found in BCP-11. Copies of in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such proprietary assurances of licenses to be made available, or the result of an
rights by implementors or users of this specification can be obtained attempt made to obtain a general license or permission for the use of
from the IETF Secretariat. such proprietary rights by implementers or users of this specification
can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published and OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
distributed, in whole or in part, without restriction of any kind, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be followed,
or as required to translate it into languages other than English.
 End of changes. 

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