Re: controlling visability of subentries

[Zachary Amsden <zach@xxxxxxxxxxxxx>]

Yes, a control is definitely needed.  I wasn't looking
forwards to parsing arbitrary filters correctly.  Also, since
ldapSubEntries aren't actually in our object databases, but
are metadata, using a control is a much easier way to figure
this out.

>I also agree that it is probably better to define a control
for this. 
>Can we do so soon?
>
>FYI, our implementation of draft-ietf-ldup-subentry-03.txt
today checks
>each equalityMatch filter component for
objectclass=ldapSubEntry and
>considers returning subentries if it finds one anywhere.  So
all of
>these filters may result in ldapSubEntries being returned:
>
>(objectclass=ldapSubEntry)
>(!(objectclass=ldapSubEntry))
>(&(objectclass=ldapSubentry)(cn=foo))
>(|(objectclass=ldapSubEntry)(objectclass=myReplicaSubEntry))
>
>If we stick with the filter approach, we should at least add
some
>examples to the document.