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 ]
der Mouse
mouse at Rodents.Montreal.QC.CA
Thu Sep 2 18:01:14 CEST 2004
>>>> % 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. "The rules"? The rules as implemented, obviously. But there are rules under which 193.0.1 is filled out to 193.0.0.1; it sees 193.0 as a network portion and 1 as a host portion, the latter being a single 16-bit number expressed in decimal. (For example, 193.0.12345 would become 193.0.48.57.) I'm sure I found this in some RFC, but I can't recall which one, and some grepping doesn't find it. Perhaps my memory is flaking out, or perhaps I just haven't found the right grep pattern. /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse at rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
- 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 ]