<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi James,
<br>
</div>
<div>
<br>
</div>
<div>
thanks for your comment. And yes, we had a problem with the minority statements. Unfortunately the final part of the ATRT3 work was overshadowed by Convid-19. If we could have the Cancun meeting, we would have possibly reached a full consensus. But it is difficult to negotiate online on a text which gets so complex as we have it now.
</div>
<div>
<br>
</div>
<div>
@ Reviews: This was indeed in the center of our discussions and it was controversial, even between me an Michael, both from the NCSG. We both agreed that the review process is a cornerstone in the existing mechanisms to hold ICANN accountable to the broader community. We never had the plan to "throw them out of the window". My approach was, that the status quo with 13 institutional and substantive reviews (each Review Team produces sometime more than 20 recommendations) has created another problem which undermines the original intentions of the reviews as a key accountability instrument. If the Board gets 300+ recommendations from 13 Review Teams it has to prioritize. This is an invitation for cherry picking. And this is bad. To make the process more efficient and effective is a challenge and not an easy task, recognizing that ICANN 3.0 after the IANA transition has created a new complexity. If you read our final report carefully you will see that we do NOT throw out the institutional and substantial reviews but we push the Board to rethink the mechanism to develop/introduce a higher standard of accountability. But this raises also the question of SO and AC accountability, which is another (open) issue. As I said in my previous mail, our report is not a "big jump", but another small stumbling step. With other words, there is a lot to do by future RTs. A key proposal is in the prolog: The "holistic review". See also my mail to the ATRT3 list below.
<br>
</div>
<div>
<br>
</div>
<div>
Hope this is ok for you.
<br>
</div>
<div>
<br>
</div>
<div>
Wolfgang
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<div class="default-style">
Hi,
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
may I join Osvaldo in expressing my thanks to all members and supporters of the ATRT3, to CLO and Pat for co-chairing, to my fellow members, the great staff support from Jennifer, Negar, Brenda and others and in particular for Bernie who finally trimmed his pen to produce the 300+ pages document, word by word, comma by comma, line by line.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
For me, as an ICANN veteran, it was a special experience. Like Osvaldo, it was my first Review Team and I expected something different. However, at the end of the 14 months - as I said in the chat during the final call - I can live with the outcome and see this as another small stumbling step forward in the meanwhile long history of ICANN to move into unchartered territory.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
As I said in out first meeting in LA in April 2019, it was the first ATRT after the IANA transition and the first opportunity to review, how the new mechanisms, introduced after the bylaw revision from 2016, have worked in practice. I expected that we can take an "eagles perspective" and to see whether ICANN as a whole has evolved in the right direction and is prepared to manage the new challenges of the 2020s. But I realized soon, that ATRT3 has a limited mandate and a long list of unfinished business (also from ATRT2) on the table. However, what I see after the 14 month of collaborative work and deep diving into the new problems ICANN is dealing with, I am happy that next to our package of five recommendations we also conclude, inter alia, that there is a need for a "holistic review" in the near future.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Such a review will not remove or substitute the existing reviews - which needed to be streamlined and executed more efficient - but in my eyes, we discovered an important gap in the new existing mechanism. The reviews under the AOC were introduced in 2009 to counter arguments by many governments that ICANN needs a special (intergovernmental) oversight mechanism. The AOC made clear, that oversight can be delivered effectively by the community itself and issue based. This was a excellent move and the right thing to do in 2009. In 2016 - after another wave of outside criticism with regard to the missing ICANN oversight from various corners of the global Internet Governance Ecosystrem - the new bylaws introduced the concept of the "empowered community" as an additional component. This was and is an innovation which still needs to be "stresstested".
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
A number of recent events - as, inter alia, the discussion around the .org-case - has produced a feeling among parts of the community, that the existing accountability mechanisms are now so complex, that they loose their efficiency. How to simplify this new complexity? It was not within the mandate of the ATRT3 to answer this question. But to be frank, I excpected from ATRT3 more discussion about this need for a "holistic review" and a simple and workable (non-governmental and multistakeholder community based) oversight mechanism for ICANN as a whole.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
I hope that in the next two or three years we will see that ICANN will be able to take this next step, closing conceptual gaps. ICANN should not wait until the next intergovernmental battle around ICANN oversight will start. The best way forward is to demonstrate to the rest of the world, that the ICANN community itself is strong (and critical) enough to manage all new challenges, including issues like security, DNS abuse, market development, privacy etc.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
My hope is, that we as ATRT3 contributed to this process. And again, thanks for this great experience of enhanced cooperation.
</div>
<div class="default-style">
Best wishes and stay safe.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Wolfgang
<br>
</div>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<blockquote type="cite">
James Gannon <lists@ICANN.GURU> hat am 2. Juni 2020 um 15:19 geschrieben:
<br>
<br>
<div class="ox-22f38e5016-WordSection1">
<p class="ox-22f38e5016-MsoNormal">I have to say I find the approach that ATRT has taken to reducing the community driven oversight that we fought so hard to build, and indeed to bolster during the IANA stewardship, is highly disappointing. To have spent thousands of hours working on these fundamental processes of accountability to only see them thrown out at the first opportunity is demoralizing to be honest.</p>
<p class="ox-22f38e5016-MsoNormal"><br></p>
<p class="ox-22f38e5016-MsoNormal">I also note the large amount of dissenting statements (4) from members of the ATRT to be a concern as to the level of completeness and representativeness that the final report represents.</p>
<p class="ox-22f38e5016-MsoNormal"><br></p>
<div>
<p class="ox-22f38e5016-MsoNormal"><span style="color: black;">---</span></p>
</div>
<p class="ox-22f38e5016-MsoNormal"><strong><span style="color: black;">James Gannon</span></strong></p>
<p class="ox-22f38e5016-MsoNormal"><br></p>
<div style="border: none; border-top: solid #B5C4DF 1.0pt; padding: 3.0pt 0cm 0cm 0cm;">
<p class="ox-22f38e5016-MsoNormal"><strong><span style="font-size: 12.0pt; color: black;">From: </span></strong><span style="font-size: 12.0pt; color: black;">NCSG-Discuss <NCSG-DISCUSS@LISTSERV.SYR.EDU> on behalf of Wolfgang Kleinwächter <wolfgang@KLEINWAECHTER.INFO><br><strong>Reply to: </strong>Wolfgang Kleinwächter <wolfgang@KLEINWAECHTER.INFO><br><strong>Date: </strong>Tuesday, 2 June 2020 at 13:26<br><strong>To: </strong>"NCSG-DISCUSS@LISTSERV.SYR.EDU" <NCSG-DISCUSS@LISTSERV.SYR.EDU><br><strong>Subject: </strong>Re: ATRT3 </span></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">With pleasure</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">w</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<blockquote>
<p style="margin-bottom: 12.0pt;" class="ox-22f38e5016-MsoNormal">Rafik Dammak <rafik.dammak@GMAIL.COM> hat am 2. Juni 2020 um 12:54 geschrieben:</p>
<div>
<div>
<p class="ox-22f38e5016-MsoNormal">Hi Wolfgang,</p>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">Thanks for the update and work at ATRT3.</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">As discussed at NCSG policy call where you shared update, we want to organize webinar for NCSG members on ATRT3 recommendations and looking forward your help.</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">Best regards,</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">Rafik</p>
</div>
<p style="margin-bottom: 12.0pt;" class="ox-22f38e5016-MsoNormal"><br></p>
<div>
<div>
<p class="ox-22f38e5016-MsoNormal">On Tue, Jun 2, 2020, 19:22 Wolfgang Kleinwächter < <a href="mailto:wolfgang@kleinwaechter.info"> wolfgang@kleinwaechter.info</a>> wrote:</p>
</div>
<blockquote>
<div>
<div>
<p class="ox-22f38e5016-MsoNormal">Dear friends,</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">as a NCSG Rep. in the ATRT3 team I just want to let you know, that we have finalized our work. The Final Report was send to the chair of the Board yesterday. It is a lengthy report. 350 pages. As indicated in a previous conversation, we have five groups of recommendations, with two set of recommendations ranked as "high" (Reviews and Prioritization). You can see the details in the Executive Summary. In a special Prolog we have also outlined some issues which are relevant in our eyes but where not touched by the RT or seen as outside of our mandate. One of the issue we raise in this part is the need for what we have called a "holistic review" of ICANN as a whole in the near future.</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">The spirit of the gorup was very good. We had more than 60 calls. Unfortunately we had to cancel pur final F2F meeting, planned for Cancun, which produced extra trouble for the final negotiations on the text. Insofar it is not a surprise that the full report includes also some minority statements from ATRT3 members who disagreed with some of the findings of the group. </p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">It is not a "big jump". However I see it as a next small stumbling step forward in the right direction to enhance ICANNs accountability and transparency. More steps has to follow. And the proposed "holistic review" could be one of them. </p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">I want to thank the NCSC community for sending me to the RT. I did my best to bring the values and positions of the non-commercial community in the ICANN familiy to the ATRT3 proceedings. It was a lot of work, but it was worth to invest the time and the energy. </p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">Best wishes and stay safe.</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal">Wolfgang</p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
<div>
<p class="ox-22f38e5016-MsoNormal"><br></p>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<div>
<p class="ox-22f38e5016-MsoNormal"><br> </p>
</div>
</div>
</blockquote>
<div class="default-style">
<br>
</div>
</body>
</html>