October 2014 - council - lists.icann.org

RE: [council] Motion for the creation of CWG-IG
by Winterfeldt, Brian J. Oct. 15, 2014

Oct. 15, 2014

Dear Avri and all: I write to offer a potentially friendly amendment to the motion for the creation of the CWG-IG. By way of background, the current motion reads that "Each GNSO Stakeholder Group will identify one member to serve on the CWG-IG by 15-October-2014." The IPC feels that this is an oversimplification. Instead, in conformity with the CWG-IG Charter, and discussions among the Charter drafting team, we propose that the motion instead read as follows: Each GNSO Stakeholder Group, or (where a stakeholder group consists of separate constituencies) each constituency, notwithstanding the GNSO Co-Chair appointment, will identify one member to serve on the CWG-IG by 15-October-2014. We hope this revised language and level of clarity meets with your approval. Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 575 Madison Avenue / New York, NY 10022-2585 p / (212) 940.6762 f / (212) 894.5585 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> ________________________________________ From: owner-council(a)gnso.icann.orgOn<mailto:owner-council@gnso.icann.orgOn> Behalf OfAvri Doria Sent: Friday, October 3, 2014 11:40:08 AM (UTC-05:00) Eastern Time (US & Canada) To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] Motion for the creation of CWG-IG Hi, noticed at least two typos in the motion. avri On 03-Oct-14 11:32, Avri Doria wrote: > Hi, > > Please find a motion for approving the charter of the CWG-IG as was > discussed at our last meeting. > > Since James and I worked on this, I have added his name as seconder > but he needs to either accept or reject that. > > Note the last item in the motion: > >> 4. As the charter calls for each of the chartering organizations to >> appoint a co-chair for the group, the GNSO Council appoints <name >> here> to serve as a member of the CWG-IG, to serve as the GNSO >> co-chair of the CWG-IG, and to serve as GNSO Council liaison to the >> group. > > We need to decide which name goes here. Does no necessarily need to > be the same person for co-chair and liaison. Rafik Dammak is a > current co-facilitator for the group from the GNSO side. > > Thanks > > avri > -- > > Adoption of a Charter for a Cross Community Working Group to discuss > Internet governance (CWG-IG) issues affecting ICANN and make > recommendation to the chartering organization on these issues > > > Made by: Avri Doria > Seconded by: James Bladel (?) (?) can be removed > > Whereas, > > This group was initiated in December 2013 in response to a call > from ICANN CEO and has been working informally since then; > > The group has developed the charter found at > <https://community.icann.org/x/ryufAg> [attached]; > > This charter has already been approved by ALAC, ccNSO and SSAC. > > Resolved: > > The GNSO Council approves the Charter > <https://community.icann.org/x/ryufAg>. > > Each GNSO Stakeholder Group will identify one member to serve on the > CWG-IG by 15-October-2014 taking into account the charter requirement > that best efforts should be made to ensure that members: > > - Have sufficient expertise to participate in the applicable > subject matter; > > - Commit to actively participate in the activities of the CWG-IG > on an ongoing and long-term basis; and > > - Where appropriate, solicit and communicate the views and > concerns of individuals in the organization that appoints them. > > 3. The GNSO will collaborate with the other SOs and ACs to issue a > call for observers to join the CWG-IG, each in accordance with its own rules. > > 4. As the charter calls for each of the chartering organization to Should be: As the charter calls for each of the chartering organizations to > appoint a co-chair for the group, the GNSO Council appoints <name > here> to serve as a member of the CWG-IG, to serve as the GNSO > co-chair of the CSG-IG and to serve as GNSO Council liaison to the group. Should be CWG-IG and to serve as GNSO Council liaison to the group. > =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). ===========================================================

3 2

GNSO Council Public Administrative Meeting Los Angeles, 15 October 2014 (Part 2) at 15:15 (22:15 UTC)
by Glen de Saint Géry Oct. 15, 2014

Oct. 15, 2014

Dear Councillors, Please find the proposed agenda for the GNSO Council Public Administrative Meeting in Los Angeles, 15 October 2014 (Part 2) This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-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 Times 22:15 UTC http://tinyurl.com/plgz5gl Coordinated Universal Time 22:15 UTC 15:15 Los Angeles; 18:15 Washington; 23:15 London; 00:15 Paris; Main Meeting Page: http://la51.icann.org/en/schedule/wed-gnso-council-admin Dial-in numbers will be sent individually to Council members. Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Seating of the 2014 / 2015 Council (20 mins) 1.1 Roll Call 1.2 Statements of interest · Carlos Raul Guterriez - SOI<https://community.icann.org/display/gnsosoi/Carlos+Raul+Gutierrez+SOI> Nominating Committee Appointee · Donna Austin - SOI<https://community.icann.org/display/gnsosoi/Donna+Austin+SOI> Registries Stakeholder Group · Edward Morris - SOI<https://community.icann.org/display/gnsosoi/Edward+Morris+SOI> Non Commercial Stakeholder Group · Heather Forrest - SOI<https://community.icann.org/display/gnsosoi/Heather+Forrest+SOI> Intellectual Property Constituency · Marilia Ferreira Maciel - SOI<https://community.icann.org/pages/viewpage.action?pageId=49353624> Non Commercial Stakeholder Group · Stephanie Perrin - SOI<https://community.icann.org/display/gnsosoi/Stephanie+Perrin+SOI> Non Commercial Stakeholder Group · Susan Kawaguchi - SOI<https://community.icann.org/display/gnsosoi/Susan+Kawaguchi+SOI> Commercial and Business Users Constituency 1.3 Review/amend agenda Item 2: Election of the Chair (30 mins) One nomination was received for this position, Jonathan Robinson. The GNSO Council held a question & answer session over the weekend with Jonathan Robinson. The Council to proceed to elect the chair according to the GNSO Operating Procedures. GNSO Operating Procedures http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf Note: Section 2.2 Officer Elections: Chair and Vice-Chairs (see Appendix 1 below) Item 3: Any Other Business (10 mins) Reminder: The Council development meeting will take place at 12025 Waterfront Drive, 2nd Floor, Los Angeles, CA 90094-2536 on Friday 17 October 2014, 10h00. Appendix 1: Excerpt from GNSO Operating Procedures (Section2.2) http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf 2.2 Officer Elections: Chair and Vice-Chairs The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows: a. The GNSO Chair shall be elected by a 60 percent vote of each house. b. Each house will be allowed to nominate one candidate for GNSO Council Chair. Each house is responsible for determining how to nominate its candidate. A candidate for GNSO Council Chair does not need to be a member of a house, but must be a member of the GNSO Council. Should a Chair be elected from outside of the houses that Chair will be a non-voting Chair. i. All ballots will include the "none of the above" option. In the event that a 60 percent vote of each house selects the "none of the above" option, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be scheduled for no sooner than 30 days after the unsuccessful vote. ii. In the case of a tie for the most votes between the two candidates, or between a candidate and "none of above," a second election will be held no sooner than 30 days. The candidates shall remain the same for this second election. In the case this second election also results in a tie, each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful vote. iii. The leading candidate will be defined as the one with the highest score. The score is calculated by adding together the voting percentages attained from each house. The highest percentage attainable in each house is 100. Thus, the maximum score a candidate can achieve is 200 as a result of attaining 100 percent of the votes from the contracted party house and 100 percent from the non-contracted party house (100 percent + 100 percent = score of 200). In case neither candidate reaches the 60 percent of each house threshold, a second ballot will be held between the leading candidate and "none of the above." iv. In case neither candidate reaches the 60 percent of each house threshold and the candidates do not tie, a second runoff ballot will be held between the leading candidate and "none of the above." v. If the single candidate does not reach the 60 percent of each house threshold in the runoff ballot, then each house will commence a new nomination period of not longer than 15 days. An election for the new nominees will be rescheduled for no sooner than 30 days after the unsuccessful runoff ballot. c. Each house shall select a Council Vice-Chair from within its respective house. d. A Chair may not be a member of the same Stakeholder Group of either of the Vice-Chairs. e. The Chair and Vice-Chairs shall retain their votes (if any) in their respective houses (if any). f. In the event that the GNSO Council has not elected a GNSO Council Chair by the end of the previous Chair's term, the Vice-Chairs will serve as Interim GNSO Co-Chairs until a successful election can be held. g. The Council shall inform the Board and the Community appropriately and post the election results on the GNSO website within 2 business days following each election and runoff ballot, whether successful or unsuccessful. Appendix 2: 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: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. 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. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. 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. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 3: 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 and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 22:15 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 15:15 San José, Costa Rica UTC-6+0DST 16:15 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 17:15 New York/Washington DC, USA (EST) UTC-4+1DST 18:15 Rio de Janiero, Brazil (BRST) UTC-2+1DST 19:15 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 20:15 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 19:15 London, United Kingdom (BST) UTC+0DST 23:15 Bonn, Germany (CET) UTC+1+0DST 00:15 (next day) Cairo, Egypt, (EET) UTC+2+0DST 00:15 (next day) Istanbul, Turkey (EEST) UTC+2+0DST 01:15 (next day) Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 01:15 (next day) Beijing/Hong Kong, China (HKT ) UTC+8+0DST 06:15 (next day) Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 06:15 (next day) Melbourne, Australia (AEDT) UTC+11+1DST 09:15 (next day) ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com ---------------------------------------------------------------------------- http://tinyurl.com/plgz5gl Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Resolutions fro new gTLD program committee - 12/14 Oct - Los Angeles
by Bruce Tonkin Oct. 15, 2014

Oct. 15, 2014

Hello All, Below are the resolutions from the new gTLD program committee meetings held on 12/14 Oct 2014. In summary: - the Board has directed the staff to organize a review by International Centre for Dispute Resolution (ICDR) with a three-member panel of the following two string confusion decisions: VeriSign Inc. (Objector) v. United TLD Holdco Ltd. (Applicant) .CAM Commercial Connect LLC (Objector) v. Amazon EU S.�� r.l. (Applicant) .ͨ؜ - provide temporary protections for the names of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies, and the 189 National Red Cross and Red Crescent Societies while the GAC, GNSO, Board, and ICANN community continue to actively work on resolving the differences in the advice from the GAC and the GNSO policy recommendations on the scope of protections for the RCRC names. Regards, Bruce Tonkin From: https://www.icann.org/resources/board-material/resolutions-new-gtld-2014-10… 1. Consent Agenda: a. Approval of Minutes Resolved (2014.10.12.NG01), the Board New gTLD Program Committee (NGPC) approves the minutes of its 8 September 2014 meeting. 2. Main Agenda: a. GAC Advice in Beijing Communiqu�� regarding Category 2 Safeguards �C Exclusive Registry Access No resolution taken. b. Perceived Inconsistent String Confusion Objection Expert Determinations Whereas, on 10 October 2013 the Board Governance Committee (BGC) requested that staff draft a report for the NGPC on String Confusion Objections (SCOs) "setting out options for dealing with the situation raised within this [Reconsideration] Request, namely the differing outcomes of the String Confusion Objection Dispute Resolution process in similar disputes involving Amazon's Applied �C for String and TLDH's Applied-for String." Whereas, the NGPC considered potential paths forward to address perceived inconsistent Expert Determinations from the New gTLD Program SCO process, including possibly implementing a new review mechanism. Whereas, on 5 February 2014, the ICANN Board New gTLD Program Committee (NGPC) directed the ICANN President and CEO, or his designee, to initiate a public comment period on framework principles of a potential review mechanism to address perceived inconsistent String Confusion Objection Expert Determinations (the "proposed review mechanism"). The proposed review mechanism, if adopted, would have been limited to the String Confusion Objection Expert Determinations for .CAR/.CARS and .CAM/.COM, and would have constituted a change to the Objection process set forth in the New gTLD Applicant Guidebook. Whereas, the NGPC has carefully considered the report that the BGC asked staff to draft in response to Reconsideration Request 13-9, the received public comments to the proposed review mechanism, other comments provided to the NGPC for consideration, as well as the processes set out in the Applicant Guidebook. Whereas, as set out in the Applicant Guidebook, ICANN has reserved the right to individually consider any application for a new gTLD to determine whether approval would be in the best interest of the Internet community. Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2014.10.12.NG02), the NGPC has identified the following String Confusion Objection Expert Determinations as not being in the best interest of the New gTLD Program and the Internet community: SCO Expert Determinations for Review VeriSign Inc. (Objector) v. United TLD Holdco Ltd. (Applicant) .CAM Commercial Connect LLC (Objector) v. Amazon EU S.�� r.l. (Applicant) .ͨ؜ Resolved (2014.10.12.NG03), the NGPC directs the President and CEO, or his designee(s), take all steps necessary to establish processes and procedures, in accordance with this resolution and related rationale, pursuant to which the International Centre for Dispute Resolution (ICDR) shall establish a three-member panel to re-evaluate the materials presented, and the Expert Determinations, in the two objection proceedings set out in the chart above under the "SCO Expert Determinations for Review" column and render a Final Expert Determination on these two proceedings. In doing so, the NGPC recommends that the three-member panel also review as background the "Related SCO Expert Determinations" referenced in the above chart. c. Reconsideration Request 14-37, I-Registry Ltd. Whereas, iRegistry Ltd. ("Requester") filed Reconsideration Request 14-37 asking the New gTLD Program Committee ("NGPC") to reverse Resolutions 2014.07.30.NG01 �C 2014.07.30.NG04 (the "Resolution") "or at least amend[]" the Resolution, and to then put the decision as to how to address name collisions "on hold" until the issues the Requester raises have "been solved." Whereas, the BGC considered the issues raised in Reconsideration Request 14-37. Whereas, the BGC recommended that the Request be denied because the Requester has not stated proper grounds for reconsideration and the NGPC agrees. Resolved (2014.10.12.NG04), the NGPC adopts the BGC Recommendation on Reconsideration Request 14-37, which can be found at https://www.icann.org/en/system/files/files/recommendation-i-registry-04sep… [PDF, 150 KB]. d. GAC Advice regarding Protections for the Red Cross and Red Crescent �C Singapore Communiqu�� Whereas, the GAC met during the ICANN 49 meeting in Singapore and issued a Communiqu�� [PDF., 449 KB] on 27 March 2014 ("Singapore Communiqu��"). Whereas, in the Singapore Communiqu�� the GAC clarified its previous advice to the ICANN Board to permanently protect from unauthorized use the terms associated with the International Red Cross and Red Crescent Movement, and advised that the protections should also include "the 189 National Red Cross and Red Crescent Societies, in English and the official languages of their respective states of origin," and the "full names of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies in the six (6) United Nations Languages." The GAC Advice is identified in the GAC Register of Advice as 2014-03-27-RCRC. Whereas, the GNSO has developed policy recommendations to the Board concerning the Red Cross and Red Crescent names that are the subject of the GAC's Singapore Communiqu��. The scope of protections in the GNSO policy recommendations differ from the GAC's advice, and the GAC, GNSO, Board, and ICANN community continue to actively work on resolving the differences. Whereas, the NGPC is responsible for considering the GAC advice pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2014.10.12.NG05), the President and CEO, or his designee(s), is directed to provide temporary protections for the names of the International Committee of the Red Cross and International Federation of the Red Cross and Red Crescent Societies, and the 189 National Red Cross and Red Crescent Societies, as identified in the GAC Register of Advice as 2014-03-27-RCRC while the GAC, GNSO, Board, and ICANN community continue to actively work on resolving the differences in the advice from the GAC and the GNSO policy recommendations on the scope of protections for the RCRC names. e. Any Other Business No resolution taken.

1 0

Summary of IPC Comments on "The Protection of Geographic Names in the New gTLDs Process"
by Winterfeldt, Brian J. Oct. 15, 2014

Oct. 15, 2014

Dear all: Please see attached for the consideration of your respective stakeholder groups and constituencies, the IPC comments on the GAC subgroup proposal regarding “protection of geographic names in the new gTLD process.” We will introduce these comments during the GAC briefing to the ICANN community on this topic scheduled to take place this morning. Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 575 Madison Avenue / New York, NY 10022-2585 p / (212) 940.6762 f / (212) 894.5585 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). ===========================================================

1 0

FW: Proxy for GNSO Council meeting Wednesday 15 October 20:00 UTC 13:00 PDT
by Glen de Saint Géry Oct. 15, 2014

Oct. 15, 2014

FYI From: Reed, Daniel A Sent: mardi 14 octobre 2014 16:54 To: Glen de Saint Géry Subject: RE: Proxy for GNSO Council meeting Wednesday 15 October 20:00 UTC 13:00 PDT Glen: My proxy goes to Thomas Best, Dan

1 0

2015 Nominating Committee Chair-Elect is Ron Andruff
by Bruce Tonkin Oct. 14, 2014

Oct. 14, 2014

From: https://www.icann.org/resources/board-material/resolutions-2014-10-11-en Appointment of 2015 Nominating Committee Chair-Elect Whereas, the Board Governance Committee (BGC) reviewed the Expressions of Interest from candidates for the 2015 Nominating Committee ("NomCom") Chair and Chair-Elect, considered the results of a 360-degree evaluation of the 2014 NomCom leadership, and evaluated responses to questions posed by the BGC to each candidate. Whereas, on 9 September 2014 the Board appointed Stéphane Van Gelder as the 2015 NomCom Chair, and deferred appointing a Chair-Elect pending interviews of some of the candidates. Whereas, the since 9 September 2014, BGC members have interviewed a short-list of candidates for the 2015 NomCom Chair-Elect position and has recommended that the Board appoint Ron Andruff as the Chair-Elect. Resolved (2014.10.11.01), the Board hereby appoints Ron Andruff as the 2015 Nominating Committee Chair-Elect.

1 0

GNSO Transcripts published
by Glen de Saint Géry Oct. 14, 2014

Oct. 14, 2014

Dear All, The transcripts from the GNSO Weekend Working Sessions as well as other GNSO Working Group meetings are posted on page http://gnso.icann.org/en/group-activities/calendar#oct as well as on the main meeting schedule http://la51.icann.org/en/schedule-full under the specific nodes, for example: http://la51.icann.org/en/schedule/sat-sci The recordings of the meetings can also be found under the specific meeting node. Please let us know if you have any questions. 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<http://gnso.icann.org/>

1 0

A small matter....
by James M. Bladel Oct. 14, 2014

Oct. 14, 2014

Hi Glen! I don't intend to sound petty, but I'm wondering if you could change my name placard to read "United States" rather than "North America." Hopefully this isn't too much trouble. Thank you! J.

5 4

Progress Report UNCT CWG
by Marika Konings Oct. 14, 2014

Oct. 14, 2014

Dear All, Please find attached the progress referred to by Heather Forrest in her update on the CWG on use of country and territory names as TLDs. Best regards, Marika

1 0

Update on WHOIS initiatives
by Bruce Tonkin Oct. 13, 2014

Oct. 13, 2014

>From the session, All Things WHOIS - Now and in the Future, I have attached the presentation. Regards, Bruce Tonkin

1 0