Re: Fwd: New Version Notification for draft-stroeder-namedobject-00.txt

Andrew,

Andrew Sciberras wrote:
> I think further clarification is required in regards to the namedPolicy object
> and the potential removal of the pwdPolicy example. 
> 
> The pwdPolicy object class is an auxiliary object class that is associated
> with a subentry. 
> I don't think that it's a good example to use in this case because you
> wouldn't use the pwdPolicy object class in association with a non-subentry
> object.
> If pwdPolicy was used with an object such as the namedPolicy object,
> then I wouldn't expect the policy to work or be applied at all.

Hmm, there are LDAP server implementations where you use 'pwdPolicy' as
auxiliary object class with normal directory entries, not subentries.

> I think that it would be good to elaborate further on the intended usage of
> the namedPolicy object and why it exists and is required in separation of the
> namedObject object. 

I've added this text to the next version of the draft to section 'namedPolicy':

      The rationale for an extra structural object class is to have
      the possibility to associate a specific set of policy-related
      auxiliary object classes without having to restrict the more
      general 'namedObject' class.

(I'm a big fan of DIT content rules...)

Ciao, Michael.

_______________________________________________
Ldapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ldapext