Honor PeeringDB 'info_never_via_route_servers' flag

[job]

Recently PeeringDB was extended to have a special informational flag info_never_via_route_servers that network operators can toggle to indicate that any route announcements containing their ASN anywhere in the AS_PATH are not expected to propagated via route servers. This can be implemented by rejecting routes, both by route server operators and on the Ingress EBGP policy attachment point in ISP's routing policies.

PeeringDB feature description: https://github.com/peeringdb/peeringdb#394

Example of an ASN that marked itself as 'never via route servers' https://www.peeringdb.com/api/net?asn=2914

All ASNs that marked themselves as info_never_via_route_servers = True can perhaps automatically be added to the TRANSIT_ANS data structure

IXP-Manager/resources/views/api/v4/router/server/bird2/filter-transit-networks.foil.php

Lines 14 to 30 in 7cd28f8

	define TRANSIT_ASNS = [ 174, # Cogent
	209, # Qwest (HE carries this on IXPs IPv6 (Jul 12 2018))
	701, # UUNET
	702, # UUNET
	1239, # Sprint
	1299, # Telia
	2914, # NTT Communications
	3257, # GTT Backbone
	3320, # Deutsche Telekom AG (DTAG)
	3356, # Level3
	3549, # Level3
	3561, # Savvis / CenturyLink
	4134, # Chinanet
	5511, # Orange opentransit
	6453, # Tata Communications
	6762, # Seabone / Telecom Italia
	7018 ]; # AT&T

I believe this feature to be beneficial to the internet community at large, it can help prevent some potentially contentious discussions about who should or shouldn't be on the TRANSIT_ASNS list.

[barryo]

Thanks @job - we'll have a look.

[barryo]

Just having a quick look:

https://www.peeringdb.com/api/net?info_never_via_route_servers=1

So ~7 results - how new is this feature and any idea when it may have some parity with your @job original list that you quoted in the issue above?

[job]

This feature is roughly two weeks old.

I am not sure when it will have parity - or if it ever will have full parity, for now I'd recommend that the 'original list' is and the info_never_via_route_servers=1 data are treated as a union set. "original list" U "peeringdb never_via_rs"

[barryo]

## Housekeeping Sept 2021

@barryo closing long running issues.

Where appropriate, will:

• Relocate to the IDEAS file.
• Add additional information below.
• No relocation / additional information for uber-stale issues.

Additional information: this has been relocated to IDEAs. NB: Ideas is not where things go to die (check the history of the file). It's where I house keep things that have no short term prospects of implementation. We have plans for OpenBGPd support, etc and all this requires big revisions to how we generate route server configs in IXP Manager. We'll include this in that process.