[council] Updated proposed Council agenda for Thursday, 24 July 2014 at 11:00UTC

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

Dear All,
Please find the updated proposed Council agenda for Thursday, 24 July 2014 at 
11:00UTC. The  agenda has been updated with the addition of an item under Any 
Other Business, namely:
10.1 Council development meeting Friday, 17 October 2014 in Los Angeles

Please let me know if you have any questions.
Thank you,
Kind regards,
Glen
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/lwky9he
Coordinated Universal Time 11:00 UTC
04:00 Los Angeles; 07:00 Washington; 12:00 London; 13: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 (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 25 June 2014, posted as approved on  XXXX 
2014
Item 2: Opening Remarks / Review of Projects & Action List (15 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: MOTION - A proposed modification of the GNSO's consensus 
recommendations relating to IGO acronyms and Red Cross identifiers (20 mins)
On 10 November 2013 the PDP Working Group (IGO-INGO PDP WG) delivered its Final 
Report<http://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf> to the 
GNSO Council that included twenty-five consensus recommendations of the WG. On 
20 November 2013 the GNSO Council unanimously 
adopted<http://gnso.icann.org/en/council/resolutions#20131120-2> all 
twenty-five consensus recommendations of the IGO-INGO PDP WG and forwarded them 
to the ICANN Board in January 2014 with a recommendation for their adoption.
On 30 April 2014 the Board 
resolved<https://www.icann.org/resources/board-material/resolutions-2014-04-30-en>
 to adopt those of the GNSO's recommendations that are not inconsistent with 
GAC advice, and to facilitate dialogue between the affected parties in order to 
reconcile the remaining differences, as further detailed in Annex 
A<https://www.icann.org/en/groups/board/documents/resolutions-annex-a-30apr14-en.pdf>
 and Annex 
B<https://www.icann.org/en/groups/board/documents/resolutions-annex-b-30apr14-en.pdf>
 of the Board's resolution. The GNSO's recommendations and GAC advice are 
largely consistent except in relation to the duration and mechanism of 
protection for IGO acronyms and the full names and acronyms of 189 Red Cross 
national societies and the international Red Cross and Red Crescent movement, 
for which the GNSO had 
recommended<http://gnso.icann.org/en/council/resolutions#20131120-2> a 90-day 
period of protection by way of a claim notification service utilising the 
Trademark Clearinghouse (TMCH).
On 16 June 2014 the NGPC 
sent<http://gnso.icann.org/en/correspondence/chalaby-to-robinson-16jun14-en.pdf>
 a letter to the GNSO Council requesting that the GNSO consider modifying its 
recommendations relating to the duration and mechanism of protection for IGO 
acronyms and national society names of the Red Cross. This modification to be 
in accordance with and as envisaged by Section 16 of the GNSO's PDP 
Manual<http://gnso.icann.org/council/annex-2-pdp-manual-13jun13-en.pdf>.
4.1 - Present the 
motions<https://community.icann.org/display/gnsocouncilmeetings/Motions+24+July+2014>
 (Thomas Rickert / Mary Wong)
4.2 - Discussion
4.3 - Vote (Threshold: simple majority)
Item 5: 
Update<http://london50.icann.org/en/schedule/wed-gnso-council/presentation-gnso-council-compliance-25jun14-en>
 - On the Uniformity of Reporting Final Issue Report Resolution (20 mins)
Here the Council will receive an update, regarding an approved 
resolution<http://gnso.icann.org/en/council/resolutions#20130516-1> as a result 
of the Final Issue 
Report<http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf> on 
Uniformity of Reporting (a recommendation from RAPWG).
The resolution states, "The GNSO Council does not initiate a Policy Development 
Process at this stage but will review at the completion of the ICANN 
Contractual Compliance three-year plan expected for 31 December 2013 whether 
additional action is required."
ICANN's Contractual Compliance team provided a presentation to the Council in 
London and here will present and be in a position to discuss the past 
activities and results of the Contractual Compliance three-year plan and future 
efforts to evolve the contractual compliance function with regard to metrics 
collection and reporting.
The GNSO Council will deliberate whether further attention to this issue is 
warranted.
Note: The second resolution launched what is now known as the non-PDP, Data & 
Metrics for Policy Making 
WG<http://gnso.icann.org/en/group-activities/active/dmpm> that is currently 
executing against its approved charter.
5.1 - 
Update<http://london50.icann.org/en/schedule/wed-gnso-council/presentation-gnso-council-compliance-25jun14-en>
 (Maguy Serad)
5.2 - Discussion
5.3 - Next steps
Item 6: UPDATE - A cross-community working group to develop a transfer process 
for the IANA stewardship role (10 mins)
An invitation to participate in a drafting team has now been circulated and 
sent to all ICANN SO & ACs. Here the Council will take the opportunity, as 
manager of the policy development processes of the GNSO, to provide direction 
on the formation, development and work of a CWG on the NTIA transition.
6.1 - Update (Jonathan Robinson)
6.2 - Discussion
6.3 - Next steps
Item 7: UPDATE - On the work of the GNSO Review Working Party (10 mins)
As part of a periodic review process that is built into the ICANN model, work 
on the ICANN Board initiated reviews of the GNSO (and the GNSO Council and 
related functions) has commenced. The objective of the Review is to examine the 
organizational effectiveness of the GNSO, including its components (GNSO 
Council, GNSO Working Groups, GNSO Stakeholder Groups and Constituencies). The 
review is to be tightly scoped based on objective and quantifiable criteria 
provided to an independent examiner. A 
webinar<http://www.icann.org/en/news/announcements/announcement-2-23apr14-en.htm>
 to discuss this has recently taken place.
The GNSO Review Working Party has been assembled to:

  *   Act as a liaison between the GNSO, the independent examiner and the SIC,
  *   Provide input on review criteria and the 360 Assessment,
  *   Coordinate interviews and objectively supply clarification and responses 
to the draft findings and recommendations.
The SIC envisages that once a final report is issued and the Board takes action 
on it, as appropriate, the GNSO Review Working Party will also coordinate with 
the GNSO community to prepare an Implementation Plan and champion 
implementation of improvement activities.
7.1 - Update (Jennifer Wolfe)
7.2 - Discussion
7.3 - Next steps
Item 8: UPDATE - On the work of the GAC / GNSO Consultation Group (10 mins)
Here the Council will receive an update, including reactions to the Group's 
work presented during ICANN 50 in London and to discuss any actions being 
planned. In particular, the Consultation Group will provide an update on the 
overall direction of its work and specifically, remind the Council of the 
decision to recruit and appoint a GNSO Liaison to GAC as well as the selection 
process for such a liaison.
The call for applications is out and the deadline for applicants is the 31 July 
2014. The Consultation Group envisages that a preliminary decision on the 
actual appointment will take place as soon as possible. Moreover that such an 
appointment will be subject to a motion before the GNSO Council in September 
and the appointment will be made immediately thereafter and, in any event, 
before ICANN 51.
8.1 - Update (Jonathan Robinson)
8.2 - Discussion
8.3 - Next steps
Item 9: UPDATE & DISCUSSION - Planning for LA (10 mins)
Making the most out of the face-to-face meeting time available at the ICANN 
Meeting in LA will take planning and preparation work. The Council has output 
from the survey<https://www.surveymonkey.com/s/QMQJY7Z> of the ICANN 50 meeting 
in London. Please complete the survey<https://www.surveymonkey.com/s/QMQJY7Z> 
if you have not already done so. GNSO Council Vice Chair, David Cake will work 
with Jonathan Robinson 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 
such as the ccNSO, the GAC and the ICANN board.
Please Note: The LA Meeting is an ICANN annual meeting and so will include the 
GNSO Council development session on the second Friday i.e. Friday 17 October 
2014. This is a day and evening session focused on the successful and 
productive functioning of the Council for the period Annual Meeting 2014 to 
Annual Meeting 2015.
9.1 - Update (David Cake & Jonathan Robinson)
9.2 - Discussion
9.3 - Next steps
Item 10: Any Other Business (5 mins)
10.1 Council development meeting Friday, 17 October 2014 in Los Angeles
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 15: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 (CET) UTC+1+0DST 19:00
Stockholm, Sweden (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(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/lwky9he



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