Re: [regext] Internationalized Email Addresses and EPP

["Hollenbeck, Scott" <[e-mail]>]

> -----Original Message-----
> From: Taras Heichenko <[e-mail]>
> Sent: Monday, November 23, 2020 1:46 PM
> To: Dmitry Belyavsky <[e-mail]>
> Cc: Hollenbeck, Scott <[e-mail]>;
> [e-mail]; [e-mail]; Gould, James
> <[e-mail]>; [e-mail]
> Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP
>
> 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.
>
> Hi!
>
> > On 23 Nov 2020, at 17:00, Dmitry Belyavsky <[e-mail]> wrote:
> >
> > Dear Scott,
> >
>
> [skip]
>
> >
> > This may be the path of least resistance. I'm still trying to think through hat
> would happen if a registry returns an internationalized email address to a
> registrar that doesn't expect one. This could happen after a domain transfer,
> for example. Is this a problem? If not, maybe we could just get by without
> any other protocol changes or extensions.
> >
> > From my point of view, if the registry has implemented EAI support, all the
> registrars will have to do it. They should deal with the clients with such emails
> _somehow_.
> > E.g., they hardly can reject the transfer relying on this reason.
>
> There are cases when registry cannot enforce registrars to implement some
> features. But I see no problem in the registry response with EAI. EPP works
> with UTF-8 encoding so EAI should not cause the EPP interface crash. Such
> email can cause strange symbols in the web interface but as for me it should
> not bring serious problems.

That's only true if you're not also doing syntax checking of the local part outside of what your XML parser is doing with the schema. A regular expression to match an ascii-only local part would NOT match an internationalized email address.

Scott