[council] Updated GNSO Council meeting draft agenda 16 February 2012 at 15:00.
- To: "council@xxxxxxxxxxxxxx GNSO" <council@xxxxxxxxxxxxxx>
- Subject: [council] Updated GNSO Council meeting draft agenda 16 February 2012 at 15:00.
- From: Glen de Saint Géry <Glen@xxxxxxxxx>
- Date: Fri, 10 Feb 2012 07:10:42 -0800
- Accept-language: fr-FR, en-US
- Acceptlanguage: fr-FR, en-US
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AczoBRacktEqoFqxStS+ofggKO81aw==
- Thread-topic: Updated GNSO Council meeting draft agenda 16 February 2012 at 15:00.
Please find the updated draft agenda for the GNSO Council meeting on 16
February 2012 at 15:00.
Please let me know if you have any questions.
Agenda for GNSO Council Meeting – 16 February 2012
Wiki agenda :
Motions before Council
This agenda was established according to the GNSO Council Operating Procedures
approved 22 September 2011 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 Time 15:00
Coordinated Universal Time: 15:00 UTC
07:00 Los Angeles; 10:00 Washington DC; 15:00 London; 16:00 Paris; 00:00 Tokyo;
17 February 2012
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
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
· 19 January 2012 GNSO Council minutes –approved on 16 February 2012.
1.5. GNSO Pending Projects List
· Review main changes.
· Comments and/or questions.
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.
• Approval of the Recommendations Report on IRTP B Rec 9 part 2 that Staff is
proposing be sent to the Board.
Refer to the Recommendations Report:
• Approval of the proposal to end the work on Whois access at this time.
• Approval of the termination of the Open Council DT.
• Approval of new calls for volunteers for the JIG.
Item 3: 'thick' Whois Final Issue Report (10 minutes)
As recommended by the IRTP Part B Working Group, the GNSO Council requested
ICANN Staff to prepare an Issue Report on the requirement of ‘thick’ WHOIS for
all incumbent gTLDs. The Preliminary Issue Report was published for public
Staff has now submitted the Final Issue
which includes the report of comments received and additional updates as a
result of the comments made. The GNSO Council will now consider the Final Issue
and decide whether or not to initiate a PDP.
3.1 Presentation of Final Issue
Refer to motion:
3.2 Reading of the motion (Stéphane Van Gelder)
Item 4: IRTP B Rec 8 (15 minutes)
As adopted by the Council on 22 June 2011
http://gnso.icann.org/resolutions#201106-1 the Council requested Staff to
provide a proposal designed to ensure a technically feasible approach can be
developed to meet the following recommendation "prior to the consideration of
approval of the recommendation regarding the standardizing and clarifying WHOIS
status messages regarding Registrar Lock status".
Staff submitted its recommendation on January 3, 2012
A motion was presented at the Jan 19, 2012 meeting, but was withdrawn to give
Staff and Council more time to fine tune. A new motion is presented today.
Refer to motion
4.1 Reading of the motion (Yoav Keren).
Item 5: JIG letter to the Board (10 minutes)
The ccNSO has not approved the joint letter the GNSO suggested sending to the
Board on the JIG. As a way forward, the ccNSO is proposing two options:
1. Sending their proposed letter
as a joint letter to the Board.
2. If the GNSO does not approve option 1, the ccNSO will send a letter on
its own. In that case, the GNSO must decide on what it wants to do, as we had
approved sending a joint letter before
5.1 Update by staff (X Y)
5.3 Next steps
Item 6: Costa Rica Weekend agenda (20 minutes)
At the Jan 19 Council meeting, it was suggested that our weekend sessions need
to be focussed more on preparation work for the Council's week and less on
updates. This is a discussion item on the proposed agenda.
6.1 Update and presentation of agenda (Wolf Ulrich Knoben)
6.2 Agenda for GNSO Council meeting with the Board
6.3 Agenda for GNSO Council meeting with the GAC
6.4 Agenda for GNSO Council lunch with the ccNSO
Item 7: Red Cross and Olympic Committee names (20 minutes)
A GNSO Drafting Team is working on a charter to determine how to handle the
protection of RC and IOC names under the new gTLD program. This agenda item is
to provide the Council with an update on that work.
7.1 Update by staff (X Y)
Item 8: GNSO liaison to the ccNSO (5 minutes)
Olga Cavalli had served as GNSO Council liaison to the ccNSO, but has now left
the GNSO Council. Therefore the GNSO Council must now appoint a new liaison to
8.1 Call for volunteers
Item 9: 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:
1. Create an Issues Report: requires an affirmative vote of more than 25% vote
of each House or majority of one House;
2. Initiate a Policy Development Process (“PDP”) Within Scope (as described in
Annex A): requires an affirmative vote of more than 33% of each House or more
than 66% of one House;
3. Initiate a PDP Not Within Scope: requires an affirmative vote of more than
75% of one House and a majority of the other House (“GNSO Supermajority”);
4. 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;
5. Approve a PDP Recommendation With a GNSO Supermajority: requires an
affirmative vote of a GNSO Supermajority; and
6. 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 with respect to any contracting
party affected by such contract provision.
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 & March, Winter in the NORTHERN hemisphere
Reference (Coordinated Universal Time) UTC 15:00
New York/Washington DC, USA (EST) UTC-5+0DST 10:00
Buenos Aires, Argentina
London, United Kingdom (BST) UTC+0DST 15:00
Tunis, Tunisia (CET) UTC+1+0DST 16:00
Bonn, Germany (CET) UTC+1+0DST 16:00
Paris, France (CET) UTC+1+0DST 16:00
) UTC+5+0DST 20:00
) UTC+8+0DST 23:00
Wellington, New Zealand
) UTC+12+1DST 04:00 next day
The DST starts/ends on last Sunday of March 2012, 2:00 or 3:00 local time (with
For other places see http://www.timeanddate.com
Glen de Saint Géry