Hi Ed, On 07.07.20 15:20, Edward Shryane wrote:
Hello Gert, Benedikt,
On 7 Jul 2020, at 15:03, Gert Doering via db-wg <db-wg@ripe.net> wrote:
Hi,
On Tue, Jul 07, 2020 at 02:53:47PM +0200, Benedikt Neuffer via db-wg wrote:
I don't get it. Does the RIPE DB prevent the usage of punycode?
Can someone give me an example, where punycode doesn't work or why punycode isn't good enough?
From what I understand, the intent is to convert incoming e-mail: attributes in "non-punycode format" to punycode before storing in the DB.
You are correct.
From my Solution Definition:
"When updating the RIPE database, it is already possible to submit a Punycode encoded value (i.e. with ASCII encoding) for an email address value, but this change automates the conversion of any non-ASCII encoded email address to Punycode."
This automated conversion will allow any email address with an IDN (non-ASCII) domain name to be stored as Punycode.
ok, thanks for the details. Know I understand the intention. I think that is the best thing one can do for now. I am in for this change. Regards, Bene