From arin at tyleromeara.com Thu May 2 20:08:34 2024 From: arin at tyleromeara.com (Tyler O'Meara) Date: Thu, 02 May 2024 19:08:34 -0500 Subject: [ARIN-consult] [General-members] ARIN Customer Count and Average Revenue Trend (was: Re: Consultation on Approaches for Adjusting the ARIN Registration Services Plan Fee Schedule) In-Reply-To: <8E3A09A2-9B11-45E9-A130-D890BE84E9B1@arin.net> References: <9A388656-A539-47AE-BF2B-D57AA3D3952C@arin.net> <5B9E1B00-B7A7-47FB-96B6-DCA11B046BBA@delong.com> <8E3A09A2-9B11-45E9-A130-D890BE84E9B1@arin.net> Message-ID: Thanks for the info John. I'm inclined to agree with Owen; I think it's better to continue with Option A. I have this opinion for 2 reasons: 1) The increased friction involved in raising fees encourages ARIN to continue to search for ways to be more efficient. 2) When fees need to be increased, I think it's valuable for the community to revisit how we dole out fees rather than just continuing with the status quo. For example, maybe the next time we need to increase fees, rather than just increasing the prices on the fee schedule it would be better to decrease the amount of IPv4 addresses required for each level, to serve as encouragement to migrate to IPv6. (Note: this is just an example, not an actual suggestion). Tyler O'Meara AS53727 On Fri, 2024-04-12 at 15:42 +0000, John Curran wrote: > > > > > > On Apr 3, 2024, at 5:58?PM, Owen DeLong via General-members > > wrote: > > > > > > > > ... > > I don?t know what the average ARIN price increase per year has been over the > > last 20+ years, and it might be useful if ARIN were able to produce some > > statistics on the matter. > > > > I realize this is a somewhat complex question because ARIN has repeatedly > > rejiggered how fees are computed as well as the price per unit (including > > changes to what constitutes a ?unit? for pricing). > > > > Nonetheless, since ARIN knows every member?s billing history, it ought to be > > possible for ARIN to do some level of historic analysis of the average price > > per / paid by all registrants and then compute the average price > > increase per year from that. > > Owen ?? > > > I did not forget about your request for additional information ? but rather, > > as you note, it is a somewhat complicated question that took a bit of effort > > to extract properly. > > > > We were able to do this for 2002 through 2022 (the fee restructure of 2023 > > is a tad more complex and still being looked at?) ? > > > > So, attached is the ARIN customer count (i.e. all paying customers, > > including RSA/LRSA and AS holders) from 2002 to 2022, and the average > > revenue per customer in that period. > > > > I will also note that the services provided to customers over that period > > have increased substantially (although that?s not something that?s really > > reducible to a chartable data series, and hence not reflected below.)? > > > I hope you find this information helpful!? > /John > > > > John Curran > President and CEO > American Registry for Internet Numbers > > p.s. ?Owen posted the query to general-members, but I am following up to both > general-members and arin-consult as the information may be germane to the > current open consolation regarding approaches for adjustment of fees. ? Please > continue the discussion just on the arin-consult mailing list given the > existing open consultation taking place there - Thanks! /John > > > > ARIN Customer Count and Average Revenue .png > > From bill at herrin.us Thu May 2 23:50:51 2024 From: bill at herrin.us (William Herrin) Date: Thu, 2 May 2024 20:50:51 -0700 Subject: [ARIN-consult] [General-members] ARIN Customer Count and Average Revenue Trend (was: Re: Consultation on Approaches for Adjusting the ARIN Registration Services Plan Fee Schedule) In-Reply-To: References: <9A388656-A539-47AE-BF2B-D57AA3D3952C@arin.net> <5B9E1B00-B7A7-47FB-96B6-DCA11B046BBA@delong.com> <8E3A09A2-9B11-45E9-A130-D890BE84E9B1@arin.net> Message-ID: On Thu, May 2, 2024 at 5:08?PM Tyler O'Meara via ARIN-consult wrote: > 2) When fees need to be increased, I think it's valuable for the community to > revisit how we dole out fees rather than just continuing with the status quo. > For example, maybe the next time we need to increase fees, rather than just > increasing the prices on the fee schedule it would be better to decrease the > amount of IPv4 addresses required for each level, to serve as encouragement to > migrate to IPv6. (Note: this is just an example, not an actual suggestion). Hi Tyler, Historically, the apportionment of fees has been ruled an ARIN business practice, out of bounds for policy discussion. I think, and it sounds like you agree, that has been a poor decision. Among other consequences, it applied a drag on IPv6 deployment for over a decade when the price mostly exceeded the value. A combination of fee reductions and IPv6's slowly increasing value has mostly brought that particular issue to heel, but it could and should have happened years ago. For obvious reasons, the particular fees charged cannot be a policy level decision. However, the -apportionment- of fees among ARIN's services -- which ones should support the brunt of ARIN's cost, what should be bundled versus carrying a separate charge, and things like that the community could reasonably choose for itself. Regards, Bill Herrin -- William Herrin bill at herrin.us https://bill.herrin.us/ From info at arin.net Mon May 13 10:24:54 2024 From: info at arin.net (ARIN) Date: Mon, 13 May 2024 10:24:54 -0400 Subject: [ARIN-consult] NOW CLOSED - Consultation on Approaches for Adjusting the ARIN Registration Plan Fee Schedule Message-ID: <76DD024F-1D0D-40F7-A5D4-5F35EB0A261A@arin.net> >From 3 April to 3 May 2024, ARIN held a consultation seeking feedback from the community regarding potential methods to adjust ARIN?s Registration Services Plan Fee Schedule to maintain a balanced alignment between operating costs and revenue, ensuring equitable cost recovery across its diverse community. Given the ongoing nature of these expenses, and in pursuit of a sustainable fiscal strategy, the ARIN Board of Trustees asked for community input on two distinct approaches for future fee adjustments: - Continue with the current practice of periodically reviewing the alignment between annual revenue and operating costs, and institute any necessary adjustments following community consultation. - Introduce a structured approach to fee adjustments, allowing for an annual increase of no more than 5%, subject to approval by the Board of Trustees. This strategy aims to offer a predictable and manageable escalation in fees, aligning more closely with the budget planning processes of many organizations within our community. ARIN would like to thank the community members who provided feedback and asked questions over the consultation period. There was support for moving to the annual structured approach for fee adjustments, but no overall consensus emerged in the discussion about which approach was best. During the discussion there were several additional points raised which will be considered by the Board of Trustees in determining the path forward, including:? - Defining the timing for the announcement of any annual increase to fees to aid in organizations with their budgeting. - Identifying if an index should be utilized in determining the increase in any given year. ARIN thanks those who provided valuable feedback on this consultation. We rely on this input from our members and community to help steer the organization as we continue our mission supporting the operation and growth of the Internet. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) ------- ACSP Consultation 2024.2: Consultation on Approaches for Adjusting the ARIN Registration Services Plan Fee Schedule: https://www.arin.net/participate/community/acsp/consultations/2024/2024-2/