Many things are usually allowed by the EPP Schemas but refused according
to server policies so it seems to me that this case is similar to many
others. For example, are registrars aware of the TLDs implementing
DNSSEC or do they simply rely on finding the DNSSEC namespace in EPP
greeting?
Besides, I agree with Dimitry that dealing with an ad-hoc EPP extension
would be more complex than just allowing the EAI email addresses. In
fact, clients/servers should send/receive an email address in the
related EPP element.
Cheers,
Mario
Il 19/10/2020 20:28, John Levine ha scritto:
In article <5f5d3bae-b38c-4663-800b-3f5918990...@verisign.com> you write:
The registry can support the receipt of UTF-8 addresses based on the EPP RFCs,
but full support comes down to the validation of the
email addresses, how the email addresses are stored, and what the email
addresses are used for. I would expect an EPP error (2004
"Parameter value range error" or 2306 "Parameter value policy error") if an
internationalized email address is received when the
registry does not support it.
That makes sense, but it also seems needlessly cruel. I expect
registrars would build ad-hoc lists of who handles EAI and who
doesn't, to provide better reports to their users, which would
then inevitably get out of date.
If we do this it really would be nice if there were a signal for who
handles EAI and who doesn't.
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
--
Dr. Mario Loffredo
Systems and Technological Development Unit
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Mobile: +39.3462122240
Web: http://www.iit.cnr.it/mario.loffredo
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
