[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
groupOfName (was: IETF ldapbis WG Last Call: draft-ietf-ldapbis-user-schema-05.txt)
- To: ietf-ldapbis@OpenLDAP.org
- Subject: groupOfName (was: IETF ldapbis WG Last Call: draft-ietf-ldapbis-user-schema-05.txt)
- From: Michael Ströder <michael@stroeder.com>
- Date: Wed, 04 Jun 2003 23:38:38 +0200
- In-reply-to: <1395B4B334FCC143B36AF788E68B63811E3F7C@ausyms21.ca.com>
- References: <1395B4B334FCC143B36AF788E68B63811E3F7C@ausyms21.ca.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425
HI!
Would it be a big problem or out of scope of ldapbis to change declaration
of object class 'groupOfNames' so that attribute 'member' is not required ?
I'd like to propose changing it to:
( 2.5.6.9 NAME 'groupOfNames'
SUP top
STRUCTURAL
MUST ( cn )
MAY ( businessCategory $
member $
seeAlso $
owner $
ou $
o $
description ) )
Similar change for object class 'groupOfUniqueNames' and attribute
'uniqueMember'.
It's rather cumbersome having to add a dummy value for 'member' each time
you create a group which does not have members yet.
Some server products already ship with a schema like that and personally I
can't imagine any problem with this approach.
Ciao, Michael.