[Cryptography] HTTP should be deprecated.

[Lodewijk andré de la porte]

2013/11/12 Guido Witmond <guido at witmond.nl>

> The era of ISP-operated caches is past.
>
> With Netflix and other movie streaming sites reaching 50% traffic mark,
> that's out of the league for ISP's. Both Netflix and Youtube (Google)
> offer free (or cheap) caches for their contents to ISPs.
>

Being fair that means that the corporations help the ISPs have caches. That
50% is mostly added traffic (didn't reduce other traffic). It would be very
interesting to know if ISPs still cache commonly accessed cache-able files.
They might not do it for a wealth of peering agreements and cheap bandwidth
mostly consumed by those companies that remove the need by having CDNs.


> The rest of the web out there is so full of advertisements that those
> operators don't want caches as it diminishes their 'tracking' abilities.
> In fact, the content of the page can be cached, the advertisement
> require a new connection each time. I'd say that the advertisements are
> more costly (in network resources) than the content.
>

Advertisements can (are, usually) served through iframes or similar
constructs, meaning the page with the adverts can be cached. The adverts
themselves fly in through their regular channel.

It is true that many websites are dynamic nowadays. I think that'll change.
The web is moving towards web-applications. Those applications have shared
libraries and are for a large part static. It simply makes very little
sense to work against caches.

The problem is that the current http-infrastructure is not good at
> specifying what can be cached and what not.
>

TTL headers aren't good enough?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20131113/d6559854/attachment.html>