<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Folks -
<div class=""> </div>
<div class=""> We’ve had a wonderful time reviewing how we got to the present state, but as </div>
<div class=""> Mr. Huberman pointed out, we’re now approaching runout of the IPv4 free pool</div>
<div class=""> for the ARIN region, and with this will obviously come an increased need by</div>
<div class=""> some parties for IPv4 transfers. The ability of this community to set policy </div>
<div class=""> applicable to IPv4 transfers should be taken as basic assumption (and we </div>
<div class=""> will certainly keep the community apprised if there should ever be a change </div>
<div class=""> in this ability.)</div>
<div class=""><br class="">
</div>
<div class=""> With that in mind, I’d like to challenge the community to consider and clearly</div>
<div class=""> state the underlying purpose for having constraints on IPv4 transfers, and how</div>
<div class=""> such policy meets ARIN’s mission <<a href="https://www.arin.net/about_us/overview.html" class="">https://www.arin.net/about_us/overview.html</a>></div>
<div class=""> or policy development goals <<a href="https://www.arin.net/policy/pdp.html" class="">https://www.arin.net/policy/pdp.html</a>>. While it is</div>
<div class=""> true that our default position on registry policy is that we preserve the status quo </div>
<div class=""> until a change is shown to be needed, the unique one-time event of the runout</div>
<div class=""> of the IPv4 free pool warrants a fresh statement and review of the purposes that</div>
<div class=""> we aim to fulfill via the IPv4 transfer policy.</div>
<div class=""><br class="">
</div>
<div class=""> Our current needs-based IPv4 transfer policy is basically derived from the IPv4</div>
<div class=""> allocation policy, and the assumption that the registry should determine those </div>
<div class=""> parties who should be issued IPv4 address space. This is very reasonable</div>
<div class=""> assumption when the resources are coming from the IPv4 regional free pool, </div>
<div class=""> but it is unclear what purpose is fulfilled in making the same determination </div>
<div class=""> when the resources are coming from another party.</div>
<div class=""><br class="">
</div>
<div class=""> If the community can agree on a common statement of the purpose for the IPv4</div>
<div class=""> transfer policy (which will take active engagement towards trying to understand</div>
<div class=""> everyone’s concerns), then it might be possible to lay groundwork for simpler</div>
<div class=""> transfer policy for which everyone understands the underlying basis, and thus</div>
<div class=""> has an much easier time supporting.</div>
<div class=""><br class="">
</div>
<div class=""> So, to start the discussion, what is the underlying need for an IPv4 transfer</div>
<div class=""> policy, and why? I will get things going with a potential less-contentious </div>
<div class=""> example - it is quite possible that the an IPv4 transfer policy is necessary</div>
<div class=""> to insure that blocks that are transferred are of a minimum size. While the </div>
<div class=""> ISP community _may_ be capable of dealing with a flood of /30’s suddenly</div>
<div class=""> appearing and seeking routing, it is quite unclear if there is any benefit in </div>
<div class=""> creating that potential condition, and there is certainly risk to the Internet if </div>
<div class=""> ISPs succumb to the customer pressure and route such in large quantity.</div>
<div class=""><br class="">
</div>
<div class=""> Can we start with a deliberate reasoned discussion on this one aspect of the </div>
<div class=""> IPv4 transfer policy, and if common ground is found, move on to any other</div>
<div class=""> perceived transfer policy requirements?</div>
<div class=""><br class="">
</div>
<div class="">Thanks!</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">ARIN</div>
<div class=""><br class="">
</div>
<div class=""> </div>
</body>
</html>