[rpp] Re: HTTP QUERY relevant for RPP ?
Pawel Kowalik <kowalik@denic.de> Wed, 24 June 2026 15:04 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 7BE2C10685568 for <rpp@mail2.ietf.org>; Wed, 24 Jun 2026 08:04:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782313490; bh=WMxK4VXrjTjQCJMaOEb1prJ8HYkinKhTwNNjWaTrgTk=; h=Date:From:Subject:To:References:In-Reply-To; b=qOeflptJIIuTUt9D2559yaYmcWDGKnVWlRp/27atiIQqt9M55+GuYZuJdUCNn5D5U uIxVPTOQZZXEGQAaWZCfOKyg/JcKfrP0HSeGE+f8k+Hn8LcyZ/QfPfr4lLljC4Huvt OzNjsVhRC+VlWsgGlpWneCQ9dKgAixOCNN9UYIAg=
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 kd7nYfSlNI_L for <rpp@mail2.ietf.org>; Wed, 24 Jun 2026 08:04:49 -0700 (PDT)
Received: from mout-b-106.mailbox.org (mout-b-106.mailbox.org [IPv6:2001:67c:2050:102:465::106]) (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 A2E3B1068555F for <rpp@ietf.org>; Wed, 24 Jun 2026 08:04:49 -0700 (PDT)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::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-106.mailbox.org (Postfix) with ESMTPS id 4gllbC0FTzzDsjW; Wed, 24 Jun 2026 17:04:39 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=denic.de; s=MBO0001; t=1782313479; 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=WMxK4VXrjTjQCJMaOEb1prJ8HYkinKhTwNNjWaTrgTk=; b=GqgKZ8NxJ7gwFtcM4b7QkyFwaZAty1wZvq5W1fhfGxZBTgNWZ7iJChCaoyIy3e5OXM8lT4 aKD9SDDPUXjQEdf3POyvdY0g8P4EkWs7mlhn8wz1fgIi/IKhwlof/9sHLCAY7z1c0PJIPp EZ5w5qBE7qRbllCZeLQ9HbU0KLtLFkNID+KBATAxVOxxtlgVJkzNpgMQGdPOHBUZp8gwnf v0glFEqC/shgpcoVZfM6oo6/9EwkJB69zFIV0jgzxC7Ye6C49ScZzBKxCNT/JLt2/QoggH KjsAfExttfIVRn9ra37JFvZF8+aP0CM9N76sBfC6pRDuR2nOwsu1MmmiH/mcsQ==
Message-ID: <df474b23-3494-4717-85fd-b71ad8cbc91c@denic.de>
Date: Wed, 24 Jun 2026 17:04:37 +0200
MIME-Version: 1.0
From: Pawel Kowalik <kowalik@denic.de>
To: rpp@ietf.org, "Gould, James" <jgould@verisign.com>
References: <f29583bd-3a80-4ad0-9a9c-8d103ccc6a1b@sidn.nl>
Content-Language: en-GB, de-DE
In-Reply-To: <f29583bd-3a80-4ad0-9a9c-8d103ccc6a1b@sidn.nl>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms040203080507040404010402"
X-MBO-RS-ID: 6cc11faaeb7557eed5b
X-MBO-RS-META: y1kyxd3eimn19x5wyc19i9d44uyhyts1
Message-ID-Hash: VVQ2LCDUICRUREW3UVJ5TYUBBEADZFLZ
X-Message-ID-Hash: VVQ2LCDUICRUREW3UVJ5TYUBBEADZFLZ
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: HTTP QUERY relevant for RPP ?
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/TFkcJhFS3qXrX7cHVqaLVagwBnI>
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>
If we face a situation of excessive query size then yes. Jim Gould had a case of an extension with such potential, but we haven't studied it yet to the depth of knowing whether it exceeds capabilities of GET or not. Kind Regards, Pawel On 24.06.26 15:44, Marco Davids (IETF IMAP) wrote: > I was wondering, could RFC10008 be relevant to the work of this WG? > > https://datatracker.ietf.org/doc/html/rfc10008 > > Abstract > > This specification defines the QUERY method for HTTP. A QUERY requests > that the request target process the enclosed content in a safe and > idempotent manner and then respond with the result of that processing. > This is similar to POST requests, but QUERY requests can be > automatically repeated or restarted without concern for partial state > changes. >
- [rpp] HTTP QUERY relevant for RPP ? Marco Davids (IETF IMAP)
- [rpp] Re: HTTP QUERY relevant for RPP ? Stephane Bortzmeyer
- [rpp] Re: HTTP QUERY relevant for RPP ? Pawel Kowalik
- [rpp] Re: HTTP QUERY relevant for RPP ? Stephane Bortzmeyer
- [rpp] Re: HTTP QUERY relevant for RPP ? Gould, James
- [rpp] Re: HTTP QUERY relevant for RPP ? Maarten Wullink