caching at windmills (i mean exchange points)
to: ISP's at mae-west we submit for your valued consideration a proposition http://www.nlanr.net/Caida/maewest.cache.html (first few paragraphs of web page included below) k and dw nlanr/caida (under we-run-commodity-infrastructure supervision from steve feldman (maewest), bill woodcock (zocalo), and david meyer (UO) ) -------------------------------------------------------- web caching as a viable Exchange Point Service proposed business-compatible model of web caching as a service provided at a NAP background NLANR has been operating a national public web caching system for about two years, as part of a research proposal sponsored by the National Science Foundation to architect and deploy prototype Internet information provisioning infrastructure. While the project has been an enormously successful `proof-of-concept' to the Internet community, especially internationally where it was received subjected to far higher and faster accelerating demand than we intended, participation in a cooperative global web caching mesh has for a variety of reasons been slower to catch on in the United States. A significant barrier to the use of caching by ISPs in the United States is the lack of a discernable pricing and business model to support caching as a commericial Internet service, either independently, packaged with a backbone service, or packaged with exchange point connectivity service. NLANR's project has allowed the development and deployment of a strong research code platform, as well as a prototype infrastructure that has recevied international recognition for its operationally pivotal role in the Internet. However, partly because of the tremendous success and resulting expectations of this `prototype' infrastructure, NLANR has not had the budget or cycles to pursue penetration of the U.S. commercial Internet market, partially expecting it to catch on from its own momentum. In 1997, NSF approved a follow-on award to use the by then globally-entrenched NLANR caching infrastructure for extended architectural investigation and experimentation. We maintain a project plan timeline, status reports, and cache status page including information on upgrades, major configuration changes, and outages. More importantly, we are now in a position to move forward with architectural models of caching that are more compatible with commerically-provisioned commodity intrastructure, and in which ISPs themselves will have an incentive to participate. On 1 December 1997, we are deploying a prototype web cache service at MAE-West, specifically designed to demonstrate the viability of a commercial model for providing web caching service. purpose The principal purpose of this peering-point-colocated Squid cache is to provide an easily accessible (no-AUP, low hop-count, low latency) alternative to the current vBNS-hosted root caches. The secondary purpose of this cache is as a demonstration of the feasibility of introducing self-supporting caches into the main stream of the Internet's core. Having a web cache at popular Internet exchange point provides ISPs an opportunity to leverage their presence at this strategic position in the Internet topology. Because the exchange point is a likely component of the paths of many web pages travelling across the Internet, storing web pages on a web cache at this point offers ISPs a potentially significant savings in bandwidth and end user latency by allowing them to retrieve pages there rather than having to go on to the original source.
k, I read your proposal an have a question. I assume that your MAE-west cache will act as a parent for the MW ISP's (otherwise, there's no data in the cache). That means that all outbound traffic from MW is routed through your cache, isn't it? That also means that e.g. all transatlantic traffic will flow through your lines. Or am I missing something? For our AMS-IX exchange in Amsterdam I would think that the best thing we could do is to connect all ISP's top level caches as neighbours, without a special AMS-IX parent cache. All ISP's connected have their own transatlantic lines... Cheers, Ton Verschuren - Communication Services - SURFnet bv ==> From: k claffy | | to: ISP's at mae-west | | we submit for your valued consideration | a proposition | | http://www.nlanr.net/Caida/maewest.cache.html | | (first few paragraphs of web page included below) | | | k and dw | nlanr/caida | (under we-run-commodity-infrastructure supervision | from steve feldman (maewest), | bill woodcock (zocalo), | and david meyer (UO) | )
I read your proposal an have a question. I assume that your MAE-west cache will act as a parent for the MW ISP's (otherwise, there's no data in the cache). That means that all outbound traffic from MW is routed through your cache, isn't it? That also means that e.g. all transatlantic traffic will flow through your lines. Or am I missing something?
You are not differentiating between an proxy cache and an interceptor cache. The NLANR cache is a proxy cache. Clients/peers/children must consciously point at it. randy
==> From: Randy Bush | > I read your proposal an have a question. I assume that your MAE-west | > cache will act as a parent for the MW ISP's (otherwise, there's no data | > in the cache). That means that all outbound traffic from MW is routed | > through your cache, isn't it? That also means that e.g. all | > transatlantic traffic will flow through your lines. Or am I missing | > something? | | You are not differentiating between an proxy cache and an interceptor | cache. The NLANR cache is a proxy cache. Clients/peers/children must | consciously point at it. I know. Still, for a cache to fill it has to fetch docs and thus act as a parent. If the NLANR cache acts as a parent for all MW connected ISP's than *all* misses from those ISP's get routed through the NLANR cache and for the transatlantic traffic the lines of NLANR's ISP will fill up. No? Ton.
On Wed, 3 Dec 1997, Ton Verschuren wrote:
If the NLANR cache acts as a parent for all MW connected ISP's than *all* misses from those ISP's get routed through the NLANR cache and for the transatlantic traffic the lines of NLANR's ISP will fill up. No?
The part I think you missed is that the NLANR cache at MAE West will not have an ISP in the usual sense, and will not have a default route. Instead, it will have routes to whatever places the ISP's who participate in the cache experiment choose to give it. In a sense, all the providers who participate in the experiment will jointly act like "NLANR's ISP", and will jointly carry the traffic. --apb (Alan Barrett)
participants (4)
-
Alan Barrett
-
k claffy
-
Randy Bush
-
Ton Verschuren