|
Well one could argue that its as expected when there is a published specification and the throttling applied matches the spec. On the whole PlusNet seem to manage that quite well baring occasional mis configurations. Eg. one gateway un-throttled usenet a bit late last week on certain package(s). We can remember when it was a mess in their early days but they've worked out a fairly good way to configure the ellacoyas and make it understandable.
Its not trivial to understand though as the mechanisms that are simpler to explain are a) throttling your entire connection for all protocols (usually all the time), b) something like the original ALT which was effective and transparent and protected latency, c) letting congestion do its own thing. And maybe something like TalkTalk where p2p is throttled (but loads of people do not realise) but they never say by how much or when.
Enta's IPSC rollout has been far odder with certain connections showing signs of clear active throttling above the ALT, the ALT not behaving how it used to and its reporting being completely opaque when it used to be very transparent. And ofcourse a major shortage of capacity versus the packages sold and no resilience.
Now the OP may be right that some aspects of the PlusNet throttling specification are not how a techi might configure things BUT and I think this has always been the key point - to Joe Bloggs the internet means web browsing (and he may not even know what a browser is by name), if you can say that your browsing is unaffected and be able to prove it to the ASA then you are on a marketing winner. This is also useful for homes/businesses with multiple PCs (2Mb*4 = 8Mb) and so on. The main reason they throttle download sites (in my opinion) is simply that a) its easy b) they are by definition not real-time critical and c) when new releases appear its easy for them to flood the network. And with places like rapidshare its a), b) and a new c) which is that a user of those sites may be pulling a lot of Mb continuously.
|