<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello all,</p>
<p><br>
</p>
<p>I just checked Alexis's spreadsheet.</p>
<p>If I'm sorting it by IPv4 block numbers I'm the 5th biggest with
233 blocks. (81408 IPs) !!!<br>
</p>
<p>With Option B I will pay at least 13000 euro.</p>
<p>The biggest LIR, de.telekom, will pay a little over 2700 euro for
28.972.032 IP addresses.</p>
<p>I just don't understand the reasoning behind the "volume" here.</p>
<p>In earlier discussions from the last 2 years here on
members-discuss, the RIPE representatives kept telling us that the
annual fee is a member fee and not a price for the resources used.</p>
<p>Now, I see a 180 degrees shift in their reasoning.</p>
<p>They are telling us that this Option B is the more fairest
because it takes into account the number of allocations because
this is somehow representing the resources used by a LIR. But why
not take into account all types of objects from the database?</p>
<p>Contact persons, route objects, domains, roles, organizations and
many more ...</p>
<p><br>
</p>
<p>Regards,</p>
<p>Alex</p>
<p>P.S. I'm so angry at RIPE right now!<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>
<style type="text/css"><!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}--></style></p>
<div class="moz-cite-prefix">On 18.04.2019 11:37, Alexis Hanicotte
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMgDU7Y0VXQPJ37ECsP40YAAV=kDucWXta3cy=aboHJ8Vjr4QQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">I agree, this vote does not make sense to me.
<div>It seems to me that the board does not want a
volume-based pricing, and so suggests an option that few
will vote for. Then they can say "you see, people do not
want volume-based pricing"...<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>An issue with most suggested "Option C" schemes is that
final income will be too high.</div>
<div>Here is a spreadsheet to help do the math and see the
impact on each LIR.</div>
<div><a
href="https://docs.google.com/spreadsheets/d/1oVAQ7ADW3UY17GPUgJl2T8AhMwHaDiuCb8a9fY6bark/edit?usp=sharing"
target="_blank" moz-do-not-send="true">https://docs.google.com/spreadsheets/d/1oVAQ7ADW3UY17GPUgJl2T8AhMwHaDiuCb8a9fY6bark/edit?usp=sharing</a><br>
</div>
<div>(feel free to make a copy and do you own math)</div>
<div><br>
</div>
<div>For instance, if we estimate RIPE needed budget to 32M€,</div>
<div>and decide to charge half via flat fee, half via number
of IPs,</div>
<div>that gives 740€ + 2.7cents / IPv4 address or IPv6/32
prefix.</div>
<div>(see tab n°2 of spreadsheet)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br clear="all">
<div>
<div dir="ltr"
class="m_-6998649169729600169gmail_signature">
<div dir="ltr">Alexis Hanicotte
<div>VelumWare SAS</div>
</div>
</div>
</div>
<br>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Apr 18, 2019 at 10:23
AM Michal Prokeš <<a href="mailto:michal.prokes@hdata.cz"
target="_blank" moz-do-not-send="true">michal.prokes@hdata.cz</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">
<div bgcolor="#FFFFFF">
<p>Dear colleagues,<br>
</p>
<p>there are many users discussing about per ipv4 payments
for a long time. I does not have to be most wanted option,
but I believe, it is most discussed option last years. </p>
<p>So if we decide to make voting about charging scheme, it
should include the most discussed option. We will see if
it win or not. Voting without this option is misleading.
Organizations with huge allocations love actual schema
(optiona A) and small organizations with symbolic
alocation of /22 are definitely not going to vote for
option B (very simplified it means: the less you have to
buy on expensive ipv4 market the less you have to pay RIPE
annualy).<br>
</p>
<p>Please <br>
</p>
<p>* Add option C (per-ipv4 fee) to choices<br>
</p>
<p> or <br>
</p>
<p>* Cancel this voting. <br>
</p>
<p><br>
</p>
<p>Results of voting with announced options will be very
misleading.</p>
<p>Thanks,</p>
<p>M. Prokeš<br>
</p>
<blockquote type="cite">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">----------
Forwarded message ----------<br>
From: Gwen van Berne <a
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-rfc2396E"
href="mailto:gvanberne@ripe.net" target="_blank"
moz-do-not-send="true"><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
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-abbreviated"
href="mailto:ncc-announce@ripe.net"
target="_blank" moz-do-not-send="true">ncc-announce@ripe.net</a><br>
Cc: <br>
<br type="attribution">
<blockquote
class="gmail-m_-6998649169729600169gmail-m_9254179706608250quote">
<p dir="ltr">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
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-freetext"
href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/supporting-documents"
target="_blank" moz-do-not-send="true">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
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-rfc2396E"
href="mailto:members-discuss@ripe.net"
target="_blank" moz-do-not-send="true"><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
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-freetext"
href="https://www.ripe.net/s/gm-registration-may-2019" target="_blank"
moz-do-not-send="true">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
class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-freetext"
href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/"
target="_blank" moz-do-not-send="true">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>
</p>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset
class="gmail-m_-6998649169729600169gmail-m_9254179706608250mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-quote-pre">_______________________________________________
members-discuss mailing list
<a class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net" target="_blank" moz-do-not-send="true">members-discuss@ripe.net</a>
<a class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-freetext" href="https://mailman.ripe.net/" target="_blank" moz-do-not-send="true">https://mailman.ripe.net/</a>
Unsubscribe: <a class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-freetext" href="https://lists.ripe.net/mailman/options/members-discuss/michal.prokes%40hdata.cz" target="_blank" moz-do-not-send="true">https://lists.ripe.net/mailman/options/members-discuss/michal.prokes%40hdata.cz</a>
</pre>
</blockquote>
<pre class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-signature" cols="72">--
Michal Prokeš, Internetová síť <a href="http://wosa.cz" target="_blank" moz-do-not-send="true">wosa.cz</a>
H-data, spol. s r.o., Václavská 4, 603 00 Brno
Infolinka: +420 534 001 200 Email: <a class="gmail-m_-6998649169729600169gmail-m_9254179706608250moz-txt-link-abbreviated" href="mailto:info@wosa.cz" target="_blank" moz-do-not-send="true">info@wosa.cz</a></pre>
</div>
_______________________________________________<br>
members-discuss mailing list<br>
<a href="mailto:members-discuss@ripe.net" target="_blank"
moz-do-not-send="true">members-discuss@ripe.net</a><br>
<a
href="https://mailman.ripe.net/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mailman.ripe.net/</a><br>
Unsubscribe: <a
href="https://lists.ripe.net/mailman/options/members-discuss/alexis%40velumware.com"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.ripe.net/mailman/options/members-discuss/alexis%40velumware.com</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
members-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/">https://mailman.ripe.net/</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.ripe.net/mailman/options/members-discuss/alexandru.doszlop%40netprotect.ro">https://lists.ripe.net/mailman/options/members-discuss/alexandru.doszlop%40netprotect.ro</a>
</pre>
</blockquote>
</body>
</html>