Massive changed in the Ripe Database..

Hi all,

> 	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.

I have indeed found my own RIPE entries indexed on WWW search engines,
which I find a violation of the copyright. However, one very significant 
purpose of the RIPE DB (IMHO) is that it is available for trouble-shooting.
This makes it necessary to give ISPs/IAPs access to it. In other words, you
might as well make it public.

> 	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=20
> 	   we can discuss), the deletions are rejected and the person
> 	   who request the delete is asked: "Why ?"

Same goes for all types of object, doesn't it ?
Yeah, well... I got a message yesterday asking me to stop flooding one
one the RIPE robots, just because I sent a batch of perfectly legitimate
update requests. I'm afraid that idea doesn't work, either.

Bernard


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 460 bytes
Desc: not available
URL: <https://www.ripe.net/ripe/mail/archives/lir-wg/attachments/19981104/f741a84d/attachment.sig>