Re: comment on IPsecPolicyGroup

[Jon Saperia <saperia@xxxxxxxxxxx>]

> The rules for inserting a new class into inheritance trees vary; for
> example, LDAP doesn't formally permit it (i.e., X.500 doesn't permit it and
> LDAP is silent), but it's done anyway and there's been discussion in ldapext
> about fixing the formal rules.  But in the information model I think we can
> insert classes as needed as long as they don't break the subclasses (e.g.,
> introduce a property that has an inconsistent definition).  It's certainly
> permitted in the CIM schemata to insert new superclasses. If, at some point
> in the future, there's a need for some other key exchange protocol, a new
> superclass for IKERule can be inserted into the inheritance tree and the
> additional requirement can be addressed at that time when there's full
> knowledge of the requirement.
> 
Just checking, I am not asserting that this has been the case in this
discussion but. I know that LDAP is talked about a lot and I like it for
a lot of things. Please do not limit your thinking here to what LDAP can
do.

Thanks,
/jon
--

Jon Saperia		     saperia@xxxxxxxxxxx
			     Phone: 617-744-1079
			     Fax:   617-249-0874
			     http://www.jdscons.com/