<div dir="ltr"><div>Hi.</div><div><br></div>Charging for *any* resource, especially ASNs, is just plain stupid. It's not like it costs anything to take care of the resources.<div><br></div><div>Personally I'm in favour of option A, perhaps lower it by 100-200€/yr for first 1-2 years for startups and such.</div><div><br></div><div>Regards,</div><div>Sebastian</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 17, 2019 at 7:55 PM Nico Schottelius <<a href="mailto:info@ungleich.ch" target="_blank">info@ungleich.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
Hello,<br>
<br>
I think the point that is most "wrong" in this charging scheme is that<br>
IPv6 resources are treated the same as IPv4. This is a) not in relation<br>
to scarcity and b) does not give any motivation for IPv6 deployements.<br>
<br>
I suggest that either any IPv6 resource is for free or that "up to" some<br>
amount of IPv6 resources it stays free and even after that the increase<br>
should be lower than IPv4.<br>
<br>
That said, I agree with Alex that if the objective is to support smaller<br>
ISPs, it should be charged on volume, not number.<br>
<br>
My counter proposal to B would be<br>
<br>
--------------------------------------------------------------------------------<br>
- Same base fee as option B<br>
- All IPv6 resources are free<br>
- Charge x per 256 IPv4 addresses<br>
- Charge y per ASN, after the 5th ASN<br>
--------------------------------------------------------------------------------<br>
<br>
The key x would have to be determined by RIPE and could be derived from<br>
the current allocations such that the new membership fee sum = the<br>
current sum.<br>
<br>
For the key y I don't have a good estimate at the moment, but 50 Euro/y<br>
does not sound unreasonable. Also most LIRs will never exceed the<br>
included number of ASNs.<br>
<br>
Best,<br>
<br>
Nico<br>
<br>
<br>
Alexandru Doszlop <<a href="mailto:alexandru.doszlop@netprotect.ro" target="_blank">alexandru.doszlop@netprotect.ro</a>> writes:<br>
<br>
> Hello,<br>
><br>
> I just read the email regarding the charging scheme for 2020 option B.<br>
> Are you kidding me?<br>
> Are you really naming it "volume based billing"?<br>
><br>
> Let's say one isp has only one /12 ipv4 PA. It will pay 1150 euro + 50 euro.<br>
> The other LIR that wants to help small companies and has 50 /24 assignments, will pay 1150 + 50*50=3650 euro.<br>
> All new lirs that receive smaller than /22 assignments will pay more than than the big isp.<br>
> Where is the volume here?<br>
><br>
> Unbelievable...<br>
><br>
> Regards,<br>
> Alex<br>
><br>
> ---------- Forwarded message ----------<br>
> From: Gwen van Berne <<a href="mailto:gvanberne@ripe.net" target="_blank">gvanberne@ripe.net</a>><br>
> Date: Apr 17, 2019 18:08<br>
> Subject: [ncc-announce] [GM] RIPE NCC Charging Scheme 2020 - Two Options to Vote On<br>
> To: <a href="mailto:ncc-announce@ripe.net" target="_blank">ncc-announce@ripe.net</a><br>
> Cc:<br>
><br>
> Dear colleagues,<br>
><br>
> Members will vote on the RIPE NCC Charging Scheme 2020 at the General<br>
> Meeting from 22-24 May. In response to requests from members, the<br>
> Executive Board is proposing two charging scheme options that the<br>
> members can choose from at the GM.<br>
><br>
> An overview of the two options is also available that explains the two<br>
> models in more detail. The overview and the two charging schemes are<br>
> available at:<br>
> <a href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/supporting-documents" rel="noreferrer" target="_blank">https://www.ripe.net/participate/meetings/gm/meetings/may-2019/supporting-documents</a><br>
><br>
> In short, the options that members will choose between are:<br>
><br>
> Option A: The RIPE NCC will maintain the existing charging scheme,<br>
> according to which members pay an annual fee of EUR 1,400 plus an extra<br>
> EUR 50 per independent number resource assignment.<br>
><br>
> Option B: The RIPE NCC will switch to a new volume-based, per<br>
> registration charging scheme. This would involve lowering the annual fee<br>
> to EUR 1,150 whilst broadening the applicability of the separate EUR 50<br>
> charge to all number registrations held by the member. See the full list<br>
> of registrations that would be charged in the document.<br>
><br>
> The existing sign-up fee of EUR 2,000 will apply to both options.<br>
><br>
> We encourage members to discuss the options on the Member Discuss<br>
> mailing list at <<a href="mailto:members-discuss@ripe.net" target="_blank">members-discuss@ripe.net</a>>. The Executive Board and the<br>
> RIPE NCC Management will follow discussions closely ahead of the GM.<br>
><br>
> If you have not yet registered for the GM, we strongly encourage you to<br>
> do so and make sure you have your say on which of two distinct charging<br>
> scheme options should be adopted in May. Full participation and voting<br>
> options are available for all members. You can register now via the LIR<br>
> Portal at:<br>
> <a href="https://www.ripe.net/s/gm-registration-may-2019" rel="noreferrer" target="_blank">https://www.ripe.net/s/gm-registration-may-2019</a><br>
><br>
> All details on the GM, including the draft agenda, are available from:<br>
> <a href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/" rel="noreferrer" target="_blank">https://www.ripe.net/participate/meetings/gm/meetings/may-2019/</a><br>
><br>
> Kind regards,<br>
><br>
> Gwen van Berne<br>
> Chief Financial Officer<br>
> RIPE NCC<br>
<br>
<br>
--<br>
Your Swiss, Open Source and IPv6 Virtual Machine. Now on <a href="http://www.datacenterlight.ch" rel="noreferrer" target="_blank">www.datacenterlight.ch</a>.<br>
<br>
_______________________________________________<br>
members-discuss mailing list<br>
<a href="mailto:members-discuss@ripe.net" target="_blank">members-discuss@ripe.net</a><br>
<a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank">https://mailman.ripe.net/</a><br>
Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/malek%40malek.li" rel="noreferrer" target="_blank">https://lists.ripe.net/mailman/options/members-discuss/malek%40malek.li</a><br>
</blockquote></div>