<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dear Jordan</div><div>Dear Steve</div><div>Generally I am in agreement with the thrust of your message.</div><div>I think we have addressed or addressing </div><div>The case didn,t , we?</div><div>Kavouss</div><div> <br><br>Sent from my iPhone</div><div><br>On 9 Apr 2015, at 23:06, Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div>
<div>
<div>I would be quite surprised if the new IRP could challenge the board on inaction. </div>
<div><br>
</div>
<div>But even so, the bylaws change that Avri identified from ATRT2 should have been implemented by the board by this point. </div>
<div><br>
</div>
<div>We should call attention to this bylaws change in our recommendations, since the community might need that to force the board to make a decision about formal AC advice. It’s that decision which triggers the ability for community to challenge the decision
vir Reconsideration or IRP.</div>
<div>
<div id="">
<div><br>
</div>
</div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Mathieu Weill<br>
<span style="font-weight:bold">Reply-To: </span>Mathieu Weill<br>
<span style="font-weight:bold">Date: </span>Thursday, April 9, 2015 at 4:50 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:wp1@icann.org">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Becky Burr<br>
<span style="font-weight:bold">Subject: </span>Re: [WP1] board inaction stress tests<br>
</div>
<div><br>
</div>
<div>
<div bgcolor="#FFFFFF" text="#000000">Hi all,<br>
<br>
I understand our requirement is that "the community", or even parts of it, have the ability to challenge the Board for not acting on something (such as a review team recommendation).
<br>
<br>
I thought that, thanks to the extended standing approach of the IRP, as well as its extended standards of review, the community, or parts of it, would have standing to challenge an inaction by the Board ?
<br>
<br>
I am copying Becky to check whether I am totally off-tracks ? <br>
<br>
Best,<br>
Mathieu<br>
<div class="moz-cite-prefix">Le 09/04/2015 22:43, Drazek, Keith a écrit :<br>
</div>
<blockquote cite="mid:504F95D0035A264EBB1BFAABAA772B95497A5A4A@BRN1WNEXMBX01.vcorp.ad.vrsn.com" type="cite">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:"League Gothic";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:HelveticaNeueLTStd-MdIt;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:HelveticaNeueLTStd-Lt;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Times;
panose-1:2 2 6 3 5 4 5 2 3 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.apple-converted-space
{mso-style-name:apple-converted-space;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Thanks Jonathan.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">I agree this is a concern and a gap that needs to be addressed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Board inaction is a risk if it prevents the community from triggering the mechanisms we’re currently designing, so we need to ensure those hooks are
in place.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><a class="moz-txt-link-abbreviated" href="mailto:wp1-bounces@icann.org">wp1-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:wp1-bounces@icann.org">mailto:wp1-bounces@icann.org</a>]
<b>On Behalf Of </b>Jonathan Zuck<br>
<b>Sent:</b> Thursday, April 09, 2015 3:04 PM<br>
<b>To:</b> Thomas Rickert<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:wp1@icann.org">wp1@icann.org</a><br>
<b>Subject:</b> Re: [WP1] board inaction stress tests<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thanks Thomas. I think there’s consensus that we shouldn’t rely only on the “spill the board” option. Avri’s point is that there was a recommendation (already
through a public comment period <u>but as yet unimplemented</u>) by ATRT2 to update the bylaws to include that language. All I’m suggesting at this point is that we roll it into what we’re doing here (as we are with many AoC commitments) to address what would
otherwise be a fairly glaring hole in our efforts. This way we’ve made a best effort at coverage of the stress tests. If the legal team comes back and says it is not enough to trigger a review, we can revisit it on the second pass, no?<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Jonathan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family: Calibri, sans-serif; color: black;">From:
</span></b><span style="font-family: Calibri, sans-serif; color: black;">Thomas Rickert<br>
<b>Date: </b>Thursday, April 9, 2015 at 12:13 PM<br>
<b>To: </b>Jonathan Zuck<br>
<b>Cc: </b>"<a moz-do-not-send="true" href="mailto:wp1@icann.org">wp1@icann.org</a>"<br>
<b>Subject: </b>Re: [WP1] board inaction stress tests<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Jonathan, all,
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">I would like to share a few thoughts on this with you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">- I understand that the legal sub team is reaching out to the firms we use to get an answer to the question whether there is a possibility for the community
to call the board to action. If there was an affirmative response to that, the stress tests would not fail.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">- If there were no such possibility to call the board to action, there would still be the possibility to remove the board. I understand that not all issues
with the Board should be resolved by using this nuclear option, I still think this is a way the board can be threatened to take action requested by the community. Thus, I am not sure the response to the stress test would inevitably be „inadequate“. Avri’s
point is a very good one. By requesting the Board to provide information on progress made and action / inaction, the Board is forced to deal with recommendations and provide a rationale for their (in)activity. One of the concerns would certainly be around
security, stability and resiliency of the DNS. If the Board chooses to ignore a recommendation by the SSAC and puts that in writing, inaction would likely be a violation of the bylaws we are working on and could lead to removing the Board. To me, Avri’s recommendation
combined with the possibility to get the board removed, could be deemed a sufficient response to the stress test. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">It is imperative that we closely collaborate with the CWG on this, so I guess it would be worthwhile to discuss with the CWG as to when they would deem a response
adequate or inadequate so that we apply the same standards.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Best,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Thomas<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;">Am 09.04.2015 um 15:46 schrieb Jonathan Zuck <<a moz-do-not-send="true" href="mailto:jzuck@actonline.org">jzuck@actonline.org</a>>:<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
<div>
<div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">Folks,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">We didn't end up with time for this on the Wenesday WP1 call but I, and others, continue to be concerned about scenarios where the board fails to act.
6 of the approved stress tests involve a failure to act on the part of the board (as opposed to a decision we can oppose) and, as such, will not evaluate well with what appears to be the current draft for public comment. There's a proposed bylaw change from
ATRT2 that should help, along with some minor language changes from WP2.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">When ST-WP applies the stress tests to proposed mechanisms, we look at all proposed measures that are under active consideration in the CCWG. (Those
are the measures cited in the right column of each stress test). When the CCWG and CWG package their proposals for public comment, the ST-WP can then re-apply the stress tests to what is actually proposed.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">6 stress tests anticipated a community power that may fail to make the cut for first public comment: a proposal from the Frankfurt meeting would allow
the community to force ICANN to implement a previously-approved Review Team Recommendation or consensus policy. Another suggested power would allow the community to force ICANN to respond to formal advice from an Advisory Committee (SSAC, ALAC, GAC, RSSAC).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">The ST-WP notes that several stress tests would likely flip from ’Adequate’ to ‘Inadequate’ if the community lacked any new powers to force ICANN to
consider and respond to formal advice from an Advisory Committee. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">You might recall that Alan Greenberg originally brought up the notion of "compelling the board to take action” in Frankfurt and there are several of
the existing stress tests that highlight the need for that capability on the part of the community. Specifically, <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">Stress test 11 was inspired by the recent breach at ICANN and the inability of the community to extract information about the breach. Without the ability
to spur action, that stress test would fail. This stress test relies upon the community’s ability to “force ICANN to implement a recommendation arising from an AOC review, namely SSR"<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">Stress test 17 was about recommendations that are ignored by the board. One example we have used for some time is on the issue of Name Collisions and
certs where a fairly large outcry on the part of the community was required to spur action a year ago. Another example is dotless domains where there was very specific advice from SSAC as well as consensus concern and the board was slow to respond. This stress
test relies upon the community’s ability to "force ICANN to respond to recommendations from advisory committees such as SSAC."<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">There is a similar concern with stress tests 3,4, 20, and 22, since they rely upn community ability to “force ICANN to implement a consensus policy or
recommendation of an AoC review” <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">Avri brought up recommendation 9 of the ATRT with respect to advice which dictates the board respond to advice in a timely manner:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">9.1. ICANN Bylaws Article XI should be amended to include the following language to mandate Board Response to Advisory Committee Formal Advice: <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><i><span style="font-family: Calibri, sans-serif; color: black;">The ICANN Board will respond in a timely manner to formal advice from all Advisory Committees, explaining what action it took and the rationale for
doing so.</span></i><span style="font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">The question then arose whether a board "response" would be sufficient to trigger the other review mechanisms currently under consideration by WP2 so
it was resolved to discuss that with Becky and her team. Perhaps it would be enough to dictate that the trigger mechanism for a review is a decision or response from the board. If not, we might need revisit a specific community power to induce the board to
vote on a recommendation so that the vote can act as a trigger for further review if necessary.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">I would really like to see if we could get these two changes into our draft before it goes to public comment. Thank you.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;">Jonathan<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
<div id="Signature">
<div name="divtagdefaultwrapper">
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:18.0pt;font-family:"League
Gothic","serif";color:black">Jonathan Zuck</span><span style="font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><i><span style="font-family: HelveticaNeueLTStd-MdIt, serif; color: black;">President</span></i><span style="font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: HelveticaNeueLTStd-Lt, serif; color: black;">202-331-2130 X 101 |<span class="apple-converted-space"> </span><a moz-do-not-send="true" href="mailto:jzuck@actonline.org">jzuck@actonline.org</a><span class="apple-converted-space"> </span>|
Skype: jvzuck</span><span style="font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="background:white"><span style="font-size:10.5pt;color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="background:white"><span style="font-size:13.5pt;font-family:"League
Gothic","serif";color:#5F605D">ACT | The App Association</span><span style="font-family: Calibri, sans-serif; color: black;"><o:p></o:p></span></p>
</div>
<table class="MsoNormalTable" style="width:150.0pt" border="0" cellpadding="0" cellspacing="3" width="200">
<tbody>
<tr style="height:9.0pt">
<td style="width:35.0pt;padding:.75pt
.75pt .75pt .75pt;height:9.0pt" width="47">
<div>
<p class="MsoNormal" style="mso-line-height-alt:9.0pt"><span style="font-family:"Times","serif""><a moz-do-not-send="true" href="https://twitter.com/actonline"><span style="color:purple;text-decoration:none"><img moz-do-not-send="true" id="_x0000_i1025" src="https://dl.dropboxusercontent.com/u/6442666/twitter.png" border="0" height="18" width="70"></span></a></span><o:p></o:p></p>
</div>
</td>
<td style="width:35.0pt;padding:.75pt
.75pt .75pt .75pt;height:9.0pt" width="47">
<div>
<p class="MsoNormal" style="mso-line-height-alt:9.0pt"><span style="font-family:"Times","serif""><a moz-do-not-send="true" href="https://www.facebook.com/actonline.org"><span style="color:purple;text-decoration:none"><img moz-do-not-send="true" id="_x0000_i1026" src="https://dl.dropboxusercontent.com/u/6442666/fb.png" border="0" height="18" width="70"></span></a></span><o:p></o:p></p>
</div>
</td>
<td style="width:39.5pt;padding:.75pt
.75pt .75pt .75pt;height:9.0pt" width="53">
<div>
<p class="MsoNormal" style="mso-line-height-alt:9.0pt"><span style="font-family:"Times","serif""><a moz-do-not-send="true" href="http://actonline.org/"><span style="color:purple;text-decoration:none"><img moz-do-not-send="true" id="_x0000_i1027" src="https://dl.dropboxusercontent.com/u/6442666/actonline.png" border="0" height="18" width="79"></span></a></span><o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<p class="MsoNormal" style="background:white"><span style="font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: black;">_______________________________________________<br>
WP1 mailing list<br>
</span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><a moz-do-not-send="true" href="mailto:WP1@icann.org"><span style="font-size: 9pt; font-family: Helvetica, sans-serif;">WP1@icann.org</span></a></span><span style="font-size: 9pt; font-family: Helvetica, sans-serif; color: black;"><br>
</span><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/wp1"><span style="font-size: 9pt; font-family: Helvetica, sans-serif;">https://mm.icann.org/mailman/listinfo/wp1</span></a><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif; color: black;"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
WP1 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WP1@icann.org">WP1@icann.org</a><a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: +33 1 39 30 83 06
<a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</div>
</div>
</span>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>WP1 mailing list</span><br><span><a href="mailto:WP1@icann.org">WP1@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/wp1">https://mm.icann.org/mailman/listinfo/wp1</a></span><br></div></blockquote></body></html>