This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Previous message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Next message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Nov 19 21:32:53 CET 2019
In message <17839.1574194412 at segfault.tristatelogic.com>, I wrote: >This is exactly what I had suggested. Using only punycode for domain names >would restrict the representation of the domain names in the data base to >traditional 7-bit US-ASCII. My apologies to everyone. When I posted that reply I didn't even notice the fact that the representation of domain names in the data base was/is now being discussed also on the anti-abuse mailing list. This very topic has already been discussed on the DB working group mailing list, which is arguably a more appropriate place for this discussion since abuse contact email addresses (and their associated domain name parts) are quite certainly not the only places where email addrsses may appear within the WHOIS data base. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
- Next message (by thread): [anti-abuse-wg] Non-ASCII characters in abuse-mailbox addresses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]