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

[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

[Comments-reserve-fund-12oct17] ccNSO-SOP sub-group input to the ICANN Reserve Fund Rationale and Target Level
by Giovanni Seppia Nov. 27, 2017

Nov. 27, 2017

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<http://www.eurid.eu/> 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. http://www.eurid.eu/en/legal-disclaimer

1 0

[Comments-reserve-fund-12oct17] ICANN Reserve Fund – Public Comment on Rationale and Target Level
by John Poole Oct. 19, 2017

Oct. 19, 2017

ICANN Reserve Fund – My Comment on Rationale and Target Level I have reviewed the open comment webpage <https://www.icann.org/public-comments/reserve-fund-2017-10-12-en>, read the attachment https://www.icann.org/en/system/files/files/draft- reserve-fund-12oct17-en.pdf, and reviewed other sources of information. I will concede upfront that I probably have a more conservative approach than many in the ICANN community who appear "ready to spend" ICANN's last red cent! For example, without more information, the comparison of ICANN to CIRA, or Nominet, appears ludicrous. ICANN is a unique global organization with immense exposure and unknown, unquantifiable, potential liabilities due to: 1) end of the U.S. government (IANA) contract; and 2) expansion of new gTLDs beginning in 2014 (adding complexity to a system often increases fragility or vulnerabilities). In addition, ICANN is (along with Verisign) one of the most important root server operators upon which the global internet DNS depends. Malicious threats and vulnerabilities, some attacking (or hijacking) the DNS root <https://en.wikipedia.org/wiki/DNS_hijacking>, continue to appear. Network science and technology will continue to evolve, as will vulnerabilities. Research, defense, security, continual improvements, and *incident recovery*, cost money, and catastrophic incident insurance coverage is probably not a viable option. Issues such as have arisen with the Root Zone KSK Rollover, are just the tip of the iceberg. Any event that forced ICANN to seek protection under Chapter 11 of the U.S. Bankruptcy Code could very well end ICANN's role in "coordinating" the internet. For that reason alone, it might be advisable for ICANN to consider "spinning off" its technical and root server operations into a separate "affiliate" (similar to, but separate from, PTI). For the reasons above, I would suggest, at a minimum, an "operating reserves fund <http://www.nonprofitaccountingbasics.org/reporting-operations/about-operati…>" of 24 months Opex. In addition, I suggest ICANN consider creating a "strategic reserves fund <https://en.wikipedia.org/wiki/Strategic_reserve>" of $200 million--funded from the auction proceeds ($235M) and application fees ($128M)--of which $100 million could be released for disbursement after five years if there proves to be "no need" for that level of "strategic reserves," with the balance released five years thereafter if not needed. Sincerely, John Poole Domain Name Registrant and Editor, DomainMondo.com <http://www.DomainMondo.com>

1 0