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/
Database proposal
- Previous message (by thread): Database proposal
- Next message (by thread): Database proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Robert Martin-Legene
robert at DK.net
Mon Sep 8 14:08:55 CEST 1997
On Mon, 8 Sep 1997, TOB wrote: > At present the RIPE database is quite open, which means that it > potentially can be used as a marketing database. My proposal is that > only allocations are shown to everyone e.g the 195.41.0.0 /16 below. > There is sufficient information to contact the provider in e.g hacker > cases. I use the RIPE DB a LOT to look up who people are. And that's most definately not for marketing purposes, but to solve problems of my customers, or remote ones. It's a far better idea to use DNS for marketing issues than the RIPE DB. > The idea is that only the provider and RIPE(and of course the customer > itself) knows the individual assignments. It should be implemented by > hiding individual assignments in the RIPE database for everyone. If a > provider does not take a proper action in e.g hacker cases RIPE should > have the right to identify who the exact user of e.g a /24 is. I think the turn around time would be too long and it also makes it a lot more difficult tracking someone down if you want to block all connections from a specific allocation. It's most definately not all ISP's who replies to, even urgent, mail within a week.. if at all. -- Robert Martin-Legène (RM59), Network Manager (AS2109) main(){int a[2],b[2];pipe(a);pipe(b);if(fork()){dup2(a[0],0);dup2(b[1],1) ;}else{dup2(b[0],0);dup2(a[1],1);write(1,"R",1);}execlp("cat","cat",0);}
- Previous message (by thread): Database proposal
- Next message (by thread): Database proposal
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]