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/
Interesting object in the RIPE database
- Previous message (by thread): Interesting object in the RIPE database
- Next message (by thread): Interesting object in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steven Bakker
steven at icoe.att.com
Fri Jul 9 10:24:32 CEST 1999
>>>>> On Wed, 7 Jul 1999, "RLE" == Robert_Martin-Leg=E8ne wrote: RLE> Doesn't mean that it makes sense in the IP Registry world. Let's be RLE> practical. And besides, classful addressing is a Thing of the Past (ahem). The BSD way of doing it is clever, but complicated and it has no place in the DB, IMO. I always understood that the DB software would pad missing octets at the end of an IP address, no ambiguity there. What I'm surprised about is that the DB apparently allows someone to register address space that's most likely not even theirs... Of course, once it gets allocated and entered into the DB, a conflict will be detected and flagged (right!?), but until then, the error will go undetected. Is this a feature? Cheers, Steven
- Previous message (by thread): Interesting object in the RIPE database
- Next message (by thread): Interesting object in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]