idnits 2.17.1 draft-ietf-ldapbis-ldapv3-ts-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. -- The draft header indicates that this document updates RFC2251, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2252, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2253, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC2254, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 209 has weird spacing: '...imed to perta...' == Unrecognized Status in 'Intended Category:', assuming Proposed Standard (Expected one of 'Standards Track', 'Full Standard', 'Draft Standard', 'Proposed Standard', 'Best Current Practice', 'Informational', 'Experimental', 'Informational', 'Historic'.) (Using the creation date from RFC2251, updated by this document, for RFC5378 checks: 1996-03-14) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) ** Obsolete normative reference: RFC 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) ** Obsolete normative reference: RFC 2253 (Obsoleted by RFC 4510, RFC 4514) ** Obsolete normative reference: RFC 2254 (Obsoleted by RFC 4510, RFC 4515) ** Obsolete normative reference: RFC 2255 (Obsoleted by RFC 4510, RFC 4516) ** Obsolete normative reference: RFC 2256 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4519, RFC 4523) ** Obsolete normative reference: RFC 2829 (Obsoleted by RFC 4510, RFC 4513) ** Obsolete normative reference: RFC 2830 (Obsoleted by RFC 4510, RFC 4511, RFC 4513) Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Jeff Hodges, Oblix Inc. 2 Intended Category: RL "Bob" Morgan, Univ of Washington 3 Standards Track 12 January, 2001 4 Updates: 2251, 2252, 2253, 2254, 5 2255, 2256, 2829, 2830 7 Lightweight Directory Access Protocol (v3): 8 Technical Specification 10 12 Status of this Document 14 This document is an Internet-Draft and is in full conformance with all 15 provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other groups 19 may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference material 24 or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Comments and suggestions on this document are encouraged. Comments on 33 this document should be sent to the LDAPbis BOF discussion list: 35 ietf-ldapbis@OpenLDAP.org 37 This document expires on 12 July 2001. 39 Abstract 41 This document specifies the set of RFCs comprising LDAPv3, and addresses 42 the "IESG Note" attached to RFCs 2251 through 2256. 44 I-D LDAPv3: Technical Specification January 2001 46 1. Background and Motivation 48 The specification for the Lightweight Directory Access Protocol version 49 3 (LDAPv3) nominally comprises eight RFCs which were issued in two dis- 50 tinct subsets at separate times -- RFCs 2251 through 2256 first, then 51 RFCs 2829 and 2830 following later. 53 RFC 2251 through 2256 do not mandate the implementation of any satisfac- 54 tory authentication mechanisms and hence were published with an "IESG 55 Note" discouraging implementation and deployment of LDAPv3 clients or 56 servers implementing update functionality until a Proposed Standard for 57 mandatory authentication in LDAPv3 is published. 59 RFC 2829 was subsequently published in answer to the IESG Note. 61 The purpose of this document is to explicitly specify the set of RFCs 62 comprising LDAPv3, and formally address the IESG Note through explicit 63 inclusion of RFC 2829. 65 2. Conventions Used in this Document 67 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 68 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 69 document are to be interpreted as described in [RFC2119]. 71 3. Specification of LDAPv3 73 The Lightweight Directory Access Protocol version 3 (LDAPv3) is speci- 74 fied by this set of nine RFCs: 76 [RFC2251] Lightweight Directory Access Protocol (v3) 77 [the specification of the LDAP on-the-wire protocol] 79 [RFC2252] Lightweight Directory Access Protocol (v3): 80 Attribute Syntax Definitions 82 [RFC2253] Lightweight Directory Access Protocol (v3): 83 UTF-8 String Representation of Distinguished Names 85 [RFC2254] The String Representation of LDAP Search Filters 87 [RFC2255] The LDAP URL Format 89 [RFC2256] A Summary of the X.500(96) User Schema for use 90 with LDAPv3 92 [RFC2829] Authentication Methods for LDAP 94 I-D LDAPv3: Technical Specification January 2001 96 [RFC2830] Lightweight Directory Access Protocol (v3): 97 Extension for Transport Layer Security 99 And, this document (RFCxxxx). 101 The term "LDAPv3" MAY be used to informally refer to the protocol speci- 102 fied by this set of RFCs. The LDAPv3 protocol suite, as defined here, 103 SHOULD be formally identified in other documents by a normative refer- 104 ence to this document. 106 Other RFCs (and perhaps Internet-Drafts) MAY specify extensions to 107 LDAPv3. Nomenclature denoting such combinations of LDAPv3-plus- 108 extension(s) is not defined by this document, and MAY be defined in some 109 future document(s). 111 4. Addressing the "IESG Note" in RFCs 2251 through 2256 113 The IESG approved publishing RFCs 2251 through 2256 with an attendant 114 IESG Note included in each document. The Note begins with.. 116 This document describes a directory access protocol that provides 117 both read and update access. Update access requires secure authenti- 118 cation, but this document does not mandate implementation of any 119 satisfactory authentication mechanisms. 121 The Note ends with this statement.. 123 Implementors are hereby discouraged from deploying LDAPv3 clients or 124 servers which implement the update functionality, until a Proposed 125 Standard for mandatory authentication in LDAPv3 has been approved and 126 published as an RFC. 128 [RFC2829] is expressly the "Proposed Standard for mandatory authentica- 129 tion in LDAPv3" called for in the Note. Thus, the IESG Note in 130 [RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255], and [RFC2256] is 131 addressed. 133 5. Security Considerations 135 This document does not directly discuss security, although the context 136 of the aforementioned IESG Note is security related, as is the manner in 137 which it is addressed. 139 Please refer to the referenced documents, especially [RFC2829], 140 [RFC2251], and [RFC2830], for further information concerning LDAPv3 141 security. 143 I-D LDAPv3: Technical Specification January 2001 145 6. Acknowledgements 147 The authors thank Patrick Falstrom, Leslie Daigle, and Kurt Zeilenga for 148 their contributions to this document. 150 7. References 152 [RFC2119] Scott Bradner. "Key Words for use in RFCs to Indicate 153 Requirement Levels". RFC 2119, March 1997. 155 [RFC2251] M. Wahl, S. Kille and T. Howes, "Lightweight Directory 156 Access Protocol (v3)", RFC 2251, December 1997. 158 [RFC2252] M. Wahl, A. Coulbeck, T. Howes, and S. Kille, "Lightweight 159 Directory Access Protocol (v3): Attribute Syntax Defini- 160 tions", RFC 2252, December 1997. 162 [RFC2253] S. Kille, M. Wahl, and T. Howes, "Lightweight Directory 163 Access Protocol (v3): UTF-8 String Representation of Dis- 164 tinguished Names", RFC 2253, December 1997. 166 [RFC2254] T. Howes, "The String Representation of LDAP Search 167 Filters", RFC 2254, December 1997. 169 [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, 170 December 1997. 172 [RFC2256] M. Wahl, "A Summary of the X.500(96) User Schema for use 173 with LDAPv3", RFC 2256, December 1997. 175 [RFC2829] M. Wahl, H. Alvestrand, J. Hodges, R. Morgan. "Authentica- 176 tion Methods for LDAP", RFC 2829, May 2000. 178 [RFC2830] J. Hodges, R. Morgan, M. Wahl, "Lightweight Directory Access 179 Protocol (v3): Extension for Transport Layer Security", RFC 180 2830, May 2000. 182 8. Authors' Addresses 184 Jeff Hodges 185 Oblix, Inc. 186 18922 Forge Drive 187 Cupertino, CA 95014 188 USA 190 Phone: +1-408-861-6656 191 EMail: jhodges@oblix.com 193 I-D LDAPv3: Technical Specification January 2001 195 RL "Bob" Morgan 196 Computing and Communications 197 University of Washington 198 Seattle, WA 199 USA 201 Phone: +1-206-221-3307 202 EMail: rlmorgan@washington.edu 204 ----------------------------------- 206 9. Intellectual Property Rights Notices 208 The IETF takes no position regarding the validity or scope of any intel- 209 lectual property or other rights that might be claimed to pertain to 210 the implementation or use of the technology described in this document 211 or the extent to which any license under such rights might or might not 212 be available; neither does it represent that it has made any effort to 213 identify any such rights. Information on the IETF's procedures with 214 respect to rights in standards-track and standards-related documentation 215 can be found in BCP-11. Copies of claims of rights made available for 216 publication and any assurances of licenses to be made available, or the 217 result of an attempt made to obtain a general license or permission for 218 the use of such proprietary rights by implementors or users of this 219 specification can be obtained from the IETF Secretariat. 221 The IETF invites any interested party to bring to its attention any 222 copyrights, patents or patent applications, or other proprietary rights 223 which may cover technology that may be required to practice this stan- 224 dard. Please address the information to the IETF Executive Director. 226 10. Copyright Notice and Disclaimer 228 Copyright (C) The Internet Society (1998). All Rights Reserved. 230 This document and translations of it may be copied and furnished to 231 others, and derivative works that comment on or otherwise explain it 232 or assist in its implementation may be prepared, copied, published 233 and distributed, in whole or in part, without restriction of any 234 kind, provided that the above copyright notice and this paragraph are 235 included on all such copies and derivative works. However, this 236 document itself may not be modified in any way, such as by removing 237 the copyright notice or references to the Internet Society or other 238 Internet organizations, except as needed for the purpose of develop- 239 ing Internet standards in which case the procedures for copyrights 240 defined in the Internet Standards process must be followed, or as 241 required to translate it into languages other than English. 243 I-D LDAPv3: Technical Specification January 2001 245 The limited permissions granted above are perpetual and will not be 246 revoked by the Internet Society or its successors or assigns. 248 This document and the information contained herein is provided on an 249 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 250 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 251 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 252 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- 253 CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 255 ----------------------------------- 257 This document expires on 12 July 2001.