IETF Logo Mail Archive

[rpp] Re: An implementation of JSContact in JSON Schema

Pawel Kowalik <kowalik@denic.de> Mon, 16 March 2026 14:42 UTC

Return-Path: <kowalik@denic.de>
X-Original-To: rpp@mail2.ietf.org
Delivered-To: rpp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D4654CB5EF89 for <rpp@mail2.ietf.org>; Mon, 16 Mar 2026 07:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=denic.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JLq3KppvepmO for <rpp@mail2.ietf.org>; Mon, 16 Mar 2026 07:42:13 -0700 (PDT)
Received: from mout-b-203.mailbox.org (mout-b-203.mailbox.org [195.10.208.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 327C6CB5EF77 for <rpp@ietf.org>; Mon, 16 Mar 2026 07:42:13 -0700 (PDT)
Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-203.mailbox.org (Postfix) with ESMTPS id 4fZHqG633gz9wXP; Mon, 16 Mar 2026 15:42:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1773672122; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=T1nbbd5+8dD+Ng3AgQDn24rxw8wSFNuVBbo9vFFeyqM=; b=nj09XZinyPxvTtNJeL1m+xWoALYBOxRgI39J3xrpKH0QQZ4jp2VRQvNqopjIC8z5n+4pqI g9sYEj6SJkxCS99bwswrg14I9zXwtrvJAtqXCQgCNBn21JumaZDKozFbxHJS6Cs/DEn5MJ ct1HvCNlO+ZQ/dEBOlJK+AUcrwJRjaep+LIQz/UQd5cgxF5Xa7vJo0hSpfmCgBpSXdVriq 8HDpV2Mfmhfygqgd3yckDfknUxdL5qWf6O3B4KNB1+Up18QzeWdjnS0lRUMKnG1AiS12ZW O2LQumR3FucruXDQPCcttMrcssf+UKJLi1SEb6ae9iky8pGyeYMs10KVEiI08Q==
Message-ID: <137566c1-114f-4635-b59f-e3cc24a9be36@denic.de>
Date: Mon, 16 Mar 2026 15:42:01 +0100
MIME-Version: 1.0
From: Pawel Kowalik <kowalik@denic.de>
To: Mario Loffredo <mario.loffredo=40iit.cnr.it@dmarc.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>
Content-Language: en-GB, de-DE
In-Reply-To: <2883529d-04cb-4b67-ae2f-4c262c90fb1c@iit.cnr.it>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms060700030508070608050300"
X-MBO-RS-ID: 5af22e81d5e4c4ea8c0
X-MBO-RS-META: uwss7encg9rbow8xzs6owwa5wmrbx9fw
Message-ID-Hash: HUO6OFKEFW4EX5CYOXINWB4TZ2UC5YVC
X-Message-ID-Hash: HUO6OFKEFW4EX5CYOXINWB4TZ2UC5YVC
X-MailFrom: kowalik@denic.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [rpp] Re: An implementation of JSContact in JSON Schema
List-Id: "This list discusses a provisioning protocol based on RESTful principles and corresponding data representations using JSON." <rpp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rpp/yQj3EcigqLVAkzZlMab36nL9nvY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rpp>
List-Help: <mailto:rpp-request@ietf.org?subject=help>
List-Owner: <mailto:rpp-owner@ietf.org>
List-Post: <mailto:rpp@ietf.org>
List-Subscribe: <mailto:rpp-join@ietf.org>
List-Unsubscribe: <mailto:rpp-leave@ietf.org>

Hi Mario,

On 16.03.26 15:14, Mario Loffredo wrote:
> Do you think that the "rdap" profile is comprehensive enough for use 
> in the RPP context ?

I think it still has too many options for the same data. For RPP it 
needs to be more strict and aligned with EPP contact model.

Kind Regards,
Pawel

v2.46.0 | Report a Bug | By Email | System Status