<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On Jun 3, 2014, at 12:51 PM, Mike Burns <<a href="mailto:mike@iptrading.com">mike@iptrading.com</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<blockquote type="cite">
<div lang="EN-US" dir="ltr" link="#0563c1" vlink="#954f72" style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div dir="ltr">
<div style="font-size: 12pt; font-family: Calibri;">
<div>Retaining the needs policy will result in a Whois filled with zombie corporations, resuscitated from the dead, alive only in the sense of their Whois listing and (sometimes) up-to-date corporate filing. These zombie corporations will be owned by companies
like David’s, whose business decisions drive them towards non-policy-compliant address transfers. Whois will not be updated.</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
Mike -
<div><br>
</div>
<div> Indeed, there quite likely will be some organizations that end up taking that approach; </div>
<div> it is not possible to know whether the "non-compliant" aspect will deter them such that </div>
<div> they transfer within policy constraints (i.e. limited to 2 years of expected growth) </div>
<div> </div>
<div> Note also that some organizations may transfer in compliance with policy and existing </div>
<div> need, but then lock in the option with the current holder for future transfer of any </div>
<div> remainder of the address block (which is neither detectable nor within ARIN's remit.) </div>
<div> Whether that kind of outcome meets the desired policy goals is not clear, but it should</div>
<div> be recognized as a rather likely in light of present policy and desire by networks for</div>
<div> more certainty in their available supply of IPv4 number resources.</div>
<div><br>
</div>
<div> In the end, the community needs to consider the ongoing expected benefits of the </div>
<div> needs-based transfer constraints in light of these evolving conditions.</div>
<div><br>
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>