May 2008 - council - lists.icann.org

Invitation for cocktails & dessert after Council/Board dinner
by Gomes, Chuck 11 Jun '08

11 Jun '08

On behalf of VeriSign, I would like to personally invite all Council members for cocktails, coffee and dessert after the Board/Council dinner meeting in Paris on Sunday, 22 June. Group transportation will be provided at 9 pm for the short ride from the dinner to the Musée d'Orsay and again for the ride back to the hotel afterwards. Note that RSVPs are requested. Please let Glen and I know if you plan to attend and I will RSVP with Tamara Tate who is coordinated the event for VeriSign. Hope all of you can join us. Chuck Gomes

2 1

ICANN Board response to GAC recommendations
by Avri Doria 30 May '08

30 May '08

Hi, The following message from Peter to the GAC relating to Whois studies has been forward to me by Suzanne Sene for circulation to the council. I believe that in addition to discussing IDNccTLD issues in our Sunday afternoon interaction with the GAC, we should be ready to discuss the question of Whois studies and get their feedback on the proposals we will be considering at the GNSO council meeting on the 25th. a. Begin forwarded message:

2 1

Staff reponse to front running question from 8 May
by Liz Gasster 30 May '08

30 May '08

All, You may recall that on 8 May the Council asked staff about whether front running is encompassed by the RAA and whether there have been any compliance activities directed at front running. Attached please find staff's response to that question. This document has also been uploaded to the front running page on the Council wiki workspace, as follows: https://st.icann.org/gnso-council/index.cgi?front_running We hope you find this information helpful in your further discussions on the topic. Please let me know if you have any questions. Thanks, Liz

2 2

GNSO Council resolutions 29 May 2008
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 30 May '08

30 May '08

[To: council[at]gnso.icann.org] Dear Council Members, During its meeting of 29 May, the GNSO council decided to create a WG in order to meet its requirements for the PDP. The details are contained in the motion in plain text below. In order to initiate this working group the following steps are being taken: - This public announcement is being made of the working group's formation. Each constituency, and the liaisons, are invited to discuss the composition of the working group and to provide a list of names of expected participants who can then be added to the WG mailing list. Other stakeholders and experts may be invited to join the WG by the GNSO council. Community members who wish to be invited to join the group should contact the GNSO secretariat and the invitations will be reviewed by the GNSO council. - The Working Group will have an initial meeting on 21 June (time to be announced) in Paris. Remote participation facilities will be available. - At the initial meeting, one topic will be that of a picking a working group chair. The choice of working group chair will be subject to GNSO council approval at its meeting of 25 June. It is expected that discussion on candidates for chair will occur before the 21 June meeting. In the interim, Avri Doria, as GNSO council chair, will chair the working group. - The GNSO council in its approval of the charter decided that more guidance may be required on the meaning of rough consensus and its application to this WG. This topic will be discussed on the GNSO council list and if/when further guidance is agreed upon, it will be forwarded to the working group and its chair. - At its meeting on 25 June, the GNSO council will also decide on its liaison to the WG. Interested council members are invited to make their willingness to serve in this capacity known. , Glen ......................................................................... Motion passed by the GNSO Council ================================= Whereas Council has decided to launch a PDP to consider potential policy development to address fast flux hosting; Note from the GNSO Issues Report on Fast Flux Hosting: In this context, the term “fast flux” refers to rapid and repeated changes to A and/or NS resource records in a DNS zone, which have the effect of rapidly changing the location (IP address) to which the domain name of an Internet host (A) or name server (NS) resolves. The GNSO Council RESOLVES: To form a Working Group 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 WG is also open to invited experts and to members of the ICANN advisory committees whether acting in their own right or as representatives of their AC. Charter The Working Group 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? Are registry operators involved, or could they be, in fast flux hosting activities? If so, how? Are registrars involved in fast flux hosting activities? If so, how? How are registrants affected by fast flux hosting? How are Internet users affected by fast flux hosting? What technical, e.g. changes to the way in which DNS updates operate, and policy, e.g. changes to registry/registrar agreements or rules governing permissible registrant behavior 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? What would be the impact of these limitations, guidelines, or restrictions to product and service innovation? What are some of the best practices available with regard to protection from fast flux? Obtain expert opinion, as appropriate, on which areas of fast flux are in scope and out of scope for GNSO policy making. The Working Group shall report back to Council within 90 days, with a report discussing these questions and the range of possible answers developed by the Working Group members. The Working Group report also shall outline potential next steps for Council deliberation. These next steps may include further work items for the WG or policy recommendation for constituency and community comment and review and for council deliberation Working Group Processes: While the development of guidelines for Working operations, are still to be developed the following guidelines will apply to this WG: The WG shall function on the basis of rough consensus, meaning all points of view will be discussed until the chair can ascertain that the point of view is understood and has been covered. Anyone with a minority view will be invited to include a discussion in the WG report. Minority report should include the names and affiliations of those contributing to the minority report. In producing the WG report, the chair will be responsible for designating each position as having one of the following designations: Rough consensus position - a position where a small minority disagrees but most agree Strong support but significant opposition Minority viewpoint If several participants in a WG disagree with the designation given to a position by the chair or any other rough consensus call, they can follow these steps sequentially : Send email to the chair, copying the WG explaining why the decision is believed to be in error. If the chair still disagrees, forward the appeal to the council liaison(s) to the group. The chair must explain his or her reasoning in the response. If the liaisons support the chair's position, forward the appeal to the council. The liaison(s) must explain his or her reasoning in the response. If the council supports the chair and liaison's position, attach a statement of the appeal to the board report. This statement should include all of the documentation from all steps in the appeals process and should include a statement from the council. The chair, in consultation with the GNSO council liaison(s) is empowered to restrict the participation of someone who seriously disrupts the WG. Any such restriction will be reviewed by the GNSO council. Generally the participant should first be warned privately, and then warned publicly before such a restriction is put into place. In extreme circumstances this requirement may be bypassed. The WG will have an archived mailing list. The mailing list will be open for reading by the community. All WG meetings will be recorded and all recordings will be available to the public. A fast flux mailing list has been created <gnso-ff-pdp-may08(a)icann.org> public archives are at: http://forum.icann.org/lists/gnso-ff-pdp-may08/ If the guidelines for WG processes change during the course of the WG, the WG may continue to work under the guidelines active at the time it was (re)chartered or use the new guidelines. The council liaisons to the WG will be asked to report on the WG status monthly to the council. All WG charters must be reviewed by the GNSO council every 6 months for renewal. Milestone (dates to be updated if/when charter is approved) With assistance from Staff, template for constituency comments due 40 days after WG is initiated Constituency statements due 30 days after template is released. -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Inter-Registrar Transfer PDP, Clarification of Reasons for Denial
by Olof Nordling 30 May '08

30 May '08

Dear Councilors, FYI: The drafting group agreed yesterday to have one additional conference call, on 4 June, and to report to Council on progress and issues following that meeting. Very best regards Olof

1 0

GNSO Council teleconference MP3 recording 29 May 2008
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG 30 May '08

30 May '08

[To: ga[at]gnso.icann.org; announce[at]gnso.icann.org [To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference, held on May 29, 2008 at: http://audio.icann.org/gnso/gnso-council-20080529.mp3 http://gnso.icann.org/calendar/#may Happy listening! Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Draft of note to accompany announcement of the Fast Flux WG.
by Avri Doria 29 May '08

29 May '08

Hi, The following is the note I propose sending out, as discussed in today's meeting, with the record the motion we passed for the WG for the Fast Flux: ---- During its meeting of 29 May, the GNSO council decided to create a WG in order to meet its requirements for the PDP. The details are contained in the motion attached below. In order to initiate this working group the following steps are being taken: - A public announcement is being made of the working group's formation. Each constituency, and the liaisons, are invited to discuss the compositions of the working and to provide a list of names of expected participants who can then be added to the WG mailing list. Other stakeholders and experts may be invited to join the WG by the GNSO council. Community members who wish to be invited to join the group should contact the GNSO secretariat and the invitations will be reviewed by the GNSO council. - The Working Group will have an initial meeting on 21 June (time to be announced) in Paris. Remote participation facilities will be available. - At the initial meeting, one topic will be that of a picking a working group chair. The choice of working group chair will be subject to GNSO council approval at its meeting of 25 June. It is expected that discussion on candidates for chair will occur before the 21 June meeting. In the interim, Avri Doria, as GNSO council chair, will chair the working group. - The GNSO council in its approval of the charter decided that more guidance may be required on the meaning of rough consensus and its application to this WG. This topic will be discussed on the GNSO council list and if/when further guidance is agreed upon, it will be forwarded to the working group and its chair. - At its meeting on 25 June, the GNSO council will also decide on its liaison to the WG. Interested council members are invited to make their willingness to serve in this capacity known. Motion which was passed by the GNSO Council: https://st.icann.org/gnso-council/index.cgi?fast_flux

1 0

RE: Notification of New Registry Services Proposals Posted
by Patrick Jones 29 May '08

29 May '08

Dear Council, ICANN has today posted two new registry services proposals, one from DotCoop and another from mTLD Ltd. (DotMobi). DotCoop has proposed release of single and two-character names from its Schedule of Reserved Names via an RFP process. DotMobi has proposed release of single-character names from its Schedule of Reserved Names via an RFP process. The DotCoop proposal is available at http://www.icann.org/registries/rsep/#2008005. The DotMobi proposal is available at http://www.icann.org/registries/rsep/#2008006. Both proposals are now in ICANN's 15-calendar day preliminary determination period. Although public comments can be submitted at any time on a registry services proposal to registryservice at icann.org, this is not notification of a formal comment period. Information on the Registry Services Evaluation Process can be found at http://www.icann.org/registries/rsep/. Please let me know if you have additional questions. Regards, Patrick -- Patrick L. Jones Registry Liaison Manager & Coordinator, ICANN Nominating Committee Internet Corporation for Assigned Names & Numbers 4676 Admiralty Way, Suite 330 Marina del Rey, CA 90292 Tel: +1 310 301 3861 Fax: +1 310 823 8649 patrick.jones(a)icann.org

1 0

GNSO Improvements Implementation Plan Presentation
by Gomes, Chuck 29 May '08

29 May '08

I will be using the attached presentation to provide an overview of the GNSO Improvements Implementation Plan that we will be discussing in our meeting. Chuck

2 2

RE: [council] Registry/ Registrar Competition Report
by Tim Ruiz 29 May '08

29 May '08

1 0