About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [address-policy-wg] RIPE DB: disclosure of commertial information

  • From: =?UTF-8?B?RGVubmlzIEx1bmRzdHLDtm0=?= <
    >
  • Date: Wed, 18 May 2005 10:33:14 +0200

Yes indeed. But in the ideal world noone does nasty things. And yes. It would be better If all information was available at any time.
Unfortunatly there will allways be people misusing this freedom so to say.
So the only option would be to hide some fields from the public whois. But we need to count in, that this will decrease the usability of the DB in general. NIC-se introduced a system some years back where their registrars could log in to a full unrestricted whois.
But on the other hand, displaying full info for LIR:s only would be a bit to sadistic.
Maybe a sollution would be to bind complete db access to a legal contract, wich needs to be applied for?

Best regards.

--Dennis Lundström
GiPPNET AB, Stockholm Sweden

Max Tulyev wrote:

Hello!


In most countries technical contacts don't decide which ISP to
buy connectivity from...

But technical peoples are that neck directing the head ;-)


Besides, there are other ways to find the info you want:
- dig (nslookup) www.bibgcompany.su -> IP address
whois IP address -> you know which ISP's customer the company is
- dig (nslookup -type=SOA) bibgcompany.su (SOA) -> E-Mail address
of responisble for dns
- send mail to info@localhost ...
- Meybe use a phone book and call in?

Ofcource yes. But RIPE DB is amazing tool if an attack directed againist certain ISP.


In western (european?) countries there are trade laws which don't allow
address harvesting (especially whois entries and other public data),
placing unwanted offers, etc.

Unfortunallly, there is no such laws in eastern one...

I found an answer (bugfix?) to my question as using my contacts in assigned block againist using client's one.

But I still think that some fields in RIPE DB should be hidden from public access (for example, crypted MD5 password, business sensistive data like clients contacts and maybe other). Like changed: attribute is now.

Many other DB's have public and private access now, and it is good. For example, russian domains .ru and .su (RIPN DB) show only contact information for domain owner, and other data like mandatory passport and registration address fields are hidden.





 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community