December 2011 - council - lists.icann.org

CEO Search Committee Progress
by Glen de Saint Géry 12 Dec '11

12 Dec '11

http://www.icann.org/en/announcements/announcement-12dec11-en.htm CEO Search Committee Progress 12 December 2011 The CEO Search Committee has met several times since Dakar, and has scheduled conference calls at least weekly through the Costa Rica meeting in March 2012. The committee received a number of e-mailed responses in reply to its request in Dakar for further input. We thank those who have provided input, either in person in Dakar or through e-mail submissions. The committee issued an RFP for a search firm to assist us in the process. Eight firms were solicited, and four acceptable responses were received. The proposal of Odgers Berndtson of Brussels was chosen, and the committee is now working actively with them. The committee, in cooperation with Odgers Berndtson, has developed a candidate profile to be used in our search efforts. The profile is a condensation of the Board's thinking and comments from the community and others, to help potential candidates understand the required skills and experience. The larger and richer set of characteristics of the new CEO, developed through community consultations, will be fully utilized in the evaluation of candidates. A job description is prepared separately. The CEO Candidate Profile may be found at http://www.icann.org/en/committees/ceo-search/ceo-candidate-profile-01dec11… [PDF, 576 KB]. Members of the community are encouraged to consult the profile and assist in encouraging excellent candidates to interest themselves in the position. The committee has decided that all inquiries and expressions of interest regarding the ICANN CEO position should be sent directly to Odgers Berndtson. The following e-mail address has been established for this purpose: ceo-icann(a)odgersberndtson.be<mailto:ceo-icann@odgersberndtson.be> This address is now operational and available for use. All expressions of interest the CEO search should be sent directly to this address. Finally, the committee is currently involved in finalizing the job description, discussing advertising strategy, and assessing a compensation package for the new CEO. The committee intends to keep the community informed of its progress on a periodic basis. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Fwd: [soac-discussion] Information on New gTLD Applicant Support Program
by Stéphane Van Gelder 12 Dec '11

12 Dec '11

Councillors, please see the below the note from Kurt. Please note that this is an advanced copy, released early, and that the formal publication of these documents will happen in the next few days. Stéphane Début du message réexpédié : > De : Kurt Pritz <kurt(a)icann.org> > Objet : [soac-discussion] Information on New gTLD Applicant Support Program > Date : 11 décembre 2011 19:15:06 HNEC > À : "soac-discussion(a)icann.org" <soac-discussion(a)icann.org>, Avri Doria <avri(a)acm.org>, Carlton Samuels <carlton.samuels(a)gmail.com>, Rafik Dammak <rafik.dammak(a)gmail.com>, Alan Greenberg <alan.greenberg(a)mcgill.ca> > Cc : Chris Disspain <ceo(a)auda.org.au>, Bertrand de La Chapelle <bdelachapelle(a)gmail.com>, George Sadowsky <george.sadowsky(a)gmail.com>, Mike Silber <silber.mike(a)gmail.com>, "sebastien(a)bachollet.com" <sebastien(a)bachollet.com>, Rod Beckstrom <rod.beckstrom(a)icann.org>, "cintra.sooknanan(a)gmail.com" <cintra.sooknanan(a)gmail.com>, David Olive <david.olive(a)icann.org>, Karla Valente <karla.valente(a)icann.org>, Karen Lentz <karen.lentz(a)icann.org>, John Jeffrey <john.jeffrey(a)icann.org>, Daniel Halloran <daniel.halloran(a)icann.org>, Karen Lentz <karen.lentz(a)icann.org>, Michael Salazar <michael.salazar(a)icann.org> > > Dear Community Leaders: > > > The purpose of this note is to introduce ICANN¹s new gTLD Applicant > Support Program intended to provide financial and other types of support > to deserving applicants. That program is embodied by four documents > attached for your review: an Overview, the Applicant Support Process, the > Applicant Support Criteria, and a rough process flowchart to facilitate > understanding. > > > These are furnished to you in advance of general publication and are for > your discussion. We wanted to get information to you as soon as possible > and will formally post this as soon as some necessary accompanying work is > completed in about a week. > > > I know that most of you have been following the work to develop an > Applicant Support Program for new gTLDs. Thus far, some non-financial > elements of an Applicant Support Program have been developed. Among them > are: the publication of a ³matching page² where entities seeking support > and those offering support can self-identify and find partners; and the > recent launch of the Customer Service Center. > > > The community (mostly through the Joint Applicant Support Working Group) > and the ICANN Board have been working to develop an Applicant Support > Program that includes financial assistance. Among other goals, the program > seeks to provide financial assistance to applicants identified as having > need and a mission to operate in the public interest. > > > The Board resolution in Dakar the Board noted that a working group of > Board members had been convened to oversee the scoping and implementation > of the recommendations arising out of the JAS Report, and resolved that > ICANN was ³expected to commence work immediately and provide a detailed > plan for consideration." That work was undertaken with the oversight of > the Board working group. The result is a program described in the two > documents that describe a Process and Criteria for evaluating candidates > for support and providing support where merited. The work follows the plan > outlined in the Board discussion in Dakar. > > A description of and the reasoning behind the program (both in overview > and in detail) can be found in the attached documents. > > Next steps, to be done in a timeline described in the documents: > 1) Before the end of the year, ICANN plans to post the proposed Process > and Criteria documents for a brief public comment period (to align the > timing of the Support Program with the new gTLD program launch). > 2) Support candidates will be able to submit applications as soon as the > New gTLDs Program launches, 12 January 2012. > 3)Evaluation Panels will be recruited. > 4) In partnership with the community additional funds will be sought. > > I hope you find this helpful. Please contact Karla Valente or me with > questions. > > > Sincerely, > > > Kurt > > > > > > > > >

1 0

Fwd: [gnso-chairs] draft informational memo attached regarding Board Resolution re: SAC051 Recommendations
by Stéphane Van Gelder 12 Dec '11

12 Dec '11

Councillors, Please see the message below from Liz and the note prepared by staff. As the note references the Council several times, we may wish to vote on whether to send it or not. However, as time is quite short, we may also decide onlist if we approve of this being sent. Which course of action has your preference? Stéphane Début du message réexpédié : > De : Liz Gasster <liz.gasster(a)icann.org> > Objet : [gnso-chairs] draft informational memo attached regarding Board Resolution re: SAC051 Recommendations > Date : 9 décembre 2011 23:36:28 HNEC > À : "gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> > > Hi all, > > Staff has prepared a draft informational memo to the Board for Council consideration/modification (please see attached). It describes the GNSO-related WHOIS protocol activities as we discussed in November. > > Before circulating this to the Council, I wanted to ask you first what you think is the best way to handle Council review of this draft. It is intended as straightforward and informational so do you believe we should seek a motion/vote to send such a note to the Board, or do you think the Council might agree on language to send by consensus ok? > > The current deadline for input to the Board from the SOs and ACs on this matter is 9 January 2012, but if you felt formal review and vote is appropriate, I think the input would still be considered following that deadline, because it was set with staff’s development of the Roadmap in mind, not by the Board per se (I’m thinking ahead to the January Council meeting). > > Please let me know what you think is the preferred approach. > > Best, Liz > > From: Stéphane Van Gelder [mailto:stephane.vangelder@indom.com] > Sent: Saturday, November 12, 2011 5:33 AM > To: Liz Gasster; GNSO Council > Subject: Re: [council] [soac-discussion] Board Resolution re: SAC051 Recommendations >

1 0

TR: GNSO Council Abstention Notification Form [#72]
by Glen de Saint Géry 09 Dec '11

09 Dec '11

FYI Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org De : ICANN [mailto:no-reply@wufoo.com] Envoyé : vendredi 9 décembre 2011 18:24 À : gnso.secretariat(a)icann.org Objet : GNSO Council Abstention Notification Form [#72] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Friday, December 9, 2011 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * NCSG Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * NCSG GNSO Councilor Mary Wong will be traveling during the 15 Dec. 2011 GNSO Council meeting. William Drake will serve as Mary Wong's proxy for this meeting. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * ? Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, December 16, 2011 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * William Drake

1 0

TR: GNSO Council Abstention Notification Form [#71]
by Glen de Saint Géry 09 Dec '11

09 Dec '11

FYI Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org De : ICANN [mailto:no-reply@wufoo.com] Envoyé : vendredi 9 décembre 2011 16:38 À : gnso.secretariat(a)icann.org Objet : GNSO Council Abstention Notification Form [#71] Name of Officer: * David Maher Officer Email Address: * dmaher(a)pir.org<mailto:dmaher@pir.org> Date Prepared: * Friday, December 9, 2011 GNSO Organization: * Registries Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Jonathan Robinson, GNSO Councillor, is unable to attend the 15 December Council meeting and has requested appointment of a proxy. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All subjects, measures, motions and actions Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, December 16, 2011 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Jeff Neuman

1 0

Fwd: [gnso-chairs] Observers on the Council call
by Stéphane Van Gelder 09 Dec '11

09 Dec '11

Councillors, Please see the message below from Glen. I personally have no problem with this as it seems very positive and will no doubt help our meetings run more smoothly in the future. If anyone does, please notify me or the VCs asap. Unless any objections are heard, I will ask Glen to give the Adigo folks the all-clear to observe our next meeting. Thanks, Stéphane Début du message réexpédié : > De : Glen de Saint Géry <Glen(a)icann.org> > Objet : [gnso-chairs] Observers on the Council call > Date : 8 décembre 2011 20:12:24 HNEC > À : Stéphane Van Gelder <stephane.vangelder(a)indom.com>, "Neuman, Jeff" <Jeff.Neuman(a)neustar.us>, "KnobenW(a)telekom.de" <KnobenW(a)telekom.de> > Cc : Gnso Chairs <gnso-chairs(a)icann.org> > > Dear Stéphane, Jeff and Wolf-Ulrich, > > ICANN is thinking of changing teleconference providers. Recently while we were in Marina del Rey we met with the staff of Adigo with whom we already schedule a number of calls and they asked if they could be observers on the upcoming Council call to find out how we run our calls. I hope that you will not mind them observing on both the call itself and the Adobe Connect room at our next Council meeting on Thursday 15 December at 20:00UTC. > Please let us know if this causes any issues for you. > > Thank you very much. > Kind regards, > Glen > > > > Glen de Saint Géry > GNSO Secretariat > gnso.secretariat(a)gnso.icann.org > http://gnso.icann.org

1 0

US Senate Hearing on new gTLDs
by Bruce Tonkin 08 Dec '11

08 Dec '11

Hello All, The US Senate Committee on Commerce, Science, & Transportation held a hearing on ICANN's Expansion of Top Level Domains. This is now archived under hearings at: http://commerce.senate.gov I have attached a copy of the testimony given by Kurt Pritz for information. Regards, Bruce Tonkin

1 0

REMINDER: Yearly Update of Statements of Interest
by Glen de Saint Géry 08 Dec '11

08 Dec '11

Dear Council Members, Pursuant to the GNSO Operating Procedures you are invited to update your statement of interest. http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf 5.3 Statement of Interest Procedures 5.3.1 Timeliness Relevant Parties are required to provide to the GNSO Secretariat a Statement of Interest, updated not less frequently than once a year or whenever there is a material change, setting forth those specified interests, relationships, arrangements, and affiliations that may affect the judgments of Relevant Parties in the conduct of their participation within the GNSO. A completed Statement of Interest, updated at least annually, is a precondition for Relevant Parties to participate in a GNSO Group. At the beginning of each meeting the Chair of the GNSO Group shall ask all Relevant Parties whether they have updates to their Statements of Interest. The SOI Wiki site is located at: https://community.icann.org/display/gnsosoi/GNSO+Statements+of+Interest+%28…. You will need to use your Confluence Login ID and Password to access this space within the Wiki site. If you are a new Confluence user these will be provided to you. If you have already been given a Confluence Login ID and Password but cannot locate them please let us know. If you have not already done so, please update your statements of interest by the next Council meeting on 17 November 2011. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Draft Agenda for GNSO Council Meeting - 15 December 2011 at 20:00UTC
by Glen de Saint Géry 08 Dec '11

08 Dec '11

Agenda for GNSO Council Meeting - 15 December 2011 http://gnso.icann.org/meetings/agenda-council-15dec11-en.htm Wiki Agenda https://community.icann.org/display/gnsocouncilmeetings/Agenda+15+December+… This agenda was established according to the GNSO Council Operating Procedures approved 22 September 2011 for the GNSO Council. http://gnso.icann.org/council/gnso-operating-procedures-22sep11-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<http://www.timeanddate.com/worldclock/fixedtime.html?msg=GNSO+Council+Meeti…> Coordinated Universal Time: 20:00 UTC 12:00 Los Angeles; 15:00 Washington DC; 20:00 London; 21:00 Paris; 16 December 2011 05:00 Tokyo; 09:00 Wellington 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:8000/gnso.m3u Item 1: Administrative matters (10 minutes) Roll Call 1.2 Statement of interest updates · Mason Cole https://community.icann.org/display/gnsosoi/Mason+Cole+SOI 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: · 17 November minutes – will be approved on 8 December 2011. . Item 2: GNSO Pending Projects List (5 minutes) Standard agenda item looking at changes made to the GNSO's Pending Projects list since the previous meeting. Refer to Pending Projects list http://gnso.icann.org/meetings/pending-projects-list.pdf 2.1 Changes to Pending Projects List since last Council meeting (Stéphane Van Gelder) • GNSO activities: 9 (9 - No change). • Other activities: 10 (11 - Deleted: RAP, request to ICANN Compliance complete) • Joint SO/AC WGs: 7 (7 - no change). • Outstanding recommendations: 2 (2 - no change). Item 3: Outreach Task Force Charter (20 minutes) As part of the GNSO improvements, the Operations Steering Committee (OSC)'s Constituency and Stakeholder Group Operations Work Team worked on a set of recommendations on a global outreach program At the previous Council meeting, a motion on this was not approved. It was proposed that a small group be assisted by Staff to produce a new motion that would include specific revisions to the charter. Refer to motion: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… Reading of the motion (Zahid Jamil) 3.1 Discussion 3.2 Vote 3.3 Next steps Item 4: UDRP (25 minutes) Following the drafting of an Issue Report on a possible review of the UDRP, a motion is before the Council to initiate a PDP on this topic and that a drafting team be formed to write a charter for the working group. Refer to motion https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… The motion was deferred from the Nov 17 Council meeting. 4.1 Reading of the motion (Jeff Neuman) 4.2 Discussion 4.3 Vote Item 5: Joint ccNSO/GNSO IDN Working Group (JIG) (15 minutes) The JIG is proposing that both GNSO and ccNSO councils ask their Chairs to send to the ICANN Board a letter in response to their August 2011 resolution on Single Character IDN TLDs. The letter would note discrepancies between the WG's work and the Board resolution. Refer to motion https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… 5.1 Reading of the motion (Ching Chiao) 5.2 Discussion 5.3 Vote Item 6: Cross-TLD registration scam and domain kiting (10 minutes) At the previous Council meeting, there was discussion on possible next steps and decisions that could be made on this topic, following SSAC's response (http://gnso.icann.org/correspondence/gnso-council-chair-to-faltstrom-10oct1…) . Staff has suggested several options: * Adding these issues to the mandate of the Fake Renewal Notices Drafting Team which is tasked to prepare a request for information for the Registrar Stakeholder Group to obtain further information on the issue of Fake Renewal Notices in order to help inform the GNSO Council on the appropriate next steps, if any. As there are certain similarities, especially between the cross-tld registration scam and fake renewal notices, it might be possible for this DT to also try and obtain further information on that specific issue to help inform the Council's deliberations. * Continue discussions on the topic of cross-TLD registration scam with the ccNSO to discuss whether there are any steps that could be taken or considered jointly. The GNSO Council and the ccNSO Council had some initial discussions on this topic at its meeting in Dakar and as this is an issue that also affects ccTLDs there might be common approaches to be explored. As noted, such approaches might involve improved communication / education in relation to this issue as it is not clear at this stage that this issue could be addressed through policy development. * Do nothing – as there is no set mechanism for data gathering or monitoring of abuses at the moment or any evidence that these practices are in non-compliance with ICANN policies or agreements, the GNSO Council could decide to not undertake any further action at this stage. Note, at any point in time, should further information or data become available, any Council member or SO/AC could raise this issue again for further consideration. This discussion item aims at seeing if this issue should be closed or if work should continue. 6.1 Discussion 6.2 Next steps Item 7: Joint SO/AC WG on New gTLD Applicant Support Working Group (JAS WG) (10 minutes) This agenda item is to update the Council on recent developments in the JAS WG, and more specifically details of the measures being taken to implement the recommendations made in the JAS Final Report that was sent to the Board. 7.1 Update from Staff (X Y) 7.2 Discussion Item 8: Transitioning existing PDP work to the new PDP procedures (10 minutes) At its meeting on December 8, 2011, the Board adopted the new GNSO PDP. Out of that comes the following text: 'For all ongoing PDPs initiated prior to the adoption by the Board, the Council shall determine the feasibility of transitioning to the procedures set forth in this Annex A for all remaining steps within the PDP. If the Council determines that any ongoing PDP cannot be feasibly transitioned to these updated procedures, the PDP shall be concluded according to the procedures set forth in Annex A in force on before the adoption of the new Annex A by the Board'. Currently the following PDPs are under way: - IRTP Part C (Working Group) - Thick Whois (Preliminary Issue Report out for public comment) - RAA (Preliminary Issue Report in preparation) - Uniformity of Contracts (Preliminary Issue Report in preparation) - UDRP (pending) - Law Enforcement recommendations (pending) 8.1 Update from Staff (Margie Milam) 8.2 Discussion 8.3 Next steps Item 9: Any 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 (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting‟s adjournment. 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 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Local time between October & March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 20:00 ---------------------------------------------------------------------------- California, USA (PST<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+0DST 12:00 New York/Washington DC, USA (EST) UTC-5+0DST 15:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 17:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 18:00 London, United Kingdom (BST) UTC+0DST 20:00 Abuja,Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 21:00 Tunis, Tunisia (CET) UTC+1+0DST 21:00 Bonn, Germany (CET) UTC+1+0DST 21:00 Paris, France (CET) UTC+1+0DST 21:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 22:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 01:00 next day Beijing, China (CST<http://www.timeanddate.com/library/abbreviations/timezones/asia/cst.html> ) UTC+8+0DST 04:00 next day Tokyo, Japan (JST<http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 05:00 next day Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 09:00 next day ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of March 2012, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Motion for JIG Response to Aug 2011 Board Resolution on Single Character IDN TLDs
by Ching Chiao 08 Dec '11

08 Dec '11

Hi everyone, Please find the motion below (as well as the attached doc) from the JIG for consideration by the council in response to the Board Resolution regarding Single Character IDN TLDs in August. Thank you very much! Ching ===== WHEREAS, the JIG (Joint ccNSO/GNSO IDN Working Group) was formed by mutual charters between the ccNSO and GNSO councils, and extended (ccNSO: http://ccnso.icann.org/workinggroups/minutes-council-23aug11-en.pdf | GNSO: http://gnso.icann.org/resolutions/#201107) to complete its work on the 3 identified issues of common interest between the ccNSO and GNSO; WHEREAS, the subject of Single Character IDN TLDs was discussed at the GNSO IDN WG, the GNSO Reserved Names WG and incorporated into the GNSO New gTLD Recommendations, and consistently resulted in community consensus to allow the implementation of Single Character IDN TLDs; WHEREAS, the JIG developed and published an Initial Report on Single Character IDN TLDs ( http://ccnso.icann.org/workinggroups/jig-initial-report-26jul10-en.pdf) for public comments ( http://www.icann.org/en/announcements/announcement-2-27jul10-en.htm) and incorporated the comments ( http://forum.icann.org/lists/jig-initial-report/pdfaul7JXcqaa.pdf) into a draft Final Report ( http://www.icann.org/en/announcements/announcement-04dec10-en.htm) for further public comments, WHEREAS, the JIG conducted a public session during the Cartagena ICANN meetings (http://cartagena39.icann.org/node/15395); WHEREAS, the JIG incorporated comments received ( http://forum.icann.org/lists/jig-draft-final-report/pdfQxF383O30Q.pdf) and completed a Final Report ( http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns…) which was approved by the ccNSO ( http://ccnso.icann.org/workinggroups/minutes-council-10may11-en.pdf) and GNSO (http://gnso.icann.org/resolutions/#201107) councils; WHEREAS, the ICANN Board made a resolution at their August 25, 2011 meeting regarding the subject: http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5; and, WHEREAS, the JIG considered the resolution and found it to be in contradiction with the community consensus on the matter, NOW THEREFORE RESOLVED that, upon the mutual resolution from both the GNSO and ccNSO councils on the subject, the Council Chairs would send to the ICANN Board the following letter in response to their August 2011 resolution on Single Character IDN TLDs: --------- JIG (Joint ccNSO/GNSO IDN Working Group) Response to ICANN Board Resolution on Single Character IDN TLDs Dear ICANN Board, First of all, we appreciate activity at the ICANN Board regarding Single Character IDN TLDs. In response to the August 2011 resolution ( http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5) however, we express our disappointment and concern on 3 critical aspects: 1. Both the ccNSO and the GNSO councils have at multiple occasions expressed a consensus principle that the introduction of IDN gTLDs or IDN ccTLDs should not be delayed because of lack of readiness of one category. The August 2011 Board resolution (by specifying that “processes for delegation of single-character IDN TLDs will be made available after the first gTLD application round and conclusion of IDN ccTLD policy work.”) perhaps inadvertently conflicted with this community consensus understanding and should be rectified or clarified. 2. The issue of Single Character IDN TLDs have gone through at least 4 rounds of community discussions, including at the GNSO IDN WG ( http://gnso.icann.org/drafts/idn-wg-fr-22mar07.htm), the GNSO Reserved Names WG ( http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.htm), incorporated into the GNSO New gTLD recommendations ( http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm), and of course the JIG report ( http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns… ). Each time there is consistent consensus support from the community for allowing Single Character IDN TLDs in the new gTLD process (including the first round), and no objections were received from any of the ACs. The August 2011 Board resolution specifying that Single Character IDN TLDs not be included in the first round ignores this repeated community consensus without reasonable rationale. 3. While the August 2011 Board resolution generally requested input from a collection of ACs, there is a lack of progressive direction towards the implementation of Single Character IDN TLDs. Furthermore, while input from ACs is always welcome, given the multitude of public comment periods already conducted for the subject, including participation from SSAC members, with consistent consensus response, such consultation with ACs should not become an arbitrary hurdle for the implementation of Single Character IDN TLDs, especially for the New gTLD process. Single Character IDN TLDs is not simply a “good to have” feature, but a necessary requirement for some of the IDN communities in order to allow broadly attractive and competitive gTLDs. As an example, for Chinese IDN TLDs, the prohibition of Single Character IDN TLDs would effectively devoid the community of single-syllable-single-word TLDs, which is otherwise acceptable for English and other alphabetic based language TLDs (e.g. “.word” would be an acceptable ASCII single-syllable-single-word TLD, yet a similar single-syllable-single-word TLD “.字” would not be acceptable for Chinese), creating an unjustified situation of inequity, and significantly hindering the adoption of IDN. The JIG, through the ccNSO and GNSO councils therefore sincerely urges the Board to: a. Implement the community consensus of allowing Single Character IDN TLDs without restricting such implementation to being after the first round of the new gTLD process, and to decouple the requirement that IDN ccTLD or IDN gTLD mechanisms wait for the other; b. If necessary, form an implementation team to assist staff in immediately implementing Single Character IDN TLDs for scripts and languages where the input of a Single Character requires multiple keystrokes (e.g. ideographical scripts, and avoiding the potential technical concern of keyboard layouts identified in the JIG report), and for the team to further guide implementation for other scripts as well as coordinate input from the ACs; and, c. Update or amend the New gTLD Applicant Guidebook for such implementation before the application period for the first round is over. The JIG and the significantly affected language communities are prepared to support ICANN staff and Board in the swift implementation of Single Character IDN TLDs without compromising the security and stability of the Internet. The JIG further believes that minor adjustments to the Applicant Guidebook would suffice and is ready to work with staff closely to complete its implementation. We look forward to the positive response and actions from the Board. Sincerely, ccNSO Council (approval: [LINK]) GNSO Council (approval: [LINK]) JIG -- Joint ccNSO/GNSO IDN Working Group --------- ===== -- Ching CHIAO Vice President, DotAsia Organisation LTD. Chair, Asia Pacific Networking Group Member of ICANN GNSO Council & RySG ===================================== Email: chiao(a)registry.asia Skype: chiao_rw Mobile: +886-918211372 | +86-13520187032 www.registry.asia | www.apngcamp.asia www.facebook.com/ching.chiao

3 3