Pascal, We're not an IP customer of Swisscom. On our European peers, we filter on the AS path. Filters are built based on the RIPE entries.
We have lots of peers all around Europe and cannot filter based on prefix lists as these would be quite too large to maintain with some peers. We rely on our peering partners for the announcements, and such invalid routes shouldn't be announced by Swisscom. What would be your suggestion to handle that? Fred Pascal Gloor wrote: > now he have it ;-P > > AS702 and AS3303 are both announcing 0.0.0.0/1 and 128.0.0.0/2 to their > customers... and look.. > > Orange is customer of PSI and UUnet... and PSI is customer of Swisscom.. > grrr... > > http://zebra.swinog.ch/wwwbin/searchipmask?ip=0.0.0.0 > http://zebra.swinog.ch/wwwbin/searchipmask?ip=128.0.0.0 > > have a look... > > I dont think we have anyone from UUnet in this list, but ppl from Swisscom, > think about the fact that not all of your customers have enough bgp > knowledge to handle those "internal" routes.. > > good, now you have a table of 75'000 routes and you announce 0.0.0.0/1 and > 128.0.0.0/2 internaly.. that's fine... what if we would all start to do > this? > > > my 0.02 cents... > > P. > > ---------------------------------------------- > [EMAIL PROTECTED] Maillist-Archive: > http://www.mail-archive.com/swinog%40swinog.ch/ > -- Best regards ----------------------------------- Frederic Borgeaud European peering coordinator Network engineering PSINetworks Europe ---------------------------------------------- [EMAIL PROTECTED] Maillist-Archive: http://www.mail-archive.com/swinog%40swinog.ch/
