idnits 2.17.1 draft-zeilenga-ldap-t-f-08.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 213 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 (3 February 2004) is 7387 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: 'RFC3674' is mentioned on line 91, but not defined ** Obsolete undefined reference: RFC 3674 (Obsoleted by RFC 4512) == Missing Reference: 'FEATURES' is mentioned on line 106, but not defined == Unused Reference: 'Features' is defined on line 143, but no explicit reference was found in the text ** 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) ** Obsolete normative reference: RFC 3674 (ref. 'Features') (Obsoleted by RFC 4512) -- 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: 9 errors (**), 0 flaws (~~), 6 warnings (==), 5 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 3 February 2004 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 mailing list 18 . Please send editorial comments directly to the 19 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 (2004). 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 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 assertions by allowing empty 'and' and 'or' in Search filters 64 [RFC2251] and extends the filter string representation [RFC2254] to 65 allow empty filter lists. 67 It is noted that certain search operations, such as those used to 68 retrieve subschema subschema information [RFC2251], require use of 69 particular filters. This document does not change these requirements. 71 This feature is intended to allow a more direct mapping between DAP 72 and LDAP (as needed to implement DAP-to-LDAP gateways). 74 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 75 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 76 document are to be interpreted as described in BCP 14 [RFC2119]. 78 2. Absolute True and False Filters 80 Implementations of this extension SHALL allow 'and' and 'or' choices 81 with zero filter elements. 83 An 'and' filter consisting of an empty set of filters SHALL evaluate 84 to True. This filter is represented by the string "(&)". 86 An 'or' filter consisting of an empty set of filters SHALL evaluate to 87 False. This filter is represented by the string "(|)". 89 Servers supporting this feature SHOULD publish the Object Identifier 90 (OID) 1.3.6.1.4.1.4203.1.5.3 as a value of the 'supportedFeatures' 91 [RFC3674] attribute in the root DSE. 93 Clients supporting this feature SHOULD NOT use the feature unless they 94 have knowledge the server supports it. 96 3. Security Considerations 98 The (re)introduction of absolute True and False filters is not 99 believed to raise any new security considerations. 101 Implementors of this (or any) LDAPv3 extension should be familiar with 102 general LDAPv3 security considerations [RFC3377]. 104 4. IANA Considerations 106 Registration of this feature is requested [FEATURES][RFC3383]. 108 Subject: Request for LDAP Protocol Mechanism Registration 109 Object Identifier: 1.3.6.1.4.1.4203.1.5.3 110 Description: True/False filters 111 Person & email address to contact for further information: 112 Kurt Zeilenga 113 Usage: Feature 114 Specification: RFC XXXX 115 Author/Change Controller: IESG 116 Comments: none 118 This OID was assigned [ASSIGN] by OpenLDAP Foundation, under its 119 IANA-assigned private enterprise allocation [PRIVATE], for use in this 120 specification. 122 5. Author's Address 124 Kurt D. Zeilenga 125 OpenLDAP Foundation 126 128 6. Normative References 130 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 131 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 133 [RFC2251] Wahl, M., T. Howes and S. Kille, "Lightweight Directory 134 Access Protocol (v3)", RFC 2251, December 1997. 136 [RFC2254] Howes, T., "A String Representation of LDAP Search 137 Filters", RFC 2254, December 1997. 139 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access 140 Protocol (v3): Technical Specification", RFC 3377, 141 September 2002. 143 [Features] Zeilenga, K., "Feature Discovery in LDAP", RFC 3674, 144 December 2003. 146 7. Informative References 148 [RFC1777] Yeong, W., Howes, T., and S. Kille, "Lightweight 149 Directory Access Protocol", RFC 1777, March 1995. 151 [RFC1960] Howes, T., "A String Representation of LDAP Search 152 Filters", RFC 1960, June 1996. 154 [RFC3383] Zeilenga, K., "IANA Considerations for LDAP", BCP 64 155 (also RFC 3383), September 2002. 157 [RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol 158 version 2 (LDAPv2) to Historic Status", RFC 3494, March 159 2003. 161 [X.500] International Telecommunication Union - 162 Telecommunication Standardization Sector, "The Directory 163 -- Overview of concepts, models and services," 164 X.500(1993) (also ISO/IEC 9594-1:1994). 166 [X.501] International Telecommunication Union - 167 Telecommunication Standardization Sector, "The Directory 168 -- Models," X.501(1993) (also ISO/IEC 9594-2:1994). 170 [X.511] International Telecommunication Union - 171 Telecommunication Standardization Sector, "The 172 Directory: Abstract Service Definition", X.511(1993). 174 [ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations", 175 http://www.openldap.org/foundation/oid-delegate.txt. 177 [PRIVATE] IANA, "Private Enterprise Numbers", 178 http://www.iana.org/assignments/enterprise-numbers. 180 Intellectual Property Rights 181 The IETF takes no position regarding the validity or scope of any 182 intellectual property or other rights that might be claimed to pertain 183 to the implementation or use of the technology described in this 184 document or the extent to which any license under such rights might or 185 might not be available; neither does it represent that it has made any 186 effort to identify any such rights. Information on the IETF's 187 procedures with respect to rights in standards-track and 188 standards-related documentation can be found in BCP-11. Copies of 189 claims of rights made available for publication and any assurances of 190 licenses to be made available, or the result of an attempt made to 191 obtain a general license or permission for the use of such proprietary 192 rights by implementors or users of this specification can be obtained 193 from the IETF Secretariat. 195 The IETF invites any interested party to bring to its attention any 196 copyrights, patents or patent applications, or other proprietary 197 rights which may cover technology that may be required to practice 198 this standard. Please address the information to the IETF Executive 199 Director. 201 Full Copyright 203 Copyright (C) The Internet Society (2004). All Rights Reserved. 205 This document and translations of it may be copied and furnished to 206 others, and derivative works that comment on or otherwise explain it 207 or assist in its implementation may be prepared, copied, published and 208 distributed, in whole or in part, without restriction of any kind, 209 provided that the above copyright notice and this paragraph are 210 included on all such copies and derivative works. However, this 211 document itself may not be modified in any way, such as by removing 212 the copyright notice or references to the Internet Society or other 213 Internet organizations, except as needed for the purpose of 214 developing Internet standards in which case the procedures for 215 copyrights defined in the Internet Standards process must be followed, 216 or as required to translate it into languages other than English.