Brian,
It has been pointed out several times now that the problem is between
the home user and the ISP, not the ISP and the BBC/Akamai. Although it
might appear from a traceroute that there is nothing between your home
router and your ISP - there is, but the IP traffic is encapsulated and
passed within BTs ATM cloud so you cannot see it. It is the cost of
moving the encapsulated IP within this cloud between the home user and
the ISP where the problem is.
No amount of caching or proxying at the ISP end will help, because it is
outside the ATM cloud. If any caching were to be effective it would have
to work inside the cloud at exchange or regional level, and I'm not
aware of any technology that can read the ATM packets, decap the IP
packets from them, interpret the IP packets - then inject more packets
with correctly encapsulated and valid IP into the ATM cloud as a
response. All this would have to be at wire speed so as not to add
latency to all connections passing through the device. Without doing
this, there is no where else to put the proxy for it to be effective.
Anyone who thinks they can do this, go and build it. You stand to make a
vast amount of money installing them in every exchange.
--
Gareth Davis | Production Systems Specialist
World Service Future Media, Digital Delivery Team - Part of BBC Global
News Division
* http://www.bbcworldservice.com/ <http://www.bbcworldservice.com/> *
702NE Bush House, Strand, London, WC2B 4PH
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Butterworth
Sent: 15 April 2008 17:14
To: backstage@lists.bbc.co.uk
Subject: Re: [backstage] iPlayer and the ISPs - a solution
You are saying that the capacity on each individual ADSL line
here is the problem? I really don't see that. The STATED problem is
PAYING for the PIPES to backbone from BT. If this isn't the problem,
then someone is lying.
