Dear BC Members, Please find below the updated proposed agenda for the GNSO Council Public Meeting in Prague today. The main updates are the room & time changes: it is now scheduled from 3 p.m. Prague time to 6:30 p.m. Prague time in Congress II. Kind Regards, Benedetta Rossi BC Secretariat https://community.icann.org/display/gnsobc/Home www.bizconst.org bc-secretariat@icann.org **__ http://gnso.icann.org/en/calendar#jun http://gnso.icann.org/en/meetings/agenda-council-27jun12-en.htm https://community.icann.org/display/gnsocouncilmeetings/Agenda+27+June+2012 Reference to ICANN Schedule http://prague44.icann.org/node/31781 *Proposed Agenda for GNSO Council Public Meeting in Prague 27 June 2012* Date: 27 June 2012 Reference to ICANN Schedule http://prague44.icann.org/node/31781 Note that this agenda may be updated as more information becomes available so interested parties are encouraged to periodically check for the latest updates on the GNSO Council workspace. <https://community.icann.org/display/gnsocouncilmeetings/GNSO+Council+Meeting...> As can be seen below, in addition to the Open Microphone at the end of the agenda, as possible throughout the meeting time will be allowed for audience participation. Please be aware that audience opportunities to comment will depend on available time. 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: * 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 12:00 UTC <http://tinyurl.com/7m62mzy>__ _*http://tinyurl.com/7m62mzy* Coordinated Universal Time 13:00 UTC: 06:00 Los Angeles; 09:00 Washington DC; 14:00 London; 15:00 Paris/Prague; 22:00 Tokyo; 01:00 Wellington next day) Dial-in numbers will be sent individually to Council members who cannot physically attend the meeting. Councilors should notify the GNSO Secretariat in advance if a dial out call is needed. 15:00- 15:45 GNSO Council Public Forum *_Presentations by Stakeholder and Constituency Group Leaders (45 minutes)_* * Registries Stakeholder Group – David Maher * Registrars Stakeholder Group – Matt Serlin * Non Commercial Users Constituency (NCUC) – Robin Gross * Not-for-Profit Operational Concerns Constituency – Alain Berranger. * Commercial and Business Users Constituency (BC) – Marilyn Cade * Intellectual Property Constituency (IPC) –Steve Metalitz * Internet Service Providers and Connectivity Providers (ISPCP) – Tony Holmes *Break 15:45 – 16:00* *_16:00 – 16:10 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 7 June 2012 approved on 28 June 2012. http://gnso.icann.org/mailing-lists/archives/council/msg13224.html 1.5. GNSO Pending Projects List http://gnso.icann.org/meetings/pending-projects-list.pdf * Review main changes. * Comments and/or questions. *_Item 2: Consent agenda _* 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 Consent agenda items *_Item 3: WHOIS Access recommendation (15 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 https://community.icann.org/display/gnsocouncilmeetings/Motions+27+June+2012 This motion was deferred from the June 7, 2012 GNSO Council meeting. 3.1 Reading of the motion (Wolf-Ulrich Knoben) 3.2 Discussion and open microphone. 3.3 Vote *_Item 4: Update on the Internationalised Registration Data Working Group (IRD WG) (10 minutes)_* The IRD submitted its final report to the GNSO Council and SSAC on March 3, 2012 for review and approval. This report was requested by the Board in June 2009. The first three recommendations are as follows: 1. ICANN staff should develop, in consultation with the community, a data model for domain registration data. 2. The GNSO council and the SSAC should request a common Issue Report on translation and transliteration of contact information. 3. ICANN staff should work with the community to identify a Registration Data Access Protocol that meets the needs of internationalization. Since then, the SSAC has recommended some substantial changes, including adding a fourth recommendation suggesting that ICANN should take appropriate steps to require gTLD registries and registrars and to persuade ccTLD Registries and registrars to support various standards described in the report. The Council now needs to decide whether to accept the report and forward it to the Board along with the SSAC or whether more work may now be needed by the IRD to address any GNSO questions or concerns before the final report can be approved by the GNSO Council. The GNSO Council will now consider a motion to approve the IRD WG Final Report. Refer to motion https://community.icann.org/display/gnsocouncilmeetings/Motions+27+June+2012 4.1 Reading of the motion (Stéphane van Gelder) 4.2 Discussion and open microphone 4.3 Vote *_Item 5: Update on the GNSO-Requested WHOIS Studies and the draft WHOIS Technical Requirements Survey being developed by the WHOIS Survey Working Group (20 minutes) _* The Whois Studies Working Group (WSWG) has a draft survey out for public comment at the moment and a draft report from Interisle on the feasibility of conducting a full study on Privacy and Proxy Relay and Reveal cases has also been posted for public comment. This agenda item is to update the Council on these initiatives. Interisle Consulting Group draft Report – Public comment announcement -- http://www.icann.org/en/news/public-comment/whois-pp-survey-04jun12-en.htm Whois Studies Working Group (WSWG) Public comment announcement -- http://www.icann.org/en/news/public-comment/draft-whois-requirements-survey-... General updated information on WHOIS Studies: http://gnso.icann.org/en/issues/whois/studies 5.1 Update from Staff (Liz Gasster) 5.2 Discussion and open microphone *_Item 6: Update on the RAA negotiations (10 minutes) _* ICANN staff has posted the status report on the RAA negotiations Staff is currently pursuing with the Registrar Stakeholder Group. This agenda item is to inform the Council on the status of these negotiations. 6.1 Update from Staff (Margie Milam) 6.2 Discussion and open microphone. *_Item 7: GNSO Council leadership elections (15 minutes) _* Between this Open Council meeting and the next, in Toronto, the GNSO Council will have started another election cycle. The election is for the new Council Chair, the current Chair being term limited and unable to stand again. Each house will also nominate its Vice Chair. This agenda item aims to provide a short overview of the process and proposed timing. 7.1 Update from Chair (Stéphane Van Gelder) 7.2 Discussion and open microphone. *_Item 8: Registration Abuse Policies Working Group (RAP WG) on Uniformity of Reporting (10 minutes) _* At its meeting on 6 October, 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: indentify 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. Refer to the report http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-uni... The Council must now decide what next steps to take, if any. 8.1 Update from Staff (Marika Konings) 8.2 Discussion and open microphone 8.3 Next steps *_Item 9: 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 comes online and the Registry and Registrar stakeholder groups are affected by this. 9.1 Discussion and open microphone. *_Item 10: 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. 10.1 Discussion and open microphone. *_Item 11: 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 <http://gnso.icann.org/issues/frn/fake-renewal-notices-report-06mar12-en.pdf>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-21ma...) and has now closed. At its last meeting, the GNSO Council requested the 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 (see http://gnso.icann.org/mailing-lists/archives/council/msg13234.html). 1. Presentation of updated Fake Renewal Notices Report (Mikey O'Connor) 2. Discussion and open microphone 3. Next steps *_Item 12: Any Other Business (5 minutes) _* 12.1 New GNSO Website <http://gnso.icann.org/en/>Reactions, comments and any suggestions for improvements/changes *_Item 13: 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 March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 13:00 ---------------------------------------------------------------------------- California, USA (PDT <http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 06:00 New York/Washington DC, USA (EDT) UTC-5+1DST 09:00 Buenos Aires, Argentina (ART <http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 10:00 Montevideo, Uruguay (UYT <http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+0DST 11:00 London, United Kingdom (BST) UTC+1DST 14:00 Abuja,Nigeria (WAT <http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 14:00 Tunis, Tunisia (CET) UTC+1+0DST 14:00 Bonn, Germany (CEST) UTC+1+1DST 15:00 Paris, France (CEST) UTC+1+1DST 15:00 Prague, Czech Repub.(CEST) UTC+1+1DST 15:00 Ramat Hasharon, Israel(IST <http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.h...>) UTC+2+0DST 16:00 Karachi, Pakistan (PKT <http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html>) UTC+5+0DST 18:00 Beijing/Hong Kong, China _(HKT_ ) UTC+8+0DST 21:00 Tokyo, Japan (JST <http://www.timeanddate.com/library/abbreviations/timezones/asia/jst.html>) UTC+9+0DST 22:00 Wellington, New Zealand (NZDT <http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html>) UTC+12+0DST 01: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