Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Klaus Malorny
On 19.11.20 19:14, Gould, James wrote: Klaus, The EAI support goes beyond RFC 5733 and is a perfect example of the use of the extensibility built into EPP. Revising the RFCs and EPP extensions that use email addresses for EAI with new XML namespaces and potentially other changes is much more

Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Hollenbeck, Scott
> -Original Message- > From: regext On Behalf Of Klaus Malorny > Sent: Friday, November 20, 2020 3:47 AM > To: regext@ietf.org > Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP > > Caution: This email originated from outside the organization. Do not click > link

Re: [regext] EAI in EPP from a registrar point of view

2020-11-20 Thread Taras Heichenko
> On 20 Nov 2020, at 07:04, Hollenbeck, Scott wrote: > [skip] >> Let's compare the pros and contras of both >> (1) >> + allows implementation by minimum changes in the software. It is enough >> to change the rule which checks email addresses. > > I disagree with this completely. A new versi

Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Taras Heichenko
> On 20 Nov 2020, at 11:06, Hollenbeck, Scott > wrote: > >> -Original Message- >> From: regext On Behalf Of Klaus Malorny >> Sent: Friday, November 20, 2020 3:47 AM >> To: regext@ietf.org >> Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP >> >> Caution: Th

Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Hollenbeck, Scott
> -Original Message- > From: Taras Heichenko > Sent: Friday, November 20, 2020 6:13 AM > To: Hollenbeck, Scott > Cc: klaus.malo...@knipp.de; regext@ietf.org > Subject: [EXTERNAL] Re: [regext] Internationalized Email Addresses and EPP > > Caution: This email originated from outside the org

Re: [regext] EAI in EPP from a registrar point of view

2020-11-20 Thread Hollenbeck, Scott
> -Original Message- > From: Taras Heichenko > Sent: Friday, November 20, 2020 5:49 AM > To: Hollenbeck, Scott > Cc: regext@ietf.org > Subject: [EXTERNAL] Re: [regext] EAI in EPP from a registrar point of view > > Caution: This email originated from outside the organization. Do not click

Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Dmitry Belyavsky
On Fri, Nov 20, 2020 at 2:17 PM Hollenbeck, Scott wrote: > > -Original Message- > > From: Taras Heichenko > > Sent: Friday, November 20, 2020 6:13 AM > > To: Hollenbeck, Scott > > Cc: klaus.malo...@knipp.de; regext@ietf.org > > Subject: [EXTERNAL] Re: [regext] Internationalized Email Ad

Re: [regext] EAI in EPP from a registrar point of view

2020-11-20 Thread Taras Heichenko
> On 20 Nov 2020, at 13:18, Hollenbeck, Scott > wrote: > >> -Original Message- >> From: Taras Heichenko >> Sent: Friday, November 20, 2020 5:49 AM >> To: Hollenbeck, Scott >> Cc: regext@ietf.org >> Subject: [EXTERNAL] Re: [regext] EAI in EPP from a registrar point of view >> >> Cau

Re: [regext] Internationalized Email Addresses and EPP

2020-11-20 Thread Mario Loffredo
Hi all, I prefer option 2. Similarly to option 3, it doesn't involve a change to EPP core but it is less complex to be implemented for both registrars and registries. After all, the placeholder value "[EAI-ADDRESS]" is itself uncompliant with the current contact:email definition. Best, M

Re: [regext] EAI in EPP from a registrar point of view

2020-11-20 Thread Klaus Malorny
On 20.11.20 14:37, Taras Heichenko wrote: Right - it's a lot MORE work. Let's ask Klaus what takes more developer's work, changing namespace, or adding the extension generation and parsing. (In the neighbor thread Klaus wrote that his company is developing EPP software.) Hi, well, for t

Re: [regext] EAI in EPP from a registrar point of view

2020-11-20 Thread Taras Heichenko
> On 20 Nov 2020, at 19:32, Klaus Malorny wrote: > > On 20.11.20 14:37, Taras Heichenko wrote: >>> Right - it's a lot MORE work. >> Let's ask Klaus what takes more developer's work, changing namespace, or >> adding the extension generation and parsing. >> (In the neighbor thread Klaus wrote t