[db-wg] rpsltool & odd prefixes in the RIPE db

Erik,

On Friday, 2012-05-04 14:18:01 +0200,
Erik Romijn <eromijn at solidlinks.nl> wrote:
> 
> 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.

I agree that the current situation is non-optimal. :)

Note that the lookup does tell you what it is doing on query:

%WARNING:905: fixed lookup key
%
% The key "2A02:4C8::1/64" has been changed to "2a02:4c8::/64" for lookup.

Regarding the update path, I think we should reject entries with
non-zero bits after the CIDR portion of the network address.

I'm not sure what to do about the existing entries. I'd recommend a
cleanup, actually, since they imply confusion on the maintainer's part.

--
Shane