- From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
- Date: Thu, 23 May 2019 13:01:57 +0200
- To: Scott Perham <scott@polystream.com>
- Cc: ietf-http-wg@w3.org
On Thu, May 23, 2019 at 09:14:40AM +0100, Scott Perham <scott@polystream.com> wrote a message of 125 lines which said: > an omission in HTTP (at least in my experience) and something that > is re-invented over and over again with, You apparently don't mention in the draft these reinventions. Specific and actual examples could be nice (may be in an appendix) to get a better idea of the problem you want to solve. More generally, I find it difficult to understand this problem. A detailed explanation of some use cases could help. Also, the abstract says "to maintain a record of their interaction with the server or to track client/server requests through a disparate system of services" but why not using RFC 6265 here? This also is worth a discussion in the draft (may be again in an appendix).
Received on Thursday, 23 May 2019 11:03:31 UTC