outdated transit-free AS list
Hi, Was just looking at https://www.seattleix.net/rs-drops which is nice work but then saw that reference to http://bgpfilterguide.nlnog.net/guides/no_transit_leaks/ ... Any chance you could update the known transit-free networks; as that's more than just a little outdated. I mean you've got like 209, 702, 3549, 3561 and 4134 still in there and are actually missing 3491, 6830 and 12956. Thanks, Steven Van Steen Director Data Interconnect Operation & Integration T + 31 20 778 8537 Liberty Global B.V. Boeing Avenue 53 1119 PE Schiphol-Rijk The Netherlands
Actually... This list is not about transit-free networks at all, this list is about IXP-free networks, which should not show up on IXPs. Like Tier 1 carriers, not Tier 1 access networks. There are transit-free networks that do peer on IXPs, I would think. But if 6830 is an IXP-free network and has no plans to show up on IXPs in the future, then sure, add it. I'm not sure 12956 belongs in that list, though. -- Wilco On 16/06/2020 12:31, Van Steen, Steven via NLNOG wrote:
Hi,
Was just looking at https://www.seattleix.net/rs-drops which is nice work but then saw that reference to http://bgpfilterguide.nlnog.net/guides/no_transit_leaks/ …
Any chance you could update the known transit-free networks; as that’s more than just a little outdated. I mean you’ve got like 209, 702, 3549, 3561 and 4134 still in there and are actually missing 3491, 6830 and 12956.
Thanks,
*Steven Van Steen* Director Data Interconnect
Operation & Integration
*T*+ 31 20 778 8537
*Liberty Global B.V.*
Boeing Avenue 53
1119 PE Schiphol-Rijk
The Netherlands
_______________________________________________ NLNOG mailing list NLNOG@nlnog.net http://mailman.nlnog.net/listinfo/nlnog
Dear Wilco, On Tue, Jun 16, 2020 at 02:39:14PM +0200, Wilco Baan Hofman wrote:
Actually...
This list is not about transit-free networks at all, this list is about IXP-free networks, which should not show up on IXPs. Like Tier 1 carriers, not Tier 1 access networks. There are transit-free networks that do peer on IXPs, I would think.
But if 6830 is an IXP-free network and has no plans to show up on IXPs in the future, then sure, add it. I'm not sure 12956 belongs in that list, though.
My interpretation of this list is not necessary about IXPs or not, but focussed on 'peering' in the broader sense of the word. If you are *not* directly peering with 6830, on the majority of your BGP sessions you'll probably want to block announcements that have 6830 anywhere in the AS_PATH, except on your 'transit' sessions. Whether 6830 is present on IXPs or not is not relevant in this context. Describing what should be done in English is really really challenging! Pull requests welcome :-) Kind regards, Job
On Tue, Jun 16, 2020 at 10:31:26AM +0000, Van Steen, Steven via NLNOG wrote:
Was just looking at https://www.seattleix.net/rs-drops which is nice work but then saw that reference to http://bgpfilterguide.nlnog.net/guides/no_transit_leaks/ ...
Any chance you could update the known transit-free networks; as that's more than just a little outdated. I mean you've got like 209, 702, 3549, 3561 and 4134 still in there and are actually missing 3491, 6830 and 12956.
I won't add 12956 without their explicit consent. I will add 3491 and 6830! Thanks for the notification that it needs a bit of TLC :-) Kind regards, Job
participants (3)
-
Job Snijders -
Van Steen, Steven -
Wilco Baan Hofman