> On 15 Dec 2021, at 16:14, Dmitry Belyavsky wrote:
>
> Dear Taras.
Dear Dmitry
>
> On Tue, Dec 14, 2021 at 8:13 PM Taras Heichenko wrote:
> The comment is in body.
>
> > On 13 Dec 2021, at 15:15, Hollenbeck, Scott
> > wrote:
> >
> >> --
] OK.
>
>>Section 8: It might be helpful to add more text to explain why
>> "Registries
>> MAY apply extra limitation to the email address syntax". Why might they
>> want to do that? It seems a little unusual to say that they MAY do
>> something,
>>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://verisigninc.com/>
>
> On 8/4/21, 2:21 AM, "Taras Heichenko" wrote:
>
>
> > On 2 Aug 2021, at 21:08, Gould, James
> wrote:
> >
> > Thomas,
&
PsaLa4OVdLtJihtpwdRk9fr_3G8g2mwx2jxOLL1sJ-eNhJwsOpo6W7ol32J_DzfjBAXa_Cw90o-bJSF0gBmXB6ESXuldajgmC3M50OyC92n_wRtUNo_XZxV-q617Ou591BoL72Nkten6pxWXT59Gx3wDODJPp1wp7OaV-Z6cj2rlRN7NM8UF2_IkjVUpxBNnG1Yxn7iIr2ZZbbgcQT_95-2rVq6WMVlGKV4PAAoyx95sLzddSZb6G18znD/https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fregext
> ___
> 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
> On 24 Nov 2020, at 19:56, Patrick Mevzek wrote:
>
> On Tue, Nov 24, 2020, at 12:35, Taras Heichenko wrote:
>> First of all, registry does not force anything. It gives the
>> possibility that registrars
>> can use.
>
> ... which then forces all other r
> On 24 Nov 2020, at 16:38, Patrick Mevzek wrote:
>
>
>
> On Tue, Nov 24, 2020, at 02:19, Taras Heichenko wrote:
>> Two notes:
>> - the authinfo field in a Contact object allows opening personal data
>> to only one registrar
>
> So... domain:authInfo
> On 24 Nov 2020, at 01:26, Patrick Mevzek wrote:
>
>
>
> On Mon, Nov 23, 2020, at 18:12, Taras Heichenko wrote:
>>> This is completely orthogonal to anything related to email addresses.
>>> Long gone are the days when only an email sent was enough to tri
> On 23 Nov 2020, at 23:55, Patrick Mevzek wrote:
>
>
>
> On Mon, Nov 23, 2020, at 16:50, Taras Heichenko wrote:
>> Just a question: How can a registrar accept the transfer of a domain by
>> a user if it does
>> not check that this domain is owned by this u
gt; registry
> it wants/do not want to handle this case, OR the registry has to provide
> something
> that is forward compatible (hence: 1) not breaking current software but 2)
> allows
> updated software to enjoy more features)
>
> --
> Patrick Mevzek
> p...@dotandco.com
&
__
> 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
> On 23 Nov 2020, at 22:07, Hollenbeck, Scott
> wrote:
>
>> -Original Message-
>> From: Taras Heichenko
>> Sent: Monday, November 23, 2020 1:46 PM
>> To: Dmitry Belyavsky
>> Cc: Hollenbeck, Scott ;
>> klaus.malo...@knipp.de; regext
ly
> > 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
> ___
> 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 pa
> 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: [rege
the protocol,
>> not an
>> optional one, in the long run. But hey, that's only my taste.
>
> Please keep in mind that they're currently an OPTIONAL SMTP extension. I
> think that would need to change before they become a MUST for EPP.
I fully agree with Klaus, th
peers and protocol must be very
simple and clear to
be supported by all the participants. The EPP protocol is already far beyond
the SMTP by complexity.
And registrars do not connect to the registries without appropriately preparing
the software. So any
negotiation at login time has a very forma
uot;encoding" field in the XML header.
>
> Scott
> ___
> 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
C8B3
>
> ___
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext
--
Best regards
Taras Heichenko
ta...@hostmaster.ua
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
18 matches
Mail list logo
