<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Our offer is that the proposal can be somehow adjusted to the current LIR number (about 20’000) based on the fee we had years ago with 15’000 LIR number.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We suppose that it is important to support the increase of IPv6 usage, so it is not reasonable to apply charges for the resources, especially IPv6, at least at
this stage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Increase of IPv6 usage can change the situation significantly.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Naira<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> members-discuss <members-discuss-bounces@ripe.net>
<b>On Behalf Of </b>Cynthia Revström via members-discuss<br>
<b>Sent:</b> Wednesday, April 10, 2024 5:42 PM<br>
<b>To:</b> Simon-Jan Haytink <simonjh@ripe.net><br>
<b>Cc:</b> Members Discuss <members-discuss@ripe.net><br>
<b>Subject:</b> Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2025 Proposals<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I would just like to say that unlike most others who have commented so far I'm pretty happy with these proposals for the most part.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The RIPE NCC has barely increased its fees at all for about a decade despite a fair amount of inflation during that time.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I support only offering charging schemes that are sustainable and won't require digging deep into the reserves. That's not what the reserves are for.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Something to also remember is that the numbers of members has stayed pretty consistent, it's the number of LIR accounts that has reduced. I would suspect that a lot of costs for the NCC will be the similar regardless of if a member has
one LIR account or five.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">-Cynthia<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, 10 Apr 2024, 12:49 Simon-Jan Haytink, <<a href="mailto:simonjh@ripe.net">simonjh@ripe.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Dear RIPE NCC members,</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">We can now share three draft charging scheme models for 2025 that the Executive Board approved with the following resolution at its meeting on 25 March
2024:</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">The RIPE NCC Executive Board approves the submission of the RIPE NCC Charging Scheme 2025 options to the upcoming RIPE NCC General Meeting for members
to vote on.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Option A - Charging Scheme as is with 22.58% price increase for the annual contribution per LIR account (EUR 1,900) and a 0% price increase for Independent
Internet number resource assignments* (EUR 50)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Option B - Charging Scheme as is with 20.97% price increase for the annual contribution per LIR account (EUR 1,875) and a 50% price increase for Independent
Internet number resource assignments* (EUR 75)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Option C - Charging Scheme as is with 16.13% price increase for the annual contribution per LIR account (EUR 1,800), a 50% price increase for Independent
Internet number resource assignments* (EUR 75) and a new AS Numbers fee of EUR 50 per assignment</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">*<span style="color:#0D0D0D;background:white">Resources falling under this charge are IPv4 and IPv6 PI assignments; Anycast assignments; IPv4 and IPv6
IXP assignments; and Legacy IPv4 resource registrations through a sponsoring LIR.</span></span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#0D0D0D;background:white">The full draft charging scheme models are available from the GM Documentation page:<br>
</span><a href="https://www.ripe.net/membership/meetings/gm/meetings/may-2024/documentation-and-archives/supporting-documents/" target="_blank"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC;background:white">https://www.ripe.net/membership/meetings/gm/meetings/may-2024/documentation-and-archives/supporting-documents/</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#0D0D0D;background:white">Although the proposed models are relatively simple, we provide a calculator where you can see exactly what you would pay
under each of the proposed models:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><a href="https://www.ripe.net/documents/3757/CS2025_Member_Calculator.xlsx" target="_blank"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC;background:white">https://www.ripe.net/documents/3757/CS2025_Member_Calculator.xlsx</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">The main considerations for the Executive Board in proposing these three models are:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">1. The consolidation of LIR accounts, which means the burden to generate sufficient income must be met by fewer accounts</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">2. Increased costs due to inflation that were previously catered for by the large number of LIR accounts</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">3. Following the discussions last year and again this year, there appears to be no clear consensus among members on how a category-based model would work
and the Board does not wish to put another category model forward at the upcoming GM that will be rejected by the members. Rather, the Board will propose a simple model that guarantees adequate funding for 2025 and 2026 - under this proposal, we expect there
would be no need for a fee increase for 2026. The Board will work with the RIPE NCC on a more in-depth consultation with the members aimed at arriving at a sustainable solution for 2027 and beyond, possibly involving a new charging scheme task force. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">All three proposed models are designed to arrive at the same income of EUR 41.1 million for the RIPE NCC in 2025. This will cover all current services
and activities, a 5% staff cost increase, a 2% inflation increase on all non-staff costs, and EUR 1 million for additional work relating to registry complexity and security projects aimed at ensuring the resilience of the Registry and the RIPE NCC more broadly.
Any such additional work would be discussed with the membership during Activity Plan and Budget consultations and then need to be approved by the Board. This will also allow some leeway should more LIR accounts close than we expect.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">It’s important to note that the RIPE NCC aims for an income budget that will provide a surplus, and this means that should we meet our budgetary targets,
a surplus can be returned to members in 2026 should they so wish.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">While the RIPE NCC continues to carry out cost-cutting efforts across the organisation, drastically reducing the budget at this time is not advisable due
to the work that needs to be carried out, especially in relation to maintaining high-quality registry services and securing the registry and RIPE NCC systems. Cutting services or activities is not something the Board is planning to do, and such actions would
take time and need full consultation with the membership. An overview of the activities and services that the membership fee covers is provided below this email.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">I also urge you to see the presentation we delivered at the charging scheme open house in March so that the full context of the situation and the financial
landscape we face is clear to you. The slides are available at:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><a href="https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-scheme-2025/" target="_blank"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">https://www.ripe.net/membership/meetings/open-house/ripe-ncc-charging-scheme-2025/</span></a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Finally, I want to thank all those who have contributed to the consultation so far on the RIPE NCC Charging Scheme 2025. The models we present here are
draft and in two weeks we will announce the final proposal that members will vote on at the GM on 22-24 May. Please discuss the draft proposal on the
</span><a href="mailto:members-discuss@ripe.net" target="_blank"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">members-discuss@ripe.net</span></a><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> list - any input received
by 19 April can be incorporated if possible into the final models we propose. And make sure to register for the GM so that you can vote on the charging scheme that will apply for you and all members next year:</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><a href="https://my.ripe.net/#/meetings/active" target="_blank"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#1155CC">https://my.ripe.net/#/meetings/active</span></a><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Simon-Jan Haytink</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Chief Financial Officer</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">RIPE NCC</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">Services and Activities Covered by the Member Fee</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- A trusted, efficient, accurate and resilient registry that guarantees uniqueness of resources held by members</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Neutral information services uninfluenced by commercial or government interests that allow both the RIPE NCC and the community to carry out useful research
into the Internet</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Engagement activities, including RIPE and regional meetings, that build an active membership and community and that contribute to the overall good of
the Internet</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- A voice and influence for the membership in key decision-making fora, including with governments and regulators</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Protection of the Joint Internet Number Registry as developed by the Internet community</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Learning and development activities that help to address skills shortages and contribute to an educated membership</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- Support for the Policy Development Process (PDP)</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- An authoritative registry of routing information provided by RPKI and the RIPE Database</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- K-root and DNS services</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Arial",sans-serif">- A dedicated staff with considerable expertise contributing to all of the above</span><o:p></o:p></p>
</div>
<p class="MsoNormal">-- <br>
Click here to unsubscribe or change your email settings: <a href="https://lists.ripe.net/mailman/options/ncc-announce" target="_blank">
https://lists.ripe.net/mailman/options/ncc-announce</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>