LCUP: collective attributes, subentries, etc.

Some statement should be made with how LCUP interacts
with collective attributes appearing both in the
filter and returned entries.  The simple approach
would be to say: 1) filter should not contain
assertions upon collective attributes, 2) changes to
an collective subentry will not cause entries within
the collection to be "updated", 3) clients are interested
in maintaining sync with collective attributes should
include the collective subentry within an LCUP request.

Which leads to my next question:
	how does a client ask for update of both entry
	and subentry DSEs subordinate to the baseObject object?

This is similar to the subordinate referral issue.  One
could generalize the question to:

	How does a client ask for update of all DSEs of
	a particular combination of DSE types subordinate
	to the baseObject?

Kurt