RE: [gnso-ff-pdp-may08] 9.k, 9.l, 9.m, 9.n, 9.o, 9.p

["Greg Aaron" <gaaron@xxxxxxxxxxxx>]

Thanks, Paul.  I note that "Adopt accelerated domain suspension processing
in collaboration with certified investigators/responders (9.o)" is more than
a technical measure, and has significant legal and business components.
Some stakeholders have stated that mandating participation in such a program
would be outside the scope of GNSO policy-making.

With best wishes,
--Greg 



-----Original Message-----
From: Diaz, Paul [mailto:pdiaz@xxxxxxxxxxxxxxxxxxxx] 
Sent: Monday, May 11, 2009 3:22 PM
To: gnso-ff-pdp-May08@xxxxxxxxx
Subject: [gnso-ff-pdp-may08] 9.k, 9.l, 9.m, 9.n, 9.o, 9.p


Re: Public Comments Issue Group 9, "Next Steps/Possible Solution"

Issue:
Jon Orbeton, an Information Security Engineer at PayPal, "implores"
ICANN to adopt some of the potential technical measures that could be
adopted to mitigate the negative effects of fast flux, including:

*  Make additional non-private information about registered domains
available through DNS based queries (9.k);

*  Make additional non-private information about registered domains
available through DNS (9.l);

*  Cooperative, community initiatives designed to facilitate data
sharing and the identification of problematic domain names (9.m);

*  Stronger registrant verification procedures (9.n); and

*  Adopt accelerated domain suspension processing in collaboration with
certified investigators/responders (9.o)


Proposed Response:
The Final Report provides a list of possible measures at Lines 251-282,
and more fully develops these ideas at Lines 1383-1469.  As noted in the
Report, however, the WG participants did not reach consensus on many of
these proposals.  Ultimately, the GNSO will need to decide whether to
recommend the implementation any of these potential technical measures.