draft-ietf-ldapbis-ldapv3-ts-01.txt   rfc3377.txt 
INTERNET-DRAFT Jeff Hodges, Sun Microsystems Inc. Network Working Group J. Hodges
Intended Category: RL "Bob" Morgan, Univ of Washington Request for Comments: 3377 Sun Microsystems Inc.
Standards Track 8 May, 2002 Category: Standards Track R. Morgan
Updates: 2251, 2252, 2253, 2254, University of Washington
2255, 2256, 2829, 2830 September 2002
Lightweight Directory Access Protocol (v3): Lightweight Directory Access Protocol (v3):
Technical Specification Technical Specification
<draft-ietf-ldapbis-ldapv3-ts-01.txt> Status of this Memo
Status of this Document
This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Comments and suggestions on this document are encouraged. Comments on This document specifies an Internet standards track protocol for the
this document should be sent to the LDAPbis BOF discussion list: Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
ietf-ldapbis@OpenLDAP.org Copyright Notice
This document expires on 8 October 2002. Copyright (C) The Internet Society (2002). All Rights Reserved.
Abstract Abstract
This document specifies the set of RFCs comprising LDAPv3, and addresses This document specifies the set of RFCs comprising the Lightweight
the "IESG Note" attached to RFCs 2251 through 2256. Directory Access Protocol Version 3 (LDAPv3), and addresses the "IESG
Note" attached to RFCs 2251 through 2256.
1. Background and Motivation 1. Background and Motivation
The specification for the Lightweight Directory Access Protocol version The specification for the Lightweight Directory Access Protocol
3 (LDAPv3) nominally comprises eight RFCs which were issued in two dis- version 3 (LDAPv3) nominally comprises eight RFCs which were issued
tinct subsets at separate times -- RFCs 2251 through 2256 first, then in two distinct subsets at separate times -- RFCs 2251 through 2256
RFCs 2829 and 2830 following later. first, then RFCs 2829 and 2830 following later.
RFC 2251 through 2256 do not mandate the implementation of any satisfac- RFC 2251 through 2256 do not mandate the implementation of any
tory authentication mechanisms and hence were published with an "IESG satisfactory authentication mechanisms and hence were published with
Note" discouraging implementation and deployment of LDAPv3 clients or an "IESG Note" discouraging implementation and deployment of LDAPv3
servers implementing update functionality until a Proposed Standard for clients or servers implementing update functionality until a Proposed
mandatory authentication in LDAPv3 is published. Standard for mandatory authentication in LDAPv3 is published.
RFC 2829 was subsequently published in answer to the IESG Note. RFC 2829 was subsequently published in answer to the IESG Note.
The purpose of this document is to explicitly specify the set of RFCs The purpose of this document is to explicitly specify the set of RFCs
comprising LDAPv3, and formally address the IESG Note through explicit comprising LDAPv3, and formally address the IESG Note through
inclusion of RFC 2829. explicit inclusion of RFC 2829.
2. Specification of LDAPv3 2. Specification of LDAPv3
The Lightweight Directory Access Protocol version 3 (LDAPv3) is speci- The Lightweight Directory Access Protocol version 3 (LDAPv3) is
fied by this set of nine RFCs: specified by this set of nine RFCs:
[RFC2251] Lightweight Directory Access Protocol (v3) [RFC2251] Lightweight Directory Access Protocol (v3) [the
[the specification of the LDAP on-the-wire protocol] specification of the LDAP on-the-wire protocol]
[RFC2252] Lightweight Directory Access Protocol (v3): [RFC2252] Lightweight Directory Access Protocol (v3): Attribute
Attribute Syntax Definitions Syntax Definitions
[RFC2253] Lightweight Directory Access Protocol (v3): [RFC2253] Lightweight Directory Access Protocol (v3): UTF-8
UTF-8 String Representation of Distinguished Names String Representation of Distinguished Names
[RFC2254] The String Representation of LDAP Search Filters [RFC2254] The String Representation of LDAP Search Filters
[RFC2255] The LDAP URL Format [RFC2255] The LDAP URL Format
[RFC2256] A Summary of the X.500(96) User Schema for use [RFC2256] A Summary of the X.500(96) User Schema for use with
with LDAPv3 LDAPv3
[RFC2829] Authentication Methods for LDAP [RFC2829] Authentication Methods for LDAP
[RFC2830] Lightweight Directory Access Protocol (v3): [RFC2830] Lightweight Directory Access Protocol (v3): Extension
Extension for Transport Layer Security for Transport Layer Security
And, this document (RFCxxxx). And, this document (RFC3377).
The term "LDAPv3" is often used informally to refer to the protocol The term "LDAPv3" is often used informally to refer to the protocol
specified by the above set of RFCs, or subsets thereof. However, the specified by the above set of RFCs, or subsets thereof. However, the
LDAPv3 protocol suite, as defined here, should be formally identified in LDAPv3 protocol suite, as defined here, should be formally identified
other documents by a normative reference to this document. in other documents by a normative reference to this document.
3. Addressing the "IESG Note" in RFCs 2251 through 2256 3. Addressing the "IESG Note" in RFCs 2251 through 2256
The IESG approved publishing RFCs 2251 through 2256 with an attendant The IESG approved publishing RFCs 2251 through 2256 with an attendant
IESG Note included in each document. The Note begins with: IESG Note included in each document. The Note begins with:
This document describes a directory access protocol that provides This document describes a directory access protocol that provides
both read and update access. Update access requires secure authenti- both read and update access. Update access requires secure
cation, but this document does not mandate implementation of any authentication, but this document does not mandate implementation
satisfactory authentication mechanisms. of any satisfactory authentication mechanisms.
The Note ends with this statement: The Note ends with this statement:
Implementors are hereby discouraged from deploying LDAPv3 clients or Implementors are hereby discouraged from deploying LDAPv3 clients
servers which implement the update functionality, until a Proposed or servers which implement the update functionality, until a
Standard for mandatory authentication in LDAPv3 has been approved and Proposed Standard for mandatory authentication in LDAPv3 has been
published as an RFC. approved and published as an RFC.
[RFC2829] is expressly the "Proposed Standard for mandatory authentica- [RFC2829] is expressly the "Proposed Standard for mandatory
tion in LDAPv3" called for in the Note. Thus, the IESG Note in authentication in LDAPv3" called for in the Note. Thus, the IESG
[RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255], and [RFC2256] is Note in [RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255], and
addressed. [RFC2256] is addressed.
4. Security Considerations 4. Security Considerations
This document does not directly discuss security, although the context This document does not directly discuss security, although the
of the aforementioned IESG Note is security related, as is the manner in context of the aforementioned IESG Note is security related, as is
which it is addressed. the manner in which it is addressed.
Please refer to the referenced documents, especially [RFC2829], Please refer to the referenced documents, especially [RFC2829],
[RFC2251], and [RFC2830], for further information concerning LDAPv3 [RFC2251], and [RFC2830], for further information concerning LDAPv3
security. security.
5. Acknowledgements 5. Acknowledgements
The authors thank Patrick Falstrom, Leslie Daigle, Thomas Narten, and The authors thank Patrik Faltstrom, Leslie Daigle, Thomas Narten, and
Kurt Zeilenga for their contributions to this document. Kurt Zeilenga for their contributions to this document.
6. References 6. References
[RFC2251] M. Wahl, S. Kille and T. Howes, "Lightweight Directory [RFC2251] Wahl, M., Kille, S. and T. Howes, "Lightweight Directory
Access Protocol (v3)", RFC 2251, December 1997. Access Protocol (v3)", RFC 2251, December 1997.
[RFC2252] M. Wahl, A. Coulbeck, T. Howes, and S. Kille, "Lightweight [RFC2252] Wahl, M., Coulbeck, A., Howes, T. and S. Kille,
Directory Access Protocol (v3): Attribute Syntax Defini- "Lightweight Directory Access Protocol (v3): Attribute
tions", RFC 2252, December 1997. Syntax Definitions", RFC 2252, December 1997.
[RFC2253] S. Kille, M. Wahl, and T. Howes, "Lightweight Directory [RFC2253] Kille, S., Wahl, M. and T. Howes, "Lightweight Directory
Access Protocol (v3): UTF-8 String Representation of Dis- Access Protocol (v3): UTF-8 String Representation of
tinguished Names", RFC 2253, December 1997. Distinguished Names", RFC 2253, December 1997.
[RFC2254] T. Howes, "The String Representation of LDAP Search [RFC2254] Howes, T., "The String Representation of LDAP Search
Filters", RFC 2254, December 1997. Filters", RFC 2254, December 1997.
[RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, [RFC2255] Howes, T. and M. Smith, "The LDAP URL Format", RFC 2255,
December 1997. December 1997.
[RFC2256] M. Wahl, "A Summary of the X.500(96) User Schema for use [RFC2256] Wahl, M., "A Summary of the X.500(96) User Schema for use
with LDAPv3", RFC 2256, December 1997. with LDAPv3", RFC 2256, December 1997.
[RFC2829] M. Wahl, H. Alvestrand, J. Hodges, R. Morgan. "Authentica- [RFC2829] Wahl, M., Alvestrand, H., Hodges, J. and R. Morgan,
tion Methods for LDAP", RFC 2829, May 2000. "Authentication Methods for LDAP", RFC 2829, May 2000.
[RFC2830] J. Hodges, R. Morgan, M. Wahl, "Lightweight Directory Access [RFC2830] Hodges, J., Morgan, R. and M. Wahl, "Lightweight Directory
Protocol (v3): Extension for Transport Layer Security", RFC Access Protocol (v3): Extension for Transport Layer
2830, May 2000. Security", RFC 2830, May 2000.
7. Authors' Addresses 7. Intellectual Property Rights Notices
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
8. Authors' Addresses
Jeff Hodges Jeff Hodges
Sun Microsystems, Inc. Sun Microsystems, Inc.
901 San Antonio Road, USCA22-212 901 San Antonio Road, USCA22-212
Palo Alto, CA 94303 Palo Alto, CA 94303
USA USA
Phone: +1-408-276-5467 Phone: +1-408-276-5467
EMail: Jeff.Hodges@sun.com EMail: Jeff.Hodges@sun.com
RL "Bob" Morgan RL "Bob" Morgan
Computing and Communications Computing and Communications
University of Washington University of Washington
Seattle, WA Seattle, WA
USA USA
Phone: +1-206-221-3307 Phone: +1-206-221-3307
EMail: rlmorgan@washington.edu EMail: rlmorgan@washington.edu
----------------------------------- 9. Full Copyright Statement
8. Intellectual Property Rights Notices
The IETF takes no position regarding the validity or scope of any intel-
lectual property or other rights that might be claimed to pertain to
the implementation or use of the technology described in this document
or the extent to which any license under such rights might or might not
be available; neither does it represent that it has made any effort to
identify any such rights. Information on the IETF's procedures with
respect to rights in standards-track and standards-related documentation
can be found in BCP-11. Copies of claims of rights made available for
publication and any assurances of licenses to be made available, or the
result of an attempt made to obtain a general license or permission for
the use of such proprietary rights by implementors or users of this
specification can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this stan-
dard. Please address the information to the IETF Executive Director.
9. Copyright Notice and Disclaimer
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (2002). 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 or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, 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 develop- Internet organizations, except as needed for the purpose of
ing Internet standards in which case the procedures for copyrights developing Internet standards in which case the procedures for
defined in the Internet Standards process must be followed, or as copyrights defined in the Internet Standards process must be
required to translate it into languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-----------------------------------
This document expires on 8 October 2002. Acknowledgement
end Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 45 change blocks. 
142 lines changed or deleted 125 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/