<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16850" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=295333415-02092009>On behalf of the
RyC, I would like to propose the following amendments to Mike Rodenbaugh's Fast
Flux motion. We hope they would be considered friendly but that is Mike's
call. Note that the current wording of the motion is in <EM>italic
font</EM><SPAN class=180424516-02092009><FONT color=#0000ff> </FONT><FONT
color=#000000>below and that I attached a red line version of the
resolution part of the motion.</FONT></SPAN>.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=295333415-02092009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=295333415-02092009>Chuck
Gomes</SPAN></FONT></DIV>
<DIV><FONT size=+0><SPAN class=295333415-02092009> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>(A) "<EM>To encourage ongoing discussions within
the community regarding the development of best practices and/or policy changes
to identify and mitigate the illicit uses of Fast Flux</EM>"</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN
class=812034216-21082009>Make</SPAN> a friendly amendment to change to:
"...the development of best practices and/or Internet industry solutions to
identify and mitigate..." </FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Reasons:<BR>* The WG did not recommend any policy
changes specific to fast-flux. The issue of domain name abuse in general
is a completely separate and more complicated matter<SPAN
class=812034216-21082009> -- see (B) below</SPAN>.<BR>* <SPAN
class=295333415-02092009>T</SPAN><SPAN class=812034216-21082009>he phrase
</SPAN>"Industry solutions" w<SPAN class=812034216-21082009>ere</SPAN> included
in the <SPAN class=812034216-21082009>relevant </SPAN>Final Report's
Recommendations section <SPAN class=812034216-21082009>-- </SPAN>but was
dropped in the Resolution language for some reason. See (C) below for why
Internet industry is a preferred option.<BR>* The creation of non-binding best
practices is a good idea; awareness-raising and education are needed and in
keeping with the RyC position. Such efforts could include the ccNSO or
other relevant bodies.</FONT></DIV>
<DIV><FONT size=+0><FONT face=Arial><FONT size=2><SPAN
class=295333415-02092009>* The RyC </SPAN>support<SPAN
class=295333415-02092009>s</SPAN> best practices and encourage<SPAN
class=295333415-02092009>s</SPAN> industry solutions by the wider Internet
community, rather than further policy change discussions.
</FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>(B) "<EM>To examine whether existing policy
sufficiently empowers Registries and Registrars to mitigate illicit uses of Fast
Flux, as a component of any future Registration Abuse PDP(s)</EM>"</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Make friendly amendment so as to read: "The
Registration Abuse Policy Working Group (RAPWG) should examine whether existing
policy may empower Registries and Registrars, <SPAN
class=295333415-02092009>including</SPAN> consideration for adequate
indemnification, to mitigate illicit uses of Fast Flux."</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Reasons:<BR>* Make the referral explicit. The
Registration Abuse Policies Working Group (RAPWG) was specifically created to
examine such abuse issues, and was an explicit outgrowth of the learning done in
the FFWG. Core issues are now being examined in the RAPWG. <BR>* It
is not agreed that GNSO policy can or should "empower" registries and registrars
to mitigate illicit FF. <BR>* "of any future Registration Abuse PDP(s)" is
poor wording. The GNSO has had several PDPs related to registration abuses
-- such as domain tasting. FF is not related to any and all registration
issues.</FONT></DIV>
<DIV><SPAN class=295333415-02092009><FONT face=Arial size=2>* The current
wording of the resolution implies that registries should be responsible for
mitigating fast-flux (and by extension other abusive uses of domain
names). </FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV>
<DIV><FONT face=Arial size=2>(C) "<EM>To encourage staff, interested
stakeholders, and subject matter experts to analyze the feasibility of a Fast
Flux Data Reporting System to collect data on the prevalence of illicit use, as
a tool to inform future discussions and/or policy work</EM>"</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Suggest friendly amendment to remove the words
"staff" and "and/or policy work." ICANN should not devote resources to the
creation or maintenance of a fast-flux reporting tool. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Reasons:<BR>* FF is an issue that ICANN is not
well-suited to deal with on a practical level, FF is really outside of GNSO
policy-making scope, and FF is not a core DNS security and stability issue
within ICANN's mission. <BR>* <SPAN
class=295333415-02092009>T</SPAN>herefore spending ICANN funds is not
relevant.<BR>* The Final Report points out that similar security issues are
dealt with by interested parties outside of ICANN -- such as for phishing (APWG
and PhishTank), botnets (ShadowServer and Conficker WG), and spam (Spamhaus and
the SURBLs). <BR>* NOTE: Discussion about a "Fast Flux Data
Reporting System" should be clear -- participation in such a tool was never
discussed as something that should be mandated by policy. A Fast Flux Data
Reporting System should not be equated with ICANN's WHOIS WDPRS reporting tool
[http://wdprs.internic.net/ ] -- the WDPRS is a compliance tool related to
existing contractual obligations that registrars and registrants must adhere to.
</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial
size=2></FONT> </DIV></DIV></SPAN></FONT></DIV></BODY></HTML>