[db-wg] domain: object normalization

[ old thread, but I've been away ]

Andrei Robachevsky wrote:
> Hi Randy,
> 
> Randy Bush wrote:
> 
>>> %WARNING:905: fixed lookup key
>>> %
>>> % The key "193.0.1" has been changed to "193.0.1.0" for lookup.
>>
>>
>>
>> uh, that should that not be 193.0.0.1?
>>
> 
> It probably should be.

No, the rules assume that any octets missing are added on as zeros at the 
end.  So:

193/8 becomes 193.0.0.0/8

The engine also sets any non-zero bits to 0 after the CIDR boundary, so:

161.15/14 becomes 161.12.0.0/14

These rules are the same whether the network part is specified or not.

>>> The server will return a similar warning for these cases:
>>>
>>> %WARNING:905: fixed lookup key
>>> %
>>> % The key "122.109.193.in-addr.arpa." has been changed to 
>>> "122.109.193.in-addr.arpa" for lookup.
>>
>>
>>
>> as both 193.0.1 and domains with trailing dots are quite legal
>> syntax, is a warning appropriate?  of what are you warning?
>>
> 
> We are warning that people might have made a typo, instead of using 
> another valid form of an address or a name. It also indicates that the 
> actual key in the database is [slightly] different.

The server outputs these changes as a warning - we found that users would 
get confused otherwise sometimes, especially in the case where we set bits 
to zero.

-- 
Shane Kerr
RIPE NCC