Hi! > On 23 Nov 2020, at 17:00, Dmitry Belyavsky <beld...@gmail.com> 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. > > > > For example, what would an "old" client do that doesn't understand a > > potential EAI extension? Would they be deprived of email addresses > > completely, and receive non-sensical placeholders which they'd unwittingly > > hand over to their email system (even if that email system would perfectly > > understand EAIs?). Does sound like a failed opportunity to me! > > See question above. > > Scott > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext > > > -- > SY, Dmitry Belyavsky > _______________________________________________ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext -- Taras Heichenko ta...@academ.kiev.ua _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
