[ispcp] Updated Proposed Agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC

["Mike O'Connor" <mike@xxxxxxxxxx>]

hi all,

here’s the current agenda for the Council meeting (11:00 UTC Thursday, 27-Feb) — there are no issues that require a vote, but please comment on anything that you would like Osvaldo and me to focus attention on during the discussion.  unfortunately, our next ISPCP call is scheduled a few days after this Council meeting, so we’ll have to have this conversation via the list.

thanks,

mikey



Begin forwarded message:

> From: Glen de Saint Géry <Glen@xxxxxxxxx>
> Subject: [council] Updated Proposed Agenda for the GNSO Council Teleconference 27 February 2014 at 11:00 UTC
> Date: February 20, 2014 at 4:09:37 PM CST
> To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
> 
> 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+2014
> 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 >
> 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 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 and Action List.
> 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 (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): 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.)
> ---------------------------------------------------------------------------- 
> Local time between October and March, Winter in the NORTHERN hemisphere 
> ---------------------------------------------------------------------------- 
> Reference (Coordinated Universal Time) UTC 11:00 
> ----------------------------------------------------------------------------
> California, USA (PDT) UTC-7+1DST 03:00 
> Iowa City, USA (CST)  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) UTC-2+1DST 09:00
> Buenos Aires, Argentina (ART) 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) UTC+2+0DST 13:00
> Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00 
> Perth, Australia (WST) 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@xxxxxxxxxxxxxx
> http://gnso.icann.org
>  


PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)