- From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
- Date: Mon, 21 May 2018 19:08:24 +0000
- To: Julian Reschke <julian.reschke@gmx.de>, Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Hi Julian, > AFAIR, there were arguments about whether RFC 3230 actually got the terminology right (it tries to clarify RFC 2616 but IMHO added even more confusion). > If you are serious about this, you may want to update RFC 3230 based on the terminology in RFC 723*. Digest offers several benefit to end-to-end content integrity, transport integrity alone (TLS etc) still allows some error in the chain to flip something that could break the clients. This thread was prompted by an edge case in configuring an experiment. Given some of the ambiguities that seem open to creative interpretation, broad interop might be interesting :) I'm not sure I understand the problems completely such that I could update 3230. Hypothetically, if I were to try that, I might wait for HTTPter to complete. Lucas
Received on Monday, 21 May 2018 19:09:01 UTC