<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="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 5 Aug 2022, at 2:39 AM, Ronald F. Guilmette <<a href="mailto:rfg@tristatelogic.com" class="">rfg@tristatelogic.com</a>> wrote:</div>
<div class="">
<div class=""><br class="">
Although I am greatly appreciative of Ted's comments, which appear to be<br class="">
supportive of the primary point that I most recently attempted to make here,<br class="">
I am obliged to point out that the example of the 199.248.255.0/24 block,<br class="">
and ARIN's seeming reluctance to reclaim it, *does not* actually support<br class="">
the point that I have attempted to make here most recently. for one very<br class="">
glaringly obvious reason:<br class="">
<br class="">
RegDate: 1994-10-11<br class="">
<br class="">
199.248.255.0/24 is unambiguously a legacy block. Thus, ARIN may or may<br class="">
not have in hand either a signed RSA or a signed LRSA that is relevant and<br class="">
applicable to this block. For the sake of argument, let's assume that it<br class="">
doesn't.<br class="">
<br class="">
Other people may reasonably disagree with me, but I personally am at least<br class="">
somewhat sympathetic to the various legal assertions and bold claims that<br class="">
have been made by various IPv4 legacy registrants, over time. I am also<br class="">
at least somewhat sympathetic to ARIN's understandable reluctance, if any,<br class="">
to sally forth and do battle in the courts over such legacy-related claims.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Alas, there’s very little evidence that legacy resource holders (being parties that lack any </div>
<div>written agreement with ARIN) have any magical ability or right that would preclude ARIN </div>
<div>operating its registry exactly as directed by community policy (including entries held by</div>
<div>legacy resource holders), but I recognize there are some who may feel otherwise.</div>
<div><br class="">
</div>
<div>ARIN actually have zero reluctance when it comes to defending the community’s right to </div>
<div>establish apply policies applicable to the entire registry, and we do quite vigorously defend </div>
<div>the same in court without hesitation. </div>
<div><br class="">
</div>
<div>(Any reticence you see regarding the establishment of new policy requirements applicable to </div>
<div>legacy resource holders is simply driven out of the desire to be respectful to all parties with </div>
<div>resources in the registry and desire that any such policy changes be based out of a clearly </div>
<div>articulated policy need of this community. We have done many such changes in the past that </div>
<div>are applicable to the entire registry including legacy resource holders – this includes addition </div>
<div>of the abuse contact, number resource resource review section, POC validation, etc.) </div>
</div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">...<br class="">
<br class="">
In fairness, I must apologize to John Curran, to the entire ARIN staff, and<br class="">
to everyone here if my questions relating to this topic of dead companies may<br class="">
at times have seemed somewhat accusatory in tone. Upon reflection, I must<br class="">
now say that any apparent inaction, on the part of ARIN staff, with respect<br class="">
to such deceased entities, although somewhat frustrating to me personally,<br class="">
is likely entirely understandable. It would be entirely unfair to lay any<br class="">
blame for what would appear to be a lack of action relating to such cases <br class="">
at the feet of the ARIN staff. I mean after all, they are but the servants<br class="">
of the ARIN community and the ARIN membership, and they cannot fairly be<br class="">
blamed if the community and the membership have given them absolutely zero<br class="">
in the way of clear guidance on what, if anything, they should do about<br class="">
dead resource-holding organizations.<br class="">
<br class="">
Rather, if there is any blame to be laid for inaction when it comes to dead<br class="">
resource-holding organizations, then I think that it can only fairly be<br class="">
assigned to the ARIN community and the ARIN membership. The community and<br class="">
the membership should have addressed this issue long ago, and having failed<br class="">
to do so, the community and the membership should do so now. Better late<br class="">
than never.<br class="">
<br class="">
It is altogether clear to me what must, at the very least be done. At the<br class="">
very least, the community and/or the membership should give clear guidance,<br class="">
immediately, to John Curran and the ARIN staff regarding what they should<br class="">
do when they become aware, VIA ANY MEANS OR CHANNEL, of the dissolution of<br class="">
any resource-holding entity that has ever signed an RSA agreement with ARIN.</div>
</div>
</blockquote>
<blockquote type="cite" class="">
<div class="">
<div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">...</span></font><br class="">
So, it is clear, to me at least, what must, at a minimum, be done. The<br class="">
question remains of what process should be used to achieve it. Should this<br class="">
be a "consultation" or should it instead be a formal policy proposal?</div>
</div>
</blockquote>
<br class="">
</div>
<div>I would suggest a formal policy proposal; you can find additional information on </div>
<div>submitting such here – <a href="https://www.arin.net/participate/policy/pdp/appendix_b/" class="">https://www.arin.net/participate/policy/pdp/appendix_b/</a></div>
<div><br class="">
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br class="">
</div>
<div>
<div>John Curran</div>
<div>President and CEO</div>
<div>American Registry for Internet Numbers</div>
<div><br class="">
</div>
</div>
<br class="">
</body>
</html>