<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>To the person (185.65.119.17 and 73.44.39.27) who is trying to
reset my password / removing me from this list:</p>
<p>Whats wrong with you? If there's a problem, please contact me by
email. Thanks.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 17.04.19 19:28, Patrick Velder
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d6a0add6-b9b2-dc09-4cc7-803235eb180a@velder.li">
<p>+1.<br>
There should be a fee of 50€ per 1024 addresses or something
like this, not per resource. <br>
</p>
<div class="moz-cite-prefix">On 17.04.19 19:04, Alexandru Doszlop
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c54b2934-ef7d-4d9c-8bfa-bdfafe1f5a5f@email.android.com">
<div dir="auto">
<div>Hello, </div>
<div dir="auto"><br>
</div>
<div dir="auto">I just read the email regarding the charging
scheme for 2020 option B. </div>
<div dir="auto">Are you kidding me? </div>
<div dir="auto">Are you really naming it "volume based
billing"?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Let's say one isp has only one /12 ipv4 PA. It
will pay 1150 euro + 50 euro. </div>
<div dir="auto">The other LIR that wants to help small
companies and has 50 /24 assignments, will pay 1150 +
50*50=3650 euro. </div>
<div dir="auto">All new lirs that receive smaller than /22
assignments will pay more than than the big isp. </div>
<div dir="auto">Where is the volume here? </div>
<div dir="auto"><br>
</div>
<div dir="auto">Unbelievable... </div>
<div dir="auto"><br>
</div>
<div dir="auto">Regards, </div>
<div dir="auto">Alex</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote" dir="auto">---------- Forwarded
message ----------<br>
From: Gwen van Berne <a class="moz-txt-link-rfc2396E"
href="mailto:gvanberne@ripe.net" 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="moz-txt-link-abbreviated"
href="mailto:ncc-announce@ripe.net"
moz-do-not-send="true">ncc-announce@ripe.net</a><br>
Cc: <br>
<br type="attribution">
<blockquote class="quote">
<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="moz-txt-link-freetext"
href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/supporting-documents"
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="moz-txt-link-rfc2396E"
href="mailto:members-discuss@ripe.net"
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="moz-txt-link-freetext"
href="https://www.ripe.net/s/gm-registration-may-2019"
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="moz-txt-link-freetext"
href="https://www.ripe.net/participate/meetings/gm/meetings/may-2019/"
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="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
members-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net" moz-do-not-send="true">members-discuss@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/" moz-do-not-send="true">https://mailman.ripe.net/</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.ripe.net/mailman/options/members-discuss/lists%40velder.li" moz-do-not-send="true">https://lists.ripe.net/mailman/options/members-discuss/lists%40velder.li</a>
</pre>
</blockquote>
<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/lists%40velder.li">https://lists.ripe.net/mailman/options/members-discuss/lists%40velder.li</a>
</pre>
</blockquote>
</body>
</html>