Maxim,

Many thanks!
The draft is desired to fix the current state of the EPP protocol which is in rather common use in both CC TLDs and gTLDs.

IMHO, if the EPP protocol is redesigned to accept these issues and adopted, these changes are to become a part of the core protocol - as for now EPP accepts local and internationalized (ASCII only :) ) post addresses. 

I totally agree that it's a good idea to make these changes simultaneously.

On Fri, Oct 9, 2020 at 11:35 AM Maxim Alzoba <m.alzoba@gmail.com> wrote:
There is a work in progress about translation and transliteration

https://gnso.icann.org/en/en/group-activities/active/transliteration-contact

(it hangs in the air due to other policy work in GNSO) ,
But with high probability a contact, may be other elements also are to have two fields (one transliterated using not yet known rules into English, another - original language), but since the work is not finished, I am not sure about the final recommendations , also, there is no info yet about any additional fields or what to do if the contact  is only in English.

To avoid a new standard applicable only to CCtlds(who are free to do what they find fit in the namespace) and following uniformity ideas it might a good idea to track the developments in that GNSO policy field
(Future PDP for IDNs too, it is to be initiated soon and I would recommend UA to send at least one member to track it and to participate in it).

⁣Maxim Alzoba​

On 9 Oct 2020, 10:53, at 10:53, Dmitry Belyavsky <beldmit@gmail.com> wrote:
>In this very first draft, I hoped it will be possible just to update
>RFC
>5733 and allow EAI in the contact object.
>
>The first responses show that the early draft should be reworked and
>the
>EPP extension specification should be used instead.
>I'll let you know when the specification is ready.
>
>On Fri, Oct 9, 2020 at 10:48 AM Mark Datysgeld
><mark@governanceprimer.com>
>wrote:
>
>> That's very interesting! Can you give us a broad overview of the
>> specification and how it works?
>>
>> Regards,
>> On 10/07/2020 10:31, Dmitry Belyavsky wrote:
>>
>> Dear colleagues,
>>
>> I've just submitted a specification allowing usage of EAI in the EPP
>> protocol to the IETF regext working group.
>>
>> If there is any interest in this work, it's worth subscribing the
>regext
>> mailing list (https://www.ietf.org/mailman/listinfo/regext) and
>> explicitly supporting the work on the document.
>>
>> Many thanks!
>>
>> --
>> SY, Dmitry Belyavsky
>>
>> _______________________________________________
>> UA-Tech mailing
>listUA-Tech@icann.orghttps://mm.icann.org/mailman/listinfo/ua-tech
>> _______________________________________________
>> By submitting your personal data, you consent to the processing of
>your personal data for purposes of subscribing to this mailing list
>accordance with the ICANN Privacy Policy
>(https://www.icann.org/privacy/policy) and the website Terms of Service
>(https://www.icann.org/privacy/tos). You can visit the Mailman link
>above to change your membership status or configuration, including
>unsubscribing, setting digest-style delivery or disabling delivery
>altogether (e.g., for a vacation), and so on.
>>
>> --
>> Mark W. Datysgeld from Governance Primer [www.markwd.website]
>> Incoming ICANN GNSO Councilor
>>
>>
>
>--
>SY, Dmitry Belyavsky
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>UA-discuss mailing list
>UA-discuss@icann.org
>https://mm.icann.org/mailman/listinfo/ua-discuss
>_______________________________________________
>By submitting your personal data, you consent to the processing of your
>personal data for purposes of subscribing to this mailing list
>accordance with the ICANN Privacy Policy
>(https://www.icann.org/privacy/policy) and the website Terms of Service
>(https://www.icann.org/privacy/tos). You can visit the Mailman link
>above to change your membership status or configuration, including
>unsubscribing, setting digest-style delivery or disabling delivery
>altogether (e.g., for a vacation), and so on.



--
SY, Dmitry Belyavsky