North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

RE: /24s run amuck again

  • From: Deepak Jain
  • Date: Sun Jun 10 05:43:59 2001



-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
David Schwartz
Sent: Sunday, June 10, 2001 4:24 AM
To: Geoff Huston
Cc: nanog@nanog.org
Subject: RE: /24s run amuck again




> If you are on my upstream chain, then I am accompanying my routing
> requirements with money. Whatever penalty you may incur I pay for with my
> upstream payment. Where your statement holds is once you are not seeing
> money from me (i.e. you are not an upstream paid directly or
> indirectly by
> me), in which case what would help us all is a recognised [*] community
> attribute which says "advertise this prefix together with this attribute
> only to your upstreams"

	Actually, in all cases the requirements are accompanied by money. Even in
settlement-free peering, if the two sides didn't feel they were getting paid
to do whatever they are doing, they should sever the peering relationship
and charge. You are getting that route from somewhere and if you aren't paid
by someone to do so with value greater than its cost to you, you should stop
accepting the route.

	The money flows along the same paths the routes do. Every time a route goes
from router 1 to router 2, there is some agreement that allows it to do so.
If the route exchange costs you more than you're getting out of it,
renegotiate that connection.

	One thing that might help is if companies that work out peering that isn't
free start to charge based, at least partly, upon aggregation. If extra
routes really cost you, charge for them where they enter your network. Heck,
charge per route if you want. This should work well for small to mid-sized
companies that generally have trouble getting settlement free peering. I
doubt you could pressure UUNet, Sprint, or C&W in this way.

	DS

----

I would say that the far simpler method is to filter.

If the filters cause harm to a settlement-free peer, then that
settlement-free peer should renegotiate the peering with the filtering-peer
to encourage them to accept the route table bloat.

If the settlement-free peer that is advertising the more specific routes
isn't interested in doing that, then the customer isn't paying their
upstream enough to be worth screwing with a system that is satisfactory to
their business case.

After years on the net, I think this is my general rule for the way things
work.

If something bothers you, you do something to mitigate it.
If you tell people what you've done, and they think its a good idea, they do
it to.
If enough people do something about it, then usually whoever was doing the
thing that was bothersome has an incentive to stop it.

If the bothersome thing doesn't stop, you've already mitigated it, and you
can scream till you are blue in the face, and only make a small dent in the
flow of things.

Case in point: RBL - Those that spam bothers a lot use it, and it helps.
Those who get put on it (because the combined power of the RBL is
significant to the affected parties) change their behavior or don't. Either
way, RBL recipients receive less bothersome behavior.

ORBS (when it was running) was used by lots of people. It bothered a lot of
other people. They started filtering ORBS. ORBS only affected people who
subscribed to it, and I am sure Abovenet could say [ORBS] didn't negatively
impact their business case. Neither side achieved a whole lot of critical
mass to sweep over the net. (Not saying RBL has either). ORBS subscribers
saw less bothersome behavior.

Verio and other networks that filter have decided that route table bloat is
an issue for their operations. Networks that peer with [Filtering Networks]
have decided that this doesn't really pose an issue to their operations.
Some customers of those Networks seem to have an issue with it, but not
enough to become [Filtering Networks] customers nor enough to convince their
upstreams to convince [Filtering Networks] to relax their filters.

The destinations that are cut off don't represent a serious business case to
the [Filtering Network] so the matter doesn't really have any steam.

In this case the [Filtering Network] has made a change to mitigate a problem
they find bothersome. Those affected by this have not achieved critical mass
to convince them or their upstreams to take action, even though they are
trying to improve their traffic flows.

Randy has offered as an engineer of Verio to help ease the amount of effort
required to do this.

Why would anyone's Customer think telling a [Filtering Network] IT should
renegotiate its working peering arrangements to suit another network's
Customer's needs is beyond me and anyway, its energetically unfavored.

Disclaimers: I have not tried to pick on Verio here, and it is my intent to
only paint specific parties in a positive light. Negative light may be cast
on categories, it is not intended to be offensive.

This whole message (less examples) could be summarized:

Rather than taking the position:

XXX is doing something I don't like and they should change it.

The Internet seems to favor this:

XXX and a bunch of other guys are doing things I don't like and I am going
to spend my time, money, and energy engineering a way to a) defeat/obsolete
what they are doing, b) make them look silly for doing it, c) bypass them,
or d) put them out of business.

If I am off base, it's probably not the first time, nor the last. :)

Deepak Jain
AiNET