[ldapext] VLV: error handling

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

The document introduces an open-ended set of VLV-specific result
codes which differ only from existing codes in that they
"pertain specifically to the VLV operation".  As all existing
codes returned pertain specifically to the operation they are
returned with, it is unclear what the meaning of each new code
is.

>From the example, it seems the authors what servers to determine
whether the fault would have occurred if another operation
(same request less VLV control) had been issued and, if so,
use an existing code and if not use a new code.  This, IMO,
is not reasonable.  Generally, one should not determine the
result of one operation based upon the processing of some
other operation... especially one which never was submitted.

Consider timeLimitExceeded.  If timeLimit is exceeded, this
specification implies the server needs to determine whether it
would have been exceeded if the VLV control was not present.
Implementing this would likely be extremely difficult.

This document should new define error codes only where it
there are specific fault conditions which need to be called out.

For example, a code which indicates that greaterThanOrEqual
assertion value doesn't conform to the syntax of the
sort control matching rule should be defined.  (Note that
this is a condition which isn't presently called out but
should be.)

My review notes (which I will soon post) detail additional
concerns in this area.

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext