Another String Representation Question

[Jeff Thompson <[e-mail]>]

In our interoperability testing, we have already encountered
organizations which always use T.61 to represent name attribute values
for their employees. This is so that they do not have to scan values
to see if they have non-printable-string characters, like '&' in
"Sales & Marketing", which would require T.61.

If I get a business card from someone at Gadgets, such as <CN=Joe,
O=Gadgets, C=US> where "Joe" in the directory is really encoded with
T.61, how can I be sure that my software will be able to find his
distinguished name?  The directory lookup protocol says to ignore
case, but does it say to ignore T.61 vs. printable string?