Re: Cable & Wireless "de-peering"?!?
albert@waller.net (Albert Meyer) writes:
Didn't UUNet try this back in 96? A quick search of Boardwatch failed to find the article, but ISTR that John Sidgemore eventually slunk back to the playground and agreed to play nice. If UUNet couldn't pull it off back then, I doubt that CW can now. ...
I am completely fascinated by your assessment (that UUNet didn't pull it off).
On Mon, May 07, 2001 at 09:37:10AM -0700, Paul Vixie wrote:
albert@waller.net (Albert Meyer) writes:
Didn't UUNet try this back in 96? A quick search of Boardwatch failed to find the article, but ISTR that John Sidgemore eventually slunk back to the playground and agreed to play nice. If UUNet couldn't pull it off back then, I doubt that CW can now. ...
I am completely fascinated by your assessment (that UUNet didn't pull it off).
It is rare, but I agree with Paul here :) Unet is, for example, one of the few (if not the only) ISP in The Netherlands that charges for *peering* (no, not transit, just peering). More and more clued people I know are avoiding UUnet because they don't peer with the small but quickly growing ISPs. Most UUnet customers are getting worse and worse connectivity as other ISPs stop peering with UUnet, because UUnet is becoming less and less important. A nice downward spiral. Greetz, Peter.
I contend that if quantifiable evidence exists that setting the peering bar high in the name of selling transit and/or restricting new players leads to a downward spiral in network quality ... then evidence exists that can be taken to stockholders and BOD of those companies. Companies, unless they are run by less than competent management, will not knowingly commit economic suicide. Stockholders tend to have a very low tolerance for management stupidity. Stockholder tolerance now is a lot lower then five years ago. At 6:45 PM +0200 07-05-2001, Peter van Dijk wrote:
On Mon, May 07, 2001 at 09:37:10AM -0700, Paul Vixie wrote:
albert@waller.net (Albert Meyer) writes:
Didn't UUNet try this back in 96? A quick search of Boardwatch failed to find the article, but ISTR that John Sidgemore eventually slunk back to the playground and agreed to play nice. If UUNet couldn't pull it off back then, I doubt that CW can now. ...
I am completely fascinated by your assessment (that UUNet didn't pull it off).
It is rare, but I agree with Paul here :)
Unet is, for example, one of the few (if not the only) ISP in The Netherlands that charges for *peering* (no, not transit, just peering).
More and more clued people I know are avoiding UUnet because they don't peer with the small but quickly growing ISPs. Most UUnet customers are getting worse and worse connectivity as other ISPs stop peering with UUnet, because UUnet is becoming less and less important. A nice downward spiral.
Greetz, Peter.
-- Joseph T. Klein +1 414 915 7489 Senior Network Engineer jtk@titania.net Adelphia Business Solutions joseph.klein@adelphiacom.com "... the true value of the Internet is its connectedness ..." -- John W. Stewart III
On Mon, 7 May 2001, Joseph T. Klein wrote:
I contend that if quantifiable evidence exists that setting the peering bar high in the name of selling transit and/or restricting new players leads to a downward spiral in network quality ... then evidence exists that can be taken to stockholders and BOD of those companies.
Refusing to peer is not always a bad option if you have a big enough share of the market. In Australia the top 3 providers (Telstra, Optus, connect.com) own about 80% of the market, host most of the domestic content and supply circuits to most other ISPs. It is "pretty hard" to setup peering with any of them. They have very little incentive to peer with smaller ISPs. The small provider will have to connect with one of them anyway and they will obviously make more money changing this provider for the circuit (and the traffic) than just peering for free. On the other hand in New Zealand we have all except on of the large providers well connected by a couple of peering exchanges. This provider is under a lot of pressure to peer with everyone else and at least one other provider has recently shutdown a circuit that was being used for peering (The large provider is trying to force others to pay for circuits directly to it, plus some other fees). -- Simon Lyall. | Newsmaster | Work: simon.lyall@ihug.co.nz Senior Network/System Admin | Postmaster | Home: simon@darkmere.gen.nz ihug, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz
On Mon, May 07, 2001 at 06:45:13PM +0200, Peter van Dijk wrote: [snip]
Unet is, for example, one of the few (if not the only) ISP in The Netherlands that charges for *peering* (no, not transit, just peering).
I stand corrected on this bit. UUnet just has quite strong peering requirements. Anybody wanting to exchange traffic with UUnet while being unable to comply must become a customer, therefore.
More and more clued people I know are avoiding UUnet because they don't peer with the small but quickly growing ISPs. Most UUnet customers are getting worse and worse connectivity as other ISPs stop peering with UUnet, because UUnet is becoming less and less important. A nice downward spiral.
I do still think UUnet is in a downward spiral, just like C&W. Strong peering policies are not good for the Internet. Greetz, Peter.
I do still think UUnet is in a downward spiral, just like C&W. Strong peering policies are not good for the Internet.
Greetz, Peter.
I'm not so sure that's true. Personally, I think the Internet is better served by having a smaller number of larger and better maintained meeting places than by just having a large number of peering points were everyone connects to everybody else. Here are just a few reasons why, for example, it's better if you use transit to FooNet to reach BarNet rather than BarNet peering with you directly (assuming you are not too big yourself): 1) FooNet and BarNet are more likely to keep their peering points scaled to handle the load than you are. They are more likely to monitor performance and shut down failures. 2) FooNet and BarNet will meet at more places than you will meet BarNet, allowing traffic to get off the source network faster and providing better fault tolerance. 3) Fewer BGP sessions means faster convergence and less instability. 4) You may be more likely to meet BarNet at public peering points while FooNet is more likely to meet BarNet at private peering points. Your traffic to BarNet will get the benefit of the higher amounts of effort FooNet and BarNet will put into keeping their meeting points efficient. DS
Peter writes:
I do still think UUnet is in a downward spiral, just like C&W. Strong peering policies are not good for the Internet.
David replies:
I'm not so sure that's true. Personally, I think the Internet is better served by having a smaller number of larger and better maintained meeting places than by just having a large number of peering points were everyone connects to everybody else.
Here are just a few reasons why, for example, it's better if you use transit to FooNet to reach BarNet rather than BarNet peering with you directly (assuming you are not too big yourself):
1) FooNet and BarNet are more likely to keep their peering points scaled to handle the load than you are. They are more likely to monitor performance and shut down failures.
2) FooNet and BarNet will meet at more places than you will meet BarNet, allowing traffic to get off the source network faster and providing better fault tolerance.
3) Fewer BGP sessions means faster convergence and less instability.
4) You may be more likely to meet BarNet at public peering points while FooNet is more likely to meet BarNet at private peering points. Your traffic to BarNet will get the benefit of the higher amounts of effort FooNet and BarNet will put into keeping their meeting points efficient.
DS
First, I'm not sure how these reasons relate to UUNET's direction (downward spiral, up and to the right, quick-quick-slow). Second, many of them are based on presumptions that relate to past performance, with no guarantee of future results. This is especially true if you consider traffic exchange to occupy more than two points on the spectrum than just Free---Paid Transit. For example, 1) has historically been true when BarNet is not paid for taking your traffic; it may value it for other reasons (content/eyeballs), but unless it is paid it is hard to get resources for link or equipment upgrades. In paid peering, it is paid to take your traffic and is likely to take seriously performance degradation or failure; whether you do is, of course up to you. So it may make more sense to enter a paid peering agreement with BarNet than to use transit through FooNet to get to them. Similarly, 3) has the interesting assumption that you are not using BGP to talk to FooNet, which will not be the case if you have a multi-homed transit arrangement aside from the peering to BarNet. 4) and 2) contain some interesting assumptions about meeting points and the topological relationships among FooNet, BarNet and the customer network. 4) seems to assume, for example, that more of BarNet's effort goes into a private connect to FooNet than to the public connect at BazNAP. Could be true; could be entirely the other way around. As David's post points out, though, there is no easy assumption about what is going to be best. I think the Internet is actually best served by having lots of available of choices for how to interconnect. That way, when your mileage varies, there is something you can do about it. regards, Ted Hardie Disclaimer: I am not speaking for my employer. This disclaimer is, however, included solely for the amusement of Stephen Stuart; any other use may be a violation of his rights to amusement. (http://www.irbs.com/internet/nanog/0104/0164.html)
Also sprach hardie@equinix.com
This is especially true if you consider traffic exchange to occupy more than two points on the spectrum than just Free---Paid Transit.
Using this statement as a hopping off place, and not trying to contradict you in any way as I largely agree with you. I think what it comes down to is that you get the best connectivity for the lowest price. Considering in the price calculation the ability to maintain that connectivity. Radical thought, huh? :) Seriously though, IgLou has transit with uu.net and att.net. Given our size, we really aren't actively considering any other transit connections at the moment as our current setup meets our needs. That being said, if anyone has a great deal on transit...don't not call because we're not actively considering it. :) What I am looking into some is peering relationships...usually fairly small scale given the scale of IgLou's network. Particularly at this point we're considering it primarily with setups that are predominantly content sources, as we're predominantly content sinks, and this is the best way to get the most bang for the buck in our peering, by peering with networks that predominantly source content rather than sink it. *shrug* I probably will not get more than one or two significant peering connections at present, however, because the cost and effort of maintaining them would outstrip the benefits. It all comes down to cost-benefit tradeoffs. If you have more transit or peering connections that you can keep on top of for maintenance and scaling, then adding more will likely end up degrading your network. I feel that IgLou is at that point for transit, but could still benefit from peering connections, and that's really the only thing on my plate that I'm looking at currently. If/when we get a couple of peering connections, then there will be enough that I won't be able to keep on top of them and I won't add anymore until we grow our resources to be able to manage them better. Its really just not all that difficult of a concept to grasp. -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456
Similarly, 3) has the interesting assumption that you are not using BGP to talk to FooNet, which will not be the case if you have a multi-homed transit arrangement aside from the peering to BarNet.
No, I'm assuming you *must* have BGP sessions to everyone you get peering or transit from. The more places you peer with, the more BGP sessions you are going to have.
4) and 2) contain some interesting assumptions about meeting points and the topological relationships among FooNet, BarNet and the customer network. 4) seems to assume, for example, that more of BarNet's effort goes into a private connect to FooNet than to the public connect at BazNAP. Could be true; could be entirely the other way around.
That's not quite the assumption. It really is that more effort goes into a private connect to FooNet than to the public connect at BazNAP as it applies to your particular connection. They might monitor their BazNAP connection closely, but not be particularly concerned if they notice possible problems with a smaller peering connection -- especially if they don't charge for it.
As David's post points out, though, there is no easy assumption about what is going to be best. I think the Internet is actually best served by having lots of available of choices for how to interconnect. That way, when your mileage varies, there is something you can do about it.
Well, I won't argue with that. Another possible disadvantage with 'free' peering is you may have a harder time getting the larger companies to deal with issues that arise surrounding that peering. They may feel they have no financial incentive to worry about it, and you really have no contractual leverage to get, for example, response time guarantees. DS
Another possible disadvantage with 'free' peering is you may have a harder time getting the larger companies to deal with issues that arise surrounding that peering. They may feel they have no financial incentive to worry about it, and you really have no contractual leverage to get, for example, response time guarantees.
Isnt the financial issue and management overhead less (relatively) for a large company with a large well ordered NOC than that of a small one? So their only excuse remains the one that they 'think your too small to care' Steve
Disclaimer: I am not speaking for my employer. This disclaimer is, however, included solely for the amusement of Stephen Stuart; any other use may be a violation of his rights to amusement. (http://www.irbs.com/internet/nanog/0104/0164.html)
I am suitably amused. Stephen
People made similar claims regarding why AT&T shouldn't have been broken up... also called the "a few big companies can take care of consumers better" argument. Watch CSPAN, you'll hear this argument periodically from the megacorp of the week making it's case before congress. Historically, a few big companies controlling any particular industry results in slower innovation until some chaotic event occurs that allows new entrants that don't have a vested interest in the status quo. Remember how MCI got its start. They weren't allways that big. Did they have a right to exist when they where small? AT&T didn't think so and didn't want them connecting to the phone network. MCI went to court and the rest is history. On Mon, 7 May 2001, David Schwartz wrote:
I do still think UUnet is in a downward spiral, just like C&W. Strong peering policies are not good for the Internet.
Greetz, Peter.
I'm not so sure that's true. Personally, I think the Internet is better served by having a smaller number of larger and better maintained meeting places than by just having a large number of peering points were everyone connects to everybody else.
Here are just a few reasons why, for example, it's better if you use transit to FooNet to reach BarNet rather than BarNet peering with you directly (assuming you are not too big yourself):
1) FooNet and BarNet are more likely to keep their peering points scaled to handle the load than you are. They are more likely to monitor performance and shut down failures.
2) FooNet and BarNet will meet at more places than you will meet BarNet, allowing traffic to get off the source network faster and providing better fault tolerance.
3) Fewer BGP sessions means faster convergence and less instability.
4) You may be more likely to meet BarNet at public peering points while FooNet is more likely to meet BarNet at private peering points. Your traffic to BarNet will get the benefit of the higher amounts of effort FooNet and BarNet will put into keeping their meeting points efficient.
DS
+------------------- H U R R I C A N E - E L E C T R I C -------------------+ | Mike Leber Direct Internet Connections Voice 510 580 4100 | | Hurricane Electric Web Hosting Colocation Fax 510 580 4151 | | mleber@he.net http://www.he.net | +---------------------------------------------------------------------------+
I do still think UUnet is in a downward spiral, just like C&W. Strong peering policies are not good for the Internet.
Is this just an opinion, or do you have evidence? A genuine impartial economic analysis of this issue would be very interesting, and probably even more interesting to the regulators. I would hope any such analysis will include cost of maintenance and stability of networks with n interconnects as n increases. Most regulation theory looks to minimize customer price over the long term. This does not necessarilly mean maximizing competion (though it normally but not always means no monopolies). European regulation in this area (yes it exists) focusses only on those with Significant Market Power (variously defined but normally 25% or above of the 'Relevant Market'), and suggests that their interconnect policies should be non-discriminatory and cost-oriented. In my book that means that A has 30,000 routes of 100,000, and B has 2 routes, then B is paying A. (before saying that 'but B would charge A too' remember that A probably has the opportunity to exchange data via B's transit, at, no doubt, a lower cost per bit). In the mean time their view is, in general, that if what you say is true (downward spiral etc.) because their peering policy is suboptimal, then this just allows some competitor with a more optimal peering policy to gain competitive advantage. IMHO there is a high correlation between people claiming strong peering policies are 'bad for the internet' and those recently refused peering. Thus data samples are somewhat skewed. -- Alex Bligh Personal Capacity
participants (11)
-
Alex Bligh
-
David Schwartz
-
hardie@equinix.com
-
Jeff Mcadams
-
Joseph T. Klein
-
Mike Leber
-
Paul Vixie
-
Peter van Dijk
-
Simon Lyall
-
Stephen J. Wilcox
-
Stephen Stuart