Compound (Families of) Entries
draft-chadwick-families-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Dr. David W. Chadwick | ||
Last updated | 1999-06-14 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
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
This document describes protocol support, in the form of LDAP controls, for compound entries. A compound entry logically allows collections of attributes to be grouped together as though they were present in the single compound entry, whereas in fact they are held in a hierarchical set of entries beneath the compound entry. The LDAP controls allow the user to treat a compound entry as either separate entries or as a single compound entry when both searching, retrieving and deleting information from the DIT. Compound entries are briefly described here and a full description of them can be found in the draft version of X.500 (2000)[FPDAM].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)