[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
ldap v2/v3 interoperability
Hi,
For ldap v2 clients interoperating with ldap v2/v3 servers, how is character
set translation to be handled? In the case where an entry containing Unicode
characters (created by a v3 operation) matches a query from a v2 client,
what happens if the Unicode character cannot be translated to T.61? There
are several possibilities:
1) server returns an error (which error?)
2) server returns the Unicode values encoded in some way (what encoding?)
3) server returns partial results terminated with an error/warning (what
error?)
I don't believe the Open/Group ldap server profile says what should be done
in this case. It does mention that in the case where the server would
normally return an ldap v3 referral, that partial results should be returned
terminated by a "sizeLimitExceeded" error. Should the same thing be expected
for the character set conversion problem? What are vendors implementing?
-----------------------------------------
Chris Oliva
Entrust Technologies
(613) 248-3014
Chris.Oliva@entrust.com
http://www.entrust.com
-----------------------------------------