Communication Agreement Lightweight Contents Access Agreement Third Edition: Technical Specifications
Yesterday, I found an article on the Internet. It is traditional Chinese. I saw it. Today, I translated it into Simplified Chinese using Word. I sent it online. "Lightweight Directory Access Agreement Third Edition: Technical Specifications" This is an important norm to do network communication software.
Lightweight Contents Access Agreement Third Edition: Technical Specification
Translator:
Peng Jianxiang,
Key words:
RFC 3377, LDAPV3
Original:
http://www.ietf.org/rfc/rfc3377.txt
Copyright © The Internet Society (2002). All Rights Reserved.
table of Contents
File status
Summary
Background information and motivation
2. Lightweight directory access agreement third edition specification
3. Processing "IESG considerations" between RFC 2251 to 2256
4. Safety consideration
5. Thanks for the statement
6. Reference data
7. Precautions for intelligent property rights
8. Contact information
9. Complete copyright statement
File status
This document describes the Internet-based standard tracking protocol of the Internet community, and recommendations on improving the Internet standard request. If you want to know the standardized situation with this protocol (LDAPV3), please refer to the current edited "Internet Official Agreement Standard" (STD1). There is no restriction condition that spreads this document.
Summary
This file details a set of RFCs composed of the Lightweight Directory Access Protocol (LDAPv3), and will manage "IESG precautions" by RFC 2251 to 2256.
Background information and motivation
The specifications of the Lightweight Directory Access Agreement Third Edition (LDAPV3) can be composed of eight RFCs in nominal, and the eight RFCs can be divided into two subsets in accordance with the interval of time. The first is RFCs 2251 to 2256, and then the RFC 2829 and RFC 2830 are later.
RFC 2251 to 2256 does not force a powerful authentication mechanism to be implemented, so there is a "IESG Precaution" to block the "IESG Precautions" when the file is released, and the LDAPV3 client or servo is released until LDAPv3 is released. It is forced that the recommended certification is standard.
The RFC 2829 released later is an answer IESG consideration.
The purpose of this document is to illustrate that LDAPv3 is composed of those RFCs and formally processed IESG considerations by the contents of RFC 2829.
2. Lightweight directory access agreement third edition specification
This file details the third edition of the lightweight directory access protocol (LDAPv3) is composed of a set of nine-nine RFCs:
[RFC2251] - Lightweight Directory Acquisition Agreement Third Edition: Large LDAP Specifications
[RFC2252] - Lightweight Directory Acquisition Protocol Third Edition: Property Symptory Definition
[RFC2253] - Lightweight Directory Acquisition Protocol Third Edition: Express distinctive names in UTF-8 string
[RFC2254] - Express LDAP Search Filters in string
[RFC2255] - LDAP URL format
[RFC2256] - Introduction X.500 (96) User Outline, in order to use LDAPV3
[RFC2829] - LDAP authentication method
[RFC2830] - Lightweight directory Acquisition Protocol Third Edition: Transport Layer Security Extension
And this RFC 3377 file.
The term "LDAPV3" is often a representative of this communication protocol with an informal usage at the upper RFC. However, the LDAPv3 protocol set is as defined here, it should be officially recognized by other files to this document.
3. Processing "IESG considerations" between RFC 2251 to 2256
IESG approval issued RFC2251 to 2256 when IESG considerations are attached to each file. Precautions begin with such text: This file introduces a directory access protocol to provide read and update access. Update access requires secure authentication, but this file does not force to specify the powerful authentication mechanism for the actual actual.
Notes on the termination of such words:
Blocking the actual deployment of the LDAPv3 client or servo ends to do its update function until it is issued in LDAPv3 to force a proposed standard.
[RFC2829] is explained that "Suggested Standards" in LDAPV3 is highly specified "will be explained in the precautions. Therefore, IESG precautions for [RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255] are treated.
4. Safety consideration
Although IESG considerations in the previous festival are related to security, this document does not discuss security issues directly.
To learn more about LDAPv3 security issues, please refer to the related files, especially [RFC2829], [RFC2251] and [RFC2830].
5. Thanks for the statement
Author thanks to Patrik Faltstrom, Leslie Daigle, Thomas Narten and Kurt Zeilenga's contribution to this document.
6. Reference data
[RFC2251] WAHL, M., Kille, S. and T. Howes, "Lightweight Contents Access Agreement Third Edition", RFC 2251, December 1997
[RFC2252] WAHL, M., Coulbeck, A., HOWES, T. And S. Kille, "Lightweight Directory Access Agreement Third Edition: Attribute Syntax Definition", RFC 2252, December 1997
[RFC2253] Kille, S., Wahl, M. and T. Howes, "Lightweight Directory Access Agreement Third Edition: Name of UTF-8 string", RFC 2253, December 1997
[RFC2254] Howes, T., "Express LDAP Search Filters in Strings", RFC 2254, December 1997
[RFC2255] HOWES, T. And M. Smith, "LDAP URL Format", RFC 2255, December 1997
[RFC2256] WAHL, M., "Introduction X.500 (96) User Outline, in order to use LDAPv3", RFC 2256, December 1997
[RFC2829] WAHL, M., AlvesTrand, H., Hodges, J. And R. Morgan, "LDAP Certification Method", RFC 2829, May 2000
[RFC2830] Hodges, J., Morgan, R. And M. Wahl, "Lightweight Directory Access Agreement Third Edition: Transport Layer Security Extension Function", RFC 2830, 2000 May
7. Precautions for intelligent property rights
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 Intested Party To Bring to Its Attention Any Copyrights, Patents Or Patent Applications, Or Other Proprietary Rights Which May Cover Technolog .
8. Contact information
Jeff HodgesSun Microsystems, Inc.901 San Antonio Road, USCA22-212Palo Alto, CA 94303USA Tel: 1-408-276-5467 Email: Jeff.Hodges@sun.comRL "Bob" MorganComputing and CommunicationsUniversity of WashingtonSeattle, WAUSA Tel: 1-206-221-3307 Email: rlmorgan@washington.edu
9. Complete copyright statement
Copyright © The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind , provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this 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 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.The limited permissions granted above are perpetual and will not BE REVOKED by the Internet society or its successs.
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 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 Merchantability Or Fitness for a particular purpose.
