<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="">
On 12 Oct 2020, at 3:55 PM, William Herrin <<a href="mailto:bill@herrin.us" class="">bill@herrin.us</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="">
<div class="">
<div class="">That having been said, you should be aware that there's some political<br class="">
spin going on here. Let me offer an outside perspective.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<chuckle> No political spin, but rather simply stating how we handle legacy resources at ARIN. It is true that I omitted legacy resources that aren’t under contract, but welcome your additional perspective. </div>
<div><br class="">
</div>
<div>(Note - I omitted mentioning legacy resources not under contract because they effectively must comply with ARIN’s policies and terms to transfer, and hence their status independent of a transfer wasn’t necessarily germane...) </div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">ARIN's treatment of legacy resources boils down to: hands off. No<br class="">
money changes hands. ARIN does not attempt to forcibly reclaim legacy<br class="">
resources. ARIN acknowledges changes in contact information and DNS<br class="">
records. That's about it. The behavior has not been contractually<br class="">
normalized but it has been consistent for near a quarter century.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>While I would state the above differently, it is essential correct. </div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">For transfers, the rule is that ARIN registrants _receive_ number<br class="">
resources under the standard RSA contract which applies the policies<br class="">
in the NRPM. Neither document makes much distinction between legacy<br class="">
and non-legacy resources and together they provide no mechanism by<br class="">
which the new registrant can have an address block treated in the same<br class="">
manner ARIN treats legacy number resources.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Also correct (and most appropriate, since it is something that we’ve provided since inception to those who held number resources _at that time_.) <br class="">
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">Where a recipient has sufficient legal standing to make trouble for<br class="">
ARIN, the rule is broken. For example, government entities in the U.S.<br class="">
are allowed to negotiate custom contracts with ARIN removing terms<br class="">
they find objectionable. </div>
</div>
</blockquote>
<div><br class="">
</div>
Incorrect - While there are some terms that we will change for governmental entities (e.g. jurisdiction/venue), it is restricted to those necessary due to law or statute - </div>
<div><br class="">
</div>
<div><i class="">"ARIN accommodates the unique circumstance of federal, state, or provincial government entities, and has a practice of modifying RSAs for such requirements. In order for any such modifications to be considered, governmental entities must provide
statutory or regulatory references to explain and demonstrate the necessity for a modification in order to meet legal requirements and allow the governmental entity to execute the RSA."</i></div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">Another example: in the Microsoft/Nortel<br class="">
matter ARIN negotiated an alternate contract with Microsoft rather<br class="">
than allow the bankruptcy court to proceed to rule on whether ARIN<br class="">
could be compelled to transfer a legacy registration without one.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div class="">The above is also incorrect - ARIN had no concern about a ruling, but such was unnecessary since the parties agreed to condition the sale on compliance with ARIN’s policies and Microsoft’s entry into an RSA with ARIN.</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=""><br class="">
</div>
<div class=""><br class="">
</div>
<br class="">
<br class="">
</div>
</body>
</html>