From: regext <regext-boun...@ietf.org> On Behalf Of Dmitry Belyavsky Sent: Thursday, November 19, 2020 4:03 AM To: regext@ietf.org Subject: [EXTERNAL] [regext] EAI in EPP from a registrar point of view
Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, I think it's worth providing some thoughts about the EAI support in EPP from a registrar's perspective. From a registrar's perspective, when the registry provides some feature, the registrar has to support it in most cases. When a registry supports EAI, the registrar should be ready to at least get an EAI address in the <info> command on transfer. Registrars usually got accreditation for working with more than one registry, and have to write some registry-specific code. In the case of EAI, the changes should require at least accepting EAI addresses from the clients not having the ASCII ones and some mechanism providing the valid ASCII email address in the case when such client wants to register a domain in a registry that does not support EAI. [SAH] This is why an optional extension is our best option. The server (registry) advertises support for the extension. The capability is requested when a client (registrar) performs a login with a server, and there’s reduced risk of the client sending something the server won’t understand and vice-versa. Scott
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
