Dear Yoshiro,
On Thu, Jun 2, 2022 at 3:04 AM Yoshiro Yoneya via Datatracker < [email protected]> wrote: > Reviewer: Yoshiro Yoneya > Review result: Ready with Issues > > Summary: > > This draft is in good shape regarding protocol. Regarding to operation, > having an additional guidance for registrar transfer from EAI supporting > registrar to non EAI supporting registrar would be better. > > Major issues: > > None. > > Minor issues: > > When a registrant who has only EAI contact addresses attempts to > transfer a > domain from EAI supporting registrar to another non EAI supporting > registrar, > then transfer of contact information will cause failure. If there were > additional operational guidance addressing this issue in this draft will > be > helpful for registrar operators. For example, when loosing registrar > who is > supporting EAI received a transfer request, it should check whether the > registrant has only EAI contact addresses, and if it was true, the > registrar > should advice the registrant to provide alternative ASCII contact > addresses > in advance for the successful transfer. > > Many thanks for your review! Yes, transfer becomes impossible in such situations, but the operational practices are beyond the scope of this document. It's more a matter of, say, ICANN recommendations. -- SY, Dmitry Belyavsky
_______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
