Message-ID: <52629a5c-c868-4a72-b5c9-ea8b5180dfd4@iit.cnr.it>
Date: Tue, 17 Mar 2026 15:45:14 +0100
Mime-Version: 1.0
Content-Language: it
To: Pawel Kowalik <kowalik=40denic.de@dmarc.ietf.org>,
 Andy Newton <andy@hxr.us>, Jasdip Singh <jasdips@arin.net>,
 "rpp@ietf.org" <rpp@ietf.org>
References: <abYT-eacTk_XBcp9@nic.fr>
 <479a9158-34bc-46a4-ba94-5c5971bbecf6@denic.de>
 <abfpLjWva5nbf3oL@ietf.bortzmeyer.fr>
 <2883529d-04cb-4b67-ae2f-4c262c90fb1c@iit.cnr.it>
 <137566c1-114f-4635-b59f-e3cc24a9be36@denic.de>
 <PH7PR15MB6084A51151DA91CA7F0BBDF5C940A@PH7PR15MB6084.namprd15.prod.outlook.com>
 <4cd4431e-65fe-4031-9159-cc52c2c20138@hxr.us>
 <6ff16be0-0db1-46eb-900f-efc1c0dc2f07@denic.de>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
In-Reply-To: <6ff16be0-0db1-46eb-900f-efc1c0dc2f07@denic.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: EVHH67U76ME3AA7OFNRA67PJEVCYH44T
CC: Robert Stepanek <rsto@fastmailteam.com>
Precedence: list
Subject: =?utf-8?q?=5Brpp=5D_Re=3A_An_implementation_of_JSContact_in_JSON_Schema?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/rpp/e2Dach8cqlif6VdqcagsJ4F1M3I>

Hi Pawel,

Il 17/03/2026 09:10, Pawel Kowalik ha scritto:
> Hi Andy,
>
> On 17.03.26 02:15, Andy Newton wrote:
>> Agreed, especially considering other tech is being built upon JSContac=
t.
>
> You mean RDAP or sth else?
>
> My point about RDAP was that its current profile for JSContact is not=20
> appropriate for provisioning. Lax processing is not favoured in RPP,=20
> therefore in order to have JSContact compatibility between the two not=20
> just on paper, the profiles shall be aligned, meaning RDAP profile=20
> being more strict.

[ML] Aside from the fact that it's possible to register a new=20
RPP-specific profile that introduces additional restrictions beyond=20
those defined in the "rdap" JSContact profile,I would like to know if=20
you mean that there are other types of restrictions missing from the=20
current version of draft-ietf-calext-jscontact-profiles.

The JSContact profile for RDAP was defined to ensure compatibility with=20
the current output of RDAP servers. Of course, it can be modified with=20
WG consensus.


Mario

>
>>
>> RPP needs to be more than EPP-in-JSON, otherwise it will be an=20
>> annoyance instead of a game-changer.
>>
>> This is also why discovery is important.
>
> Agree.
>
> Jim keeps mentioning Registry Mapping for EPP, which somehow did not=20
> fly. We have to learn from this.
>
> [1]=20
> https://www.verisign.com/assets/epp-sdk/verisign_epp-extension_registry=
_v00.html
>
> Kind Regards,
> Pawel
>
>
> _______________________________________________
> rpp mailing list -- rpp@ietf.org
> To unsubscribe send an email to rpp-leave@ietf.org

--=20
Dott. Mario Loffredo
Senior Technologist
Technological Unit =E2=80=9CDigital Innovation=E2=80=9D
Institute of Informatics and Telematics (IIT)
National Research Council (CNR)
Address: Via G. Moruzzi 1, I-56124 PISA, Italy
Phone: +39.0503153497
Web: http://www.iit.cnr.it/mario.loffredo