[council] RE: Reminder: Proposed Agenda for the GNSO Council Meeting 1 August 2013

Jonathan Robinson jrobinson at afilias.info
Thu Aug 1 08:08:54 UTC 2013



Thanks and no problem.  I understand that people are busy and that this is a
recently scheduled meeting.


Everything apart from the motion and Item 2 are essentially administrative /
standard items.  

In item 2, I had no intention of going into detail but rather to remind
everyone of the existence of the action list and to keep an eye on it for
commitments they have made or effort they may be required to put in.


Look forward to seeing you and others on the call later.




From: Neuman, Jeff [mailto:Jeff.Neuman at neustar.us] 
Sent: 01 August 2013 03:51
To: 'Glen de Saint Géry'; GNSO Council List
Subject: [council] RE: Reminder: Proposed Agenda for the GNSO Council
Meeting 1 August 2013




A friendly request
.can we scrap all agenda items other than the motion.
Some people are on vacation and others are in the middle of work activities
and travel.   If this wasn’t to approve a PDP Final Report, I would have
asked it to be put on the consent agenda J


But I believe this call should not take us more than 15 minutes tops unless
there is any discussion on the motion.  However, given that the motion has
been out there for a number of weeks and was a topic of discussion in
Durban, there really should not be discussion.


Jeffrey J. Neuman 
Neustar, Inc. / Vice President, Business Affairs


From: owner-council at gnso.icann.org [mailto:owner-council at gnso.icann.org] On
Behalf Of Glen de Saint Géry
Sent: Monday, July 29, 2013 9:57 AM
To: GNSO Council List
Subject: [council] Reminder: Proposed Agenda for the GNSO Council Meeting 1
August 2013


Dear Councillors,

Please find below the proposed agenda for the GNSO Council meeting on 1
August 2013 at 15:00 UTC.  This agenda confirms the one item contained in
the 18 July 2013 notice of the GNSO Council meeting (see
http://gnso.icann.org/mailing-lists/archives/council/msg14866.html) and
there have been no additions since provision of that notice.

Please let me know if you have any questions.
Thank you.

Kind regards,

Proposed Agenda for the GNSO Council Meeting 1 August 2013

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%20> >
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

Meeting Times 15:00UTC <http://tinyurl.com/bojlrbx> 

Coordinated Universal Time 15:00 UTC
08:00 Los Angeles; 11:00 Washington; 16:00 London; 17:00 Paris; 03:00
Wellington next day

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.

Item 1: Administrative matters (10 mins)

1.1 Roll Call
1.2 Statement of interest updates
1.3 Review/amend agenda

Item 2: Opening Remarks from Chair (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

No items


Item 4: MOTION - Locking of a Domain Name subject to UDRP Proceedings (15


The “locking” of a domain name registration associated with UDRP proceedings
is not something that is literally required by the UDRP as written, but is a
practice that has developed around it. As a result, there is no uniform
approach, which has resulted in confusion and misunderstandings. The GNSO
Council initiated a PDP on this specific topic in December 2011 and tasked
the WG to make recommendations to the GNSO Council to address the issues
identified with the locking of a domain name subject to UDRP Proceedings.


The PDP Working Group has now submitted its Final Report for GNSO Council
consideration containing 17 full consensus recommendations (see

4.1 – Review motion
4.3 - Discussion
4.4 – Vote (Threshold supermajority)

Item 5:  Any Other Business (5 min) 

Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section
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

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  <http://www.icann.org/en/about/governance/bylaws#AnnexA> 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

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

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
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 March and October, Summer in the NORTHERN hemisphere 

Reference (Coordinated Universal Time) UTC 15:00 
California, USA (PST
<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html> )
UTC-8+1DST 08:00 
New York/Washington DC, USA (EST) UTC-5+1DST 11:00
Rio de Janiero, Brazil (BRST) UTC-3+1DST 12:00
Montevideo, Uruguay (UYST
<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html> )
UTC-3+1DST 12:00
London, United Kingdom (BST) UTC+0DST 16:00 
Abuja, Nigeria (WAT
) UTC+1+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
html> ) UTC+2+0DST 18:00
Karachi, Pakistan (PKT
) UTC+5+0DST 20:00 
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 23:00 
Perth, Australia (WST
<http://timeanddate.com/library/abbreviations/timezones/au/wst.html> )
UTC+8+0DST 23:00 
Wellington, New Zealand (NZDT
l>  ) UTC+12+1DST 03:00 (next day)

The DST starts/ends on last Sunday of October 2013, 2:00 or 3:00 local time
(with exceptions)
For other places see http://www.timeanddate.com 

Glen de Saint Géry 
GNSO Secretariat 
gnso.secretariat at gnso.icann.org 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20130801/7e8c8842/attachment.html>

More information about the council mailing list