idnits 2.17.1 draft-hodges-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 208 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. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Jeff Hodges, Oblix Inc. 3 Intended Category: RL "Bob" Morgan, Univ of Washington 4 Standards Track October, 2000 5 Updates: 2251, 2252, 2253, 2254, 6 2255, 2256, 2829, 2830 8 Lightweight Directory Access Protocol (v3): 9 Technical Specification 11 13 Status of this Document 15 This document is an Internet-Draft and is in full conformance with all 16 provisions of Section 10 of RFC2026. 18 Internet-Drafts are working documents of the Internet Engineering Task 19 Force (IETF), its areas, and its working groups. Note that other groups 20 may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference material 25 or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Comments and suggestions on this document are encouraged. Comments on 34 this document should be sent to the LDAPbis BOF discussion list: 36 ietf-ldapbis@OpenLDAP.org 38 This document expires in May 2001. 40 Abstract 42 This document specifies the set of RFCs comprising LDAPv3, and documents 43 the addressing of the "IESG Note" attached to RFCs 2251 through 2256. 45 I-D LDAPv3: Technical Specification October 2000 47 1. Background and Motivation 49 The specification for the Lightweight Directory Access Protocol version 50 3 (LDAPv3) nominally comprises eight RFCs which were issued in two dis- 51 tinct subsets at separate times (RFCs 2251 through 2256 first, then RFCs 52 2829 and 2830 following later). 54 RFCs 2251 through 2256 are each embellished with an "IESG Note" (Note) 55 warning implementors and deployers of potential interoperability prob- 56 lems due to the lack of a specification of mandatory-to-implement 57 authentication mechanism(s). 59 The purpose of this document is to remedy both issues by explicitly 60 specifying the set of RFCs comprising LDAPv3 and documenting the fact 61 that the IESG now considers the "IESG Note" as "addressed" given the 62 specification of mandatory-to-implement authentication mechanisms in RFC 63 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 October 2000 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 referenced by a normative reference to this document. 105 Other RFCs (and perhaps Internet-Drafts) MAY specify extensions to 106 LDAPv3. Nomenclature denoting such combinations of LDAPv3-plus- 107 extension(s) is not defined by this document, and MAY be defined in some 108 future document(s). 110 4. Addressing the "IESG Note" on RFCs 2251 through 2256 112 The IESG approved publishing RFCs 2251 through 2256 with an attendant 113 Note included in each document. The Note begins with.. 115 This document describes a directory access protocol that provides 116 both read and update access. Update access requires secure authenti- 117 cation, but this document does not mandate implementation of any 118 satisfactory authentication mechanisms. 120 The Note ends with this statement.. 122 Implementors are hereby discouraged from deploying LDAPv3 clients or 123 servers which implement the update functionality, until a Proposed 124 Standard for mandatory authentication in LDAPv3 has been approved and 125 published as an RFC. 127 [RFC2829] is the "Proposed Standard for mandatory authentication in 128 LDAPv3" called for in the Note. Therefore, the IESG considers the Note 129 on [RFC2251], [RFC2252], [RFC2253], [RFC2254], [RFC2255], and [RFC2256] 130 as being addressed. 132 5. Security Considerations 134 This document does not directly discuss security, although the context 135 of the aforementioned "IESG Note" is security related, as is the manner 136 in which the Note is addressed. 138 Please refer to the referenced documents, especially [RFC2829], 139 [RFC2251], and [RFC2830], for further information concerning LDAPv3 140 security. 142 I-D LDAPv3: Technical Specification October 2000 144 6. Acknowledgements 146 The authors thank Patrick Falstrom, Leslie Daigle, and Kurt Zeilenga for 147 their contributions to this document. 149 7. References 151 [RFC2119] Scott Bradner. "Key Words for use in RFCs to Indicate 152 Requirement Levels". RFC 2119, March 1997. 154 [RFC2251] M. Wahl, S. Kille and T. Howes, "Lightweight Directory 155 Access Protocol (v3)", RFC 2251, December 1997. 157 [RFC2252] M. Wahl, A. Coulbeck, T. Howes, and S. Kille, "Lightweight 158 Directory Access Protocol (v3): Attribute Syntax Defini- 159 tions", RFC 2252, December 1997. 161 [RFC2253] S. Kille, M. Wahl, and T. Howes, "Lightweight Directory 162 Access Protocol (v3): UTF-8 String Representation of Dis- 163 tinguished Names", RFC 2253, December 1997. 165 [RFC2254] T. Howes, "The String Representation of LDAP Search 166 Filters", RFC 2254, December 1997. 168 [RFC2255] T. Howes, M. Smith, "The LDAP URL Format", RFC 2255, 169 December 1997. 171 [RFC2256] M. Wahl, "A Summary of the X.500(96) User Schema for use 172 with LDAPv3", RFC 2256, December 1997. 174 [RFC2829] M. Wahl, H. Alvestrand, J. Hodges, R. Morgan. "Authentica- 175 tion Methods for LDAP", RFC 2829, May 2000. 177 [RFC2830] J. Hodges, R. Morgan, M. Wahl, "Lightweight Directory Access 178 Protocol (v3): Extension for Transport Layer Security", RFC 179 2830, May 2000. 181 8. Authors' Addresses 183 Jeff Hodges 184 Oblix, Inc. 185 18922 Forge Drive 186 Cupertino, CA 95014 187 USA 189 Phone: +1-408-861-6656 190 EMail: JHodges@oblix.com 192 I-D LDAPv3: Technical Specification October 2000 194 RL "Bob" Morgan 195 Computing and Communications 196 University of Washington 197 Seattle, WA 198 USA 200 Phone: +1-206-221-3307 201 EMail: rlmorgan@washington.edu 203 ----------------------------------- 205 9. Intellectual Property Rights Notices 207 The IETF takes no position regarding the validity or scope of any intel- 208 lectual property or other rights that might be claimed to pertain to 209 the implementation or use of the technology described in this document 210 or the extent to which any license under such rights might or might not 211 be available; neither does it represent that it has made any effort to 212 identify any such rights. Information on the IETF's procedures with 213 respect to rights in standards-track and standards-related documentation 214 can be found in BCP-11. Copies of claims of rights made available for 215 publication and any assurances of licenses to be made available, or the 216 result of an attempt made to obtain a general license or permission for 217 the use of such proprietary rights by implementors or users of this 218 specification can be obtained from the IETF Secretariat. 220 The IETF invites any interested party to bring to its attention any 221 copyrights, patents or patent applications, or other proprietary rights 222 which may cover technology that may be required to practice this stan- 223 dard. Please address the information to the IETF Executive Director. 225 10. Copyright Notice and Disclaimer 227 Copyright (C) The Internet Society (1998). All Rights Reserved. 229 This document and translations of it may be copied and furnished to 230 others, and derivative works that comment on or otherwise explain it 231 or assist in its implementation may be prepared, copied, published 232 and distributed, in whole or in part, without restriction of any 233 kind, provided that the above copyright notice and this paragraph are 234 included on all such copies and derivative works. However, this 235 document itself may not be modified in any way, such as by removing 236 the copyright notice or references to the Internet Society or other 237 Internet organizations, except as needed for the purpose of develop- 238 ing Internet standards in which case the procedures for copyrights 239 defined in the Internet Standards process must be followed, or as 240 required to translate it into languages other than English. 242 I-D LDAPv3: Technical Specification October 2000 244 The limited permissions granted above are perpetual and will not be 245 revoked by the Internet Society or its successors or assigns. 247 This document and the information contained herein is provided on an 248 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 249 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 250 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 251 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- 252 CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 254 ----------------------------------- 256 This document expires in January 2001.