[council] Proposed Agenda for the GNSO Council Public Meeting on 24 June 2015 at 13:00 ART (16:00 UTC)

[Glen de Saint Géry <Glen@xxxxxxxxx>]

Dear Councillors,

Please find the proposed Agenda for the GNSO Council Public Meeting on 24 June 
2015 at 13:00 ART (16:00 UTC)
https://community.icann.org/display/gnsocouncilmeetings/Agenda+24+June+2015
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.

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.

Coordinated Universal Time: 16:00 UTC
http://tinyurl.com/oqlv22k

09:00 Los Angeles; 12:00 Washington; 13:00 Buenos Aires; 17:00 London; 18:00 
Brussels; 00:00 Perth

http://buenosaires53.icann.org/en/schedule/wed-gnso-council
Councilors should notify the GNSO Secretariat in advance if they will be absent 
and if a dial out call is needed.
___________________________________

Item 1: Administrative matters (5 mins)
1.1 - Roll call
1.2 - Updates to Statements of Interest
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, 19 March,16 April, 21 May 
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<http://gnso.icann.org/meetings/projects-list.pdf> and Action 
List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>
2.2 - Comments or questions arising

Item 3: Consent agenda (0 mins)


Item 4: COUNCIL VOTE - Adoption of Final Report and Recommendations from the 
Policy & Implementation Working Group (10 mins)



The GNSO Council 
chartered<http://gnso.icann.org/en/drafts/policy-implementation-charter-04jul13-en.pdf>
 Working Group in July 2013 to develop recommendations on, among other matters, 
principles to underpin GNSO policy- and implementation-related discussions; 
processes and criteria for developing gTLD policy guidance (for creating policy 
other than "Consensus Policy"); and guidance on the operation and functions of 
GNSO Implementation Review Teams. The WG submitted its Final 
Report<http://gnso.icann.org/en/drafts/policy-implementation-recommendations-01jun15-en.pdf>
 to the GNSO Council on 2 June 2015. Here the Council will vote on whether to 
adopt the WG's Final Report and the recommendations contained therein.



4.1 - Presentation of the 
motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+24+June+2015>
 (Amr Elsadr)

4.2 - Discussion

4.3 - Council vote





Item 5: COUNCIL VOTE - Adoption of Final Report and Recommendations from the 
Translation & Transliteration of gTLD Contact Information PDP Working Group (10 
mins)



The GNSO Council initiated<http://gnso.icann.org/en/council/resolutions#201306> 
this PDP in June 2013, and the WG was 
chartered<http://gnso.icann.org/en/issues/gtlds/transliteration-contact-charter-20nov13-en.pdf>
 in November 2013 to develop policy recommendations on whether or not it would 
be desirable to translate or transliterate gTLD contact information into a 
single common language or script (as applicable), and if so who should bear the 
cost burden of doing so. The PDP WG submitted its Final 
Report<http://gnso.icann.org/en/issues/gtlds/translation-transliteration-contact-final-12jun15-en.pdf>
 to the GNSO Council on 12 June 2015. Here the Council will vote on whether to 
adopt the WG's Final Report and the recommendations contained therein.



5.1 - Presentation of the motion<https://community.icann.org/x/l4kQAw> (Amr 
Elsadr)

5.2 - Discussion

5.3 - Council vote





Item 6: COUNCIL VOTE - Issue Report Preceding a Potential Policy Development 
Process on New gTLDs in Subsequent Rounds (15 mins)



The GNSO Council created<http://gnso.icann.org/en/council/resolutions#201406> a 
New gTLDs Subsequent Rounds Discussion Group in June 2014 to discuss 
experiences gained during the current expansion round of new gTLDs, and 
identify possible subjects for future policy work that might result in changes 
to application procedures. The Discussion Group co-chairs notified the Council 
at the Council's May meeting that the Group has completed its 
Issues/Recommendations Matrix and would be recommending that the Council 
request an Issue Report - a mandatory step preceding a possible Policy 
Development Process (PDP) - to further scope out the topics that have been 
identified by the Discussion Group as potential issues for a PDP.



6.1 - Presentation of the 
motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+24+June+2015>
 (Bret Fausett)

6.2 - Discussion

6.3 - Council vote



Item 7: COUNCIL VOTE - Proposal from the Cross Community Working Group 
regarding the transition of IANA stewardship on naming related functions (20 
mins)
The GNSO is one of the chartering organizations for the Cross Community Working 
Group that was tasked<https://community.icann.org/x/2grxAg> to develop a 
proposal on Naming Related Functions for the IANA Stewardship Transition 
(CWG-Stewardship). A draft proposal was published for community comment on 1 
December 2014, with a revised timeline and update provided for discussion at 
ICANN52 in Singapore. The CWG-Stewardship's updated proposal was subsequently 
published<https://www.icann.org/public-comments/cwg-stewardship-draft-proposal-2015-04-22-en>
 for public comment (ending on 20 May), following which its final draft 
proposal<../AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/Content.Outlook/BTHAHPWK/FinalTransitionProposal_11June.docx>
 was submitted on 11 June 2015 to all its chartering SO/ACs for discussion 
during ICANN53. The aim is that an approved final proposal will then be 
submitted to the IANA Stewardship Coordination Group (ICG) for consolidation 
with the other proposals from the Numbering Resources and Protocol Parameters 
communities, for submission to the NTIA.
As a chartering organization of the CWG-Stewardship the GNSO will need to 
approve the group's final proposal. Here the Council will review the GNSO 
community's deliberations on the issue, and vote on whether or not to adopt the 
final proposal, which is conditional on the completion and adoption of the work 
on Work Stream I from the CCWG-Accountability (see further below).
7.1 - Presentation of the 
motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+24+June+2015>
 (Jonathan Robinson)
7.2 - Discussion
7.3 - Council vote
Item 8: DISCUSSION FOR POTENTIAL ACTION - Cross Community Working Group on 
Enhancing ICANN Accountability - CCWG Accountability (20 mins)
In discussions around the IANA stewardship transition, the broader topic of the 
impact on ICANN's accountability was raised, given ICANN's historical 
contractual relationship with the United States government. The community 
concerns indicated that existing ICANN accountability mechanisms do not yet 
meet some stakeholders' expectations. Considering that the US Government 
(through the NTIA) has stressed that it expects community consensus on the 
transition, this gap between the current situation and stakeholder expectations 
needed to be addressed. This has been done through the 
charter<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en.pdf>ing
 of a Cross Community Working Group on Enhancing ICANN Accountability - 
CCWG-Accountability<https://community.icann.org/x/ogDxAg>, of which the GNSO is 
a chartering organization.
The CCWG-Accountability developed two work streams, of which Work Stream 1 is 
intended to align with the timing of the CWG-Transition work and the overall 
NTIA objectives and timeline. Initial proposals for Work Stream 1 were 
published<https://www.icann.org/public-comments/ccwg-accountability-draft-proposal-2015-05-04-en>
 for public comment on 4 May 2015, with comments closing on 3 June. The 
CCWG-Accountability is reviewing all public comments received, and will conduct 
a face-to-face meeting on 17 & 18 July. Here the Council will review the CCWG's 
work to date and to discuss what, if any, issues will need to be addressed by 
the GNSO or Council at this critical stage.

8.1 - Summary and status update (Thomas Rickert)
8.2 - Discussion
8.3 - Next steps


Item 9: DISCUSSION - Community Concerns over ICANN's Response to the IPC 
Request regarding the "dotsucks" Registry (10 mins)



Some GNSO community groups have raised with the Council their concerns over 
ICANN's handling of the Intellectual Property Constituency's (IPC) 
letter<http://gnso.icann.org/mailing-lists/archives/council/pdfd7ImDr4QkG.pdf> 
of 27 March 2015 requesting that ICANN take action to halt the rollout of the 
"dotsucks" gTLD. Here the Council will hear from affected community members and 
discuss what, if any, action the Council can take to follow up on those 
concerns.



9.1 - Summary of the topic (Susan Kawaguchi)

9.2 - Discussion

9.3 - Next steps





Item 10: COUNCIL ACTION - GNSO Drafting Team on New ICANN Meeting Strategy (10 
mins)
Following initial Council discussions on planning GNSO-related meetings at 
ICANN Public Meetings after implementation of the new ICANN meeting strategy, a 
Drafting Team comprising several Council members was created to develop an 
initial 
proposal<http://gnso.icann.org/en/drafts/gnso-council-proposal-new-meeting-strategy-29apr15-en.pdf>
 for GNSO community discussion. The proposal has since been circulated to other 
SO/ACs for their consideration and feedback, in the hope that it would assist 
these groups with planning, especially in relation to their interactions with 
the GNSO and for Meeting "B". Here the Council will consider any feedback 
received from the community, and decide on next steps with implementing the 
GNSO planning proposal.


10.1 - Update (Volker Greimann / Marika Konings)

10.2 - Discussion

10.3 - Next steps


Item 11: Any Other Business (5 mins)


Item 12: Open microphone (5 mins)

_____________________________

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.)
Reference (Coordinated Universal Time) UTC 16:00
Local time between March and October, Summer in the NORTHERN hemisphere
----------------------------------------------------------------------------
California, USA 
(PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) 
UTC-7+1DST 09:00
San José, Costa Rica UTC-5+1DST  11:00
Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 
11:00
New York/Washington DC, USA (EST) UTC-4+1DST 12:00
Rio de Janiero, Brazil (BRST) UTC-3+0DST 13:00
Montevideo, Uruguay 
(UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) 
UTC-3+0DST 13:00
Buenos Aires, Argentina 
(ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) 
UTC-3+0DST 13:00
London, United Kingdom (BST) UTC+0DST 17:00
Bonn, Germany (CET) UTC+1+0DST 18:00
Cairo, Egypt, (EET) UTC+2+0DST 18:00
Istanbul, Turkey (EEST) UTC+3+0DST 19:00
Ramat Hasharon, 
Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
 UTC+3+0DST 19:00
Perth, Australia 
(WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) 
UTC+8+1DST 00:00 Thursday
Sydney/Hobart, Australia (AEDT) UTC+11+1DST 02:00 Thursday
----------------------------------------------------------------------------
DST starts/ends on last Sunday of October 2015, 2:00 or 3:00 local time (with 
exceptions)
----------------------------------------------------------------------
For other places see http://www.timeanddate.com
http://tinyurl.com/oqlv22k