<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Mar 14, 2016, at 2:08 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class="">So I have a couple of questions…<br class="">
<br class="">
In trying to parse the combination of the table and the text under “End Users / Assignments”,<br class="">
it’s completely unclear to me what happens going forward.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Owen - </div>
<div> </div>
<div>Thanks for posting these questions - it is a good reminder of how complicated </div>
<div>this can be for normal folks (as opposed to the myself and the staff who deal </div>
<div>with these matters each day.)</div>
<div>
<div class="">
<div class="">
<div class=""><br class="">
</div>
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">Currently, I have 2 ORG IDs as an artifact of ARIN accounting irregularities. (inability to treat LRSA and RSA as a single ORG)<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>It’s actually not accounting irregularities: each agreement represents a distinct </div>
<div>relationship with ARIN - many organizations find the ability to have multiple</div>
<div>relationships useful for various reasons (e.g. business units, different terms </div>
<div>from older agreements, etc.)</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">Some of the text seems to indicate that I have the option of no change from current billing practices.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
That is correct. If you are an end-user (or legacy holder billed as same), then </div>
<div>you do not experience any difference as a fee schedule change (unless you opt </div>
<div>to do so as discussed further below.)</div>
<div><br class="">
</div>
<div>You may confirm this by running the Fee estimator for the new schedule referenced in </div>
<div>the original announcement (available here - <a href="https://www.arin.net/fees/calculator.html" class="">
https://www.arin.net/fees/calculator.html</a>)</div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="">Some of the text seems to indicate that I’m going to fee-per-ORG rather than fee-per-resource.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
If you choose to do so, you will now be able to switch to a registration services plan </div>
<div>(the same fee schedule used by all ISPs, and including ARIN Membership)</div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">Some of the text seems to indicate that I can choose one or the other of these.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Correct - once the new fee schedule is in effect, you may indicate that you’d like</div>
<div>to switch to a registration services plan (if you prefer such), and your billing will</div>
<div>change accordingly.<br class="">
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">No mention is made of how any of this relates to LRSA with price increase limitations.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>You will be billed accordingly to each agreement you have with ARIN, as they have</div>
<div>different terms and fees. If you consolidate, you will be billed under the single RSA</div>
<div>that results.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">Does this mean I’m going to get double-billed?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
You will not.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">My non-LRSA ORG-ID is currently billed $100/year and contains one resource.<br class="">
My LRSA ORG-ID is currently billed $175/year and will hit $200/year in the next billing cycle (under the current scheme).<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
Correct. The forthcoming fee schedule is regarding the new registration services</div>
<div>fees for ISPs, whereby we shift the categories to allow more IPv6 resources in each</div>
<div>category, as well as opening them up to end-users who prefer this type of schedule.</div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">My LRSA ORG-ID has a contractual restriction of $25/year price increases.<br class="">
My non-LRSA ORG-ID is subject to whatever form of pillaging the board chooses to engage in.<br class="">
<br class="">
To further complicate the matter, my RSA resources are 3X-Small. My LRSA are 2X-Small.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
The various sizes only matters if you switch to registrations services plan </div>
<div>billing, and that may not make sense for those with relatively few IP address</div>
<div>blocks and ASNs</div>
<div>
<div class="">
<div class=""><br class="">
</div>
</div>
<blockquote type="cite" class="">
<div class="">
<div class="">So, under this new change, which outcome am I facing?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>The same as you are presently paying (but per the agreement you signed,</div>
<div>you should be aware that the LRSA fees may increase up to $25/year)</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">There are things about the new structure that I like:<br class="">
<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>1.<span class="Apple-tab-span" style="white-space:pre">
</span>Membership for end-users included in their price.<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>2.<span class="Apple-tab-span" style="white-space:pre">
</span>Fee per ORG rather than fee per resource.<br class="">
<span class="Apple-tab-span" style="white-space:pre"></span>3.<span class="Apple-tab-span" style="white-space:pre">
</span>Potentially a return to the promised slow-ramp on fees to LRSA users.<br class="">
<br class="">
But I’d love to hear not only which of the 5 billing possibilities above (and possibly more I haven’t thought of) ARIN will consider valid and which would be rejected and why. I’d also like to know which one ARIN will default to if I don’t specify.</div>
</div>
</blockquote>
<div><br class="">
</div>
As noted above, your fees do not change as a result of the new fee schedule,</div>
<div>they will be as you noted earlier (and repeated again below - </div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class=""></blockquote>
</div>
<blockquote type="cite" class="">
<div>
<blockquote type="cite" class="">My non-LRSA ORG-ID is currently billed $100/year and contains one resource.</blockquote>
</div>
<div>
<div>
<blockquote type="cite" class="">My LRSA ORG-ID is currently billed $175/year and will hit $200/year in the next billing cycle (under the current scheme).<br class="">
</blockquote>
</div>
</div>
</blockquote>
<div>
<div>
<div class=""><br class="">
</div>
</div>
</div>
<div>If you wished to, you could switch to a registration services plan, and you would be</div>
<div>at the 2X small for all resources combined at $500/year. This would also cover the</div>
<div>registration services for all ASN that you have and would include ARIN Membership. </div>
<div>Again, I don’t know if it makes sense given your total resource holdings, but it will now</div>
<div>be an option.</div>
<div><br class="">
</div>
<div>Thanks! (and do not hesitate to ask if you have any further questions.)</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
</body>
</html>