[Cryptography] HTTP should be deprecated.

[Guido Witmond]

On 11/12/13 10:12, Lodewijk andré de la porte wrote:

> ISPs are suggested to cache common files. The requests can be dealt 
> with locally, on the same network. Of course it requires static
> files but it gives you a free CDN!

> (Note it saves an ISP money to employ caches, that's why you can 
> trust them to do it. (Except when they have pairing agreements with 
> the destination...))

With British Telecom promoting PHORM, that trust has eroded.

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.

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.


The problem is that the current http-infrastructure is not good at
specifying what can be cached and what not.
Examples: compare: https://us.gov/constitution and
https://meteo.com/current_weather

Bad example :-) both are not worth caching, but you get the point. :-)


But I agree that the unencrypted transmissions should be eradicated.

Regards, Guido.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20131112/4c01aba0/attachment.pgp>