idnits 2.17.1 draft-zeilenga-ldap-features-05.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 215 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 (26 May 2003) is 7639 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 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) ** Obsolete normative reference: RFC 3377 (Obsoleted by RFC 4510) ** Obsolete normative reference: RFC 3383 (Obsoleted by RFC 4520) -- No information found for draft-zeilenga-ldap-opattrs-xx - is the name correct? -- No information found for draft-zeilenga-ldap-t-f-xx - is the name correct? Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 4 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 26 May 2003 6 Feature Discovery in LDAP 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 an Standard Track document. 16 Distribution of this memo is unlimited. Technical discussion of this 17 document will take place on the IETF LDAP Extension 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 The Lightweight Directory Access Protocol (LDAP) is an extensible 42 protocol with numerous elective features. This document introduces a 43 general mechanism for discovery of elective features and extensions 44 which cannot be discovered using existing mechanisms. 46 1. Background and Intended Use 48 The Lightweight Directory Access Protocol (LDAP) [RFC3377] is an 49 extensible protocol with numerous elective features. LDAP provides 50 mechanisms for a client to discover supported protocol versions, 51 controls, extended operations, Simple Authentication and Security 52 Layer (SASL) mechanisms, and subschema information. However, these 53 mechanisms are not designed to support general feature discovery. 55 This document describes a simple, general-purpose mechanism which 56 clients may use to discover the set of elective features supported by 57 a server. For example, this mechanism could be used by a client to 58 discover whether or not the server supports requests for all 59 operational attributes, e.g. "+" [OPATTRS]. As another example, this 60 mechanism could be used to discover absolute true, e.g. "(&)" and 61 false, e.g. "(|)", search filters [T-F] support. 63 This document extends the LDAP Protocol Mechanism registry [RFC3383] 64 to support registration of values of the supportedFeatures attribute. 65 This registry is managed by the Internet Assigned Numbers Authority 66 (IANA). 68 Schema definitions are provided using LDAP description formats 69 [RFC2252]. Definitions provided here are formatted (line wrapped) for 70 readability. 72 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 73 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 74 document are to be interpreted as described in BCP 14 [RFC2119]. 76 2. Discovery of supported features 78 Each elective feature whose support may be discovered SHALL be 79 identified by an Object Identifier (OID). A server advertises its 80 support for a given feature by providing the OID associated with the 81 feature as a value of the 'supportedFeatures' attribute held in the 82 root DSE. A client may examine the values of this attribute to 83 determine if a particular feature is supported by the server. A 84 client MUST ignore values it doesn't recognize as they refer to 85 elective features it doesn't implement. 87 Features associated with Standard Track protocol mechanisms MUST be 88 registered. Features associated with other protocol mechanisms SHOULD 89 be registered. Procedures for registering protocol mechanisms are are 90 described in [RFC3383]. "Feature" should be placed in the usage field 91 of the submitted LDAP Protocol Mechanism template. 93 The 'supportedFeatures' attribute type is described as follows: 95 ( 1.3.6.1.4.1.4203.1.3.5 96 NAME 'supportedFeatures' 97 DESC 'features supported by the server' 98 EQUALITY objectIdentifierMatch 99 SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 100 USAGE dSAOperation ) 102 Servers MUST be capable of recognizing this attribute type by the name 103 'supportedFeatures'. Servers MAY recognize the attribute type by 104 other names. 106 4. Security Considerations 108 As rogue clients can discover features of a server by other means 109 (such as by trial and error), this feature discovery mechanism is not 110 believed to introduce any new security risk to LDAP. 112 5. IANA Considerations 114 5.1. Registration of Features as Protocol Mechanisms 116 Future specifications detailing LDAP features are to register each 117 feature as a LDAP Protocol Mechanism per guidance given in BCP 64 118 [RFC3383]. A usage of "Feature" in a Protocol Mechanism registration 119 template indicates that the value to be registered is associated with 120 an LDAP feature. 122 5.2. Registration of the supportedFeatures descriptor 124 It is requested that IANA register upon Standards Action the LDAP 125 'supportedFeatures' descriptor. The following registration template 126 is suggested: 128 Subject: Request for LDAP Descriptor Registration 129 Descriptor (short name): supportedFeatures 130 Object Identifier: 1.3.6.1.4.1.4203.1.3.5 131 Person & email address to contact for further information: 132 Kurt Zeilenga 133 Usage: Attribute Type 134 Specification: RFC XXXX 135 Author/Change Controller: IESG 137 This OID was assigned [ASSIGN] by OpenLDAP Foundation under its IANA 138 assigned private enterprise allocation [PRIVATE] for use in this 139 specification. 141 6. Acknowledgment 143 This document is based upon input from the IETF LDAPEXT working group. 145 7. Author's Address 147 Kurt D. Zeilenga 148 OpenLDAP Foundation 149 151 8. Normative References 153 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 154 Requirement Levels", BCP 14 (also RFC 2119), March 1997. 156 [RFC2252] Wahl, M., A. Coulbeck, T. Howes, and S. Kille, 157 "Lightweight Directory Access Protocol (v3): Attribute 158 Syntax Definitions", RFC 2252, December 1997. 160 [RFC3377] Hodges, J. and R. Morgan, "Lightweight Directory Access 161 Protocol (v3): Technical Specification", RFC 3377, 162 September 2002. 164 [RFC3383] Zeilenga, K., "IANA Considerations for LDAP", BCP 64 165 (also RFC 3383), September 2002. 167 9. Informative References 169 [OPATTRS] Zeilenga, K., "LDAPv3: All Operational Attributes", 170 draft-zeilenga-ldap-opattrs-xx.txt, a work in progress. 172 [T-F] Zeilenga, K., "LDAP True/False Filters", 173 draft-zeilenga-ldap-t-f-xx.txt, a work in progress. 175 [ASSIGN] OpenLDAP Foundation, "OpenLDAP OID Delegations", 176 http://www.openldap.org/foundation/oid-delegate.txt. 178 [PRIVATE] IANA, "Private Enterprise Numbers", 179 http://www.iana.org/assignments/enterprise-numbers. 181 Intellectual Property Rights 183 The IETF takes no position regarding the validity or scope of any 184 intellectual property or other rights that might be claimed to pertain 185 to the implementation or use of the technology described in this 186 document or the extent to which any license under such rights might or 187 might not be available; neither does it represent that it has made any 188 effort to identify any such rights. Information on the IETF's 189 procedures with respect to rights in standards-track and 190 standards-related documentation can be found in BCP-11. Copies of 191 claims of rights made available for publication and any assurances of 192 licenses to be made available, or the result of an attempt made to 193 obtain a general license or permission for the use of such proprietary 194 rights by implementors or users of this specification can be obtained 195 from the IETF Secretariat. 197 The IETF invites any interested party to bring to its attention any 198 copyrights, patents or patent applications, or other proprietary 199 rights which may cover technology that may be required to practice 200 this standard. Please address the information to the IETF Executive 201 Director. 203 Full Copyright 205 Copyright (C) The Internet Society (2003). All Rights Reserved. 207 This document and translations of it may be copied and furnished to 208 others, and derivative works that comment on or otherwise explain it 209 or assist in its implmentation may be prepared, copied, published and 210 distributed, in whole or in part, without restriction of any kind, 211 provided that the above copyright notice and this paragraph are 212 included on all such copies and derivative works. However, this 213 document itself may not be modified in any way, such as by removing 214 the copyright notice or references to the Internet Society or other 215 Internet organizations, except as needed for the purpose of 216 developing Internet standards in which case the procedures for 217 copyrights defined in the Internet Standards process must be followed, 218 or as required to translate it into languages other than English.