January 2016 - council - lists.icann.org

Motion to Adopt the Final Issue Report on a PDP to Review all RPMs in all gTLDs
by Amr Elsadr 11 Jan '16

11 Jan '16

Hi, Please find attached to this email a motion to adopt the final issue report on the PDP to review all RPMs. There is a link in the motion to the page on the GNSO website for this PDP, but the final issue report hasn’t been uploaded there yet (I’m sure it’ll be up there soon). Lars circulated the report on this list a little earlier today, and I’ve attached it to this email as well. The motion includes some information on how this PDP will be conducted over two phases, which should also be described in detail in the report itself (although I haven’t had time to read it yet). The motion also clarifies that the review of RPMs for all gTLDs will be within the scope of this PDP, and additionally addresses how this work will be coordinate with the PDP on new gTLDs subsequent procedures. Thanks. Amr

2 1

Updated proposed Agenda for the Special GNSO Council Meeting on 14 January 2016 at 12:00 UTC.
by Glen de Saint Géry 11 Jan '16

11 Jan '16

Dear Councillors, Please find the updated proposed Agenda for the Special GNSO Council Meeting on 14 January 2016 at 12:00 UTC. https://community.icann.org/display/gnsocouncilmeetings/Agenda+14+January+2… http://gnso.icann.org/en/meetings/agenda-council-14jan16-en.htm https://community.icann.org/display/gnsocouncilmeetings/Motions+14+January+… The update relates to the additional sub-items in Item 2, namely: Item 2: Opening Remarks (5 minutes) 2.1 - Overview of the purpose of this special Council meeting (James Bladel) 2.2 - Explanation of format of response to the CCWG 2.3 - Scope of Council consideration of the substance of the response to the CCWG This agenda was established according to the GNSO Council Operating Procedures,<http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> approved and updated on 24 June 2015. 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. Coordinated Universal Time: 12:00 UTC http://tinyurl.com/ha4rugt 04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Istanbul; 23:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________________ Item 1: Administrative matters (5 minutes) 1.1 - Roll call 1.2 - Updates to Statements of Interest 1.3 - Review/amend agenda. Item 2: Opening Remarks (5 minutes) 2.1 - Overview of the purpose of this special Council meeting (James Bladel) 2.2 - Explanation of format of response to the CCWG 2.3 - Scope of Council consideration of the substance of the response to the CCWG Item 3: VOTE ON MOTION - GNSO Endorsement of the Third Draft Proposal from the Cross-Community Working Group on ICANN Accountability (90 minutes) In the course of discussions over the IANA stewardship transition, the community had raised concerns about ICANN's accountability, given ICANN's historical contractual relationship with the United States government. The community discussions indicated that existing ICANN accountability mechanisms do not yet meet some stakeholders' expectations. As that the U.S. government (through the National Telecommunications and Information Administration (NTIA)) has stressed that it expects community consensus on the transition, this gap between the current situation and stakeholder expectations needed to be addressed. This resulted in the creation<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en…> of a Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability<https://community.icann.org/x/ogDxAg>) of which the GNSO is a chartering organization. In May 2015, the CCWG-Accountability published<https://www.icann.org/public-comments/ccwg-accountability-draft-proposal-20…> an initial proposal regarding its work on Work Stream 1 (meant to align with the timing of the IANA stewardship transition) for public comment. In August 2015, the CCWG-Accountability published<https://www.icann.org/public-comments/ccwg-accountability-2015-08-03-en> its Second Draft Proposal for public comment. This second proposal included significant changes to the initial document, arising from feedback received in the first public comment period. Following community input, including from the ICANN Board, and discussions at several sessions during ICANN54, the CCWG-Accountability made further adjustments to its draft recommendations, resulting in its Third Draft Proposal that was published<https://www.icann.org/public-comments/draft-ccwg-accountability-proposal-20…> for public comment on 30 November 2015. The comment period closed on 21 December 2015, with all Chartering Organizations expected to consider whether to adopt the recommendations in time for the CCWG-Accountability to send its final report on Work Stream 1 to the ICANN Board by late January 2016. Concurrently, the IANA Stewardship Transition Coordination Group (ICG) - the community group formed to consolidate the various proposals relating to the IANA stewardship transition submitted by the Internet communities affected by the issue - announced<https://www.icann.org/news/announcement-2015-10-29-en> after ICANN54 that it had completed its task. However, before the ICG can send its consolidated proposal to the NTIA via the ICANN Board, it will first have to confirm with the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (CWG-Stewardship<https://community.icann.org/display/gnsocwgdtstwrdshp/CWG+to+Develop+an+IAN…>) that its accountability requirements have been met by the Work Stream 1 recommendations from the CCWG-Accountability. In this regard, the CWG-Stewardship had submitted a public comment which, while noting that several of the CCWG-Accountability's latest recommendations adequately satisfied the CWG-Stewardship's requirements, nevertheless highlighted a number of points that in its view merited further attention. In order to meet the CCWG-Accountability's planned timeline, the GNSO Council had agreed at its December 2015 meeting to form a Sub Team that was to review all the various public comments from the GNSO's Stakeholder Groups and Constituencies. Here the Council will discuss the status of the work of the Sub Team, and if appropriate vote on whether to adopt the CCWG-Accountability's recommendations. 3.1 - Summary and update from GNSO Council Sub-Team (James Bladel / Philip Corwin / Keith Drazek / Paul McGrady / Edward Morris) 3.2 - Discussion 3.3 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+14+January+…> (James Bladel) 3.4 - Vote on motion (voting threshold: simple majority) 3.5 - Next steps Item 4: Any Other Business (10 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<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 12: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-7+1DST 04:00 San José, Costa Rica UTC-6+0DST 06:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+0DST 06:00 New York/Washington DC, USA (EST) UTC-5+0DST 07:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 09:00 Rio de Janiero, Brazil (BRST) UTC-2+0DST 10:00 London, United Kingdom (BST) UTC+0DST 12:00 Bonn, Germany (CET) UTC+1+0DST 13:00 Cairo, Egypt, (EET) UTC+2+0DST 14:00 Istanbul, Turkey (EEST) UTC+3+0DST 14:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 20:00 next day Singapore (SGT) UTC +8 20:00 Sydney/Hobart, Australia (AEDT) UTC+11+0DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2016, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/ha4rugt Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Final Issue Report on a PDP to Review all RPMs in all gTLDs
by Lars Hoffmann 11 Jan '16

11 Jan '16

Dear Councillors, For your consideration, please find attached the Final Issue Report on a Policy Development Process to Review All Rights Protection Mechanisms in All Generic Top-Level Domains. A motion to launch a PDP should be submitted shortly. Please note, the report is based on the Preliminary Issue Report <http://gnso.icann.org/en/issues/new-gtlds/rpm-prelim-issue-09oct15-en.pdf> and the feedback submitted through the public comment forum <https://www.icann.org/public-comments/rpm-prelim-issue-2015-10-09-en> . If you have any questions on procedure or substance, please do not hesitate to contact either Mary Wong or myself. Many thanks and best wishes, Lars --- Lars Hoffmann | Policy Manager lars.hoffmann(a)icann.org | +1 310-804-2586 ICANN | Internet Corporation for Assigned Names and Numbers

1 0

Policy Development Process (PDP) Updates
by Glen de Saint Géry 08 Jan '16

08 Jan '16

Dear Councillors, In an effort to assure that the GNSO and wider ICANN community stays informed in these busy times, we would like to remind you that the GNSO support staff puts out monthly PDP Updates. The latest version can be found here: http://gnso.icann.org/en/issues/pdp-updates Please feel free to share this with your colleagues and any other interested parties. Many thanks and best wishes, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Document and Motion deadline Monday, 11 January 2016 at 23:59 UTC for Council meeting 21 January 2016 at 21:00 UTC
by Glen de Saint Géry 08 Jan '16

08 Jan '16

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 11 January 2016 at 23:59 UTC) of the GNSO Council meeting on 21 January 2016 at 21:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+21+January+… Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Charter for New gTLD Subsequent Procedures
by Austin, Donna 07 Jan '16

07 Jan '16

Hi All Happy New Year I see by the Council list that many of you have not stopped to rest during the holiday season. I'm not wishing to add to the burden of workload, but I'm interested to know if we have an update on the status of Charter for New gTLD Subsequent Procedures, in particular, whether we will be in a position to reconsider a motion to approve the Charter at our meeting on 21 January 2016. >From memory, I think Susan, Phil and Paul were going to review the Charter provided in the Final Issues Report to ensure that there is no duplication or overlap of Rights Protection Mechanisms given the issue appears as an item in the Subsequent Procedures Final Issue Report and is also being considered in a stand-alone Issues Report on the Review of all RPMs in all gTLDs. I am happy to contribute to this effort if required in order to move this along if required. Thanks in advance Donna Donna Austin: Neustar, Inc. Policy and Industry Affairs Manager Cell: +1.310.890.9655 Email: donna.austin(a)neustar.biz<mailto:donna.austin@neustar.biz> ________________________________ The information contained in this e-mail message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this e-mail message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify me immediately and delete the original message. Follow Neustar: [cid:image001.png@01CC3CD3.5F595DC0] Facebook<http://www.facebook.com/neustarinc> [cid:image002.png@01CC3CD3.5F595DC0] LinkedIn<http://www.linkedin.com/company/5349> [cid:image003.png@01CC3CD3.5F595DC0] Twitter<http://www.twitter.com/neustar> P Please consider the environment before printing this e-mail.

1 0

Proposed agenda for the Special GNSO Council Meeting of 14 January 2016 at 12:00UTC
by Glen de Saint Géry 06 Jan '16

06 Jan '16

Dear Councillors, Please find the proposed agenda for the Special GNSO Council Meeting of 14 January 2016 at 12:00UTC This agenda was established according to the GNSO Council Operating Procedures,<http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> approved and updated on 24 June 2015. 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. Coordinated Universal Time: 12:00 UTC http://tinyurl.com/ha4rugt 04:00 Los Angeles; 07:00 Washington; 12:00 London; 14:00 Istanbul; 23:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________________ Item 1: Administrative matters (5 minutes) 1.1 - Roll call 1.2 - Updates to Statements of Interest 1.3 - Review/amend agenda. Item 2: Opening Remarks (5 minutes) 2.1 - Overview of the purpose of this special Council meeting (James Bladel) Item 3: Consent agenda (0 minutes) Item 4: VOTE ON MOTION - GNSO Endorsement of the Third Draft Proposal from the Cross-Community Working Group on ICANN Accountability (90 minutes) In the course of discussions over the IANA stewardship transition, the community had raised concerns about ICANN's accountability, given ICANN's historical contractual relationship with the United States government. The community discussions indicated that existing ICANN accountability mechanisms do not yet meet some stakeholders' expectations. As that the U.S. government (through the National Telecommunications and Information Administration (NTIA)) has stressed that it expects community consensus on the transition, this gap between the current situation and stakeholder expectations needed to be addressed. This resulted in the creation<http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en…> of a Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability<https://community.icann.org/x/ogDxAg>) of which the GNSO is a chartering organization. In May 2015, the CCWG-Accountability published<https://www.icann.org/public-comments/ccwg-accountability-draft-proposal-20…> an initial proposal regarding its work on Work Stream 1 (meant to align with the timing of the IANA stewardship transition) for public comment. In August 2015, the CCWG-Accountability published<https://www.icann.org/public-comments/ccwg-accountability-2015-08-03-en> its Second Draft Proposal for public comment. This second proposal included significant changes to the initial document, arising from feedback received in the first public comment period. Following community input, including from the ICANN Board, and discussions at several sessions during ICANN54, the CCWG-Accountability made further adjustments to its draft recommendations, resulting in its Third Draft Proposal that was published<https://www.icann.org/public-comments/draft-ccwg-accountability-proposal-20…> for public comment on 30 November 2015. The comment period closed on 21 December 2015, with all Chartering Organizations expected to consider whether to adopt the recommendations in time for the CCWG-Accountability to send its final report on Work Stream 1 to the ICANN Board by late January 2016. Concurrently, the IANA Stewardship Transition Coordination Group (ICG) - the community group formed to consolidate the various proposals relating to the IANA stewardship transition submitted by the Internet communities affected by the issue - announced<https://www.icann.org/news/announcement-2015-10-29-en> after ICANN54 that it had completed its task. However, before the ICG can send its consolidated proposal to the NTIA via the ICANN Board, it will first have to confirm with the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (CWG-Stewardship<https://community.icann.org/display/gnsocwgdtstwrdshp/CWG+to+Develop+an+IAN…>) that its accountability requirements have been met by the Work Stream 1 recommendations from the CCWG-Accountability. In this regard, the CWG-Stewardship had submitted a public comment which, while noting that several of the CCWG-Accountability's latest recommendations adequately satisfied the CWG-Stewardship's requirements, nevertheless highlighted a number of points that in its view merited further attention. In order to meet the CCWG-Accountability's planned timeline, the GNSO Council had agreed at its December 2015 meeting to form a Sub Team that was to review all the various public comments from the GNSO's Stakeholder Groups and Constituencies. Here the Council will discuss the status of the work of the Sub Team, and if appropriate vote on whether to adopt the CCWG-Accountability's recommendations. 4.1 - Summary and update from GNSO Council Sub-Team (James Bladel / Philip Corwin / Keith Drazek / Paul McGrady / Edward Morris) 4.2 - Discussion 4.3 - Presentation of the motion<https://community.icann.org/display/gnsocouncilmeetings/Motions+14+January+…> (James Bladel) 4.4 - Vote on motion (voting threshold: simple majority) 4.5 - Next steps Item 5: Any Other Business (10 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<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 12: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-7+1DST 04:00 San José, Costa Rica UTC-6+0DST 06:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-6+0DST 06:00 New York/Washington DC, USA (EST) UTC-5+0DST 07:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 09:00 Rio de Janiero, Brazil (BRST) UTC-2+0DST 10:00 London, United Kingdom (BST) UTC+0DST 12:00 Bonn, Germany (CET) UTC+1+0DST 13:00 Cairo, Egypt, (EET) UTC+2+0DST 14:00 Istanbul, Turkey (EEST) UTC+3+0DST 14:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 20:00 next day Singapore (SGT) UTC +8 20:00 Sydney/Hobart, Australia (AEDT) UTC+11+0DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of October 2016, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> http://tinyurl.com/ha4rugt Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

TR: Board with GNSO - ICANN 55
by Glen de Saint Géry 06 Jan '16

06 Jan '16

FYI De : Megan Bishop Envoyé : jeudi 7 janvier 2016 00:34 À : Glen de Saint Géry Objet : Board with GNSO - ICANN 55 Dear Glen, Happy New Year! Just confirming the GNSO's joint meeting with the ICANN Board for Sunday, 6 March from 1pm-2:30pm in Marrakech. Thank you, Megan Megan Bishop Board Operations Coordinator Internet Corporation of Assigned Names and Numbers (ICANN) 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 One World. One Internet.

1 0

GNSO Council meeting dates and times for 2016
by Glen de Saint Géry 05 Jan '16

05 Jan '16

Dear Councillors, The GNSO Council meeting dates and times for the whole year 2016 are posted on the GNSO website on page: http://gnso.icann.org/en/group-activities/calendar In particular see: http://gnso.icann.org/en/group-activities/calendar#jan 4 January Motions and Documents Due for GNSO Council Meeting 14 January 11 January Motions and Documents Due for GNSO Council Meeting 21 January 14 January GNSO Council Teleconference 12:00 UTC 21 January GNSO Council Teleconference 21:00 UTC http://gnso.icann.org/en/group-activities/calendar#feb 8 February Motions and Documents Due for GNSO Council Meeting 18 February 18 February GNSO Council Teleconference 12:00 UTC 28 February Motions and Documents Due for GNSO Council Meeting 9 March 9 March ICANN Meeting - Public Council meeting Marrakech 13:30 Local Time Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Re: [council] Re: Draft minutes of the GNSO Council meeting on Thursday 17 December 2015
by James M. Bladel 05 Jan '16

05 Jan '16

Hi Heather - The next regular Council meeting will be on 21 JAN. the 14 JAN meeting is a special session for consideration of the CCWG-Accountabilty response. Hope this helps. Thanks-- J. From: <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Heather Forrest <Heather.Forrest(a)acu.edu.au<mailto:Heather.Forrest@acu.edu.au>> Date: Tuesday, January 5, 2016 at 16:35 To: GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>> Subject: [council] Re: Draft minutes of the GNSO Council meeting on Thursday 17 December 2015 Dear colleagues, I'm catching up on our December meeting, unfortunately having missed it. May I just quickly confirm that the Motion on Adoption of the Final Report from Privacy & Proxy Services Accreditation Issues PDP Working Group is deferred to our upcoming 14 January meeting? Many thanks and best wishes, Heather ________________________________ From: owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org> <owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org>> on behalf of Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>> Sent: Monday, January 4, 2016 4:09 To: GNSO Council List (council(a)gnso.icann.org<mailto:council@gnso.icann.org>) Subject: [council] Draft minutes of the GNSO Council meeting on Thursday 17 December 2015 Dear Councillors, Attached, please find the draft minutes of the GNSO Council meeting on 17 December 2015 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 14 January 2016. GNSO Operating Rules and Procedures<http://gnso.icann.org/en/council/op-procedures-24jun15-en.pdf> gnso.icann.org GNSO Operating Procedures, Version 3.0 Page 5 between a candidate and "none of above," a second election will be held no sooner than 30 days. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

2 1