Proposed Agenda for the GNSO Council Teleconference on 19 March 2015 at 18:00 UTC

Last Updated: 18 March 2015
Date: 
19 March 2015

Proposed Agenda for the GNSO Council Meeting on 19 March 2015 at 18:00 UTC

This agenda was established according to the GNSO Council Operating Procedures, approved and updated on 13 November 2014.

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.

Please all note that on Sunday 08 March 2015, some countries (US) will have started using Daylight Saving Time, so please check on the link below to make sure you have the right meeting time!

Coordinated Universal Time: 18:00
http://tinyurl.com/omgtusy
11:00 Los Angeles; 14:00 Washington; 18:00 London; 19:00 Brussels; 02:00 Perth (next day)

GNSO Council Meeting Audio Cast

To join the event click on the link:
http://stream.icann.org:8000/gnso.m3u

Councilors should notify the GNSO Secretariat in advance if a dial out call is needed.

Item 1: Administrative matters (5 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 meeting of 11 February 2015 will be posted as approved on xxxx 2015.

Item 2: Opening Remarks / Review of Projects & Action List (10 mins)

2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action List.
2.2 - Comments or questions arising.

Item 3: Consent agenda (5 mins)

3.1 – Confirm selection of Privacy & Proxy Services Accreditation Issues (PPSAI) Working Group for facilitated face-to-face meeting at ICANN53 in Buenos Aires

Item 4: MOTION – GAC/GNSO Consultation Group (15 mins)

The GAC-GNSO Consultation Group (CG) was formed to develop proposals to facilitate the GAC's ability to engage more productively and effectively with the GNSO on relevant issues in the GNSO's Policy Development Processes (PDPs). At ICANN52 in Singapore, the CG presented its preliminary recommendations concerning specific mechanisms intended to facilitate early engagement by the GAC in a PDP, during the Issue Scoping phase. Here the Council will consider a proposed motion on adopting these preliminary recommendations from the CG on a trial basis.

4.1 – Presentation of Motion
4.2 – Discussion
4.3 – Vote

Item 5: DISCUSSION – Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (10 mins)

The CWG-Transition was chartered to develop a proposal on Naming Related Functions for the IANA Stewardship Transition Proposal. The original January 2015 target date was driven by the request for proposals from the IANA Stewardship Transition Coordination Group (ICG).

A draft proposal was published for community comment on 1 December 2014, following which a revised timeline and update was provided for discussion at ICANN52 in Singapore.

Given that the GNSO is a chartering organisation of the CWG-Transition and will need to approve the CWG's ultimate proposal, this is an opportunity for the Council to review and discuss the CWG's work and to determine what, if any, issues arise from a GNSO or Council perspective at this stage.

5.1 – Status summary (Jonathan Robinson)
5.2 – Discussion
5.3 – Next steps

Item 6: DISCUSSION - Cross Community Working Group on Enhancing ICANN Accountability (10 mins)

In discussions around the IANA stewardship transition process, the community raised the broader topic of the impact of the change on ICANN's accountability given its historical contractual relationship with the United States and NTIA. The community concerns indicate that the level of trust regarding existing ICANN accountability mechanisms does not yet meet some stakeholders' expectations. Considering that the NTIA has stressed that it expects community consensus on the transition, this gap between the current situation and stakeholder expectations could be a possible impediment to timely progress of the transition.

The GNSO is one of the chartering organizations for this CCWG, having adopted the charter in November 2014. The CCWG developed two work streams, of which the first is intended to align with the timing of the CWG-Transition work and the overall NTIA objectives and timeline. Here the Council will have the opportunity to consider how it can continue to facilitate the progress of this CCWG, especially in view of the work and timelines of the CWG-Transition.

6.1 Status summary (Thomas Rickert)
6.2 Discussion
6.3 Next steps

Item 7: UPDATE – Progress of the PDP Working Group on IGO-INGO Curative Rights Protections (10 mins)

This WG was chartered by the GNSO Council in June 2014 to consider whether or not existing curative rights protection mechanisms should be amended to address the needs and concerns of international governmental and non-governmental organizations (IGOs and INGOs). The WG's charter directed the WG to consider only those IGOs that appear on the GAC's list of protected IGOs (sent to ICANN in April 2013). Here the Council will receive a report on the progress of the WG, including a request for guidance from the WG as to appropriate next steps concerning the WG's consideration of the scope of the IGO list.

7.1 Status summary (Mason Cole/Mary Wong)
7.2 Discussion
7.3 Next steps

Item 8: UPDATE – Progress of the Discussion Group on New gTLD Subsequent Procedures (10 mins)

This DG was created by the GNSO Council in June 2014 to develop a list of issues for consideration as part of the GNSO's preparation for the next round of new gTLDs. The DG has also provided the GNSO Council with input for the Council's 28 January 2015 letter to the ICANN Board responding to the Board's enquiry concerning planning for the next round. Here the Council will receive an update from the DG on its further progress.

8.1 – Update (Bret Fausett / Steve Chan)
8.2 – Discussion
8.3 – Next steps

Item 9: UPDATE: GNSO Review (15 minutes)

The Independent Examiner commissioned by the ICANN Board to conduct the GNSO Review presented its initial findings to the GNSO Review Working Party at the ICANN 52 meeting in Singapore. Here the GNSO Council will discuss these findings and consider further direction (if any and if needed) to be provided to the GNSO Review Working Party.

9.1 Update – Jennifer Wolfe
9.2 Discussion

Item 10: DISCUSSION: Working Group Self-Assessment Survey (10 mins)

The GNSO's Working Group Guidelines allow a WG's chartering organization to request feedback from the WG about its inputs, processes and outputs. The GNSO's WG Self-Assessment Tool was tested by the Thick WHOIS PDP WG and the first formal survey has just been completed by the IRTP Part D PDP WG. Staff has prepared a report on the survey results. Here the Council will consider the feedback provided and appropriate next steps for this input.

10.1 Update (Lars Hoffman)
10.2 Discussion
10.3 Next steps

Item 11: DISCUSSION – Issues for Possible Referral to the SCI (5 minutes)

At its January 2015 meeting, the GNSO Council placed on hold two items it had identified previously as possibly meriting referral to the GNSO's Standing Committee for Improvements (SCI) for review. Following discussion with the SCI at ICANN52 in Singapore, the Council liaison to the SCI agreed to complete a template request form for these items. Here the Council will discuss whether or not to refer these items to the SCI for further work.

11.1 Update – Avri Doria/Mary Wong
11.2 Discussion

Item 12: DISCUSSION – Remaining Items from the GNSO's Strategic Discussion Session in Singapore (15 minutes)

At ICANN52 in Singapore, the GNSO engaged in an open and strategic discussion concerning the effective functioning of the GNSO Council and the community as a whole. Here the Council will aim to conclude the discussion, with the emphasis on reviewing its goals and performance based on the objectives and priorities identified during its Development Session at ICANN51 in Los Angeles in October 2014.

12.1 Update – Jonathan Robinson/Marika Konings
12.2 Discussion

Item 13: Any Other Business (5 mins)

13.1 – CWG on Auction Proceeds

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): 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)

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

Reference (Coordinated Universal Time) UTC 18:00
Local time between March and October, Summer in the NORTHERN hemisphere

---------------------------------------------------------

California, USA (PDT) UTC-7+1DST 11:00
San José, Costa Rica UTC-5+1DST 13:00
Iowa City, USA (CDT) UTC-5+1DST 13:00
New York/Washington DC, USA (EST) UTC-4+1DST 14:00
Rio de Janiero, Brazil (BRST) UTC-3+0DST 15:00
Montevideo, Uruguay (UYST) UTC-3+0DST 15:00
Buenos Aires, Argentina (ART) UTC-3+0DST 15:00
London, United Kingdom (BST) UTC+0DST 18:00
Bonn, Germany (CET) UTC+1+0DST 19:00
Cairo, Egypt, (EET) UTC+2+0DST 20:00
Istanbul, Turkey (EEST) UTC+2+0DST 20:00
Ramat Hasharon, Israel(IDT) UTC+3+0DST 20:00
Perth, Australia (WST) UTC+8+1DST 02:00 next day
Melbourne, Australia (AEDT) UTC+11+1DST 05:00 next day

---------------------------------------------------------

DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions)

---------------------------------------------------------

For other places see http://www.timeanddate.com
http://tinyurl.com/omgtusy