idnits 2.17.1 draft-zeilenga-ldap-t-f-06.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: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 205 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 (30 June 2003) is 7599 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) ** Obsolete normative reference: RFC 3377 (Obsoleted by RFC 4510) -- 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) -- Obsolete informational reference (is this intentional?): RFC 3383 (Obsoleted by RFC 4520) Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 7 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 30 June 2003 6 LDAP Absolute True and 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 comments 19 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 (C) The Internet Society (2003). All Rights Reserved. 36 Please see the Full Copyright section near the end of this document 37 for 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][RFC3494] placed no restriction on the number of 57 elements in 'and' and 'or' filter sets, the LDAPv2 string 58 representation [RFC1960] could not represent empty 'and' and 'or' 59 filter sets. Due to this, absolute True or False filters were 60 (unfortunately) eliminated from LDAPv3 [RFC3377]. 62 This documents extends LDAPv3 to support absolute True and False 63 matches by allowing empty 'and' and 'or' in Search filters [RFC2251] 64 and extends the filter string representation [RFC2254] to allow empty 65 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 represented by the string "(&)". 79 An 'or' filter consisting of an empty set of filters SHALL evaluate to 80 False. This filter is represented by the string "(|)". 82 Servers supporting this feature SHOULD publish the Object Identifier 83 (OID) 1.3.6.1.4.1.4203.1.5.3 as a value of the supportedFeatures 84 [FEATURES] 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 is not 92 believed to raise any new security considerations. 94 Implementors of this (or any) LDAPv3 extension should be familiar with 95 general LDAPv3 security considerations [RFC3377]. 97 4. IANA Considerations 99 The OID 1.3.6.1.4.1.4203.1.5.3 identifies the feature described above. 100 This OID was assigned [ASSIGN] by OpenLDAP Foundation, under its 101 IANA-assigned private enterprise allocation [PRIVATE], for use in this 102 specification. 104 Registration of this feature is requested [FEATURES][RFC3383]. 106 Subject: Request for LDAP Protocol Mechanism Registration 107 Object Identifier: 1.3.6.1.4.1.4203.1.5.3 108 Description: T/F Filters 109 Person & email address to contact for further information: 110 Kurt Zeilenga 111 Usage: Feature 112 Specification: RFC XXXX 113 Author/Change Controller: IESG 114 Comments: none 116 5. Author's Address 118 Kurt D. Zeilenga 119 OpenLDAP Foundation 120 122 6. Normative References 124 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 125 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 127 [RFC2251] Wahl, M., T. Howes and S. Kille, "Lightweight Directory 128 Access Protocol (v3)", RFC 2251, December 1997. 130 [RFC2254] Howes, T., "A String Representation of LDAP Search 131 Filters", RFC 2254, December 1997. 133 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access 134 Protocol (v3): Technical Specification", RFC 3377, 135 September 2002. 137 [FEATURES] Zeilenga, K., "Feature Discovery in LDAP", 138 draft-zeilenga-ldap-features-xx.txt, a work in progress. 140 7. Informative References 142 [RFC1777] Yeong, W., Howes, T., and S. Kille, 143 "Lightweight Directory Access Protocol", RFC 1777, March 144 1995. 146 [RFC1960] Howes, T., "A String Representation of LDAP Search 147 Filters", RFC 1960, June 1996. 149 [RFC3383] Zeilenga, K., "IANA Considerations for LDAP", BCP 64 150 (also RFC 3383), September 2002. 152 [RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol 153 version 2 (LDAPv2) to Historic Status", RFC 3494, March 154 2003. 156 [X.500] International Telecommunication Union - 157 Telecommunication Standardization Sector, "The Directory 158 -- Overview of concepts, models and services," 159 X.500(1993) (also ISO/IEC 9594-1:1994). 161 [X.501] International Telecommunication Union - 162 Telecommunication Standardization Sector, "The Directory 163 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994). 165 [ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations", 166 http://www.openldap.org/foundation/oid-delegate.txt. 168 [PRIVATE] IANA, "Private Enterprise Numbers", 169 http://www.iana.org/assignments/enterprise-numbers. 171 Intellectual Property Rights 173 The IETF takes no position regarding the validity or scope of any 174 intellectual property or other rights that might be claimed to pertain 175 to the implementation or use of the technology described in this 176 document or the extent to which any license under such rights might or 177 might not be available; neither does it represent that it has made any 178 effort to identify any such rights. Information on the IETF's 179 procedures with respect to rights in standards-track and 180 standards-related documentation can be found in BCP-11. Copies of 181 claims of rights made available for publication and any assurances of 182 licenses to be made available, or the result of an attempt made to 183 obtain a general license or permission for the use of such proprietary 184 rights by implementors or users of this specification can be obtained 185 from the IETF Secretariat. 187 The IETF invites any interested party to bring to its attention any 188 copyrights, patents or patent applications, or other proprietary 189 rights which may cover technology that may be required to practice 190 this standard. Please address the information to the IETF Executive 191 Director. 193 Full Copyright 195 Copyright (C) The Internet Society (2003). All Rights Reserved. 197 This document and translations of it may be copied and furnished to 198 others, and derivative works that comment on or otherwise explain it 199 or assist in its implmentation may be prepared, copied, published and 200 distributed, in whole or in part, without restriction of any kind, 201 provided that the above copyright notice and this paragraph are 202 included on all such copies and derivative works. However, this 203 document itself may not be modified in any way, such as by removing 204 the copyright notice or references to the Internet Society or other 205 Internet organizations, except as needed for the purpose of 206 developing Internet standards in which case the procedures for 207 copyrights defined in the Internet Standards process must be followed, 208 or as required to translate it into languages other than English.