<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">I don't believe that Christopher Wilkinson has posting rights to this list. Therefore, I am forwarding the email below.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Christopher Wilkinson</b> <span dir="ltr"><<a href="mailto:lists@christopherwilkinson.eu">lists@christopherwilkinson.eu</a>></span><br>Date: Tue, Aug 2, 2016 at 3:18 PM<br>Subject: Re: [CWG-Stewardship] [client com] IANA IPR Community Agreement and License Agreement drafts<br>To: "<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a> IANA" <<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>><br>Cc: Client Committee <<a href="mailto:cwg-client@icann.org">cwg-client@icann.org</a>>, <a href="mailto:contreraslegal@att.net">contreraslegal@att.net</a>, JOSHUA HOFHEIMER <<a href="mailto:jhofheimer@sidley.com">jhofheimer@sidley.com</a>><br><br><br><div style="word-wrap:break-word">Good evening<div><ul>
<li style="margin:0px;font-size:14px;font-family:Times"></li>
<li style="margin:0px;font-size:14px;font-family:Times"><b>Reference: Proposed ICANN/PTI-IETF Trust License Agreement (several drafts)</b></li>
<li style="margin:0px;font-size:14px;font-family:Times"></li>
<li style="margin:0px;font-size:14px;font-family:Times">I have a few comments regarding these texts. Since none of them are conclusive I reserve my definitive comments to the necessary public consultation on the proposed final agreement, particularly as I am not party to the on-going negotiations. Indeed it is absolutely essential that this License Agreement goes out for public comment to - at least - the full CWG List. The license agreement will regulate several critical parameters regarding notably the terms and conditions of the reassignment of IANA IPR to eventual successor entity to ICANN/PTI and the registration of non-IETF protocols.</li>
<li style="margin:0px;font-size:14px;font-family:Times"></li>
<li style="margin:0px;font-size:14px;font-family:Times">1.<span style="white-space:pre-wrap"> </span>In general I find that the draft agreement is not balanced. The PTI party benefits from extensive privileges, particularly insofar as matters are to be determined at the parties' own expense. In that context may I recall that the IETF Trust has an annual budget of about $50k, of which $25k is for legal expenses. Whereas PTI - as we have seen recently - can spend millions of dollars on legal fees. Specifically, whenever it is said that each party may be represented by counsel, one must assume that PTI will be represented, as we have recently seen, whatever the cost, and the IETF Trust will be represented at best by itself, without the financial support of ICANN which would have been available in the past to defend the interests of IANA.</li>
</ul><div style="margin:0px;font-size:14px;font-family:Times">In general, this license agreement should say nothing about succession, separability or separation of the IANA functions. All that, should the need ever arise is matter for the ICANN Empowered Community as a whole and should not be preempted by a technical license agreement between ICANN/PTI and the IETF Trust, the former having no standing to regulate its own future and the latter - as such - having very little standing in the ICANN community, except through the participation of its members in their respective capacities.</div><div style="margin:0px;font-size:14px;font-family:Times"><br></div><div style="margin:0px;font-size:14px;font-family:Times">My comments below, follow the order of the document and not necessarily the relative importance of the issues.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">2.<span style="white-space:pre-wrap"> </span>Article 1.1:<span style="white-space:pre-wrap"> </span>The exclusive reference to the American Arbitration Association (AAA) is not appropriate in this context. The scope of the agreement is potentially 'global' and 'worldwide'.</div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span>(a) there are several other arbitration fora which have a broader global reach and (b) at the very least, ICANN/PTI and IETF Trust should conduct an open call for proposals to fulfil this function.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">3.<span style="white-space:pre-wrap"> </span>Article 1.2:<span style="white-space:pre-wrap"> </span>The reference that "the Internet Society … is not an Affiliate of the Licensor." is perplexing to say the least:</div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span>(a) I recall that IETF and ISOC created the Trust; (b) several of its recent Trustees are present or past ISOC Board members, (c ) the IETF Trust certainly makes an annual report to the ISOC Board:</div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span><a href="http://www.internetsociety.org/search/gss/ietf%20trust" target="_blank">http://www.internetsociety.org/search/gss/ietf%20trust</a></div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span>I suggest that it would be more transparent to state what IS the relationship between ISOC and the Trust, rather than to state what it is NOT.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">4.<span style="white-space:pre-wrap"> </span>Articles 2.1 and 3.1:<span style="white-space:pre-wrap"> </span>For reasons that I have set out on several previous occasions, I do not accept the language that "… three independent and separately terminable licenses are granted thereunder with respect to the three categories of IANA services …".</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">Indeed, eventual separation of the IANA functions would give rise to unmanageable oversight requirements on the part of the rest of the Internet community, including the GAC.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">5.<span style="white-space:pre-wrap"> </span>Article 4.1:<span style="white-space:pre-wrap"> </span>Goodwill: The goodwill that accrues to IANA relates to its past and present operators - in some cases at a personal level. The idea that such goodwill can be assigned to the IETF Trust by a simple legal act appears to be rather fanciful. Indeed I rather doubt that the IETF Trust would be volunteering for that role!</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">6.<span style="white-space:pre-wrap"> </span>Article 4.3: Policing and enforcement: So, the right of enforcement, including employment of counsel, devolves to the IETF Trust, with a legal budget of $25k! </div><div style="margin:0px;font-size:14px;font-family:Times"> <span style="white-space:pre-wrap"> </span>Colourful, if not absurd. Insofar as such enforcement has been required in the recent past, the costs would have devolved to ICANN.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">7.<span style="white-space:pre-wrap"> </span>Article 6.1: Term: the proposed amendment reinforces the supposition that the authors envisage separation of the IANA functions. No appropriate in this context.</div><div style="margin:0px;font-size:14px;font-family:Times"><br></div><div style="margin:0px;font-size:14px;font-family:Times">8.<span style="white-space:pre-wrap"> </span>Article 6.6 c: I do not agree to the amendment "… or to its successor licensee(s) for the terminated services…"</div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span>This amendment could (a) by-pass or short-cut the established procedures within the Empowered Community, and (b) presupposes that there would be plural successor licensees. Not appropriate in this context.</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">9.<span style="white-space:pre-wrap"> </span>Exhibit A: IANA Protocol Parameter Service:<span style="white-space:pre-wrap"> </span>I do not agree to the proposed amendment "(ii) registering protocol parameters of interest to the Internet community, upon agreement with other parties, provided such protocol parameters do to conflict with clauses (i) and (iii)". (i.e. specified in RFCs and/or made available to the public - but not necessarily free for use.)</div><div style="margin:0px;font-size:14px;font-family:Times;min-height:18px"><br></div><div style="margin:0px;font-size:14px;font-family:Times">This amendment would open the door to the registration of proprietary protocol parameters which would cumulatively, over time, prejudice the Open Internet, increase costs to the final users and undermine the conditions of fair competition among Internet based services.</div><div style="margin:0px;font-size:14px;font-family:Times"><br></div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> </span>*<span style="white-space:pre-wrap"> </span>*<span style="white-space:pre-wrap"> </span>* </div><div style="margin:0px;font-size:14px;font-family:Times"><span style="white-space:pre-wrap"> <span style="font-size:15px"> <span style="white-space:pre-wrap"> </span></span></span></div><div style="margin:0px;font-size:14px;font-family:Times">I trust that these comments shall reach the negotiators concerned. May I re-iterate, that the final proposal must be subject to open public consolation of all interested parties.</div><div style="margin:0px;font-size:14px;font-family:Times"><br></div><div style="margin:0px;font-size:14px;font-family:Times">Regards</div><div style="margin:0px;font-size:14px;font-family:Times"><br></div><div style="margin:0px;font-size:14px;font-family:Times">Christopher Wilkinson</div><div><br></div><div><div><div class="h5"><div>On 30 Jul 2016, at 22:43, "Hofheimer, Joshua T." <<a href="mailto:jhofheimer@sidley.com" target="_blank">jhofheimer@sidley.com</a>> wrote:</div><br></div></div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple" style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div><div class="h5"><div><br></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Jonathan, Lise and the Client Committee,<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">See attached. Sidley will prepare a table for your review that highlights the key departures from our proposed drafts.<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Best regards,<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Josh<u></u><u></u></span></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Joshua Hofheimer<u></u><u></u></span></i></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Sidley Austin LLP<u></u><u></u></span></i></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="mailto:jhofheimer@sidley.com" style="color:purple;text-decoration:underline" target="_blank">jhofheimer@sidley.com</a><u></u><u></u></span></i></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="tel:%28213%29%20896-6061" value="+12138966061" target="_blank">(213) 896-6061</a> (LA direct)<u></u><u></u></span></i></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="tel:%28650%29%20565-7561" value="+16505657561" target="_blank">(650) 565-7561</a> (Palo Alto direct)<u></u><u></u></span></i></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><i><span style="font-size:9pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><a href="tel:%28323%29%20708-2405" value="+13237082405" target="_blank">(323) 708-2405</a> (cell)<u></u><u></u></span></i></div></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"> </span></div><div><div style="border-style:solid none none;border-top-width:1pt;border-top-color:rgb(181,196,223);padding:3pt 0in 0in"><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span><a href="mailto:iana-ipr-bounces@nro.net" style="color:purple;text-decoration:underline" target="_blank">iana-ipr-bounces@nro.net</a><span> </span>[mailto:<a href="mailto:iana-" target="_blank">iana-</a><a href="mailto:ipr-bounces@nro.net" style="color:purple;text-decoration:underline" target="_blank">ipr-bounces@nro.net</a>]<span> </span><b>On Behalf Of<span> </span></b>Jorge Contreras<br><b>Sent:</b><span> </span>Saturday, July 30, 2016 10:03 AM<br><b>To:</b><span> </span><a href="mailto:iana-ipr@nro.net" style="color:purple;text-decoration:underline" target="_blank">iana-ipr@nro.net</a><br><b>Subject:</b><span> </span>[Iana-ipr] IANA IPR Community Agreement and License Agreement drafts<u></u><u></u></span></div></div></div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><u></u> <u></u></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">Dear colleagues,<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">We have attached for your review clean and redlined versions of the Community Agreement and License Agreement, which have been marked against the versions distributed on July 5. We have inserted numerous<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">comments in the marked version using the MS Word comment feature. These comments are intended to address specific text or suggestions made by CWG, RIR or IETF during the last round.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">In these candidate agreements, we have accepted a number of suggestions both the operational communities. We know that everyone is anxious to get these done, and many of the changes seem to us to be reasonable and in keeping with the Trust’s responsibilities.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">What we have not accepted, and what we do not believe we can accept, is any arrangement in which the Trust is subject to "approvals" by the CCG. We remain convinced that such acceptance would be contrary to<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">the Trust's anticipated fiduciary responsibility as the holder of the Marks, and the Trustees cannot responsibly expose the Trust to such a threat. We believe that any independent trust would face this problem.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">In addition, we do not think that, given the terms of our Trust Agreement, the Trust is capable of acting as a "steward" for other operational communities. The existing Trust Agreement also does not permit the Trust to transfer away any asset once it is owned by the Trust, so we cannot accept any term that anticipates such a transfer.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">We realize that some people would prefer to amend some terms of the IETF Trust Agreement. That may be possible in the future in order to accommodate some of the above worries. But all changes have to go through the IETF consensus process, and there simply isn't time to do that this year. Hence our agreement must work with the Trust as it currently exists.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">We hope that you will agree that we are making substantive and collegial process here, and we hope you understand that the existing terms of the Trust Agreement are a hard limit on what we may possibly<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:-webkit-standard,serif">do. We look forward to additional comments and to a fruitful discussion on our next call.<u></u><u></u></span></div></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif"> </span></div></div><div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif">Jorge L. Contreras<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif">Contreras Legal Strategy LLC<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif">1711 Massachusetts Ave. NW, No. 710<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif">Washington, DC 20036<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif"><a href="mailto:contreraslegal@att.net" style="color:purple;text-decoration:underline" target="_blank">contreraslegal@att.net</a><u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif"> </span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif">The contents of this message may be attorney-client privileged and confidential. If you are not the intended recipient, please delete this message immediately.<u></u><u></u></span></div></div><div><div style="margin:0in 0in 0.0001pt;font-size:12pt;font-family:'Times New Roman',serif"><span style="font-size:8.5pt;font-family:Calibri,sans-serif"> </span></div></div></div></div><div><br></div><div> <br></div><p>****************************************************************************************************<br>This e-mail is sent by a law firm and may contain information that is privileged or confidential.<br>If you are not the intended recipient, please delete the e-mail and any attachments and notify us<br>immediately.<br><br>****************************************************************************************************</p></div></div><span><License-Agreement IANA IPR 2016-07-30 clean.doc></span><span><License-Agreement IANA IPR 2016-07-30 marked vs 07-05.pdf></span><span><Community-Agreement-2016-07-30 clean.doc></span><span><Community-Agreement-2016-07-30 marked vs 07-05.pdf></span>_______________________________________________<br>Iana-ipr mailing list<br><a href="mailto:Iana-ipr@nro.net" style="color:purple;text-decoration:underline" target="_blank">Iana-ipr@nro.net</a><br><a href="https://www.nro.net/mailman/listinfo/iana-ipr" style="color:purple;text-decoration:underline" target="_blank">https://www.nro.net/mailman/listinfo/iana-ipr</a><span class=""><br>_______________________________________________<br>Cwg-client mailing list<br><a href="mailto:Cwg-client@icann.org" style="color:purple;text-decoration:underline" target="_blank">Cwg-client@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/cwg-client" style="color:purple;text-decoration:underline" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-client</a><br></span></div></blockquote></div><br></div></div><br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></div><br></div>