This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] Annoucing supernets in BGP?
- Previous message (by thread): [routing-wg] Annoucing supernets in BGP?
- Next message (by thread): [routing-wg] Annoucing supernets in BGP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
daniel.karrenberg at ripe.net
Wed Sep 12 23:40:10 CEST 2012
On 12.09.2012, at 22:46 , Florian Weimer wrote: > ... If the prefixes end up in RIS, this could come from leakage > by a Swisscom customer (and another upstream which doesn't filter > properly), or a misconfigured BGP peering for the RIS data feed. Looks like AS35054 is to blame: https://stat.ripe.net/widget/looking-glass#w%5Bresource%5D=80/5 : IIRC we talked to them ages ago and it was difficult for them to give RIS another view in Geneva. But my recollection may be wrong ... Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/routing-wg/attachments/20120912/83225476/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2012-09-12 at 23.37.33 .png Type: image/png Size: 69961 bytes Desc: not available URL: </ripe/mail/archives/routing-wg/attachments/20120912/83225476/attachment.png>
- Previous message (by thread): [routing-wg] Annoucing supernets in BGP?
- Next message (by thread): [routing-wg] Annoucing supernets in BGP?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]