-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ask a few on-topic questions and lots of people jump down your throat - except Aj. Who'da thunk it? He's normally pretty quick to get a couple of jabs in on me when the opportunity arises. The only possible explanation I can think of is that he has a word-of-the-day calendar on his desktop - and today's word was "facetious". - --- Drew Calcott Linux System Administrator Science IT University of Auckland (p) +64 9 373 7599 x84269 Alastair Johnson wrote:
Drew Calcott wrote:
Maybe I've missed something here, but does implementing traffic shaping on content that is sitting in a local cache seem a little bit silly...? And is it really fair to count data that is merely being pushed from inside their own network towards people's (rather insignificant) usage caps?
As other people have mentioned, shaping towards the subscriber access loop may be required to avoid congestion in the access network. Shared spectrum networks in particular have this requirement especially for the upstream direction (i.e. DOCSIS style).
On the transit-ingress side of the equation, the cache appliance provides a nice easy place to provide aggregate contention - and if it has logic in it that can do it itself based on some rules (time-of-day, number of subscribers, content type, whatever) then it makes it a really good place to ensure that the cache itself isn't congesting your upstream transit.
aj
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkkpPgACgkQD+yXTWfduLHS/gCgjDSemBp9K7bSUgMCN+cQJOEr 3i8An29ZYfm7wVwTO1CuXYNQDPjj3aHR =b0Fs -----END PGP SIGNATURE-----