<div dir="ltr"><div>Dear All,</div><div>We in ICG have spent over two months with more than several hundreds of message exchanged on consensus building and in particular points raised in this message.</div><div>May I recommend you to kindly look at that document in ICG drop box or ask Patrik or Mohamd or Alissa ,if still available to provide that to you.</div><div>It would be a useful element to consider </div><div>Kavouss .</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-12 18:26 GMT+01:00 Marika Konings <span dir="ltr"><<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="color:rgb(0,0,0)">
<div style="font-family:Calibri,sans-serif;font-size:14px">The definitions from the GNSO Working Group guidelines closely align with those in the charter:</div>
<div><br>
</div>
<div>
<p style="margin:0px 0px 8.1px"><b>Full consensus </b>- when no one in the group speaks against the recommendation in its last readings. This is also sometimes referred to as
<b>Unanimous Consensus. </b></p>
<p style="margin:0px"><b>Consensus </b>- a position where only a small minority disagrees, but most agree </p>
<p style="margin:0px"><br>
</p>
</div>
<div style="font-family:Calibri,sans-serif;font-size:14px">(From the GNSO Working Group Guidelines section 3.6 (<a href="http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-13nov14-en.pdf" target="_blank">http://gnso.icann.org/council/annex-1-gnso-wg-guidelines-13nov14-en.pdf</a>)</div>
<div>
<p style="margin:0px"><br>
</p>
<p style="margin:0px">Best regards,</p>
<p style="margin:0px"><br>
</p>
<p style="margin:0px">Marika</p>
</div>
<div style="font-family:Calibri,sans-serif;font-size:14px"><br>
</div>
<span style="font-family:Calibri,sans-serif;font-size:14px">
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in;text-align:left;color:black;font-family:Calibri;font-size:11pt">
<span style="font-weight:bold">From: </span>Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:Mathieu.Weill@afnic.fr" target="_blank">Mathieu.Weill@afnic.fr</a>" <<a href="mailto:Mathieu.Weill@afnic.fr" target="_blank">Mathieu.Weill@afnic.fr</a>><br>
<span style="font-weight:bold">Date: </span>Monday 12 January 2015 12:11<br>
<span style="font-weight:bold">To: </span>Finn Petersen <<a href="mailto:FinPet@erst.dk" target="_blank">FinPet@erst.dk</a>>, "<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org" target="_blank">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-Accountability] WS1 vs WS2 recap and proposals<br>
</div>
<div><br>
</div>
<div>
<div text="#000000" bgcolor="#FFFFFF"><div><div class="h5">Dear Finn, <br>
<br>
This is a good point you're raising. <br>
<br>
Looking at our own Charter, I did find this definition of consensus in the decision making methodologies section :
<br>
<blockquote type="cite">
<p class="MsoNormal" style>
<span lang="EN-US">In developing its Proposal(s), work plan and any other reports, the CCWG-Accountability shall seek to act by consensus. Consensus calls should always make best efforts to involve all members (the CCWG-Accountability or sub-working group).
The Chair(s) shall be responsible for designating each position as having one of the following designations:<u></u><u></u></span></p>
<p class="MsoNormal" style>
<span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal" style>
<span lang="EN-US" style="color:black"><span>a)<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span lang="EN-US" style="color:black">Full Consensus - a position where no minority disagrees; identified by an absence of objection</span><span lang="EN-US"><u></u><u></u></span></p>
<p class="MsoNormal" style>
<span lang="EN-US" style="color:black"><span>b)<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span lang="EN-US" style="color:black">Consensus – a position where a small minority disagrees, but most agree</span><span lang="EN-US"><u></u><u></u></span></p>
</blockquote>
I do not know whether Icann has a documented definition of consensus other than that ? Maybe there is within the gNSO for PDP purposes ?
<br>
<br>
Best<br>
Mathieu<br>
<br>
<div>Le 12/01/2015 12:08, Finn Petersen a écrit :<br>
</div>
</div></div><blockquote type="cite">
<div><div><div class="h5">
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Dear Co-Chairs, colleagues,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Thank you for all the work that have gone into advancing this key issue.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Acknowledging that the discussion regarding the definitions of WS1/WS2 is moving fast, we would, however, like to raise a question regarding
the proposal submitted for comment by the Co-chairs and the wording “consensus support” (marked in yellow). What would “consensus support from the community” entail in this situation? For example, would it mean that a proposal would be taken off the table
if only one person/stakeholder group/AC-SO etc. from the community (also a term that is currently discussed) would be against it?
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">WS1 mechanisms are those that, when in place or committed to, would provide the community with confidence that any accountability mechanism
that would further enhance Icann's accountability would be implemented if it had consensus support from the community, even if it were to encounter Icann management resistance or if it were against the interest of Icann as a corporate entity.
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">This is just another example of the importance of carefully considering the Problem definition of our work.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Looking forward to continuing our work on this important issue.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Best,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt">Finn<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:10pt">Kind regards<br>
<br>
<b>Finn Petersen<u></u><u></u></b></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:10pt">Director of International ICT Relations</span><span lang="EN-US" style="color:rgb(31,73,125);font-family:Arial,sans-serif;font-size:10pt"><br>
<br>
</span><b><span lang="EN-US" style="color:maroon;font-family:Arial,sans-serif;font-size:7.5pt">DANISH BUSINESS AUTHORITY</span></b><span lang="EN-US" style="color:maroon;font-family:Arial,sans-serif;font-size:7.5pt"><br>
</span><span lang="EN-US" style="font-family:Arial,sans-serif;font-size:7.5pt"><br>
Dahlerups Pakhus<br>
Langelinie Allé 17<br>
DK-2100 København Ø<br>
Telephone: <a href="tel:%2B45%203529%201000" target="_blank" value="+4535291000">+45 3529 1000</a><br>
Direct: <a href="tel:%2B45%203529%201013" target="_blank" value="+4535291013">+45 3529 1013</a><u></u><u></u></span></p>
</div></div><p class="MsoNormal"><div><div class="h5"><span lang="EN-US" style="font-family:Arial,sans-serif;font-size:7.5pt">Mobile: <a href="tel:%2B45%202072%207131" target="_blank" value="+4520727131">+45 2072 7131</a><br>
E-mail: <a href="mailto:FinPet@erst.dk" target="_blank">FinPet@erst.dk</a><br>
<a href="http://www.erhvervsstyrelsen.dk" target="_blank">www.erhvervsstyrelsen.dk</a><br>
<br>
MINISTRY FOR BUSINESS AND GROWTH<br>
<br>
</span></div></div><span style="color:green;font-family:Webdings;font-size:13.5pt">P</span><span style="color:rgb(31,73,125)"></span><span lang="EN-US" style="color:green;font-family:Arial,sans-serif;font-size:7.5pt">Please consider the environment before printing this
email.</span><span lang="EN-US" style="color:rgb(31,73,125)"></span><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u><u></u></span><p></p><div><div class="h5">
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:11pt"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext;font-family:Tahoma,sans-serif;font-size:10pt">Fra:</span></b><span lang="EN-US" style="color:windowtext;font-family:Tahoma,sans-serif;font-size:10pt"><a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">
accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org" target="_blank">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>På vegne af </b>Mathieu Weill<br>
<b>Sendt:</b> 5. januar 2015 16:56<br>
<b>Til:</b> <a href="mailto:accountability-cross-community@icann.org" target="_blank">
accountability-cross-community@icann.org</a><br>
<b>Emne:</b> [CCWG-Accountability] WS1 vs WS2 recap and proposals<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal">Dear Colleagues,<br>
<br>
During our 30th December call, we had extensive discussions regarding what our group would consider work stream 1 or swork stream 2. We concluded with an action item as such :
<br>
<br>
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:7pt"> </span><b><span style="font-family:Calibri,sans-serif;font-size:10pt">ACTION:</span></b><span style="font-family:Calibri,sans-serif;font-size:10pt"> Recap of definitions of WS1/WS2 for mailing list and discussion next week.</span><u></u><u></u></p>
<p class="MsoNormal">As Co-chairs, we have attempted to summarize the various inputs expressed on the list as well as during the calls on the matter. Below is a recap, including a proposal for discussion, inspired by the WA2 proposal, and which, in our opinion,
would be a good candidate to move forward. <br>
<br>
This is for you review at this stage before we discuss it tomorrow during the weekly call. Comments or alternate will be welcome during the call or later on this thread.
<br>
<br>
I'd like to once again thank Steve del Bianco and the WA2 team for their essential contribution to this key piece of our work.
<br>
<br>
Mathieu<br>
<br>
------------------------<br>
Main inputs, comments and positions expressed so far regarding WS1/WS2: <br>
<br>
<u></u><u></u></p>
<p class="MsoNormal">Problem statement from our Charter : <br>
<br>
<u></u><u></u></p>
<div>
<pre style="font-size:inherit;word-spacing:0px"><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">The concerns raised during these discussions around the transition process indicate that the existing <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">ICANN accountability mechanisms do not yet meet stakeholder expectations. Recent statements <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">made by various stakeholders suggest that current accountability mechanisms need to be reviewed <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">and, if need be, improved, amended, replaced, or supplemented with new mechanisms (see for <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">instance ATRT recommendations). Considering that the NTIA has stressed that it is expecting <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">community consensus regarding the transition, a failure to meet stakeholder expectations with <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">regards to accountability may create a situation where NTIA does not accept the IANA transition <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">proposal as meeting its conditions. Thus reviewing ICANN’s accountability mechanisms was <u></u><u></u></span></pre>
<pre><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">considered to be crucial for the transition process.</span><u></u><u></u></pre>
</div>
<p class="MsoNormal">Work stream scopes from our Charter :<br>
<br>
<u></u><u></u></p>
<div>
<div>
<div style="margin-top:13.45pt">
<p class="MsoNormal"><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">In the discussions around the accountability process, the CCWG-Accountability will proceed with two Work Streams:</span><span style="font-family:Calibri,sans-serif"><u></u><u></u></span></p>
</div>
<p class="MsoNormal" style="margin-left:41pt">
<span style="color:rgb(1,1,1);font-size:10pt"><span>·<span style="font:7pt/normal "Times New Roman"">
</span></span></span><b><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">Work Stream 1</span></b><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt"> : focused on mechanisms
enhancing ICANN accountability that must be in place or committed to within the time frame of the IANA Stewardship Transition;</span><span style="color:rgb(1,1,1);font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:41pt">
<span style="color:rgb(1,1,1);font-size:10pt"><span>·<span style="font:7pt/normal "Times New Roman"">
</span></span></span><b><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">Work Stream 2</span></b><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt"> : focused on addressing
accountability topics for which a timeline for developing solutions and full implementation may extend beyond the IANA Stewardship Transition.</span><span style="color:rgb(1,1,1);font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">The CCWG-Accountability will allocate issues to Work Stream 1 and Work Stream 2. Some issues may span both Work Streams.</span><span style="font-family:Calibri,sans-serif"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">Suggested questions to be considered as part of Work Stream 1 include, but are not limited to: </span><span style="font-family:Calibri,sans-serif"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:41pt">
<span style="color:rgb(1,1,1);font-size:10pt"><span>·<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">What would be the impact of NTIA’s transition of the IANA Functions Contract in ensuring ICANN’s accountability and what potential accountability
concerns could this cause?</span><span style="color:rgb(1,1,1);font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:41pt">
<span style="color:rgb(1,1,1);font-size:10pt"><span>·<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">What enhancements or reforms are required to be implemented or committed to before the NTIA Stewardship Transition?</span><span style="color:rgb(1,1,1);font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:87pt">
<span><span>o<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">How will these enhancements or reforms be stress-tested?</span><span><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:41pt">
<span style="color:rgb(1,1,1);font-size:10pt"><span>·<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">What enhancements or reforms must be committed to before the NTIA Stewardship Transition, but could be implemented after.</span><span style="color:rgb(1,1,1);font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:87pt">
<span><span>o<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">If the implementation of enhancements or reforms are to be deferred, how can the community be assured they will be implemented?</span><span><u></u><u></u></span></p>
<p class="MsoNormal" style="margin-left:87pt">
<span><span>o<span style="font:7pt/normal "Times New Roman"">
</span></span></span><span style="color:rgb(1,1,1);font-family:Calibri,sans-serif;font-size:11pt">How will these enhancements or reforms be stress-tested?</span><span><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">Work Area 2 proposed definition of WS1/2 :<br>
<br>
<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif">WS 1 is designated for accountability mechanisms that must be in place of rimly committed to before IANA transition occurs. <u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif">All other consensus items could be in WS2, provided <b>there are mechanisms in WS1 adequate for force implementation of WS2 items despite resistance from Icann management and Board.</b> <u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal">Paul Rosenzweig tentative defintiion of WS0 :<br>
<br>
<u></u><u></u></p>
<div>
<blockquote style="font-size:inherit;margin-top:5pt;margin-bottom:5pt;word-spacing:0px">
<p class="MsoNormal"><span style="font-family:Arial,sans-serif">As a result, I think that part of what we should be doing in the long run is focusing on the core/critical 3-5 items that are absolutely essential to ensuring accountability. In short, I think
there is actually a sub-category of WS1 (call it <b>WS0</b> for want of a better term) that would be fundamental red-lines for the community. <u></u><u></u></span></p>
</blockquote>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal">Alan Greenberg's concern : <br>
<br>
<u></u><u></u></p>
<div>
<pre style="font-size:inherit;word-spacing:0px"><span style="font-family:Arial,sans-serif">Needs to demontrate why items in WS1 or WS2 are needed as a consequence of the NTIA transition. </span><u></u><u></u></pre>
</div>
<p class="MsoNormal"><br>
Comment from Becky Burr :<u></u><u></u></p>
<div>
<p class="MsoNormal"><span style="font-family:Arial,sans-serif">Understands the community to say there were certain basic accountability mechanisms that would enable them to feel comfortable with the IANA transition, these may not be directly related to
the transition itself. What we need from WS1 is the community feels comfortable that tools are in place to continue the work to create real and meaningful accountability. <u></u><u></u></span></p>
</div>
<p class="MsoNormal">-----------------------------------<br>
Proposal submitted for comments (to be presented and initially discussed during tomorrow's call):
<br>
<br>
<u></u><u></u></p>
<p class="MsoNormal"><span style="font-family:Calibri,sans-serif">WS1 mechanisms are those that, when in place or committed to, would provide the community with confidence that any accountability mechanism that would further enhance Icann's accountability
would be implemented if it had consensus support from the community, even if it were to encounter Icann management resistance or if it were against the interest of Icann as a corporate entity. </span><u></u><u></u></p>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<pre>-- <u></u><u></u></pre>
<pre>*****************************<u></u><u></u></pre>
<pre>Mathieu WEILL<u></u><u></u></pre>
<pre>AFNIC - directeur général<u></u><u></u></pre>
<pre>Tél: <a href="tel:%2B33%201%2039%2030%2083%2006" target="_blank" value="+33139308306">+33 1 39 30 83 06</a><u></u><u></u></pre>
<pre><a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a><u></u><u></u></pre>
<pre>Twitter : @mathieuweill<u></u><u></u></pre>
<pre>*****************************<u></u><u></u></pre>
</div></div></p></div>
</blockquote><div><div class="h5">
<br>
<pre cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: <a href="tel:%2B33%201%2039%2030%2083%2006" target="_blank" value="+33139308306">+33 1 39 30 83 06</a>
<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</div></div></div>
</div>
</span>
</div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>