<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.im
{mso-style-name:im;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">What you said Greg is all the more reason why the accountability mechanisms need to be strong, just in case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Greg Shatan [mailto:gregshatanipc@gmail.com]
<br>
<b>Sent:</b> Friday, June 05, 2015 3:27 PM<br>
<b>To:</b> Gomes, Chuck<br>
<b>Cc:</b> avri@acm.org; cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] Final response from DT-M regarding public comments<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I think that unless we prohibit it, it is an inherent right of the Board (and management) to explore and potentially adopt other methods and/or providers for carrying out ICANN's responsibilities
relating to the IANA Functions. It may be as simple as some small (in size, not in effect) drafting fixes that make it clear that this is the only path to explore or adopt such changes.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Right now it appears highly unlikely that the Board and management would ever want to explore a radical change in how the IANA Functions are carried out relative to ICANN. Indeed, the emphasis
has been on maintaining the status quo (albeit without the NTIA's involvement). Indeed, ICANN's ultimate responsibility for the IANA Functions is a core value in the Articles of Incorporation and Bylaws, so completely exiting the "IANA Functions business"
at all levels would require serious changes in governance documents, etc., etc., which would run up against the powers relating to changing bylaws that the CCWG contemplates.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">All that said, off the top of my head, I can't recall any formal limitation on ICANN's ability to exercise its business judgment with regard to making major changes in this area, short of
a complete exit. Maybe there are some existing limitations that would apply, and I'm not thinking it through. (For instance, would such a potential change trigger a PDP? Would such a change even be a policy decision?) There may be practical limitations
-- imagine the uproar if a unilateral, top-down decision was taken to outsource the IANA Functions to the Root Zone Management Company (<a href="http://www.rootzonemanagement.com.au/about.htm">http://www.rootzonemanagement.com.au/about.htm</a>). But an "uproar"
is not an enforceable right or prohibition.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">So I would agree that this is a "hole" or at least an unanticipated angle on this issue.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Greg<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Jun 5, 2015 at 12:38 PM, Gomes, Chuck <<a href="mailto:cgomes@verisign.com" target="_blank">cgomes@verisign.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I am inclined to agree with this: " I do not think that an RFP should be initiated without an SIFR & SCWG."<br>
<span style="color:#888888"><br>
<span class="hoenzb">Chuck</span><br>
</span><br>
<span class="im">-----Original Message-----</span><br>
<span class="im">From: <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>] On Behalf Of Avri Doria</span><br>
<span class="im">Sent: Friday, June 05, 2015 11:51 AM</span><br>
<span class="im">To: <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a></span><br>
<span class="im">Subject: Re: [CWG-Stewardship] Final response from DT-M regarding public comments</span><br>
<br>
<span class="im">Hi,</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">That is a fascinating question and perhaps a hole in the solution. I do not think that an RFP should be initiated without an SIFR & SCWG. I have no real issue with the Board, or even the members if we have members, initiating a SIFR if
they see problems no one else does.<br>
Perhaps this is the catch all for the wider community issue that some claim are not included.<br>
<br>
But to have them just decide on their own, for commercial or 'profitability' reasons perhaps, without community involvement seems very inappropriate.<br>
<br>
avri<br>
<br>
<br>
<br>
On 05-Jun-15 07:53, Matthew Shears wrote:<br>
> I agree Greg and have similar concerns to Staffan and Martin. But on<br>
> your second point have we specified how the board would do this:<br>
><br>
> t/he Board could initiate an RFP or other change to IANA functions<br>
> operations without a SIFR/<br>
><br>
> Matthew<br>
><br>
> On 6/5/2015 12:48 PM, Greg Shatan wrote:<br>
>> I see this as a community power. Frankly, the Board could initiate an<br>
>> RFP or other change to IANA functions operations without a SIFR.<br>
>><br>
>> Greg<br>
>><br>
>> On Friday, June 5, 2015, Staffan Jonson <<a href="mailto:staffan.jonson@iis.se">staffan.jonson@iis.se</a><br>
>> <mailto:<a href="mailto:staffan.jonson@iis.se">staffan.jonson@iis.se</a>>> wrote:<br>
>><br>
>> The rationale for giving ICANN (or PTI) the ability to initiate a<br>
>> SIFR would allude to some general principles of transparency<br>
>> ('everybody should be able to check everybody'). In my view the<br>
>> principles behind is an interesting discussion, but not very much<br>
>> more. The current Hybrid model and contract governance give ICANN<br>
>> a lot of power, the upper hand so to say. So according to<br>
>> proposal ICANN will already control IANA functions operations.<br>
>><br>
>> So who would ICANN scrutinize with its review power? Its own<br>
>> supporting organizations? SO:s and AC:s? Most cc:s are not even<br>
>> contracted with ICANN, and have few plans to become. Or would<br>
>> ICANN need to review its own IANA operations with an external<br>
>> organization? The latter would to me indicate lack of control. Or<br>
>> dual representation by MS community.<br>
>><br>
>> So a practical answer is: It wouldn't need to. And I see very few<br>
>> possibilities of change in this area.<br>
>><br>
>> So my answer is more along a pragmatic stream: Is this relevant<br>
>> for the CWG? Now? Do we really, really need to include this<br>
>> aspect in transition? This late? Are we limiting our<br>
>> deliberations to what is absolutely necessary for the transition,<br>
>> or are we - once the window of ooportunity is open- trying to<br>
>> make it a perfect world? I would say no to both.<br>
>><br>
>> Another answer relates to direct process: The need for a review<br>
>> is about accountability, so any power for ICANN to review itself<br>
>> should preferably be discussed by CCWG (WS2).<br>
>><br>
>><br>
>><br>
>> However what might be valid, is that ICG soon will have to handle<br>
>> up to three parallel mechanisms for review (one from each<br>
>> community within CWG). Maybe we should remind them of the<br>
>> potential need to coordinate review mechanisms.<br>
>><br>
>><br>
>><br>
>> Staffan<br>
>><br>
>><br>
>><br>
>> With best regards<br>
>><br>
>> Staffan Jonson<br>
>><br>
>><br>
>><br>
>> Mr. Staffan Jonson, Senior Policy Adviser<br>
>><br>
>> .SE (The Internet Infrastructure foundation)<br>
>><br>
>><br>
>><br>
>> BOX 7399 | SE-103 91 STOCKHOLM | SWEDEN<br>
>><br>
>> Direct: <a href="tel:%2B46%208%20452%2035%2074">+46 8 452 35 74</a> | SMS:
<a href="tel:%2B46%2073%20317%2039%2067">+46 73 317 39 67</a><br>
>><br>
>> <a href="mailto:staffan.jonson@iis.se">staffan.jonson@iis.se</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:staffan.jonson@iis.se">staffan.jonson@iis.se</a>');> |<br>
>> <a href="http://www.iis.se/en" target="_blank">www.iis.se/en</a> <<a href="http://www.iis.se/en" target="_blank">http://www.iis.se/en</a>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> *Från:*<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');><br>
>> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');>]<br>
>> *För *Martin Boyle<br>
>> *Skickat:*den 5 juni 2015 12:01<br>
>> *Till:* Matthew Shears; Milton L Mueller;<br>
>> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>');><br>
>> *Ämne:* Re: [CWG-Stewardship] Final response from DT-M regarding<br>
>> public comments<br>
>><br>
>><br>
>><br>
>> I struggle to imagine why the ICANN Board (any more than the PTI<br>
>> Board) would want to initiate an SIFR, in particular without the<br>
>> support of the community. Worse, I would feel that there would<br>
>> be a "cunning plan" somewhere behind such a decision and that<br>
>> leaves me seriously questioning why we would want this process to<br>
>> be triggered in such a way. No support for an SIFR, no<br>
>> overriding ICANN (or PTI) Board to ignore interests of the community.<br>
>><br>
>> If someone can see possible reasons, I'd like to hear them. Then<br>
>> any trigger route could be defined (and limited) more carefully.<br>
>><br>
>><br>
>><br>
>> Martin<br>
>><br>
>><br>
>><br>
>> *From:*<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');><br>
>> [mailto:<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');>]<br>
>> *On Behalf Of *Matthew Shears<br>
>> *Sent:* 05 June 2015 06:17<br>
>> *To:* Milton L Mueller; <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>');><br>
>> *Subject:* Re: [CWG-Stewardship] Final response from DT-M<br>
>> regarding public comments<br>
>><br>
>><br>
>><br>
>> But what would the thresholds be? And, currently an SIFR comes<br>
>> as a result of other mechanisms being exhausted as well as the<br>
>> IANA probems resolution process.<br>
>><br>
>> /The Special IFR would be triggered by a supermajority vote of<br>
>> each of the ccNSO and GNSO Councils according to their normal<br>
>> procedures for determining supermajority. /<br>
>><br>
>> Would we require a supermajority of only the Board, or in<br>
>> addition to the ccNSO and GNSO. And as a result of the<br>
>> mechanisms being exhausted? I would assume so.<br>
>><br>
>> Matthew<br>
>><br>
>> On 6/5/2015 4:05 AM, Milton L Mueller wrote:<br>
>><br>
>> I can't<br>
>><br>
>> --MM<br>
>><br>
>><br>
>><br>
>> -----Original Message-----<br>
>><br>
>> From: <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');><br>
>> [mailto:<a href="mailto:cwg-stewardship">cwg-stewardship</a><br>
>> <javascript:_e(%7B%7D,'cvml','cwg-stewardship');>-<br>
>><br>
>> <a href="mailto:bounces@icann.org">bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:bounces@icann.org">bounces@icann.org</a>');>] On Behalf Of<br>
>> Gomes, Chuck<br>
>><br>
>> Sent: Thursday, June 4, 2015 5:02 PM<br>
>><br>
>> To: <a href="mailto:avri@acm.org">avri@acm.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:avri@acm.org">avri@acm.org</a>');>;<br>
>> <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>');><br>
>><br>
>> Subject: Re: [CWG-Stewardship] Final response from DT-M<br>
>> regarding public<br>
>><br>
>> comments<br>
>><br>
>><br>
>><br>
>> Good catch Avri and good question. Can anyone think of a<br>
>> reason why the<br>
>><br>
>> ICANN Board should not be able to request an SIFR?<br>
>><br>
>><br>
>><br>
>> Chuck<br>
>><br>
>><br>
>><br>
>> -----Original Message-----<br>
>><br>
>> From: <a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>');><br>
>> [mailto:<a href="mailto:cwg-stewardship">cwg-stewardship</a><br>
>> <javascript:_e(%7B%7D,'cvml','cwg-stewardship');>-<br>
>><br>
>> <a href="mailto:bounces@icann.org">bounces@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:bounces@icann.org">bounces@icann.org</a>');>] On Behalf Of<br>
>> Avri Doria<br>
>><br>
>> Sent: Thursday, June 04, 2015 4:39 PM<br>
>><br>
>> To: <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a>');><br>
>><br>
>> Subject: Re: [CWG-Stewardship] Final response from DT-M<br>
>> regarding public<br>
>><br>
>> comments<br>
>><br>
>><br>
>><br>
>> Hi,<br>
>><br>
>><br>
>><br>
>> I am part of DT-M and partly responsible for this.<br>
>><br>
>><br>
>><br>
>> But. It has a cost, which I did mention on the DT-M list:<br>
>><br>
>><br>
>><br>
>> There is currently no mechanism defined for the Board to initiate a SIFR.<br>
>><br>
>><br>
>><br>
>> Should there be?<br>
>><br>
>><br>
>><br>
>> avri<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> On 04-Jun-15 16:10, Gomes, Chuck wrote:<br>
>><br>
>><br>
>><br>
>> Here is DT-M's final proposed response to comment<br>
>> review tool item #<br>
>><br>
>> 246 regarding AFRALO's suggestion that the PTI Board<br>
>> be allowed to<br>
>><br>
>> initiate a SIFR directly: *"DT M carefully<br>
>> considered the<br>
>><br>
>> recommendation to allow the PTI Board to initiate a<br>
>> Special IFR but<br>
>><br>
>> decided against that while at the same time noting<br>
>> that the PTI Board<br>
>><br>
>> could request that the ICANN Board consider doing<br>
>> so."*<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> If there are any questions, please let me know.<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> Chuck<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> "This message (including any attachments)<br>
>> is intended only<br>
>><br>
>> for the use of the individual or entity to<br>
>> which it is<br>
>><br>
>> addressed, and may contain information that<br>
>> is non-public,<br>
>><br>
>> proprietary, privileged, confidential and<br>
>> exempt from<br>
>><br>
>> disclosure under applicable law or may be<br>
>> constituted as<br>
>><br>
>> attorney work product. If you are not the<br>
>> intended<br>
>><br>
>> recipient, you are hereby notified that any<br>
>> use,<br>
>><br>
>> dissemination, distribution, or copying of<br>
>> this<br>
>><br>
>> communication is strictly prohibited. If<br>
>> you have received<br>
>><br>
>> this message in error, notify sender<br>
>> immediately and delete<br>
>><br>
>> this message immediately."<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>><br>
>> CWG-Stewardship mailing list<br>
>><br>
>> <a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>');><br>
>><br>
>> <a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> ---<br>
>><br>
>> This email has been checked for viruses by Avast antivirus software.<br>
>><br>
>> <a href="https://www.avast.com/antivirus" target="_blank">https://www.avast.com/antivirus</a><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>><br>
>> CWG-Stewardship mailing list<br>
>><br>
>> <a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>');><br>
>><br>
>> <a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
>><br>
>> _______________________________________________<br>
>><br>
>> CWG-Stewardship mailing list<br>
>><br>
>> <a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>');><br>
>><br>
>> <a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
>><br>
>> _______________________________________________<br>
>><br>
>> CWG-Stewardship mailing list<br>
>><br>
>> <a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
>> <javascript:_e(%7B%7D,'cvml','<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>');><br>
>><br>
>> <a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
>><br>
>><br>
>><br>
>> --<br>
>><br>
>> Matthew Shears<br>
>><br>
>> Global Internet Policy and Human Rights<br>
>><br>
>> Center for Democracy & Technology (CDT)<br>
>><br>
>> <a href="tel:%2B%2044%20%280%29771%20247%202987">+ 44 (0)771 247 2987</a><br>
>><br>
><br>
> --<br>
> Matthew Shears<br>
> Global Internet Policy and Human Rights Center for Democracy &<br>
> Technology (CDT)<br>
> <a href="tel:%2B%2044%20%280%29771%20247%202987">+ 44 (0)771 247 2987</a><br>
><br>
><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" target="_blank">
https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" target="_blank">https://www.avast.com/antivirus</a><br>
<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" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><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" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>