March 2026 - Inputonreviews

Considerations on reviews
by Osvaldo Novoa March 16, 2026

March 16, 2026

Dear all, These considerations might seem trivial or too evident to make them but I thought that they might clarify my opinion regarding periodical reviews. While in Mumbai and hearing comments regarding the reviews, and in particular de discussion on periodical reviews and on demand reviews, I started thinking on the objectives of a review. Why do we review? A review of a structure, an organization or a process it’s not necessarily to change it. A review allows you to verify that what you are reviewing is functioning as desired, fit for purpose, that you are obtaining the results as designed and if there is a way to improve it. Of course if you detect a problem, being that something is not working as it should or the results are not what was expected, then a review may be needed to detect the causes of the problem. It is preferable to solve any problem that might arise before they happen, this is the reason why I think that the reviews should be, in general, periodical and not on demand. An on demand review is required when a problem or an issue is detected, a periodical review may allow you to detect the problem or the issue before it happens and prevent it from happening. Best regards, Osvaldo Novoa

1 0

some ideas for RoR
by jorge.cancio＠bakom.admin.ch March 12, 2026

March 12, 2026

Dear colleagues Just in case this fits in your discussions, here are some ideas I shared in the chat during the RoR session: * It would be great if it is checked that the process(es) of the reviews is (are) consistent with the Sao Paulo Multistakeholder Guidelines, especially their "process steps". The SPMG were recently recognized by the UNGA in para 94 of the WSIS+20 Outcome Document. More info: https://netmundial.br/netmundial-10-multistakeholder-statement-strengthenin… * A main principle to avoid duplications, overlaps and proliferation of reviews is the functional approach: forms follows function, hence if the scope and function of each review is neatly defined, the risk of duplication/overlap is minimized. This means scrutinizing all reviews, also existing reviews, to make sure no duplications/overlaps exist. * On the triggering of so called "on demand" reviews: here I'm a bit unsure to what extent important existing reviews, such as CCT, are covered. Anyways, it is worth considering not only "positive agreement" triggers, i.e. when a number of SOAC consider a review is due it is started, but also "default triggers unless negative consensus" models, where specific important reviews are automatically triggered, unless SOAC agree that the review is not needed, e.g. because the last one is still valid etc. A "negative agreement" approach is stronger, when you need to avoid collusion or capture, so it is especially useful for reviews that might be thorny for one or two SOACs... which would need to convince the rest about *not* needing a review... Kindly Jorge GAC Rep Switzerland

1 0

RrSG Governance Team Input and Comments
by Prudence Malinki March 11, 2026

March 11, 2026

Hello everyone, Please find attached input and comments from the RrSG Governance Team on the RoR draft proposal. Many thanks, Prudence Malinki Head of Industry Relations, Markmonitor [cid:image001.png@01DCB18E.1B6357C0]

1 0

Fwd: ISPCP input to Review of Reviews Cross-Community Working Group (RoR CCWG)
by Osvaldo Novoa March 5, 2026

March 5, 2026

Please find enclosed ISPCP’s considerations related to a structural review of ICANN. Best regards, Osvaldo Novoa

1 0