Agenda for the GNSO Council Meeting 7 June 2012
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.
Coordinated Universal Time 20:00 UTC
13:00 Los Angeles; 16:00 Washington; 21:00 London; 22:00 Paris; 05:00 Tokyo 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.
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 Operating Procedures:
Draft Minutes of the GNSO Council meeting 10 May 2012 approved on 28 May 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.
2.1 IOC/RC DT. (GAC/GNSO Issues Related to International Olympic Committee (IOC) & Red Cross (RC) Names Drafting Team.) Approve sending of note to GAC.
2.2 Council approval of proposed WG Chair and VC UDRP Domain Locking WG (Michele Neylon and Alan Greenberg).
Item 3: Update on the Joint Supporting Organisations/Advisory Committee on New gTLD Applicant Support Working Group (JAS WG) (15 minutes)
This item aims to provide the Council with a status update on the JAS WG so that next steps for the group can be determined.
This was discussed at the May 10, 2012 Council meeting but as Kurt was unable to attend, the Council felt another discussion point was needed on this subject. Also, a number of questions were asked by the Council during its previous meeting and it was felt that it would be useful to get responses from Kurt to them.
3.1 WG update from Staff, and answers to Council questions (Kurt Pritz)
3.3 Next steps
Item 4: Update on the Prague GNSO working weekend sessions (10 minutes)
Discussion item in preparation of the GNSO Council's work weekend at the Prague ICANN meeting. This item will be introduced by Jeff Neuman, who is in charge of organizing our Prague agenda.
4.1 Update from Jeff Neuman
Item 5: Best practices for addressing abusive registrations (15 minutes)
Following the recommendation of the Registration Abuse Policies (RAP) Working Group, the GNSO Council requested a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registrations of domain names.
The discussion paper recommended the creation of two Working Groups, one to establish the framework for best practices and one to propose candidate best practices to address the abusive registration of domain names.
The Council must now consider a motion to set up a drafting team to create the charter for these groups. This motion was deferred from the May 10, 2012 meeting.
5.1 Reading of the motion (Zahid Jamil)
Item 6: WHOIS Access recommendation (10 minutes)
The WHOIS access recommendation was considered as part of the consent agenda at the Council's 16 February 2012 meeting.
At that meeting, the ISP constituency requested that the proposal to end this work be removed from the consent agenda and considered as part of the GNSO's main agenda. A further suggestion was suggested that constituency/stakeholder members work with Staff to identify a path forward and that the topic be further discussed at the Costa Rica meetings.
A motion has been made to consider next steps.
Refer to motion 2
6.1 Reading of the motion (Wolf-Ulrich KnobenWolf-Ulrich Knoben)
Item 7: Consumer Metrics WG (10 minutes)
The Consumer Metrics WG has prepared a draft advice document for discussion in Prague in order to finalise the document before sending it to the Council.
As part of that process, the WG would like to solicit the GAC's input. A letter
has been drafted for the Council Chair to send to the GAC Chair.
The Council must decide whether to send that letter.
7.1 WG update from Council Liaison (Rosemary Sinclair)
7.2 Council approval of sending proposed letter.
Item 8: Outreach Task Force (OTF) (10 minutes)
The Council has set up a drafting team to develop a charter for an OTF. A motion to approve that charter did not pass when made at the Dakar meeting. A second motion was made at the December 15, 2011 meeting and was not seconded, which meant it was not considered. In Costa Rica, the Council decided to form a group to discuss options on how to proceed.
This is an update item on the work of that group.
8.1 Update from Wolf-Ulrich Knoben
Item 9: Update on the Internationalised Registration Data WG (10 minutes)
The IRD submitted its final report to the GNSO Council and SSAC on March 3, 2012 for review and approval.
However, SSAC has recommend some substantial changes and more work may now be needed by the IRD before its final report can be considered.
This agenda item is to provide an update on these latest developments in the IRD WG's work to the Council.
9.1 WG update from Staff (Steve Sheng)
9.3 Next steps
Item 10: Fake Renewal Notices (10 minutes)
The GNSO Council requested that a small group prepare a request for information concerning Fake Renewal Notices for the RrSG to help inform its deliberations on the RAP WG Recommendation on Fake Renewal Notices (#2).
The drafting team submitted its report to the GNSO Council on 6 March. 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. The Council is now expected to consider next steps.
10.1 Public comment forum submissions overview (Marika Konings)
Report of Public Comments on Fake Renewal Notices
10.3 Next steps
Item 11: Uniformity of Reporting (10 minutes)
To help inform its consideration of the RAPWG Recommendation on Uniformity of Reporting, the GNSO Council requested the ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage.
The ICANN Compliance Team submitted its report on 18 March and presented it to the GNSO Council at its meeting on 12 April. ICANN Staff also provided a background presentation on the RAP WG Recommendation (see https://gnso.icann.org/node/30809).
The GNSO Council is now expected to consider next steps, if any.
11.1 Update from Staff (Marika Konings)
11.3 Next steps
Item 12: 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 )
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 20:00
California, USA (PDT) UTC-8+1DST 13:00
New York/Washington DC, USA (EDT) UTC-5+1DST 16:00 – next day Buenos Aires, Argentina (ART) UTC-3+0DST 17:00
Montevideo, Uruguay (UYT) UTC-3+0DST 17:00
London, United Kingdom (BST) UTC+1DST 21:00
Abuja,Nigeria (WAT) UTC+1+0DST 21:00
Tunis, Tunisia (CET) UTC+1+0DST 21:00
Bonn, Germany (CEST) UTC+1+1DST 22:00
Paris, France (CEST) UTC+1+1DST 22:00
Ramat Hasharon, Israel(IST) UTC+2+0DST 23:00
Karachi, Pakistan (PKT ) UTC+5+0DST 01:00 – next day
Beijing/Hong Kong, China (HKT ) UTC+8+0DST 04:00 – next day
Tokyo, Japan (JST) UTC+9+0DST 05:00 – next day
Wellington, New Zealand (NZDT ) UTC+12+0DST 08:00 – next day
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