This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] domain: object normalization
- Previous message (by thread): [db-wg] domain: object normalization
- Next message (by thread): [db-wg] domain: object normalization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Sep 2 23:57:36 CEST 2004
>>>> %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. you might want to be a bit more in line with internet standards. apologies for being too off balance here at apnic to give you an exact ref. but 127.1 is 127.0.0.1 etc. randy
- Previous message (by thread): [db-wg] domain: object normalization
- Next message (by thread): [db-wg] domain: object normalization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]