October 2013 - council - lists.icann.org

FW: GNSO Council Meeting 10 October 2013 / String Similarity Issues
by Jonathan Robinson 10 Oct '13

10 Oct '13

All, I have sent this information to Christine Willett in order to assist her with preparing for today's council meeting. Jonathan -----Original Message----- From: Jonathan Robinson [mailto:jonathan.robinson@ipracon.com] Sent: 10 October 2013 11:15 To: Christine Willett (christine.willett(a)icann.org) Cc: Akram Atallah (akram.atallah(a)icann.org); Cyrus Namazi (cyrus.namazi(a)icann.org) Subject: GNSO Council Meeting 10 October 2013 / String Similarity Issues Dear Christine, First, thank-you for agreeing to engage with the Council on this topic. In this context, I thought it may be helpful to forward to you (See below) a couple of emails on the subject of your participation. Specifically, Thomas Rickert's question (which I expect he may ask on the call, so it will be helpful if you are able to address it directly) seeks to understand what is the scope of the GNSO Council's potential response. Essentially, my sense is that Council recognises a problem, has drawn the board's additional attention to it and is willing to assist in fixing it if possible. But, in order for any Council initiative to be constructive, we need to know the scope of what is possible from a legal perspective. Therefore, as far as I can see it, the essence of the questions from the GNSO Council will be along the following lines: 1. Has ICANN already come to a conclusion on how it will deal with the apparent inconsistencies in outcomes? (including when compared to one another and when referenced against original, relevant GNSO policy) 2. Is there any (legal) advice that the Council should consider when thinking about policy recommendations to remedy the inconsistencies? If we can get past 1 and 2 above, the Council may well be in a position to recommend the formation of a group to rapidly address and suggest remedial measures to deal with the apparent inconsistencies. I trust that this is helpful additional information and context and look forward to talking with you later today. Best wishes, Jonathan -----Original Message----- From: Thomas Rickert [mailto:rickert@anwaelte.de] Sent: 06 October 2013 13:27 To: john(a)crediblecontext.com Cc: council(a)gnso.icann.org Subject: Re: [council] Inviting Christine Willett to our next meeting John, I guess this is a good idea. I also think that it would be good if someone could say something about the legal side of things that might impact / limit the scope of the ways forward we may consider. Thanks, Thomas Am 04.10.2013 um 17:46 schrieb john(a)crediblecontext.com: > Jonathan, > > In as much as we have a discussion of string confusion on our agenda and that new gTLD program manager Christine Willett has recently discussed ICANN's focus on "inconsistencies" (http://www.icann.org/en/news/press/kits/video-willett-new-gtld-17sep13-en.h tm) it might serve our understanding to have her participate. > > Cheers, > > Berard

1 0

GNSO Council Action Items
by Jonathan Robinson 10 Oct '13

10 Oct '13

All, Regarding the GNSO Council Action Items, at our last meeting, we agreed to confirm the requirement with respect to the following: BGC Recommendation on Reconsideration Request 13-3 1. The Chair, on behalf of the GNSO Council, writes to the Board Governance Committee (copying the New gTLD Programme Committee). Jeff Neumann to draft 2. The Chair, on behalf of the GNSO Council, writes to the ATRT2. A volunteer to draft. a. To highlight concerns with the reconsideration process as a mechanism for ensuring accountability and transparency. b. To not propose a specific remedy but rather to leave that to the ATRT. 3. The Chair, on behalf of the GNSO Council, writes to the ICANN Board. Jonathan to draft. a. To summarise and refer to both 1 & 2 above b. To highlight on-going concerns about the issue of accountability for actions (implementation or policy) which are not in agreement with GNSO policy or policy advice. c. To propose solutions such as: - Agreement to effectively communicate with the GNSO in the event that a decision goes against such policy or policy advice (something we have already agreed to on the back of our Beijing / recent discussions) - Possible change/s to the ICANN bylaws Having seen the outcome of the latest reconsideration request i.e. as follows: Based on the foregoing, the BGC concludes that Booking.com has not stated proper grounds for reconsideration and we therefore recommend that Booking.com's request be denied without further consideration. This Request challenges a substantive decision taken by a panel in the New gTLD Program and not the process by which that decision was taken. As stated in our Recommendation on Request 13-2, Reconsideration is not a mechanism for direct, de novo appeal of staff or panel decisions with which the requester disagrees, and seeking such relief is, in fact, in contravention of the established processes within ICANN. It strikes me that point 2 above, assisted by the latest reconsideration decision, remains valid. Looking at points 1 & 3 above, it strikes me that 1 is no longer required and has been dealt with by other communications and actions but 3 may still be valid. Therefore, please can you assist me by confirming (or denying) that going forwards, we should complete the action by: 1. Dropping Action 1 above 2. Completing Action 2 above (If so, a volunteer to draft please?) 3. Completing 3 above. Thank-you. Jonathan

2 3

Comment Periods Extended, Aligned to Maximize Public Input
by Glen de Saint Géry 10 Oct '13

10 Oct '13

http://www.icann.org/en/news/announcements/announcement-09oct13-en.htm 9 October 2013 Comment Periods Extended, Aligned to Maximize Public Input To provide more opportunity for community consideration and public comment on a draft ICANN Vision and 5-year Strategic Plan, the development schedule has been extended to accommodate two rounds of online public input, and community discussions at the ICANN Buenos Aires<http://buenosaires48.icann.org> (November 2013) and Singapore<http://meetings.icann.org/> (March 2014) meetings. In addition, to more tightly link the multi-stakeholder processes used for developing ICANN's strategic, operating and budget plans, as well as for commenting on the ICANN Strategy Panels<http://www.icann.org/en/news/announcements/announcement-15jul13-en.htm>, the schedules for these processes have been aligned. Specifically, public comment schedules for Strategic Planning, Strategy Panels, and the Operating Plan and Budget have been adjusted to maximize community input. The corresponding schedules are illustrated<http://www.icann.org/en/news/announcements/announcement-09oct13-en.htm#sche…> below. Strategy Panels - To provide more opportunity for community consideration and public comment on the Panels' output-and to more clearly connect the Panels to ICANN's multi-stakeholder strategic, operational, and budget planning processes, the Panels' schedule has been escalated. ICANN President and CEO, Fadi Chehadé, is asking the Panels to provide strategic recommendations by the end of January 2014. (Panel membership will be announced shortly). Panel output will be posted for public comment 31 January-31 March 2014, and will be discussed by the community at the ICANN Singapore meeting in March. This allows time for public discussion and community engagement on the Panels' output, and integration of comments and recommendations into the Final Strategic Plan, as appropriate. This schedule also enables the Panels' recommendations to be factored into the FY2015 Operating Plan and Budget, which currently is scheduled for Board action by 21 June 2014. Strategic Planning - The First Draft of an ICANN Vision and 5-year Strategic Plan will be posted on or before 28 October 2013 for public comment through January 2014. This will include community discussions at the ICANN meeting in Buenos Aires next month. Factored into the First Draft will be the extensive public input received thus far on ICANN's key challenges and opportunities<https://myicann.org/join-strategy-conversation?language=en> and on the eight strategic areas<http://www.icann.org/en/about/planning/strategic-engagement/conversation-in…> [PDF, 209 KB] highlighted by ICANN's Board of Directors. Work and input on related initiatives, such as the Security, Stability & Resiliency Framework, and the Regional Engagement Strategies, also will inform the First Draft. Comments received on the First Draft, as well as on the output of the Strategy Panels, will be considered and incorporated, as appropriate, into a Final Draft. The Final Draft of ICANN's Vision and 5-year Strategic Plan will be posted for public comment by early March 2014 and discussed by the community at the ICANN meeting in Singapore, before being finalized at the end of April 2014 and submitted for Board action. Operational Plan & Budget - The schedule for development of, and comment on, the FY2015 Operational Plan and Budget is expected to run from January - June 2014. The draft schedule is illustrated below and is expected to include public comment and community discussion for the proposed FY2015 Operating Plan beginning in January, followed by comment and discussion of the proposed FY 2015 Budget beginning in April. This will include opportunities for community engagement on the proposals at the ICANN Buenos Aires and Singapore meetings. The FY2015 Operating Plan and Budget is schedule for Board approval by 21 June 2014. A final schedule for this process will be posted on 15 November 2013. See announcement for diagram http://www.icann.org/en/news/announcements/announcement-09oct13-en.htm Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Seconds for the Motions for GNSO Council Meeting - 10 October 2013
by Jonathan Robinson 10 Oct '13

10 Oct '13

All, Please be aware of the motions proposed for our meeting on Thursday. https://community.icann.org/display/gnsocouncilmeetings/Motions+10+Oct.+2013 Note that I have proposed all three motions and that none have been seconded so far. Given that we have a lot to get through on Thursday, it will be helpful if these can be seconded ahead of the meeting. Any seconds for any of the motions please? Jonathan

2 2

Resolution on New gTLD Collision Occurrence Management from the new gTLD committee meeting 7 Oct 2013
by Bruce Tonkin 09 Oct '13

09 Oct '13

From: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-07oct13… 1. Main Agenda: a. New gTLD Collision Occurrence Management Whereas, on 15 March 2013, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 057: SSAC Advisory on Internal Name Certificates. Whereas, in response to the overall issues highlighted in SAC 057, the ICANN Board directed the President and CEO, in consultation with the SSAC, to commission a study on the use of TLDs that are not currently delegated at the root level of the public DNS (the "Name Collision Study"). Whereas, the Name Collision Study, together with a proposal to manage the risks identified in the Name Collision Study (the "Proposal") was published for public comment from 5 August to 17 September. The Proposal has been revised in response to public comments. Whereas, the NGPC is undertaking this action pursuant to the authority granted to it by the Board on 10 April 2012, to exercise the ICANN Board's authority for any and all issues that may arise relating to the New gTLD Program. Resolved (2013.10.07.NG01), the NGPC directs the President, Generic Domains Division to implement the proposal to manage the occurrence of collisions between new gTLDs and existing private uses of the same strings as presented in the "New gTLD Collision Occurrence Management Plan" attached as Annex 1 (http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1… ) and in doing so to take into account further advice that may be offered by SSAC and other experts and stakeholders. Resolved (2013.10.07.NG02), the NGPC directs the ICANN President and CEO, and as appropriate through the President, Generic Domains Division, to appropriately target the planned outreach campaign. The NGPC also recommends to the Board that: (1) the ICANN Board Risk Committee expressly reviews this matter and reports back to the Board, and continues to review and report at regular intervals; (2) the Board directs the ICANN President and CEO to develop a long-term plan to manage name collision at the root; and (3) the Board directs the ICANN President and CEO to work with the community to develop a long-term plan to retain and measure root-server data.

1 0

TR: GNSO Council Abstention Notification Form [#132]
by Glen de Saint Géry 08 Oct '13

08 Oct '13

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : mardi 8 octobre 2013 22:35 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#132] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Tuesday, October 8, 2013 GNSO Organization: * Non-Commercial Stakeholder Group Officer Position or Title: * Chair Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * In the unlikely but possible event that Joy Liddicoat drops-off the line during a vote of the 10 Oct. GNSO Council meeting, then David Cake will hold Joy's proxy during her absence. Joy will be participating in the meeting via telephone while traveling and it is possible that her connection could be dropped during a vote. Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * any and all Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, October 11, 2013 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * David Cake

1 0

Updated proposed agenda for the GNSO Council Meeting 10 October 2013 at 18:00UTC
by Glen de Saint Géry 08 Oct '13

08 Oct '13

Dear Councillors, Please find the updated proposed agenda for the GNSO Council Meeting 10 October 2013 at 18:00UTC. The updates consist of shortening the agenda and changing the order of the items. This agenda was established according to the GNSO Council Operating Procedures approved 13 September 2012 for the GNSO Council and updated. <http://gnso.icann.org/en/council/op-procedures-13jun13-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 18:00 UTC<http://tinyurl.com/bojlrbx> http://tinyurl.com/lc97zd8 Coordinated Universal Time 18:00 UTC 11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 07:00 Wellington 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 audio cast http://stream.icann.org:8000/gnso.m3u Item 1: Administrative matters (10 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 1 August 2013<http://gnso.icann.org/en/meetings/minutes-council-01aug13-en.htm> posted as approved on 6 September 2013 Minutes of the GNSO Council meeting 5 September 2013<http://gnso.icann.org/mailing-lists/archives/council/msg15019.html> to be posted as approved on 10 October 2013 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) After careful review of the GNSO Project List, the Council Chairs propose to formally close the following projects and remove them from the Project List, noting that either work is being undertaken on the subject outside of the GNSO and/or that no further GNSO activity is foreseen in the near future. The projects are as follows: * Fake renewal notices * Defensive registrations Note: Any Council member can re-open the discussion on any of these items in the future, should it be deemed necessary. Item 4: MOTION - To approve the report of the Whois Survey Working Group (WSWG) (10 mins) This report<http://gnso.icann.org/en/issues/whois/wswg-final-21aug13-en.pdf> was published in response to a request by the GNSO Council for a report and analysis on a survey about possible technical requirements of a future WHOIS Service. The objective of the Working Group was to develop a set of proposed recommendations around the measurement of support of proposed technical requirements. After consideration of community input on a draft survey and the implementation of the Lime Survey software within the ICANN IT infrastructure, the survey was made available to the community in September 2012. ICANN staff compiled and consolidated the survey results and the WSWG completed the WSWG Final Report<http://gnso.icann.org/en/issues/whois/wswg-final-21aug13-en.pdf> for delivery to the GNSO Council. Here the Council will vote whether to approve the report. 4.1 - Review motion 1<https://community.icann.org/display/gnsocouncilmeetings/Motions+10+Oct.+2013> 4.2 - Discussion 4.3 - Next steps Item 5: MOTION - Motion to approve the further development of a framework for cross community working groups (10 mins) This motion seeks further develop a framework for cross community working groups by picking up the work of the drafting team which proposed a set of Draft Principles for Cross Community Working Groups<http://gnso.icann.org/drafts/draft-principles-for-cwgs-23dec11-en.pdf> (CCWGs) that were approved<http://gnso.icann.org/en/council/resolutions#201203> by the GNSO Council in March 2012. This work has had the benefit of subsequent review, comments and suggestions<http://gnso.icann.org/en/drafts/ccnso-comments-cwg-principles-11jun13-en.pdf> provided by the ccNSO. The motion here proposes that, in full cooperation with other SO/ACs,the GNSO Council jointly develops an updated set of principles for CCWGs taking into consideration the feedback provided by the ccNSO and in collaboration with other interested SO/ACs. The aim being to to create a framework applicable across all SO/ACs for the effective future functioning of CCWGs 5.1 - Review motion 2<https://community.icann.org/display/gnsocouncilmeetings/Motions+10+Oct.+2013> 5.2 - Discussion 5.3 - Next steps Item 6: MOTION - To approve a charter for the Translation and Transliteration of Contact Information PDP Working Group (10 mins) On 13 June 2013 the GNSO Council initiated a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information and decided to create a PDP Working Group for the purposes of fulfilling the requirements of the PDP. Following a call for volunteers, a Drafting Team was formed and its members have developed a charter for consideration by the GNSO Council. The drafting team has submitted the charter and so the GNSO Council, having reviewed the charter, will vote on whether to approve it as submitted by the Drafting Team. 6.1 - Review motion 3<https://community.icann.org/display/gnsocouncilmeetings/Motions+10+Oct.+2013> 6.2 - Discussion 6.3 - Next steps Item 7: DISCUSSION - Policy issues surrounding string confusion (10 mins) The Council previously discussed issues associated with the string confusion decisions that have been made recently e.g. relating to plural and singular versions of the same term and the contradictory decisions on identical strings. The Council agreed to write to the ICANN board and new gTLD programme committee<http://gnso.icann.org/en/correspondence/robinson-to-crocker-chalaby-18sep13…> and to consider appropriate additional action. Here the Council needs to decide what, if any, additional and appropriate action is to be taken. 7.1 Input from ICANN staff 7.2 Discussion 7.3 Next steps Item 8: UPDATE & DISCUSSION - A PDP for relevant policies on issues not dealt with during the course of developing the 2013 RAA (10 mins) ICANN staff has prepared a paper<http://gnso.icann.org/en/issues/raa/negotiations-conclusion-16sep13-en.pdf> to summarise the outcomes of the 2013 Registrar Accreditation Agreement (RAA) negotiations in order to set the scene for subsequent, relevant policy development work to be managed by the Council. This will be an ICANN Board initiated PDP. Here the Council will receive an update from staff and confirm the intended course of action. 8.1 Staff update (Margie Milam / Mary Wong) 8.2 Discussion 8.3 Next steps Item 9: Procedure to elect the GNSO Council Chair (10 minutes) We have previously used an election procedure. Here we will review a current version of the same procedure<http://gnso.icann.org/elections/proposed-council-chair-02oct13-en.pdf> with a view to approving it for use in the run up to and during the course of the 2013 annual meeting in Buenos Aires. 9.1 Presentation of procedure (Jonathan Robinson) 9.2 Discussion 9.3 Call to approve the procedure Item 10: UPDATE & DISCUSSION - Protection of IGO-INGO Identifiers in all gTLDs Policy Development Process (10 mins) The WG Chair will provide an update on status of WG deliberations and the public comment<http://www.icann.org/en/news/public-comment/igo-ingo-final-20sep13-en.htm> solicitation process for the draft Final Report<http://gnso.icann.org/en/issues/igo-ingo-final-20sep13-en.pdf>. This PDP WG was formed to develop a set of policy recommendations to address the issue of whether and if so, what types of protections should be provided for the identifiers of certain IGOs and INGOs including the RCRC and IOC at the top and second levels in all gTLDs. For further information please see: http://gnso.icann.org/en/group-activities/active/igo-ingo. 10.1 - Review of proposed WG recommendations (Thomas Rickert) 10.2 - Discussion 10.3 - Next steps Item 11: UPDATE & DISCUSSION - Planning for Buenos Aires (10 mins) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Buenos Aires will take planning. GNSO Council Vice Chair, Wolf-Ulrich Knoben has again volunteered to lead this and will be working with the Council and staff on this effort. Here the Council has the opportunity to feed into plans and provide input based on past experience. Included in this item will be the opportunity to shape the approach to and substance of the Council's proposed meetings with other groups in such as the CCNSO, the GAC and the ICANN board. 11.1 - Update<http://gnso.icann.org/en/drafts/buenos-aires-schedule-07oct13-en.pdf> (Wolf-Ulrich Knoben) 12.2 - Discussion 12.3 - Next steps Item 12: INPUT & DISCUSSION - Prospective improvements to the Policy Development Process (10 mins) The Council is committed to on-going enhancements to the methods of working of the Council and the work initiated and managed by the Council. The PDP process is a cornerstone of policy making within the GNSO and, as such, the work of the Council. The PDP outcomes and associated processes are the subject of focus and attention both within the GNSO and the broader ICANN Community. The Council has previously discussed a paper prepared by ICANN staff<http://gnso.icann.org/en/drafts/pdp-improvements-22aug13-en.pdf> on potential improvements to the PDP process and agreed to tabulate and review the prospective improvements with a view to agreeing concrete next steps. 12.1 - Review of table of prospective PDP Improvements (Marika Konings) 12.2 - Discussion 12.3 - Next steps Item 13: 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.) ---------------------------------------------------------------------------- Local time between March and October, Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 18:00 ---------------------------------------------------------------------------- California, USA (PST<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-8+1DST 11:00 New York/Washington DC, USA (EST) UTC-5+1DST 14:00 Rio de Janiero, Brazil (BRST) UTC-3+1DST 15:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-3+1DST 16:00 London, United Kingdom (BST) UTC+0DST 19:00 Abuja, Nigeria (WAT<http://www.timeanddate.com/library/abbreviations/timezones/africa/wat.html>) UTC+1+0DST 19:00 Bonn, Germany (CEST) UTC+1+0DST 20:00 Stockholm, Sweden (CET) UTC+1+0DST20:00 Istanbul, Turkey (EEST) UTC+2+0DST 21:00 Ramat Hasharon, Israel(IST<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+2+0DST 21:00 Karachi, Pakistan (PKT<http://www.timeanddate.com/library/abbreviations/timezones/asia/pkt.html> ) UTC+5+0DST 23:00 Beijing/Hong Kong, China (HKT ) UTC+8+0DST 02:00 (next day) Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+0DST 02:00 (next day) Wellington, New Zealand (NZDT<http://www.timeanddate.com/library/abbreviations/timezones/pacific/nzdt.html> ) UTC+12+1DST 07:00 (next day) ---------------------------------------------------------------------------- DST starts/ends on last Sunday of Oct 2013, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com - http://tinyurl.com/lc97zd8 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

2 1

Project list
by Glen de Saint Géry 08 Oct '13

08 Oct '13

Dear Councillors, In preparation for the Council meeting on 10 October 2013, attached please find the red line and the clean version of the Projects List for your review. The Projects List is also posted at: http://gnso.icann.org/meetings/projects-list.pdf Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Inviting Christine Willett to our next meeting
by john＠crediblecontext.com 08 Oct '13

08 Oct '13

Jonathan, In as much as we have a discussion of string confusion on our agenda and that new gTLD program manager Christine Willett has recently discussed ICANN's focus on "inconsistencies" (http://www.icann.org/en/news/press/kits/video-willett-new-gtld-17sep13-en.h…) it might serve our understanding to have her participate. Cheers, Berard

3 2

Motions for GNSO Council Meeting - 10 October 2013
by Jonathan Robinson 08 Oct '13

08 Oct '13

All, Please be aware of the motions proposed for our meeting on Thursday. https://community.icann.org/display/gnsocouncilmeetings/Motions+10+Oct.+2013 Note that I have proposed all three motions and that none have been seconded so far. Given that we have a lot to get through on Thursday, it will be helpful if these can be seconded ahead of the meeting. So, any seconds for any of the motions please? Jonathan

1 0