November 2017 - comments-reserve-fund-12oct17@icann.org

[Comments-reserve-fund-12oct17] ICANN Reserve Fund - Comment on Rationale and Target Level
by Stephen Deerhake ＠ GDNS Nov. 30, 2017

Nov. 30, 2017

The following comments are in my personal capacity as an ICANN Community member. They draw in part upon the submissions made by the ccNSO-SOP (full disclosure: I am a member of this SOP) and the GNSO Business Constituency (see http://mm.icann.org/pipermail/comments-reserve-fund-12oct17/attachments/201… and http://mm.icann.org/pipermail/comments-reserve-fund-12oct17/attachments/201… respectively). 1. ICANN (non-PTI/IANA) needs at a minimum 18 months of reserve funding at the current budget level. 2. Per the recommendation made by the GNSO Business Constituency, “There should be separate and enhanced Reserve Fund targets specifically related to the PTI and IANA administration budgets”. This recommendation is echoed in the submission of the ccNSO-SOP, which states “…there should be one reserve fund for ICANN and a separate one for PTI.” 3. With respect to the separate reserve fund for PTI/IANA administration budgets, I concur with the submission of the GNSO Business Community that this reserve should cover 36 months “…of expected expenditures.” 4. I concur with the cNSO-SOP “…that it is of paramount importance for ICANN to establish a long-term plan for an adequate reserve fund that could ensure the continuity and reliability of ICANN core tasks.” 5. I fully support the use of the new gTLD auction fee proceeds to fund the two (ICANN and PTI/IANA) reserve funds as a priority over any other use of these funds. It is of paramount importance that ICANN protect itself (and especially, the PTI/IANA function) from a global “Black Swan” event, which seems more likely with each passing day. Sincerely, Stephen Deerhake

1 0

[Comments-reserve-fund-12oct17] Comments on ICANN Reserve Fund
by William Michael Cunningham Nov. 30, 2017

Nov. 30, 2017

Please see the attached. -- Minority and Women-owned Company Small Business Financing Guide and Workbook: https://www.minorityfinance.com/mfinform1.html Twitter: @CreativeInv My new book: The JOBS Act: Crowdfunding for Small Businesses and Startups https://www.amazon.com/JOBS-Act-Crowdfunding-Businesses-Startups/dp/1484224… 202-455-0430 "Evil is not driven out, but crowded out...through the expulsive power of something good. " MLK This communication (including all pages in this email and any attached document) are for the sole use of the intended recipient and may contain confidential information. Unauthorized use, distribution, disclosure or any action taken or omitted to be taken in reliance on this document is prohibited, and may be unlawful. By inadvertent disclosure of this document Creative Investment Research, Inc. and William Michael Cunningham do not waive confidentiality privilege with respect hereto. This writing/publication is a creative work fully protected by all applicable copyright laws, as well as by misappropriation, trade secret, unfair competition and other applicable laws. No copyright is claimed in the text of statutes, regulations, and any excerpts from others’ reports or articles quoted within this work. Copyright©2017 by William Michael Cunningham and Creative Investment Research, Inc. All rights reserved – including the right to reproduce in whole or in part in any form.

1 0

[Comments-reserve-fund-12oct17] RrSG Comment on ICANN Reserve Fund –Rationale and Target Level
by Zoe Bonython Nov. 30, 2017

Nov. 30, 2017

Hello, On behalf of the RrSG, I would like to submit the below comment on the ICANN Reserve Fund - Rationale and Target Level. Kind regards, Zoe Bonython RrSG Secretariat Registrar Stakeholder Group Comment on the ICANN Reserve Fund –Rationale and Target Level The RrSG considers that the proposed ICANN Reserve Funding proposal is well thought out and researched. The use of comparisons to other not-for-profits was appropriate. Estimates of what is needed in reserve are by their nature a series of deductions based on foreseen contingencies. Consequently deliberations about the optimal size of a reserve fund must reflect a number of considerations. What are the reasonable risks? How long must the organization be able to run without revenues? How independent should the ICANN structure be from its sources of revenue? What is lavish and what is a prudent? The Registrars recognize that opinions will differ on reasonable grounds, and as a group they have clear interests to advance and concerns to express. Registrars’ concerns The Registrars are concerned with two questions: the size of the reserves, and therefore the duration of the time that ICANN should be expected to run without further revenues, and the sources of the money intended as reserves: what sources should be used, in what order, and what sources should not be used. Duration of reserves There was no support whatever for a duration of reserves longer than 12 months. Some members considered that even 12 months of funding at current expenditure levels was excessive for the intended purpose of the reserves. Those members stated a preference that the reserves be held strictly for the purpose of winding down ICANN in the event that that becomes necessary. A majority of RrSG members considered that a twelve month reserve suitable for the purpose of running the organization was reasonable. Sources of the reserves It was the strong feeling of the Registrars that ICANN was living on a rich diet, that administration was top-heavy, and this in turn generated a wariness towards allowing one-time uses of reserve funds to make up for budget deficits. It was recognized that benefits once extended, and habits once ingrained, would render it difficult to roll back or restrain. Of supreme importance, Registrars also state their opposition to any proposed increase (temporary or permanent) in Registrar per-domain fees to replenish the reserve fund. Replenishing and maintaining the fund must be incorporated in to ICANN’s budget, and shortfalls should not be borne by registrants, but by cutting expenses elsewhere in the organization. In this regard it was proposed that, for greater transparency on the expense side, Registrars request that ICANN-Finance identify Board expenses directly related to Board governance activities as distinct from those of representing ICANN in various venues. Second, registrars expressed concern that ICANN should not use the gTLD auction proceeds for purposes of replenishing the reserves. The group considers that such an act would run counter to the stated purpose of the gTLD auction proceeds and could set a dangerous precedent for future ICANN funding. If once registrars allowed such a practice, it is believed that ICANN would tend to make a habit of over-spending its budget, drawing down the reserves to cover the shortfall, then replenishing the reserves from the auction fund, thereby turning auction proceeds into an additional source of funding to cover ICANN over-expenditure. According to the New gTLD Auction Proceeds Discussion Paper, Updated[1]the complete set of uses of the auction proceeds have not finally be agreed upon, but no one has contemplated auction proceeds should be used for establishing reserves. It cited the New gTLD Applicant Guidebook as follows: “The purpose of an auction is to resolve contention in a clear, objective manner. It is planned that costs of the new gTLD program will offset by fees, so any funds coming from a last resort contention resolution mechanism such as auctions would result (after paying for the auction process) in additional funding. Any proceeds from auctions will be reserved and earmarked until the uses of funds are determined. Funds must be used in a manner that supports directly ICANN’s Mission and Core Values and also allows ICANN to maintain its not for profit status. Possible uses of auction funds include formation of a foundation with a clear mission and a transparent way to allocate funds to projects that are of interest to the greater Internet community, such as grants to support new gTLD applications or registry operators from communities in subsequent gTLD rounds, the creation of an ICANN-administered/community based fund for specific projects for the benefit of the Internet community, the creation of a registry continuity fund for the protection of registrants (ensuring that funds would be in place to support the operation of a gTLD registry until a successor could be found), or establishment of a security fund to expand use of secure protocols, conduct research, and support standards development organizations in accordance with ICANN's security and stability mission.” New gTLD Applicant Guidebook –Section 4.3. Third, the Registrars considered that, independently of the preceding considerations, other reserves should be used in priority to auction funds, namely the funds set aside as litigation reserves. Accordingly, the registrars consider that a reserve policy must address the issue of the priority of use of various reserve funds: in what order they should be drawn down, and they consider that unused litigation reserves should be used before registrars are called upon to top up general reserves. [1] https://gnso.icann.org/en/drafts/new-gtld-auction-proceeds-07dec15-en.pdf

1 0

[Comments-reserve-fund-12oct17] Business Constituency (BC) comment on ICANN Reserve Fund – Rationale and Target Level
by Steve DelBianco Nov. 30, 2017

Nov. 30, 2017

The ICANN Business Constituency (BC) submits the attached comment on the ICANN Reserve Fund – Rationale and Target Level. ( ICANN comment page at https://www.icann.org/public-comments/reserve-fund-2017-10-12-en ) This comment was drafted by Jimson Olufuye, Jay Sudowski, and Marilyn Cade. It was approved in accord with the BC Charter. — Steve DelBianco Vice chair for policy coordination ICANN Business Constituency

1 0

[Comments-reserve-fund-12oct17] IPC Comments on Reserve Fund
by Lori Schulman Nov. 30, 2017

Nov. 30, 2017

Attached please find the IPC comments. If you have any questions or concerns, please do not hesitate to contact me. Lori Schulman Senior Director, Internet Policy International Trademark Association 1250 Connecticut Avenue, Suite 200 Washington DC, USA +1-202-704-0408, skype: lsschulman www.inta.org<http://www.inta.org/> Find us on: [Description: Description: Description: cid:F361C18F-02FE-4CF0-A43E-AA8566DC2514] Twitter<https://twitter.com/INTA> [Description: Description: LinkedIn] LinkedIn<http://www.linkedin.com/groupInvitation?groupID=69899> [Description: Description: facebook-logo (2)] Facebook<http://www.facebook.com/home.php?#!/GoINTA?ref=ts> [Description: Description: pnpb_sig.png]

1 0

[Comments-reserve-fund-12oct17] i2Coalition comments on the ICANN Reserve Fund - Public Comment on Rationale and Target Level
by Jay Sudowski - Handy Networks LLC Nov. 30, 2017

Nov. 30, 2017

Attached please find the i2Coalition’s comments on ICANN Reserve Fund - Public Comment on Rationale and Target Level. ----- Jay Sudowski // Handy Networks LLC // Co-Founder & CEO i2coalition’s Member Representative to the BC Providing Dedicated Server, IaaS and Colocation Hosting Solutions Tel: 303-414-6902 | Cell: 720-544-1485 | Fax: 303-414-6912 www.handynetworks.com<http://t.sidekickopen04.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XZsQ…>

1 0

[Comments-reserve-fund-12oct17] Pending Ratification: ALAC Statement on the ICANN Reserve Fund – Public Comment on Rationale and Target Level
by ICANN At-Large Staff Nov. 30, 2017

Nov. 30, 2017

Dear All, Kindly find attached the ALAC Statement on the ICANN Reserve Fund – Public Comment on Rationale and Target Level. In the interest of time, the ALAC Chair requested that the Statement be transmitted to the ICANN public comment process, copying the ICANN Staff member responsible for this topic, with a note that the Statement is pending ALAC ratification. ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/atlarge.icann.org> Facebook: facebook.com/icann<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/facebook.com/icannatlar…>atlarge<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/facebook.com/icannatlar…> Twitter: @<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/@ICANNAtLarge>ICANNAtLarge<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/@ICANNAtLarge>

1 0

[Comments-reserve-fund-12oct17] Registries Stakeholder Group (RySG) comments on ICANN Reserve Fund – Public Comment on Rationale and Target Level
by svg＠milathan.ltd Nov. 30, 2017

Nov. 30, 2017

Please find attached, in PDF format, the Registries Stakeholder Group (RySG) comments on ICANN Reserve Fund – Public Comment on Rationale and Target Level. In the interest of time, the RySG did not conduct a formal vote on these comments. They were circulated and debated on our mailing list, with no member expressing opposition to their submission. Please do not hesitate to contact me or any member of the RySG Executive Committee should you have any questions. Best regards, Stéphane Van Gelder RySG Vice Chair (Policy)

1 0

[Comments-reserve-fund-12oct17] Sebastien Bachollet comments regarding “ICANN Reserve Fund Public Comment on Rationale and Target Level”
by Sebicann Bachollet Nov. 29, 2017

Nov. 29, 2017

1 0

Re: [Comments-reserve-fund-12oct17] [Ext] ccNSO-SOP sub-group input to the ICANN Reserve Fund Rationale and Target Level
by Xavier J. Calvez Nov. 27, 2017

Nov. 27, 2017

Giovanni, Many thanks for the work of the ccNSO SOP Working Group in reviewing and submitting comments on this important topic. I have published the comment submitted on the comment forum today. Thank you. Best, Xavier Xavier Calvez ICANN – SVP & CFO 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Phone: 310-301-5838 Mobile: 805-312-0052 Fax: 310-957-2348 From: Giovanni Seppia <Giovanni.Seppia(a)eurid.eu> Date: Monday, November 27, 2017 at 12:26 AM To: "comments-reserve-fund-12oct17(a)icann.org" <comments-reserve-fund-12oct17(a)icann.org> Cc: Xavier Calvez <xavier.calvez(a)icann.org> Subject: [Ext] ccNSO-SOP sub-group input to the ICANN Reserve Fund Rationale and Target Level Dear ICANN Finance, On behalf of the working sub-group set by the ccNSO-SOP at the ICANN60 meeting, please see attached the input to the ICANN Reserve Fund Rationale and Target Level. The working sub-group remains available for any further clarification and/or input you may need. Kind regards, Giovanni Giovanni Seppia External Relations Manager EURid Woluwelaan 150 1831 Diegem - Belgium TEL: +32 (0) 2 401 2750 MOB:+39 335 8141733 giovanni.seppia(a)eurid.eu<mailto:giovanni.seppia@eurid.eu> http://www.eurid.eu[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_&d=DwMFAg&…> Please consider the environment before printing this email. Disclaimer: This email and any attachment hereto is intended solely for the person to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient or if you have received this email in error, please delete it and immediately contact the sender by telephone or email, and destroy any copies of this information. You should not use or copy it, nor disclose its content to any other person or rely upon this information. Please note that any views presented in the email and any attachment hereto are solely those of the author and do not necessarily represent those of EURid. While all care has been taken to avoid any known viruses, the recipient is advised to check this email and any attachment for presence of viruses. Other languages: English[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_en_legal-2…> Estonian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_et_legal-2…> Italian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_it_legal-2…> Maltese[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_mt_legal-2…> Romanian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_ro_legal-2…> Swedish[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_sv_legal-2…> Czech[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_cs_legal-2…> Spanish[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_es_legal-2…> Latvian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_lv_legal-2…> Dutch[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_nl_legal-2…> Slovak[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_sk_legal-2…> Greek[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_el_legal-2…> Danish[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_da_legal-2…> French[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_fr_legal-2…> Lithuanian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_lt_legal-2…> Polish[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_pl_legal-2…> Slovenian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_sl_legal-2…> Bulgarian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_bg_legal-2…> German[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_de_legal-2…> Gaelic[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_ga_legal-2…> Hungarian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_hu_legal-2…> Portuguese[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_pt_legal-2…> Finnish[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_fi_legal-2…> Croatian[eurid.eu]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.eurid.eu_hr_legal-2…>

1 0