[rpp] Re: Call for adoption: draft-wullink-rpp-json-02 (Ends 2026-06-30)

Jaromir Talir <jaromir.talir@nic.cz> Tue, 30 June 2026 09:07 UTC

Return-Path: <jaromir.talir@nic.cz>
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 D331110A91731; Tue, 30 Jun 2026 02:07:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782810425; bh=9m9Xdmr9UlqUq2RM8/jYDSJHIutcou80cn8CXO/jl24=; h=Subject:From:To:Date:In-Reply-To:References; b=X6xq/oA4ckjBT331XGqKC6KJaNIUHCSFOOMVZt+aVzN4utC2ENGanCHMRHMsEhNTS xV/joO9H82rfeDSWEFpPP96nfv59KmCl6C0sopNQwLzxkqI2c4+/PffcBS7vUQuthk b69i3waS8Rs1Zln9rQ4WGQ4qWF6Uj3AptjgsVOk4=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 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_MED=-2.3, 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 (1024-bit key) header.d=nic.cz
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 1-oCPgy2zMwU; Tue, 30 Jun 2026 02:07:05 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 22F5910A9172C; Tue, 30 Jun 2026 02:07:01 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:2:c46d:134b:674c:2ae1] (unknown [IPv6:2001:1488:fffe:2:c46d:134b:674c:2ae1]) by mail.nic.cz (Postfix) with ESMTPSA id 5CBFE1C0DD6; Tue, 30 Jun 2026 11:07:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.cz; s=default; t=1782810420; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9m9Xdmr9UlqUq2RM8/jYDSJHIutcou80cn8CXO/jl24=; b=XZXnJ1KoxBcXNEmWJ66x5b6USHonDuz8rVCXw0vsnBPBbuywBb1jxhcRFBC65thEQJM5u3 36WQi5fNFD5Fzt5lJKJFZVkPie/MCBaVTmbseEOhACnKEUi/ILBjKhBZsg4U77M//nEq52 IxEM0WCVDsf/fewINdy9P0BkiJef3sQ=
Authentication-Results: mail.nic.cz; auth=pass smtp.auth=jaromir.talir@nic.cz smtp.mailfrom=jaromir.talir@nic.cz
Message-ID: <fc551a98d6100a5433a886114dd9fd0b7f4a2a2f.camel@nic.cz>
From: Jaromir Talir <jaromir.talir@nic.cz>
To: Marco Davids <marco.davids@sidn.nl>, rpp@ietf.org, rpp-chairs@ietf.org, draft-wullink-rpp-json@ietf.org
Date: Tue, 30 Jun 2026 11:06:59 +0200
In-Reply-To: <178159401878.533102.4994758117588597092@dt-datatracker-f9b87776f-8pmmg>
References: <178159401878.533102.4994758117588597092@dt-datatracker-f9b87776f-8pmmg>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.60.2 (3.60.2-1.fc44)
MIME-Version: 1.0
X-Rspamd-Action: no action
X-Spamd-Result: default: False [-0.10 / 16.00]; MIME_GOOD(-0.10)[text/plain]; FUZZY_RATELIMITED(0.00)[rspamd.com]; ARC_NA(0.00)[]; ASN(0.00)[asn:25192, ipnet:2001:1488::/32, country:CZ]; WHITELISTED_IP(0.00)[2001:1488:fffe:2:c46d:134b:674c:2ae1]; FROM_HAS_DN(0.00)[]; LOCAL_OUTBOUND(0.00)[]; DKIM_SIGNED(0.00)[nic.cz:s=default]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]
X-Rspamd-Server: mail
X-Rspamd-Queue-Id: 5CBFE1C0DD6
X-Spamd-Bar: /
X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: WHITELISTED_IP
Message-ID-Hash: LBWVOYQI6R7KPOHGZPTFKFEJCOIAOEO5
X-Message-ID-Hash: LBWVOYQI6R7KPOHGZPTFKFEJCOIAOEO5
X-MailFrom: jaromir.talir@nic.cz
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: Call for adoption: draft-wullink-rpp-json-02 (Ends 2026-06-30)
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/k4sX6uGYd22EgK_SiFhDqvLANVE>
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>

I support adoption.

Regards,
Jaromir

On Tue, 2026-06-16 at 00:13 -0700, Marco Davids via Datatracker wrote:
> This message starts a rpp WG Call for Adoption of:
> draft-wullink-rpp-json-02
> 
> This Working Group Call for Adoption ends on 2026-06-30
> 
> As a reminder, adoption does not imply consensus on the document's
> content; issues can still be raised and changes proposed. We are
> simply agreeing on a starting point for the WG's work. Likewise,
> adoption means that change control for any resulting IETF product
> rests with the IETF.
> 
> Based on the responses received, the chairs will determine whether
> there is consensus for adoption. 
> 
> Abstract:
>    This document defines the rules for representing the RESTful
>    Provisioning Protocol (RPP) data objects, as defined in
>    [I-D.kowalik-rpp-data-objects], using the JavaScript Object
> Notation
>    (JSON) Data Interchange Format [RFC8259].  It specifies how RPP
>    primitive types, common data types, component objects, resource
>    objects, and associations are mapped to JSON and JSON Schema, and
>    provides normative JSON Schema definitions and worked examples for
>    domain name, contact, and host data objects.
> 
> Please reply to this message and indicate whether or not you support
> adoption
> of this Internet-Draft by the rpp WG. Comments to explain your
> preference are
> greatly appreciated. Please reply to all recipients of this message
> and
> include this message in your response.
> 
> Authors, and WG participants in general, are reminded of the
> Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> Appropriate IPR disclosures required for full conformance with the
> provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy
> can be
> found at [3].
> 
> Thank you.
> 
> -- 
> Gavin & Marco
> RPP co-chairs
> 
> 
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-wullink-rpp-json/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-wullink-rpp-json-02.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-wullink-rpp-json-02
> 
> _______________________________________________
> rpp mailing list -- rpp@ietf.org
> To unsubscribe send an email to rpp-leave@ietf.org