more-specifics via IX

Mon Oct 15 13:27:04 UTC 2007

The problem is you're announcing the aggregate prefixes of your customer's
customers to your upstream providers and the traffic from your upstreams to
those networks will be routed through the IX (instead of your customer
connection) because of the longer prefix effect and so you're not charging
the traffic and you're losing revenue!!!

I think in this case, you have to filter all those prefixes learnt from the
IX.

Che-Hoo

On 10/15/07, Wolfgang Tremmel <wolfgang.tremmel at de-cix.net> wrote:
>
>
>  Am 15.10.2007 um 07:09 schrieb Bradley Urberg Carlson:
>
>
>
> I have a few customers' customers, who appear at a local IX.  Due to the
> MLPA-like nature of the IX, I hear their prefixes both at the IX and via my
> own transit customers.  I normally use localpref to prefer customer
> advertisements over peers' advertisements.
>
>
> There is a customer's customer who is advertising more-specifics at the IX
> (and using a different source AS, to boot).  I can think of a couple ways
> to prevent hearing these, but thought I should ask for suggestions first.
>
>
>
>
> you should honor your customers routing policy and simply accept the
> routes.
>
>
> Wolfgang
>
>  --
> Wolfgang Tremmel                     e-mail: wolfgang.tremmel at de-cix.net
> DE-CIX Management GmbH               Phone: +49 69 1730 902-26
> Lindleystr. 12, 60314 Frankfurt      Mobile: +49 173 340 4833
> Geschaeftsfuehrer Harald A. Summa    Fax: +49 69 4056 2716
> Registergericht AG Koeln, HRB 51135  http://www.de-cix.net
> Zentrale: Lichtstr. 43i, 50825 Koeln
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20071015/8c90f1d6/attachment.html>