Re: Revised Matched Values Draft

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

Another comment:
>If the server supports this control, the server MUST make use of the 
>control as follows:
>
>(1) The Search Filter is first executed in order to determine 
>which entries satisfy the Search criteria. The control has no 
>impact on this step.
>
>(2) If the typesOnly parameter of the Search Request is TRUE, 
>the control has no effect and the Search Request SHOULD be 
>processed as if the control had not been specified.
>
>(3) If the attributes parameter of the Search Request consists 
>of a list containing only the attribute with OID "1.1" 
>(specifying that no attributes are to be returned), the control 
>has no effect and the Search Request SHOULD be processed as if 
>the control had not been specified.

This step seems unnecessary.


>(4) For each attribute listed in the attributes parameter of the 
>Search Request, the server MUST apply the control as follows:
>
>i) Every attribute value that evaluates TRUE against one or 
>more elements of the ValuesReturnFilter is placed in the 
>SearchResultEntry.
>ii) Every attribute value that evaluates FALSE or undefined 
>against all elements of the ValuesReturnFilter is not 
>placed in the SearchResultEntry. An attribute that has no 
>values selected is returned with an empty set of vals.

How is the control applied if no attribute list is provided or "*"
is in the list.  I would assume, in both cases, that all user
attributes contain in entry would be evaluated (per step 4)
as if they were explicitly listed.