not rewriting next-hop, pointing default, ...s

> Before you throw too many stones, these guys (I happen to know) take
> transit from UUnet, and not, before you ask, over the MAE. Personally
> I don't see a problem with this behaviour as a last resort.

If they buy transit, or do not buy transit from UUNet makes no difference.
You don't see a problem with pointing default at UUNet or any other
provider? This trace was to a network that did not exist, so it should not
have been sent to UUNet.

I'm not parsing your query.
The trace was to a network that did not exist and was sent to UUNet
because someone, with UUNet's permission presumably, had a preexisting
default route.

I have network.
You want access.
You buy T3 to me.
I send you routes.
Also, you default to me over a common exchange point as a backup.
T3 goes down.
Things fall over due to default route automagically.
Yes, it can be done with BGP and metrics over the common XP but
sometimes isn't.

Some question whether the XPs should be used for customer connectivity,
but that's a separate issue.

Or is that what you're driving at?

Nathan Stratton President, CTO, NetRail,Inc.


YES, just look at the data going over MAE-East and MAE-West a large
amount of that traffic is for customer connectivity. I guess it will not
mater most NSPs are setting up private peering, so the NAPs will soon just
turn into a place to sell transit. I just think it did not need to turn
out that way. Also of the current defaults at MAE-East most of them are
not there with permission from the provider they are point to. I have had
2 peers at MAE-East point default to me in the last 3 months.

Nathan Stratton President, CTO, NetRail,Inc.