RE: objectIdentifierMatch on ambiguous name

["Steven Legg" <steven.legg@adacel.com.au>]

Kurt,

Kurt D. Zeilenga wrote:
> I'm thinking 4.3.26 of [Syntaxes] should say something like:
> 
>         Servers SHOULD prevent values in <descr> form from be
>         stored in the directory for which the server is not
>         able to unambiguously determine which OID the <descr>
>         represents.
> 
> and 5.1.17:
>         If the assertion value is presented in <descr> form and
>         the implementation is not able to determine which OID
>         the <descr> represents, the server SHOULD treat the
>         assertion as being Undefined.
> 
> That is, if the server cannot determine which OID the <descr>
> refers to, the <descr> should be viewed as invalid.

This is basically what my server implementation does. It always
tries to convert a <descr> into a numeric oid, using the context
(if available), and throws an "invalid syntax" error if unable to
do so. The error will fail an update request, or will cause an
assertion to evaluate to undefined.

Regards,
Steven