BGP Large Community Policy

RegPEX IX (AS199911) tags all accepted routes with BGP Large Communities (RFC 8092) providing location and filtering information to participants.

Community Format

All RegPEX communities use the BGP Large Community format (RFC 8092): Global Administrator : Function : Parameter

199911 : Fonksiyon : Parametre
↑ RegPEX IX ASN

Location Communities (Informational)

These communities are added by RegPEX RS to all accepted routes and indicate the physical POP where the announcing member is connected.

199911 : 1002 : <ISO-3166-1-Numeric> — Country

Community	Country	ISO 3166-1
`199911:1002:100`	Bulgaria	BG / 100
`199911:1002:276`	Germany	DE / 276
`199911:1002:528`	Netherlands	NL / 528
`199911:1002:642`	Romania	RO / 642
`199911:1002:792`	Turkey	TR / 792

199911 : 1003 : <POP-ID> — Point of Presence

Community	POP	City	Country	Status
`199911:1003:1`	ODTU Teknokent ODTU Teknokent, Çankaya, Ankara	Ankara	TR	active
`199911:1003:2`	UPCELL Veri Merkezi UPCELL Data Center, Ankara	Ankara	TR	planned
`199911:1003:3`	ULUS TTN Turk Telekom Ortak Yerleşim, Ulus, Ankara	Ankara	TR	planned
`199911:1003:4`	Telepoint DC Telepoint Data Center, Sofia, Bulgaria	Sofya	BG	planned
`199911:1003:5`	Atakoy TTN Turk Telekom Ortak Yerleşim, Atakoy, İstanbul	İstanbul	TR	planned
`199911:1003:6`	Gayrettepe TTN Turk Telekom Ortak Yerleşim, Gayrettepe, İstanbul	İstanbul	TR	planned
`199911:1003:7`	NXDATA-1 DC NXDATA-1 Data Center, Bucharest, Romania	Bükreş	RO	planned
`199911:1003:8`	Equinix FR5 Equinix FR5, Frankfurt am Main, Germany	Frankfurt	DE	planned
`199911:1003:9`	NIKHEF DC NIKHEF, Science Park, Amsterdam, Netherlands	Amsterdam	NL	planned
`199911:1003:10`	Hatay TTN Turk Telekom Ortak Yerleşim, Hatay, İzmir	İzmir	TR	planned
`199911:1003:11`	Konak TTN Turk Telekom Ortak Yerleşim, Konak, İzmir	İzmir	TR	planned
`199911:1003:12`	Kiziltoprak TTN Turk Telekom Ortak Yerleşim, Kiziltoprak, Antalya	Antalya	TR	planned
`199911:1003:13`	NetDirekt DC NetDirekt Veri Merkezi, İzmir	İzmir	TR	planned
`199911:1003:14`	PenDC Bursa PenDC Veri Merkezi, Bursa	Bursa	TR	planned

Planned POPs are listed for reference. Communities will be activated when the POP becomes operational.

199911 : 1004 : <CITY-ID> — City

Community	City	Country	POP IDs
`199911:1004:1`	Ankara	TR	#1, #2, #3
`199911:1004:2`	Istanbul	TR	#5, #6
`199911:1004:3`	Izmir	TR	#10, #11, #13
`199911:1004:4`	Antalya	TR	#12
`199911:1004:5`	Bursa	TR	#14
`199911:1004:6`	Sofia	BG	#4
`199911:1004:7`	Bucharest	RO	#7
`199911:1004:8`	Frankfurt	DE	#8
`199911:1004:9`	Amsterdam	NL	#9

City communities are added to all routes from POPs in that city. A member connected at multiple POPs in the same city receives the same city community.

Filtering Communities (Informational)

These communities indicate why a route was filtered or accepted. Filtered routes are not propagated to the master table.

Community	Meaning
`199911:1000:1`	RPKI Valid
`199911:1000:2`	RPKI Unknown
`199911:1000:3`	RPKI Not Checked
`199911:1001:1`	IRRDB Valid
`199911:1001:2`	IRRDB Not Checked
`199911:1101:9`	Filtered: IRRDB prefix not found
`199911:1101:13`	Filtered: RPKI Invalid
`199911:1101:3`	Filtered: Bogon prefix
`199911:1101:1`	Filtered: Prefix too long (>/24)

Usage Examples

Lower local preference for routes from POP #1 (Ankara ODTU Teknokent):

# Bird2 example — filter by POP
if bgp_large_community ~ [(199911, 1003, 1)] then {
    bgp_local_pref = 80;  # prefer other paths
}

Lower local preference for all routes from Istanbul (city ID 2, all POPs):

# Bird2 example — filter by city
if bgp_large_community ~ [(199911, 1004, 2)] then {
    bgp_local_pref = 80;  # prefer other paths
}

Reject all routes from a specific country (e.g. Bulgaria, ISO 3166-1: 100):

# Bird2 example — filter by country
if bgp_large_community ~ [(199911, 1002, 100)] then {
    reject;
}