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] New on RIPE Labs: A Tale of BGP Collectors and Customer Cones
- Previous message (by thread): [routing-wg] BGP Update Report
- Next message (by thread): [routing-wg] New on RIPE Labs: Updates to the RIPE NCC Routing Information Service
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mirjam Kuehne
mir at ripe.net
Mon Oct 5 12:31:22 CEST 2015
Dear colleagues, When operators and researchers use data from BGP route collectors such as RIS and Route Views, it's not easy to tell if a path announced to a collector is an ISP's customer cone, an internal route, or one learned from peering or transit. In this new RIPE Labs post we look at what information we can currently get from BGP communities in RIS: https://labs.ripe.net/Members/emileaben/a-tale-of-bgp-collectors-and-customer-cones Kind regards, Mirjam Kuehne RIPE NCC
- Previous message (by thread): [routing-wg] BGP Update Report
- Next message (by thread): [routing-wg] New on RIPE Labs: Updates to the RIPE NCC Routing Information Service
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]