Re: matched values 05

[Bruce Greenblatt <bgreenblatt@directory-applications.com>]

While I appreciate all of the hard work that has gone into the development 
of the control, I don't feel that it is a good idea.  So, I guess the time 
has come (again) for me to state my opinion about the Matched Values Only 
(MVO) control.  IMHO the MVO control as described in this draft is a 
negative.  Throughout its progression, it has grown increasingly more 
complex.  As I recall, it started out life as a simple boolean.

The problem that is solved is mostly due to poor schema and DIT structure 
design.  There is no reason to have so many attribute values in the 
attribute of an entry.  As an example of how to solve this problem, I wrote 
a draft that described an alternative way of storing certificates (alas, it 
has expired).  With more thought given to the schema and DIT structure 
design, existing protocol and simple matching rules can be used to solve 
the problem that this complex MVO control solves.

I don't think that the Section 4 adequately address the problems of the 
interaction with other controls.  I am not convinced that the MVO control 
acts independently of server side sorting.  It seems to me that attribute 
values that are used in the sorting process can be subsequently affected by 
the MVO control.

My recommendation would be to not progress this draft at all.  If it is to 
be progressed at all, it should go only as Experimental since the impact on 
existing controls has not been explored, and since there are simpler 
solutions to the problem it claims to solve.

Thanks,

Bruce Greenblatt


==============================================
Bruce Greenblatt, Ph. D.
Directory Tools and Application Services, Inc.
http://www.directory-applications.com
See my new Book on Internet Directories: 
http://www.phptr.com/ptrbooks/ptr_0139744525.html