idnits 2.17.1 draft-ietf-asid-leafnonleaf-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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 document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (21 November 1995) is 10384 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1777 (ref. '2') (Obsoleted by RFC 3494) ** Downref: Normative reference to an Informational draft: draft-howes-x500-schema (ref. '3') Summary: 11 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 The leaf and nonLeaf Object Classes M. Smith 2 INTERNET-DRAFT T. Howes 3 University of Michigan 4 21 November 1995 6 Definition of the leaf and nonLeaf Object Classes 7 Filename: draft-ietf-asid-leafnonleaf-00.txt 9 Status of this Memo 11 This document is an Internet-Draft. Internet-Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its 13 areas, and its working groups. Note that other groups may also 14 distribute working documents as Internet-Drafts. 16 Internet-Drafts are draft documents valid for a maximum of six 17 months and may be updated, replaced, or obsoleted by other 18 documents at any time. It is inappropriate to use Internet- 19 Drafts as reference material or to cite them other than as 20 ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check 23 the ``1id-abstracts.txt'' listing contained in the Internet- 24 Drafts Shadow Directories on ftp.is.co.za (Africa), 25 nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), 26 ds.internic.net (US East Coast), or ftp.isi.edu (US West Coast). 28 Distribution of this memo is unlimited. Editorial comments should be 29 sent to the authors (mcs@umich.edu). Technical discussion will take 30 place on the IETF ASID mailing list (ietf-asid@umich.edu). 32 This Internet Draft expires on 21 May 1995. 34 Abstract 36 Applications of X.500, LDAP, and similar directory services need to 37 be able to efficiently and unambiguously determine if an entry is a 38 leaf entry (no entries exist beneath the entry) or a non-leaf entry 39 (entries do exist beneath the entry). While some implementations use 40 proprietary object classes to allow directory clients to make the 41 distinction, there is no standard defined. This document defines two 42 object classes that may be used by all implementations to allow 43 directory clients to distinguish leaf entries from non-leaf entries. 45 Background and Intended Usage 47 This document defines two object classes (leaf and nonLeaf) that may 48 be used by X.500 [1], LDAP [2], and other directory implementations 49 to allow applications to distinguish leaf entries from non-leaf 50 entries. A leaf entry is one that does not have any other entries 51 beneath it (that is, it is not a container). A non-leaf entry is one 52 that does have other entries beneath it (that is, it is a container 53 for other entries). Each entry in the directory is one of these two 54 types. 56 Directory servers that comply with this specification should 57 automatically include the leaf object class value in all entries that 58 do not have other entries beneath them. Similarly, the nonLeaf 59 object class value should be included in all other entries. If one 60 of these two object class values is present in an entry, directory 61 clients can unambiguously know whether an entry may have other 62 entries beneath it. This capability is particularly useful when 63 browsing the directory in a hierarchical fashion. If neither value 64 is present, the client must use other means (such as a one-level or 65 subtree search based at the entry in question to see if any "child" 66 entries are present). 68 It is intended that the schema elements defined in this document will 69 be progressed according to the process defined by the Internet X.500 70 Schema Working Group [3]. 72 Definition of the leaf Object Class 74 Name: leaf 75 Description: object that does not contain other entries 76 OID: umichObjectClass.19 (1.3.6.1.4.1.250.3.19) 77 SubclassOf: top 78 MustContain: 79 MayContain: 81 Definition of the nonLeaf Object Class 83 Name: nonLeaf 84 Description: object that contains other entries 85 OID: umichObjectClass.20 (1.3.6.1.4.1.250.3.20) 86 SubclassOf: top 87 MustContain: 88 MayContain: numberOfChildren, numberOfDescendants 90 Definition of the numberOfChildren Attribute 92 Name: numberOfChildren 93 ShortName: 94 OID: umichAttributeType.62 (1.3.6.1.4.1.250.1.62) 95 Syntax: Integer 96 SizeRestriction: none 97 SingleValued: TRUE 98 MatchesFor: 100 Definition of the numberOfDescendants Attribute 102 Name: numberOfDescendants 103 ShortName: 104 OID: umichAttributeType.63 (1.3.6.1.4.1.250.1.63) 105 Syntax: Integer 106 SizeRestriction: none 107 SingleValued: TRUE 108 MatchesFor: 110 Discussion of the Object Class and Attribute Schema 112 Entries that do not have other entries beneath them belong to the 113 leaf object class. Entries that have other entries beneath them 114 belong to the nonLeaf object class. 116 The numberOfChildren attribute, if present, contains a count of the 117 entries that are listed directly below the non-leaf entry (that is, 118 the number of entries that are in the single-level beneath the 119 entry). The numberOfDescendants attribute, if present, contains a 120 count of the total number of entries that are listed anywhere beneath 121 the non-leaf entry (that is, the total number of entries that are 122 contained in the directory subtree beneath the entry). 124 References 126 [1] Information Processing Systems -- Open Systems Interconnection -- 127 The Directory: Overview of Concepts, Models and Service. ISO/IEC JTC 128 1/SC21; International Standard 9594-1, 1988. 130 [2] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access 131 Protocol", RFC 1777, Performance Systems International, University of 132 Michigan, ISODE Consortium, March 1995, 133 135 [3] Howes, T., Rossen, K., Sataluri, S., and Wright, R., "Procedures 136 for Formalizing, Evolving, and Maintaining the Internet X.500 137 Directory Schema", Internet Draft (Work In Progress) of the Schema 138 Working Group, 141 Security Considerations 143 Security considerations are not discussed in this memo. 145 Acknowledgments 147 This material is based upon work supported by the National Science 148 Foundation under Grant No. NCR-9416667. 150 Authors' Addresses 152 Mark Smith 153 University of Michigan 154 Information Technology Division 155 535 W. William St. 156 Ann Arbor, MI 48103-4943, USA 157 Phone: +1 313 764-2277 158 EMail: mcs@umich.edu 160 Tim Howes 161 University of Michigan 162 Information Technology Division 163 535 W. William St. 164 Ann Arbor, MI 48103-4943, USA 165 Phone: +1 313 747-4454 166 EMail: tim@umich.edu 168 This Internet Draft expires on 21 May 1995.