In message CAK5YLgfKOkNBDANwHWzAcDLdfkSEOcETj0nwHHUVABQLFxUkaA@mail.gmail.com,
Aftab Siddiqui aftab.siddiqui@gmail.com wrote:
I was under the impression that it is not possible to create route objects
with private ASN, I tried it this morning to test as well and yes it
doesn't work. But I don't know how these showed up in the database.
I am pleased to see this topic raised on the apnic-talk mailing list.
Recently, I have been in communication with all five of the Regional
Internet registries and I have been doing my level best to persuade
them all that they should remove from their respective route registries
and and all route objects that make reference -either- (1) to unassigned
"bogon" IP address blocks -or- (2) to unassigned "bogon" AS numbers.
So far I have been at least particially successful in persuading the
various RIRs that such "bogon" route objects are not ones they should
be carrying and publishing in their respective IRR.
In the case of AFRINIC, at least, they have now eliminated all routes
that fall into either category from their data base.
Other RIRs have, in general, been cooperative in eliminating bogon route
objects that fall into category (1) from their respective data bases,
but ARIN, RIPE, and APNIC have expressed varying degrees of relunctance
when it comes to eliminating the bogon routes that fall into category (2)...
for reasons that remain quite entirely perplexing to me personally. (My
own view is that junk is junk, and that -all- of the bogon route objects
should be removed from all RIR route registries at the earliest possible
moment.)
I have just now re-run the scripts that I've developed to try to find the
remaining bogon route objects within the APNIC data base. These are
summarized below.
I have been in communication with APNIC staff members about these specific
bogon routes fairly continuously for over three weeks now, but the only
thing I am being told is that these routes are being "discussed internally".
Needless to say, that is not a terribly satisfying answer, and I continue
to hope that these internal discusssion may actually reach an endpoint
sometime before the (signed) system time values on my old 32-bit UNIX
system rolls over to negative numbers.
IPv4 routes using bogon ASNs -------------------------------
49.40.4.0/24 64520 2018-01-16
103.70.232.0/24 7363 2018-05-31
114.130.75.0/24 65505 2018-11-05
103.127.238.0/23 209956 2019-03-07
114.130.108.0/24 65530 2020-04-05
203.9.118.0/24 18549 2020-05-25
202.82.123.0/24 26799 2020-06-12
112.79.118.0/24 65010 2020-11-03
112.79.112.0/24 65010 2020-11-03
110.164.86.0/24 135074 2021-06-01
IPv6 routes using bogon ASNs -------------------------------
2405:0700:FFFF:FFFF:FFFF:FFFF::/112 45756 2015-05-05
In fairness, I did report to APNIC staff several IPv6 routes which made
reference to bogon ASNs, and with the exception of the one shown above,
those have indeed already been removed from the APNIC IRR.
My hope is that all of the other bogon routes shown above will likewise
follow those into oblivion in the near future.
Regards,
rfg
