Re: [ldapext] Dynamic group draft

[Jaimon Jose <jjaimon@novell.com>]

Pierangelo Masarati wrote:
> Additional comments: "dgIdentity" is used in objectClass definition, but
> it is actually defined as "identity" in the attributes section.  I guess
> the intended definition is "dgIdentity".
>   

Section #4.5 refers this attribute as dgIdentity.  The second paragraph
in this section, talks about "identity values" which should have been
"dgIdentity values" .   Did I miss out something?
> BTW, would prefixing "memberQueryURL" and "excludedMember" with "dg" be
> an option?
>   
MAY be a good idea to have consistency in attribute naming with respect
to the features where the attributes are used.  As I recall, this is not
used in all cases.
> AUXILIARY classes dynamicGroupAux and dynamicGroupOfUniqueNamesAux
> cannot respectively inherit from groupOfNames and groupOfUniqueNames
> since the latter are STRUCTURAL.
>   

The idea of inheriting from groupOfnames and groupOfUniqueNames is to
have the group properties in addition to dynamicGroup properties. 
Certain implementations seem to allow that.   I'm personally not in
favor of copying the group properties to the auxiliary class.  Lack of
these properties will introduce a constraint that,  only group objects
can be marked as dynamic group. 

--jaimon

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