<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 1 Nov 2022, at 3:03 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:</div>
<div class="">
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<br class="">
<blockquote type="cite" class="">
<div class="">On Nov 1, 2022, at 05:07, John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div>
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">The “double-charging” that you allege was imposed by the ARIN Board of Trustees was actually self-imposed by you; i.e., you chose to maintain separate billing relationships with ARIN in order to continue benefiting from annual maintenance fee
cap applicable to services for legacy IPv4 number resources. This fee cap isn’t applicable to IPv6 number resources nor the registration services fee paid for an organization that consolidates resources under a single registration services plan including
non-legacy resources. </div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
We will continue to disagree about this, sir.</div>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<br class="">
</div>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
When I made the mistake of signing the LRSA, it was fee per ORG and I maintained a single ORG that had both LRSA and RSA resources and a single billing relationship.</div>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
<br class="">
</div>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">
When the board pulled the rug out from under that relationship, despite the material adverse change in the relationship, I was not allowed to terminate the LRSA and keep my resources without incurring significant financial penalties and loss of protections
that were material to my willingness to sign the LRSA in the first place. Further as a result of that action by the board, ARIN (whether by board decision or by staff choices surrounding the implementation of that decision) chose to bifurcate my organization
into two separate organizations for ARIN’s convenience in handling the new billing structure.</div>
</div>
</blockquote>
<div><br class="">
</div>
Owen - </div>
<div><br class="">
</div>
<div>That was your choice: you could have consolidated into a single billing relationship if you wished or opted (as you did) to maintain distinct billing relationships in which each relationship was billed for services for a distinct and non-overlapping set
of resources. </div>
<div><br class="">
</div>
<div>“Double charging” implies being charged twice for the same services and that was never the situation in any case. </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="">
</div>
</div>
<div><br class="">
</div>
</body>
</html>