idnits 2.17.1 draft-howard-namedobject-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 Internet-Drafts being working documents. ** 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 page length should not exceed 58 lines per page, but there was 4 longer pages, the longest (page 1) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 68: '... STRUCTURAL MAY cn )...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (18 June 2002) is 7981 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC2251' is defined on line 92, but no explicit reference was found in the text == Unused Reference: 'RFC2252' is defined on line 96, 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 2252 (Obsoleted by RFC 4510, RFC 4512, RFC 4517, RFC 4523) Summary: 9 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Application Working Group L. Howard 3 INTERNET-DRAFT PADL Software 4 Expires in six months from 18 June 2002 5 Intended Category: Informational 7 A Structural Object Class for Arbitrary Auxiliary Object Classes 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 an Internet-Draft. Internet-Drafts are working docu- 16 ments of the Internet Engineering Task Force (IETF), its areas, and its 17 working groups. Note that other groups may also distribute working docu- 18 ments as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months. 21 Internet-Drafts may be updated, replaced, or made obsolete by other doc- 22 uments at any time. It is not appropriate to use Internet-Drafts as ref- 23 erence material or to cite them other than as a "working draft" or "work 24 in progress". 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.html 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 Distribution of this document is unlimited. 34 Abstract 36 The Lightweight Directory Access Protocol (LDAP) supports auxiliary 37 object classes for adding additional attributes to a directory entry. 39 This document defines a structural object class that may be used when no 40 other structural object class is available. 42 1. Background 43 Schema for LDAP directories often define auxiliary object classes that 44 are intended to be used with a specific structural object class. 46 For example, the posixGroup object class [RFC2307bis] is an auxiliary 47 object class that may be used to overlay POSIX group identification on 48 an existing group of distinguished names. In this case, it is suggested 49 that the groupOfUniqueNames object class be used as a structural object 50 class. However, this may sometimes be inappropriate: that groupOfUnique- 51 Names requires at least one member may make it impossible to migrate 52 existing group information. [RFC2307bis] could define a specific struc- 53 tural object class for this case (say, structuralPosixGroup), but this 54 would unnecessarily add to the proliferation of redundant schema. 56 This document defines a structural object class, namedObject, that man- 57 dates no attributes other than a common name. Arbitrary auxiliary object 58 classes may be thus associated with entries which have this as a struc- 59 tural object class. 61 2. Object Class Definitions 63 The namedObject object class defines one mandatory attribute, a common 64 name. The OID arc is iso(1) org(3) dod(6) internet(1) private(4) enter- 65 prise(1) padl(5322) namedObjectSchema(13) objectClasses(1). 67 ( 1.3.6.1.4.1.5322.13.1.1 NAME 'namedObject' SUP top 68 STRUCTURAL MAY cn ) 70 Other attributes allowed by auxiliary classes may be used for naming 71 purposes. 73 An example entry would be: 75 dn: cn=Sample Entry,dc=padl,dc=com 76 objectClass: top 77 objectClass: namedObject 78 cn: Sample Entry 80 An example entry with an auxiliary class from [RFC2307bis] would be: 82 dn: cn=wheel,ou=Groups,dc=padl,dc=com 83 objectClass: top 84 objectClass: namedObject 85 objectClass: posixGroup 86 cn: wheel 87 gidNumber: 0 88 memberUid: root 90 3. References 92 [RFC2251] 93 M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access Protocol 94 (v3)", RFC 2251, December 1997. 96 [RFC2252] 97 Wahl, M., Coulbeck, A., Howes, T., and S. Kille, "Lightweight 98 Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 99 2252, December 1997. 101 [RFC2307bis] 102 L. Howard, M. Ansari, "An Approach for Using LDAP as a Network 103 Information Service", March 2001. 105 4. Author's Address 107 Luke Howard 108 PADL Software Pty. Ltd. 109 PO Box 59 110 Central Park Vic 3145 111 Australia 112 EMail: lukeh@padl.com 114 5. Full Copyright Statement 116 Copyright (C) The Internet Society (2001). All Rights Reserved. 118 This document and translations of it may be copied and furnished to oth- 119 ers, and derivative works that comment on or otherwise explain it or 120 assist in its implementation may be prepared, copied, published and dis- 121 tributed, in whole or in part, without restriction of any kind, provided 122 that the above copyright notice and this paragraph are included on all 123 such copies and derivative works. However, this document itself may not 124 be modified in any way, such as by removing the copyright notice or ref- 125 erences to the Internet Society or other Internet organizations, except 126 as needed for the purpose of developing Internet standards in which case 127 the procedures for copyrights defined in the Internet Standards process 128 must be followed, or as required to translate it into languages other 129 than English. 131 The limited permissions granted above are perpetual and will not be 132 revoked by the Internet Society or its successors or assigns. 134 This document and the information contained herein is provided on an "AS 135 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 136 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 137 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 138 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FIT- 139 NESS FOR A PARTICULAR PURPOSE. 141 -- 142 Luke Howard | lukehoward.com 143 PADL Software | www.padl.com