Thanks Osvaldo,
At the very least, the cadence as proposed doesn’t seem to reflect any sense of urgency.
It also seems that the review itself the timeline seems very lengthy: to consider a year or more for both the internal landscape assessment and its implications seems
like a long time.
Regarding structural review and ICANN org, I am pretty sure that over the last 25 years, the corporation has undergone significant structural changes already – if anything
the compliance and policy teams seem to have. To me, it’s more a question of suggesting optimal structural elements, new ones for example, to ICANN org to map a new structure than doing a thorough review and potentially revamp the whole org structure. Just
my 2 cents.
I suggest we go over this at our next call on Monday, and consider a call for the small team on this topic.
Regards,
Philippe
From: anil Jain via ispcp <ispcp@icann.org>
Sent: Tuesday, May 12, 2026 5:14 PM
To: Osvaldo Novoa <osvaldo.j.novoa@gmail.com>
Cc: ispcp@icann.org
Subject: [ispcp] Re: Review of Reviews
|
CAUTION : This email originated outside the company. Do not click on any links or open attachments
unless you are expecting them from the sender. |
|
ATTENTION : Cet e-mail provient de l'extérieur de l'entreprise. Ne cliquez pas sur les liens ou n'ouvrez
pas les pièces jointes à moins de connaitre l'expéditeur. |
Dear all,
I agree with Osvaldo regarding structural review.
Let me study ATRT proposal and come back.
Anil
Anil Kumar Jain
On Tue, 12 May 2026 at 16:10, Osvaldo Novoa via ispcp <ispcp@icann.org> wrote:
Dear all,
I am enclosing the presentation of the Draft proposal for future reviews that will be presented during ICANN 86. This document has been prepared by the chairs of the CCG and will be discussed in the group during the following weeks.
I personally have some objections to the proposal.
The proposal for the ATRT review I think it is quite vague in its scope, it will be decided after a process within and between the SO/AC and NC, which seems quite complicated and lengthy.
The Structural reviews is propose to be done every 15 years after the implementation of the previous Structural Review recommendations. This implementation may take years, look at the NomCom changes, so I propose to reduce this period to 10 years. There is no review of the Board or ICANN org, which I think should also be reviewed. Regarding ICANN org I consider that its structure and operation should be reviewed, not the individual personnel.
On Demand Reviews. I consider that the SSR and RDS should be periodic reviews since it is fundamental ensure that ICANN’s performance is up to standards.
These are just some of my observations, I think our constituency should present comments on this proposal in line with the letter sent to the Board and our previous submittals to the CCG.
Best regards,
Osvaldo
_______________________________________________
ispcp mailing list -- ispcp@icann.org
To unsubscribe send an email to ispcp-leave@icann.org
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
_______________________________________________ ______________________________ ______________________________ _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.