February 2014 - council - lists.icann.org

Who is @ICANN_GNSO?
by Avri Doria 21 Feb '14

21 Feb '14

Hi, Just notified that my tweets were being followed by @ICANN_GNSO. I obviously have no problem with that. What I am wondering is who is acting as the official tweeting voice of the GNSO? thanks avri

3 4

Updated Proposed Agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC
by Glen de Saint Géry 20 Feb '14

20 Feb '14

Dear Councillors, Please find the updated proposed agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC. http://gnso.icann.org/en/meetings/agenda-council-27feb14-en.htm https://community.icann.org/display/gnsocouncilmeetings/Agenda+27+February+… The updates relate to a change in the order of the updates and discussions that have been changed to accommodate Sally Costerton who will address the Council on GNSO Engagement with the work of the ICANN Strategy Panels, and under Any Other Business: Two items have been added, namely: * ICANN Board Seat 14 - NCPH - additional Council meeting Thursday, 10 April 2014 at 14:00 UTC * Note the Root Server System Advisory Committee (RSSAC) presence in Singapore Proposed Agenda for the GNSO Council Teleconference 27 February 2014. 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 <http://gnso.icann.org/en/council/op-procedures-13jun13-en.pdf%20> > 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 11:00 UTC http://tinyurl.com/nkaf7dk Coordinated Universal Time 11:00 UTC 03:00 Los Angeles; 06:00 Washington; 11:00 London; 12:00 Brussels; 19:00 Perth 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. GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 mins) 1.1 Roll Call 1.2 Statement of interest updates Maria Farrell https://community.icann.org/display/gnsosoi/Maria+Farrell+SOI 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meetings 23 January 2014<http://gnso.icann.org/en/meetings/minutes-council-23jan14-en.htm> were posted as approved on 17 February 2014. Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (0 mins) Item 4: UPDATE & DISCUSSION - GNSO Engagement with the work of the ICANN Strategy Panels (15 mins) Here the Council will receive an update on any relevant interaction with and output from the strategy panels and discuss any appropriate action going forward. 4.1 - Status update (Sally Costerton) 4.2 - Discussion 4.3 - Next steps Item 5: UPDATE - PDP Working Group on Translation & Transliteration of Contact Information (10 mins) The GNSO Council recently initiated a Policy Development Process<http://gnso.icann.org/en/basics/pdp-process.htm> (PDP) on the Translation and Transliteration of Contact Information. As part of its efforts to obtain broad input from the ICANN Community at an early stage of its deliberations, the Working Group has requested input from the Supporting Organizations (including the GNSO) and Advisory Committees on several questions relating to the issues identified in the PDP Final Issue Report. 5.1 - Update (Ching Chiao) 5.2 - Discussion 5.3 - Next steps Item 6: UPDATE & DISCUSSION - International Internet Governance Issues (20 mins) Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. Item 7: UPDATE & DISCUSSION - GAC Engagement - the work of the Joint GAC / GNSO Consultation Group (15 mins) Here the Council will receive an update and discuss any action going forward. 7.1 - Status update 7.2 - Discussion 7.3 - Next steps Item 8: UPDATE & DISCUSSION - Forthcoming review of the GNSO (10 mins) As part of a periodic review process that is built into the ICANN model, ICANN board initiated reviews of the GNSO (and the GNSO Council and related functions) are expected. In order to be informed and effectively prepared for this work, we have begun to engage with the body that commissions such reviews (the structural improvements committee) through its chair, Ray Plazk. The Council will track the planning work of the SIC and, where appropriate; provide relevant input to the process. We will also prepare to undertake a form of self-review in a similar format to that which we expect to arise out of the work of the SIC. A self-review will ensure that we are not only prepared for the board initiated work but also able to flag areas for potential improvement in as timely as possible a manner. 8.1 - Update (Jennifer Wolfe) 8.2 - Discussion 8.3 - Next steps Item 9: UPDATE & DISCUSSION - Planning for Singapore (15 mins) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, David Cake will lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council's proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board. 9.1 - Update (David Cake & Jonathan Robinson) 9.2 - Discussion 9.3 - Next steps Item 10: Any Other Business (10 mins) * Community budget requests * ICANN Board Seat 14 - NCPH - additional Council meeting Thursday, 10 April 2014 at 14:00 UTC * Note the Root Server System Advisory Committee (RSSAC) presence in Singapore 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: 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 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 and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 03:00 Iowa City, USA (CST<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+1DST 05:00 New York/Washington DC, USA (EST) UTC-4+1DST 06:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 08:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 09:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 08:00 London, United Kingdom (BST) UTC+0DST 11:00 Bonn, Germany (CET) UTC+1+0DST 12:00 Stockholm, Sweden (CET) UTC+1+0DST 12:00 Cairo, Egypt, (EET) UTC+2+0DST 13:00 Istanbul, Turkey (EEST) UTC+2+0DST 13:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 13:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 19:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/nkaf7dk Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Recapping today's ccNSO Council meeting
by john＠crediblecontext.com 20 Feb '14

20 Feb '14

All, Today's ccNSO Council meeting did not have a quorum so all motions were put off. Interestingly, not put off to the next meeting, but to the mailing list. An example of some of the ways our two Councils operate differently. Let with discussion items only, the bulk of the meeting was devoted to Internet governance. While the best that was said is that the multiple efforts (e.g., 1Net, cross-community working group, Strategy Panel on the Internet Governance Ecosystem and the 5th Panel) are “starting to get more functional.” It is clear that momentum on this issue and the date of the meeting in Brazil will make it hard for ICANN in general and Fadi in particular to tamp down urgency on Internet governance in Singapore. We know this is his intent on the strength of his comments at the most recent SO & AC Leaders conference call. There were some stats reported about the Brazil meeting. There are 800 spots available and 433 “expressions of interest” have been made. Of those expressions, 31 percent are female and 69 percent are male. Regionally, 37 percent are from Latin America, 19 percent are from Europe, 18 percent are from North America, 12 percent from Asia, 11 percent from Africa and 3 percent from Oceana. There was a sense of the ccNSO Council that participation by ccTLD managers is being tamped down because the organizers are focused on three other kinds of participants: Government, Business and Civil Society. The frustration over this was focused on the future of the IANA contract which it was said is essential to the cc's. Finally, there was a report from staff that name collisions will be on the Singapore agenda for the ccNSO Council meeting. Cheers, Berard

1 0

GNSO Project List - for review
by Glen de Saint Géry 20 Feb '14

20 Feb '14

Dear Councillors, Please find attached for your review the revised project list, both in redline and clean format, in preparation for the GNSO Council meeting on 27 February at 11:00 UTC. For reference, the updated project list is posted at: http://gnso.icann.org/meetings/projects-list.pdf on page : http://gnso.icann.org/en/council/project under the heading: Council activities 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

4 3

ICANN Board resolution from meeting held 17 Feb 2014
by Bruce Tonkin 20 Feb '14

20 Feb '14

http://www.icann.org/en/groups/board/documents/resolutions-17feb14-en.htm Approved Board Resolutions | Special Meeting of the ICANN Board 17 February 2014 President's Globalization Advisory Groups Whereas, the multistakeholder model has matured in response to the many challenges of exponential growth in the Internet, so ICANN must continue to evolve and grow in response to those challenges. Whereas, ICANN's mission and responsibilities are to the global community and stakeholders worldwide. Whereas, as a multistakeholder organization ICANN must evolve to fully execute its narrow mission, which is to coordinate, at the overall level, the global Internet's systems of unique identifiers, and be in a position to meet new challenges whether operational, policy, political or technical. Whereas, in order for ICANN to fully execute its mission as a multistakeholder organization and be in a position to meet operational, policy, political, or technical challenges, there must be an evolution of the globalization of ICANN. Whereas, the globalization of ICANN includes, among other things: strengthening and continuing to evolve and improve ICANN as a multistakeholder organization; and contributing as a partner in the Internet eco-system to strengthen awareness and the evolution of multistakeholder Internet governance and cooperation in a manner that ensures the continued flexibility to adapt to emerging issues. Whereas, on 28 September 2013, the ICANN Board authorized the CEO to, among other things, "work with other key organizations and leaders to establish a coalition towards the formation of a movement or initiative" ("Coalition"), in order to address increasing concerns regarding the effectiveness of a "global, open, multi-stakeholder Internet governance system." Whereas, the President and CEO has executed the mandate of the 28 September 2013 Board resolution and has helped facilitate a number of activities, including: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" (ii) development of and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. Whereas, on 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the President and CEO to continue supporting the three emerging and evolving initiatives and recognizing that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following three initiatives: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; (ii) development and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multistakeholder Internet governance that is now likely to take place in Brazil in April 2014. Whereas, in Resolution 2013.11.17.01, the Board noted that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." Whereas, the continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. Whereas, given the nature and breadth of issues involved with the continued globalization efforts, ICANN has recognized the importance of the timely establishment of groups of Board members to focus on given topic areas, and then report and make recommendations to the President and CEO, and the full Board, for consideration. Whereas, as part of its continued globalization efforts, ICANN should establish certain "President's Globalization Advisory Groups" composed of Board members to address the following areas: Affirmation of Commitments ("AOC"), policy structures, legal structure, root server system, the IANA multistakeholder accountability, and Internet governance. Resolved (2014.02.17.01), the Board approves the creation of several President's Globalization Advisory Groups in order to support further ICANN globalization. These Advisory Groups of Board members are being set up to provide guidance to the full Board in support of ICANN's globalization work led by the President and CEO. The President's Globalization Advisory Groups will meet with the community during ICANN 49 Singapore Meeting, and around IETF 89, and other community meetings to discuss the ICANN globalization issues. The President's Globalization Advisory Groups will then make recommendations to the Board, which the Board will report during ICANN 50 London Meeting. These Advisory Groups will deal with the following topics: Affirmation of Commitments ("AOC"); policy structures; legal structure; root server system; the IANA multistakeholder accountability; and, Internet governance. The President and CEO will announce the composition of these Advisory Groups within two days following the posting of this resolution at http://www.icann.org/en/groups/other/globalization-19feb14-en.pdf [see attached]; the President and CEO shall have the authority to change the Advisory Groups and their composition from time to time, without requiring a further resolution. RATIONALE FOR RESOLUTION 2014.02.17.01 This resolution is a continuation of the Board's 28 September 2013 and 17 November resolutions providing ICANN's President and CEO with a mandate to explore how ICANN could coordinate with stakeholders from across the globe to address the pressing issue of the future of Internet governance. On 28 September 2013, the Board directed the President and CEO to work towards the establishment of a coalition to start an effort to form an Internet cooperation agenda, and to do so in a manner consistent with ICANN's mission. Following the September meeting, the President and CEO executed the mandate of the 28 September 2013 Board resolution and helped facilitate a number of activities, including: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance;" (ii) development of and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. On 17 November 2013, the Board approved Resolution 2013.11.17.01 directing the CEO to continue supporting the three emerging and evolving initiatives and recognizes that ICANN, as part of the Internet ecosystem, is just one of the many participants providing resources and support to the following initiatives: (i) the expansion and launch of a previously announced strategy panel now entitled "Panel on the Future of Internet Governance"; (ii) development and participation in the "1net initiative"; and (iii) encouraging the establishment of and support for a meeting on multi-stakeholder Internet governance that is now likely to take place in Brazil in April 2014. The Board also noted in Resolution 2013.11.17.01 that "without strengthening a global, coherent approach to Internet governance, ongoing and emerging issues will not be properly addressed in a collective, collaborate way, which may inadvertently affect the operational unity of the Internet, consistent with ICANN's mandate." ICANN and the multistakeholder model have been exposed to many challenges, and ICANN must evolve to face the challenges. ICANN's mission and responsibilities are to the global community and stakeholders worldwide. To remain accountable to ICANN's mission and community, the Board recognizes that as a multistakeholder organization ICANN must evolve to fully execute on its mission, and be in a position to meet the challenges whether operational, political or technical. The continued globalization of ICANN must evolve in several ways, including: partnerships in the broader Internet eco-system to strengthen multistakeholder Internet governance frameworks; strengthening ICANN itself, including affirmations of commitments and relationships among the stakeholders; evolving the policy structures to serve and scale to the needs of the global community, and identify opportunities for the future legal structures and IANA globalization. This is an Organizational Administrative Function for which public comment is not required. Published on 19 February 2014

1 0

FW: CEO/Community Leaders Conference Call - 18 Feb 2014
by Jonathan Robinson 19 Feb '14

19 Feb '14

All, Yesterday, ICANN senior staff held a second CEO / Community Leaders Conference Call. As I understand it, this is intended to be a regular briefing and interaction session which assists in bridging the (significant) time gap between ICANN meetings. Especially in the context of such significant activity. A recording of the call will be circulated shortly but I thought it may be helpful if I shared a couple of highlights that I picked up personally. In particular 3 key areas were raised by Fadi Chehade as follows: 1. Introduction of major themes for the ICANN Singapore Meeting 2. Encourage feedback and comments on Strategic Panel suggestions/recommendations 3. An update on the Recent Board Workshop Singapore Themes: a. Carry strategic planning through to final stages. N.B. The issuing of strategic panels reports will occur prior to the meeting. All will be out by this weekend. It is very important that ICANN hears from us. N.B. These are recommendations for discussion & debate. b. Recognise and ATRT2 outputs. We need to embrace these and recognise how they need to be acted on. c. ICANN globalisation area. There is broad momentum gathering behind this and we will shortly see an ICANN board resolution from 18 February regarding ICANN globalisation My personal take on this is positive i.e. that ICANN Singapore will not be dominated solely by the Internet Governance agenda. Important as this topic is, we have plenty to think about and do as we get on with the "day job" at ICANN. Encouragingly, this balance is also consistent with the weighting that the GNSO Council has been placing on these areas (where appropriate to our remit) i.e. with a relatively even balance between a, b & c above. Fadi also touched on budgeting and expenses before handing over to Xavier (ICANN's CFO) to discuss these in more detail. A key point Fadi made was his intention to: A. Manage operations within the budget and B. Recognise that the rate of expenditure growth needs to slow down from circa 20% per annum to a growth rate of high teens next year and then low teens the following year. Fadi & Xavier's input were followed by Q&A through both audio and chat and for those of you who would like to know and understand more, this should all be public soon. I trust that this is helpful and/or insightful. Jonathan

3 2

Proposed agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC.
by Glen de Saint Géry 18 Feb '14

18 Feb '14

Dear Councillors, Please find the proposed agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC. http://gnso.icann.org/en/meetings/agenda-council-27feb14-en.htm https://community.icann.org/display/gnsocouncilmeetings/Agenda+27+February+… There are no motions before Council this meeting. 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 11:00 UTC http://tinyurl.com/nkaf7dk Coordinated Universal Time 11:00 UTC 03:00 Los Angeles; 06:00 Washington; 11:00 London; 12:00 Brussels; 19:00 Perth 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. GNSO Council meeting audiocast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 mins) 1.1 Roll Call 1.2 Statement of interest updates Maria Farrell https://community.icann.org/display/gnsosoi/Maria+Farrell+SOI 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council meetings 23 January 2014<http://gnso.icann.org/en/meetings/minutes-council-23jan14-en.htm> were posted as approved on 17 February 2014. Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (0 mins) Item 4: Update - PDP Working Group on Translation & Transliteration of Contact Information (10 mins) The GNSO Council recently initiated a Policy Development Process<http://gnso.icann.org/en/basics/pdp-process.htm> (PDP) on the Translation and Transliteration of Contact Information. As part of its efforts to obtain broad input from the ICANN Community at an early stage of its deliberations, the Working Group has requested input from the Supporting Organizations (including the GNSO) and Advisory Committees on several questions relating to the issues identified in the PDP Final Issue Report. 4.1 - Update (Ching Chiao) 4.2 - Discussion 4.3 - Next steps Item 5: DISCUSSION - GNSO Engagement with the work of the ICANN Strategy Panels (15 mins) Here the Council will receive an update on any relevant interaction with and output from the strategy panels and discuss any appropriate action going forward. 5.1 - Status update 5.2 - Discussion 5.3 - Next steps Item 6: UPDATE - GAC Engagement - the work of the Joint GAC / GNSO Consultation Group (15 mins) Here the Council will receive an update and discuss any action going forward. 6.1 - Status update 6.2 - Discussion 6.3 - Next steps Item 7: Update - Forthcoming review of the GNSO (10 mins) As part of a periodic review process that is built into the ICANN model, ICANN board initiated reviews of the GNSO (and the GNSO Council and related functions) are expected. In order to be informed and effectively prepared for this work, we have begun to engage with the body that commissions such reviews (the structural improvements committee) through its chair, Ray Plazk. The Council will track the planning work of the SIC and, where appropriate; provide relevant input to the process. We will also prepare to undertake a form of self-review in a similar format to that which we expect to arise out of the work of the SIC. A self-review will ensure that we are not only prepared for the board initiated work but also able to flag areas for potential improvement in as timely as possible a manner. 7.1 - Update (Jennifer Wolfe) 7.2 - Discussion 7.3 - Next steps Item 8: DISCUSSION - International Internet Governance Issues (20 mins) Discussions and activity relating to international Internet Governance issues are attracting a great deal of attention in ICANN and related groups. This item is on the agenda to provide an opportunity for discussion within the Council about how this impacts the role and work of the Council and mindful of the scope and remit of the Council, what action the Council should or could be taking. Item 9: UPDATE & DISCUSSION - Planning for Singapore (15 mins) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, David Cake will lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council's proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board. 9.1 - Update (David Cake & Jonathan Robinson) 9.2 - Discussion 9.3 - Next steps Item 10: Any Other Business (10 mins) * Community budget requests * Proposed SSAC liaison to GNSO Council 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: 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 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 and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 11:00 ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 03:00 Iowa City, USA (CST<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+1DST 05:00 New York/Washington DC, USA (EST) UTC-4+1DST 06:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 08:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 09:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 08:00 London, United Kingdom (BST) UTC+0DST 11:00 Bonn, Germany (CET) UTC+1+0DST 12:00 Stockholm, Sweden (CET) UTC+1+0DST 12:00 Cairo, Egypt, (EET) UTC+2+0DST 13:00 Istanbul, Turkey (EEST) UTC+2+0DST 13:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 13:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 19:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2014, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/nkaf7dk Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

2 1

Statement from the I* Leaders Coordination Meeting, Santa Monica, 14 February 2014
by Glen de Saint Géry 14 Feb '14

14 Feb '14

https://www.icann.org/en/news/announcements/announcement-14feb14-en.htm Statement from the I* Leaders Coordination Meeting, Santa Monica, 14 February 2014 14 February 2014 Leaders of the organizations responsible for coordination of the Internet technical infrastructure (loosely referred to as "I* leaders") met last week in Santa Monica, California, USA. During the 2-day meeting, they discussed activities underway and exchanged views and updates on a range of topics including: · IETF and W3C efforts to improve overall Internet privacy and security (http://www.ietf.org & http://w3.org) · Globalization of the IANA functions (http://www.iana.org) · The 1net initiative, website and new collaboration forum (http://1net.org) · The "Netmundial" - Global Multistakeholder Meeting on the Future of Internet Governance (http://netmundial.br) · ICANN strategy panels and globalization efforts (http://www.icann.org<https://www.icann.org/>) · Preparations for the 2014 ITU Plenipotentiary Conference (http://www.internetsociety.org/plenipotbackground) · Web 25th anniversary and W3C 20th anniversary planning (http://w3.org) There was discussion of the significant progress and momentum that has developed since our last meeting, and as well as the need for continued engagement of all stakeholders in evolution of the Internet ecosystem. The leaders were encouraged by the progress made in many areas, and note that there is a lot of work happening in our respective communities, driven by the participants and handled with the usual community processes. The meeting also welcomed Kathy Brown, the incoming CEO of the Internet Society, and Carolina Aguerre as a representative of the ccTLD registry community. Participating I* Leaders - · Adiel A. Akplogan, CEO African Network Information Center (AFRINIC) · John Curran, CEO American Registry for Internet Numbers (ARIN) · Paul Wilson, Director General Asia-Pacific Network Information Centre (APNIC) · Russ Housley, Chair Internet Architecture Board (IAB) · Fadi Chehadé, President and CEO Internet Corporation for Assigned Names and Numbers (ICANN) · Jari Arkko, Chair Internet Engineering Task Force (IETF) · Kathy Brown, President and CEO Internet Society (ISOC) · Raúl Echeberría, CEO Latin America and Caribbean Internet Addresses Registry (LACNIC) · Axel Pawlik, Managing Director Réseaux IP Européens Network Coordination Centre (RIPE NCC) · Jeff Jaffe, CEO World Wide Web Consortium (W3C) · Carolina Aguerre, General Manager, LACTLD (association of ccTLD registry operators in Latin America and Caribbean) Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Qualified Launch Program for New gTLD Registries
by Glen de Saint Géry 14 Feb '14

14 Feb '14

https://www.icann.org/en/news/public-comment/qlp-addendum-13feb14-en.htm Qualified Launch Program for New gTLD Registries Comment / Reply Periods (*) Comment Open Date: 13 February 2014 Comment Close Date: 28 February 2014 - 23:59 UTC Reply Open Date: 1 March 2014 Reply Close Date: 15 March 2014 - 23:59 UTC Important Information Links Public Comment Announcement<https://www.icann.org/en/news/announcements/announcement-13feb14-en.htm> To Submit Your Comments (Forum)<mailto:comments-qlp-addendum-13feb14@icann.org> View Comments Submitted<http://forum.icann.org/lists/comments-qlp-addendum-13feb14/> Brief Overview Originating Organization: ICANN Categories/Tags: * Contracted Party Agreements * Intellectual Property * Top-Level Domains Purpose (Brief): As contemplated by the Trademark Clearinghouse Rights Protection Mechanism Requirements, a Qualified Launch Program may be developed. A draft of the Qualified Launch Program Addendum<http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements…> [PDF, 84 KB] (the "QLP Addendum") is being posted for comment to give the community an opportunity to review and provide feedback. Current Status: The draft QLP Addendum reflects ICANN's review and analysis regarding the feasibility of and implementation mechanics for a Qualified Launch Program as well as its potential impact on intellectual property rights. The Addendum is being posted to allow stakeholders to review and comment on the QLP Addendum. The public comment period is on an accelerated timeline to enable follow-up consideration so that if the QLP is adopted, as many new TLD operators as possible can take advantage of it. Next Steps: Public comment will be analyzed and taken into account by ICANN. If approved by ICANN following this process, the QLP Addendum will be automatically incorporated into the TMCH Requirements without any further action of ICANN or any Registry Operator. All Registry Operators will thereafter be permitted to have a Qualified Launch Program in accordance with the terms of the approved QLP Addendum, and will not need to seek ICANN's approval to implement the Qualified Launch Program. Staff Contact: Karen Lentz Email Staff Contact<mailto:karen.lentz@icann.org?subject=More%20information%20on%20the%20Qualified%20Launch%20Program%20for%20New%20gTLD%20Registries%20public%20comment%20period> Detailed Information Section I: Description, Explanation, and Purpose: Section 3.2 of Specification 5 of the gTLD Registry Agreement allows a Registry Operator to register up to 100 domain names to itself. Section 4.5.1 of the Trademark Clearinghouse Rights Protection Mechanism Requirements (the "TMCH Requirements") contemplated the possibility, subject to ICANN's further review and analysis, that Registry Operators could offer a "Qualified Launch Program" in which they could register these domain names to third parties for the purposes of promoting their TLDs. The Qualified Launch Program is intended to provide a mechanism for Registry Operators to register a limited number of names to third parties to promote their TLDs prior to the Sunrise period, while maintaining safeguards against intellectual property infringement. The draft is being published for comment to gather additional input from interested stakeholders. Section II: Background: Having conducted a review and analysis regarding the feasibility of and implementation mechanics for a Qualified Launch Program as well as its potential impact on intellectual property rights, ICANN has developed the attached QLP Addendum. If approved, the QLP Addendum will allow a Registry Operator to register some or all of the 100 domain names referenced in Section 3.2 of Specification 5 to third parties prior to the Sunrise Period for the TLD under certain conditions. Under the proposed QLP Addendum, if a domain name under a Qualified Launch Program does not match a label registered in the Trademark Clearinghouse (TMCH), the domain name may be registered in a Qualified Launch Program to any third party. On the other hand, if the domain name does match a label in the TMCH, the domain name may only be registered to a Sunrise-Eligible Rights Holder (as defined in the TMCH Requirements) in the Qualified Launch Program. In the case of geographic TLDs, names may also be registered to public authorities under the Qualified Launch Program, subject to certain requirements. Each domain name registered in a Qualified Launch Program will reduce the number of domain names available to a Registry Operator under Section 3.2 of Specification 5. Section III: Document and Resource Links: * TMCH Requirements<http://newgtlds.icann.org/en/about/trademark-clearinghouse/rpm-requirements…> [PDF, 167 KB] * Registry Agreement<http://newgtlds.icann.org/en/applicants/agb/agreement-approved-02jul13-en.p…> [PDF, 2.15 MB] Section IV: Additional Information: N/A ________________________________ (*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Second Accountability and Transparency Review Team (ATRT 2) Final Report & Recommendations
by Jonathan Robinson 14 Feb '14

14 Feb '14

All, If you are not already, please be aware of the following: http://www.icann.org/en/news/public-comment/atrt2-recommendations-09jan14-en .htm The opportunity to provide comments ends one week from today 23h59 UTC on 21 Feb 2014. The ATRT2 interacted with many in the community during the course of its work, including directly with the GNSO Council which was certainly appreciated. We now have an opportunity to comment on the final report. If we do intend to comment, my opinion is that we should at least submit an indication of intent, if not the primary comment, in the initial comment period and not wait for the reply period. Given the tight time frame, I have taken the unusual step of drafting a council response for your consideration. The ATRT2 deals with some critical areas of GNSO work and function and so it seems to me that we should respond to the call for comments, specifically in so far as the report deals with GNSO Policy and directly related areas. I am aware that some of you were on the ATRT2 and others actively worked on Council interaction with the ATRT2. Therefore, you may well have strong views on the subject matter. I look forward to your input and any suggestions. Thanks, Jonathan

1 0