Hello Peter, WG, > On 13 Jul 2020, at 15:03, Peter Koch via db-wg <[email protected]> wrote: > > On Mon, Jul 13, 2020 at 12:12:42PM +0000, ripedenis--- via db-wg wrote: > >> Do we therefore have support to introduce Puny code now and then consider >> how to move forward with UTF-8? > > I'm not sure I understand the proposal. "punycode" is primarily IDNA2003 > speak - and the initial suggestion by Ed was to apply an automatic > conversion.
Correct, I propose to automatically convert non-ASCII IDN email address domains into Punycode, as per RFC 5891. > How would that system deal with conversion failures > and/or with ambiguities between IDNA2003 and IDNA2008? We plan to use a third-party Java library to convert Punycode, rather than implementing one from scratch (doing it ourselves would increase complexity and time taken). Any conversion failures will result in the attribute value being considered invalid. A workaround in that case is to manually convert the IDN to ASCII (Punycode). > > -Peter > Regards Ed Shryane RIPE NCC
smime.p7s
Description: S/MIME cryptographic signature
