December 2011 - council - lists.icann.org

Updated GNSO Council agenda 15 December at 20:00UTC
by Glen de Saint Géry Dec. 15, 2011

Dec. 15, 2011

Dear Councillors, The latest update to the GNSO Council agenda is the addition under Item 10: Any Other business 10.3 Update on International Olympic Committee (IOC) & Red Cross (RC) names (Jeff Neuman) Thank you. Kind regards, Glen 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+… Motions: https://community.icann.org/display/gnsocouncilmeetings/Motions+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 –approved on 8 December 2011 http://gnso.icann.org/meetings/minutes-council-17nov11-en.htm. . 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 (10 – No Change) • 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 1: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… Reading of the motion (John Berard) 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 2. 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 3. 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: Update on Congressional Hearings (10 minutes) There have been two recent hearings in the U.S. CONGRESS on new gTLDS on 8 and 14 December 2011, namely the U.S. Senate Committee on Commerce, Science, and Transportation full committee hearing on ICANN’s expansion of top level domains, examining the merits and implications of this new program and ICANN’s continuing efforts to address concerns raised by the Internet community, and the HOUSE Subcommittee on Communications and Technology hearing on “ICANN’s Top-Level Domain Name Program.” 6.1 Update from Kurt Pritz 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 (Kurt Pritz) 7.2 Discussion Item 8: 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. 8.1 Discussion 8.2 Next steps Item 9: 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) 9.1 Update from Staff (Margie Milam) 9.2 Discussion 9.3 Next steps Item 10: Any Other Business (5 minutes) 10.1 Draft response to the Board regarding the GNSO input on Implementation of SAC 051 (SSAC Report on Whois Terminology and Structure) http://gnso.icann.org/drafts/draft-board-update-for-gnso-council-09dec11-en… 10.2 Update on Registrar Accreditation Agreements (RAA) (Margie Milam) 10.3 Update on International Olympic Committee (IOC) & Red Cross (RC) names (Jeff Neuman) 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

FW: GNSO Council Abstention Notification Form [#73]
by Glen de Saint Géry Dec. 14, 2011

Dec. 14, 2011

From: ICANN [mailto:no-reply@wufoo.com] Sent: mercredi 14 décembre 2011 21:18 To: gnso.secretariat(a)icann.org Subject: GNSO Council Abstention Notification Form [#73] Name of Officer: * Steve DelBianco Officer Email Address: * sdelbianco(a)netchoice.org<mailto:sdelbianco@netchoice.org> Date Prepared: * Wednesday, December 14, 2011 GNSO Organization: * Business Constituency Officer Position or Title: * Vice chair for policy coordination Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Councilor Zahid Jamil will be on an airline flight during the Council meeting Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * Voting on 3 pending motions( JIG, URDP PDP, and Outreach Task Force), plus any other business that comes before Council on 15-Dec-2011 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: * John Berard

1 0

FW: Outreach document background
by Neuman, Jeff Dec. 14, 2011

Dec. 14, 2011

All, Olga sent the following e-mail to Stephane, myself and Wolf and with her permission I am posting this to the full Council list. Jeffrey J. Neuman Neustar, Inc. / Vice President, Law & Policy ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message. From: Olga Cavalli [mailto:olgacavalli@gmail.com] Sent: Monday, December 12, 2011 2:59 PM To: Stéphane Van Gelder Cc: Neuman, Jeff; KnobenW(a)telekom.de> <KnobenW(a)telekom.de Subject: Outreach document background Dear Stéphane, I hope you are doing well. I am contacting you in relation with the Outreach document and other documents related. I understand that council didn't approve my motion related with the charter on the last call, also there was a request for deferring it during the open council meeting in Dakar. In my modest oppinion this is surprising and disappointing because this outreach document is part of the GNSO restructuring process, that was open to everyone and where all constituencies and stakeholder groups participated. For your reference I have included as follows all the background information of the OSC CSG working team I chaired for more than two years. Task 2 of this working team was the mandate to develop an outreach strategy: The ICANN Board Governance Committee (BGC) created a working group (the BGC WG) to consider the results of the reviews and recommend a comprehensive proposal to improve the effectiveness of the Generic Names Supporting Organization (GNSO), including its policy activities, structure, operations and communications. This BGC WG produced a comprehensive set of recommendations: the "Report of the Board Governance Committee GNSO Review Working Group on GNSO Improvements" (hereinafter the BGC Report) that were approved by the full Board in July 2008.1 As a follow up to Board approval of many BGC Report recommendations, the GNSO Council formed two steering committees, the Operations Steering Committee (OSC) and the Policy Process Steering Committee (PPSC). The OSC formed three work teams, one of which is the OSC Constituency Operations Work Team, subsequently called the OSC Constituency and Stakeholder Group Operations Work Team (OSC CSG Work Team). The OSC CSG Work Team, chaired by Olga Cavalli with active participation from all constituencies and stakeholder groups, created a Work Plan and broke it down into specific tasks. Task 2 directed the work team to develop recommendations for a global outreach program to broaden participation in GNSO constituencies. This is where the Outreach document came from, as a mandate for the working team. See the produced report here: http://gnso.icann.org/drafts/global-outreach-recommendations-21jan11-en.pdf Draft versions of this document went for public comments and also for consideration of the constituencies and stakeholder groups in different stages of the process. Other references: BGC Report : See: <http://www.icann.org/topics/gnso-improvements/gnso-improvements-report-03fe…> OSC CSG Work Team wiki workspace: <https://community.icann.org/display/gnsoosc/Constituency+Operations+Team> OSC CSG Task 2: Task 2: Develop a global outreach program to broaden participation in current constituencies. --Reach all current members of the ICANN community and potential members, particularly non-English speakers --Develop global outreach programs aimed at increasing participation Members of the OSC CSG Working team: Work Team Members: * Olga Cavalli - Nominating Committee Appointee * Rafik Dammak - Non-Commercial Users Constituency * Claudio DiGangi - Intellectual Property Interests Constituency * Chuck Gomes - gTLD Registries Constituency * Tony Harris - Internet Service and Connectivity Providers Constituency * Zahid Jamil - Commercial and Business Users Constituency * S.S. Kshatriya - Individual (India) * Victoria McEvedy - Intellectual Property Interests Constituency * Hector Ariel Manoff - Intellectual Property Interests Constituency * Krista Papac - Registrar Constituency * Dr. Shahram Soboutipour - Individual (Iran) * Michael Young - gTLD Registries Constituency As you can see in the members and conformation of the working group, constituencies and stakeholder groups were part of the team. And after all we went through these procedural steps during two years of work, which had the support and participation of all SGs, now some stakeholder groups want to change the motion. This undermines the value of the work that during two years the OSC CSG working team did and also undermines the value and purpose of all the GNSO restructuring process. In my modest oppinion GNSO as council should respect the work done under the GNSO restructuring process, specially considering that all steps were supervised by the OSC, in the case of our CSG working team, and by the council as a whole. Please if you need any other clarification on this regard feel free to let me know. Many thanks and best regards. Olga

4 4

Updated Draft Agenda for GNSO Council Meeting - 15 December 2011 at 20:00UTC
by Glen de Saint Géry Dec. 14, 2011

Dec. 14, 2011

Dear Councillors, Please find the latest updated draft agenda for the GNSO Council meeting on 15 December 2011 at 20:00UTC. The main changes are the following additions: Item 6: Update from Congressional Hearings – Kurt Pritz Item 10: Any Other Business: 10.1 Draft response to the Board regarding the GNSO input on Implementation of SAC 051 (SSAC Report on Whois Terminology and Structure) http://gnso.icann.org/drafts/draft-board-update-for-gnso-council-09dec11-en… 10.2 Update on Registrar Accreditation Agreements (RAA) (Margie Milam) Please let me know if you have any questions. Thank you. Kind regards, Glen 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 –approved on 8 December 2011. http://gnso.icann.org/meetings/minutes-council-17nov11-en.htm. . 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 (10 – No Change) • 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 1: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+December… Reading of the motion (John Berard) 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 2. 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 3. 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: Update on Congressional Hearings (10 minutes) There have been two recent hearings in the U.S. CONGRESS on new gTLDS on 8 and 14 December 2011, namely the U.S. Senate Committee on Commerce, Science, and Transportation full committee hearing on ICANN’s expansion of top level domains, examining the merits and implications of this new program and ICANN’s continuing efforts to address concerns raised by the Internet community, and the HOUSE Subcommittee on Communications and Technology hearing on “ICANN’s Top-Level Domain Name Program.” 6.1 Update from Kurt Pritz 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 (Kurt Pritz) 7.2 Discussion Item 8: 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. 8.1 Discussion 8.2 Next steps Item 9: 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) 9.1 Update from Staff (Margie Milam) 9.2 Discussion 9.3 Next steps Item 10: Any Other Business (5 minutes) 10.1 Draft response to the Board regarding the GNSO input on Implementation of SAC 051 (SSAC Report on Whois Terminology and Structure) http://gnso.icann.org/drafts/draft-board-update-for-gnso-council-09dec11-en… 10.2 Update on Registrar Accreditation Agreements (RAA) (Margie Milam) 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

Agenda item 8 - Transitioning existing PDP work to the new PDP procedures
by Marika Konings Dec. 14, 2011

Dec. 14, 2011

Dear All, In preparation for agenda item 8 (Transitioning existing Policy Development Process (PDP) work to the new PDP procedures) on the GNSO Council agenda for tomorrow, please find attached an overview which compares the old GNSO PDP with the new GNSO PDP, which was adopted by the ICANN Board at its meeting on 8 December. In addition, the status of each of the ongoing PDPs has been highlighted throughout the document, so that it should become easier for the GNSO Council to assess what the next step would be for each of the PDPs should they continue on the old or the new track. There might not be an opportunity to go into great detail with regards to the differences and new elements of the new PDP at tomorrow's call, but should there be an interest from Council members and/or Stakeholder Groups / Constituencies, Staff would be more than happy to organize a dedicated session on this topic. If you have any questions, please let me know. With best regards, Marika

1 0

UDRP Motion and Thoughts on the Friendly Amendment from the RySG
by Neuman, Jeff Dec. 13, 2011

Dec. 13, 2011

All, As you are aware the following motion is currently on the table: Original Motion Whereas the Registration Abuse Policies Working Group submitted a final report the GNSO Council on 29 May 2010 (see http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf) recommending an issue report on the current state of the UDRP considering both (a) How the UDRP has addressed the problem of cybersquatting to date, and any insufficiencies/inequalities associated with the process, and (b) Whether the definition of cybersquatting inherent within the existing UDRP language needs to be reviewed or updated, and Whereas, on February 3, 2011, the GNSO Council requested an Issues Report in accordance with the recommendations of the Registration Abuse Policies Working Group (http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf) and Whereas, a Preliminary Issue Report was published on 27 May 2011 (http://gnso.icann.org/issues/prelim-report-current-state-udrp-27may11-en.pdf) and series of webinars and workshops were held soliciting public comment to allow for the ICANN community to provide feedback on the analysis and recommendations contained therein, and Whereas, a Final Issue Report was published on 3 October 2011 (http://gnso.icann.org/issues/udrp/udrp-final-issue-report-03oct11-en.pdf) in which ICANN staff recommended the GNSO Council consider the "perspective of the majority of the ICANN community, and the advice of the Government Advisory Committee (GAC), and the At-Large Advisory Committee" and that "a PDP be delayed until after the New gTLD Uniform Rapid Suspension System (URS) has been in operation for at least eighteen months. . . [to] allow the policy process to be informed by data regarding the effectiveness of the URS, which was modeled on the UDRP, to address the problem of cybersquatting." RESOLVED, that the GNSO approved the initiation of a PDP and the establishment of a Working Group on recommendation #7 of the IRTP Part B Working Group concerning the requirement to lock a domain name subject to UDRP proceedings, which the GNSO Council at its meeting on 22 June 2011 received and agreed to consider when it takes up consideration of the Final Issue Report on the Current State of the UDRP. RESOLVED further, the GNSO Council requests a new a new Issue Report on the current state of all rights protection mechanisms implemented for both existing and new gTLDs, including but not limited to, the UDRP and URS, should be delivered to the GNSO Council by no later than eighteen (18) months following the delegation and launch of the first new gTLD. Proposed Friendly Amendment David Taylor, on behalf of the IPC has proposed a friendly amendment that would substitute the following for the last paragraph: RESOLVED further, the GNSO Council requests a new Issue Report on the current state of all rights protection mechanisms implemented for both existing and new gTLDs, including but not limited to, the UDRP and URS, should be prepared with staff commencing the drafting of this report eighteen (18) months after the publication of at least a 100 UDRP or URS that cover at least 10 new gTLDs. Such report should be delivered to the GNSO Council within four (4) months of that trigger date. RySG position on proposed Amendment As currently drafted, the RySG would not accept the amendment as friendly. The RySG believe that it has already compromised in agreeing to delay the PDP for 18 months after the launch of the first of the new gTLDs and increasing the scope to cover all trademark rights protection mechanisms. This was precisely what the GAC, ALAC, IPC & BC asked for during the public comment period on the Preliminary Issue report. This already delays the full pdp for 3.5 years from today. This is because we believe the first new gTLD will not launch until Q1 2013. 18 months from then is Q3 2014. That is when a Preliminary Issue Report will be put out for comment. By the time you get a Final Issue Report (after a public comment period, staff analysis, etc.), and a vote to approve a PDP by the Council (including possibly 1 deferral), we are talking about late Q1 or Q2 of 2015. The proposed amendment would delay the full PDP by at least another year (4.5 years from now). The rationale is that the first gTLD will not launch until Q1 2013 at the earliest. We estimate that it will take 6 months to get at a minimum to get 100 decisions in both the UDRP and URS. That brings us to Q3 2013. 18 months from the publication of 100 decisions in each is Q1 2015 at the earliest. 4 months from then is Q3 2015 and that is only for the preliminary issue report. A 30-45 day public comment period, plus analysis, debates, etc. makes the delivery of the final issue report at Q1 2016 and a vote by the Council (with deferral) at q2 2016. We believe that much delay is too long. Although the registries understand the IPC's view that there should be a number of URS decisions before commencing the evaluation, the original concept was to just look at the UDRP. In order to compromise with the IPC and the GAC, the RySG agreed it should cover other trademark RPMs as well for new gTLDs. Now, that we agreed to expand the scope, the IPC is using that compromise to ask for further delay. Had we known that when we initially compromised to cover the additional topics, we may not have agreed to increase the scope or we would have separated the motion out to call for the UDRP review within 18 months and a later time period for the rest of the RPMs. Not to mention that the Affirmation of Commitments calls for a review of new gTLDs (which I am sure will also look at RPMs) within 12 months of the launch of the first new gTLD. So whether the data is there or not, ICANN will be evaluating the new RPMs before we commence our PDP on them. Finally, we believe that a Preliminary Issue report can be written before a full set of data is available. It would just be identifying the issues at the time. If additional issues come up or more data comes in, that can be looked at by the Working Group at that time (assuming a PDP is commenced). We are now asking the entire Council to come together and compromise. The NCSG and certain members of the contracted parties house are not happy because they want to commence the PDP on the UDRP right away (at least with respect to certain topics) and the CSG wants to delay the PDP even further to ensure we have the full set of data. Each side has very legitimate arguments. No one is right or wrong and no one is completely happy. Perhaps that is why the RySG believes this motion strikes the appropriate balance :) I hope this note helps and we will discuss further during the meeting. Jeffrey J. Neuman Neustar, Inc. / Vice President, Law & Policy 21575 Ridgetop Circle, Sterling, VA 20166 Office: +1.571.434.5772 Mobile: +1.202.549.5079 Fax: +1.703.738.7965 / jeff.neuman(a)neustar.biz<mailto:jeff.neuman@neustar.biz> / www.neustar.biz<http://www.neustar.biz/> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 0

Fwd: [soac-discussion] Upcoming Public Comments - 2012
by Stéphane Van Gelder Dec. 13, 2011

Dec. 13, 2011

Councillors, FYI. Stéphane Début du message réexpédié : > De : Filiz Yilmaz <filiz.yilmaz(a)icann.org> > Objet : [soac-discussion] Upcoming Public Comments - 2012 > Date : 12 décembre 2011 22:45:23 HNEC > À : "soac-discussion(a)icann.org" <soac-discussion(a)icann.org> > > Dear Community Leaders, > > Following the process (attached) that is now in place since June 2011 (based on the implementation of ATRT recommendation 21), it is time for me to ask for your input for the 2012 Upcoming Public Comments list to be published at: > http://www.icann.org/en/public-comment/upcoming-en.htm > > We are seeking your input about topics that you think will be opened for Public Comment in 2012. > As the ICANN Community leaders you are very well aware of the issues that are being discussed or to be discussed within your groups that will require public input in the coming year. This will provide us valuable feedback for the compilation of this list that will help raising early awareness about the issues among the ICANN community. > > Please send these topics to me until 21 January 2012. > For your convenience, I am also attaching a template for the submissions you would like to make. > > Following the process, after receiving your input, we will publish the list for 2012 by February and make another call for updates after March meeting in Costa Rica. > > Kind regards, > > Filiz Yilmaz > Sr Dir Participation and Engagement > ICANN

1 0

November Council minutes posted and Pending Project list updated
by Glen de Saint Géry Dec. 13, 2011

Dec. 13, 2011

Dear Councillors, Just to inform you that the the Council minutes of the 17 November 2011 meeting have been posted on page: http://gnso.icann.org/calendar/#nov and can be directly viewed at : http://gnso.icann.org/meetings/minutes-council-17nov11-en.htm The Pending Projects list has been updated. http://gnso.icann.org/meetings/pending-projects-list.pdf 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

ICANN Board resolutions from 8 Dec 2011
by Bruce Tonkin Dec. 13, 2011

Dec. 13, 2011

Hello All, See below for information on the Board resolutions passed on 8 Dec 2011. Key areas of interest are: - update on applicant support for needy applicants - update on batching - approval of New Annex A/GNSO Policy Development Process - approval of Board Director compensation - extended conflict of policy to apply to new gTLDs From: http://www.icann.org/en/minutes/resolutions-08dec11-en.htm Approved Board Resolutions | Special Meeting of the ICANN Board 8 December 2011 * Note: Where available, draft Rationale of the Board's actions is presented under the associated Resolution. The draft Rationale is not final until approved with the minutes of the Board meeting. 1.New gTLDs1.1. Applicant Support Rationale for Resolutions 2011.12.08.01 – 2011.12.08.03 1.2. Batching Rationale for Resolutions 2011.12.08.04 – 2011.12.08.06 2.Consent Agenda2.1. Approval of Minutes of 22 October 2011 ICANN Board Meeting 2.2. Approval of Minutes of 28 October 2011 ICANN Regular Board Meeting 2.3. Approval of Minutes of 28 October 2011 ICANN Organizational Board Meeting 2.4. ccNSO Amendment to the Fast Track Implementation Plan Rationale for Resolution 2011.12.08.10 2.5. New Annex A/GNSO Policy Development Process Rationale for Resolution 2011.12.08.11 2.6. Changes to SSAC Membership 2.6.1 Thank You from Security and Stability Advisory Committee to John Schnizlein Rationale for Resolution 2011.12.08.12 2.6.2 SSAC Appointments – Don Blumenthal and Rod Rasmussen Rationale for Resolution 2011.12.08.13 3.ATRT Recommendation 5: Board Compensation Rationale for Resolutions 2011.12.08.14 – 2011.12.18 4.Board Member Rules on Conflicts of Interest for New gTLDs Rationale for Resolution 2011.12.08.19 1. New gTLDs Conflict of Interest Identification: Ram Mohan, Thomas Narten, Thomas Roessler, Bruce Tonkin, Suzanne Woolf and Kuo-Wei Wu did not participate in the deliberation of these items. 1.1. Applicant Support ======================= Whereas, the JAS WG had published its Final Report with recommendations for a program to provide support to applicants requiring financial assistance in applying for and operating new gTLDs. Whereas, a Board working group was formed during the Dakar ICANN Meeting (24-28 October 2011) to work with staff on an implementation model taking into account the JAS WG Final Report and timely implementation of program. Whereas, the Board considered and discussed potential implementation models taking into account the current New gTLD Program development stage and timing. It is hereby Resolved (2011.12.08.01), the Board directs staff to finalize the implementation plan in accordance with the proposed criteria and process for the launch of the Applicant Support Program in January 2012. Resolved (2011.12.08.02), the Board approves the fee reduction to $47,000 Applicant Support candidates that qualify according to the established criteria. Resolved (2011.12.08.03), the Board directs staff to amend the communications campaign as needed to incorporate the Applicant Support Program which should include the publication of a brief handbook. Rationale for Resolutions 2011.12.08.01 – 2011.12.08.03 Delaying the evaluation of financial support applications provides additional time to raise funds. It is intended that the determination of financial need is to be made in parallel with the first batch of “regular” new gTLD applications. If the financial assistance awards are not made until the end of the first batch of new gTLD evaluations, fundraising can operate until November 2012. Delaying also takes the recruitment of the financial assistance evaluation panel off of the critical path. In this new plan, the panel is not required until May 2012. The $138K fee reduction is meaningful in size and follows JAS and GAC recommendations. It is thought that providing a meaningful level of assistance to a fewer number of applicants is better than providing a small benefit to all those who qualify. Assistance is limited to the available funding, thereby mitigating risk. The criteria (demonstrating need and operating in the public benefit) follow JAS recommendations. Completed new gTLD applications are due at the same time the financial assistance applications are due. This will help ensure only serious participants apply for financial assistance. Those who do not meet the criteria threshold will be disqualified from the new gTLD process altogether and lose their $47K fee. This will help ensure only bona fide candidates for assistance will apply. Note: This process does not follow all JAS recommendations. In particular, the JAS recommendations state that the $2MM seed fund should not be used for fee reductions. The JAS intended the $2MM and other funds raised be paid out to needy and worthy applicants to help build out registries. 1.2. Batching ============== Resolved (2011.12.08.xx), the ICANN Board authorizes the President and CEO to develop a plan and propose to the community that a “secondary time stamp” be used for purposes of determining the processing order in the event that multiple batches of applications are to be processed under the New gTLD Program. A “secondary time stamp” would require applicants who are interested in participating in early batches to obtain a time-stamp through a designated process following the close of the application window. Resolved, (2011.12.08.04), there will be no preference given on the basis of whether an application is submitted in the beginning, middle or end of the application window. Resolved (2011.12.08.05), the Board will not approve a system that would include random selection process for determining the development of batches. Resolved (2011.12.08.06), the President and CEO is directed to add to the Applicant Guidebook that upon completion of the Board’s approval of a final designation of the operational details of the “secondary timestamp” batching process, the final plan will be added as a process within the Applicant Guidebook. Rationale for Resolutions 2011.12.08.04 – 2011.12.08.06 The best option from an operational and process management standpoint, random selection, is not available. It is likely to result in lawsuit based upon California law that makes operation of a lottery illegal in most cases. Even if a random selection process were determined to not be a lottery by a court, those seeking to discredit, delay or halt the process would file a lawsuit. The recommended option requires the development and implementation can be done outside of TAS and so not provide risk to the implementation of that complex system. There is judgment required on the part of the applicant, i.e., when to submit the secondary registration in order to increase the likelihood of prioritization in an earlier batch. One key to any mechanism is communications. Communications can be facilitated through TAS since applicants will have registered through the system. Concerns that European and North American participants might have an edge through greater participation in numbers and a higher level of process sophistication are addressed by rotating the award of priorities through every region. There are arguments against this but it is thought that this approach better promotes diversity. In the end, no application is denied consideration. Availability of an opt-out mechanism has been recommended several times in public comment. It will provide those entities that have elected to apply but not fully fleshed out business models time to consider the use of the TLD. Additionally, it will reduce the need and the importance of a batching mechanism. 2. Consent Agenda Resolved, the following resolutions in this Consent Agenda are approved: 2.1 Approval of Minutes of 22 October 2011 ICANN Board Meeting Resolved (2011.12.08.07), the Board approves the minutes of the 22 October 2011 ICANN Board Meeting. 2.2 Approval of Minutes of 28 October 2011 ICANN Regular Board Meeting Resolved (2011.12.08.08), the Board approves the minutes of the 28 October 2011 ICANN Regular Board Meeting. 2.3 Approval of Minutes of 28 October 2011 ICANN Organizational Board Meeting Resolved (2011.12.08.09), the Board approves the minutes of the 28 October 2011 ICANN Organizational Board Meeting. 2.4 ccNSO Amendment to the Fast Track Implementation Plan Whereas, the ICANN Board of Directors approved the Fast Track Implementation Plan at the ICANN meeting in Seoul, Republic of Korea on 30 October 2009 (http://www.icann.org/en/minutes/resolutions-30oct09-en.htm#2) Whereas, at the ICANN meeting in San Francisco in March 2011, the ccNSO formed a sub-group within ccNSO PDP Working Group 1 to provide clarification for the DNS Stability Panel within the IDN ccTLD Fast Track for handling cases of confusing similarity. Whereas, the ccNSO working group conducted a session on its recommendations during the ICANN meeting in Dakar, Senegal, in October 2011, and the ccNSO approved a resolution recommending that the ICANN Board approve an amendment to the Fast Track Implementation Plan in order to provide further guidance for a specific case of confusing similarity. Whereas a proposed amendment to the Fast Track Implementation Plan was prepared to implement the ccNSO recommendation. Resolved (2011.12.08.10), the ICANN Board of Directors approves the proposed amendment to the Fast Track Implementation Plan designed to implement the recommendation approved by the ccNSO at the ICANN meeting in Dakar, Senegal. The President and CEO is directed to incorporate the amendment into the Fast Track Implementation Plan previously adopted by the ICANN Board on 30 October 2009 and implement the amendment as soon as practicable. Rationale for Resolution 2011.12.08.10 Why is the Board addressing this issue now? In December 2010, ICANN conducted the first review of the IDN ccTLD Fast Track Process. The review sought community input on a variety topics including assessment of confusingly similar strings. This resulted in several public sessions and the formation of a sub-group within ccNSO PDP Working Group 1 to provide clarification for the DNS Stability Panel within the IDN ccTLD Fast Track for handling cases of confusing similarity. The working group conducted a session on its recommendations during the ICANN meeting in Dakar, Senegal, in October 2011, and the ccNSO approved a resolution recommending that the ICANN Board approve an amendment to the Fast Track Implementation Plan in order to provide further guidance for a specific case of confusing similarity. What is the proposal being considered? This modification to the Fast Track Implementation Plan is made to clarify the rules for the DNS Stability Panel in its evaluation of confusing similarity of requested IDN ccTLD strings. This change addresses specific situations when a requested IDN ccTLD string is confusingly similar to an existing ASCII ccTLD and the request is being made by the existing ccTLD operator with consent of the relevant public authority for the country or territory name requested. Which stakeholders or others were consulted? The string similarity topic was the focus of a public session held during ccNSO meetings during the ICANN meetings in San Francisco in March 2011. This meeting resulted in the ccNSO forming a sub-group created within IDN ccPDP Working Group 1 to work on providing more guidelines to improve the predictability of confusingly similar strings. The ccNSO sub-group reported its findings during another public ccNSO session during the Dakar meeting in October 2011 Are there fiscal impacts or ramifications on ICANN? There are no anticipated fiscal impacts on ICANN from this decision. The amendment will clarify the rules for confusing similarity in the IDN ccTLD Fast Track, upholding ICANN’s obligation to manage the introduction of new TLDs in a secure and stable manner, and is not expected to affect or impact the security or stability of the DNS. 2.5 New Annex A/GNSO Policy Development Process ================================================ Whereas, in October 2008, the GNSO Council established a framework (see GNSO Council Improvement Implementation Plan; (http://www.icann.org/en/topics/gnso-improvements/gnso-improvements-implemen… [PDF, 95 KB]) for implementing the various GNSO Improvements identified and approved by the ICANN Board of Directors on 26 June 2008 (http://www.icann.org/en/minutes/resolutions-26jun08.htm#_Toc76113182) (http://www.icann.org/en/minutes/resolutions-26jun08.htm) Whereas, that framework included the formation, in January 2009, of two Steering Committees, the Operations Steering Committee (OSC) and the Policy Process Steering Committee (PPSC), to charter and coordinate the efforts of five community work teams in developing specific recommendations to implement the improvements; Whereas, the PPSC established two work teams, including the Policy Development Process Work Team (PDP-WT), which was chartered to develop a new policy development process that incorporates a working group approach and makes it more effective and responsive to ICANN's policy development needs; Whereas, the GNSO Council decided to terminate the PPSC on 28 April 2011 and instructed the PDP-WT to deliver its Final Report directly to the GNSO Council; Whereas, the PDP-WT submitted its Final Report (http://gnso.icann.org/issues/pdp-wt-final-report-final-31may11-en.pdf [PDF,1.39 MB]) on 1 June 2011 to the GNSO Council; Whereas the GNSO Council opened a 30-day public comment period on the Final Report (see http://www.icann.org/en/announcements/announcement-2-09jun11-en.htm) Whereas the GNSO Council referred those comments back to the PDP-WT for consideration (see http://gnso.icann.org/resolutions/#201107) Whereas the PDP-WT reviewed those comments and updated the report as deemed appropriate (see https://community.icann.org/download/attachments/9405500/PDP-WT+Public+Comm…) Whereas the PDP-WT submitted its Updated Final Report (see http://gnso.icann.org/improvements/updated-final-report-pdpwt-28sep11.pdf [PDF, 1.51 KB]) to the GNSO Council on 27 September 2011. Whereas, the GNSO Council adopted the Updated Final Report, including the proposed new Annex A and the PDP Manual unanimously. Resolved (2011.12.08.11), the ICANN Board adopts the new Annex A as described in http://www.icann.org/en/general/proposed-bylaws-revision-annex-a-clean-04no… [PDF, 80 KB]. The Bylaws as amended will take effect upon adoption. The transition to the new PDP will be conducted as recommended by the GNSO Council in its resolution (see http://gnso.icann.org/resolutions/#201110) Rationale for Resolution 2011.12.08.11 Why is the Board addressing the issue now? On 26 June 2008 the ICANN Board approved a set of recommendations designed to improve the effectiveness of the GNSO, including its policy activities, structure, operations, and communications. The following pertains to the PDP: “Revising the PDP: The Policy Development Process (PDP) needs to be revised to make it more effective and responsive to ICANN's needs. It should be brought in-line with the time and effort actually required to develop policy and made consistent with ICANN's existing contracts (including, but not limited to, clarifying the appropriate scope of GNSO “consensus policy” development). While the procedure for developing "consensus policies" will need to continue to be established by the Bylaws as long as required by ICANN's contracts, the GNSO Council and Staff should propose new PDP rules for the Board's consideration and approval that contain more flexibility. The new rules should emphasize the importance of the preparation that must be done before launch of a working group or other activity, such as public discussion, fact-finding, and expert research in order to properly define the scope, objective, and schedule for a specific policy development goal and the development of metrics for measuring success. The revised PDP, after review and approval by the GNSO Council and ICANN Board, would replace the current PDP defined in Annex A of the ICANN bylaws”. The GNSO Council has now submitted its proposal for this revised PDP. What is the proposal being considered? In furtherance of this effort, the GNSO Council unanimously recommended to the ICANN Board the adoption of a policy development process (PDP) as outlined in the Updated PDP Final Report [PDF, 1.51 MB]. The proposed Annex A to the ICANN Bylaws, and the PDP Manual proposed in the Updated PDP Final Report attempts to achieve the goals established by the ICANN Board when it approved the restructure of the GNSO Council. This revised PDP, after review and approval by ICANN Board, would replace the current PDP defined in Annex A of the ICANN Bylaws. The main elements of the new PDP include, amongst others: ◦Recommending the use of a standardized "Request for an Issue Report Template" ◦The introduction of a "Preliminary Issues Report" which shall be published for public comment prior to the creation of a Final Issues Report to be acted upon by the GNSO Council ◦A Requirement that each PDP Working Group operate under a Charter ◦Dialogue between the GNSO Council and an Advisory Committee in the event that an the GNSO Council decides not to initiate a PDP following an Issues Report requested by such Advisory Committee ◦Seeking the opinion of other ICANN Advisory Committees and Supporting Organizations, as appropriate that may have expertise, experience, or an interest in the PDP issue early on in the process ◦Changing the existing Bylaws requiring a mandatory public comment period upon initiation of a PDP to optional at the discretion of the PDP Working Group ◦Clarification of ‘in scope of ICANN policy process or the GNSO’ ◦Changing the timeframes of public comment periods including (i) a required public comment period of no less than 30 days on a PDP Working Group’s Initial Report and (ii) a minimum of 21 days for any non-required public comment periods the PDP WG might choose to initiate at its discretion ◦Maintaining the existing requirement of PDP Working Groups producing both an Initial Report and Final Report, but giving PDP Working Groups the discretion to produce additional outputs ◦A recommendation allowing for the termination of a PDP prior to delivery of the Final Report ◦Guidance to the GNSO Council on the treatment of PDP WG recommendations ◦New procedures on the delivery of recommendations to the Board including a requirement that all reports presented to the Board are reviewed by either the PDP Working Group or the GNSO Council and made publicly available ◦The use of Implementation Review Teams Which stakeholders or others were consulted? Public comment forums were held on the Initial Report, the Proposed Final Report, the Final Report and the proposed new Annex A, in additional to regular updates to the GNSO Council as well as workshops to inform and solicit the input from the ICANN Community at ICANN meetings (see for example, the ICANN Meeting in Brussels and San Francisco). What concerns or issues were raised by the community? In addition to workshops and regular updates to the GNSO Council, three public comment periods were held on the different versions of the report. Eight community submissions were received during the public comment forum on the Initial Report, seven contributions were received in relation to the Proposed Final Report and four contributions were received during the public comment forum on the Final Report. The PDP-WT reviewed all the comments received in great detail and documented how each of these comments were considered by the PDP-WT and how these comments resulted in changes to the report, if any (see Annex A, B and C of the Updated PDP Final Report [PDF, 1.51 MB]). As a result, all issues and concerns raised were addressed and responded to by the PDP-WT. A summary and analysis of comments received during the public comment period prior to ICANN Board consideration of the revisions to Annex A can be found here: [To be completed following closing of public comment period on 5 December]. As of 23 November 2011, no comments were received What significant materials did the Board review? The Board reviewed the Updated PDP Final Report, including the Annexes that detail how the PDP-WT has reviewed and addressed the comments received, the proposed Annex A, a redline showing the changes from the Current Annex A, as well as the summary of public comments and Staff's response to those comments. What factors the Board found to be significant? The recommendations were developed allowing for broad community input and participation. The Updated Final Report was adopted unanimously by the GNSO Council. The new PDP is expected to: maximize the ability for all interested stakeholders to participate in the GNSO's policy development processes; incorporate the Working Group model; ensure that the policy development process is based on thoroughly-researched, well-scoped objectives, and are run in a predictable manner that yields results that can be implemented effectively; and make it more effective and responsive to ICANN’s policy development needs. Are there positive or negative community impacts? As outlined above, the ICANN Board expects positive effects of the new PDP, including maximizing the ability for all interested stakeholders to participate in the GNSO’s policy development process. Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, budget); the community; and/or the public? No fiscal impacts or ramifications on ICANN; the community; and/or the public are expected. Are there any security, stability or resiliency issues relating to the DNS? There are no security, stability, or resiliency issues related to the DNS if the Board approves the proposed recommendations. 2.6 Changes to SSAC Membership 2.6.1 Thank You from Security and Stability Advisory Committee to John Schnizlein Whereas, John Schnizlein was appointed to the ICANN Security and Stability Advisory Committee on 26 June 2009. Whereas, ICANN wishes to acknowledge and thank John Schnizlein for his service to the community by his membership on the Security and Stability Advisory Committee. Rationale for Resolution 2011.12.08.12 It is the practice of the SSAC to seek Board recognition of the service of Committee members upon their departure. 2.6.2 SSAC Appointments – Don Blumenthal and Rod Rasmussen Whereas, the Security and Stability Advisory Committee (SSAC) does review its membership and make adjustments from time-to- time. Whereas, the SSAC Membership Committee, on behalf of the SSAC, requests that the Board should appoint Rod Rasmussen and Don Blumenthal to the SSAC. Resolved (2011.12.08.13) that the Board appoints Rod Rasmussen and Don Blumenthal to the SSAC. Rationale for Resolution 2011.12.08.13 The SSAC is a diverse group of individuals whose expertise in specific subject matters enables the SSAC to fulfill its charter and execute its mission. Since its inception, the SSAC has invited individuals with deep knowledge and experience in technical and security areas that are critical to the security and stability of the Internet’s domain name system. The SSAC’s continued operation as a competent body is dependent on the accrual of talented subject matter experts who have consented to volunteer their time and energies to the execution of the SSAC mission. Don Blumenthal is a Senior Policy Advisor with the Public Interest Registry. He would bring to the SSAC wide experience from government and law enforcement. Rod Rasmussen is President and CTO of Internet Identity. He would bring to the SSAC extensive experience in cross-industry organizations, law enforcement collaboration, and Internet policy development. 3. ATRT Recommendation 5: Board Compensation ============================================== Whereas, ICANN is considering whether to offer compensation to all of its voting directors for their services to ICANN. Whereas, ICANN is a nonprofit California public benefit corporation that is exempt from Federal income tax under §501(a) of the Internal Revenue Code of 1986, as amended (the “Code”) as an organization described in §501(c)(3) of the Code. Whereas, ICANN may not pay directors more than Reasonable Compensation as determined under the standards set forth in §53.4958-4(b) of the regulations issued under §4958 of the Code (the “Regulations”). Whereas, ICANN has taken all steps necessary, and to the extent possible, to establish a presumption of reasonableness in the level of voting Board member compensation, if approved. Whereas, certain portions of ICANN’s current Conflicts of Interest Policy must be revised in order for the Board to vote on whether to approve compensation for the voting Directors. Whereas, certain portions of ICANN’s current Bylaws must be revised in order to allow voting Board members other than the Chair to be compensated. Whereas, the public comments received on the specific proposed revisions to the Conflicts of Interest Policy and Bylaws generally were in favor of the proposed revisions. Whereas, the Board recognizes that many commenters suggested additional but unrelated revisions to the Conflicts of Interest Policy, which ICANN is committed to reviewing and revising as appropriate (see Board Resolution on Review of ICANN Conflicts of Interest Policy and Ethics at http://www.icann.org/en/minutes/resolutions-28oct11-en.htm#6) Resolved (2011.12.08.14), the Board approves the limited changes to ICANN’s Conflicts of Interest Policy needed to allow the Board to either approve or reject the Independent Valuation Expert recommendation on voting Board member compensation. Resolved (2011.12.08.15), the Board approves the limited changes to ICANN’s Bylaws needed to allow all voting Board members to receive compensation for services provided. Resolved (2011.12.08.16), the Board approves the recommendation from the Independent Valuation Expert (as that term is defined in §53.4958-1(d)(4)(iii)(C) of the IRS Regulations), made in its Report or Reasoned Written Opinion, (as that term is defined in §53.4958-1(d)(4)(iii)(C) of the Regulations), that it is reasonable to “[i]ntroduce annual cash retainer of $35,000 for outside directors and maintain the $75,000 for Chairman of the Board” and “[a]n additional $5,000 annual retainer would be provided for committee chair (except the Chairman of the Board).” Resolved (2011.12.08.17), all Board members will be required to complete and sign a form either specifically accepting or declining the approved compensation, and a list of all will be posted on the Board of Directors page. Resolved (2011.12.08.18), compensation for all voting Board members who choose to accept the compensation approved herein, shall be effective on 9 December 2011. Rationale for Resolutions 2011.12.08.14 – 2011.12.18 Over the past several years, ICANN has been considering issues surrounding voting Board member compensation. The Board has publicly discussed the matter and has reviewed independent analysis and advice on the matter, as well as public comment. For example: (i) there were calls from the community in relation to ICANN Framework for Accountability and Transparency that voting Board members be compensated; (ii) budget contingency discussions since FY08 have involved the concept of possible Board compensation; (iii) outside counsel provided advice on the ramifications of Board compensation, including identification of assessments and safeguards ICANN would need to establish before proceeding; (iv) Watson Wyatt, and then Towers Watson, provided studies on other non-profit organizations and Board member compensation; (v) the Boston Consulting Group (“BCG”) that conducted the Board Review suggested that relatively modest fees to compensate voting directors for service may be appropriate; (vi) the Board Review working group acknowledged general support from the BCG and the community for director compensation, but recommended further study in coordination with General Counsel; (vii) the Accountability and Transparency Review Team (ATRT) specifically recommended that the Board should implement a compensation scheme for voting Board members; and (viii) public comment and input was sought on required changes to ICANN’s Conflicts of Interest Policy and Bylaws, as well as on the Independent Expert report on voting Board member compensation. In August of 2010, the Board approved compensation for the Board Chair. (See http://www.icann.org/en/minutes/resolutions-05aug10-en.htm#5.) Since that time, a call for all voting Board members to be compensated has continued, most recently through Recommendation 5 from the ATRT. On 24 June 2011, the Board noted that the CEO and General Counsel had been directed to take the next steps to properly consider the ATRT’s recommendation. (See http://www.icann.org/en/minutes/resolutions-24jun11-en.htm#2.) ICANN followed a process calculated to pay an amount that is in its entirety Reasonable Compensation for such service under the standards set forth in §53.4958-4(b) of the Treasury Regulations. First, the Board sought a recommendation from an Independent Valuation Expert (“Expert”) as to the reasonableness of, and if so, the amount of compensation. The Board approved Towers Watson (TW) to be engaged to serve as the Expert. TW is a leading global professional services company with expertise in compensation for non-profit organizations. TW had provided advice on the Board Chair compensation and was recommended by the National Association of Corporate Directors to serve as the Expert. The Expert Report, which was posted for public feedback, can be found with the Announcement at http://www.icann.org/en/announcements/announcement-3-04nov11-en.htm. Second, in the event that the Expert recommended compensation for voting Board members and the Board intended to vote on that recommendation, ICANN’s Conflicts of Interest (COI) Policy had to be revised. Currently, the Policy states “[n]o Director shall vote on any matter in which he or she has a material Financial Interest that will be affected by the outcome of the vote.” (See Article II, section 2.4(a) http://www.icann.org/en/committees/coi/coi-policy-30jul09-en.htm.) Thus, voting on Board compensation without any change would be a direct conflict of interest. Accordingly, the Board approved posting for public comment limited revisions to the COI Policy that will allow the Board to vote on director compensation. (See http://www.icann.org/en/public-comment/bylaws-amend-vi-coi-policy-01sep11-e….) Third, in the event that the Expert recommended a compensation arrangement for voting directors and the Board approves that recommendation, ICANN’s Bylaws must be changed. Currently the Bylaws specifically prohibit compensation for voting directors. Article VI, section 22 states “All Directors other than the Board Chair shall receive no compensation for their services as Directors.” See http://www.icann.org/en/general/bylaws.htm#VI. The Board approved the posting for public comment proposed revisions to the Bylaws that would allow all voting Directors to be compensated. (See http://www.icann.org/en/public-comment/bylaws-amend-vi-coi-policy-01sep11-e….) The Board was provided a summary of all of the public comments with reference to each individual comment (see http://www.icann.org/en/public-comment/bylaws-amend-vi-coi-policy-01sep11-e…) on the specific proposed revisions and determined that all generally were in favor of the proposed revisions as they were necessary to allow for all voting Board members to be receive compensation, if approved. Further, no Feedback was received on the Expert Report. The Board has thus taken all steps necessary to ensure that consideration of voting Board member compensation for services provided was done in accordance with all appropriate laws, rules and regulations, including that any compensation be, in its entirety, Reasonable Compensation under the standards set forth in §53.4958-4(b) of the Treasury Regulations. In making its decision and passing these resolutions, the Board has reviewed all of relevant materials referenced above. In addition, throughout the time the Board has been considering the issue of voting Board member compensation, it has had the opportunity to review and consider: (i) the Boston Consulting Group’s Independent Review Final Report, comment on that report, the Board Review Working Group’s Final Report and comment on that final report (all of which can be found at http://www.icann.org/en/reviews/board/) and (ii) the ATRT Recommendations and related comments, all of which can be found through http://www.icann.org/en/public-comment/public-comment-201012-en.htm#atrt-dr… and http://www.icann.org/en/announcements/announcement-31dec10-en.htm. Taking these steps positively impacts the accountability and transparency of ICANN as it fulfills a particular recommendation of the ATRT. Further, regularly informing the community through posting all of the process steps the Board is followed, as well as the proposed revisions for the Conflicts of Interest Policy and the Bylaws, and the Expert Report, significantly enhanced ICANN’s transparency in this matter. Accordingly, this should have a positive community impact in its implementation. Compensating voting Board members who choose to accept compensation at the amount recommended and approved will have a fiscal impact on ICANN. For this fiscal year, in anticipation of possible approval of voting Board member compensation, a portion of the budgeted contingency fee has been identified to cover whatever amount is needed to compensate voting Board members as approved pursuant to this resolution. As it is not yet not known precisely how many Board members will and will not accept compensation, the precise amount needed has not yet been calculated. This decision will have no impact on the security, stability or resiliency of the domain name system. 4. Board Member Rules on Conflicts of Interest for New gTLDs ============================================================== Whereas, ICANN is committed to attaining a higher ethical standard to ensure the legitimacy and sustainability of the multi-stakeholder model. Whereas, ICANN's current corporate governance documents, as set out at http://www.icann.org/en/documents/governance/, include a Conflicts of Interest Policy and Board Code of Conduct (including ethical guidelines and confidentiality provisions). Whereas, it is crucial to have strengthened rules and practices in place as ICANN embarks on the New gTLD Program. Whereas, ICANN is undertaking multiple external reviews of its existing Conflicts of Interest Policy, Code of Conduct and other conflicts and ethics practices. Whereas, while awaiting specific recommendations for enhancements to ICANN's policies and practices, ICANN is committed to demonstrating that it will treat decisions approving any new gTLD application in an ethical manner and with care to avoid even an appearance of a conflict of interest. Resolved (2011.12.08.19), the Board adopts the following conflicts of interest rules as they specifically apply to the New gTLD Program: ◦Any and all Board members who are either knowingly or potentially advising on, or involved in any way with submitting, any new gTLD application: ■Will not vote on that application or any related application; ■Will not participate in any deliberations about that application or any related application; and ■Will not receive any information about that application or any related application until such information is made public. ◦Any and all Board members who approve any new gTLD application shall either: ■Not take a contracted or employment position with any company sponsoring or in any way involved with that new gTLD for 12 months after the Board made the decision on the application. ◦If deliberations call for expertise about the industry operations, or any other matters, that could be provided by a Board member excluded as a result of these rules, the Board member can be asked to participate in the limited discussion requiring such expertise. Independent experts could be similarly invited to participate in the deliberations. If such expertise is sought, the nature of the discussion and the expert will be identified in the meeting minutes or notes, as applicable. ◦In addition to all of the above, all existing conflicts of interest, ethics and conduct requirements continue to apply to all Board members, including the prohibition on using any confidential information obtained while serving on the Board for any other purpose whatsoever. Rationale for Resolution 2011.12.08.19 Over the past several months, ICANN has placed a strong emphasis on the need for enhancing ICANN's policies relating to conflicts of interest, ethics, confidentiality and an overall code of conduct. During the Singapore meeting, the President and CEO identified such issues as crucial given that the New gTLD Program was entering into a new phase with Board approval, which was taken on 20 June 2011. In addition, the community has been calling for a thorough review of these policies. Accordingly, ICANN has determined that it should strive to achieve a Gold Standard in both the documentation of polices and the adherence to polices relating to conflicts of interest ethics, confidentiality and code of conduct. In order to achieve the Gold Standard that ICANN has determined to achieve, ICANN is undertaking multiple external reviews of its conflicts and ethics practices. First, our corporate law firm is reviewing our current working documents, including our "Conflicts of Interest Policies", "Code of Conduct" and "Employee Handbooks," to enhance the focus on best practices for conflicts and ethics. Second, a new independent law firm (not involved in ICANN processes) is reviewing ICANN's documentation, comparing ICANN to similarly situated non-profits and making recommendations for enhancements. Third, ICANN is contracting with an international expert group to review ICANN's documents and practices and to make recommendations. This group will focus on ICANN's global function and the best practices of other international organizations. While awaiting specific recommendations for enhancements to ICANN's policies and practices, ICANN is committed to demonstrating that it will treat decisions relating to approving any new gTLD application in an ethical manner and with care, to avoid even the appearance of a conflict of interest. Accordingly, ICANN has passed this resolution to help direct the Board members’ conduct. Again, it should be noted that this is not meant to supplant or supersede any existing or soon to be additional policies and practices relating to conflicts of interest, conduct or ethical behavior. Taking this action will positively impact the ICANN community by addressing these issues with urgency, and committing to the highest ethical standards, particularly with respect to the New gTLD Program. Such enhancements are meant to ensure the legitimacy and sustainability of the multi-stakeholder model as enshrined in ICANN. Further, this resolution will should not have any fiscal impact on ICANN or the community. This action will not have any impact on the security, stability and resiliency of the domain name system.

1 0

Preliminary Issue Report on the Registrar Accreditation Agreement Amendments
by Margie Milam Dec. 13, 2011

Dec. 13, 2011

Dear All, I am pleased to report that the Preliminary Issue Report on the Registrar Accreditation Agreement Amendments requested by the ICANN Board in Dakar has been published today. A copy of the Preliminary Issue Report is attached for your review and consideration. A public comment forum has been opened until January 13, 2012 at the link below: http://www.icann.org/en/announcements/announcement-2-12dec11-en.htm Please let me know if you have any questions regarding the Preliminary Issue Report, or the status of the RAA negotiations. Best regards, Margie ___________ Margie Milam Senior Policy Counselor ICANN ___________

1 0