[NCSG-EC] Fwd: [GNSO-SG-C-Leadership] FW: Pilot Holistic Review

Fri Mar 28 12:28:38 EET 2025

Sorry for not answering before, Rafik - I think it would be great to have
Sophie in our call, I'm curious about some part of the reports she made and
more details are needed to understand better their suggestions.

Cordially,

*Pedro de Perdigão Lana*
Lawyer <https://www.nic.br/>, GEDAI/UFPR <https://www.gedai.com.br/>
Researcher
PhD Candidate (UFPR), LLM in Business Law (UCoimbra)
Coordination/Board/EC @ ISOC Brazil <https://www.isoc.org.br/>, NCUC
<https://www.ncuc.org/> & NCSG
<https://community.icann.org/display/gnsononcomstake/Home>(ICANN) and CC
Brazil <https://br.creativecommons.net/>.
This message is restricted to the sender and recipient(s). If received by
mistake, please reply informing it.

Em seg., 24 de mar. de 2025 às 18:02, Rafik Dammak via NCSG-EC <
ncsg-ec at lists.ncsg.is> escreveu:

> hi all,
>
> we get this update about Pilot holistic review. We already heard about
> some discussion between the team and the SO/AC chair during ICANN82 and the
> topic was also raised during the GNSO council session. Sophie Hey reached
> me out and said she was ready to give NCSG an update, if you agree we can
> invite her to our next NCSG policy call.
> We need to allocate some time to review this and discuss. I am not sure
> about the impact and how that links with other streams.
>
> Best,
>
> Rafik
>
>
> ---------- Forwarded message ---------
>
>
>
>
>    - *Attachments protected by Amazon: *
>    - hey-disspain-to-barrett-13feb25-en.pdf
>    <https://us-west-2.secure-attach.amazon.com/2a369807-637d-42da-9ac1-128616137e0d/7979646a-410f-460a-bf21-3a0ef5566e6f> |
>
>    - ICANN Bylaws Specific Reviews.pdf
>    <https://us-west-2.secure-attach.amazon.com/2a369807-637d-42da-9ac1-128616137e0d/c687ecd1-47a9-41cf-8f37-c53655170771> |
>
>    - pilot-holistic-review-tor-13may24-en.pdf
>    <https://us-west-2.secure-attach.amazon.com/2a369807-637d-42da-9ac1-128616137e0d/7ce5076f-a905-4567-afe7-1a680dd9d1c8> |
>
>    - Current-operating-standards-specific-...9-en.pdf
>    <https://us-west-2.secure-attach.amazon.com/2a369807-637d-42da-9ac1-128616137e0d/51d8b255-c830-4799-96d6-8c0d65de1202> |
>
>
> Amazon has replaced the attachments in this email with download links.
> Downloads will be available until April 23, 2025, 15:06 (UTC+00:00). Tell
> us what you think
> <https://amazonexteu.qualtrics.com/jfe/form/SV_ehuz6zGo8YnsRKK>
> For more information click here
> <https://docs.secure-attach.amazon.com/guide>
>
> Hello SG/C Chairs,
>
>
>
> Please see the below update from the chairs of the Pilot Holistic Review.
> As this was a topic of discussion at ICANN 82, I thought it would be
> helpful to send along.
>
>
>
> Thanks,
>
> Greg
>
>
>
> >
> *Subject:* [EXTERNAL] Pilot Holistic Review
>
>
>
> *CAUTION*: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> TO
>
> Chair of Board
>
> Chair of Board Organisational Effectiveness Committee
>
> Chair of Board Governance Committee
>
> ATRT3 Co-Chairs
>
> SO/AC Chairs
>
>
>
> Dear all,
>
>
>
> We are writing to close the loop on the discussions held during ICANN 82
> on reviews, to the extent that these discussions impact the work of the
> Pilot Holistic Review (PHR). During ICANN 82 the Board held discussions
> with each SO/AC at which the subject of reviews generally and the PHR
> specifically were raised.
>
>
>
> By way of background, we attach our letter to the OEC chair dated 13
> February which explains the lead up to the various discussions that took
> place at ICANN 82.
>
>
>
> What we heard during ICANN 82:
>
>    1. The possibility of suspending all reviews whilst the community
>    worked on a new approach, assessing why we review, what we should review
>    and how best to review.
>    2. The possibility of using ATRT4 to do the above or to replace the
>    PHR and work on the design of the 'Structural Review' part of the ATRT3
>    recommendations.
>    3. A number of proposals on how to proceed with the PHR.
>
>
>
> Having listened to a number of the exchanges we convened a meeting of the
> SO/AC/NC Chairs, the ATRT 3 Chairs and ourselves. At that meeting a number
> of matters were clarified:
>
>    1. ATRT3 intended the Holistic Review to be an ICANN Specific Review.1
>    This means that an eventual Holistic Review would be conducted in
>    accordance with Section 4.6(a) of ICANN's Bylaws and pursuant to the
>    Operating Standards for Specific Reviews. We note that the current
>    Operating Standards are under review2 so the PHR is designing an
>    Holistic Review with, at this stage, an unclear set of operating standards.
>
> By way of examples of issues arising, under the current Bylaws and
> Operating Standards, such matters as the structure of the review team3
> and the use or non-use of independent experts4 are matters for the
> Holistic Review team itself, not for the PHR. Further, under the Bylaws,
> specific review recommendations are made to the Board5 not to the
> individual SO/AC or NC that may be the subject of the recommendation. This
> is inconsistent with deliverable 8 of the PHR Terms of Reference.
>
>    2. To the extent the PHR has been given deliverables on issues covered
>    by Section 4.6(a) of the ICANN Bylaws, these deliverables become
>    redundant.
>    3. Whilst the result of a Review of the Continuous Improvement efforts
>    of the SO/AC/NCs would feed into a Structural Review, the two reviews are
>    based on two contradictory assumptions: that the SO/AC/NCs are fit for
>    purpose as set out in the Bylaws, and that the SO/AC/NCs are not fit for
>    purpose as set out in the Bylaws. Therefore, the two reviews are really
>    separate pieces of work with separate skill sets and deliverables.
>    4. The PHR is misnamed. It is, in essence, The Holistic Review
>    Drafting Team.
>    5. There may not be consensus amongst the SO/AC/NC chairs that a
>    specific review is the right mechanism for conducting a Structural Review
>    of ICANN and/or for reviewing the continuous improvement efforts of
>    SO/AC/NC. This is consistent with the feedback and discussions from the
>    Board and SO/AC interactions at ICANN 82.
>
>
>
> Clearly the ICANN Board is currently considering the ICANN reviews as a
> whole. In the event that a decision is made to launch a process to review
> ICANN reviews then the below is redundant. However, should the Board decide
> to continue with the PHR process we recommend the following steps –
>
>    1. Bifurcate the work to develop a Continuous Improvement Program
>    (CIP) Review and a Structural Review.
>    2. Empower a CIP Review drafting team to work closely with the
>    SO/AC/NC to ascertain their CIP methodologies and design a streamlined
>    review of the CIP work.
>    3. Confirm that there is SO/AC/NC consensus in favour of creating a
>    Specific Review on ICANN's structure.
>    4. Empower a Structural Review drafting team to design a Specific
>    Review of the Structure of ICANN based upon Bylaws s4.6(a) and the
>    Operating Standards.
>
>
>
> Note that in the above, steps 1 and 2 could proceed immediately should the
> Board wish.
>
>
>
> Should be Board decide to proceed in this manner both of us stand ready to
> continue our work as Chairs.
>
>
>
> Chris Disspain & Sophie Hey
>
> Co-Chairs Pilot Holistic Review
>
>
>
>
> ------------------------------
>
> 1 See ATRT3 recommendation 8, p71-2
>
> 2
> https://www.icann.org/en/public-comment/proceeding/proposed-updates-to-the-operating-standards-for-specific-reviews-23-12-2024
>
> 3 Bylaws s 4.6(a)(i)
>
> 4 Bylaws, s 4.6(a)(iv)
>
> 5 Bylaws, s 4.6(a)(viii)(C)
>
>
>
>
>
> Sophie Hey
>  she/her
>  Policy Advisor
>
> <https://comlaude.com/>
>
> 28 Little Russell Street,
> London WC1A 2HN, UK
> *T* +44 (0) 20 7421 8250
> *Ext* 252
>
> *comlaude.com <http://comlaude.com>*
>
> *Follow us on LinkedIn
> <https://t-uk.xink.io/Tracking/Index/pRkAAFJfAADl_RQA0> and YouTube
> <https://t-uk.xink.io/Tracking/Index/bhkAAFJfAADl_RQA0>*
>
> <https://www.linkedin.com/company/com-laude>
> <https://twitter.com/comlaude?lang=en>
> <https://www.facebook.com/ComLaude/>  <https://www.youtube.com/@comlaude>
>
> ------------------------------
>
> The contents of this email and any attachments are confidential to the
> intended recipient. They may not be disclosed, used by or copied in any way
> by anyone other than the intended recipient. If you have received this
> message in error, please return it to the sender (deleting the body of the
> email and attachments in your reply) and immediately and permanently delete
> it. Please note that Com Laude Group Limited (the “Com Laude Group”) does
> not accept any responsibility for viruses and it is your responsibility to
> scan or otherwise check this email and any attachments. The Com Laude Group
> does not accept liability for statements which are clearly the sender's own
> and not made on behalf of the group or one of its member entities. The Com
> Laude Group is a limited company registered in England and Wales with
> company number 10689074 and registered office at 28 Little Russell Street,
> London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a
> Com Laude, a company registered in England and Wales with company number
> 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN
> England; Valideus Limited, a company registered in England and Wales with
> company number 6181291 and registered office at 28 Little Russell Street,
> London, WC1A 2HN England; Demys Limited, a company registered in Scotland
> with company number SC197176 and registered office at 15 William Street,
> South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude
> USA and Valideus USA, a corporation incorporated in the State of Washington
> and principal office address at Suite 332, Securities Building, 1904 Third
> Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered
> in Japan with company number 0100-01-190853 and registered office at 1-3-21
> Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a
> company registered in Spain and registered office address at Calle Barcas
> 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com
> <https://comlaude.com>
>
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 103154 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1463 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1945 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1954 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1195 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 85818 bytes
Desc: not available
URL: <http://lists.ncsg.is/pipermail/ncsg-ec/attachments/20250328/de94779b/attachment-0001.jpg>