Re: [idn] LDAPv3 and IDN

["Eric A. Hall" <ehall@ehsco.com>]

"Kurt D. Zeilenga" wrote:

> Bottom line for non-LDAP'ers is, IDNA appears to work for
> LDAP (and likely similar protocols).  [BTW, my I-D was
> written against IDNA -04, but I don't think -05 impacts
> the bottom line.]

I think IDNA-05 added the notion of allowing protocol data to use the
native encoding, which means that the unencoded domain names can be passed
directly in an LDAPv3 data stream as UTF-8 encoded UCS, rather than as
encoded data that has to be be encoded and decoded by the end-points.

| 6.2 Applications and resolver libraries

| In protocols and document formats that define how to handle
| specification or negotiation of charsets, IDN host name labels can be
| encoded in any charset allowed by the protocol or document format. If a
| protocol or document format only allows one charset, IDN host name
| labels MUST be given in that charset. In any place where a protocol or
| document format allows transmission of the characters in IDN host name
| labels, IDN host name labels SHOULD be transmitted using whatever
| character encoding and escape mechanism that the protocol or document
| format uses at that place.

I wouldn't advise either approach at the moment, since its unclear what
format the source domain names will be in or how the TBD format options
will affect LDAP or anything else. There is way too much in flux,
including the scope of the WG itself, to define anything at the moment.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/