Ronald F. Guilmette via db-wg wrote on 13/06/2021 23:30:
Assuming that that is the current plan, then Ed's results and mine are in reasonably close agreement with regards to the number of IPv4 route objects that need to be purged, i.e. some 800+.
Your figure is nearly double that, so obviously, you are fishing out a rather different set of IPv4 route objects than Ed and I are.
yep that's correct - the previous figures included internal RIR resource re-registrations and resource transfers, which will need to be dealt with at some point in future. You can get comparable output for the current discussion as follows:
% perl -I lib bin/bogonsearch.pl --protocol 4 --no-checkregtime --authsource delegated | gron - | grep route | wc -l 834 % perl -I lib bin/bogonsearch.pl --protocol 6 --no-checkregtime --authsource delegated | gron - | grep route | wc -l 58
The output of these is here: ipv4: https://pastebin.com/7dSHSnHa ipv6: https://pastebin.com/XegepuBZ This turns up several additional prefixes. 156.38.0.0/24 156.38.1.0/24 156.38.2.0/24 156.38.3.0/24 169.239.104.0/22 196.43.234.0/24 41.57.124.0/22 41.57.124.0/23 41.57.124.0/24 41.57.125.0/24 41.57.126.0/23 41.57.126.0/24 41.57.127.0/24 2c0f:f0a8::/32 Nick