<<<
Chronological Index
>>> <<<
Thread Index
>>>
[council] FW: [ipf] SSAC advisory on fast flux hosting and DNS
- To: "'Council GNSO'" <council@xxxxxxxxxxxxxx>, "'BC list'" <bclist@xxxxxxxxxxxx>
- Subject: [council] FW: [ipf] SSAC advisory on fast flux hosting and DNS
- From: "Mike Rodenbaugh" <mxrodenbaugh@xxxxxxxxx>
- Date: Thu, 31 Jan 2008 09:02:56 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language; b=CNolkaAsi4mZ5rKxfrKRpGBSX1viEcbDOX/ue8GxUgm3MgjAq7G+t1VjqbW+E1w+Us25Wokk8w3XgqecsFhW3Z48iWWYe1vjjV4gGeL9xKEve/0FF22Huer+KrBrVPyIXoIB8JOhkNHUZF1qSugY8Py3FSIE2gMum8sJ/6b5GcQ= ;
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AchjYJ/b3qaroc9TEdyBDwAX8sPTkQAyZoTQ
http://www.icann.org/committees/security/sac025.pdf
Fyi there is a recent report from SSAC, which recommends that the community
examine steps to mitigate the criminal effects of fast flux hosting. The
rise of fast flux hosting has had severely negative effects on law
enforcement (private and governmental) efforts to deal with e-crime.
Moreover, fast flux hosting appears to have no legitimate purpose, and can
be effectively mitigated by certain steps adopted by some registries and
registrars already. SSAC has done great background work here, and now I
think it is time for the GNSO to take lead on this issue.
I would like to have preliminary discussion at a Council meeting in the near
future, please. I also copy the Business Constituency for comments back to
me or the BC List please.
Thanks,
Mike Rodenbaugh
-----Original Message-----
From: Dave Piscitello [mailto:dave.piscitello@xxxxxxxxx]
Sent: Wednesday, January 30, 2008 8:53 AM
To: ipf@xxxxxxxxxxxxxxxxxxxxx
Subject: [ipf] SSAC advisory on fast flux hosting and DNS
Is now published at
http://www.icann.org/committees/security/sac025.pdf
Many of you deserve our thanks for providing valuable insights. You will
undoubtedly note these as you read. I've also alluded to or referenced APWG
activities and reports in the Advisory.
Think of this Advisory as first in a series of efforts. Most of the ICANN
community is at best vaguely familiar with criminal activities and how
criminals are pursued. Hopefully this Advisory provides much-needed
education and awareness. We also enumerate current and possible
countermeasures. We hope that a broader and more uniform set of practices
emerges from our findings and recommendations.
SSAC doesn't dictate or write policy. We only advise ICANN, its BoD, and the
community. We can make recommendations, but it's up to ICANN, the registries
and registrars, and other affected and influencing parties to act on our
recommendations.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|