[council] Draft GNSO Council Public Meeting Buenos Aires Agendas 20 November 2013

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

Dear Councillors,

Please find the draft agendas for the GNSO Council Public meetings in Buenos 
Aires. The Public meeting will be in two parts, part one in  Libertador AB at 
13:00ART, (16:00UTC) and the second Administrative part in Retiro B at 15:00ART 
(18:00UTC)

http://buenosaires48.icann.org/en/schedule/wed-gnso-council
https://community.icann.org/display/gnsocouncilmeetings/Agenda+20+November+2013
Proposed Agenda for the GNSO Council Public Meeting in Buenos Aires, 20 
November 2013 Part 1
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 16:00 UTC
http://tinyurl.com/oby4lzl

Coordinated Universal Time 16:00 UTC
08:00 Los Angeles; 11:00 Washington; 13:00 Buenos Aires; 16:00 London; 17:00 
Paris; 05:00 Wellington next day

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.

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 meeting 31 October 2013 will be posted as approved 
on 21 November 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<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 (5 mins)
Item 4: MOTION - To approve a charter for the Translation and Transliteration 
of Contact Information PDP Working Group (10 mins)
On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) 
on the Translation and Transliteration of Contact Information and decided to 
create a PDP Working Group for the purposes of fulfilling the requirements of 
the PDP.  Following a call for volunteers, a Drafting Team was formed and its 
members have developed a charter for consideration by the GNSO Council.  The 
drafting team has submitted the charter, reviewed and revised it on the request 
of the Council and then re-submitted it and so the GNSO Council, having 
reviewed the charter, will vote on whether to approve it as submitted by the 
Drafting Team.
4.1 - Review Motion 1
https://community.icann.org/display/gnsocouncilmeetings/Motions+20+November+2013
4.2 - Discussion
4.3 - Next steps
Item 5: MOTION - To approve the Recommendations for IGO-INGO Protections (20 
mins)

On 20 September 2013 the WG published its Draft Final 
Report<http://gnso.icann.org/en/issues/igo-ingo-final-20sep13-en.pdf> which 
includes policy recommendations for the protection of IGO and INGO (including 
the RCRC and IOC) identifiers in all gTLDs. Each recommendation or proposal 
also contains the WG's Chair assessment of consensus. The objective of the 
Draft Final Report was to solicit feedback from the community on the proposed 
consensus policy recommendations. The comment period closed 1 November 2013. 
The WG has reviewed the public comments and modified the Final Report.  The 
GNSO Council will consider this Final Report and vote on whether to approve the 
recommendations contained therein.
5.1 - Review Motion 2
https://community.icann.org/display/gnsocouncilmeetings/Motions+20+November+2013
5.2 - Discussion
5.3 - Next steps
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<http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf> 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.  Further work needs to be done on reviewing the table and agreeing 
concrete next steps.
6.1 - Review of table of prospective PDP 
Improvements<http://gnso.icann.org/en/drafts/pdp-improvements-table-23sep13-en.pdf>
 (Marika Konings)
6.2 - Discussion
6.3 - Next steps
Item 7: DISCUSSION - Forthcoming reviews of the GNSO and GNSO Council (15mins)

As part of a periodic review process that is built into the ICANN model, board 
initiated reviews of the GNSO and the GNSO Council as an integral part of the 
GNSO are expected.  In order to be effectively prepared for these reviews, it 
was originally proposed in Beijing that a group be formed to understand the 
issues and begin to take appropriate next steps.  One key suggestion from 
Beijing was that any group (such as the Council) being reviewed undertakes a 
form of self-review.  The intended course of action was impacted by the board 
deliberations on whether or not to proceed with the review and, more recently, 
what format the review might follow.  The Council will receive an update during 
its meeting with the board in Buenos Aires and this item provides an 
opportunity to discuss and agree the intended course of action.
7.1 - Current status
7.2 - Discussion
7.3 - Next steps
Item 8:  Thanks to outgoing councillors (5 mins)


 *   Lanre Ajayi (NCA)
 *   Mason Cole (RySG & Vice Chair)
 *   Zahid Jamil (CSG / BC)
 *   Wolf-Ulrich Knoben (CSG / ISPC & Vice Chair)
 *   Joy Liddicoat (NCSG)
 *   Wendy Seltzer (NCSG)

Item 9:  Any Other Business (5 mins)

Item 10: Open microphone

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.)
----------------------------------------------------------------------------
Local time between October and March, Winter in the NORTHERN hemisphere
----------------------------------------------------------------------------
Reference (Coordinated Universal Time) UTC 16:00
----------------------------------------------------------------------------
California, USA 
(PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) 
UTC-7+1DST 08:00
New York/Washington DC, USA (EST) UTC-4+1DST 11:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 14:00
Montevideo, Uruguay 
(UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) 
UTC-2+1DST 14: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 16:00
Bonn, Germany (CEST) UTC+1+0DST 17:00
Stockholm, Sweden (CET) UTC+1+0DST 17:00
Istanbul, Turkey (EEST) UTC+2+0DST 18:00
Ramat Hasharon, 
Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
 UTC+2+0DST 18:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 00:00 (next day)
Perth, Australia 
(WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) 
UTC+8+0DST 00:00 (next day)
Wellington, New Zealand  UTC+12+1DST 05:00 (next day)
----------------------------------------------------------------------------
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

http://buenosaires48.icann.org/en/schedule/wed-gnso-council-admin
https://community.icann.org/display/gnsocouncilmeetings/Aministrative+Agenda-20-11-2013
Proposed Agenda for the GNSO Council Public Meeting in Buenos Aires, 20 
November 2013 Part 2

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

Coordinated Universal Time 18:00 UTC
10:00 Los Angeles; 13:00 Washington; 15:00 Buenos Aires; 18:00 London; 19:00 
Paris;

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.

Item 1: Seating of the 2013 / 2014 Council (10 mins)

1.1  Roll Call

1.2  Statements of interest

·       James Bladel - 
SOI<https://community.icann.org/display/gnsosoi/James+M.+Bladel+SOI>  
Registrars Stakeholder Group

·       Gabriela Szlak - 
SOI<https://community.icann.org/display/gnsosoi/Gabriela+Szlak+SOI> Commercial 
and Business Users Constituency

·       Mikey O'Connor - 
SOI<https://community.icann.org/display/gnsosoi/Mikey+O%27Connor+SOI> Internet 
Service Providers & Connectivity Providers

·       Amr Elsadr - 
SOI<https://community.icann.org/display/gnsosoi/Amr+Elsadr+SOI> Non Commercial 
Stakeholder Group

·       Avri Doria - 
SOI<https://community.icann.org/display/gnsosoi/Avri+Doria+SOI> Stakeholder 
Group

·       Daniel Reed - SOI  Nominating Committee Appointee

1.3  Review/amend agenda

Item 2: Election of the Chair (10 mins)

One nomination was received for this position, Jonathan Robinson.  The GNSO 
Council held a question & answer session over the weekend with Jonathan 
Robinson. The Council to proceed to elect the chair according to the GNSO 
Operating Procedures.

GNSO Operating Procedures

http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf

Note: Section 2.2 Officer Elections: Chair and Vice-Chairs (see Appendix 1 
below)
Item 3: UPDATE & DISCUSSION - Meeting with the ATRT2 (40 mins)
3.1 - Update
3.2 - Discussion
3.3 - Next steps
Item 4:  Any Other Business (5 mins)

Reminder:
Council development meeting. Friday 22 November 2013, 10h00 Buenos Aires.

Appendix 3: Excerpt from GNSO Operating Procedures (Section2.2)

http://gnso.icann.org/en/council/gnso-operating-procedures-13sep12-en.pdf

2.2 Officer Elections: Chair and Vice-Chairs

The GNSO Council shall select the GNSO Chair and two Vice-Chairs as follows:

a.     The GNSO Chair shall be elected by a 60 percent vote of each house.

b.     Each house will be allowed to nominate one candidate for GNSO Council 
Chair. Each house is responsible for determining how to nominate its candidate. 
A candidate for GNSO Council Chair does not need to be a member of a house, but 
must be a member of the GNSO Council. Should a Chair be elected from outside of 
the houses that Chair will be a non-voting Chair.

                           i.          All ballots will include the "none of 
the above" option. In the event that a 60 percent vote of each house selects 
the "none of the above" option, each house will commence a new nomination 
period of not longer than 15 days. An election for the new nominees will be 
scheduled for no sooner than 30 days after the unsuccessful vote.

                          ii.          In the case of a tie for the most votes 
between the two candidates, or between a candidate and "none of above," a 
second election will be held no sooner than 30 days. The candidates shall 
remain the same for this second election. In the case this second election also 
results in a tie, each house will commence a new nomination period of not 
longer than 15 days. An election for the new nominees will be rescheduled for 
no sooner than 30 days after the unsuccessful vote.

                        iii.          The leading candidate will be defined as 
the one with the highest score. The score is calculated by adding together the 
voting percentages attained from each house. The highest percentage attainable 
in each house is 100. Thus, the maximum score a candidate can achieve is 200 as 
a result of attaining 100 percent of the votes from the contracted party house 
and 100 percent from the non-contracted party house (100 percent + 100 percent 
= score of 200). In case neither candidate reaches the 60 percent of each house 
threshold, a second ballot will be held between the leading candidate and "none 
of the above."

                        iv.          In case neither candidate reaches the 60 
percent of each house threshold and the candidates do not tie, a second runoff 
ballot will be held between the leading candidate and "none of the above."

                         v.          If the single candidate does not reach the 
60 percent of each house threshold in the runoff ballot, then each house will 
commence a new nomination period of not longer than 15 days. An election for 
the new nominees will be rescheduled for no sooner than 30 days after the 
unsuccessful runoff ballot.

c.     Each house shall select a Council Vice-Chair from within its respective 
house.

d.     A Chair may not be a member of the same Stakeholder Group of either of 
the Vice-Chairs.

e.     The Chair and Vice-Chairs shall retain their votes (if any) in their 
respective houses (if any).

f.      In the event that the GNSO Council has not elected a GNSO Council Chair 
by the end of the previous Chair's term, the Vice-Chairs will serve as Interim 
GNSO Co-Chairs until a successful election can be held.

g.     The Council shall inform the Board and the Community appropriately and 
post the election results on the GNSO website within 2 business days following 
each election and runoff ballot, whether successful or unsuccessful.
Appendix 2: 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 3: 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.)
----------------------------------------------------------------------------
Local time between October and March, Winter in the NORTHERN hemisphere
----------------------------------------------------------------------------
Reference (Coordinated Universal Time) UTC 18:00
----------------------------------------------------------------------------
California, USA 
(PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) 
UTC-7+1DST 10:00
Iowa City, USA (CST<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>)  
UTC-6+1DST 12:00
New York/Washington DC, USA (EST) UTC-4+1DST 13:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 16:00
Montevideo, Uruguay 
(UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) 
UTC-2+1DST 16:00
Buenos Aires, Argentina 
(ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) 
UTC-3+0DST 15:00
London, United Kingdom (BST) UTC+0DST 18:00
Bonn, Germany (CEST) UTC+1+0DST 19:00
Stockholm, Sweden (CET) UTC+1+0DST 19:00
Istanbul, Turkey (EEST) UTC+2+0DST 20:00
Ramat Hasharon, 
Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
 UTC+2+0DST 20:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 02:00 (next day)
Perth, Australia 
(WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) 
UTC+8+0DST 02:00 (next day)
----------------------------------------------------------------------------
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/posr6mw



Glen de Saint Géry
GNSO Secretariat
gnso.secretariat@xxxxxxxxxxxxxx<mailto:gnso.secretariat@xxxxxxxxxxxxxx>
http://gnso.icann.org<http://gnso.icann.org/>