Proposed Agenda for the GNSO Council Teleconference 12 December 2013

Last Updated: 6 December 2013
Date: 
12 December 2013

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 15:00 UTC
http://tinyurl.com/mlhk5kr

Coordinated Universal Time 15:00 UTC
07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Paris; 23: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
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 20 November 2013 will be posted as approved on xxxxxxxxxxxx 2013

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 and Action List.

Comments or questions arising.

Item 3: Consent agenda (5 mins)

  • Transmit the GNSO Council recommendations on Thick Whois GNSO to the ICANN Board

Item 4: MOTION – JIG Final Report on Universal Acceptance of IDN TLDs

The purpose of the joint ccNSO/GNSO Joint IDN Working Group (JIG) is to deal with issues related to the introduction of IDN ccTLDs under the IDN ccTLD Fast Track implementation process and with IDN gTLDs under the new gTLD implementation process which are of common interest to both the GNSO and ccNSO.

The JIG was formed by mutual charters between the ccNSO and GNSO councils  and then extended (ccNSO: http://ccnso.icann.org/workinggroups/minutes-council-23aug11-en.pdf | GNSO: http://gnso.icann.org/resolutions/#201107) to complete its work on the three identified issues of common interest between the ccNSO and GNSO. One of the three issues relates to the Universal Acceptance of IDN TLDs.

The JIG has delivered its Final Report on Universal Acceptance of IDN TLDs on 17 November for GNSO Council consideration. Here the GNSO will consider a motion to accept the Final Report.

4.1 – Review Motion 1
4.2 – Discussion
4.3 – Next steps
4.4 – Vote (voting threshold – simple majority vote of each house)

Item 5: MOTION – DNS Security and Stabilty and Analysis (DSSA) Working Group Final Report

In December 2010, the ALAC, ccNSO, GNSO and NRO (acting as ASO in this case) all endorsed the charter of the joint DNS Security and Stability and Analysis working group (DSSA WG) according to each of their own rules and procedures and as a result are the participating SO's and AC's in the DSSA.

The DSSA delivered its Final Report to the chartering organisations on 11 November 2013. Here, the GNSO Council will vote on adopting the Final Report of the DSSA as well as other related actions contained in the motion.

5.1 – Review Motion 2
5.2 – Discussion
5.3 – Next steps
5.4 – Vote (voting threshold – simple majority vote of each house)

Item 6: INPUT & DISCUSSION – Prospective improvements to the Policy Development Process (15 mins)

The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community. The Council has previously discussed a paper prepared by ICANN staff on potential improvements to the PDP process. The discussion is now encapsulated in a table form and now includes reference to the related recommendations of the ATRT2. Here the Council will discuss the table and aim to agree on concrete next steps.

6.1 – Review of table of prospective PDP Improvements (Marika Konings)
6.2 – Discussion
6.3 – Next steps

Item 7: DISCUSSION – Written final input to the ATRT2 (15 mins)

The Second Accountability and Transparency Review Team (ATRT 2), mandated by paragraph 9.1 of the Affirmation of Commitments (AoC), is completing its analysis and holding consultations with Community, staff and Board. To fully inform its work, the ATRT 2 seeks input from the Community on its Draft Report & Recommendations (and the Correction Issued 7 November 2013) compiled for the Community's consideration. Community participation is essential to the success of the review, and all input will be carefully considered. The ATRT 2 welcomes any additional feedback by 13 December 2013, with the goal of producing final recommendations by 31 December 2013.

Here the Council will confirm what written feedback, if any, it intends to provide in advance of the 13 December 2013 deadline.

7.1 – Discussion
7.2 – Next steps

Item 8: DISCUSSION – Geographic Regions Review Working Group (15 mins)

The Geographic Regions Review Working Group was formed by the ICANN Board to (1) identify the different purposes for which ICANN's Geographic Regions are used; (2) determine whether the uses of ICANN's Geographic Regions (as currently defined, or at all) continue to meet the requirements of the relevant stakeholders; and (3) submit proposals for community and Board consideration relating to the current and future uses and definition of the ICANN Geographic Regions. A full record of the Working Group's past reports and public workshops and presentations can be found at the Working Group's Confluence Wiki space.

At various times over the past few years, the ALAC, ASO, ccNSO, GAC and GNSO communities have supplied representatives to serve on the Working Group. These communities have had the opportunity to review and provide formal comments on the Working Group's recommendations before being submitted to the ICANN Board. The recommendations are provided a Final Report which is posted here.

The Chair of the working group has now written to the GNSO indicating that the charter of the Working Group, as approved by the ICANN Board, requires that the Chair receive written notification (by 31 December if possible) from each of the organisations that contributed members to the Working Group before the Final Report can be submitted formally to the ICANN Board. The form of the notification could support, oppose or take no position on the recommendations of the working group. Here the Council will decided what form of notification to provide to the working group.

8.1 – Discussion
8.2 – Next steps

Item 9: Any Other Business (5 mins)

  • Liason to SCI (Outstanding)
  • Liason to Policy & Implementation WG (replace Jeff Neumann)

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 one-fourth (1/4) 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 one-third (1/3) of each House or more than two-thirds (2/3) of one House.

  3. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority.

  4. 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.

  5. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority.

  6. 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.

  7. 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.

  8. 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.

  9. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority,

  10. 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.

  11. 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.

  12. 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)
4.4.1 Applicability
Absentee voting is permitted for the following limited number of Council motions or measures.

  1. Initiate a Policy Development Process (PDP);
  2. Approve a PDP recommendation;
  3. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws;
  4. 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 15:00
----------------------------------------------------------------------------
California, USA (PDT) UTC-7+1DST 07:00
Iowa City, USA (CST)  UTC-6+1DST 09:00
New York/Washington DC, USA (EST) UTC-4+1DST 10:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 13:00
Montevideo, Uruguay (UYST) UTC-2+1DST 13:00
Buenos Aires, Argentina (ART) UTC-3+0DST 12:00
London, United Kingdom (BST) UTC+0DST 15:00
Bonn, Germany (CEST) UTC+1+0DST 16:00
Stockholm, Sweden (CET) UTC+1+0DST 16:00
Istanbul, Turkey (EEST) UTC+2+0DST 17:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 17:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 23:00
Perth, Australia (WST) UTC+8+0DST 23: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/oby4lzl