On Fri, Oct 30, 1998 at 04:54:50PM +0100, Petra Zeidler wrote: : shoot him to the moon? :-3 Would suit my feelings better .. anyone can : err, but then messing with my repair work by faking our headers is way off : bounds. : This whole little escapade cost Xlink about 3 man-days work, and we're not : finished mopping up yet. Well....I think, we must have another database access. My ideas: 1. No Public Access to the Database I think, we have all (and our customers) problems (with email spam, and the normal snail mail spam. Many of the addresses are only in the RIPE DB. 2. Protection of the RIPE DB Objects Well, we can protect the person objects with our mnt objects. if anyone change the local ir, the old local ir can change the mnt entry in the object to the new local ir. 3. special work with person objects the only way to create, modify and delete person objects is the way to create, modify and delete person objects at a regional IR (denic@germany etc.). Non-Members of regional IR can only create, modify and delete person templates @ the local ir, where they register domains, or register ip networks. 4. Special work with RIPE objects in common what about a timestamped list of requests to the RIPE DB ? If anyone wants to delete objects, and do it in an interval of 10 deletions in 5 seconds (or any other interval we can discuss), the deletions are rejected and the person who request the delete is asked: "Why ?" these 4 points are just ideas...dunno if we can deploy it, but I think we can discuss several problems with the RIPE DB, and think about a solution of the problems. My 2Cent :) sh -- Stephan Hermann, techn. Leiter eMail office: sh@nwu.de NWU GmbH, Am Brambusch 1, D-44536 Luenen home : sh@linux.de Sales: Widumer Str. 28, D-44339 Dortmund Tel.: +49-231-9809110 sales-eMail: vertrieb@nwu.de FAX : +49-231-98091120