- Comments-draft-opplan-budget-fy21-25-20dec19

C. Langdon-Orr Personal Comments re FY21-FY25 Operating and Financial Plan
by Cheryl Langdon-Orr Feb. 24, 2020

Feb. 24, 2020

Please find inline below and attache my personal comments' Firstly as a long-time active ICANN participant and reader of a long history of Operating and Financial Plans, let me note my gratitude and appreciation for the continued improvements in the accessibility of information/data and general readability over the last few years and specifically complement this current document which in my view allows for several ‘levels’ of reader enquiry into the important material and data contained within, in particular, improved cross-referencing and the use of 5 year and 1-year details. Secondly, I also note the overall conservative yet well-considered nature of the planned expenditure, from modest growth predictions, for these operational and strategic activities overall, (a reflection of course of the highly professional work of the team involved with the Plans development and production, however concerning Budget Çontingenecy provision, specifically for New gTLD Subsequent Procedures policy development process • Specific and Organizational Reviews • Policy development and compliance required by the European Union’s General Data Protection Regulation • Cross Community Working Group on Enhancing ICANN Accountability Work Stream 2, all of which I admit I have a keen interest or involvement with, does give me slight I hope unfounded concern, that it may be too conservative and risk some diminution of possible progress or commitment to these activities as they come into play quite possible as processes and projects that overlap in time. Perhaps consideration or a higher provision percentage and then not exceeding expenditure being seen as good fiscal management would be a preferred approach, on these key/critical matters. This would have the added benefit of not risking as likely the need to as was required previously to ‘dip into the Reserve Funds to complete time-critical ICANN/Community activities. Regarding the Annexed Document "Evolving ICANN's Multistakeholder Model Work Plan:" my brief responses to the specific questions posed follow: 1. Are the right entities suggested to take the lead in developing an approach or solution to an identified issue? If not, which entity would be appropriate? - Yes, I believe they are, providing that each sees themselves as the convenor or prime facilitator of an ICANN Community-wide interactive process, that engages the ICANN.Org and relevant staff support.. 2. How can the ICANN community effectively coordinate the work of developing approaches and solutions? - Communication and opportunity for equitable input and interaction (a mix of Face to Face and intercessional work) will be key to this if it is going to be effective or successful within the ICANN-MSM model. Change is always resisted by some in any situation and experienced facilitators or change agents might also be a useful tool to deploy in various stage of these processes. 3. How should the six issues included in the work plan be prioritized? - As one of the Co-Chairs of ATRT3 that is going to make recommendations regarding prioritisation of Key ICANN Activities and Review Team/ CCWG etc., Recommendations to date, I would recommend that specifics of that proposal are applied to these six issues being triaged (sorted in order of action) But my personal view of matters to be addressed would be:- 1. 1st ICANN deal with #6 the delegation of Roles and Responsibilities, (ensuring wider ICANN Community ‘buy-in’; 2. 2nd #5 Precision Scoping (now that GNSO Council has Resolved adoption of PDP 3.0) it is essential to establish with the wider ICANN Community what their opinions/acceptance/reactions to the details of PDP3.0 is across the ACSOs, but also but the most fragile of many of our process plans in ICANN seems to me to be a problem with proper scoping of planned activities. It could be effective and efficient to also deal with #4 Complexity as an issue in parallel with the mater of Scoping. 3. 3rd #1 Consensus, Representatives and Inclusivity, may to some extent be a product of the success (or not) of the other Community interactions relating to the identified Issues. But this could be addressed in parallel to others identified. 4. #2 Prioritisation and Effective Use of Resources and #4 Culture Trust and Silos could be addressed as Overarching issues throughout a process that ques the other matter. <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_m…> Cheryl Langdon-Orr about.me/cheryl.LangdonOrr <https://about.me/cheryl.LangdonOrr?promo=email_sig&utm_source=product&utm_m…>

1 0

ccNSO SOPC comments on the ICANN FY21-25 Operating and Financial Plan
by Giovanni Seppia Feb. 24, 2020

Feb. 24, 2020

Dear ICANN Finance, Please see attached the ccNSO SOPC comments on the ICANN FY21-25 Operating and Financial Plan. As ever, we remain available for any clarification you may need. Kind Regards, Giovanni Seppia [cid:image006.jpg@01D5EAEC.50D7D080]<http://www.eurid.eu/>Giovanni Seppia / External Relations Manager EURid vzw Telecomlaan 9, 1831 Diegem, Belgium T: +32 2 401 27 50 | M: +39 335 8141733 www.eurid.eu<http://www.eurid.eu/> RPR Brussel - VAT BE 0864.240.405 [cid:image003.jpg@01D4F6BF.C28BB830]<https://twitter.com/EUregistry> [cid:image004.jpg@01D4F6BF.C28BB830] <https://www.linkedin.com/company/eurid/> [cid:image005.jpg@01D4F6BF.C28BB830] <https://www.facebook.com/EUregistry> 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. Any processing of personal data via email is done in accordance with our Privacy Policy. 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 https://eurid.eu/en/other-infomation/privacy-policy

1 0

The budget of personal rh
by betty＠ipeos.com Feb. 18, 2020

Feb. 18, 2020

1 0

Comments
by Martin Atayo, Executive-in-Chief/ President Feb. 4, 2020

Feb. 4, 2020

ICANN Committee Team, I am respectfully submitting two suggestionsfor your review and possible adoption that gearto enhance a healthy, safe, and secure digital technology virtual world. The suggestions include: 1) Overhaul of existing third-party registration of ICANN membership with the objective of cancellation, and replacement with direct Domain registration and payment of reasonable and affordable fee into ICANN account thanallowing payment into third-party registration account. This is very necessary for security reasons and elimination of fraud.2) ICANN should introduce in its White papers, strategic security regulations and guidelines as security complexity changes by the day to most troubling online safety and credibility concern. ICANN should develop and make public at its level security and safety guidelines, all ofwhich are independent of IT services providing companies security and safety guidelines. We suggest ICANN may put up suggestions like this to the global public for open discourse,dialogue, and refinement prior to final generally accepted statement version.Thank you for your time. Sincerely, Martin Atayo CEOMPGATECHNOLOGIES CORPP.O.Box 1689Washington DC 20013 Sent from Yahoo Mail on Android

1 0