<div dir="auto">I (personally) strongly agree with Marilyn's criteria of what we are expecting of the mechanism. It is what several of us have been insisting on as a bottom line, for 2.5 years already?... how time flies.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 30 Jul 2019, 5:53 AM Marilyn Cade, <<a href="mailto:marilynscade@hotmail.com">marilynscade@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Mechanism C is a new foundation, with independence from ICANN. </div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Mechanism D is different, but is not still under consideration. So, let's not even go there. </div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
So, we are not reopening Mechanism D, but it is important to understand that in the discussions, Mechanism C is an independent foundation, not controlled by ICANN Org; not controlled by ICANN Board, and not controlled by ICANN community, but advised by each,
as is appropriate -- e.g consistent with ICANN mission; ensuring that risks do not reflect back to ICANN Org; are not influenced by Board or community other than in advisory capacity. AND, ensure that there are not anti trust or IRS implications to ICANN Org. </div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
We have still to do the due diligence work on the mechanisms that are 'nominated', and that has to be independent, not opinion based, and not limited to ICANN Org staff but uses experts who can do the due diligence needed for the mechanisms that are then put
forward to the community. </div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div>
<div id="m_-3080485369177377034appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_-3080485369177377034divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank" rel="noreferrer">alan.greenberg@mcgill.ca</a>><br>
<b>Sent:</b> Tuesday, July 30, 2019 10:40 AM<br>
<b>To:</b> Sam Lanfranco <<a href="mailto:sam@lanfranco.net" target="_blank" rel="noreferrer">sam@lanfranco.net</a>>; Vanda Scartezini <<a href="mailto:vanda@scartezini.org" target="_blank" rel="noreferrer">vanda@scartezini.org</a>>; Becky Burr <<a href="mailto:BBurr@hwglaw.com" target="_blank" rel="noreferrer">BBurr@hwglaw.com</a>>; Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank" rel="noreferrer">AAikman@lrrc.com</a>>; Marilyn Cade <<a href="mailto:marilynscade@hotmail.com" target="_blank" rel="noreferrer">marilynscade@hotmail.com</a>>; Elliot Noss <<a href="mailto:enoss@tucows.com" target="_blank" rel="noreferrer">enoss@tucows.com</a>><br>
<b>Cc:</b> <a href="mailto:ccwg-auctionproceeds@icann.org" target="_blank" rel="noreferrer">ccwg-auctionproceeds@icann.org</a> <<a href="mailto:ccwg-auctionproceeds@icann.org" target="_blank" rel="noreferrer">ccwg-auctionproceeds@icann.org</a>><br>
<b>Subject:</b> Re: [Ccwg-auctionproceeds] Judith Hellerstein's comments on the Auction Proceeds Draft</font>
<div> </div>
</div>
<div>Sam, Option C, but an established foundation instead of a new one is Option D which I believe we have already discarded.<br>
<br>
Sure, we can put it back on the table even though I believe it was discarded for valid reasons.<br>
<br>
I do note that as of last week, this CCWG had been meeting for exactly 2.5 years. If we continually reopen closed issues this CCWG will outlive us all! And we will never use the funds for "good stuff".<br>
<br>
Alan<br>
<br>
-- <br>
Sent from my mobile. Please excuse brevity and typos.<br>
<br>
<div class="m_-3080485369177377034x_gmail_quote">On July 30, 2019 7:28:58 AM EDT, Sam Lanfranco <<a href="mailto:sam@lanfranco.net" target="_blank" rel="noreferrer">sam@lanfranco.net</a>> wrote:
<blockquote class="m_-3080485369177377034x_gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<p>Thank you Alan, <br>
</p>
<p>We mainly agree and I understand that the grant decision process will be "outside of ICANN" in the sense that in either A or C there will be no scope for interventions by any element of the ICANN community. I have suggested (just now in response to comments
by Marilyn Cade) that a timeline be set for a review of lessons learned, and in the mean time if there are any subsequent auction proceeds, they be held back until after that review.</p>
<p>My one differing view is the hope that under Option C ICANN look to the existing not-for-profit granting organizations and seek a contractual collaboration for going forward, and that it not try to set up a brand new entity. The ICANN community has already
worries about challenges of ramping up, then ramping down, a unit within ICANN. The challenges of recruiting proper expertise for a completely new entity with a finite life are equally challenging. Start up costs, in money and time, would be considerable,
and recruiting proper personnel would be a challenge. <br>
</p>
<p>One strength we have within ICANN is that, even taking the private interests of some stakeholder groups into account, we tend to reach consensus and try to make the best of the policy decisions we decide on. <span class="m_-3080485369177377034x_moz-smiley-s1"><span>:-)</span></span>
<i>Maybe ICANN has a future, with a new line of business, consulting with national governments to help them move beyond confrontation and stalemate to consensus and some degree of actually policy making.</i>
<span class="m_-3080485369177377034x_moz-smiley-s1"><span>:-)</span></span><br>
</p>
<p>Sam <br>
</p>
<div class="m_-3080485369177377034x_moz-cite-prefix">On 7/29/2019 11:10 PM, Alan Greenberg wrote:<br>
</div>
<blockquote type="cite">Sam, a few corrections.<br>
<br>
You say: <br>
<br>
<blockquote type="cite" class="m_-3080485369177377034x_cite">Lastly, in addition to the issue of required independence and Option A, there is the challenge of amassing the appropriate expertise to properly and efficiently administer the granting process within a unit of ICANN itself.
One has to weigh those costs against Option C, where for a management fee the administrative process is transferred to a competent entity.
</blockquote>
<br>
The difference between A and C is that in A, the entity administering the entire project is within ICANN (subject to what it might choose to outsource) and in C, it is in a brand new entity that we will create - no existing expertise.<br>
<br>
In both A and B, the actual application analysis and grant decision will be outside of ICANN.
<br>
<br>
Although in theory there might be future auction proceeds, one of the premises of our entire work is that this is a one-time bonanza that will not be rrepeated and we should expect the funds to be used up in some (finite) time.<br>
<br>
Alan<br>
</blockquote>
<br>
</blockquote>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Ccwg-auctionproceeds mailing list<br>
<a href="mailto:Ccwg-auctionproceeds@icann.org" target="_blank" rel="noreferrer">Ccwg-auctionproceeds@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a><br>
_______________________________________________<br>
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 (<a href="https://www.icann.org/privacy/policy" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). 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.</blockquote></div>