Definition of the leaf and nonLeaf Object Classes
draft-ietf-asid-leafnonleaf-00
| Document | Type |
Expired Internet-Draft
(asid WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tim Howes , Mark C. Smith | ||
| Last updated | 1995-11-21 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Applications of X.500, LDAP, and similar directory services need to be able to efficiently and unambiguously determine if an entry is a leaf entry (no entries exist beneath the entry) or a non-leaf entry (entries do exist beneath the entry). While some implementations use proprietary object classes to allow directory clients to make the distinction, there is no standard defined. This document defines two object classes that may be used by all implementations to allow directory clients to distinguish leaf entries from non-leaf entries.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)