[rpp] Re: HTTP QUERY relevant for RPP ?

Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 24 June 2026 13:53 UTC

Return-Path: <bortzmeyer@nic.fr>
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 DFB6E1067B399; Wed, 24 Jun 2026 06:53:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782309232; bh=6AGl8eK68ryHfiolsLkILP+1eBTzET8LWj0DljtK6E8=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=dZ5a4Wn6T9X7NQNYJg7+3ivsjsCiyu2y7F/a2/E02gDr+ITkPDAmSckgieIMbosYE HM0ngibtt7WBcL9hpaRwCmAds5hE+wOVkl3R4YfUQfCKtwFC4crxTmyNIXgNmjXfSj 6+bQvcX2sFa95NcgMFHwMPAgD5q+g4bJPoVVJnOs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_HELO_NONE=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=nic.fr
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 gkLVHdwtv3ad; Wed, 24 Jun 2026 06:53:52 -0700 (PDT)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:67c:2219:10::51:2]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2B0D71067B393; Wed, 24 Jun 2026 06:53:52 -0700 (PDT)
Received: from pps.filterd (mx2.nic.fr [127.0.0.1]) by mx2.nic.fr (8.18.1.7/8.18.1.7) with ESMTP id 65ODriNS002332; Wed, 24 Jun 2026 13:53:44 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nic.fr; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=nic-20240601; bh=sjgIKY9+oK6PamFMDOPcg aTxCzAQ6T4zfO+d12862ec=; b=Jbj7Z0yCbZSa5q0qnZSHMJtg3POEa8MIowfjx h5Ob/3UbkJ2XfegxFUhQNe3XY6WN4s2smN2LYFwdcLzLnqwkzh8J/dLXWEUDroT3 kbzAwZ5O6SQa/+63XvDe3hIkjiotqIIj3Nfgmc1GVWuW6LG0KIThetvd7jqduMOt 8rcNmq4y6TPpseml3WlUzCC96CoZKagQY+mr2ug5RW/gqqIAG8z0QdLgW+4vHQrD GLJc6Mj6VUQO1V2NuGYnKbleYZtKxfOtP46mzYUkIqM9p8vAmx77lmL2CXx7zzKS 0+m8K/0tpc6tl44rzzlSyjg3F3WsT/Og8jK5Bp0vlGEVE/1Cw==
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [10.1.50.11]) by mx2.nic.fr (PPS) with ESMTP id 4ex9528jtr-1; Wed, 24 Jun 2026 13:53:44 +0000 (GMT)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.23.33]) by relay01.prive.nic.fr (Postfix) with ESMTP id F034D608A017; Wed, 24 Jun 2026 15:53:43 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id DC054410B8; Wed, 24 Jun 2026 15:53:13 +0200 (CEST)
Date: Wed, 24 Jun 2026 15:53:13 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "Marco Davids (IETF IMAP)" <marco.davids=40sidn.nl@dmarc.ietf.org>
Message-ID: <ajvhSR4mjXD5Zm3Z@nic.fr>
References: <f29583bd-3a80-4ad0-9a9c-8d103ccc6a1b@sidn.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <f29583bd-3a80-4ad0-9a9c-8d103ccc6a1b@sidn.nl>
X-Operating-System: Debian GNU/Linux 13.5
X-Kernel: Linux 6.12.94+deb13-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
X-Proofpoint-ORIG-GUID: A8ZtulQ2isLmAGqYqkPOnDUgwOfzS0_m
X-Proofpoint-Spam-Info: AW1haW4tMjYwNjI0MDExNSBTYWx0ZWRfXz1am8dbaN24F X+cIav1K2Rs4JV6LjyXG/JqRZaLUlIWTU150Yi+MPK1W/vNzam/+BngogdcekSfeSny1w3Z1Z4Z ldo5ij1QymdZNw+A1ejvPsfhLVIEQug=
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNjI0MDExNSBTYWx0ZWRfX5LCEzheYq0M9 4hPwnXHZL2NkeLzxfHaXP7pEDMueaZnfDhBFSKNSnZEyLi7WAG5EReDZXRugw64dWh7eBr34gaw 3tJ9y3xmrHiwpnl70aKwfqH81lFS/ytxDXAtfV07G1sqYaGzokhdIbo1GFFwH8+FDFFBDp0L6/T iKK/Apfkm58+D6bKj2xqMpfZpXAlOc3zLPRkqh/Bf4EKE8/8lxouGeObjILYTTvfvN0eIbQJQJZ tz2j/Fw+A27NGp6otsLUVQ+zod+nAKlHOBCMaoQDHZILbid3i3llhDPs/stRsHaqAOsk+lRwPyb stJ1EWThJhk0XR6RuZA/7YhJ4wE++/aM6IkFLeI9n3KANSCsFrayOfNTR2e+U9DWyFIv9GJMBFG ryAjqtvV
X-Proofpoint-GUID: A8ZtulQ2isLmAGqYqkPOnDUgwOfzS0_m
Message-ID-Hash: CFVKMTNJZDSSQJLHTZWO26J4FPAHS4XS
X-Message-ID-Hash: CFVKMTNJZDSSQJLHTZWO26J4FPAHS4XS
X-MailFrom: bortzmeyer@nic.fr
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: rpp@ietf.org
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/1MWgIqYfAfF7d7ewq5m_pV74Rv8>
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 Wed, Jun 24, 2026 at 03:44:22PM +0200,
 Marco Davids (IETF IMAP) <marco.davids=40sidn.nl@dmarc.ietf.org> wrote 
 a message of 12 lines which said:

> I was wondering, could RFC10008 be relevant to the work of this WG?

At the very least, we should modify draft-wullink-rpp-core, where -05
says (section 13):

   A RPP client MAY use the HTTP GET method for executing informational
   request only when no request data has to be added to the HTTP message
   body.  Sending content using an HTTP GET request is discouraged in
   [RFC9110], there exists no generally defined semantics for content
   received in a GET request.  When an RPP object requires additional
   information, the client MUST use the HTTP POST method and add the
   query command content to the HTTP message body.