IRRDB Source doesn't update properly when using the PeeringDB auto import feature

[kmorin18]

ISSUE TYPE

Bug Report

OS

N/A

VERSION

define( 'APPLICATION_VERSION', '6.4.2' );
define( 'APPLICATION_VERDATE', '2024112000' );

ENVIRONMENT

N/A

CONFIGURATION

N/A

SUMMARY

When auto importing information for a customer via the PeeringDB

STEPS TO REPRODUCE

Import from PeeringDB any ASN that lists RADB:ASN in their AS-set field in peering DB

EXPECTED RESULTS

If the AS-set starts with RADB: or ARIN: or [...] the IRRDB Source field should update to that

ACTUAL RESULTS

The "IPv4 Peering Macro" just gets filled with "RADB:ASN" which doesn't seem to work very well with the IRRDB script (routes not accepted / added to the prefix list for said peer)

IMPORTANCE

Low importance, could be seen as a feature request rather than a bug. Mostly helpful for IXPs migrating to IXPM (ie need to import tens of ASNs at once)

RELEVANT LOGS

N/A

[agbcix]

I'd like to add that this appears impractical (and might not do what is intended).

The information in PeeringDB only refers to where the peer's AS-Set is to be taken from, but does not say anything about the source of its members.

For larger peers, members will almost always be spread over other IRRDB.

If you set the source to RADB only, the bgpq[34] will limit the source for the whole recursive lookup.

What you rather want is "the" source that has RADB as first/preferred entry. Selecting this automatically is way more complex.