[148149] in cryptography@c2.net mail archive
Re: [Cryptography] HTTP should be deprecated.
daemon@ATHENA.MIT.EDU (Guido Witmond)
Tue Nov 12 19:34:56 2013
X-Original-To: cryptography@metzdowd.com
Date: Tue, 12 Nov 2013 22:37:40 +0100
From: Guido Witmond <guido@witmond.nl>
To: cryptography@metzdowd.com
In-Reply-To: <CAHWD2rLZM3weDzkHXnOPKsiOwkNavuKu2ts5POLATvsvUpprtQ@mail.gmail.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============8942627182013946842==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature";
boundary="----enig2IGUSMIQFPVLPXVKHPGKT"
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2IGUSMIQFPVLPXVKHPGKT
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 11/12/13 10:12, Lodewijk andr=E9 de la porte wrote:
> ISPs are suggested to cache common files. The requests can be dealt=20
> 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=20
> trust them to do it. (Except when they have pairing agreements with=20
> 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.
------enig2IGUSMIQFPVLPXVKHPGKT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBAgAGBQJSgp+kAAoJEHPd8GglaNRmTtEP/3nxx3350PuvhEKJiTgSU6Ln
B53dX/7ASqaiC/ig5T1plISZFPYivEdMtJpo//5ZEuGMLEcu2BX3iIJQYW5VSdFK
J3Zgb8K6wwNbBEpNRB3oi7/OyEl8DxEMOiN+oRAfeUNwK4T2ogQKRtQjhGiukccw
bAdYw/bQvGbwsoGRvul9w66yjrCuRuZO4l0W3kGZ7CjQ9TmsLcfR6azaAQOiukZx
UZWFzR5dRNl92u1aOgwCUWTG2e2SttCmPsLd6lqwQfiFOs2Dqs7LaTJ0uM0F0B6u
0sT03tX/Cu0EkTI3LSmOzDzooLAYedx6GM0VaP+0oXgw8IugFizDD30PXIHukws1
Va6VsvGf70Xv/vIl/i43/vTjpcPQxOxzKTkKTmRnn3RlGXYohzrV7vhFrRvakFY1
CTOkdFUTHCC3PVbuV9zvi0LQ/228jBub38LZH5nCOIDzKSfw3LAlYmhI9G86TJvM
N/hprRDGnJPCTS+9/qnxzvUWPe2Ewy/hQ3+5FyYKoEThcepDlXlFhmnnSxnXxTCg
rrMvMyFNY3V1J9nBIKN2vHAFToofkdgk9P/lAHUYkVseVf41GBnf8V1eyzyfB/1a
bGj+XXucaoU/6kgFOX+fikCKgSW+12H9m2MIq5Mh1aAr+m5NNMSDO98w2wxE+Eyi
3FdjGj6OjH93BlNN80n6
=FO+r
-----END PGP SIGNATURE-----
------enig2IGUSMIQFPVLPXVKHPGKT--
--===============8942627182013946842==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============8942627182013946842==--
