- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 17 Dec 2014 17:19:00 +1100
- To: Mark Watson <watsonm@netflix.com>
- Cc: Noah Mendelsohn <nrm@arcanedomain.com>, "www-tag@w3.org List" <www-tag@w3.org>
Hi Mark, On 16 Dec 2014, at 3:39 am, Mark Watson <watsonm@netflix.com> wrote: > It would be good to have some clearer discussion of caching in the main document. Presently there is a reference to "content optimization", but it's not very clear whether this includes transparent caching. I think the impact of HTTPS on ISP transparent caching should be clearly acknowledged and the TAG should explain their rationale for accepting this as a consequence of the proposed transition. I've added some text here: https://github.com/w3ctag/web-https/commit/f9c53a41accb892cad63358811e8d88d218f4d00 Note that there's a distinction between "normal" shared caching proxies and "transparent" (more formally, interception) proxies. The latter have long been condemned by the IETF, and are effectively a loophole that some networks have exploited. Closing that loophole is going to cause them some pain, but they can't say they're surprised by it (the writing has been on the wall for some time). Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 17 December 2014 06:19:28 UTC