<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<base href="x-msg://138/"><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;}
/* 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-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Courier New";
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-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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> arin-ppml-bounces@arin.net [mailto:arin-ppml-bounces@arin.net]
<b>On Behalf Of </b>John Curran<br>
<br>
</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">To be clear, Microsoft met the same needs-based criteria as any other <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">transfer recipient and the resources they hold are subject to number <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">resource policies in the region.<o:p></o:p></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D">[Milton L Mueller] John, you probably read an earlier version of the study which did not include our analysis of the use of the number blocks purchased by MSFT.
(We wanted to verify certain methodological aspects of that before publishing it.)
<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D">We found that since acquiring the addresses, which is now more than a year ago, MSFT has actually _reduced_ the number of blocks being routed. They have only put
into service a few /24s and /22s I think, and have actually withdrawn from use a couple of /16s.
<o:p></o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p> </o:p></span></i></b></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D">Now, I cannot assert that ARIN did not do a needs assessment. Only ARIN staff can verify or refute that. I can, however, assert with confidence that a 1-year time
horizon was used at that time (according to your policy in place), and that the entity who claimed need based on that timeline is not, after more than one year, using the vast majority of the addresses; indeed, fewer addresses from the Nortel block are being
routed after the transaction than before. Therefore, there are legitimate questions to be raised about what “needs assessment” actually consists of.</span></i></b><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D">[Milton L Mueller] The significance of this fact increases when, as you can see from the comments on our blog, there are complaints that many transactions of entities
less powerful than MSFT have been killed by the needs assessment process. </span>
</i></b><span style="font-size:11.0pt;font-family:"Courier New";color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>