idnits 2.17.1 draft-zeilenga-ldap-t-f-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 160 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 (17 May 2002) is 8015 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) ** Obsolete normative reference: RFC 2251 (Obsoleted by RFC 4510, RFC 4511, RFC 4512, RFC 4513) ** Obsolete normative reference: RFC 2254 (Obsoleted by RFC 4510, RFC 4515) -- No information found for draft-ietf-ldapbis-ldapv3-ts-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'LDAPTS' -- No information found for draft-zeilenga-ldap-features-xx - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'FEATURES' -- Obsolete informational reference (is this intentional?): RFC 1777 (Obsoleted by RFC 3494) -- Obsolete informational reference (is this intentional?): RFC 1960 (Obsoleted by RFC 2254) Summary: 6 errors (**), 0 flaws (~~), 2 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Kurt D. Zeilenga 3 Intended Category: Standard Track OpenLDAP Foundation 4 Expires in six months 17 May 2002 6 LDAP True/False Filters 7 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 This document is intended to be, after appropriate review and 15 revision, submitted to the RFC Editor as a Standard Track document. 16 Distribution of this memo is unlimited. Technical discussion of this 17 document will take place on the IETF LDAP Extensions 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 This document extends the Lightweight Directory Access Protocol (LDAP) 42 to support absolute True and False filters based upon similar 43 capabilities found in X.500 directory systems. The document also 44 extends the String Representation of LDAP Search Filters to support 45 these filters. 47 1. Background and Intended Use 49 The X.500 Directory Access Protocol (DAP) [X.511] supports absolute 50 True and False assertions. An 'and' filter with zero elements always 51 evaluates to True. An 'or' filter with zero elements always evaluates 52 to False. These filters are commonly used when requesting DSA- 53 specific Entries (DSEs) which do not necessarily have objectClass 54 attributes. That is, where "(objectClass=*)" may evaluate to False. 56 While LDAPv2 [RFC1777] placed no restriction on the number of elements 57 in 'and' and 'or' filter sets, the LDAPv2 string representation 58 [RFC1960] could not represent empty 'and' and 'or' filter sets. Due 59 to this, LDAPv3 [RFC2251] required 'and' and 'or' filter sets to have 60 at least one element. Hence, LDAPv3 does not provide absolute True or 61 False filters. 63 This documents extends LDAPv3 [RFC2251] to support absolute True and 64 False matches by allowing empty 'and' and 'or' and extends the filter 65 string representation [RFC2254] to allow empty filter lists. 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 BCP 14 [RFC2119]. 71 2. Absolute True and False Filters 73 Implementations of this extension SHALL allow 'and' and 'or' choices 74 with zero filter elements. 76 An 'and' Filter consisting of an empty set of filters SHALL evaluate 77 to True. This filter is to represented by the string "(&)". 79 An 'or' Filter consisting of an empty set of filters SHALL evaluate to 80 False. This filter is to represented by the string "(|)". 82 Servers supporting this feature SHOULD publish the Object Identifier 83 1.3.6.1.4.1.4203.1.5.3 as a value of the supportedFeatures [FEATURES] 84 attribute in the root DSE. 86 Clients supporting this feature SHOULD NOT use the feature unless they 87 have knowledge the server supports it. 89 3. Security Considerations 91 The (re)introduction of absolute True and False filters does not raise 92 any new security considerations. 94 Implementors of this (or any) LDAP extension should be familiar with 95 general LDAP general security considerations [LDAPTS]. 97 4. IANA Considerations 99 No IANA assignments are requested. 101 This document uses the OID 1.3.6.1.4.1.4203.1.5.3 to identify the 102 feature described above. This OID was assigned [ASSIGN] by OpenLDAP 103 Foundation under its IANA assigned private enterprise allocation 104 [PRIVATE] for use in this specification. 106 5. Author's Address 108 Kurt D. Zeilenga 109 OpenLDAP Foundation 110 112 6. Normative References 114 [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate 115 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 117 [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access 118 Protocol (v3)", RFC 2251, December 1997. 120 [RFC2254] T. Howes, "A String Representation of LDAP Search Filters", 121 RFC 2254, December 1997. 123 [LDAPTS] J. Hodges, R. Morgan, "Lightweight Directory Access 124 Protocol (v3): Technical Specification", 125 draft-ietf-ldapbis-ldapv3-ts-xx.txt (a work in progress). 127 [FEATURES] K. Zeilenga, "Feature Discovery in LDAP", 128 draft-zeilenga-ldap-features-xx.txt (a work in progress). 130 7. Informative References 132 [RFC1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory 133 Access Protocol", RFC 1777, March 1995. 135 [RFC1960] T. Howes, "A String Representation of LDAP Search Filters", 136 RFC 1960, June 1996. 138 [X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts, 139 Models and Service", 1993. 141 [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service 142 Definition", 1993. 144 [ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations", 145 http://www.openldap.org/foundation/oid-delegate.txt. 147 [PRIVATE] IANA, "Private Enterprise Numbers", 148 http://www.iana.org/assignments/enterprise-numbers. 150 Copyright 2002, The Internet Society. All Rights Reserved. 152 This document and translations of it may be copied and furnished to 153 others, and derivative works that comment on or otherwise explain it 154 or assist in its implementation may be prepared, copied, published and 155 distributed, in whole or in part, without restriction of any kind, 156 provided that the above copyright notice and this paragraph are 157 included on all such copies and derivative works. However, this 158 document itself may not be modified in any way, such as by removing 159 the copyright notice or references to the Internet Society or other 160 Internet organizations, except as needed for the purpose of 161 developing Internet standards in which case the procedures for 162 copyrights defined in the Internet Standards process must be followed, 163 or as required to translate it into languages other than English. 165 The limited permissions granted above are perpetual and will not be 166 revoked by the Internet Society or its successors or assigns. 168 This document and the information contained herein is provided on an 169 "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET 170 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, 171 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 172 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 173 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.