[council] Proposed Agenda for the GNSO Council Public Meeting on 11 February 2015 at 13:00 Singapore time
Glen de Saint Géry
Glen at icann.org
Wed Feb 4 11:31:13 UTC 2015
Please find the proposed Agenda for the GNSO Council Public Meeting on 11 February 2015 at 13:00 Singapore time (05:00 UTC)
This agenda was established according to the GNSO Council Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf>, approved and updated on 13 November 2014.
· 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 05:00 UTC:
Coordinated Universal Time 05:00 UTC
21:00 (10 February 2015) Los Angeles; 00:00 Washington; 05:00 London; 06:00 Brussels; 13:00 Singapore; 13:00 Perth
GNSO Council meeting
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 meetings 11 December 2014, 15 January 2015 and 29 January 2015 will be posted as approved on 14 February 2015.
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: DISCUSSION - Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (15 mins)
The CWG<https://community.icann.org/x/37fhAg> 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<https://www.icann.org/stewardship/coordination-group> (ICG).
A draft proposal was published for community comment on 1 December 2014. The CWG conducted an intensive work weekend on 10 & 11 January 2015, following which a revised timeline and update was provided to the community in the form of a Discussion Document<https://community.icann.org/download/attachments/49351404/CWG-SingaporeDiscussionDocument-Final.pdf?version=1&modificationDate=1422998880000&api=v2>. This was discussed by the GNSO at its weekend working session in Singapore.
Given the deadlines and associated intensity of the work of the CWG as well as the need for the GNSO as a chartering organisation to approve the CWG's ultimate proposal, this is an opportunity for the Council to discuss its and the GNSO community's further tasks following the GNSO's weekend deliberations on the updated CWG plan and timeline.
4.1 - Status summary (Jonathan Robinson)
4.2 - Discussion
4.3 - Next steps
Item 5: DISCUSSION - Cross Community Working Group on Enhancing ICANN Accountability (15 mins)
The National Telecommunications and Information Administration (NTIA) had requested that ICANN "convene a multistakeholder process to develop a plan to transition the U.S. government stewardship role" with regard to the IANA Functions and related root zone management (see item 4 above).
During discussions around the 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 concerns raised during these discussions 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 may impede the progress of the transition.
The charter<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en.pdf> for this CCWG was adopted by the GNSO Council during its meeting on 13 November. The group has been meeting regularly since, and has 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. Following the weekend update to the GNSO from the group's co-chairs and further discussions with the ICANN Board and other stakeholders, the Council will now consider how it might facilitate the continued progress of this CCWG, especially in view of the work and timelines of the CWG working on an IANA Transition Proposal for Naming-related Functions.
5.1 Status summary (Thomas Rickert)
5.3 Next steps
Item 6: DISCUSSION - Progress toward Launching the Pending PDP on the Purpose of gTLD Registration Data (WHOIS) (15 mins)
An ICANN Board and GNSO Discussion Group was formed to develop recommendations on how to best effect next steps in the Board-mandated GNSO PDP on the purpose of WHOIS (including taking into account the work of the Expert Working Group). This group has been meeting regularly. An update on the group's progress was provided to the GNSO during its working weekend at this meeting. Following that session and in light of other WHOIS-related work going on in the community, the Council will discuss here the options and timing for conducting the PDP.
6.1 Status summary (Jonathan Robinson/Susan Kawaguchi)
6.3 Next steps
Item 7: UPDATE - GNSO / GAC Consultation Group and related work (10 mins)
The GNSO/GAC Consultation Group released its initial recommendations regarding the scoping of a Policy Development Process (PDP) in late January 2015. In addition, the GNSO Liaison to the GAC has been actively engaging with the GAC on questions and issues arising from the GAC Communique in Los Angeles insofar as these had implications for ongoing GNSO Working Groups.
Here the Council will consider the recommendations from the GNSO/GAC Consultation Group, taking into account feedback received from the community during meetings earlier in the week and with a view toward voting on a motion at the next Council meeting. If time permits, the Council will also discuss ideas put forward during the GNSO Council Development Session in Los Angeles, in relation to potential GNSO responses to the regular GAC Communiqués from each ICANN meeting.
7.1 - Update on GAC/GNSO Consultation Group (Mason Cole)
7.2 - Discussion
7.3 - Next steps
Item 8: DISCUSSION: Potential CWG for Use of Auction Proceeds from New gTLD Auctions (15 mins)
The Council has commenced deliberations on whether and when to convene a Cross-Community Working Group to develop suggestions on ways to best use the proceeds received by ICANN from new gTLD auctions. Having received initial feedback from the GNSO community on this potential idea (including at the GNSO weekend working session), the Council will now consider whether and, if so, how to move forward with an initiative to convene such a CWG.
8.1 Update - Jonathan Robinson
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 this ICANN meeting. This will be the first opportunity that the GNSO Council will have to discuss these findings and to consider further direction (if any and if needed) to be provided to the GNSO Review Working Party.
9.1 Update - Jennifer Wolfe
Item 10: ccNSO Update (10 minutes)
At most ICANN meetings, the ccNSO and GNSO Councils conduct joint meetings to discuss matters of mutual interest, an initiative that continues to grow in importance as collaborations between the two SOs increase. Here the ccNSO Council liaison to the GNSO will be invited to update the GNSO Council on ongoing work in the ccNSO that is likely to be of interest or that may impact the work of the GNSO and/or its Stakeholder Groups and Constituencies.
10.1 Update - Patrick Myles
Item 10: Any Other Business (10 mins)
10.1 Summary of Upcoming Important Dates and Milestones for GNSO Working Groups
- Jonathan Robinson/Marika Konings
10.2 Any other business
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>)
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 05:00
Local time between October and March, Winter in the NORTHERN hemisphere
California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+0DST 21:00 (10 February 2015)
San José, Costa Rica UTC-6+0DST 23:00 (10 February 2015)
Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+0DST 23:00 (10 February 2015)
New York/Washington DC, USA (EST) UTC-5+0DST 00:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 03:00
Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 03:00
London, United Kingdom (BST) UTC+0DST 05:00
Bonn, Germany (CET) UTC+1+0DST 06:00
Cairo, Egypt, (EET) UTC+2+0DST 07:00
Istanbul, Turkey (EEST) UTC+2+0DST 07:00
Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>) UTC+3+0DST 07:00
Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 13:00
Singapore (SGT) UTC+8+0DST 13:00
Melbourne, Australia (AEDT) UTC+11+1DST 16:00
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
Let me know if you have any questions.
Glen de Saint Géry
gnso.secretariat at gnso.icann.org<mailto:gnso.secretariat at gnso.icann.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the council