Mario, I've been thinking about this a bit and I have a slightly different
proposal to suggest. See below.
> -Original Message-
> From: Mario Loffredo
> Sent: Monday, November 8, 2021 3:58 PM
> To: Hollenbeck, Scott ; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] I-D Action:
I view the jscontact is a valid use case for a standards track RDAP extension.
We have many similar use cases for standards track extensions in EPP, where the
RFCs couldn't envision a feature or an approach that comes up later. The
jscontact draft needs to be defined as an RDAP extension that
On 8 Dec 2021, at 09:55, Mario Loffredo wrote:
>
>
>
> Il 07/12/2021 14:42, Marc Blanchet ha scritto:
>>
>>> Le 7 déc. 2021 à 08:35, Hollenbeck, Scott
>>> a écrit :
>>>
>>> We can *certainly* do that, Mario. It’s the option I support because there
>>> is a cost to replace a jCard
Il 07/12/2021 14:42, Marc Blanchet ha scritto:
Le 7 déc. 2021 à 08:35, Hollenbeck, Scott
a écrit :
We can **certainly** do that, Mario. It’s the option I support
because there is a cost to replace a jCard implementation once it’s
been implemented and deployed. Make it an optional
