<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 16 Jul 2022, at 4:30 AM, Ronald F. Guilmette <<a href="mailto:rfg@tristatelogic.com" class="">rfg@tristatelogic.com</a>> wrote:</div>
<div class="">
<div class="">...<br class="">
Rather, I have elaborated a set of facts that, as far as I can tell, are<br class="">
quite explicitly indicative of -someone- having messed up. </div>
</div>
</blockquote>
<div><br class="">
</div>
Interestingly, I do agree with that statement (“-someone- having messed up”)</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">That may be the member in question, or it could be ARIN. </div>
</div>
</blockquote>
<div><br class="">
</div>
I shall present a third alternative shortly.</div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">And in fact, I have gone the other way by suggesting that it appears to<br class="">
me more likely than not that the "suspicious fact pattern" I have described<br class="">
may be attributed to a misstep on the part of ARIN.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Yes, I have taken note of your often repeated suggestion to that effect, and despite the lack of </div>
<div>any actual report, a review of the request in question was conducted. </div>
<div><br class="">
</div>
<div>The conclusion of the review is that the particular request was appropriated approved back in </div>
<div>2012 under the policy in effect at that time. </div>
<div><br class="">
</div>
<div class="">
<div class="">
<blockquote type="cite" class=""> There does seem to have been some deviance from written ARIN policy in this instance. </blockquote>
</div>
</div>
<br class="">
Yes, you’ve indicated that is your belief on this list several times in recent days. <br class="">
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">I have most certainly *not* asked John to provide *any* details about how<br class="">
his staff goes about reviewing member compliance with policy, nor would<br class="">
I have any reason to do so. NRPM Section 9 lays out quite clearly the<br class="">
various criteria that ARIN should (must?) use to evaluate whether any<br class="">
given member does or does not have "a real and substantial connection<br class="">
with the ARIN region”. </div>
</div>
</blockquote>
<div><br class="">
</div>
<div>NRPM section 9 was adopted __in 2016__ <<a href="https://www.arin.net/participate/policy/nrpm/changelog/#version-2016-2" class="">https://www.arin.net/participate/policy/nrpm/changelog/#version-2016-2</a>></div>
<div><br class="">
</div>
<div>Please do not tell me that you expected ARIN to utilize those yet-to-written criteria during consideration </div>
<div>of a number resource request made in 2012? Please tell me that your basis for your repeated allegations </div>
<div>on this list of ARIN failure to adhere to policy is based on more that a policy section that _did not exist_ </div>
<div>at the time of the request in question??</div>
<div class=""><br class="">
</div>
<blockquote type="cite" class="">
<div class="">
<div class=""> You must think very little of me if you think<br class="">
that I am unable to intuit how ARIN staff might go about the process of<br class="">
simply verifying a member's "substantial connection with the ARIN region".<br class="">
I am not sure why you would have such a low opinion of my capability in<br class="">
this regard, especially given all of the relevant facts that I have found<br class="">
and documented in relation to this specific case (SL-206). I guess you<br class="">
just think I'm a dunce.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
I shall decline to opine of much of the above, but note that “intuition” is not at all required to determine </div>
<div>how ARIN considered such a request back in 2012, as ARIN (after seeing a quantity of requests from </div>
<div>entities with only a loose association to the region) raised the matter with the community in March 2013 </div>
<div>by way of the ARIN 31 Public Policy Meeting / Policy Experience Report, pages 9 - 14, </div>
<div><<a href="https://www.arin.net/vault/participate/meetings/reports/ARIN_31/PDF/monday/nobile_policy.pdf" class="">https://www.arin.net/vault/participate/meetings/reports/ARIN_31/PDF/monday/nobile_policy.pdf</a>><br class="">
<br class="">
(This is what ARIN does when we see a circumstances where the implementation of existing policy </div>
<div>might not align with community expectations…) </div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">I have presented a set of facts which can all be independently verified,<br class="">
and which I assert do undeniably and beyond a reasonable doubt show that<br class="">
a clear deviance from ARIN policy exists. </div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Which policy (or to be more point - which policy that was actually in effect in 2012 when the request </div>
<div>was considered) do you believe was violated?</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">No one, not even you, have denied that this is exactly what I have done, and exactly what I have<br class="">
demonstrated. So we have an apparent policy violation. Now the only open questions are</div>
</div>
</blockquote>
<blockquote type="cite" class="">
<div class="">
<div class="">(a) Whose fault is it that this arose? and (b) What should be done about it?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
You suggested earlier “someone messed up” and I concurred. I’ll further suggest that the crux of the</div>
<div>mistake may come down to someone examining a 2012 request against number resource policy that </div>
<div>was adopted in 2016. </div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">What I have done is to raise the possibility that within ARIN, policy<br class="">
enforcement may perhaps have been de-emphasized, ...<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>This was not that case - not only did ARIN enforce the applicable policy against the request at the</div>
<div>time, but we went out of way to inform the community about the potential that current policy might </div>
<div>not be sufficiently precise so as to result in unexpected outcomes when entities with only a loose </div>
<div>association to the region apply for resources. </div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">In any event, even my raising of the question of ARIN priorities does not<br class="">
in any way demean either the skills or the professionalism of any member<br class="">
of the ARIN staff, let alone all of them. At most, we are simply and only<br class="">
discussing budget priorities and arguably well-founded considerations<br class="">
relating to the avoidance of costly legal entanglements, and whether such<br class="">
considerations should outweigh the value of additional transparency when<br class="">
it comes to the final resolutions of "fishyness" reports submitted to ARIN.</div>
</div>
</blockquote>
<br class="">
</div>
<div>ARIN does not shy away from performance of duties _ever_ due to potential litigation. </div>
<div>The community expects the community-developed number resource policy to be utilized</div>
<div>in management of the registry and this is done uniformly and without exception. </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>
<div><br class="">
</div>
<div><br class="">
</div>
<br class="">
</body>
</html>