<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
It's interesting that Kathy mentioned Godaddy and take down requests. I
have a personal story about what happened with Godaddy taking out an
entire data center due to a spam complaint. I was hosted at the data
center and a friend of mine owns it and he had me make the call knowing
that I'm good at getting results. The data center was called
nectartech.com.<br>
<br>
What happened was that some customer got hacked and was sending spam.
The customer was using nectartech.com name servers as was most of their
customers. On Friday January 13th around 5:00pm Godaddy suspended the
nectartech.com domain. And it was a 3 day weekend. What happened then
was a legendary story about how I managed to get nectartech.com back
online in spite of Godaddy's suspention.<br>
<br>
This is a great anecdotal story about what can happen when registrars
go wild with domain suspension. You can read about it all over the
internet by googling godaddy and nectartech. What I did was to record
the phone call with Godaddy support and post it on the Internet/ About
18 hours later, service was restored. <br>
<br>
The thread starts here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.webhostingtalk.com/showthread.php?t=477562">http://www.webhostingtalk.com/showthread.php?t=477562</a><br>
<br>
And the recording with Godaddy is here:<br>
<br>
<a class="moz-txt-link-freetext" href="http://marc.perkel.com/audio/godaddy.mp3">http://marc.perkel.com/audio/godaddy.mp3</a><br>
<br>
It speaks to the problem Kathy talks about when it comes to due
process. In this case it was resolved due to some unique skills that
aren't available to most people. But if anyone needs an example of what
happens when a registrar wrongly suspends a domain, is one says it all.<br>
<br>
On 6/28/2010 1:33 AM, Alex Gakuru wrote:
<blockquote
cite="mid:AANLkTik_EslrBb-Dy1BuhYyg6YUnxmgYu45UfGxpQJrH@mail.gmail.com"
type="cite">Carlos,
<div><br>
</div>
<div>Would you be in a position to assert our voices on this WG?</div>
<div><br>
</div>
<div>kindly,</div>
<div><br>
</div>
<div>Alex<br>
<br>
<div class="gmail_quote">On Sun, Jun 27, 2010 at 9:21 PM, Kathy
Kleiman <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:Kathy@kathykleiman.com">Kathy@kathykleiman.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi
Carlos and All,<br>
I attended the same session and had similar concerns to those of
Carlos. On the good side, for the first time in my recollection of
these discussions, law enforcement at least discussed and answered
questions about the importance of due process and data
protection/privacy laws.<br>
<br>
on the downside, the road to registrars (and their RAA contract
changes) is being paved with a request for every sort of monitoring and
takedown request. Christine Jones, the respected General Counsel of
GoDaddy, complained bitterly about this in the Public Forum.<br>
<br>
The other downside is that, in such an important Working Group, there
is no NCUC representative. I know there are too many things going on,
and too many important issues, but this one is central. If you can put
someone on the WG (which has much more work to go), then NCUC's
insights, understandings, and concerns for due process and the limits
of the scope and mission of ICANN will have a much stronger voice than
comments alone.<br>
<br>
Best,<br>
<font color="#888888">Kathy</font>
<div>
<div class="h5"><br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I will be happy to try and help.<br>
<br>
fraternal regards<br>
<br>
--c.a.<br>
<br>
On 06/24/2010 07:28 AM, Alex Gakuru wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Jun 24, 2010 at 1:13 PM, Wendy Seltzer<<a
moz-do-not-send="true" href="mailto:wendy@seltzer.com" target="_blank">wendy@seltzer.com</a>>
wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Thanks Carlos,<br>
We should include you in drafting public comments on the RAA report
which<br>
attached the law enforcement recommendations.<br>
<br>
</blockquote>
<br>
I second Carlos inclusion on the drafters team.<br>
<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think at least some of the law enforcement representatives are
concerned<br>
about balance, and perhaps we can acknowledge their concerns while<br>
recommending safeguards and due process requirements to oppose many of
their<br>
specific recommendations.<br>
</blockquote>
<br>
<br>
Absolutely! On our comments, please call for privacy law enforcement<br>
representatives also?<br>
<br>
kindly,<br>
<br>
Alex<br>
<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Best,<br>
--Wendy<br>
<br>
<br>
On 06/24/2010 06:06 AM, Carlos A. Afonso wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have just read the transcript of the panel "Law Enforcement<br>
Amendments to the RAA ", held on 21 June, 2010 during the Brussels ICANN<br>
meeting. The panel was chaired by ALAC's Cheryl Langdon-Orr. Everyone<br>
seemed to be sort of happy of sharing a discussion room full of police
:)<br>
<br>
I do not understand the role law enforcers are supposed to play in<br>
defining ICANN policies.<br>
<br>
Law enforcers such as the FBI, Interpol etc work on a very simple<br>
paradigm: they follow orders, and the more information they get, the<br>
better to fulfill the orders they ought to follow. So they will always<br>
defend the idea that all private data should be recorded and made<br>
available to them whenever they deem necessary. It simply makes their<br>
job easier, and this is enough for them, and is all we will hear from<br>
them, whatever the nice dressing of their discourses.<br>
<br>
However, ICANN should be looking for appropriate policies which abide by<br>
internationally recognized human rights principles. This is the realm of<br>
legislators, policy-makers, regulators -- not law enforcers -- and these<br>
are the organizations ICANN should be talking to in deciding policies<br>
regarding balancing privacy rights with security.<br>
<br>
If decisions regarding the users' / consumers' rights to privacy are<br>
going to be taken on the advice of the police, I do not think we will<br>
arrive at a good end of this story.<br>
<br>
--c.a.<br>
<br>
<br>
<br>
</blockquote>
<br>
-- <br>
Wendy Seltzer -- <a moz-do-not-send="true"
href="mailto:wendy@seltzer.org" target="_blank">wendy@seltzer.org</a><br>
Fellow, Silicon Flatirons Center at University of Colorado Law School<br>
Fellow, Berkman Center for Internet& Society at Harvard University<br>
<a moz-do-not-send="true"
href="http://cyber.law.harvard.edu/seltzer.html" target="_blank">http://cyber.law.harvard.edu/seltzer.html</a><br>
<a moz-do-not-send="true"
href="http://www.chillingeffects.org/" target="_blank">http://www.chillingeffects.org/</a><br>
<a moz-do-not-send="true" href="https://www.torproject.org/"
target="_blank">https://www.torproject.org/</a><br>
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</body>
</html>