| < draft-ietf-ldapbis-ldapv3-ts-00.txt | draft-ietf-ldapbis-ldapv3-ts-01.txt > | |||
|---|---|---|---|---|
| INTERNET-DRAFT Jeff Hodges, Oblix Inc. | A new Request for Comments is now available in online RFC libraries. | |||
| Intended Category: RL "Bob" Morgan, Univ of Washington | ||||
| Standards Track 12 January, 2001 | ||||
| Updates: 2251, 2252, 2253, 2254, | ||||
| 2255, 2256, 2829, 2830 | ||||
| Lightweight Directory Access Protocol (v3): | ||||
| Technical Specification | ||||
| <draft-ietf-ldapbis-ldapv3-ts-00.txt> | ||||
| 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 should be sent to the LDAPbis BOF discussion list: | ||||
| ietf-ldapbis@OpenLDAP.org | ||||
| This document expires on 12 July 2001. | ||||
| Abstract | ||||
| This document specifies the set of RFCs comprising LDAPv3, and addresses | ||||
| the "IESG Note" attached to RFCs 2251 through 2256. | ||||
| I-D LDAPv3: Technical Specification January 2001 | ||||
| 1. Background and Motivation | ||||
| The specification for the Lightweight Directory Access Protocol version | ||||
| 3 (LDAPv3) nominally comprises eight RFCs which were issued in two dis- | ||||
| tinct subsets at separate times -- RFCs 2251 through 2256 first, then | ||||
| RFCs 2829 and 2830 following later. | ||||
| RFC 2251 through 2256 do not mandate the implementation of any satisfac- | ||||
| tory authentication mechanisms and hence were published with an "IESG | ||||
| Note" discouraging implementation and deployment of LDAPv3 clients or | ||||
| servers implementing update functionality until a Proposed Standard for | ||||
| mandatory authentication in LDAPv3 is published. | ||||
| RFC 2829 was subsequently published in answer to the IESG Note. | ||||
| The purpose of this document is to explicitly specify the set of RFCs | ||||
| comprising LDAPv3, and formally address the IESG Note through explicit | ||||
| inclusion of RFC 2829. | ||||
| 2. Conventions Used in this Document | ||||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | ||||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | ||||
| document are to be interpreted as described in [RFC2119]. | ||||
| 3. Specification of LDAPv3 | ||||
| The Lightweight Directory Access Protocol version 3 (LDAPv3) is speci- | ||||
| fied by this set of nine RFCs: | ||||
| [RFC2251] Lightweight Directory Access Protocol (v3) | ||||
| [the specification of the LDAP on-the-wire protocol] | ||||
| [RFC2252] Lightweight Directory Access Protocol (v3): | ||||
| Attribute Syntax Definitions | ||||
| [RFC2253] Lightweight Directory Access Protocol (v3): | ||||
| UTF-8 String Representation of Distinguished Names | ||||
| [RFC2254] The String Representation of LDAP Search Filters | ||||
| [RFC2255] The LDAP URL Format | ||||
| [RFC2256] A Summary of the X.500(96) User Schema for use | ||||
| with LDAPv3 | ||||
| [RFC2829] Authentication Methods for LDAP | ||||
| I-D LDAPv3: Technical Specification January 2001 | ||||
| [RFC2830] Lightweight Directory Access Protocol (v3): | ||||
| Extension for Transport Layer Security | ||||
| And, this document (RFCxxxx). | ||||
| The term "LDAPv3" MAY be used to informally refer to the protocol speci- | ||||
| fied by this set of RFCs. The LDAPv3 protocol suite, as defined here, | ||||
| SHOULD be formally identified in other documents by a normative refer- | ||||
| ence to this document. | ||||
| Other RFCs (and perhaps Internet-Drafts) MAY specify extensions to | ||||
| LDAPv3. Nomenclature denoting such combinations of LDAPv3-plus- | ||||
| extension(s) is not defined by this document, and MAY be defined in some | ||||
| future document(s). | ||||
| 4. Addressing the "IESG Note" in RFCs 2251 through 2256 | ||||
| The IESG approved publishing RFCs 2251 through 2256 with an attendant | ||||
| IESG Note included in each document. The Note begins with.. | ||||
| This document describes a directory access protocol that provides | ||||
| both read and update access. Update access requires secure authenti- | ||||
| cation, but this document does not mandate implementation of any | ||||
| satisfactory authentication mechanisms. | ||||
| The Note ends with this statement.. | ||||
| Implementors are hereby discouraged from deploying LDAPv3 clients or | ||||
| servers which implement the update functionality, until a Proposed | ||||
| Standard for mandatory authentication in LDAPv3 has been approved and | ||||
| published as an RFC. | ||||
| [RFC2829] is expressly the "Proposed Standard for mandatory authentica- | ||||
| tion in LDAPv3" called for in the Note. Thus, the IESG Note in | ||||
| [RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255], and [RFC2256] is | ||||
| addressed. | ||||
| 5. Security Considerations | ||||
| This document does not directly discuss security, although the context | ||||
| of the aforementioned IESG Note is security related, as is the manner in | ||||
| which it is addressed. | ||||
| Please refer to the referenced documents, especially [RFC2829], | ||||
| [RFC2251], and [RFC2830], for further information concerning LDAPv3 | ||||
| security. | ||||
| I-D LDAPv3: Technical Specification January 2001 | ||||
| 6. Acknowledgements | ||||
| The authors thank Patrick Falstrom, Leslie Daigle, and Kurt Zeilenga for | ||||
| their contributions to this document. | ||||
| 7. References | ||||
| [RFC2119] Scott Bradner. "Key Words for use in RFCs to Indicate | ||||
| Requirement Levels". RFC 2119, March 1997. | ||||
| [RFC2251] M. Wahl, S. Kille and T. Howes, "Lightweight Directory | ||||
| Access Protocol (v3)", RFC 2251, December 1997. | ||||
| [RFC2252] M. Wahl, A. Coulbeck, T. Howes, and S. Kille, "Lightweight | ||||
| Directory Access Protocol (v3): Attribute Syntax Defini- | ||||
| tions", RFC 2252, December 1997. | ||||
| [RFC2253] S. Kille, M. Wahl, and T. Howes, "Lightweight Directory | ||||
| Access Protocol (v3): UTF-8 String Representation of Dis- | ||||
| tinguished Names", RFC 2253, December 1997. | ||||
| [RFC2254] T. Howes, "The String Representation of LDAP Search | ||||
| Filters", RFC 2254, December 1997. | ||||
| [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, | ||||
| December 1997. | ||||
| [RFC2256] M. Wahl, "A Summary of the X.500(96) User Schema for use | ||||
| with LDAPv3", RFC 2256, December 1997. | ||||
| [RFC2829] M. Wahl, H. Alvestrand, J. Hodges, R. Morgan. "Authentica- | ||||
| tion Methods for LDAP", RFC 2829, May 2000. | ||||
| [RFC2830] J. Hodges, R. Morgan, M. Wahl, "Lightweight Directory Access | ||||
| Protocol (v3): Extension for Transport Layer Security", RFC | ||||
| 2830, May 2000. | ||||
| 8. Authors' Addresses | ||||
| Jeff Hodges | ||||
| Oblix, Inc. | ||||
| 18922 Forge Drive | ||||
| Cupertino, CA 95014 | ||||
| USA | ||||
| Phone: +1-408-861-6656 | ||||
| EMail: jhodges@oblix.com | ||||
| I-D LDAPv3: Technical Specification January 2001 | ||||
| RL "Bob" Morgan | ||||
| Computing and Communications | ||||
| University of Washington | ||||
| Seattle, WA | ||||
| USA | ||||
| Phone: +1-206-221-3307 | RFC 3377 | |||
| EMail: rlmorgan@washington.edu | ||||
| ----------------------------------- | Title: Lightweight Directory Access Protocol (v3): | |||
| Technical Specification | ||||
| Author(s): J. Hodges, R. Morgan | ||||
| Status: Standards Track | ||||
| Date: September 2002 | ||||
| Mailbox: Jeff.Hodges@sun.com, rlmorgan@washington.edu | ||||
| Pages: 6 | ||||
| Characters: 9981 | ||||
| Updates/Obsoletes/SeeAlso: None | ||||
| 9. Intellectual Property Rights Notices | I-D Tag: draft-ietf-ldapbis-ldapv3-ts-01.txt | |||
| The IETF takes no position regarding the validity or scope of any intel- | URL: ftp://ftp.rfc-editor.org/in-notes/rfc3377.txt | |||
| 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 | This document specifies the set of RFCs comprising the Lightweight | |||
| copyrights, patents or patent applications, or other proprietary rights | Directory Access Protocol Version 3 (LDAPv3), and addresses the "IESG | |||
| which may cover technology that may be required to practice this stan- | Note" attached to RFCs 2251 through 2256. | |||
| dard. Please address the information to the IETF Executive Director. | ||||
| 10. Copyright Notice and Disclaimer | This document is a product of the LDAP (v3) Revision Working Group of | |||
| the IETF. | ||||
| Copyright (C) The Internet Society (1998). All Rights Reserved. | This is now a Proposed Standard Protocol. | |||
| This document and translations of it may be copied and furnished to | This document specifies an Internet standards track protocol for | |||
| others, and derivative works that comment on or otherwise explain it | the Internet community, and requests discussion and suggestions | |||
| or assist in its implementation may be prepared, copied, published | for improvements. Please refer to the current edition of the | |||
| and distributed, in whole or in part, without restriction of any | "Internet Official Protocol Standards" (STD 1) for the | |||
| kind, provided that the above copyright notice and this paragraph are | standardization state and status of this protocol. Distribution | |||
| included on all such copies and derivative works. However, this | of this memo is unlimited. | |||
| document itself may not be modified in any way, such as by removing | ||||
| the copyright notice or references to the Internet Society or other | ||||
| Internet organizations, except as needed for the purpose of develop- | ||||
| ing 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. | ||||
| I-D LDAPv3: Technical Specification January 2001 | This announcement is sent to the IETF list and the RFC-DIST list. | |||
| Requests to be added to or deleted from the IETF distribution list | ||||
| should be sent to IETF-REQUEST@IETF.ORG. Requests to be | ||||
| added to or deleted from the RFC-DIST distribution list should | ||||
| be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. | ||||
| The limited permissions granted above are perpetual and will not be | Details on obtaining RFCs via FTP or EMAIL may be obtained by sending | |||
| revoked by the Internet Society or its successors or assigns. | an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body | |||
| help: ways_to_get_rfcs. For example: | ||||
| This document and the information contained herein is provided on an | To: rfc-info@RFC-EDITOR.ORG | |||
| "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | Subject: getting rfcs | |||
| TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | ||||
| BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | ||||
| HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- | ||||
| CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | ||||
| ----------------------------------- | help: ways_to_get_rfcs | |||
| This document expires on 12 July 2001. | Requests for special distribution should be addressed to either the | |||
| author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless | ||||
| specifically noted otherwise on the RFC itself, all RFCs are for | ||||
| unlimited distribution.echo | ||||
| Submissions for Requests for Comments should be sent to | ||||
| RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC | ||||
| Authors, for further information. | ||||
| End of changes. 14 change blocks. | ||||
| 243 lines changed or deleted | 36 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||