Dear All,
Please find the draft agenda for the GNSO Council Meeting 20 July
2012 at 11:00 UTC which is also posted on the Wiki at:
https://community.icann.org/display/gnsocouncilmeetings/Agenda+20-07-2012
And on the website at:
http://gnso.icann.org/en/meetings/agenda-council-20jul12-en.htm
Please let me know if you have any questions.
Thank you.
Kind regards,
Glen
Proposed Agenda for the GNSO Council Meeting
20 July 2012
This agenda was established according to the
GNSO Council Operating Procedures approved 22 September 2011
for the GNSO Council and updated.
http://gnso.icann.org/council/gnso-operating-procedures-16dec11-en.pdf
For
convenience:
Meeting Times 11:00
UTC
http://tinyurl.com/ccz4c9u
Coordinated Universal Time 11:00 UTC
04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00
Paris; 20:00 Tokyo.
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 audiocast
http://stream.icann.org:8000/gnso.m3u
Item 1: Administrative matters (10 minutes)
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:
Draft Minutes of the GNSO Council meeting 27
June 2012 will be approved on
1.5. GNSO Pending Projects List
http://gnso.icann.org/meetings/pending-projects-list.pdf
Item
2: Consent agenda (5 minutes)
A consent agenda item is being added as a
standard agenda item to provide for a simplified process to
obtain Council approval on specific tasks.
No items on the consent agenda.
Item 3: Final Elections procedure (10
minutes)
At the Prague meeting, the proposed election
procedure was shown to the Council. A refined
version was sent to the list. This item is to discuss
and approve this procedure, so that it can be started.
3.1 Presentation of procedure (Stéphane Van
Gelder)
http://gnso.icann.org/en/issues/gnso-council-chair-election-13jul12-en.pdf
3. 2 Discussion
3. 3 Call to approve procedure.
Item 4: Thick Whois PDP (10 minutes)
As the .com agreement has now been renewed (see
http://www.icann.org/en/groups/board/documents/resolutions-23jun12-en.htm#2),
the Council may not want to wait until November before a
Drafting Team is formed to develop a charter for the 'thick'
Whois Policy Development Process Working Group (PDP WG).
4.1 Update from staff (X Y)
4. 2 Discussion
4. 3 Next steps.
Item 5: Whois RT Final Report (10 minutes)
Considering the Board resolution on the Whois
Review Team Final Report and the Board's call for input from
the GNSO by August 31, 2012, how should the Council respond?
5.1 Update from staff (X Y)
5. 2 Discussion
5. 3 Next steps.
Item 6: GNSO Review (10 minutes)
At the wrap-up in Prague, there was discussion
around forming a small group to examine possible actions
ahead of the 2013 ICANN bylaws-mandated review. This is a
discussion item to determine whether the Council wishes to
move ahead in this way.
6.1 Update from staff (X Y)
6. 2 Discussion
6. 3 Next steps.
Item 7: Impact of new gTLD program on
existing GNSO structure (10 minutes)
The new gTLD program may impact the GNSO's
Contracted Parties. This item aims to initiate a discussion
of potential issues to look at as the new gTLD program comes
online and the Registry and Registrar stakeholder groups are
affected by this.
7.1 Discussion
Item 8: Management of work (10 minutes)
Recent discussions on the Council list have
raised concerns about the volume of documents published
prior to an ICANN meeting and how these can best be managed
by the volunteer community that makes up the GNSO Council as
it struggles to read a substantial amount of reports and
other documents in order to better inform its own decision
making processes with regards to policy.
8.1 Discussion
Item 9: Fake Renewal Notices (10 minutes)
The GNSO Council requested that a small group
prepare a request for information concerning Fake Renewal
Notices for the Registrar Stakeholder Group to help inform
its deliberations on the Registration Abuse Policies Working
Group (RAP WG) Recommendation on Fake Renewal Notices (#2).
The drafting team submitted its report to the GNSO Council
on 6 March 2012. Following a presentation of the report to
the GNSO Council at the ICANN Meeting in Costa Rica, the
GNSO Council decided to put the report out for public
comment. A public comment forum was opened (see http://www.icann.org/en/news/public-comment/fake-renewal-notices-report-21mar12-en.htm)
and has now closed. At its last meeting, the GNSO Council
requested the Drafting Team (DT) to review the comments
received, update the report if deemed appropriate and report
back accordingly. The DT has reviewed the comments received
and submitted its updated report to the GNSO Council on 21
June 2012 (see http://gnso.icann.org/issues/frn/fake-renewal-notices-updated-report-20jun12-en.pdf).
9.1 Presentation of updated Fake Renewal
Notices Report (Mikey O'Connor)
9. 2 Discussion
9. 3 Next steps
Item 10: Internationalised Registration
Data WG Final Report (10 minutes)
During its June 27 Open Meeting, the GNSO
Council approved a motion
to deliver the IRD Final Report to the ICANN Board and to
"review the recommendations in the Report and shall provide
to the Board its advice with regard to those recommendations
that may have policy implications".
This agenda item is to discuss next steps in
light of this commitment, and to determine how the Council
wishes to review and report on the IRD recommendations that
may have policy implications.
10.1 Update from Staff (Margie Milam).
10.1 Discussion.
10.1 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): 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)
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 March and October, Summer in the NORTHERN
hemisphere
----------------------------------------------------------------------------
Reference (Coordinated Universal Time) UTC 11:00
----------------------------------------------------------------------------
California, USA (PDT) UTC-8+1DST 04:00
New York/Washington DC, USA (EDT) UTC-5+1DST 07:00
Buenos Aires, Argentina (ART) UTC-3+0DST 08:00
Montevideo, Uruguay (UYT) UTC-3+0DST 08:00
London, United Kingdom (BST) UTC+1DST 12:00
Abuja,Nigeria (WAT) UTC+1+0DST 12:00
Tunis, Tunisia (CET) UTC+1+0DST 12:00
Bonn, Germany (CEST) UTC+1+1DST 13:00
Paris, France (CEST) UTC+1+1DST 13:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 14:00
Karachi, Pakistan (PKT ) UTC+5+0DST 16:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 19:00
Tokyo, Japan (JST) UTC+9+0DST 20:00
Wellington, New Zealand (NZDT ) UTC+12+0DST 23:00
----------------------------------------------------------------------------
The DST starts/ends on last Sunday of October 2012, 2:00 or
3:00 local time (with exceptions)
----------------------------------------------------------------------
For other places see http://www.timeanddate.com and http://tinyurl.com/ccz4c9u
Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat@icann.org