<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="">
Mike -
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span></div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>There are very clean and routine everyday 8.2 transfers that occur… company renaming or complete acquisition where the supporting documentation is routine and current - definitely brings
down the average quite a bit.</div>
<div class=""><br class="">
</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 class=""><br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 20 Apr 2021, at 12:24 PM, Mike Burns <<a href="mailto:mike@iptrading.com" class="">mike@iptrading.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; 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;">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Hi John,<o:p class=""></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Side topic.<o:p class=""></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
How can the cost of 8.2 transfers be so low compared to 8.3 and 8.4 transfers?<o:p class=""></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
This makes no sense to me as 8.2 transfers take longer and seem to involve a lot more work.<o:p class=""></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Regards,<br class="">
Mike<o:p class=""></o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div class="">
<div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<b class="">From:</b><span class="Apple-converted-space"> </span>ARIN-consult <<a href="mailto:arin-consult-bounces@arin.net" style="color: blue; text-decoration: underline;" class="">arin-consult-bounces@arin.net</a>><span class="Apple-converted-space"> </span><b class="">On
Behalf Of<span class="Apple-converted-space"> </span></b>John Curran<br class="">
<b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, April 20, 2021 11:54 AM<br class="">
<b class="">To:</b><span class="Apple-converted-space"> </span>Dale W. Carder <<a href="mailto:dwcarder@es.net" style="color: blue; text-decoration: underline;" class="">dwcarder@es.net</a>><br class="">
<b class="">Cc:</b><span class="Apple-converted-space"> </span><<a href="mailto:arin-consult@arin.net" style="color: blue; text-decoration: underline;" class="">arin-consult@arin.net</a>> <<a href="mailto:arin-consult@arin.net" style="color: blue; text-decoration: underline;" class="">arin-consult@arin.net</a>><br class="">
<b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [ARIN-consult] Consultation on ARIN Fees<o:p class=""></o:p></div>
</div>
</div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
On 20 Apr 2021, at 11:07 AM, Dale W. Carder <<a href="mailto:dwcarder@es.net" style="color: blue; text-decoration: underline;" class="">dwcarder@es.net</a>> wrote:<o:p class=""></o:p></div>
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Thus spake ARIN (<a href="mailto:info@arin.net" style="color: blue; text-decoration: underline;" class="">info@arin.net</a>) on Fri, Apr 09, 2021 at 04:38:21PM -0400:<br class="">
<br class="">
<o:p class=""></o:p></div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
ARIN’s Fee Schedule has always been based on the principle of equitable cost recovery across our community through a stable and consistent fee schedule. In general, this means that ARIN has avoided making routine changes to the Fee Schedule (for example, making
annual readjustments for changing costs) and instead has only made changes when deemed necessary.<o:p class=""></o:p></div>
</blockquote>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<br class="">
I'd challenge the board to consider how the fee schedule could be made<br class="">
sustainable year over year. Certainly with other non-profits I've<br class="">
worked with, a set of published fixed rates doesn't reflect the costs<span class="Apple-converted-space"> </span><br class="">
of staff & benefits that increase yearly. Maybe we can get to the point<br class="">
where there are not stair steps but a socially expected 'n'% increase<span class="Apple-converted-space"> </span><br class="">
yearly.<o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Dale - <o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
It is certainly possible for ARIN to take that approach, but we’ve previously heard input that says “Keep my fees the same each year so that I don’t need to get approval to renew any higher number”… We’d need to have quite a bit of community feedback before
going to any annually adjusting model compared to our present “review every four or five years” approach.<o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
We are consulting with the community regarding changes to the ARIN Fee Schedule that are intended for implementation in January of 2022. These changes are:<br class="">
<br class="">
* Transitioning End Users from annual per-resource maintenance fees to the RSP (Registration Services Plan) Fee Schedule<o:p class=""></o:p></div>
</blockquote>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<br class="">
I have always found the end-user vs lir distinction confusing, but I get<br class="">
why it exists.<o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Indeed - it is a frequently cited concern. <o:p class=""></o:p></div>
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
</div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Are there also policy changes happening (or have happened) in the NPRM<br class="">
that coincide with the change here to treat them the same with respect<br class="">
to services used? It would appear that this could result in a sizable<br class="">
bill increase for orgs used to paying per-resource? Or in practice,<br class="">
does it come out to a wash in which case the simplification is worth it?<o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
The number resource policy manual is fairly agnostic on fees and services, and our traditional approach to issuance has end-user organizations receiving significantly smaller blocks than service providers; as such, it doesn’t appear that any policy changes
are necessitating by the fee change. (As I noted in a message to arin-consult on 14 April 2021, the community may explore potential policies that restrict subassignment of address blocks of “end-users”, but that’s entirely up to the community as to the
merit/issues in doing so...) <o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
* Transitioning Legacy resource holders from annual per-resource maintenance fees to the RSP Fee Schedule while maintaining the annual cap of total maintenance fees (which will increase $25 per year)<o:p class=""></o:p></div>
</blockquote>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<br class="">
This seems totally reasonable.<br class="">
<br class="">
<br class="">
<o:p class=""></o:p></div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
* Providing a temporary IPv6 fee waiver for organizations in the 3X-Small category that desire a larger address block<o:p class=""></o:p></div>
</blockquote>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<br class="">
This seems like a gimmick of penetration pricing and a bit disingenuous in the<span class="Apple-converted-space"> </span><br class="">
spirit of a membership organization. <o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Alas, it is not clear that a permanent fee change is viable over the long-term for the organization, and yet there was support in providing some option for very small organizations to obtain larger IPv6 blocks - that left us with the waiver as the best approach
for the time being. <o:p class=""></o:p></div>
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
</div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
* Implementing a $100 fee for OrgCreate and OrgRecovery transactions<o:p class=""></o:p></div>
</blockquote>
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<br class="">
I guess I'd be slightly careful here that we don't unnecessarily create<br class="">
disincentives for correct registrations due to there being a fee for this.<br class="">
I would have thought this processing fee to be adequately covered in the<span class="Apple-converted-space"> </span><br class="">
service category fee (bigger categories probably do more of them,<br class="">
smaller ones less) or bundled into the transfer processing fee (below)<o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><br class="">
<br class="">
</span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">It’s important to encourage accurate recordkeeping and that would suggest that no fee is preferred, but we also should have some consideration for vetting services conducted and the contract being entered. It was felt that $100 struck
a reasonable balance between these two goals. </span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
* Increasing the transfer processing fee to $500<o:p class=""></o:p></div>
</blockquote>
</div>
</div>
</blockquote>
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</blockquote>
</div>
</div>
<div class="">
<blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite">
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
I would think that the fee here should be the full cost recovery to process the<span class="Apple-converted-space"> </span><br class="">
transaction. Is that the case here?<o:p class=""></o:p></div>
</div>
</div>
</blockquote>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">We’ve got some real challenges with equitable fees for transfers… It’s important to encourage accurate recordkeeping, and that means that a fixed fee is preferred despite the highly variable costs. In addition, there are many teams
involved, including registration, finance, and legal. We realize that transfers were having a substantial toll on the organization, so we did a review of the full set of 2019 transfers and the costs incurred (see below) which resulted in a clear understanding
that the present $300 fee was insufficient – <o:p class=""></o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><span id="cid:image001.png@01D735DF.6408B3B0"><image001.png></span></span><span style="" class=""><o:p class=""></o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">Great feedback, and I hope the above information is helpful in understanding some of the factors that led to the proposed change.<o:p class=""></o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">Thanks again! <o:p class=""></o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">/John<o:p class=""></o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<div class="">
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">John Curran</span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">President and CEO</span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class="">American Registry for Internet Numbers</span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><br class="">
<br class="">
</span><o:p class=""></o:p></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><br class="">
<br class="">
</span><o:p class=""></o:p></div>
</div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
<div class="">
<div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="" class=""><o:p class=""> </o:p></span></div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>