Re: [core] Stateless proxy and Request-Tag

'Christian Amsüss' <christian@amsuess.com> Thu, 31 October 2019 15:38 UTC

Return-Path: <christian@amsuess.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8D171207FE for <core@ietfa.amsl.com>; Thu, 31 Oct 2019 08:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fn0lfqbOzsWB for <core@ietfa.amsl.com>; Thu, 31 Oct 2019 08:38:50 -0700 (PDT)
Received: from prometheus.amsuess.com (alt.prometheus.amsuess.com [IPv6:2a01:4f8:190:3064::3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23D4D1200F4 for <core@ietf.org>; Thu, 31 Oct 2019 08:38:50 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (095129206250.cust.akis.net [95.129.206.250]) by prometheus.amsuess.com (Postfix) with ESMTPS id 7C22946D0A; Thu, 31 Oct 2019 16:38:47 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 9B90436; Thu, 31 Oct 2019 16:38:46 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:6d78:bd47:b07:7e5c]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 1324A7A; Thu, 31 Oct 2019 16:38:46 +0100 (CET)
Received: (nullmailer pid 17053 invoked by uid 1000); Thu, 31 Oct 2019 15:38:42 -0000
Date: Thu, 31 Oct 2019 16:38:42 +0100
From: 'Christian Amsüss' <christian@amsuess.com>
To: Jim Schaad <ietf@augustcellars.com>
Cc: 'Core WG mailing list' <core@ietf.org>
Message-ID: <20191031153842.GD25593@hephaistos.amsuess.com>
References: <20191031133656.GA17667@hephaistos.amsuess.com> <009101d58ff6$22d85f70$68891e50$@augustcellars.com> <20191031145048.GB25593@hephaistos.amsuess.com> <00a001d58fff$e7d9f0f0$b78dd2d0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="ieNMXl1Fr3cevapt"
Content-Disposition: inline
In-Reply-To: <00a001d58fff$e7d9f0f0$b78dd2d0$@augustcellars.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/OMnLX_x21qlwmXrzTmsrzfR0IOY>
Subject: Re: [core] Stateless proxy and Request-Tag
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2019 15:38:52 -0000

On Thu, Oct 31, 2019 at 08:28:51AM -0700, Jim Schaad wrote:
> If it is a fetch then it has payload

In the Block2:1 request? That's good to hear b/c that's what I thought
but couldn't support.

Still, that leaves any messages that are Block2:>0 with an empty payload
undecidible for a proxy (could be tail of Block1+2, could be just tail
of Block2 and the request body is just empty), on which it'd need to
tack a Request-Tag, so as to ensure that the correct result of an
earlier Block1+2 operation is pulled out of the server.

(I'm not saying I'd advocate build servers that have such statefullness,
but 7959 allows such constructs, and I'd like to see all of that work
through a stateless proxy.)

KR
c

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom