<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Bill –
<div class=""><br class="">
</div>
<div class="">From a great height or distance, your “bottom line” summary of a some form of status quo probably </div>
<div class="">appears accurate. </div>
<div class=""><br class="">
</div>
<div class="">(I am unfortunately much closer and see quite a bit a of detail lost in it; for example, we have been </div>
<div class="">enforcing different community-developed transfer policies that have changed over the years, and </div>
<div class="">that has very real-world implications for those who wish monetize their excess number resources – </div>
<div class="">similarly, we revoke legacy resources from parties who have hijacking or otherwise surreptitiously</div>
<div class="">obtained them so that the proper party can recover their resources, etc. These activities routinely</div>
<div class="">take place today and are based on application of policies that did not exist 25 years ago to all of</div>
<div class="">the number resources in the registry - legacy number resources included.)</div>
<div class=""><br class="">
</div>
<div class="">We have had parties litigate to prevent application of community policy to their legacy number </div>
<div class="">resources and they have never prevailed to date – ARIN continues to operate the registry </div>
<div class="">according to the community-developed policies in the region. Indeed, this record of success is</div>
<div class="">likely just as much the result of the community not creating burdensome policy obligations on </div>
<div class="">resource holders (such an approach is particularly prudent when it comes to legacy resource </div>
<div class="">holders since many have not updated their contact information over the years and therefore </div>
<div class="">the ability to reliably inform them of any new obligations is a rather reasonable concern.)</div>
<div class=""><br class="">
</div>
<div class="">The ARIN policy development process is open to all and transparent in operation, and ARIN </div>
<div class="">operates the registry in accordance to the developed policies. I am not aware of any obligations </div>
<div class="">of ARIN that prevent us from doing so or might even remotely suggest that any party be immune </div>
<div class="">from such policies, but can say without any doubt that the US government expects our developed </div>
<div class="">policies to define how the Internet numbers "are managed and allocated within the North American </div>
<div class="">region.”</div>
<div class=""><br class="">
</div>
<div class="">To the extent that the community continues to be reasonable in its obligations on number resource</div>
<div class="">holders in the region, we may indeed see a lack of contentious outcomes (and continuity of what </div>
<div class="">you may perceive as an apparent “status quo”) – but that only means that ARIN will continue enforce </div>
<div class="">the policy – including as it evolves – for all number resources in the registry - just we do today. Folks </div>
<div class="">who have any concerns about the potential of policy developed by this community affecting their IP</div>
<div class="">number resources are advised to participate in the open policy development process (you can find </div>
<div class="">more details here - <a href="https://www.arin.net/participate/policy/" class="">https://www.arin.net/participate/policy/</a>) </div>
<div class=""><br class="">
</div>
<div class="">Thanks!</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On 16 Sep 2022, at 4:56 PM, William Herrin <<a href="mailto:bill@herrin.us" class="">bill@herrin.us</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">On Fri, Sep 16, 2022 at 12:47 PM John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:<br class="">
<blockquote type="cite" class="">Again, to make sure there is 100% clarity: we have consistently ended up settling with orders<br class="">
that recognize ARIN’s ability to operate the registry according to the community-developed<br class="">
policy, including the application of that policy to legacy address blocks. ARIN simply doesn’t<br class="">
settle absent those terms, as it is fundamental principle of our inception that this community<br class="">
can set the policies used to administer the registry for this region.<br class="">
</blockquote>
<br class="">
Bottom line:<br class="">
<br class="">
* There is a status quo for ARIN's relationship with the legacy registrants.<br class="">
<br class="">
* It hasn't materially changed since ARIN's inception a quarter century ago.<br class="">
<br class="">
* ARIN has indicated no intention of changing it.<br class="">
<br class="">
* Were ARIN's behavior to materially drift from the status quo, they<br class="">
would be sued with an uncertain outcome.<br class="">
<br class="">
You want to dispute that last item, we can go another ten rounds on<br class="">
it, but what's the point? Nothing has changed since the last time we<br class="">
debated on the PPML list: In 25 years no one has successfully induced<br class="">
ARIN to act contrary to the status quo and in 25 years no one has<br class="">
successfully challenged ARIN on the status quo.<br class="">
<br class="">
<br class="">
Summarizing the status quo:<br class="">
<br class="">
* ARIN continues to report the legacy registrations.<br class="">
<br class="">
* Legacy registrants do not pay ARIN for anything associated with the<br class="">
legacy registrations.<br class="">
<br class="">
* Legacy registrants change POCs and RDNS servers associated with<br class="">
legacy registrations at their pleasure.<br class="">
<br class="">
* ARIN will not record a transfer of a legacy resource to another<br class="">
registrant absent ARIN's current approved contracts.<br class="">
<br class="">
* ARIN provides "new" services (developed after ARIN's inception) to<br class="">
legacy registrants only where those services directly replace<br class="">
functionality that has been retired. For example, the Web UI replaces<br class="">
the old email forms so it's provided to legacy registrants but RPKI is<br class="">
entirely new so it is not.<br class="">
<br class="">
Regards,<br class="">
Bill Herrin<br class="">
<br class="">
<br class="">
-- <br class="">
For hire. <a href="https://bill.herrin.us/resume/" class="">https://bill.herrin.us/resume/</a><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>