nanog mailing list archives
Re: What's really needed is a routing slot market
From: Dorn Hetzel <dorn () hetzel org>
Date: Sun, 6 Feb 2011 16:29:02 -0500
1) You get a note from the owner of jidaw.com, a large ISP in Nigeria, telling you that they have two defaultless routers so they'd like a share of the route fees. Due to the well known fraud problem in Nigeria, please pay them into the company's account in the Channel Islands. What do you do? (Helpful hint: there are plenty of legitimate reasons for non-residents to have accounts in the Channel Islands. I have a few.)
If I peer with them or sell them transit or buy transit from them then we have a reason to talk, otherwise, not so much.
2) Google says here's our routes, we won't be paying anything. What do you do?
There's a cost to taking the routes from Google, and a benefit to having those routes. As long as the benefit exceeds the cost, no worries.
2a) If you insist no pay, no route, what do you tell your users when they call and complain? 2b) If you make a special case for Google, what do you do when Yahoo, AOL, and Baidu do the same thing? Back to the cost/benefit balance above.
I can imagine some technical backpressure, particularly against networks that don't aggregate their routes, but money? Forget about it, unless perhaps you want to mix them into the peering/transit negotiations.
I think the only way it works, presuming anyone wanted to do it, is as a property of transit and peering. If I buy transit from you and want to send you a mess of routes, you might charge me more for my transit on account of that. Perhaps I get one free prefix announcement per x amount of bandwidth I am buying ? If we are peering then prefix balance might join traffic balance as a way to think about whether the arrangement is good for both peers. All of these arrangements occur between directly peering or transit providing neighbors. If I buy transit from you, I expect you to pay any costs needed to get my routes out to the world (and probably to charge me accordingly).
Current thread:
- Re: Using IPv6 with prefixes shorter than a /64 on a LAN, (continued)
- Re: Using IPv6 with prefixes shorter than a /64 on a LAN Mark Andrews (Feb 05)
- Re: Using IPv6 with prefixes shorter than a /64 on a LAN Jack Bates (Feb 06)
- Re: Using IPv6 with prefixes shorter than a /64 on a LAN Mark Andrews (Feb 06)
- What's really needed is a routing slot market (was: Using IPv6 with prefixes shorter than a /64 on a LAN) John Curran (Feb 06)
- Re: What's really needed is a routing slot market Joel Jaeggli (Feb 06)
- Re: What's really needed is a routing slot market John Curran (Feb 06)
- Re: What's really needed is a routing slot market Joel Jaeggli (Feb 06)
- Re: What's really needed is a routing slot market Jimmy Hess (Feb 06)
- Re: What's really needed is a routing slot market William Herrin (Feb 06)
- Re: What's really needed is a routing slot market John Levine (Feb 06)
- Re: What's really needed is a routing slot market Dorn Hetzel (Feb 06)
- Re: What's really needed is a routing slot market Jack Bates (Feb 06)
- Re: What's really needed is a routing slot market Eliot Lear (Feb 08)
- RE: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) Jamie Bowden (Feb 07)
- Re: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) William Herrin (Feb 07)
- Re: What's really needed is a routing slot market Jack Bates (Feb 07)
- Re: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) Owen DeLong (Feb 07)
- Re: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) Matthew Petach (Feb 07)
- Re: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) Owen DeLong (Feb 07)
- Re: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) cja () daydream com (Feb 07)
- RE: What's really needed is a routing slot market (was: Using IPv6 withprefixes shorter than a /64 on a LAN) Koch, Andrew (Feb 07)