ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-ff-pdp-may08] Crafting a solution for fast flux

  • To: "Marc Perkel" <marc@xxxxxxxxxx>, "gnso-ff-pdp-may08@xxxxxxxxx" <gnso-ff-pdp-may08@xxxxxxxxx>
  • Subject: Re: [gnso-ff-pdp-may08] Crafting a solution for fast flux
  • From: "Zbynek Loebl" <zbynek@xxxxxxxx>
  • Date: Thu, 17 Jul 2008 06:54:17 +0200

I have not participated in our discussions yet, I was on holidays :-). I think 
that this is a good direction to go in my view.
Zbynek Loebl

> -----Original Message----- 
> From: Marc Perkel <marc@xxxxxxxxxx> 
> To: "gnso-ff-pdp-may08@xxxxxxxxx" <gnso-ff-pdp-may08@xxxxxxxxx> 
> Date: 07/16/08 23:16 
> Subject: [gnso-ff-pdp-may08] Crafting a solution for fast flux 
> There appears to be more and more evidence that there are legit uses for 
> fast flux which makes me wonder what we should do about it. I should ask 
> this question.
> If there are legit uses for fast flux, especially relating to free 
> speech, then should we work to block it?
> It also supports some of the suggestions I've put forth. That we craft a 
> policy to make more information available through DNS to help others 
> detect fast flux. Then others, like myself and other spam filtering 
> systems, can use this information to help determine if email is spam or 
> free speech. The idea being that if a domain is fast fluxing AND it 
> wants you to give up your bank account information, that's not free 
> speech, that fraud.
> I don't think ICANN policy itself is going to stop fraud. However if 
> Whois information is provided through DNS information servers then it 
> can help others stop fraud.
> Thoughts?

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy