[council] Draft Agenda for the GNSO Council Meeting 17 January 2013 at 20:00UTC
- To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Subject: [council] Draft Agenda for the GNSO Council Meeting 17 January 2013 at 20:00UTC
- From: Glen de Saint Géry <Glen@xxxxxxxxx>
- Date: Tue, 8 Jan 2013 09:49:02 -0800
- Accept-language: fr-FR, en-US
- Acceptlanguage: fr-FR, en-US
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: Ac3tyDs/v7GmGkgiR6u+Aahcbq0Q8A==
- Thread-topic: Draft Agenda for the GNSO Council Meeting 17 January 2013 at 20:00UTC
Please find the draft Agenda for the GNSO Council Meeting 17 January 2013 at
20:00 UTC posted at:
And on the Wiki (where you will find the latest updates)
Tomorrow, 9 January 2013 is the deadline for motions and they will be posted on
Draft Agenda for the GNSO Council Meeting 17 January 2013
This agenda was established according to the GNSO Council Operating Procedures
approved 13 September 2012 for the GNSO Council and updated.
* 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 20:00 UTC<http://tinyurl.com/bojlrbx>
Coordinated Universal Time 20:00 UTC
12:00 Los Angeles; 15:00 Washington; 20:00 London; 21:00 Paris; 09:00
Wellington (next day 14 January 2013)
Dial-in numbers will be sent individually to Council members. Councilors should
notify the GNSO Secretariat in advance if a dial out call is needed.
GNSO Council meeting audio cast
Item 1: Administrative matters (10 minutes)
1.1 Roll Call
1.2 Statement of interest updates
General updates and/or for specific current agenda items.
1.3 Review main changes.
1.4 Note the status of minutes for the previous Council meeting per the GNSO
Minutes of the GNSO Council meeting 20 December
approved effective 2 January 2013.
1.5 GNSO Pending Projects List
* Review main changes.
* Comments and/or questions.
Item 2: Opening Remarks from Chair (5 minutes)
Review focus areas and provide updates on specific key themes / topics
Item 3: Consent agenda (0 minutes)
Item 4: MOTION - Any motion submitted by 09 January 2013 (10 minutes)
Description of motion
4.1 Reading of the motion (Proposer).
4.2 Discussion of motion and next steps.
4.3 Vote (Standard threshold: simple majority of each house).
Item 5: MOTION - Any additional motion submitted by 09 January 2013 (10 minutes)
Description of motion
5.1 Reading of the motion (Proposer).
5.2 Discussion of motion and next steps.
5.3 Vote (Standard threshold: simple majority of each house).
Item 6: INFORMATION - GNSO Council Review and SIC Update (15 minutes)
In Toronto, the Chair of the SIC provided an overview of a new framework for
future independent review efforts at ICANN. The GNSO was used as a case study
to describe the effort because it is the first Supporting Organization lined-up
in the next review cycle. Staff will brief the Council on the set of criteria
metrics for GNSO Stakeholder Groups and Constituencies, and the work underway
to develop metrics for the Council and the Working Group Model of policy.
6.1 Update from Staff (Rob Hogarth)
6.3 Next Steps
Item 7: UPDATE - Trademark Clearinghouse (TMCH) Strawman Proposal and Defensive
Registrations Discussion (20 Minutes)
ICANN's CEO has requested GNSO Council input on the Strawman
recently developed through the TMCH related implementation discussions, which
has been posted for public comment.
ICANN's CEO additionally requested Council input on the joint proposal from the
Business Constituency/Intellectual Property Constituency (BC/IPC) for a
"limited preventative registration mechanism" which is also currently available
for public comment. A subsequent note (19 December 2012) from ICANN's CEO
clarified the desired deadline for input to be no later than 22 February 2013.
Related to this discussion is the Staff briefing paper
(http://gnso.icann.org/en/node/32287) to the GNSO Council on the topic of
defensive registrations at the second level, in response to a previous request
from the New GLTD Committee (2012.04.10.NG2). The New GTLD Committee requested
the GNSO to consider whether additional work on defensive registrations at the
second level should be undertaken.
The Council is to continue to discuss: (i) a response to the ICANN CEOs
request, and (ii) to consider whether to undertake any additional work related
to the BC/IPC proposal and/or the Staff briefing paper, on the topic of second
level defensive registrations.
7.3 Next Steps
Item 8: UPDATE - Response to the GAC Letter (20 minutes)
The GAC has sent a
to the GNSO Council with regard to the initiation of a PDP on the IGO/INGO
issue, and specifically requesting a rationale for undertaking a PDP i.e. an
explanation as to why GNSO believes this issue should be evaluated through a
PDP rather than simply executed as an implementation process. The Council has
sent an initial response and now needs to move ahead with developing a full
This is a discussion item.
8.3 Next steps
Item 9: INFORMATION & DISCUSION - Policy vs. Implementation (20 minutes)
The recent letter from the GAC as well as activities relating to work on the
Trademark Clearinghouse, highlights a broader issue regarding the boundary
between policy development and implementation work as well as the effective
integration of policy development and integration work from the outset.
Recent discussions on the Council mailing list indicate that there is an
interest to undertake further work on this issue. At the same time, ICANN Staff
has published a paper (include link when available) that is intended to
facilitate further community discussions on this topic.
9.1 Update from Staff (Marika Konings)
9.3 Next steps
Item 10: UPDATE - ATRT2 Developments (5 minutes)
The call for applicants to serve on the next Accountability and Transparency
Review Team (ATRT) has been extended until 14 January 2013. (See:
http://www.icann.org/en/news/announcements/announcement-03dec12-en.htm ). An
update on the process and next steps to provide GNSO Council endorsements of
applicants will be provided.
This is a discussion item.
10.1 Update (Wolfe-Ulrich Knoben)
10.3 Next steps
Item 11: Any Other Business (5 minutes)
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
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
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
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 20:00
New York/Washington DC, USA (EST) UTC-5+0DST 15:00
Rio de Janiero, Brazil (BRST) UTC-3+1DST 18:00
Edinburgh, Scotland (BST) UTC+0DST 20:00
London, United Kingdom (BST) UTC+0DST 20:00
Bonn, Germany (CEST) UTC+1+0DST 21:00
Stockholm, Sweden (CET) UTC+1+0DST 21:00
Ramat Hasharon, Israel
) UTC+5+0DST 01:00 - next day
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 04:00 - next day
UTC+8+0DST 04:00 - next day
Wellington, New Zealand
) UTC+12+1DST 09:00 - next day
The DST starts/ends on last Sunday of March 2013, 2:00 or 3:00 local time (with
For other places see: http://www.timeanddate.com
Glen de Saint Géry