ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Updated GNSO Council agenda for Wednesday, 20 November at 16:00 UTC, 13:00 Buenos Aires

  • To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] Updated GNSO Council agenda for Wednesday, 20 November at 16:00 UTC, 13:00 Buenos Aires
  • From: Glen de Saint Géry <Glen@xxxxxxxxx>
  • Date: Tue, 19 Nov 2013 05:39:10 -0800
  • Accept-language: fr-FR, en-US
  • Acceptlanguage: fr-FR, en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Ac7lLHoxGG5grXX7RfeJtCYiQTn9tAAADYMg
  • Thread-topic: Updated GNSO Council agenda for Wednesday, 20 November at 16:00 UTC, 13:00 Buenos Aires

Dear All,
Please find the updated GNSO Council agenda for Wednesday, 20 November at 16:00 
UTC, 13:00 Buenos Aires.
Two item for discussion have been added if time allows/
Item 8 - JIG Final Report on Universal Acceptance of IDN 
TLDs<http://buenosaires48.icann.org/en/schedule/mon-jig/presentation-jig-final-idn-tld-acceptance-15nov13-en>
 (if time allows)

Item 9 - DNS Security and Stabilty and Analysis (DSSA) Working Group Final 
Report (if time allows)

Please let me know if you have any questions.
Thank you.
Kind regards,
Glen
Proposed Agenda for the GNSO Council Public Meeting in Buenos Aires, 20 
November 2013 Part 1
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 
<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 agenda.
Meeting Times 16:00 UTC
http://tinyurl.com/oby4lzl
Coordinated Universal Time 16:00 UTC
08:00 Los Angeles; 11:00 Washington; 13:00 Buenos Aires; 16:00 London; 17:00 
Paris; 05:00 Wellington next day

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.

Item 1: Administrative matters (10 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 31 October 
2013<http://gnso.icann.org/mailing-lists/archives/council/msg15145.html> will 
be posted as approved on 21 November 2013

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)
Item 4: MOTION - To approve a charter for the Translation and Transliteration 
of Contact Information PDP Working Group (10 mins)
On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) 
on the Translation and Transliteration of Contact Information and decided to 
create a PDP Working Group for the purposes of fulfilling the requirements of 
the PDP.  Following a call for volunteers, a Drafting Team was formed and its 
members have developed a charter for consideration by the GNSO Council.  The 
drafting team has submitted the charter, reviewed and revised it on the request 
of the Council and then re-submitted it and so the GNSO Council, having 
reviewed the 
charter<http://gnso.icann.org/en/drafts/transliteration-contact-charter-06nov13-en.pdf>,
 will vote on whether to approve it as submitted by the Drafting Team.
4.1 - Review Motion 
1<https://community.icann.org/display/gnsocouncilmeetings/Motions+20+November+2013>
4.2 - Discussion
4.3 - Next steps
Item 5: MOTION - To approve the Recommendations for IGO-INGO Protections (20 
mins)

On 10 November 2013 the WG published its Final 
Report<http://gnso.icann.org/en/issues/igo-ingo-final-10nov13-en.pdf> [PDF, 644 
KB] which includes policy recommendations for the protection of IGO and INGO 
(including the RCRC and IOC) identifiers in all gTLDs. The recommendations are 
organized by organization type seeking protection and each one also contains 
the WG's Chair assessment of consensus. The GNSO Council will consider this 
Final Report and vote on whether to approve the recommendations contained 
therein.

5.1 - Review Motion 
2<https://community.icann.org/display/gnsocouncilmeetings/Motions+20+November+2013>
5.2 - Discussion
5.3 - Next steps
Item 6: INPUT & DISCUSSION - Prospective improvements to the Policy Development 
Process (15 mins)
The Council is committed to on-going enhancements to the methods of working of 
the Council and the work initiated and managed by the Council. The PDP process 
is a cornerstone of policy making within the GNSO and, as such, the work of the 
Council.  The PDP outcomes and associated processes are the subject of focus 
and attention both within the GNSO and the broader ICANN Community. The Council 
has previously discussed a paper prepared by ICANN 
staff<http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf> on 
potential improvements to the PDP process.  The discussion is now encapsulated 
in a table form and now includes reference to the related recommendations of 
the ATRT2.  Further work needs to be done on reviewing the table and agreeing 
concrete next steps.
6.1 - Review of table of prospective PDP 
Improvements<http://gnso.icann.org/en/drafts/pdp-improvements-table-14nov13-en.pdf>
 (Marika Konings)
6.2 - Discussion
6.3 - Next steps
Item 7: DISCUSSION - Forthcoming reviews of the GNSO and GNSO Council (15mins)

As part of a periodic review process that is built into the ICANN model, board 
initiated reviews of the GNSO and the GNSO Council as an integral part of the 
GNSO are expected.  In order to be effectively prepared for these reviews, it 
was originally proposed in Beijing that a group be formed to understand the 
issues and begin to take appropriate next steps.  One key suggestion from 
Beijing was that any group (such as the Council) being reviewed undertakes a 
form of self-review.  The intended course of action was impacted by the board 
deliberations on whether or not to proceed with the review and, more recently, 
what format the review might follow.  The Council will receive an update during 
its meeting with the board in Buenos Aires and this item provides an 
opportunity to discuss and agree the intended course of action.
7.1 - Current status
7.2 - Discussion
7.3 - Next steps
Item 8 - JIG Final Report on Universal Acceptance of IDN 
TLDs<http://buenosaires48.icann.org/en/schedule/mon-jig/presentation-jig-final-idn-tld-acceptance-15nov13-en>
 (if time allows)

The purpose of the Ad-hoc ccNSO/GNSO Joint IDN Working Group is to deal with 
issues related to the introduction of IDN ccTLDs under the IDN ccTLD Fast Track 
implementation process and IDN gTLDs under the new gTLD implementation process 
which are of common interest to both the GNSO and ccNSO. The JIG has delivered 
its JIG Final Report on Universal Acceptance of IDN 
TLDs<http://buenosaires48.icann.org/en/schedule/mon-jig/presentation-jig-final-idn-tld-acceptance-15nov13-en>
 on 17 November for GNSO Council consideration. The GNSO will now consider the 
Final Report.

 1.  Discussion
 2.  Next steps
Item 9 - DNS Security and Stabilty and Analysis (DSSA) Working Group Final 
Report (if time allows)

The ALAC, ccNSO, GNSO and NRO, acting as ASO in this particular case, all 
endorsed the charter of the joint DNS Security and Stability and Analysis 
working group (DSSA) according to each own rules and procedures, in December 
2010 and as a result are the participating SO's and AC's in the DSSA. The DSSA 
delivered its Final Report to the chartering organisations on 11 November 2013. 
The GNSO Council will now consider the Final Report.

 1.  Discussion
 2.  Next steps
Item 10:  Thanks to outgoing councillors (5 mins)


 *   Lanre Ajayi (NCA)
 *   Mason Cole (RrSG & Vice Chair)
 *   Zahid Jamil (CSG / BC)
 *   Wolf-Ulrich Knoben (CSG / ISPC & Vice Chair)
 *   Joy Liddicoat (NCSG)
 *   Jeff Neuman (RySG)
 *   Wendy Seltzer (NCSG)
Item 11:  Any Other Business (5 mins)

Item 12: Open microphone
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 16:00
----------------------------------------------------------------------------
California, USA 
(PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) 
UTC-7+1DST 08:00
New York/Washington DC, USA (EST) UTC-4+1DST 11:00
Rio de Janiero, Brazil (BRST) UTC-2+1DST 14:00
Montevideo, Uruguay 
(UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) 
UTC-2+1DST 14:00
Buenos Aires, Argentina 
(ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) 
UTC-3+0DST 13:00
London, United Kingdom (BST) UTC+0DST 16:00
Abuja, Nigeria (WAT) UTC+1+0DST             17: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<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.html>)
 UTC+2+0DST 18:00
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 00:00 (next day)
Perth, Australia 
(WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) 
UTC+8+0DST 00:00 (next day)
Wellington, New Zealand  UTC+12+1DST 05: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/oby4lzl
Glen de Saint Géry
GNSO Secretariat
gnso.secretariat@xxxxxxxxxxxxxx<mailto:gnso.secretariat@xxxxxxxxxxxxxx>
http://gnso.icann.org<http://gnso.icann.org/>



<<< Chronological Index >>>    <<< Thread Index >>>