May 2013 - council - lists.icann.org

Resolutions from new gTLD committee meeting on 18 May 2013 in Amsterdam
by Bruce Tonkin 21 May '13

21 May '13

Hello All, From: http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-18may13… Approved Resolution | Meeting of the New gTLD Program Committee 18 May 2013 1. Consent Agenda: a. Approval of Minutes of New gTLD Program Committee Meeting of 26 March 2013, 5 April 2013 and 11 April 2013 Resolved (2013.05.18.NG01), the New gTLD Program Committee approves the minutes of the 26 March 2013, 5 April 2013 and 11 April 2013 Meetings of the New gTLD Program Committee. b. BGC Recommendation on Reconsideration Request 13-1 Whereas, Ummah's Digital, Ltd.'s ("Ummah") Reconsideration Request, Request 13-1, sought reconsideration of the staff conclusion that the Ummah gTLD application "is ineligible for further review under the New gTLD Program," which was based on the Support Applicant Review Panel (SARP) determination that Ummah's application did not meet the criteria for financial assistance. Whereas, the BGC recommended that Reconsideration Request 13-1 be denied because Ummah has not stated proper grounds for reconsideration, and Ummah's stay request fails to satisfy the Bylaws' requirements for a stay. Whereas, the BGC noted that "Ummah raises some interesting issues in its Request and suggests that the Board direct that the concerns raised in Ummah's Request be included in a review of the Applicant Support Program so that the design of future mechanisms to provide financial assistance and support in the New gTLD Program can benefit from the experiences within this first round." Resolved (2013.05.18.NG02), the New gTLD Program Committee adopts the recommendation of the BGC that Reconsideration Request 13-1 be denied on the basis that Ummah has not stated proper grounds for reconsideration and that Ummah's stay request fails to satisfy the Bylaws' requirements for a stay. Resolved (2013.05.18.NG03), the Board directs the President and CEO to include the concerns raised in Ummah's Reconsideration Request in the review of the Applicant Support Program so that the design of future mechanisms to provide financial assistance and support in the New gTLD Program can benefit from the experiences within this first round. c. BGC Recommendation on Reconsideration Request 13-2 Whereas, Reconsideration Request 13-2, sought reconsideration of: (1) Staff and Board inaction on the consideration of Nameshop's letter of "appeal" sent after denial of Nameshop's change request to change its applied-for string in the New gTLD Program from .IDN to .INTERNET (the "Change Request"); and (ii) the decision of the Support Applicant Review Panel ("SARP") that Nameshop did not meet the criteria to be eligible for financial assistance under ICANN's Applicant Support Program. Whereas, the BGC recommended that Reconsideration Request 13-2 be denied because Nameshop has not stated proper grounds for reconsideration. Whereas, the BGC concluded that the Reconsideration Request 13-2 challenges: (i) an "appeal" process that does not exist; and (i) the substantive decisions taken within the New gTLD Program on a specific application, not the processes by which those decisions were taken and that the reconsideration process is not, and has never been, a tool for requestors to seek the re-evaluation of decisions. Resolved (2013.05.18.NG04), the New gTLD Program Committee adopts the BGC's recommendation that Reconsideration Request 13-2 be denied on the basis that Nameshop has not stated proper ground for reconsideration. Rationale for Resolution 2013.05.18.NG04 .... Request 13-2 challenges an "appeal" process that does not exist, and challenges the substantive decisions taken in implementation of the New gTLD Program on a specific application and not the processes by which those decisions were taken. Reconsideration is not, and has never been, a tool for requestors to seek the re-evaluation of substantive decisions. This is an essential time to recognize and advise the ICANN community that the Board is not a mechanism for direct, de novo appeal of staff (or evaluation panel) decisions with which the requester disagrees. Seeking such relief from the Board is, in itself, in contravention of established processes and policies within ICANN. 2. Main Agenda: a. Addressing GAC Advice from Beijing Communique No resolution taken.

1 0

Action items arising from GNSO Council meeting 16 May 2013
by Glen de Saint Géry 21 May '13

21 May '13

Dear Councillors, Please find a list of the action items aring from the Council meeting on 16 may 2013 for your review and action. Please let me know if you have any questions. Thank you very much. Kind regards, Glen https://community.icann.org/display/gnsocouncilmeetings/Action+Items Item 2: Opening Remarks from Chair Jonathan Robinson provided a brief review of the Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Arising from the Action list<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>: · Write to Jean-Francois Baril leading the Expert Working Group (EWG) on Directory Services, to confirm the objective of EWG recommendations Jonathan Robinson committed to writing the letter very shortly · GNSO Review - form small committee to consider issues and possible next steps in relation to the GNSO review. Additional work needed. Further information to be circulated shortly. · Policy vs Implementation - reached out to other SO/ACs to determine interest in joining GNSO WG/DT to explore issues further. Team of volunteers is being formed Item 4: MOTION - To address the Final Issue Report on the Uniformity of Reporting Action Item: Create a drafting team to develop a charter for a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the investigation. Item 5: MOTION - To adopt revised Policy Development Process (PDP) Manual incorporating modifications to include the suspension of a PDP Action Item: ICANN staff to post the new version of the PDP Manual and to include it as a revised Annex 2 in the GNSO Operating Procedures, effective immediately upon adoption. Item 7: UPDATE & DISCUSSION - Report on User Experience Implications of Active Variant TLDs & IDN Letter to the Board Action Item: The council is urged to provide input on: a) Which recommendations if any, are pre-requisites to the delegation of any IDN variant TLDs (i.e., delegation of IDN Variant TLDs should not proceed until these recommendations are implemented), b) Which recommendations, if any, can be deferred until a later time, and c) Which recommendations, if any, require additional policy work by the ICANN community and should be referred to the relevant stakeholder group for further policy work Jonathan Robinson committed to work with Ching Chiao to finalise the draft letter<http://gnso.icann.org/mailing-lists/archives/council/msg14489.html> and send it to the ICANN Board Item 8: UPDATE & DISCUSSION - Planning for Durban Action Items: Provide timely feedback to Wolf-Ulrich Knoben · On discussion topics with the ICANN Board, Government Advisory Committee, and CEO Fadi Chehadé. · Time-slot for Constituency/Stakeholder Group meeting on Sunday, 14 July 2013. Provide timely feedback to John Berard and Petter Rindforth on topics for discussion with the ccNSO. Item 9: Any Other Business 9.1 - Updated dates for Q4 2013 GNSO Council meetings. Changed to accommodate Buenos Aires meeting dates. Council accepted the new proposed dates. Action Item: New dates to be posted on calendar<http://gnso.icann.org/en/group-activities/calendar> 9.2 - Additional day for Buenos Aires. Induction and preparation session for the new GNSO Council. Action Item: Diarize Friday, 22 November 2013 as an additional day in Buenos Aires for the induction and preparation session for the new GNSO Council. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

2 1

Draft minutes of the GNSO Council meeting 16 May 2013
by Glen de Saint Géry 21 May '13

21 May '13

Dear Councillors, Attached please find the draft minutes of the GNSO Council meeting held on 16 May 2013. 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/gnso-operating-procedures-13sep12-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 30 May 2013. 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

GNSO Council teleconference, Thursday, 14 March 2013 MP3 recording & Adobe chat transcript
by Glen de Saint Géry 17 May '13

17 May '13

Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 16 May 2013 at: http://audio.icann.org/gnso/gnso-council-20130516-en.mp3 on page http://gnso.icann.org/en/group-activities/calendar#may The Adobe chat transcript may be viewed at: http://gnso.icann.org/en/group-activities/calendar#may http://gnso.icann.org/en/meetings/transcript-chat-council-16may13-en.pdf 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

GNSO Council Motions adpoted on Thursday, 16 May 2013
by Glen de Saint Géry 16 May '13

16 May '13

Dear Councillors, The following motions were adopted at the Council meeting on Thursday, 16 May 2013. Motion 1: Address the Final Issue Report on the Uniformity of Reporting ========================================================= Whereas, The Registration Abuse Policies Working Group (RAPWG) identified in its Final Report the 'need for more uniformity in the mechanisms to initiate, track, and analyze policy-violation reports'; The RAPWG as a result recommended in its Final Report that 'the GNSO and the larger ICANN community in general, create and support uniform reporting processes'. The GNSO Council at its meeting on 6 October 2011 requested ICANN Compliance Department to report on existing systems to report and track violations and/or complaints; improvements / changes made since the RAPWG Report or foreseen in the near future, and: identify gaps and any improvements that might be desirable but not foreseen at this stage; The ICANN Compliance Department provided a response to the GNSO Council on 18 March 2012 and presented it to the GNSO Council at its meeting on 12 April 2012 (see http://gnso.icann.org/issues/rap/contractual-compliance-report-reporting-un…); The GNSO Council discussed the RAPWG recommendation in light of the feedback received from the ICANN Compliance Department and RAPWG Alumni volunteered to provide some further thoughts on how the RAPWG recommendation could be implemented; RAPWG Alumni submitted their proposed approach to the GNSO Council on 3 September 2012 (see http://gnso.icann.org/mailing-lists/archives/council/msg13484.html); The GNSO Council reviewed and discussed the proposed approach at its meeting on 13 September 2012; The GNSO Council requested an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyze policy-violation reports. ICANN Staff completed and released the Preliminary Issue Report on Uniformity of Reporting on 22 March 2013 for public comment. No comments were received; ICANN Staff submitted the Final Issue Report to the GNSO Council on 2 April 2013 (see http://gnso.icann.org/en/issues/uofr-final-31mar13-en.pdf). The GNSO Council has reviewed the Final Issue Report and supports the staff recommendation to not initiate a Policy Development Process at this stage but to await the completion of the ICANN Contractual Compliance three-year plan. Resolved, The GNSO Council does not initiate a Policy Development Process at this stage but will review at the completion of the ICANN Contractual Compliance three-year plan expected for 31 December 2013 whether additional action is required; The GNSO Council further approves the creation of a drafting team to develop a charter for a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the investigation. Motion 2: Adopt Revised PDP Manual Incorporating Modifications to Include the Suspension of a PDP =============================================================================== WHEREAS: Having encountered the need to suspend a Policy Development Process (PDP) for a limited amount of time, the GNSO Council realized that currently the PDP Manual does not contain a specific provision on how to deal with such a situation; The GNSO Council requested the Standing Committee on Improvements Implementation (SCI) in April 2012 to review whether there should be a modification to the GNSO PDP Manual to address the possible suspension of a PDP following its initiation; The SCI deliberated on provisions for suspension of a PDP and reached consensus on proposed modifications to be incorporated in Section 15 of the GNSO PDP Manual, which also is included as Annex 2 in the GNSO Council Operating Procedures; The revised PDP manual, including the proposed provisions for suspension of a PDP, was put out for a minimum 21-day public comment period on 06 March 2013 ending on 06 April 2013 (see http://www.icann.org/en/news/public-comment/pdp-suspension-07mar13-en.htm) as required by the ICANN Bylaws; As a result of the public comment period, no further changes were deemed necessary by the SCI; NOW THEREFORE, BE IT RESOLVED The GNSO Council adopts the revised PDP Manual including the providing for the suspension of a PDP (see http://gnso.icann.org/en/council/op-procedures-pdp-redline-03may13-en.pdf) The GNSO Council instructs ICANN staff to post the new version of the PDP Manual and to include it as a revised Annex 2 in the GNSO Operating Procedures, effective immediately upon adoption. 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 Council audio cast link 16 May 2013
by Glen de Saint Géry 16 May '13

16 May '13

GNSO Council meeting audio cast http://stream.icann.org:8000/gnso.m3u 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

TR: GNSO Council Abstention Notification Form [#121]
by Glen de Saint Géry 16 May '13

16 May '13

FYI De : ICANN [mailto:no-reply@wufoo.com] Envoyé : jeudi 16 mai 2013 16:26 À : gnso.secretariat(a)icann.org; council(a)gnso.icann.org Objet : GNSO Council Abstention Notification Form [#121] Name of Officer: * Robin Gross Officer Email Address: * robin(a)ipjustice.org<mailto:robin@ipjustice.org> Date Prepared: * Thursday, May 16, 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: * David Cake is unable to attend the 16 May 2013 GNSO Council Meeting and Wolfgang Kleinwachter will serve as David's proxy. 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, May 17, 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: * Wolfgang Kleinwachter

1 0

Durban meeting
by WUKnoben 16 May '13

16 May '13

All, under item 8 of today’s agenda we’ll discuss the planning for Durban. For your preparation I attach a list of categorized proposed topics. I think the discussion could cover - comprehensiveness of the agenda - topic priorities - ideas with regards to the “Cross Community” meetings Any further input from your side is welcome. As discussed in Beijing, to allow for more room of discussion on the topics Staff will work with WG Chairs and other presenters to ensure that presentations during the weekend session focus on the substance of the issue, while any background information is either included as an annex to the presentation or covered in a separate paper to allow those that are new or unfamiliar with the issue to prepare accordingly. Looking forward to the meeting today Wolf-Ulrich

2 2

REMINDER: GNSO Council meeting Agenda & Projects List
by Glen de Saint Géry 16 May '13

16 May '13

Dear Councillors, In preparation for the Council meeting today, please find the agenda and attached the red line and the clean version of the Projects List for your review. Agenda for GNSO Council Meeting - 16 May 2013 http://gnso.icann.org/en/group-activities/calendar#may http://gnso.icann.org/en/meetings/agenda-council-16may13-en.htm On the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Agenda+16+May+2013 The motions are published on page: https://community.icann.org/display/gnsocouncilmeetings/Motion+16+May+2013 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/gnso-operating-procedures-13sep12-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/d7gphxh Coordinated Universal Time 18:00 UTC 11:00 Los Angeles; 14:00 Washington; 19:00 London; 20:00 Paris; 06: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. Item 1: Administrative matters (10 minutes) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Draft Minutes of the GNSO Council meeting 10 April 2013 posted on 11 May 2013 1.5. GNSO Projects List http://gnso.icann.org/meetings/projects-list.pdf & Action items<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> · Review main changes. · Comments and/or questions. Item 2: Opening Remarks from Chair (10 minutes) Review focus areas and provide updates on specific key themes / topics Include brief review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items> Item 3: Consent agenda ([0] minutes) TBC. Item 4: MOTION - To address the Final Issue Report on the Uniformity of Reporting (10 minutes) At its October meeting last year the GNSO Council requested an Issue Report on the current state of uniformity in the mechanisms to initiate, track, and analyse policy-violation reports. ICANN Staff was also explicitly requested to provide its recommendation(s) on how this issue can be further addressed outside of a PDP if recommendations in relation to this issue do not require consensus policies to implement. The Final Issue Report<http://gnso.icann.org/en/issues/uofr-final-31mar13-en.pdf> was presented to the GNSO Council in Beijing. The Council will now consider a motion to form a non-PDP Working Group to consider additional methods for collecting necessary metrics and reporting from Contracted Parties and other external resources to aid the policy development process as outlined in the Final Issue Report. Link to motion https://community.icann.org/display/gnsocouncilmeetings/Motion+16+May+2013 4.1 Reading of the motion (Wolf-Ulrich Knoben). 4.2 Discussion of motion. 4.3 Vote. (Threshold: Simple majority of Both 4 CPH, 7 NCPH) Item 5: MOTION - To adopt a revised Policy Development Process (PDP) Manual incorporating modifications to include the suspension of a PDP (10 minutes) In April 2012 the GNSO Council requested the Standing Committee on Improvements Implementation (SCI) to review whether or not there should be a modification to the GNSO PDP Manual to address the possible suspension of a PDP following its initiation; The SCI deliberated on provisions for suspension of a PDP and reached consensus on proposed modifications to be incorporated in Section 15 of the GNSO PDP Manual, which also is included as Annex 2 in the GNSO Council Operating Procedures; The revised PDP manual, including the proposed provisions for suspension of a PDP, was put out for a minimum 21-day public comment period on 06 March 2013 ending on 06 April 2013 (see http://www.icann.org/en/news/public-comment/pdp-suspension-07mar13-en.htm) as required by the ICANN Bylaws. The GNSO Council will now consider a motion to adopt the revised GNSO Operating Procedures. Link to motion https://community.icann.org/display/gnsocouncilmeetings/Motion+16+May+2013 5.1 Reading of the motion (Wolf-Ulrich Knoben). 5.2 Discussion of motion. 5.3 Vote (Threshold: Simple majority of Both 4 CPH, 7 NCPH) Item 6: MOTION - Initiation of a Policy Development Process (PDP) on the Translation and Transliteration of Contact Information (10 minutes) A Final Issue Report translation and transliteration of contact information was submitted to the GNSO Council on 21 March 2013 (see http://gnso.icann.org/en/library). The Final Issue Report recommends that the GNSO Council should initiate a Policy Development Process (PDP) limited to the issues discussed in this report but delay the next steps in the PDP until the Expert Working Group on gTLD Directory Services completes its recommendations, in May 2013 with a possible extension, in order to ensure that the resulting policy recommendations would be consistent with any new model or approaches to contact data that may result from the Expert Working Group's deliberations; As recommended by the WHOIS Policy Review Team the Final Issue Report also recommends that ICANN should commission a study on the commercial feasibility of translation or transliteration systems for internationalized contact data, which is expected to help inform the PDP Working Group in its deliberations; ICANN's General Counsel has confirmed that the topic is properly within the scope of the ICANN policy process and within the scope of the GNSO. An overview of the Final Report was provided in Beijing. The Council is now expected to consider whether or not to initiate a PDP. 6.1 Reading of the motion (Ching Chiao) 6.2 Discussion 6.3 Vote (Threshold: 33% of Both 3 CPH, 5 NCPH; OR 66% of ONE 5 CPH, 9 NCPH) Item 7: UPDATE & DISCUSSION - Report on User Experience Implications of Active Variant TLDs & IDN Letter to the Board (20 mins) During its meeting in Beijing, the ICANN Board requested that, by 1 July 2013, interested Supporting Organizations and Advisory Committees provide staff with any input and guidance they may have to be factored into implementation of the Recommendations from the Report on User Experience Implications of Active Variant TLDs<http://www.icann.org/en/resources/idn/variant-tlds/active-ux-21mar13-en.pdf>' (see http://www.icann.org/en/groups/board/documents/prelim-report-11apr13-en.htm…). The Report on User Experience Implications of Active Variant TLDs examines potential challenges from a user experience perspective when variants of IDN TLDs are activated and offers recommendations to users to minimize risks and optimize the implementation. Ideally, input is requested on: a) Which recommendations if any, are pre-requisites to the delegation of any IDN variant TLDs (i.e., delegation of IDN Variant TLDs should not proceed until these recommendations are implemented), b) Which recommendations, if any, can be deferred until a later time, and c) c) Which recommendations, if any, require additional policy work by the ICANN community and should be referred to the relevant stakeholder group for further policy work Furthermore, it was suggested that the GNSO Council should send a letter to the Board highlighting the importance of IDN related issues. A first draft of such letter was sent to the GNSO Council mailing list on 11/4 (see http://gnso.icann.org/mailing-lists/archives/council/msg14489.html). 7.1 Update on Report on User Experience Implications of Active Variant TLDs (Naela Sarras) 7.2 Discussion 7.3 Next steps 7.4 Update on letter to the Board (Ching Chiao) 7.5 Discussion 7.6 Next steps Item 8: UPDATE & DISCUSSION - Planning for Durban (30 minutes) Making the most out of the face-to-face meeting time available at the ICANN Meeting in Durban will take planning. GNSO Council VC Wolf-Ulrich Knoben is working with staff to lead this effort. The Council has the opportunity to feed into plans and provide input based on experience in Beijing. Included in this item will be the opportunity to shape the topics and substance of the Council's proposed meetings with other groups in Durban such as the CCNSO, the GAC and the ICANN board. 8.1 - Update (Wolf-Ulrich Knoben) 8.2 - Discussion 8.3 - Next steps Item 9: Any Other Business (5 minutes) 9.1 - Updated dates for Q4 2013 GNSO Council meetings. Changed to accommodate Buenos Aires meeting dates. 9.2 - Additional day for Buenos Aires. Induction and preparation session for the new GNSO Council. 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 UTC ---------------------------------------------------------------------------- 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 15: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+0DST 20: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 06:00 (next day) ---------------------------------------------------------------------------- The DST starts/ends on last Sunday of October 2013, 2:00 or 3:00 local time (with exceptions) For other times see: http://tinyurl.com/d7gphxh 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

ICANN FY12 Form 990
by Glen de Saint Géry 16 May '13

16 May '13

https://www.icann.org/en/news/announcements/announcement-14may13-en.htm ICANN FY12 Form 990 14 May 2013 ICANN filed its Form 990 for the fiscal year ending 30 June 2012 with the Internal Revenue Service (IRS) on 14 May 2013 in compliance with the extended due date of 15 May 2013. The Form 990 is the United States return for organizations exempt from income taxes under section 501(c) of the Internal Revenue Code. ICANN continues to provide accountability and transparency regarding its financial results and the filed Form 990 is available on the "Financial Information for ICANN<https://www.icann.org/en/about/financials>" page of the ICANN.org site and is also included in this announcement. ICANN's FY12 Form 990 is now posted<https://www.icann.org/en/about/financials/tax/us/fy-2012-form-990-en.pdf> [PDF, 800 KB] and is available to the community. The Community is invited to review ICANN's Form 990 and to provide commentaries and/or questions. 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