<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On Jul 14, 2014, at 9:06 PM, Jeffrey Lyon <<a href="mailto:jeffrey.lyon@blacklotus.net">jeffrey.lyon@blacklotus.net</a>> wrote:<br>
<div>
<blockquote type="cite">
<p dir="ltr">It applies to all but is of zero benefit to large orgs with contiguous space. This idea that it allows big orgs to horde space is a red herring.</p>
</blockquote>
</div>
<div>Jeffrey - </div>
<div> </div>
<div> For sake of argument, imagine a large ISP which over the course of time has</div>
<div> ended up with a /8, two /16, and a /14 IPv4 blocks (with the /14 being the most</div>
<div> recently issued block because of nearly full utilization of all prior blocks at the</div>
<div> time.)</div>
<div> </div>
<div> Under present policy, the ISP cannot request address space until they have </div>
<div> brought the utilization of the most recently issued block (the /14) up to 80%.</div>
<div> </div>
<div> Under the proposed policy, the ISP is immediately eligible to request space,</div>
<div> since their aggregate utilization (even with a completely unused /14) is going </div>
<div> to be very high (potentially as much as 97% due to the fully-used /8 block.)</div>
<div><br>
</div>
<div> The proposed policy allows organizations to request space so long as their </div>
<div> aggregate utilization is higher than 80%, and this means many existing </div>
<div> organization with large IPv4 holdings will suddenly qualify to receive an </div>
<div> additional allocation if they choose to request it. Whether that is desirable</div>
<div> or not is a matter for the community to decide.</div>
<div><br>
</div>
<div>FYI,</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>
</body>
</html>