draft-ietf-ldapbis-roadmap-07.txt   draft-ietf-ldapbis-roadmap-08.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 10 February 2005 Expires in six months 30 September 2005
Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771 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-07.txt> <draft-ietf-ldapbis-roadmap-08.txt>
Status of this Memo Status of this Memo
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 By submitting this Internet-Draft, each author represents that any
4 of RFC 3667. By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which he or she is aware have
applicable patent or other IPR claims of which I am aware have been been or will be disclosed, and any of which he or she becomes aware
disclosed, or will be disclosed, and any of which I become aware will will be disclosed, in accordance with Section 6 of BCP 79.
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 material time. It is inappropriate to use Internet-Drafts as reference material
or to cite them other than as "work in progress." or to cite them other than as "work in progress."
skipping to change at page 3, line 20 skipping to change at page 3, line 20
Standardization (ITU-T) Recommendations when providing the service. Standardization (ITU-T) Recommendations when providing the service.
However, it is not required that an LDAP server make use of any X.500 However, it is not required that an LDAP server make use of any X.500
protocols in providing this service, e.g. LDAP can be mapped onto any protocols in providing this service, e.g. LDAP can be mapped onto any
other directory system so long as the X.500 data and service models other 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 This technical specification explicitly incorporates portions of
X.500(93). Later revisions of X.500 do not automatically apply to X.500(93). Later revisions of X.500 do not automatically apply to
this technical specification. this technical specification.
3. Security Considerations 3. Relationship to Obsolete Specifications
LDAP security considerations are discussed in each document comprising
the technical specification.
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, RFC 3771, and RFC (which consists of RFC 2251-2256, RFC 2829-2830, RFC 3771, and RFC
3377 itself). The technical specification was significantly 3377 itself). The technical specification was significantly
reorganized. 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, portions of RFC 2252, and [Protocol] replaces the majority RFC 2251, portions of RFC 2252, and
skipping to change at page 4, line 8 skipping to change at page 3, line 50
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
replace a number of other documents not listed above. These replace a number of other documents not listed above. These
relationships are discussed in the documents detailings these portions relationships are discussed in the documents detailings these portions
of this technical specification. of this technical specification.
5. Acknowledgments 4. Security Considerations
LDAP security considerations are discussed in each document comprising
the technical specification.
5. IANA Considerations
No actions.
[[Note to RFC Editor: this section may be removed prior to
publication.]]
6. 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. This document is a product of the IETF LDAPBIS Working Group.
6. Author's Address 7. Author's Address
Kurt D. Zeilenga Kurt D. Zeilenga
OpenLDAP Foundation OpenLDAP Foundation
Email: Kurt@OpenLDAP.org Email: Kurt@OpenLDAP.org
7. References 8. References
[[Note to the RFC Editor: please replace the citation tags used in [[Note to the RFC Editor: please replace the citation tags used in
referencing Internet-Drafts with tags of the form RFCnnnn where referencing Internet-Drafts with tags of the form RFCnnnn where
possible.]] possible.]]
7.1. Normative References 8.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", [BCP64bis] Zeilenga, K., "IANA Considerations for LDAP",
draft-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.
skipping to change at page 5, line 41 skipping to change at page 5, line 49
[X.501] International Telecommunication Union - [X.501] International Telecommunication Union -
Telecommunication Standardization Sector, "The Directory Telecommunication Standardization Sector, "The Directory
-- Models," X.501(1993) (also ISO/IEC 9594-2:1994). -- Models," X.501(1993) (also ISO/IEC 9594-2:1994).
[X.511] International Telecommunication Union - [X.511] International Telecommunication Union -
Telecommunication Standardization Sector, "The Telecommunication Standardization Sector, "The
Directory: Abstract Service Definition", X.511(1993) Directory: Abstract Service Definition", X.511(1993)
(also ISO/IEC 9594-3:1993). (also ISO/IEC 9594-3:1993).
7.2. Informative References 8.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 to the
documents it replaces (in whole or in part). documents it replaces (in whole or in part).
Appendix A.1. Changes to RFC 3377 Appendix A.1. Changes to RFC 3377
skipping to change at page 6, line 44 skipping to change at page 7, line 7
http://www.ietf.org/ipr. 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 that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Full Copyright
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. 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 the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 10 change blocks. 
21 lines changed or deleted 28 lines changed or added

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