[Date Prev][Date Next] [Chronological] [Thread] [Top]

[ldapext] New I-D: 'untypedObject' object class



People often make container entries like 'ou=people,dc=foo,dc=no' which
use object class 'organizationalUnit' even though such entries do not
represent real org.units at all.  organizationalUnit just seems to get
used because no better standard object class is available.

So I've submitted a small Internet-Draft for an 'untypedObject' class to
use instead:

  http://www.ietf.org/internet-drafts/draft-furuseth-ldap-untypedobject-00.txt

Abstract:

  "This document defines an 'untypedObject' structural object class for
  the Lightweight Directory Access Protocol (LDAP) and X.500.  This is
  useful for entries with no 'natural' choice of structural object
  class, e.g. if an entry must exist even though its contents are
  uninteresting."

Please comment.  For one thing, I'd like to know if I should rename it
to e.g. 'subtreeBase', supposed to be used to the above purpose only,
or generalize (object class 'something'?) for other purposes as well.

-- 
Hallvard

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext