August 2010 - council - lists.icann.org

Update on WHOIS Privacy/Proxy Abuse Study and Draft RFP on Privacy/Proxy Reveal study for your review - deadline 30 August 2010
by Liz Gasster Aug. 16, 2010

Aug. 16, 2010

All, As you know, ICANN staff has been researching the feasibility and cost to study several high priority aspects of WHOIS, soliciting bids using an RFP approach to determine costs and feasibilities. That RFP process has been completed for two studies (WHOIS Misuse and WHOIS Registrant Identification) but is still underway for two more studies (WHOIS Privacy/Proxy Abuse and WHOIS Privacy/Proxy Reveal). The purpose of this email is to provide an update regarding progress our on the latter two studies. WHOIS Privacy and Proxy Abuse Studies A small staff review team has completed careful review and preliminary assessment of three RFP responses received for WHOIS Privacy and Proxy Abuse studies. The review team's consensus is that two proposals were of high quality, exhibiting many unique strengths and deserving of serious consideration. However, we were unable to assess whether either proposal would realistically produce required results at bid cost without clarifications regarding each proposed project's scope, methods, and associated efforts. As a result, staff has requested further detail from these two bidders, offering them approximately a month (until 16 September) to supply clarifications to be considered in our final assessment. Although we regret this delay, staff cannot provide a meaningful and confident assessment without clarification. We expect to deliver our final assessment of WHOIS Privacy and Proxy Abuse study feasibility, merits, limitations, and costs to the Council approximately two weeks after the above due date. WHOIS Privacy and Proxy Reveal Studies Staff has completed a draft Terms of Reference for WHOIS Privacy and Proxy Reveal studies (see attached). Staff believes this draft is now ready for your review prior to publication with an RFP soliciting bids. Feedback received from subject matter experts has been incorporated into this draft, helping to refine and sharpen study scope, methods, and inputs. Several issues that make this study especially challenging have been considered. Rationale and review questions are highlighted in italicized boxes throughout the draft, but you should feel free to comment on any aspect. In particular, we ask that those who generate relay and reveal requests during their normal course of business examine proposed inputs and comment on the feasibility of providing them, were they to participate in this study. Comments on draft WHOIS Privacy and Proxy Reveal Studies should be sent to me by 30 August 2010. Our goal is to publish this RFP in September for a 60-day period, generating responses to be assessed in November. Please let me know if you have any questions. Thanks, Liz

1 0

REVISED GNSO Council meeting draft minutes - 5 August 2010.
by Glen de Saint Géry Aug. 12, 2010

Aug. 12, 2010

Dear Councillors, Attached please find the REVISED draft minutes of the GNSO Council meeting on 5 August 2010. Item 2: OSC GNSO Improvement Recommendations: It was during this vote that Wendy Seltzer, due to connectivity issues, was dropped off the call at the time of the vote and did not vote. Not during the vote in Item 3 as previously noted. Apologies for the confusion. If no other comments are received, these minutes will be published as approved on August 21, 2010 on the website on page: http://gnso.icann.org/calendar/#aug Thank you. kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

REVISED GNSO Council meeting draft minutes - 5 August 2010.
by Glen de Saint Géry Aug. 12, 2010

Aug. 12, 2010

Dear Councillors, Attached please find the revised draft minutes of the GNSO Council meeting on 5 August 2010. Item 3: Whois Studies. The vote for the motion made by mike Rodenbaugh and seconded by Terry Davis has been modified to indicate that Wendy Seltzer was dropped off the call at the time of the vote due to connectivity issues. 7 Yes votes - Mike Rodenbaugh, Jaime Wagner, Debbie Hughes, Rafik Dammak, Mary Wong, Bill Drake, Olga Cavalli, "Wendy Seltzer, due to connectivity issues, was dropped off the call at the time of the vote and did not vote." Please let me know if you would like any other changes made. If no comments are received, these minutes will be published as approved on August 21, 2010 on the website on page: http://gnso.icann.org/calendar/#aug Thank you. kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

2 1

Motion and Document Deadline - Wednesday, 18 August 2010 for Council meeting on 26 August 2010
by Glen de Saint Géry Aug. 12, 2010

Aug. 12, 2010

Dear Councillors, As required in the GNSO Operating Procedures, motions and reports for consideration in the GNSO Council meeting on 26 August 2010 are due not later than 8 days in advance of that meeting, that is, Wednesday, 18 August 2010. Please note that the status update notes are no longer needed and the pending project list: http://gnso.icann.org/meetings/pending-projects-list.pdf reflects all updates. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Agenda for GNSO Council Meeting 26 August 2010
by Glen de Saint Géry Aug. 12, 2010

Aug. 12, 2010

Agenda for GNSO Council Meeting 26 August 2010. https://st.icann.org/gnso-council/index.cgi?proposed_agenda_26_august_2010 http://gnso.icann.org/meetings/agenda-council-26aug10-en.htm This agenda was established according to the GNSO Council Operating Procedures approved 5 August 2010 for the GNSO Council. http://gnso.icann.org/council/gnso-op-procedures-05aug10-en.pdf For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Time 20:00 UTC See the following and http://www.timeanddate.com/ for other times: 13:00 PDT; 15:00 CDT; 16:00 EST; 17:00 Buenos Aires; 17:00 Brazil; 22:00 CET; 24:00 Moscow Friday, 27 August 01:00 Pakistan; 04:00 Hong Kong; 05:00 Tokyo, 06:00 Melbourne Dial-in numbers will be sent individually to Council members. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. GNSO Council meeting audiocast http://stream.icann.org/gnso/ Item 1: Administrative matters (10 minutes) 1.1 Roll call of Council members 1.2 Update any statements of interest 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: * 5 August 2010 meeting - Approved 21 August 2010. Item 2: Overview of New Procedures Related to Voting (15 minutes) 2.1 Refer to: * GNSO Operating Procedures http://gnso.icann.org/council/gnso-op-procedures-05aug10-en.pdf * Cheat sheet for new voting procedures Visual Procedures Map<file:///\\council\visual-procedures-map-en.htm> covering abstentions, absences, and vacancies http://gnso.icann.org/council/visual-procedures-map-en.htm Abstention Notification Form<file:///\\council\abstention-notification-form-en.htm> to be completed by an officer of the abstaining Councilor's appointing organization (Stakeholder Group or Constituency, as appropriate) http://gnso.icann.org/council/abstention-notification-form-en.htm 2.2 Brief Overview (Ken Bour) 2.3 Discussion Item 3: Whois Studies (25 minutes) 3.1 Refer to: * Whois Studies Report: http://gnso.icann.org/issues/whois/whois-studies-report-for-gnso-23mar10-en… * RFP for Proxy/Abuse Study: http://www.icann.org/en/announcements/announcement-2-18may10-en.htm * Liz Gasster's summary chart of the studies: http://gnso.icann.org/whois/whois-studies-chart-30jul10-en.pdf * Brief overview of the study choices presented by Lisa Phifer on 15 July: http://brussels38.icann.org/meetings/brussels2010/presentation-whois-report… 3.2 Highlights of Report for Whois Study # 3 (Liz Gasster) 3.3 Motion to proceed with Study # 1 * Refer to motion: https://st.icann.org/gnso-council/index.cgi?26_august_motions * Discussion * Vote (Note that absentee voting will not be allowed for this but new procedures may apply.) 3.4 Continuing discussion of how to proceed in selecting studies 3.5 Next steps? Item 4: GNSO Endorsements for the AoC SSR & Whois Policies RTs (25 minutes) 4.1 Refer to: * GNSO AoC Reviews site: http://gnso.icann.org/aoc-reviews/ * GNSO SSR RT site: http://gnso.icann.org/aoc-reviews/dns-ssr-en.htm * GNSO Whois RT site: http://gnso.icann.org/aoc-reviews/whois-policies-en.htm 4.2 SG primary & alternate endorsements: CSG NCSG RrSG RySG SSR Primary Ken Silva SSR Alternate(s) Whois Primary Kathy Kleiman Whois Alternate(s) Kim G. von Arx 4.3 Summary of Geographic & Gender Diversity for SG Primary Endorsements: # from Africa # from Asia/Pacific # from Europe # from Latin America & Caribbean # from North America # Male # Female 0 4.4 Possible Candidates to Improve Diversity: Africa Asia/Pacific Europe Latin America & Caribbean North America Male # Female None 4.5 Should the GNSO add one or two candidates to improve diversity of either RT slate? * Discussion * Next steps? [e.g., motion(s) for consideration on 8 September] * Note: GNSO endorsement slate is due to Selectors not later than 12 September Item 5: Vertical Integration (VI) PDP WG (20 Minutes) 5.1 Refer to Revised Initial Report from the WG (insert link) 5.2 Overview of the report (Stéphane Van Gelder) * Discussion * Next steps? * Deadline for submission of report to the Board for their retreat: 13 September 5.3 Refer to motion (if any): https://st.icann.org/gnso-council/index.cgi?26_august_motions * Discussion * Vote * Follow-up actions Item 6: Ongoing Action Items (10 Minutes) 6.1 Next Steps for Prioritization of GNSO Projects (Chuck Gomes) 6.2 Registration Abuse Policies WG Recommendations Action Plan (Marika Konings) 6.3 Suggested improvements for GNSO Public Council meetings * (Wendy Seltzer) * Target date for completion of work and submission of input to Stéphane & Glen for schedule planning: 15 September. 6.4 Suggestions for GNSO Council interaction with the Board * (Stéphane Van Gelder) * Target date for completion of work and submission of input to Stéphane & Glen for schedule planning: 15 September. 6.5 Drafting team for draft DNS-CERT/SSR WG charter (Chuck Gomes) 6.6 Standing committee to monitor GNSO Improvements implementation (Glen de Saint Géry) 6.7 Council meeting dates for November, December & January (Glen de Saint Géry) Item 7: Other Business (5 Minutes) Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: 1. Create an Issues Report: requires an affirmative vote of more than 25% vote of each House or majority of one House; 2. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A): requires an affirmative vote of more than 33% of each House or more than 66% of one House; 3. Initiate a PDP Not Within Scope: requires an affirmative vote of more than 75% of one House and a majority of the other House ("GNSO Supermajority"); 4. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation; 5. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority; and 6. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded with respect to any contracting party affected by such contract provision. Appendix 2: Absentee Voting Procedures (Council Operating Procedures 4.4) Members that are absent from a meeting at the time of a vote on the following items may vote by absentee ballot: 1. Initiate a policy development process; 2. Forward a policy recommendation to the Board; 3. Recommend amendments to the ICANN Bylaws; 4. Fill a position open for election. The GNSO Secretariat will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, or web-based interface. Absentee ballots must be submitted within 72 hours following the start of the meeting in which a vote is initiated, except that, in exceptional circumstances announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 days. There must be a quorum for the meeting in which the vote is initiated. Local time between March and October, Summer in the NORTHERN hemisphere ________________________________________ Reference (Coordinated Universal Time) 20:00UTC ________________________________________ California, USA (PST) UTC-8+1DST 13:00 Cedar Rapids, USA (CDT) UTC-6+1DST 15:00 New York/Washington DC, USA (EDT) UTC-5+1DST 16:00 Buenos Aires, Argentina UTC-3+0DST 17:00 Rio de Janeiro/Sao Paulo Brazil UTC-3+0DST 17:00 Dublin, Ireland (GMT) UTC+0DST 21:00 Darmstadt, Germany (CET) UTC+1+1DST 22:00 Paris, France (CET) UTC+1+1DST 22:00 Moscow, Russian Federation (MSK) UTC+3+0DST 00:00 next day Karachi, Pakistan UTC+5+0DST 01:00 next day Hong Kong, China UTC+8+0DST 04:00 next day Tokyo, Japan UTC+9+0DST 05:00 next day Melbourne,/Sydney Australia (EDT) UTC+10+1DST 06:00 next day ________________________________________ The DST starts/ends on last Sunday of October 2010, 2:00 or 3:00 local time (with exceptions) ________________________________________ For other places see http://www.timeanddate.com/ Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

GNSO Council meeting draft minutes - 5 August 2010.
by Glen de Saint Géry Aug. 12, 2010

Aug. 12, 2010

Dear Councillors, Attached please find the draft minutes of the GNSO Council meeting on 5 August 2010. Please let me know if you would like any changes made. If no comments are received, these minutes will be published as approved on August 21, 2010 on the website on page: http://gnso.icann.org/calendar/#aug Thank you. kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

GNSO Council meeting Wednesday 8 September at 15:00UTC
by Glen de Saint Géry Aug. 11, 2010

Aug. 11, 2010

Dear Councillors, Just a reminder that it was agreed to change the GNSO Council meeting date in September to Wednesday, 8 September 2010 at 15:00 UTC. Please see the calendar page: http://gnso.icann.org/calendar/#sep Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

4 6

GNSO Project Prioritization
by Gomes, Chuck Aug. 10, 2010

Aug. 10, 2010

In follow-up to the poll we took in our Council meeting this past week regarding GNSO project prioritization, for those that selected the "Other" choice. Please respond on this list with a description of what your "Other" choice is. I will start of by repeating mine: A combination of option 2 (use the prioritization exercise results to make project decisions going forward) and option 4 (improve the process). For those who did not participate or did not vote, please feel free to submit a new option if you have one. Thanks, Chuck

5 11

RE: [council] Additions to GNSO Operating Procedures
by Tim Ruiz Aug. 10, 2010

Aug. 10, 2010

I'm not able to review the changes in context right now to know to what extent we may need our SG sign-off, if any. So It would be helpful to have until the end of week to object. Tim Sent from Go Daddy Mobile Mail using my iPad! > -------- Original Message -------- > Subject: [council] Additions to GNSO Operating Procedures > From: "Gomes, Chuck" <cgomes(a)verisign.com> > Date: Mon, August 09, 2010 9:16 pm > To: <council(a)gnso.icann.org> > > > GNSO Councilors: > I recently learned that, when > Staff was incorporating the > relevant sections of the CSG > Work Team recommendations (2.1 > and 2.2) into the GNSO > Operating Procedures (v2.0), > an important explanatory note > was inadvertently omitted. > Appropriately, Staff did not > transfer certain > non-procedural content, for > example, "Background" and > "Executive Summary." > Unfortunately, there were two > sentences that should have > been included; however, they > were originally located under > "Background" and, thus, were > not noticed. > What I am recommending is that > the following paragraph be > added immediately below the > GOP Chapter 7 heading and > before 7.1-Participation > Rules. It will be inserted in > a shaded box as follows: > [Important Note: The > recommendations in Chapter 7 > apply to both Constituencies > and Stakeholder Groups, > referred to collectively as > "Groups." In addition, with > respect to this Chapter's > contents, the word "should" > shall be interpreted to mean: > an obligation or duty to take > a certain course of action, > unless otherwise specified.] > Would anyone object if this > addition is made to the > version that the Council > approved on 5 August 2010? > If there are no objections, I > will ask Staff to update the > version on the GNSO web site > (http://gnso.icann.org/council > /docs.html); otherwise, we > will have to draft a motion > and put the matter to a vote > at our 26 August meeting. > Thank you, > Chuck Gomes

2 1

Letter from ICANN chair to GAC chair regarding GAC's comments on DAGv3 (published n October 2009)
by Bruce Tonkin Aug. 10, 2010

Aug. 10, 2010

Hello All, The chair of the ICANN Board has sent a letter to the GAC responding to the GAC's comments on version 3 of the draft Applicant Guidebook. It is quite significant in that it sets out the rationale for some of the recent Board decisions that led to DAGv4. Up until now ICANN usually explains the reason for including something in the guidebook - but this letter also identifies some reasons why certain suggestions have not been incorporated. Topics covered in the letter include: - Root scaling implications - Malicious conduct and abuse of the DNS - Intellectual Property Rights - Economic studies - Country and territory names prohibited in version 4 of the Draft Applicant - Definition of geographical strings insufficient and not in line with paragraphs 2.2 and 2.7 of the GAC principles regarding new gTLDs - Mechanisms for dealing with post-delegation deviation from conditions of government approval - Objection mechanisms should be improved - Resolution of competing string applications does not give rise to auction-derived surpluses, but is decided on the respective value of the applications for end users - Potential benefits of categories (or track differentiation) should be fully explored. Regards, Bruce Tonkin From: http://www.icann.org/correspondence/dengate-thrush-to-dryden-05aug10-en.pdf 5 August 2010 Heather Dryden Chair of the Governmental Advisory Committee Senior Advisor to the Government of Canada Dear Heather, GAC Comments on new gTLDs and Draft Applicant Guidebook version 3 Thank you for the GAC’s letter of 10 March 2010, providing comments on new gTLDs and version 3 of the Draft Applicant Guidebook. I believe the Board and GAC share a similar viewpoint that it would be in the global public interest that “... the opening up of the gTLD space is undertaken in a way that does not compromise the resilience and integrity of the DNS and serves the global public interest”. The Board is pleased with the way in which the various iterations of the guidebooks are evolving, and is particularly pleased by the mechanism whereby the overarching issues are being resolved through working groups comprised of members of the ICANN community and independent experts. I respond below to each of the areas of concern raised by the GAC. Root scaling implications ========================= ICANN supports the principle that the scale and rate of changes must not negatively impact the resilience, security and stability of the DNS. In February 2009, the ICANN Board requested the Root Server System Advisory Committee (RSSAC), the Security and Stability Advisory Committee(SSAC), and the ICANN staff (including ICANN Staff members dealing with technical issues and the IANA functions) to study the potential issues regarding the addition of IDNs, IPv6 addresses, DNSSEC and substantial numbers of new TLDs to the root zone. This study was completed in August 200 and posted for comment at http://www.icann.org/en/committees/dns-root/root-scaling-study-report-31aug… A complementary report http://www.icann.org/en/committees/dns-root/root-scaling-model-description-… describes the characteristics of the quantitative model developed by TNO for dynamic analysis of root scaling issues. In addition, and as part of ongoing efforts to ensure the stability of the DNS, ICANN contracted with the DNS Operations, Analysis and Research Center (https://www.dns-oarc.net ) as independent and well-respected experts to provide an analysis of the impact of adding IPv6, DNSSEC, and additional top-level domains to the ICANN-operated L root server. This study, while independent of the Root Server System Root Scaling study and focused specifically on the impact to the ICANN-operated L root server, has been used as input in the more comprehensive study undertaken by the Root Scaling Study Group. The final report of the DNS-OARC study was published at http://www.icann.org/en/topics/ssr/root-zone-augementation-analysis-17sep09… Regarding the number of strings in an application round, this was considered in the analysis and model for anticipated new gTLD delegation rates published by staff, and is available at http://www.icann.org/en/announcements/announcement-03mar10-en.htm This analysis indicates that processing constraints will limit delegation rates to a steady state even in the event of extremely large numbers of applications, so that even in a scenario where there are very many applications for new gTLDs, the rate of growth of the root zone would remain linear. The SSAC and RSSAC are considering the data and analysis in each of these reports and are expected to prepare recommendations for the Board on concrete steps (such as any limitations or emergency removal procedures) to be implemented prior to the initial gTLD application round. Malicious conduct and abuse of the DNS ====================================== Some have made the case that the introduction of new gTLDs will result in an increase in malicious conduct. While this has not been quantitatively demonstrated, significant steps have been taken to ensure that malicious conduct is mitigated in the new environment of new gTLDs through the introduction of several protections. These protections, described below, were the result of a study undertaken of malicious conduct as it related to the new gTLD space. During the study, ICANN staff solicited and received comments from multiple outside sources, including Intellectual Property Constituency (IPC), Registry Internet Safety Group (RISG), the Security and Stability Advisory Committee (SSAC), Computer Emergency Response Teams (CERTs) and members of the banking/financial, and Internet security communities. As a result of this work, nine measures were recommended to increase the benefits to overall security and stability for registrants and trust by all users of these new gTLD zones, and each of these requirements will be implemented in the program: • Vetted registry operators (background checks) • Demonstrated plan for DNSSEC deployment • Prohibition of DNS redirection or “wildcarding” • Removal of orphan glue records to eliminate a tool of spammers and others • Maintenance of thick WHOIS records • Centralized method of zone-file access • Documented registry abuse contacts and procedures • Participation in an expedited registry security request process. These are the recommendations of the experts in this area when asked the same question that was posed by the GAC. More detailed information about these recommendations is available in the Mitigating Malicious Conduct explanatory memorandum, available at: http://www.icann.org/en/topics/new-gtlds/mitigating-malicious-conduct-memo-… Intellectual Property Rights ============================ The GAC comments, in concert with other comments, were taken in account in version 4 of the Applicant Guidebook that, for the first time, included the set of proposed intellectual property rights protection mechanisms. In particular, ICANN has broadened the types of trademark registrations that must be honored in offering a “Sunrise” service and all new registries employing an IP Claims service must honor trademarks registered in all jurisdictions. The types of registrations offered protections have also been broadened for the Uniform Rapid Suspension Service, one of the new post-delegation rights protection mechanisms. The Post Delegation Dispute Resolution Policy has also been amended in response to specific recommendations from the ICANN community. Rather than recount all the changes here, please see the redlined proposals for: − The Clearinghouse Procedures http://www.icann.org/en/topics/new-gtlds/trademark-clearinghouse-redline-28… − URS Procedures http://www.icann.org/en/topics/new-gtlds/draft-urs-redline-28may10-en.pdf − Post Delegation Dispute Resolution Procedures http://www.icann.org/en/topics/new-gtlds/pddrp-redline-28may10-en.pdf Economic studies ================ The issues of costs and benefits to the expansion of the namespace, the possible impacts on users, the relevance of market power, and the use of defensive registrations are discussed in “An Economic Framework for the Analysis of the Expansion of Generic Top-Level Domain Names,” an independent study completed by economists Michael Katz, Gregory Rosston, and Theresa Sullivan and published by ICANN for comment in June 2010. See http://icann.org/en/topics/new-gtlds/economic-analysis-of-new-gtlds-16jun10… The report examines the current status of the gTLD market and surveys existing work that has been done on this set of economic issues. The report also outlines a number of potential case studies that would seek to quantify the net costs and benefits involved in the introduction of new gTLDs. Selected studies recommended in the report are now being initiated. It is possible that these second-phase studies will recommend particular measures for the gTLD evaluation process that would minimize external costs (including, for example, the cost of defensive registrations) while allowing socially beneficial innovation. In this case, any such recommendations will be considered by ICANN and subject to public consultation before being implemented. ICANN has published additional economic studies: • Report Of Dennis Carlton Regarding ICANN’s Proposed Mechanism for Introducing New gTLDs (http://www.icann.org/en/topics/new-gtlds/carlton-re-proposed-mechanism-05ju… ) • Preliminary Report of Dennis Carlton Regarding Impact of New gTLDs on Consumer Welfare (http://www.icann.org/en/topics/new-gtlds/prelim-report-consumer-welfare-04m… ) • Preliminary Analysis of Dennis Carlton Regarding Price Caps for New gTLD Internet Registries (http://www.icann.org/en/topics/new-gtlds/prelim-report-registry-price-caps-… ) • Report from CRA International “Revisiting Vertical Separation of Registries and Registrars” (http://www.icann.org/en/topics/new-gtlds/crai-report-24oct08-en.pdf ) In addition, the GNSO considered whether new gTLDs should be introduced and the net benefits of new gTLDs in its final report on the introduction of new gTLDs (http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm ). Country and territory names prohibited in version 4 of the Draft Applicant Guidebook ===================================================================================== As you are aware, the treatment of country and territory names in the DAG4 Guidebook was developed specifically to adhere to paragraph 2.2 of the GAC principles on new gTLDs, i.e., the GAC view that governments should not be denied the opportunity to apply for, or support an application for, their respective country or territory name. However, the GAC’s clarification of their interpretation of GAC principle 2.2 ("The GAC interprets para 2.2 of the GAC gTLD principles that the strings that are meaningful representation or abbreviation of a country or territory name should be handled through the forthcoming ccTLD PDP, and other geographical strings could be allowed in the gTLD space if in agreement with the relevant government or public authority.”) has resulted in a reconsideration of the treatment of country and territory names in the new gTLD process. This has resulted in a change of approach as reflected in the recently published draft version 4 of the Applicant Guidebook: namely, that country and territory names will not be available for delegation in the first round of the new gTLD application process. With regard to the definition of country names, the Board has sought to ensure both clarity for applicants, and appropriate safeguards for governments and the broad community. A considerable amount of time has been invested in working through the treatment of country and territory names to ensure it meets these two objectives. Following discussion at the Mexico City meeting, the Board recommended that the Applicant Guidebook be revised in two areas regarding this subject: (1) provide greater specificity as to what should be regarded as a representation of a country or territory name in the generic space, and (2) provide greater specificity in defining the qualifying support requirements for continent names, with a revised position to be posted for public comment. The resulting definition for country and territory names is based on ISO 3166-1 and other published lists to provide clarity for potential applicants and the community. It seeks to remove the ambiguity created by use of the term ‘meaningful representation.’ Therefore, the definition of country and territory names has not been amended in the recent Guidebook draft and remains consistent with the Board goals and resolution on this issue. While the revised criteria may have resulted in some changes to what names are afforded protection, there is no change to the original intent to protect all names listed in ISO 3166-1 or a short or long form of those names (and, importantly, translations of them). This level of increased clarity is important to provide process certainty for potential TLD applicants, governments and ccTLD operators – so that it is known which names are provided protections. The definition is objectively based on the ISO list, which is developed and maintained by a recognised international organisation. It is acknowledged that ICANN has used the concept of ‘meaningful representation’ of a country or territory in the context of the IDN ccTLD Fast Track. This reflects the objective of rapid initial deployment of IDNs and the associated need to remove as many potential obstacles as possible. There have always been particular sensitivities about geographic names where non-Latin scripts and a range of languages are involved. It does not follow that these considerations should automatically apply to the broader ccTLD and gTLD spaces. It is reasonable that the criteria for including names (the Fast Track) could be different than the criteria for excluding names (gTLDs). The ccNSO will be undertaking policy discussions, which may result in a change in position on these two issues. In particular, defining the distinction between country code and generic names may warrant a broader cross-SO/AC policy discussion. Once policy is developed, it will be appropriate for the Board to reconsider these positions. Definition of geographical strings insufficient and not in line with paragraphs 2.2 and 2.7 of the GAC principles regarding new gTLDs =================================================================================================== As mentioned above, the Board has sought to ensure, throughout the process of developing a framework for new gTLDs, that there is 1) clarity for applicants, and 2) appropriate safeguards for the benefit of the broad community. The current criteria for defining geographic names as reflected in version 4 of the Draft Applicant Guidebook are considered to meet the Board’s objectives and are also considered to address to the extent possible the GAC principles. The current definitions, combined with the secondary avenue of recourse available by way of objections are considered adequate to address the GAC’s concerns. It should be noted that much of the treatment of geographic names in the Applicant Guidebook was developed around the GAC Principles regarding new gTLDs, and conversations and correspondence with the GAC on this issue going back to 2008. On 2 October 2008, (http://www.icann.org/correspondence/twomey-to-karklins-02oct08.pdf ) following a teleconference with the GAC on 8 September 2008, the then CEO & President, Paul Twomey, wrote to the GAC explaining proposed principles to guide a procedure for implementing elements of paragraph 2.2. Place names were split into two categories, as follows: 1) sub-national geographical identifiers such as countries, states, provinces; and, 2) city names. Regional language or people descriptions were considered difficult to develop an implementation plan for this element of paragraph 2.2, because it will be difficult to determine the relevant government or public authority for a string which represents a language or people description as there are generally no recognised established rights for such descriptions. As described in the 2008 letter, city names were considered challenging because a city name can also be a generic term, or a brand name, and in many cases city names are not unique. Therefore, where it is clear that an applicant intends to use the gTLD for purposes associated with the city name evidence of support, or non-objection is necessary. However, provision is made in the Guidebook to protect sovereign rights by requiring government approval for capital city names in any language, of any country or territory listed in the ISO 3166-1 standard. During the teleconference of 8 September 2008, GAC members identified the ISO 3166-2 List, as an option for defining sub-national names. Accordingly, version 4 of the Applicant Guidebook provides protection for all the thousands of names on that list. Also during this call the idea of the GAC creating a list of geographic and geopolitical names was discussed, however, it is understood that the GAC moved away from this suggestion because it would be a resource intensive effort for all governments to undertake. In relation to paragraph 2.7, at the Board’s request, Paul Twomey (who was ICANN’s CEO and President), wrote to the GAC on 17 March 2009 (http://www.icann.org/correspondence/twomey-to-karklins-17mar09-en.pdf ), requesting the GAC’s input on possible options to resolve the outstanding implementation issues regarding the protection of geographic names at the second level. The end result of this request was a letter from the GAC to Paul Twomey, dated 26 May 2009 (http://www.icann.org/correspondence/karklins-to-twomey-29may09-en.pdf ), which proposed a solution, that was accepted by the Board and ultimately reflected in the draft Registry Agreement developed for new gTLDs. On this basis, the Board considers that this matter has been dealt with to the satisfaction of the Board and the GAC. Mechanisms for dealing with post-delegation deviation from conditions of government approval =========================================================================================== The GAC’s suggestion of including a clause in the registry agreement requiring that in the case of a dispute between a relevant Government and the registry operator, ICANN must comply with a legally binding decision in the relevant jurisdiction has been adopted. The Registry Agreement has been amended accordingly. In addition, the processes and remedies of the Registry Restrictions Dispute Resolution Procedure are available to governments in cases where the geographic name is applied for as a community-based TLD. The remedies that can be recommended to ICANN under this procedure include: • remedial measures for the registry to employ to ensure against allowing future registrations that do not comply with community-based restrictions; • suspension of accepting new domain name registrations in the gTLD until such time as violation(s) is cured; or, in extraordinary circumstances; • providing for the termination of a registry agreement. Other protections have been added to ensure ongoing government approval of the delegation. Further information is available in explanatory memoranda. The following “Withdrawal of Government Support – Post delegation procedures” (http://www.icann.org/en/topics/new-gtlds/withdrawal-government-support-28ma… ) and “Registry Transition Procedures” (http://www.icann.org/en/topics/new-gtlds/registry-transition-processes-28ma… ) were posted on 31 May 2010. Objection mechanisms should be improved ======================================== I reiterate my response of 22 September 2009, to the GAC on this issue: “It is difficult to predict with accuracy whether the costs of the objection procedure will prove to be a barrier to legitimate objections; however, it is felt that the existence of a fee to lodge an objection is necessary as a deterrent to frivolous objections. Interested parties may pool their resources to finance an objection that they consider to be legitimate and important. The rule that the prevailing party will be fully reimbursed for the filing fee and advance payment of costs that it paid (Article 14(e)) is intended to lessen the financial burden upon parties that file a well-founded objection. Finally, it should be recalled that the Independent Objector may also file an objection where, for various reasons (including cost), no other objection had been filed.” “Governments that are members of the GAC have a mechanism to provide advice to ICANN’s Board, in accordance with ICANN’s Bylaws; however, it is not clear that Bylaw was intended to provide an avenue for governments to provide advice on operational matters of this nature. The ICANN Board wishes to have a neutral, expert determination, based upon certain published standards, when deciding whether to accept an application for a new gTLD or if an objection should be upheld.” Reviewing that response and the issues posed in your letter, I would add the following. ICANN (and the community) devoted substantial resources to develop the policy and implementation models to protect important interests through an objection based dispute resolution benefit. Still, specific suggestions for improvements are encouraged and I understand some Supporting Organizations and Advisory Committees are forming groups to study the issue. ICANN staff will support that work. The costs of that process are paid directly to the dispute resolution provider – no fees are added as a deterrent to potential objectors. In fact, one intended result of the process is to discourage applicants of controversial names that may infringe upon those important interests. We note that governments pay fees for other services, enter into agreements, and pursue conflict resolution. We do not believe that governments should be afforded special consideration by exempting them from paying fees associated with filing an objection. To do so would result in an inflation of costs for other objectors to cover the costs incurred by government requests. This is different, however, from arrangements to assist impecunious governments. If the GAC is able to provide the principle on which they base their request for exemption, it will be considered for inclusion into the procedure. Resolution of competing string applications does not give rise to auction-derived surpluses, but is decided on the respective value of the applications for end users ==================================================================== The purpose of an auction is to resolve contention in a clear, objective manner as the avenue of last resort in resolving contending applications. Possible uses of funds from this source include formation of a foundation with a clear mission and a transparent way to allocate funds to projects that are of interest to the greater Internet community, such as grants to support new gTLD applications or registry operators from communities in subsequent gTLD rounds, the creation of an ICANN-administered/community-based fund for specific projects for the benefit of the Internet community, the creation of a registry continuity fund for the protection of registrants (ensuring that funds would be in place to support the operation of a gTLD registry until a successor could be found), or establishment of a security fund to expand use of secure protocols, conduct research, and support standards development organizations in accordance with ICANN’s security and stability mission. That is, funds will be used in a manner that supports directly ICANN’s Mission and Core Values and also maintains its not for profit status. Potential benefits of categories (or track differentiation) should be fully explored. ==================================================================================== ICANN is a strong proponent of innovative uses of new TLDs. This is especially so in cases where TLDs can be delegated to address the needs of specific communities such as intergovernmental organizations, socio-cultural groups and registered brands. Rather than having ICANN limit this type of innovation and identification with certain TLD models, more creativity might be spawned by allowing different groups to self-identify the type of TLD they purport to be and promote that model among their community. If a self-declaration program is instituted and contractual accommodations are eliminated or minimized, fees can remain constant. Socio-economic groups, brand owners and other groups all can be accommodated under the existing structure and self-identify as a particular type of TLD. Over time, the market and community interests will sort TLD types – a model preferable to having ICANN make that determination a priori. To reiterate, it is not for ICANN to develop these distinctions a priori. It may well be that as definitive categories of applicants emerge in practice, and as ICANN and the respective communities gain further experience of possible benefits of additional gTLD categorization over time, organizational structures might be developed with ICANN to reflect these categories. That will be a consequence of bottom-up policy developments by affected participants, according to the ICANN model. Nothing in the current implementation procedures forecloses those future developments. Significant consideration has been given to the issue of the introducing category-based TLDs in the new gTLD process. The policy recommendations of the GNSO and the GAC principles have resulted in the creation of three gTLD categories or types: Community-based TLDs Geographic Name TLDs Everything else (called standard or open TLDs) Community comment suggests the creation of several TLD categories: for example, single-owner, country, intergovernmental organization, socio-cultural, community and open. Depending on the category, various accommodations are suggested: for example, no requirements for an ICANN contract, or to use accredited registrars, or to follow consensus policy, or policy provisions outlined in the GAC’s ccTLD principles. Some might be restricted to not-for-profit status, be eligible for reduced fees, require registration restrictions, and have names reserved in anticipation of registration by certain parties. Beyond the accommodations sought, many or all of the suggested categories seem to be variations of community-based TLDs. The preference for community-based TLDs in the evaluation/contention process is based on policy advice from the GNSO and is intended to ensure that community-based applicants receive the TLD string to which their community is strongly related. Perhaps the most important aspect of the suggested categories is that an applicant within these categories does, in fact, receive the string associated with its community, and that is what the existing process is designed to do. The introduction of a number of new gTLD categories with a number of different accommodations will lead to a complex and difficult application, administration and evaluation process, in addition to a very complicated contractual compliance environment. Additionally, there will be considerable debate and discussion in the community as to whether certain accommodations should be made. Should certain gTLDs not be required to have an agreement with ICANN or not be required to follow consensus policy? Should certain TLDs be required to maintain not-for-profit status? These discussions and debates will take considerable time and resources and may ultimately not result in consensus. The structure of TLD categories, if granted different accommodations with differing contractual obligations, would result in significantly higher compliance costs and therefore, annual fees. I thank the GAC for their continued effort in considering the implementation of the new gTLD program. As the Board’s resolution (http://www.icann.org/en/minutes/resolutions-25jun10-en.htm#11 ) from the Brussels meeting sets out, there will be a Board Workshop focusing on new gTLDs on 24 and 25 September 2010. The Board will use this time to consider all of the outstanding issues relating to the implementation of the new gTLD program. We will likely follow the Board Workshop with a Special Board Meeting focusing on the new gTLD topics. I understand the GAC is preparing their comments on version 4 of the Draft Applicant Guidebook, and we very much look forward to the GAC’s input for use in that Board Workshop. Yours sincerely Peter Dengate-Thrush Chair, ICANN Board of Directors

1 0