[council] Updated proposed Agenda GNSO Council Teleconference 15 January 2015 at 18:00 UTC.

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

Dear Councillors,

Please find the updated proposed Agenda for the GNSO Council Teleconference on 
15 January 2015 at 18:00 UTC.

The updates are mainly links that have been added, so please check, and an item 
under AOB 10.4 - Request for extension of time for Issue Report on Rights 
Protection Mechanisms
This agenda was established according to the GNSO Council Operating 
Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> 
approved and updated on 13 November 2014.
https://community.icann.org/display/gnsocouncilmeetings/Agenda+15+January+2015
http://gnso.icann.org/en/meetings/agenda-council-15jan15-en.htm

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

Coordinated Universal Time 18:00 UTC
10:00 Los Angeles; 13:00 Washington; 18:00 London; 19:00 Brussels; 02:00 Perth

GNSO Council meeting audio cast
To join the event click on the link:
http://stream.icann.org:8000/gnso.m3u


Councillors should notify the GNSO Secretariat in advance if a dial out call is 
needed.
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 11 December 2014 will be posted as approved 
on xxxxx 2015.
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)

  *   Approve the GNSO Council Recommendations 
Report<http://gnso.icann.org/en/drafts/council-board-irtp-d-05jan15-en.pdf> to 
the ICANN Board concerning IRTP Part D

Note: The 
outcome<http://gnso.icann.org/mailing-lists/archives/council/msg16986.html> of 
the vote on the Council input to the public comment forum on the Board Working 
Group Report on Nominating Committee (BWG-NomCom).

Item 4: UPDATE  - Cross Community Working Group to develop a transition 
proposal for IANA stewardship on naming related functions (20 mins)
The CWG<https://community.icann.org/x/37fhAg> has been chartered to develop a 
proposal on Naming Related Functions for the IANA Stewardship Transition 
Proposal and has been meeting for 2 hours every week since its creation with a 
goal of delivering a final proposal by the end of January 2015. The January 
2015 target date is driven by the request for proposals from the IANA 
Stewardship Transition Coordination 
Group<https://www.icann.org/stewardship/coordination-group> (ICG).
A number of sub-groups were formed to progress work on the different elements 
of the ICG Request for Proposals and a face-to-face meeting was run in 
mid-November. A draft proposal was published for community comment on 1 
December 2014 and the public comment period has since closed. An intensive work 
weekend is planned for the CWG on 10 & 11 January 2015, following which it is 
anticipated that a proposal on Naming Related Functions for the IANA 
Stewardship Transition will be drafted and then distributed to the chartering 
organisations.
Given the deadlines and associated intensity of the work of the CWG as well as 
the need for the GNSO as a chartering organisation to approve the proposal, it 
is timely for the Council to receive a full update and to discuss the work of 
the CWG.
4.1 - Update (Jonathan Robinson)
4.2 - Discussion
4.3 - Next steps
Item 5: UPDATE - Cross Community Working Group on Enhancing ICANN 
Accountability (15 mins)
The National Telecommunications and Information Administration (NTIA) has 
requested that ICANN "convene a multistakeholder process to develop a plan to 
transition the U.S. government stewardship role" with regard to the IANA 
Functions and related root zone management (see item 4 above).

During discussions around the transition process, the community raised the 
broader topic of the impact of the change on ICANN's accountability given its 
historical contractual relationship with the United States and NTIA. The 
concerns raised during these discussions around the transition process indicate 
that the level of trust into the existing ICANN accountability mechanisms does 
not yet meet some stakeholder's expectations. Considering that the NTIA has 
stressed that it was expecting community consensus regarding the transition, 
this gap between the current situation and stakeholder expectations may prevent 
the transition to proceed.

As a result, a DT was formed with participants, amongst others, from the ccNSO, 
GNSO, ASO and ALAC to develop a charter for a Cross Community Working Group on 
Enhancing ICANN Accountability. The DT delivered the proposed 
charter<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en.pdf>
 for consideration to all the ICANN Supporting Organizations and Advisory 
Committees on 3 November 2014 and the 
charter<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en.pdf>
 was adopted by the GNSO Council during its meeting on 13 November.



Here the Council will receive an 
update<http://gnso.icann.org/mailing-lists/archives/council/msg16987.html> on 
status and activities of the CCWG to date.
5.1 Update (Thomas Rickert)
5.2 Discussion
5.3 Next steps

Item 6: UPDATE  - Prospective policy work on "name collision" (10 mins)
On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed 
staff to "provide information to, and work with the GNSO to consider whether 
policy work on developing a long-term plan to manage gTLD name collision issues 
should be undertaken."

ICANN Staff submitted this 
paper<https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oct14-en.pdf>
 to the GNSO Council on 7 October 2014 and it was presented to the Council 
during the ICANN meeting in Los Angeles. Council members agreed in Los Angeles 
to discuss with their respective group what further action, if any, should be 
taken on this topic and report back accordingly during this meeting.

Furthermore, a 
letter<http://gnso.icann.org/en/correspondence/namazi-to-robinson-30oct14-en.pdf>
 was received from Cyrus Namazi offering any additional information or 
assistance that ICANN Staff can provide to further assist the Council in its 
deliberations.

The GNSO Council discussed the topic during previous meetings following which 
it was agreed to draft a response. Here the Council will receive and update and 
provide any additional input needed.

6.1 Status update (Donna Austin)
6.2 Discussion
6.3 Next steps
Item 7: DISCUSSION - Board resolution concerning future gTLD Application Rounds 
(10 mins)
On 17 November 2014 the ICANN Board adopted a 
resolution<https://www.icann.org/resources/board-material/resolutions-2014-11-17-en#2.b>
 the planning for future gTLD application rounds. As part of its action, the 
Board acknowledged the effort and progress within the GNSO to identify areas 
where the GNSO believes that policy advice can be clarified or where it wishes 
to provide additional policy advice applicable to future application rounds. 
Furthermore, as requested in the GNSO Council's June 2014 resolution, the Board 
provided input into the GNSO Council's discussion to identify areas that the 
Board believes may be appropriate for discussion in an evaluation of the 
current gTLD application round and for possible adjustments for subsequent 
application procedures.
A draft 
letter<http://gnso.icann.org/en/drafts/robinson-to-crocker-12jan15-en.pdf> of 
response has been prepared, distributed to the Council and commented on. This 
is an opportunity for the GNSO Council to review the draft and ideally agree to 
send the letter as drafted or with any agreed modifications.

7.1 - Update
7.2 - Discussion
7.3 - Next steps
Item 8: UPDATE - GNSO / GAC Consultation Group and related work (15 mins)
Here the Council will have an opportunity to hear about the work of the GNSO / 
GAC Consultation Group and from the GNSO Liaison to the GAC including any 
initial input and feedback derived following the ICANN meeting in Los Angeles.
In addition, there will be an opportunity to further discuss ideas put forward 
during the GNSO Council Development Session in relation to potential GNSO work 
in response to the GAC Communiqué from ICANN meetings.
8.1 - Update on GAC/GNSO Consultation Group (Mason Cole)
8.2 - Update on draft process for dealing with GAC Communique (Volker Greimann)
8.3 - Discussion


Item 9: Update: Planning for ICANN meeting in Singapore - key direction & themes

9.1 Update - Volker Greimann
9.2 Discussion

Item 10: Any Other Business (10 mins)

10.1 - Correspondence with NGPC on IGO & RCRC. Any update?
10.2 - Consideration of a CWG to deal with new gTLD auction proceeds
10.3 - Note that the Translation & Transliteration PDP WG Initial Report is out 
for public comment - Update Amr Elsadr
10.4 - Request for extension of time for Issue Report on Rights Protection 
Mechanisms

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.)
----------------------------------------------------------------------------
Reference (Coordinated Universal Time) UTC 18:00
Local time between October and March, Winter in the NORTHERN hemisphere
----------------------------------------------------------------------------
California, USA 
(PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) 
UTC-8+0DST 10:00
San José, Costa Rica UTC-6+0DST  12:00
Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+0DST 
12:00
New York/Washington DC, USA (EST) UTC-5+0DST 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
Cairo, Egypt, (EET) UTC+2+0DST 20:00
Istanbul, Turkey (EEST) UTC+2+0DST 20:00
Ramat Hasharon, 
Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
 UTC+3+0DST 20:00
Perth, Australia 
(WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) 
UTC+8+1DST 02:00
Melbourne, Australia (AEDT) UTC+11+1DST 05:00 next day
----------------------------------------------------------------------------
DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with 
exceptions)
----------------------------------------------------------------------
For other places see http://www.timeanddate.com
http://tinyurl.com/lgn2ohv









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