Sascha,<br><br><div class="gmail_quote">On Tue, Sep 4, 2012 at 8:59 PM, <span dir="ltr"><<a href="mailto:lists-ripe@c4inet.net" target="_blank">lists-ripe@c4inet.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Sep 04, 2012 at 05:29:19PM +0000, Milton L Mueller wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You are considering a policy change for the Whois, not for transfers<br>
transparency. Please don't confuse the two.<br>
</blockquote>
<br></div>
Please do not accuse me of something *you* brought into this<br>
discussion. I admit fault for falling into your trolling net though.<br>
<br></blockquote><div>I am not sure I got what you mean.<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Anyway, as long as all information like personal names, phone numbers,<br>
addresses and email are removed from these publications, I consider them suitably anonymised for the purposes of this policy.<br>
<br></blockquote><div>I share Milton's view that a name (etc) of a person acting in business is not personal only, however, a business ID, what is public information. This is the rule in my country which is not in the US and won't be.<br>
<br>What you said: sometimes purely personal data also included in the whois database. Milton and I understood this argument, and Milton answer was: this is a "whois problem". I would say, this is problem of keeping the address allocation process transparent while allowing hiding individual only information, Milton's and my approach may be the same.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
rgds,<br>
Sascha Luck<br></blockquote><div><br>There is a trade-off: I vote for the trancparency of the address allocation (and any change in the address allocated).<br><br>Thanks,<br><br>Géza <br></div></div><br>