[rpp] Re: New Version Notification for draft-kowalik-rpp-data-objects-03.txt

Pawel Kowalik <kowalik@denic.de> Tue, 03 March 2026 14:07 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 52A12C37027A for <rpp@mail2.ietf.org>; Tue, 3 Mar 2026 06:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, 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 Pa2FfIT4KJHA for <rpp@mail2.ietf.org>; Tue, 3 Mar 2026 06:06:53 -0800 (PST)
Received: from mout-b-107.mailbox.org (mout-b-107.mailbox.org [IPv6:2001:67c:2050:102:465::107]) (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 B8880C36FBE7 for <rpp@ietf.org>; Tue, 3 Mar 2026 06:03:30 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (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-107.mailbox.org (Postfix) with ESMTPS id 4fQHZc3VSqzDrwT; Tue, 3 Mar 2026 15:03:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1772546600; 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=6TVIXIfluyucG0LtEOU43bze6Z//5JGy5e1dM3r8DKo=; b=v4BpagaduE5C6U/JKo01CgwcBW4Gwxbq9+ghJWX8PcysNW1sTXxM/oqi9LgHXtJbNw6Csw hOec55/UstI3nq+N5HSScQgK8z5LBY72AkK6DekCKvxEldlZRyLxTtASz2Z5Or9mLFMq++ 0nQK06qjG0xUizyw01XEXWEjsg9XiuQuyUydyw04kQeGCYdVeDg2hoQ1jw93mgT3o3iJIM QsMkv8oPv4PA2IHmZcVlYo4DBY4HMrDrSPg4HO9VCuorBMX9y+udE/dYDRUYL3crAvjkDv 4dkT3GZe2sogdNaoz7U0RpgNqg8OD0AV9yIObFfOYs2mj2JNCuFLEBK678jGDg==
Message-ID: <7662ad0b-169c-42d4-bf77-51a675ff012d@denic.de>
Date: Tue, 03 Mar 2026 15:03:18 +0100
MIME-Version: 1.0
From: Pawel Kowalik <kowalik@denic.de>
To: Pierre Thierry <pierre@nothos.net>, rpp@ietf.org
References: <177248745626.3659784.8644715906427944698@dt-datatracker-6ff7c68975-7k42g> <b6bece74-ec0d-4280-9b8d-38e0f275246b@denic.de> <29104b9b-8493-4a54-8930-268c4f42691b@nothos.net>
Content-Language: en-GB, de-DE
In-Reply-To: <29104b9b-8493-4a54-8930-268c4f42691b@nothos.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070909020105020602090606"
X-MBO-RS-ID: 9953a53a12e1b89e777
X-MBO-RS-META: 9p5dhcqig13f6ugdy5gpjxmp9fi4u5xy
Message-ID-Hash: D2GX7BFA6B632C7KRXRPUCB3AKABHESG
X-Message-ID-Hash: D2GX7BFA6B632C7KRXRPUCB3AKABHESG
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: New Version Notification for draft-kowalik-rpp-data-objects-03.txt
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/akJZfTud40sfHyCjJjMr3ov77eA>
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 Pierre,

On 03.03.26 14:30, Pierre Thierry wrote:
> Le 02/03/2026 à 23:01, Pawel Kowalik a écrit :
>> - is this draft the right place to describe business logic (example 
>> RGP in 2.5.5.)? If not, where?
>
> Maybe it's a similar question: should RPP provide stricter types than 
> "String" with subsets of Unicode code points from RFC 9839 or PRECIS, 
> or should it let invalid strings be dealt with on another layer?
>
Yes it should. We have noted an issue to have 2nd pass on data elements 
once we have all the elements in the document in the right structure.

https://github.com/pawel-kow/draft-kowalik-rpp-data-objects/issues/43

> I saw that RPP Architecture 5.2.3 says there will be descriptions 
> using a schema language, will they go in the Data Objects documents? 
> (that could be that other layer where proper restrictions are expressed)
>
Take a look into draft-wullink-rpp-json-01. This one maps artefacts from 
data objects into JSON and JSON Schemas. It's not yet complete but 
you'll get the idea.

Kind regards,
Pawel