idnits 2.17.1 draft-ietf-ldapbis-roadmap-02.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? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 abstract seems to contain references ([RFC2119]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. -- The draft header indicates that this document obsoletes RFC2251-2256, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 211 has weird spacing: '...for the purpo...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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.) -- The document date (1 March 2003) is 7721 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC3377' is mentioned on line 104, but not defined ** Obsolete undefined reference: RFC 3377 (Obsoleted by RFC 4510) == Missing Reference: 'Syntax' is mentioned on line 111, but not defined ** Obsolete normative reference: RFC 3383 (Obsoleted by RFC 4520) -- No information found for draft-ietf-ldapbis-models-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'Models' -- No information found for draft-ietf-ldapbis-protocol-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'Protocol' -- No information found for draft-ietf-ldapbis-authmeth-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'AuthMeth' -- No information found for draft-ietf-ldapbis-dn-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'LDAPDN' -- No information found for draft-ietf-ldapbis-filter-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'Filters' -- No information found for draft-ietf-ldapbis-url-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'LDAPURL' -- No information found for draft-ietf-ldapbis-syntaxes-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'Syntaxes' -- No information found for draft-ietf-ldapbis-user-schema-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'Schema' Summary: 9 errors (**), 0 flaws (~~), 5 warnings (==), 19 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Editor: Kurt D. Zeilenga 3 Intended Category: Standard Track OpenLDAP Foundation 4 Expires in six months 1 March 2003 5 Obsoletes: RFC 2251-2256, 2829-2830, 3377 7 LDAP: Technical Specification Road Map 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026. 15 This document is intended to be published as a Standard Track RFC. 16 Distribution of this memo is unlimited. Technical discussion of this 17 document will take place on the IETF LDAP Revision Working Group 18 mailing list . Please send editorial 19 comments directly to the author . 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other 23 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as ``work in progress.'' 29 The list of current Internet-Drafts can be accessed at 30 . The list of 31 Internet-Draft Shadow Directories can be accessed at 32 . 34 Copyright 2003, The Internet Society. All Rights Reserved. 36 Please see the Copyright section near the end of this document for 37 more information. 39 Abstract 41 The Lightweight Directory Access Protocol (LDAP) is an Internet 42 protocol for accessing distributed directory services which act in 43 accordance with X.500 data and service models. This document provides 44 a roadmap of the LDAP Technical Specification. 46 Conventions 48 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 49 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 50 document are to be interpreted as described in BCP 14 [RFC2119]. 52 1. The LDAP Technical Specification 54 The technical specification detailing version 3 of the Lightweight 55 Directory Access Protocol (LDAP), an Internet Protocol, consists of 56 this document and the following documents: 58 LDAP: Directory Information Models [Models], 59 LDAP: The Protocol [Protocol], 60 LDAP: Authentication Methods and Connection Level Security 61 Mechanisms [AuthMeth], 62 LDAP: String Representation of Distinguished Names [LDAPDN], 63 LDAP: String Representation of Search Filters [Filters], 64 LDAP: Uniform Resource Locator [LDAPURL], 65 LDAP: Syntaxes [Syntaxes], and 66 LDAP: User Schema [Schema]. 68 The terms "LDAP" and "LDAPv3" are commonly used to informally refer to 69 the protocol specified by this technical specification. The LDAP 70 suite, as defined here, should be formally identified in other 71 documents by a normative reference to this document. 73 Extensions to LDAP may be specified in other documents. Nomenclature 74 denoting such combinations of LDAP-plus-extension(s) is not defined by 75 this document but may be defined in some future document(s). 77 IANA (Internet Assigned Numbers Authority) considerations for LDAP 78 described in BCP 64 [RFC3383] apply fully to this revision of the LDAP 79 technical specification. 81 2. Relationship to X.500 83 This technical specification defines LDAP in terms of [X.500] as an 84 X.500 access mechanism. An LDAP server MUST act in accordance with 85 X.500(1993) series of International Telephone Union (ITU) 86 Recommendations when providing the service. However, it is not 87 required that an LDAP server make use of any X.500 protocols in 88 providing this service, e.g. LDAP can be mapped onto any other 89 directory system so long as the X.500 data and service models 90 [X.501][X.511] as used in LDAP is not violated in the LDAP interface. 92 This technical specification explicitly incorporates portions of 93 X.500(93). Later revisions of X.500 do not automatically apply. 95 3. Security Considerations 97 LDAP security considerations are discussed in each document comprising 98 the technical specification. 100 4. Relationship to Obsolete Specifications 102 This technical specification, as defined in Section 1, obsoletes 103 entirely the previously defined LDAP technical specification [RFC3377] 104 (which consists of RFC 2251-2256, RFC 2829-2830 and [RFC3377] itself). 105 The technical specification was significantly reorganized. 107 This document replaces RFC 3377 as well as Section 3.3 of RFC 2251. 108 [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256. 109 [Protocol] replaces the majority RFC 2251 and portions of RFC 2252. 110 [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251. 111 [Syntax] replaces the majority of RFC 2252 and portions of RFC 2256. 112 [Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC 113 2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255. 115 Each document of this specification contains appendices summarizing 116 changes to all sections of the specifications they replace. Appendix 117 A.1 of this document details changes made to RFC 3377. Appendix A.2 118 of this document details changes made to Section 3.3 of RFC 2251. 120 5. Acknowledgments 122 This document is based largely on RFC 3377 by J. Hodges and R. 123 Morgan, a product of the LDAPBIS and LDAPEXT Working Groups. The 124 document also borrows from RFC 2251 by M. Wahl, T. Howes, and S. 125 Kille, a product of the ASID Working Group. 127 This document is a product of the IETF LDAPBIS Working Group. 129 6. Author's Address 131 Kurt Zeilenga 132 E-mail: 134 7. References 135 7.1. Normative References 137 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 138 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 140 [RFC3383] K. Zeilenga, "IANA Considerations for LDAP", BCP 64 (also 141 RFC 3383), September 2002. 143 [Models] K. Zeilenga (editor), "LDAP: Directory Information Models", 144 draft-ietf-ldapbis-models-xx.txt, a work in progress. 146 [Protocol] J. Sermersheim (editor), "LDAP: The Protocol", 147 draft-ietf-ldapbis-protocol-xx.txt, a work in progress. 149 [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods and 150 Connection Level Security Mechanisms", 151 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. 153 [LDAPDN] K. Zeilenga (editor), "LDAP: String Representation of 154 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work 155 in progress. 157 [Filters] M. Smith (editor), LDAPbis WG, "LDAP: String Representation 158 of Search Filters", draft-ietf-ldapbis-filter-xx.txt, a 159 work in progress. 161 [LDAPURL] M. Smith (editor), "LDAP: Uniform Resource Locator", 162 draft-ietf-ldapbis-url-xx.txt, a work in progress. 164 [Syntaxes] S. Legg (editor), "LDAP: Syntaxes", 165 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress. 167 [Schema] K. Dally (editor), "LDAP: User Schema", 168 draft-ietf-ldapbis-user-schema-xx.txt, a work in progress. 170 [X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts, 171 Models and Service", 1993. 173 [X.501] ITU-T Rec. X.501, "The Directory: Models", 1993. 175 [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service 176 Definition", 1993. 178 7.2. Informative References 180 None. 182 Appendix A. Changes to Previous Documents 184 This appendix outlines changes this document makes relative 185 to the documents it replaces (in whole or in part). 187 Appendix A.1. Changes to RFC 3377 189 This document is nearly a complete rewrite of RFC 3377 as 190 much of the material of RFC 3377 is no longer applicable. 191 These changes include defining the terms "LDAP" and 192 "LDAPv3" to refer to this revision of the technical 193 specification. 195 Appendix A.2. Changes to Section 3.3 of RFC 2251 197 The section was modified slightly (the word "document" was 198 replaced with "technical specification") to clarify that it 199 applies to the entire LDAP technical specification. 201 Copyright 2003, The Internet Society. All Rights Reserved. 203 This document and translations of it may be copied and furnished to 204 others, and derivative works that comment on or otherwise explain it 205 or assist in its implementation may be prepared, copied, published and 206 distributed, in whole or in part, without restriction of any kind, 207 provided that the above copyright notice and this paragraph are 208 included on all such copies and derivative works. However, this 209 document itself may not be modified in any way, such as by removing 210 the copyright notice or references to the Internet Society or other 211 Internet organizations, except as needed for the purpose of 212 developing Internet standards in which case the procedures for 213 copyrights defined in the Internet Standards process must be followed, 214 or as required to translate it into languages other than English. 216 The limited permissions granted above are perpetual and will not be 217 revoked by the Internet Society or its successors or assigns. 219 This document and the information contained herein is provided on an 220 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET 221 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 222 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 223 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 224 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.