January 2015 - council - lists.icann.org

Updated project list for your review
by Glen de Saint Géry 29 Jan '15

29 Jan '15

Dear Councillors, Please find the updates project list for your review. The graphics have also been updated and it has been posted on page : http://gnso.icann.org/en/council/project under the heading Council activities http://gnso.icann.org/meetings/projects-list.pdf Thank you. Kind regards, Glen

1 0

REMINDER: Board/GNSO EWG Process - Invites to GNSO Members
by Glen de Saint Géry 29 Jan '15

29 Jan '15

Dear Councillors, The updated call schedule for this WG can be located on their wiki: https://community.icann.org/pages/viewpage.action?pageId=49359624 The next call is on: * 29 January @ 20:00-21:30 UTC Remote details are also listed at the bottom of that wiki page but I'm including it below as well for ease of reference. You will note that people will join as a "listen-only" participants. Agendas, meeting notes, recordings, etc. all can be located on that wiki page. REMOTE PARTICIPATION DETAILS Link to Adobe Connect: https://icann.adobeconnect.com/ewgprocesswg/ Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (remember to change the Country Code if needed). You will join as a "listen only" participant. If you are unable to log into Adobe Connect and can only join via phone, find your local dial in number here: International Dial-In Numbers<http://tinyurl.com/og9p8aa> and enter Participant Passcode: 910 641 7120 when prompted. 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

GNSO Policy Briefing for Singapore
by Marika Konings 28 Jan '15

28 Jan '15

Dear All, On behalf of the GNSO Policy Team, please find attached the GNSO Policy Briefing (previously known as background briefings) that will hopefully assist you and your respective groups in your preparations for the ICANN meeting in Singapore. Best regards, Marika

1 0

FW: Re: NGPC Resolution 2014.07.30.NG03 on Implementing Name Collision Occurrence
by Jonathan Robinson 28 Jan '15

28 Jan '15

All. FYI Jonathan From: Jonathan Robinson [mailto:jrobinson@afilias.info] Sent: 28 January 2015 09:52 To: 'cyrus.namazi(a)icann.org' Cc: gnso-secs(a)icann.org Subject: Re: NGPC Resolution 2014.07.30.NG03 on Implementing Name Collision Occurrence Dear Cyrus, Please see attached. Best wishes, Jonathan

1 0

Joint CWG-Stewardship & CCWG-Accountability Chairs' Statement
by Glen de Saint Géry 26 Jan '15

26 Jan '15

To view the original announcement, please see: https://www.icann.org/news/announcement-2015-01-26-en Joint CWG-Stewardship & CCWG-Accountability Chairs' Statement Lise Fuhr & Jonathan Robinson - CWG-Stewardship <https://community.icann.org/display/gnsocwgdtstwrdshp/CWG+to+Develop+an+IAN…>Thomas Rickert, León Sanchez, & Mathieu Weill - CCWG-Accountability<https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+A…> As both Cross Community Working Groups prepare for community engagement and work sessions at ICANN52 in Singapore, the Chairs of the CWG-Stewardship and CCWG-Accountability would like to recognize the interdependence and connected nature of the work of their respective groups, as set out by the ICANN processes1<https://www.icann.org/news/announcement-2015-01-26-en#foot1> and further reinforced by each working group's Charter.2<https://www.icann.org/news/announcement-2015-01-26-en#foot2> Following the ICANN 51 Meeting in Los Angeles, the CWG-Stewardship Chairs and the Chairs of the CCWG-Accountability Charter Drafting Team started to hold update and coordination calls, a practical and early recognition of the requirement for active collaboration on their respective work efforts. These weekly interchanges and updates are ongoing and serve to keep each other informed about questions and issues arising from their respective working groups. Moving forward, the Chairs commit to continue to actively work together, and synchronize insofar as possible, on timelines and milestones, especially where there are accountability mechanisms that may be relevant for both groups. To assist in broader community understanding of the interdependencies of the parts of Work Stream 1 that relates to the CWG, a schematic illustration of the dynamics between the two working groups is available in a flowchart<https://community.icann.org/download/attachments/49352017/Link%20with%20CCW…> [PDF, 154 KB]. Work in Progress The CCWG-Accountability has just concluded a two-day meeting<https://www.icann.org/news/announcement-2015-01-23-en> in Frankfurt, Germany (19-20 January), during which they discussed their Work Stream 1 requirements, with initial input from the CWG-Stewardship on accountability dependencies. Both working groups are expected to continue this dialogue as work progresses. The CWG-Stewardship, following an intensive work weekend<https://www.icann.org/news/announcement-2-2015-01-12-en> on 10-11 January, is in the process of reviewing its timeline for submission of a proposal to the IANA Stewardship Transition Coordination Group (ICG). A vital part of this endeavor is the seeking of legal advice on questions related to the viability of key elements of the CWG-Stewardship proposal. As the CCWG-Accountability also moves forward to seek legal advice, the Chairs will inform each other of the process used and advice received, so as to further ensure efficient synchronization in light of dependent and compressed timeframe. ICANN 52 Meeting in Singapore (9-13 February 2015) The Chairs intend to all be present at both CWG-Stewardship and CCWG-Accountability related sessions during the ICANN 52 Meeting in Singapore<http://singapore52.icann.org/en/>, including the ICG-organized events. This will reinforce the working groups' commitment to a productive meeting, advancing discussions and improving collaboration. Below is a compiled list of engagement sessions and working sessions that are relevant to both processes: *All times in local time (UTC +8) IANA Stewardship Transition & Enhancing ICANN Accountability Information Session<http://singapore52.icann.org/en/schedule/sun-iana-stewardship-accountability> Olivia Meeting Room Sunday, 8 February 17:30-19:00 Responses to the ICG RFP Regarding the IANA Stewardship Transition<http://singapore52.icann.org/en/schedule/mon-icg-rfp-iana-stewardship> Padang/Canning Meeting Room Monday, 9 February 10:30-13:00 CCWG-Accountability Working Session<http://singapore52.icann.org/en/schedule/mon-ccwg-accountability> Padang Meeting Room Monday, 9 February 16:00-19:00 CCWG-Accountability Engagement Session<http://singapore52.icann.org/en/schedule/wed-ccwg-accountability> Padang Meeting Room Wednesday, 11 February 9:45-11:15 CWG-Stewardship Working Session<http://singapore52.icann.org/en/schedule/wed-cwg-stewardship> Padang Meeting Room Wednesday, 11 February 17:15-19:15 CCWG-Accountability Working Session<http://singapore52.icann.org/en/schedule/thu-ccwg-accountability> Padang Meeting Room Thursday, 12 February 07:00-10:00 CWG-Stewardship Questions & Answers Session<http://singapore52.icann.org/en/schedule/thu-cwg-stewardship> Padang Meeting Room Thursday, 12 February 10:30-11:45 The full schedule for the ICANN 52 meeting in Singapore is available here<http://singapore52.icann.org/en/schedule-full>. ________________________________ 1<https://www.icann.org/news/announcement-2015-01-26-en#note1> On 6 June 2014, ICANN, in its role as facilitator, published a community-driven process for the IANAStewardship Transition<https://www.icann.org/resources/pages/process-next-steps-2014-06-06-en>. Community discussions on the IANA Stewardship Transition led to the development of an additional process on Enhancing ICANN Accountability<https://www.icann.org/resources/pages/process-next-steps-2014-10-10-en>, which was published on 10 October. 2<https://www.icann.org/news/announcement-2015-01-26-en#note2> The CWG-Stewardship Charter<https://community.icann.org/x/2grxAg> was circulated for adoption on 14 August 2014. The CCWG-Accountability Charter<https://community.icann.org/x/KYMHAw> was circulated for adoption on 3 November 2014.

1 0

ICANN's risk management activities
by Bruce Tonkin 24 Jan '15

24 Jan '15

Hello All, Attached is some information on ICANN's risk management activities that was prepared in response to a question from the Cross-Community Working Group (CCWG) on Enhancing ICANN's accountability. It is publicly available at: https://www.icann.org/en/system/files/files/summary-risk-management-process… I thought you may also find the list useful. Regards, Bruce Tonkin

1 0

ICANN Board Chair letter to the GAC chair - covering responses to GAC advice from the Los Angeles Communiqué
by Bruce Tonkin 23 Jan '15

23 Jan '15

Hello All, Attached is a letter from the ICANN Board chair to the GAC chair. The letter addresses GAC advice regarding implementation of WHOIS-related safeguards; security risks safeguard advice,; the Public Interest Committee Dispute Resolution process; and the WHOIS roadmap. Regards, Bruce Tonkin

1 0

Updated Proposed GNSO Council Teleconference Agenda Thursday, 29 January 2015 at 12:00 UTC.
by Glen de Saint Géry 23 Jan '15

23 Jan '15

Dear Councillors, Please find the updated proposed Agenda for the GNSO Council Teleconference on Thursday, 29 January 2015 at 12:00 UTC. https://community.icann.org/display/gnsocouncilmeetings/Agenda+29+January+2… http://gnso.icann.org/en/meetings/agenda-council-29jan15-en.htm The update is as follows : Item 3 Consent agenda (5 minutes) 3.1 - Approve request for extension of timeline for Issue Report on Rights Protection Mechanisms 3.2 - Approve formation of informal community group to review IDN Implementation Guidelines and approve draft GNSO Council letter in response to these. This agenda was established according to the GNSO Council Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> approved and updated on 13 November 2014. 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 Time 12:00 UTC: http://tinyurl.com/lsupjfs Coordinated Universal Time 12:00 UTC 04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Brussels; 20:00 Perth GNSO Council meeting audio cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (5 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 11 December 2014 will be posted as approved on xxxxx 2015 and the minutes of the 15 January 2015 Council meeting will be posted as approved on XXXX 2015 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) 3.1 - Approve request for extension of timeline for Issue Report on Rights Protection Mechanisms 3.2 - Approve formation of informal community group to review IDN Implementation Guidelines and approve draft GNSO Council letter in response to these. Item 4: UPDATE - Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (30 mins) The CWG<https://community.icann.org/x/37fhAg> has been chartered to develop a proposal on Naming Related Functions for the IANA Stewardship Transition Proposal and has been meeting for 2 hours every week since its creation with a goal of delivering a final proposal by the end of January 2015. The January 2015 target date is driven by the request for proposals from the IANA Stewardship Transition Coordination Group<https://www.icann.org/stewardship/coordination-group> (ICG). It is by now clear that the January target date will not be met and that a new target needs to be agreed. A number of sub-groups were formed to progress work on the different elements of the ICG Request for Proposals and a face-to-face meeting was run in mid-November 2014. A draft proposal was published for community comment on 1 December 2014 and the public comment period has since closed. An intensive work weekend followed on 10 & 11 January 2015 which attempted to systematically review inputs from the public comment. Given the deadlines and associated intensity of the work of the CWG as well as the need for the GNSO as a chartering organisation to approve the proposal, it is relevant for the Council, and through it the GNSO, to receive a full update and to have the opportunity to discuss the work of the CWG. This item will provide an update, create the opportunity for discussion and empahsise the need for the GNSO to be informed about the work of this important group. 4.1 - Update (Jonathan Robinson) 4.2 - Discussion 4.3 - Next steps Item 5: Update: Planning for ICANN meeting in Singapore - key direction & themes (10 mins) 5.1 Update - Volker Greimann 5.2 Open issues / Discussion 5.3 Actions arising Item 6: Any Other Business (5 mins) 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 18: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-8+0DST 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 Rio de Janiero, Brazil (BRST) UTC-2+1DST 10:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 10:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 09: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+2+0DST 14:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 14:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 20:00 Melbourne, Australia (AEDT) UTC+11+1DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/lsupjfs Please let me know if you have any questions. 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

1 0

Proposed GNSO Council Teleconference Agenda Thursday, 29 January 2015 at 12:00 UTC.
by Glen de Saint Géry 22 Jan '15

22 Jan '15

Dear Councillors, Please find the proposed Agenda for the GNSO Council Teleconference on Thursday, 29 January 2015 at 12:00 UTC. https://community.icann.org/display/gnsocouncilmeetings/Agenda+29+January+2… This agenda was established according to the GNSO Council Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> approved and updated on 13 November 2014. 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 Time 12:00 UTC: http://tinyurl.com/lsupjfs Coordinated Universal Time 12:00 UTC 04:00 Los Angeles; 07:00 Washington; 12:00 London; 13:00 Brussels; 20:00 Perth GNSO Council meeting audio cast To join the event click on the link: http://stream.icann.org:8000/gnso.m3u Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (5 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 11 December 2014 will be posted as approved on xxxxx 2015 and the minutes of the 15 January 2015 Council meeting will be posted as approved on XXXX 2015 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 (0 mins) Item 4: UPDATE - Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (30 mins) The CWG<https://community.icann.org/x/37fhAg> has been chartered to develop a proposal on Naming Related Functions for the IANA Stewardship Transition Proposal and has been meeting for 2 hours every week since its creation with a goal of delivering a final proposal by the end of January 2015. The January 2015 target date is driven by the request for proposals from the IANA Stewardship Transition Coordination Group<https://www.icann.org/stewardship/coordination-group> (ICG). It is by now clear that the January target date will not be met and that a new target needs to be agreed. A number of sub-groups were formed to progress work on the different elements of the ICG Request for Proposals and a face-to-face meeting was run in mid-November 2014. A draft proposal was published for community comment on 1 December 2014 and the public comment period has since closed. An intensive work weekend followed on 10 & 11 January 2015 which attempted to systematically review inputs from the public comment. Given the deadlines and associated intensity of the work of the CWG as well as the need for the GNSO as a chartering organisation to approve the proposal, it is relevant for the Council, and through it the GNSO, to receive a full update and to have the opportunity to discuss the work of the CWG. This item will provide an update, create the opportunity for discussion and empahsise the need for the GNSO to be informed about the work of this important group. 4.1 - Update (Jonathan Robinson) 4.2 - Discussion 4.3 - Next steps Item 5: Update: Planning for ICANN meeting in Singapore - key direction & themes (10 mins) 5.1 Update - Volker Greimann 5.2 Open issues / Discussion 5.3 Actions arising Item 6: Any Other Business (5 mins) 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 18: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-8+0DST 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 Rio de Janiero, Brazil (BRST) UTC-2+1DST 10:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 10:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 09: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+2+0DST 14:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 14:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 20:00 Melbourne, Australia (AEDT) UTC+11+1DST 23:00 ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/lsupjfs Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

GNSO Policy & Implementation Working Group Publishes Initial Recommendations Report for Public Comment
by Marika Konings 20 Jan '15

20 Jan '15

For your information, the Policy & Implementation Working Group has published its Initial Recommendations Report<http://gnso.icann.org/en/issues/policy-implementation/pi-wg-initial-recomme…> for public comment. Comments can be submitted through the traditional public comment forum or via a survey that has been developed by the WG (see https://www.surveymonkey.com/s/PI-InitialReport). Best regards, Marika From: ICANN News Alert <communications(a)icann.org<mailto:communications@icann.org>> Reply-To: "communications(a)icann.org<mailto:communications@icann.org>" <communications(a)icann.org<mailto:communications@icann.org>> Date: Monday 19 January 2015 20:08 To: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Subject: ICANN News Alert -- GNSO Policy & Implementation Working Group Publishes Initial Recommendations Report for Public Comment [ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2015-01-19-en ________________________________ GNSO Policy & Implementation Working Group Publishes Initial Recommendations Report for Public Comment 19 January 2015 Forum Announcement: Comment Period Opens on Date: 19 January 2015 Categories/Tags: Policy Processes Purpose (Brief): Mainly as a result of discussions stemming from implementation related issues of the new generic Top-Level Doman (gTLD) program, there has been an increased focus on which topics call for policy and which call for implementation work, including which processes should be used, at what time and how issues which are the subject of diverging opinions during the implementation process should be acted upon. Following several discussions, including the publication of a staff discussion paper and a community session during the ICANN meeting in Beijing in April 2013, the Generic Names Supporting Organization (GNSO) Council decided in July 2013 to form a Working Group (WG) which was tasked to provide the GNSO Council with a set of recommendations on a number of questions that specifically relate to policy and implementation in a GNSO context. The WG has now published its Initial Recommendations Report<http://gnso.icann.org/en/issues/policy-implementation/pi-wg-initial-recomme…> [PDF, 1.46 MB] for community input which can be provided either through input received via this public comment forum or via the following survey: https://www.surveymonkey.com/s/PI-InitialReport Public Comment Box Link: https://www.icann.org/public-comments/policy-implementation-2015-01-19-en This message was sent to marika.konings(a)icann.org<mailto:marika.konings@icann.org> from: ICANN News Alert | communications(a)icann.org<mailto:communications@icann.org> | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Email Marketing by [iContact - Try It Free!] <http://www.icontact.com/a.pl/144186> Manage Your Subscription <http://app.icontact.com/icp/mmail-mprofile.pl?r=11415898&l=6333&s=KUM2&m=95…>

1 0