Re: vendorACI attribute in draft-ietf-ldapext-acl-model-04.txt

[Ellen Stokes <stokes@austin.ibm.com>]

David,
The intent of vendorACI is to provide a way in which to allow non-LDAP
defined ACI to appear in LDIF, so if you dump the directory into LDIF
and then reload into another vendor's server and back again into your
server, you don't lose any data.  Vendors will continue to use their
own access control mechanisms in cases, so it is expected that in some
parts of the tree that may not be ldap accessible that you'll see the
use of aCIMechanism, and hence vendorACI for preservation of that
information at dump/restore time.
The vendorACI attribute will remain in the model.
Ellen


At 09:53 AM 10/14/1999 -0600, David Ward wrote:
>What value does the vendorACI attribute add?  It appears to be a
placeholder vendors can use for proprietary aci information. However, the
model already allows vendors to define their own access control mechanisms
( section 5.1 ).  In my opionion, having vendors define specific access
control mechanisms, is better than stuffing everything into a vendorACI
printable string attribute.  I think the attribute should be dropped.
>
>David
>