Re: utf-8 encode

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

At 02:43 PM 5/30/00 +0200, Villy Kruse wrote:
>It seams a bit unclear what is supposed to happen if you mix protocol
>versions, for example a v2 client talking to a v3 server.  Per the
>specs the v2 client would expect a T.61 string from the server and
>act accordingly.

The server may store information in whatever charset it chooses,
but it must translate in as necessarity to conform to the protocol
specification.

>If the server is then to accommodate this  expectation it
>should then translate from utf8 to T.61 if it receives a v2 request.
>Or not?

The server should do whatever translations are necessary to
provide UTF-8 encoded ISO-10646-1 directory strings over LDAPv3
and T.61 directoryStrings over LDAPv2.  What translations that
might be required are implementation specific as each implementation
can choose it's own storage.  Some dual protocol servers store
strings in UTF-8, some store it as BER encoded directoryString
(which supports multiple encodings).  Either way, both have
translations to do when data is provided by one protocol and
requested from another.

Some (server AND client) implementations do not provide properly
encoded directory strings.  They are broken.