transit across the ixs

Mailman List Mirror (Read Only)
1

you might be amused to write a bit of code to see if your ix peers are
giving you next-hops of other provider(s). it is clear that a number of
providers are selling transit across the ixs. not at all cool.

we can't decide whether to force next hop on their routes, or keep watching
and de-peer them if they do not cease and desist. what do others do in this
circumstance?

randy

2

I'm aware of at least one fairly major backbone who does
this (at least they used to).

What's the issue with this anyways? I mean, at least
superficially it's basically the same traffic. I can see
that there would be some issues with how the traffic
transitions the ixs, which may or may not be a problem.

Pete.

3

Doesnt your AUP cover this? If its a violation of AUP, notify them, then
force next hop, then de-peer in that order.

-Dan

4

we can't decide whether to force next hop on their routes, or keep
watching and de-peer them if they do not cease and desist. what do
others do in this circumstance?

Doesnt your AUP cover this? If its a violation of AUP, notify them, then
force next hop, then de-peer in that order.

apologies for being insufficiently clear. let me be more specific with my
question.

do you peer at the ixs? if so, do you detect such circumstances? if so,
what do you do? if not, no reply needed.

randy

5

I know of two major providers who are (well were 12 months ago) doing
this. I would call them up and try to get them to quit, if not and you can
afford it force next hop.

6

you might be amused to write a bit of code to see if your ix peers are
giving you next-hops of other provider(s). it is clear that a number of
providers are selling transit across the ixs. not at all cool.

Note that CIX does this by default at PAIX and on PB-SMDS. Not that those
are major exchanges by Randy's likely definition. The only time we force
next-hop-self is if the peer deliberately asks the exchange operator for
port filtering, or if we're otherwise explicitly requested by a BGP peer
send routes with next-hop-self.

7

you might be amused to write a bit of code to see if your ix peers are
giving you next-hops of other provider(s). it is clear that a number of
providers are selling transit across the ixs. not at all cool.

Note that CIX does this by default at PAIX and on PB-SMDS. Not that those
are major exchanges by Randy's likely definition. The only time we force
next-hop-self is if the peer deliberately asks the exchange operator for
port filtering, or if we're otherwise explicitly requested by a BGP peer
send routes with next-hop-self.

cool beans. employment security for level-3s at the noc. makes it really
fun to debug when packets come from places different where routes go. good
job.

randy