<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:13.5pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri Light",sans-serif;
color:#1F3763;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Carolina,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks very much for sharing this input, which is being compiled with the other feedback received.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">You can find the CCWG Agreements document here: <a href="https://community.icann.org/download/attachments/102138829/new%20gTLD%20AP%20CCWG%20Agreements%20-%20updated%206%20June%202019.docx?version=1&modificationDate=1560325341000&api=v2">
https://community.icann.org/download/attachments/102138829/new%20gTLD%20AP%20CCWG%20Agreements%20-%20updated%206%20June%202019.docx?version=1&modificationDate=1560325341000&api=v2</a>.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It is also available at the bottom of this wiki page: <a href="https://community.icann.org/display/CWGONGAP/Initial+Report+Public+Comment+Review">
https://community.icann.org/display/CWGONGAP/Initial+Report+Public+Comment+Review</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Kind regards,<o:p></o:p></p>
<p class="MsoNormal">Emily<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Ccwg-auctionproceeds <ccwg-auctionproceeds-bounces@icann.org> on behalf of Carolina Caeiro <carolina@lacnic.net><br>
<b>Date: </b>Friday, 26 July 2019 at 20:21<br>
<b>To: </b>"ccwg-auctionproceeds@icann.org" <ccwg-auctionproceeds@icann.org><br>
<b>Subject: </b>Re: [Ccwg-auctionproceeds] New Deadline - 26 July 2019 - input on updated draft Final Report and outstanding questions<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p>Dear all,<o:p></o:p></p>
<p>Please find my comments to the report attached.<o:p></o:p></p>
<p>On the more substantive matters:<o:p></o:p></p>
<p>1. My preference would be that the CCWG recommend one single mechanism, so that work can start as soon as possible. I would be Ok with recommending two if we continue to be unable to arrive to an agreement.
<o:p></o:p></p>
<p>2. As stated by Eliot and Sylvia, we should ensure we bring community input into the process. This in my view would enrich any mechanism, A, B or C. I support Sylvia's proposal that we outline what that community engagement would look like to best inform
the work of the implementing team (just to be clear, I am talking about the community advisory board and an independent evaluation panel). I won't have the chance to review the text circulated by Emily today, but will try to do so prior to the next meeting
on Wednesday.<o:p></o:p></p>
<p>4. In terms of preferred mechanisms, I incline for Mechanism A. I think there is more agreement than we think on the safeguards that we want to provide among both supporters of mechanisms A and C: independence, cost-efficiency of the mechanism, community
engagement. My sense is that we should prioritize what allows us to more swiftly get to work, and that for whichever mechanism we pick, we ensure those safeguards are in place.
<o:p></o:p></p>
<p>Lastly, Emily, the report references the CCWG Agreements by number. Could you please circulate the document where all those agreements are compiled?
<o:p></o:p></p>
<p>Happy weekend to you all,<o:p></o:p></p>
<p>Carolina<o:p></o:p></p>
<div>
<p class="MsoNormal">El 25/7/19 a las 15:03, Alan Greenberg escribió:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>How autonomous an affiliate organization is (that <o:p></o:p></pre>
<pre>is the correct term in lieu of "subsidiary") is <o:p></o:p></pre>
<pre>wholly dependant on its Bylaws and Board composition.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>In the case of PTI/IANA, the Board has five <o:p></o:p></pre>
<pre>member, three of who are appointed by ICANN. That <o:p></o:p></pre>
<pre>gives ICANN full control unless a vote needs a supermajority (rare if ever).<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Alan<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>At 25/07/2019 12:26 PM, Maureen Hilyard wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>John<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>The point is that ICANN can create a structure/department that can act<o:p></o:p></pre>
<pre>autonomously<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On Thu, Jul 25, 2019 at 5:58 AM John Levine <a href="mailto:johnl@taugh.com"><johnl@taugh.com></a> wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>PTI's structure and functions have no <o:p></o:p></pre>
</blockquote>
<pre>relationship to the ccwg's. I do not understand why people keep bringing it up.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>PTI does administrative activities under <o:p></o:p></pre>
</blockquote>
<pre>contract to icann and others. It does nothing <o:p></o:p></pre>
<pre>even a little bit like giving out grants.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Autocorrectly,<o:p></o:p></pre>
<pre>John<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>-------- Original message --------<o:p></o:p></pre>
<pre>From: Maureen Hilyard <a href="mailto:maureen.hilyard@gmail.com"><maureen.hilyard@gmail.com></a><o:p></o:p></pre>
<pre>Date: 7/25/19 08:46 (GMT-08:00)<o:p></o:p></pre>
<pre>To: <a href="mailto:marienoemie.marques@orange.com">marienoemie.marques@orange.com</a><o:p></o:p></pre>
<pre>Cc: Alan Greenberg <o:p></o:p></pre>
</blockquote>
<pre><a href="mailto:alan.greenberg@mcgill.ca"><alan.greenberg@mcgill.ca></a>, John Levine <o:p></o:p></pre>
<pre><a href="mailto:johnl@taugh.com"><johnl@taugh.com></a>, CCWG Auction Proceeds <a href="mailto:ccwg-auctionproceeds@icann.org"><ccwg-auctionproceeds@icann.org></a><o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Subject: Re: [Ccwg-auctionproceeds] New <o:p></o:p></pre>
</blockquote>
<pre>Deadline - 26 July 2019 - input on updated <o:p></o:p></pre>
<pre>draft Final Report and outstanding questions<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Thank you for reminding us of this <o:p></o:p></pre>
</blockquote>
<pre>connection which we raised as an option to <o:p></o:p></pre>
<pre>consider very early in our discussions but was ignored.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>On Thu, 25 Jul 2019, 5:40 AM , <a href="mailto:marienoemie.marques@orange.com"><marienoemie.marques@orange.com></a> wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Would it be helpful, just for information, to note that :<o:p></o:p></pre>
<pre>"Public Technical Identifiers (PTI) was <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>incorporated in August 2016 as an affiliate of <o:p></o:p></pre>
<pre>ICANN, and, through contracts and subcontracts <o:p></o:p></pre>
<pre>with ICANN, began performing the IANA functions <o:p></o:p></pre>
<pre>on behalf of ICANN in October 2016."<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>-----Message d'origine-----<o:p></o:p></pre>
<pre>De : Ccwg-auctionproceeds <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>[<a href="mailto:ccwg-auctionproceeds-bounces@icann.org">mailto:ccwg-auctionproceeds-bounces@icann.org</a>] De la part de Alan Greenberg<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Envoyé : jeudi 25 juillet 2019 17:36<o:p></o:p></pre>
<pre>À : John Levine<o:p></o:p></pre>
<pre>Cc : CCWG Auction Proceeds<o:p></o:p></pre>
<pre>Objet : Re: [Ccwg-auctionproceeds] New <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>Deadline - 26 July 2019 - input on updated <o:p></o:p></pre>
<pre>draft Final Report and outstanding questions<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>B was not an ICANN Subsidiary but some other existing entity that we<o:p></o:p></pre>
<pre>could team up with so that we did not have to re-invent services that<o:p></o:p></pre>
<pre>we could outsource. That being said, I am happy to eliminate it!<o:p></o:p></pre>
<pre>Mechanism A always has the option of outsourcing some of the functions.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>BTW, under the California law that we operate under, a Public<o:p></o:p></pre>
<pre>Interest Corp cannot have a "subsidiary", but that is just a<o:p></o:p></pre>
<pre>nomenclature issue.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Alan<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>At 25/07/2019 01:35 AM, John Levine wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Mechanism B: I presume the phrase "established at a public charity"<o:p></o:p></pre>
<pre>should be "established as a public<o:p></o:p></pre>
<pre>charity". I do not understand why the issue of tax benefits is<o:p></o:p></pre>
<pre>being raised as in our case all of the<o:p></o:p></pre>
<pre>money is coming form ICANN which does not pay any taxes. So it<o:p></o:p></pre>
<pre>SOUNDS like a benefit but is in fact<o:p></o:p></pre>
<pre>meaningless in our case.<o:p></o:p></pre>
<pre>It should be made clear that at this point, it is not clear what<o:p></o:p></pre>
<pre>parts would be outsourced and what<o:p></o:p></pre>
<pre>will be kept within ICANN (except the application evaluation which<o:p></o:p></pre>
<pre>must be outsourced).<o:p></o:p></pre>
</blockquote>
<pre>I believe that this is supposed to say that ICANN establishes a<o:p></o:p></pre>
<pre>captive foundation as a subsidiary.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Having done exactly that at ISOC, I can say that for the CCWG's<o:p></o:p></pre>
<pre>purposes, giving away a one-time pile of money, this mechanism is<o:p></o:p></pre>
<pre>inferior in every way to mechanism A. It costs more, takes longer,<o:p></o:p></pre>
<pre>has a lot more bureaucratic overhead, and can do no more or no less<o:p></o:p></pre>
<pre>than mechanism A. As Alan notes, it has no tax benefits. It is a<o:p></o:p></pre>
<pre>waste of everyone's time to pursue it further.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>If anyone has a concrete reason why they believe this would be a<o:p></o:p></pre>
<pre>good idea, and is reasonably familiar with US non-profit tax law so<o:p></o:p></pre>
<pre>they understand what's involved, I would like to hear about it.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>R's,<o:p></o:p></pre>
<pre>John<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>PS: ISOC's situation is quite different and it makes sense for us.<o:p></o:p></pre>
<pre>If anyone wants details write me privately.<o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Ccwg-auctionproceeds mailing list<o:p></o:p></pre>
<pre><a href="mailto:Ccwg-auctionproceeds@icann.org">Ccwg-auctionproceeds@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>By submitting your personal data, you <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>consent to the processing of your personal data <o:p></o:p></pre>
<pre>for purposes of subscribing to this mailing <o:p></o:p></pre>
<pre>list accordance with the ICANN Privacy Policy <o:p></o:p></pre>
<pre>(<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=lSDJEui_8VIPow5Or1iw0m7l3ACaNYXwG3Y820gQOAw&e=">https://www.icann.org/privacy/policy [icann.org]</a>) and the <o:p></o:p></pre>
<pre>website Terms of Service <o:p></o:p></pre>
<pre>(<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=LU9CS7MI5n8d7FAnE8vxJZUlV2LpZYkgXk51RM380gM&e=">https://www.icann.org/privacy/tos [icann.org]</a>). You can <o:p></o:p></pre>
<pre>visit the Mailman link above to change your <o:p></o:p></pre>
<pre>membership status or configuration, including <o:p></o:p></pre>
<pre>unsubscribing, setting digest-style delivery or <o:p></o:p></pre>
<pre>disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p> </o:p></pre>
</blockquote>
</blockquote>
<pre>_________________________________________________________________________________________________________________________<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Ce message et ses pieces jointes peuvent <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>pas etre diffuses, exploites ou copies sans <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>a l'expediteur et le detruire ainsi que les <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Orange decline toute responsabilite si ce <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>This message and its attachments may contain <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>confidential or privileged information that may be protected by law;<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>they should not be distributed, used or copied without authorisation.<o:p></o:p></pre>
<pre>If you have received this email in error, <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>please notify the sender and delete this message and its attachments.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>As emails may be altered, Orange is not <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>liable for messages that have been modified, changed or falsified.<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Thank you.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Ccwg-auctionproceeds mailing list<o:p></o:p></pre>
<pre><a href="mailto:Ccwg-auctionproceeds@icann.org">Ccwg-auctionproceeds@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>By submitting your personal data, you <o:p></o:p></pre>
</blockquote>
</blockquote>
<pre>consent to the processing of your personal data <o:p></o:p></pre>
<pre>for purposes of subscribing to this mailing <o:p></o:p></pre>
<pre>list accordance with the ICANN Privacy Policy <o:p></o:p></pre>
<pre>(<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=lSDJEui_8VIPow5Or1iw0m7l3ACaNYXwG3Y820gQOAw&e=">https://www.icann.org/privacy/policy [icann.org]</a>) and the <o:p></o:p></pre>
<pre>website Terms of Service <o:p></o:p></pre>
<pre>(<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=LU9CS7MI5n8d7FAnE8vxJZUlV2LpZYkgXk51RM380gM&e=">https://www.icann.org/privacy/tos [icann.org]</a>). You can <o:p></o:p></pre>
<pre>visit the Mailman link above to change your <o:p></o:p></pre>
<pre>membership status or configuration, including <o:p></o:p></pre>
<pre>unsubscribing, setting digest-style delivery or <o:p></o:p></pre>
<pre>disabling delivery altogether (e.g., for a vacation), and so on.<o:p></o:p></pre>
</blockquote>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Ccwg-auctionproceeds mailing list<o:p></o:p></pre>
<pre><a href="mailto:Ccwg-auctionproceeds@icann.org">Ccwg-auctionproceeds@icann.org</a><o:p></o:p></pre>
<pre><a href="https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds">https://mm.icann.org/mailman/listinfo/ccwg-auctionproceeds</a><o:p></o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=lSDJEui_8VIPow5Or1iw0m7l3ACaNYXwG3Y820gQOAw&e=">https://www.icann.org/privacy/policy [icann.org]</a>) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=LU9CS7MI5n8d7FAnE8vxJZUlV2LpZYkgXk51RM380gM&e=">https://www.icann.org/privacy/tos [icann.org]</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.<o:p></o:p></pre>
</blockquote>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
<h3><span style="color:#009DCA">Carolina Caeiro<o:p></o:p></span></h3>
<p><strong><span style="font-family:"Calibri",sans-serif;color:#8A8B8A">Coordinadora de Proyectos de Desarrollo</span></strong><span style="color:#8A8B8A"><br>
Coordinator of Development Projects<o:p></o:p></span></p>
<p><em><span style="font-family:"Calibri",sans-serif;color:#8A8B8A"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.lacnic.net&d=DwMD-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=kHlbw2dYUC8QDX5wII6tyFKOZjS_QEYEgxUIj3-adUs&s=y8cg5SO_y2LItTsZBMUDCnpR9rfjLN-sXpoaKRsRHSY&e=">www.lacnic.net
[lacnic.net]</a></span></em><i><span style="color:#8A8B8A"><br>
<em><span style="font-family:"Calibri",sans-serif">Latin American and Caribbean Internet Addresses Registry</span></em></span></i><span style="color:#8A8B8A"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>