Sorry, you need to enable JavaScript to visit this website.

GNSO Council Teleconference Agenda

Last Updated:
09 September 2009
Date

Proposed GNSO Council Agenda 17 April 2008



This agenda was established according to the Rules of Procedure for the GNSO Council



Coordinated Universal Time12:00 UTC - see below for local times

(05:00 Los Angeles, 08:00 Washington DC, 13:00 London, 14:00 Brussels, 22:00 Melbourne)



Avri Doria will be chairing the GNSO Council meeting

Scheduled time for meeting 120 mins.

Dial-in numbers sent individually to Council members.



Item 0: Roll call of Council members

Item 1: Update any statements of interest

Item 2: Review/amend agenda



Item 3: Approve GNSO Council minutes of March 6, 2008 (5 mins)

http://gnso.icann.org/mailing-lists/archives/council/msg04907.html



Item 4: Update from Denise Michel on Board activities (10 mins)



Item 5: Update from Edmon Chung on IDNC (10 mins)



Item 6: GNSO Improvements - update (10 mins)



Item 7: New gTLD - follow up (10 mins)

Item 8: Discussion on how to complete deliberations on IRTP PDP – Denial Definitions (15 mins)

http://gnso.icann.org/drafts/final-report-irt-policy-09apr08.pdf

Item 9: Proposed IRTP PDP recommendations (15 mins)

http://gnso.icann.org/drafts/transfer-wg-recommendations-pdp-groupings-…



Item 10: Domain Tasting PDP discussion/vote (15 mins)

http://gnso.icann.org/issues/domain-tasting/gnso-final-report-domain-ta…

Item 11: Fast Flux Issues Report discussion (15 mins)

http://gnso.icann.org/issues/fast-flux-hosting/gnso-issues-report-fast-…

Motion proposed by Mike Rodenbaugh

Whereas, "fast flux" DNS changes are increasingly being used to commit crime and frustrate law enforcement efforts to combat crime, with criminals

rapidly modifying IP addresses and/or nameservers in effort to evade detection and shutdown of their criminal website;



Whereas, the Security and Stability Advisory Committee has reported on this trend in its Advisory SAC 025, dated January 2008:

http://www.icann.org/committees/security/sac025.pdf/



Whereas, the SSAC Advisory describes the technical aspects of fast flux hosting, explains how DNS is being exploited to abet criminal activities,

discusses current and possible methods of mitigating this activity, and recommends that appropriate bodies consider policies that would make

practical mitigation methods universally available to all registrants, ISPs, registrars and registries,



Whereas, the GNSO resolved on March 6, 2008 to request an Issues Report from ICANN Staff, to consider the SAC Advisory and outline potential next steps for GNSO policy development designed to mitigate the current ability for criminals to exploit the NS via "fast flux" IP and/or nameserver changes;

Whereas, the ICANN Staff has prepared an Issues Report dated March 25, 2008,

http://gnso.icann.org/issues/fast-flux-hosting/gnso-issues-report-fast-…- 25mar08.pdf,

recommending that the GNSO sponsor additional fact-finding and research to develop best practices guidelines concerning fast flux `hosting, and to provide data to assist policy development and illuminate potential policy options.;

Whereas, ICANN should consider whether and how it might encourage registry operators and registrars to take steps that would help to reduce the damage done by cybercriminals, by curtailing the effectiveness of these fast flux hosting exploits.



The GNSO Council RESOLVES:



To initiate a Policy Development Process in accord with the ICANN Bylaws, by forming a Task Force of interested stakeholders and Constituency

representatives, to collaborate broadly with knowledgeable individuals and organizations, in order to develop potential policy options to curtail the

criminal use of fast flux hosting.

The Task Force initially shall consider the following questions:

..Who benefits from fast flux, and who is harmed?

..Who would benefit from cessation of the practice and who would be harmed?

..How are registry operators involved in fast flux hosting activities?

..How are registrars involved in fast flux hosting activities?

..How are registrants affected by fast flux hosting?

..How are Internet users affected by fast flux hosting?

..What measures could be implemented by registries and registrars to mitigate the negative effects of fast flux?

..What would be the impact (positive or negative) of establishing limitations, guidelines, or restrictions on registrants, registrars and/or registries with respect to practices that enable or facilitate fast flux hosting?

The Task Force shall report back to Council within 90 days, with a report discussing these questions and the range of possible answers developed by the Task Force members. The Task Force report also shall outline potential next steps for Council deliberation.

Item 12: Single character 2 letter domain names

http://gnso.icann.org/drafts/icann-synthesis-on-sldns-27feb08.pdf

Item 13: ALAC Letter to Board on "front-running" and Board referral to GNSO council (10 mins)



- ALAC letter: <http://gnso.icann.org/mailing-lists/archives/council/msg04857.html >

- Board Prelim Minutes

Discussion under 11 Other business: <http://www.icann.org/minutes/prelim-report-27mar08.htm > Board's Disposition: "The Chair determined that emergency action is not required today but the matter will be referred to the GNSO for additional information or policy development if necessary, but not an emergency action."



13.1 D o we need an issues report?

13.2 Discussion of SSAC note from Steve Crocker

http://gnso.icann.org/mailing-lists/archives/council/msg04920.html

Item 14: Action Items

http://gnso.icann.org/meetings/pending-action-list.pdf

Item 15: AOB



(05:00 Los Angeles, 08:00 Washington DC, 13:00 London, 14:00 Brussels, 22:00 Melbourne)

----------------------------------------------------------------------------

Local time between March and October, Summer in the NORTHERN hemisphere

----------------------------------------------------------------------------

Reference (Coordinated Universal Time) UTC 12:00

----------------------------------------------------------------------------

California, USA (PST) UTC-8-0DST 05:00

New York/Washington DC, USA (EST) UTC-5+0DST 08:00

Buenos Aires, Argentina UTC-3+0DST 09:00

Rio de Janeiro, Brazil UTC-3+0DST 09:00

London, United Kingdom (BST) UTC+1DST 13:00

Brussels, Belgium (CEST) UTC+1+1DST 14:00

Karlsruhe, Germany (CEST) UTC+1+1DST 14:00

Barcelona, Spain (CEST) UTC+1+1DST 14:00

Oslo, Norway (CEST) UTC+1+1DST 14:00

Amman, Jordan UTC+2+1DST 15:00

Phnom Penh, Cambodia UTC+7+0DST 19:00

Hong Kong, China UTC+8+0DST 20:00

Singapore, Singapore UTC+8+0DST 20:00

Melbourne, Australia (EST) UTC+10+1DST 22:00

----------------------------------------------------------------------------

The DST starts/ends on last Sunday of October 2008, 2:00 or 3:00 local time (with exceptions)

----------------------------------------------------------------------

For other places see http://www.timeanddate.com