idnits 2.17.1 draft-ietf-ldapbis-roadmap-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? ** 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 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 208 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 (21 February 2002) is 8093 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: 'Syntax' is mentioned on line 105, but not defined -- 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' -- No information found for draft-ietf-ldapbis-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'LDAPIANA' -- Obsolete informational reference (is this intentional?): RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) -- No information found for draft-ietf-ldapbis-ldapv3-ts-xx - is the name correct? Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 23 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: 21 August 2002 21 February 2002 5 Obsoletes: RFC 2251-2256, 2829-2830, LDAPTS 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 2002, 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 protocol suite, as defined here, should be formally identified in 71 other 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 considerations for LDAP [LDAPIANA] apply fully to this revision 78 of the LDAP technical specification. 80 2. Relationship to X.500 82 This technical specification defines LDAP in terms of [X.500] as an 83 X.500 access mechanism. An LDAP server MUST act in accordance with 84 X.500(1993) series of ITU recommendations when providing the service. 85 However, it is not required that an LDAP server make use of any X.500 86 protocols in providing this service, e.g. LDAP can be mapped onto any 87 other directory system so long as the X.500 data and service model as 88 used in LDAP is not violated in the LDAP interface. 90 3. Security Considerations 91 LDAP security considerations are discussed in each document comprising 92 the technical specification. 94 4. Relationship to Obsolete Specifications 96 This technical specification, as defined in Section 1, obsoletes 97 entirely the previously defined LDAP technical specification [LDAPTS] 98 (which consists of RFC 2251-2256, RFC 2829-2830 and [LDAPTS] itself). 99 The technical specification was significantly reorganized. 101 This document replaces replaces [LDAPTS] as well as Section 3.3 of RFC 102 2251. [Models] replaces portions of RFC 2251, RFC 2252 and RFC 2256. 103 [Protocol] replaces the majority RFC 2251 and portions of RFC 2252. 104 [AuthMeth] replaces RFC 2829, RFC 2830, and portions of RFC 2251. 105 [Syntax] replaces the majority of RFC 2252 and portions of RFC 2256. 106 [Schema] replaces the majority of RFC 2256. [LDAPDN] replaces RFC 107 2253. [Filters] replaces RFC 2254. [LDAPURL] replaces RFC 2255. 109 Each document of this specification contains appendices detailing 110 changes to all sections of the specifications they replace. Appendix 111 A.1 of this document details changes made to [LDAPTS]. Appendix A.2 112 of this document details changes made to Section 3.3 of RFC 2251. 114 5. Acknowledgments 116 This document is based largely on [LDAPTS] by J. Hodges and R. 117 Morgan, a product of the LDAP Extensions Working Group. The document 118 also borrows from [RFC2251] by M. Wahl, T. Howes, and S. Kille, a 119 product of the ASID Working Group. 121 6. Author's Address 123 Kurt Zeilenga 124 E-mail: 126 7. References 128 7.1. Normative References 130 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 131 Requirement Levels", RFC 2119, March 1997. 133 [Models] K. Zeilenga (editor), "LDAP: Directory Information Models", 134 draft-ietf-ldapbis-models-xx.txt, a work in progress. 136 [Protocol] J. Sermersheim (editor), "LDAP: The Protocol", 137 draft-ietf-ldapbis-protocol-xx.txt, a work in progress. 139 [AuthMeth] R. Harrison (editor), "LDAP: Authentication Methods and 140 Connection Level Security Mechanisms", 141 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. 143 [LDAPDN] K. Zeilenga (editor), "LDAP: String Representation of 144 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work 145 in progress. 147 [Filters] M. Smith (editor), LDAPbis WG, "LDAP: String Representation 148 of Search Filters", draft-ietf-ldapbis-filter-xx.txt, a 149 work in progress. 151 [LDAPURL] M. Smith (editor), "LDAP: Uniform Resource Locator", 152 draft-ietf-ldapbis-url-xx.txt, a work in progress. 154 [Syntaxes] K. Dally (editor), "LDAP: Syntaxes", 155 draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress. 157 [Schema] K. Dally (editor), "LDAP: User Schema", 158 draft-ietf-ldapbis-user-schema-xx.txt, a work in progress. 160 [LDAPIANA] K. Zeilenga, "IANA Considerations for LDAP", 161 draft-ietf-ldapbis-xx.txt (a work in progress). 163 [X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts, 164 Models and Service", 1993. 166 [X.501] ITU-T Rec. X.501, "The Directory: Models", 1993. 168 [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service 169 Definition", 1993. 171 7.2. Informative References 173 [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access 174 Protocol (v3)", RFC 2251, December 1997. 176 [LDAPTS] J. Hodges, R.L. Morgan, "Lightweight Directory Access 177 Protocol (v3): Technical Specification", 178 draft-ietf-ldapbis-ldapv3-ts-xx.txt. 180 Appendix A. Changes to Previous Documents 181 This appendix outlines changes this document makes relative to the 182 documents it replaces (in whole or in part). 184 Appendix A.1. Changes to [LDAPTS] 186 This document is nearly a complete rewrite of [LDAPTS] as much of the 187 material of [LDAPTS] is no longer applicable. These changes include 188 defining the term "LDAP" in addition to "LDAPv3" and using "LDAP" in 189 favor of "LDAPv3" for consistency with the remainder of the technical 190 specification. 192 Appendix A.2. Changes to Section 3.3 of RFC 2251 194 The section was modified slightly (the word "document" was replaced 195 with "technical specification") to clarify that it applies to the 196 entire LDAP technical specification. 198 Copyright 2002, The Internet Society. All Rights Reserved. 200 This document and translations of it may be copied and furnished to 201 others, and derivative works that comment on or otherwise explain it 202 or assist in its implementation may be prepared, copied, published and 203 distributed, in whole or in part, without restriction of any kind, 204 provided that the above copyright notice and this paragraph are 205 included on all such copies and derivative works. However, this 206 document itself may not be modified in any way, such as by removing 207 the copyright notice or references to the Internet Society or other 208 Internet organizations, except as needed for the purpose of 209 developing Internet standards in which case the procedures for 210 copyrights defined in the Internet Standards process must be followed, 211 or as required to translate it into languages other than English. 213 The limited permissions granted above are perpetual and will not be 214 revoked by the Internet Society or its successors or assigns. 216 This document and the information contained herein is provided on an 217 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET 218 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 219 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 220 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 221 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.