<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
<br>
<br>
On 4/27/2012 2:00 PM, Jack Bates wrote:
<blockquote cite="mid:4F9ADEB5.3050305@brightok.net" type="cite">On
4/27/2012 12:09 PM, Chris Grundemann wrote:
<br>
<blockquote type="cite">On Fri, Apr 27, 2012 at 10:32, Lee
Dilkie<a class="moz-txt-link-rfc2396E" href="mailto:lee@dilkie.com"><lee@dilkie.com></a> wrote:
<br>
<br>
<blockquote type="cite">It seems to me, and I am not a lawyer,
that even requesting third party
<br>
customer information, much less storing it is just a ticking
time bomb...
<br>
waiting for the day ARIN gets either hacked or a
disgruntled/wikileaks
<br>
employee posts the information either publically or sells it.
<br>
</blockquote>
Of course, that could happen at the ISP as well...
<br>
<br>
</blockquote>
Of course. Like any secret, the more copies of the secret there
are, the more likely it will spread or become public knowledge. It
also becomes more problematic when you have a single location that
contains a lot of secrets. It makes it more of a target for abuse.
<br>
<br>
<br>
Jack
<br>
</blockquote>
<br>
My point was more along the lines of "this is third party
information". It's one thing for an ISP's customer list to be
compromised. At least in a lawsuit a customer cannot claim that the
ISP had no right to store the data. But I worry that for ARIN the
argument would come down to that, does ARIN have more liability
because it would have to make a non-obvious argument as to why it
needed to possess such data..<br>
<br>
just me being a worry-wart I guess.<br>
<br>
-lee<br>
<br>
</body>
</html>