IETF Logo Mail Archive

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

Pawel Kowalik <kowalik@denic.de> Wed, 18 March 2026 06:41 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 5DF48CCD6E5D for <rpp@mail2.ietf.org>; Tue, 17 Mar 2026 23:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, HTML_MESSAGE=0.001, 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=ham 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 E7vSt2bEEtSv for <rpp@mail2.ietf.org>; Tue, 17 Mar 2026 23:41:58 -0700 (PDT)
Received: from mout-b-105.mailbox.org (mout-b-105.mailbox.org [195.10.208.50]) (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 1F20FCCD6DFE for <rpp@ietf.org>; Tue, 17 Mar 2026 23:41:56 -0700 (PDT)
Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:b231:465::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-105.mailbox.org (Postfix) with ESMTPS id 4fbK4D0dyvz9xgf; Wed, 18 Mar 2026 07:41:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1773816108; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=mw2EAYcfKgFCKxWbLXc6LJ2K9kmmsKuijXRpo3xsgOA=; b=H1/jVrA+XtKQaq4TtfMI+ofiLVP60mmPl0pc37866PMuBFDKys0UtSygHwXX9T8HXVJW+8 rBw4KeqL1L5aI6+DNs/2dhtxozyfkrXWiAiFQ0L0WZ7zOOXr1QBtLHKKzWQxoZtCVfm0QI Ro9p6QbrNaTi/3pgnUAsWKKuxzLmPZDW9jS+taZ3+KDHHzBZWZIIpIbAvYKmDKqc/BO7d1 qi84P2M2ktR7cBVorWI31ESNOvGKjldYwjMy5PxaI3H03jRSgUdRzFRYndA7KHxccScHSZ /DQkZjfbIA5Vux6Qba+pnmenipY2rsqmES8+z/DVC/eXt5AdUbbIwX5ziXW3mA==
Message-ID: <8be0d8d4-3864-4555-8ea6-c21e50c6d689@denic.de>
Date: Wed, 18 Mar 2026 07:41:45 +0100
MIME-Version: 1.0
From: Pawel Kowalik <kowalik@denic.de>
To: Jasdip Singh <jasdips@arin.net>, Mario Loffredo <mario.loffredo=40iit.cnr.it@dmarc.ietf.org>, Pawel Kowalik <kowalik=40denic.de@dmarc.ietf.org>, Andy Newton <andy@hxr.us>, "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> <52629a5c-c868-4a72-b5c9-ea8b5180dfd4@iit.cnr.it> <f8495bcc-287a-4cea-8aeb-e46bf61d5808@denic.de> <PH7PR15MB6084375FA079460A87D5CF6AC941A@PH7PR15MB6084.namprd15.prod.outlook.com>
Content-Language: en-GB, de-DE
In-Reply-To: <PH7PR15MB6084375FA079460A87D5CF6AC941A@PH7PR15MB6084.namprd15.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms010608080703010607070504"
X-MBO-RS-META: xpedtae1tn68g6y65wtw4seta8a4f16g
X-MBO-RS-ID: c125d3c09e07f0543a8
Message-ID-Hash: WDBRMJ4LJTXGC2YBX65WCDAXLQAHBV7D
X-Message-ID-Hash: WDBRMJ4LJTXGC2YBX65WCDAXLQAHBV7D
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
CC: Robert Stepanek <rsto@fastmailteam.com>
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/PFp8xKamqUtSQS2CRH9snhII_L8>
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>

On 17.03.26 19:10, Jasdip Singh wrote:

> On 3/17/26, 11:19 AM, "Pawel Kowalik" <kowalik@denic.de> wrote:
>
> > [ML] Aside from the fact that it's possible to register a new
> > RPP-specific profile that introduces additional restrictions beyond
> > those defined in the "rdap" JSContact profile,I would like to know if
> > you mean that there are other types of restrictions missing from the
> > current version of draft-ietf-calext-jscontact-profiles.
> >
> [PK] As far as I can tell for now draft-ietf-calext-jscontact-profiles
> shall be sufficient to define a profile for RPP. We are quite early in
> the evaluation though.
>
> [JS] Glad a JSContact profile for RPP would be considered. :)
>
[PK] This is even captured in the requirement C3.1 , so should not come 
with surprise.

Kind Regards,
Pawel

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