[members-discuss] New charging model
Lu Heng h.lu at outsideheaven.com
Tue Jul 10 12:10:45 CEST 2012
Hi On Tue, Jul 10, 2012 at 12:06 PM, Erik Bais <erik at bais.name> wrote: > Hi Lu, > >> Just a quick common, these 0.0XXX% of member represent of 99.XX% resource usage,correct me if I am wrong. > > I'm not sure what the actual resource usage is by them, but will the number of v4 still matter post v4 depletion and everyone needs to go to v6 ? > > Would they also use actual RIPE NCC resources (personnel) at the same rate ? That is a much more interesting question imho, FTE usage will be a much bigger factor to count towards. > The changes are, that the smaller LIR's (due to in-experience) take much longer to obtain additional assignments / allocations than larger (seasoned LIR's). > I know a couple LIR's (probably medium ranked currently) which received a /19 or /18 between 2002 and 2005 and are still using that same prefix and haven't been back to the hostmasters since. > > Resource usages (in IP addresses) doesn't say much imho as it doesn't give a real indication on actual FTE usage in the RIPE office or the services used. If only the Ripe service time usage is the matter, why not we charge LIR by flat hourly rate? The reason we are not I think is because internet is a community, billiionairs who already made a lot money in the business shouldn't ask more from new comers just because they ask too many questions. Every body are once a newbie. So we should lower the barriers of the community in order to have more people to join. > > Erik Bais > > > -- This transmission is intended solely for the addressee(s) shown above. It may contain information that is privileged, confidential or otherwise protected from disclosure. Any review, dissemination or use of this transmission or its contents by persons other than the intended addressee(s) is strictly prohibited. If you have received this transmission in error, please notify this office immediately and e-mail the original at the sender's address above by replying to this message and including the text of the transmission received.