Hello,
Running rpsltool[1] against the RIPE database, it broke on a rather odd object in the RIPE database:
inet6num: 2a02:4c8::1/64
netname: ITDNET
descr: ITD Network, AD
country: BG
........
route6: 2a02:4c8::1/64
descr: ITD Network AD
origin: AS9070
.........
That doesn't seem right - the correct prefix would be 2a02:4c8::/64.
I've asked the RIPE NCC about this, and they explained that internally, the database silently discards the host bits. So for the database, this is 2a02:4c8::/64. This is also visible in whois queries: searching for 2a02:4c8::1/64 yields no results, you have to search for 2a02:4c8::/64.
Upon asking, the RIPE NCC responded that this is technically valid according to the relevant RFCs. But, they acknowledged that this behaviour can be confusing, and say they intend to disallow it at a later time.
Down to my specific question: has anyone made the appropriate modifications to rpsltool to handle these kind of objects, and also silently discard the host bits in the address? I imagine we can't be the first people running into this.
[1] http://www.linux.it/~md/software/