nanog mailing list archives
Re: Vancouver IXP - VanTX - BCNet
From: Jay Hanke <jay.hanke () mankatonetworks com>
Date: Fri, 23 Aug 2013 09:06:50 -0500
On Fri, Aug 23, 2013 at 5:59 AM, Niels Bakker <niels=nanog () bakker net>wrote:
Indeed. I think that ISPs who understand their business model well enough to understand the effect the IXP will have on their average-per-bit-delivery-cost is essential. I think it's also essential that they have some basic familiarity with the different ways IXPs can fail, or fail to thrive, so that they can avoid mistakes others have made in the past. Over-spending, particularly on switches, is a huge killer of IXPs. Under-provisioning of circuits to the IXP is another big mistake. Failure to encourage local content and hosting is another.Can you cite a few examples of an IXP going under because of overspending on switch hardware? You call this a "huge killer" so there must be dozens you can choose from.anke
Having recently been through the startup process at an independent non-profit IXP, I can see spending too much on hardware being a problem particularly on supporting the ongoing hardware/software maintenance on the switch. Something else to think about, if an exchange is given an endowment from from outside entity it might be harder to build the commitment levels of participants/volunteers because it's too easy to solve the problems with money as opposed to member contributions. We went through 3 switch upgrades in 2 years and IMHO it built a lot of community. Each IXP will have a set of faithful founders and the key is growing that group beyond the initial group before the founders lose interest and move on to bigger things. Particularly before connecting to the IXP makes business sense to a company that won't connect just because it's cool. When the exchange gets over the hump were companies are saving real money it is much easier to keep the ball rolling and the exchange growing. Many exchange points never make it to that level. Jay
Current thread:
- Re: Vancouver IXP - VanTX - BCNet, (continued)
- Re: Vancouver IXP - VanTX - BCNet Randy Bush (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet joel jaeggli (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Matthew Petach (Aug 22)
- Re: Vancouver IXP - VanTX - BCNet Bill Woodcock (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Randy Bush (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Martin Hannigan (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet William F. Maton Sotomayor (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Clayton Zekelman (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Bill Woodcock (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Niels Bakker (Aug 23)
- Re: Vancouver IXP - VanTX - BCNet Jay Hanke (Aug 23)
- Re: Vancouver IXP - VanTX - BCNet Jay Ashworth (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet William F. Maton Sotomayor (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Clayton Zekelman (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet William F. Maton Sotomayor (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet John Osmon (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet bmanning (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet William F. Maton Sotomayor (Aug 21)
- Re: Vancouver IXP - VanTX - BCNet Christopher Morrell (Aug 21)
- RE: Vancouver IXP - VanTX - BCNet Jacques Latour (Aug 21)