<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></style> </head> <body lang="RU" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> Confidential/Конфіденційно <div> <div class="WordSection1"> Why do you think “is simply not true” ??<o:p></o:p> <o:p> </o:p> In majority of cases in small LIR relations with RIPE will care 1-2 people in big LIR 2-4. Not so big difference.<o:p></o:p> And about offline learning, as 1 LIR you can register 2 persons, it is totally independently of LIR size.<o:p></o:p> <o:p> </o:p> -----Original Message----- From: Sebastian-Wilhelm Graf <ripe-members@sebastian-graf.at> Sent: Thursday, April 11, 2024 5:14 PM To: Evgeniy Brodskiy <Evgeniy.Brodskiy@kyivstar.net>; members-discuss@ripe.net Subject: Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2025 Proposals <o:p> </o:p> > If you think about different "non-MAIN" services like Learning, then there is no difference between big and small LIR at all.<o:p></o:p> <o:p> </o:p> This is simply not true. If you think of a larger LIR (typically, but not always) with more employees, the bigger lir will typically (Again not always) have more of its Employees attend real life training events for example.<o:p></o:p> <o:p> </o:p> Whereas smaller LIR's may be bound by tighter budgets and will potentially focus on online-sessions.<o:p></o:p> <o:p> </o:p> The same is also true for community building with real life events.<o:p></o:p> <o:p> </o:p> This is also why i would favor that the RipeNCC focuses on online events and online training (with recorded corses and just online Q&A sessions) over "tought" courses (with the same content repeating) for real life/online sessions.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> > Even if you think about auditing or maintaining RIPE DB, it would be strange to think that working with /16 requires 256 times more time and effort than working with /24.<o:p></o:p> <o:p> </o:p> While i would not say 256 times more, i would say more on average. Because whats the chance both will be a single assignment of the whole resources to an end user/org? And if the resource is split into smaller inetnums then yes it will be more time to audit,...<o:p></o:p> <o:p> </o:p> <o:p> </o:p> > And again you are talking about fairness.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Especially when considering the argument above, if we want a contribution that is more fair than the current model to most of the LIR's, then the number of assignments (per /48, or /24) is a good general indicator of scale.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Regards<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> On 4/11/24 3:53 PM, Evgeniy Brodskiy via members-discuss wrote:<o:p></o:p> > Confidential/Конфіденційно<o:p></o:p> ><o:p> </o:p> > Why do you think this statement is correct: “They are the main source of work for RIPE employees.” ??<o:p></o:p> ><o:p> </o:p> > Even if you think about auditing or maintaining RIPE DB, it would be strange to think that working with /16 requires 256 times more time and effort than working with /24.<o:p></o:p> > If you think about different "non-MAIN" services like Learning, then there is no difference between big and small LIR at all.<o:p></o:p> > Resources do not reflect all of these dependencies. And again you are talking about fairness.<o:p></o:p> ><o:p> </o:p> ><o:p> </o:p> > -----Original Message-----<o:p></o:p> > From: members-discuss <<a href="mailto:members-discuss-bounces@ripe.net">members-discuss-bounces@ripe.net</a>> On Behalf Of <o:p></o:p> > Mihail Fedorov<o:p></o:p> > Sent: Thursday, April 11, 2024 3:39 PM<o:p></o:p> > Cc: <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> > Subject: Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC <o:p></o:p> > Charging Scheme 2025 Proposals<o:p></o:p> ><o:p> </o:p> > Charging per ASN is even worse than just price increase. It is <o:p></o:p> > terrible and killing even more LIRs<o:p></o:p> ><o:p> </o:p> > Imagine rather new LIR who is trying to do business based on what is LIR intended for - providing LIR services to consumers. For example 30 clients who requested ASN sponsorship during year.<o:p></o:p> > If charged per ASN they will pay twice more than huge corporations serving only purpose of their own. Those typically have just 1-2 ASNs and tons of resources attached to it. They are main source of work for RIPE staff and they should be funding expensive projects like Atlas and others.<o:p></o:p> ><o:p> </o:p> > Actually working LIRs also have business contracts/logic already established on current charging scheme and adding ASN fee will kill them.<o:p></o:p> ><o:p> </o:p> > Once again - why not just bill based on resources? It’s extremely <o:p></o:p> > easy. Oh, right, resource holders won’t like it :)<o:p></o:p> ><o:p> </o:p> >> On 11 Apr 2024, at 15:11, ROSKOMNADZOR LIMITED <<a href="mailto:admin@roskomnadzor.io">admin@roskomnadzor.io</a>> wrote:<o:p></o:p> >><o:p> </o:p> >> Why LIR who havent resources must pay same amount as LIR who have a lot of resources?<o:p></o:p> >><o:p> </o:p> >> RIPE declaring about "community" and about "spending budget must be distributed across all members" - but in practically is not.<o:p></o:p> >><o:p> </o:p> >> When RIPE want to take extra fee for ASN - its mean then RIPE want to charge by resources. Then why RIPE dont want to charge due resources for IPv4?<o:p></o:p> >><o:p> </o:p> >> Guess big members who hold a lot IPv4 allocations dont want it - because current situation is fine for their point of view. Dont forget - RIPE charget 50 EUR per resource - not matter what is it - /24 or /16.<o:p></o:p> >><o:p> </o:p> >> If we are not using all RIPE services - why we must pay for that? Why not any option to select - "Only core services"?<o:p></o:p> >><o:p> </o:p> >><o:p> </o:p> >><o:p> </o:p> >> On 11.04.2024 11:45, Evgeniy Brodskiy wrote:<o:p></o:p> >>> Confidential/Конфіденційно<o:p></o:p> >>> Hi,<o:p></o:p> >>> Not at all.<o:p></o:p> >>> More RESOURCES in hands of some LIR doesn’t mean consuming MORE SERVICES.<o:p></o:p> >>> If you want to bill somebody based on consuming SERVICES it would be logical to count consuming SERVICES, not RESOURCES.<o:p></o:p> >>> But who cares about logic if goal to force somebody else to pay... even if some particular BIG LIR doesn't use majority of this SERVICES.<o:p></o:p> >>> -----Original Message-----<o:p></o:p> >>> From: members-discuss <<a href="mailto:members-discuss-bounces@ripe.net">members-discuss-bounces@ripe.net</a>> On Behalf <o:p></o:p> >>> Of ROSKOMNADZOR LIMITED<o:p></o:p> >>> Sent: Thursday, April 11, 2024 2:06 PM<o:p></o:p> >>> To: <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >>> Subject: Re: [members-discuss] [ncc-announce] [GM] Draft RIPE NCC <o:p></o:p> >>> Charging Scheme 2025 Proposals [Вы нечасто получаете письма от <o:p></o:p> >>> <a href="mailto:admin@roskomnadzor.io">admin@roskomnadzor.io</a>. Узнайте, почему это важно, по адресу <a href="https://aka.ms/LearnAboutSenderIdentification">https://aka.ms/LearnAboutSenderIdentification</a> ] Its great, but why RIPE trying to make funding from less adquate method?<o:p></o:p> >>> Big members of RIPE region request MORE SERVICE - but why ALL must pay for that?<o:p></o:p> >>> Why RIPE continue to ignoring taking membership fee based on RESOURCES?<o:p></o:p> >>> Currently RIPE depend upon LIR signup fee and year/year LIR fee in most cases - but its very unstable.<o:p></o:p> >>> NOR, RIPE can take fee per IPv4/24 in holding per member and have STABLE SOURCE OF FUNDING!<o:p></o:p> >>> ARIN, APNIC, AFRINIC already a long time do it on successful basis.<o:p></o:p> >>> Why small members of RIPE must pay SAME amount as big members? Are its fair? Guess not.<o:p></o:p> >>> Dont forget about fact - if early LIR guarantee receive /22, after <o:p></o:p> >>> only<o:p></o:p> >>> /24 - then now LIR receive only place in waiting list (like in Communists USSR) and undefined ETA on receive resources! But pay SAME amount as any other.<o:p></o:p> >>> Why RIPE didnt want to change fee based on fact - if LIR didnt have IPv4 in holding - then LIR must pay less, nor LIR who holding 10-100-100 IPv4 blocks?<o:p></o:p> >>> On 11.04.2024 10:46, Daniel Stolpe via members-discuss wrote:<o:p></o:p> >>>> Hi,<o:p></o:p> >>>><o:p> </o:p> >>>> Yoel is absolutely right. A few years ago the financial situation <o:p></o:p> >>>> was not looking good but the "last /8 policy" made a huge <o:p></o:p> >>>> difference. The "handing out /22 blocks" was like printing new money - for a while.<o:p></o:p> >>>> As the number of members whent sky rocket, RIPE could lower <o:p></o:p> >>>> membership fees at the same time as an ever expanding budget.<o:p></o:p> >>>><o:p> </o:p> >>>> But now we are seeing what everyone could have predicted - the <o:p></o:p> >>>> number of members are declining and the NCC keeps calling for more money.<o:p></o:p> >>>><o:p> </o:p> >>>> No, this is not reasonable. In tough times everyone has to try to <o:p></o:p> >>>> make ends meet. The NCC should be no exception. For years only a <o:p></o:p> >>>> few persistent voices have been trying to call for cuts or cost <o:p></o:p> >>>> control as an alternative to eternal growth. What happened last <o:p></o:p> >>>> year should have been a clear signal but instead the voting is now <o:p></o:p> >>>> rigged with more or less equal outcomes.<o:p></o:p> >>>><o:p> </o:p> >>>> Regards,<o:p></o:p> >>>> Daniel Stolpe<o:p></o:p> >>>><o:p> </o:p> >>>> On Thu, 11 Apr 2024, Yoel Caspersen via members-discuss wrote:<o:p></o:p> >>>><o:p> </o:p> >>>>> Dear RIPE member,<o:p></o:p> >>>>><o:p> </o:p> >>>>> Kaj Niemi is absolutely right: RIPE increasing its budget does not <o:p></o:p> >>>>> serve the interests of its members, and allowing it to pass <o:p></o:p> >>>>> because you are spending other people's money is a sign of bad <o:p></o:p> >>>>> judgement and lack of accountability.<o:p></o:p> >>>>><o:p> </o:p> >>>>> For years, I was wondering why RIPE was handing out /22 blocks at <o:p></o:p> >>>>> what was effectively a fraction of the market price. I think we <o:p></o:p> >>>>> have the answer now: Membership fees and diluted voting power of <o:p></o:p> >>>>> each member served the interests of the management just fine.<o:p></o:p> >>>>><o:p> </o:p> >>>>> RIPE is a mandatory phonebook for IP addresses, nothing more and <o:p></o:p> >>>>> nothing less. All the fat that has grown on the organisation in <o:p></o:p> >>>>> the last decade must be trimmed, and I call for a drastic budget <o:p></o:p> >>>>> reduction - if some members are willing to spend their own money <o:p></o:p> >>>>> on additional services, they should be free to do so, but with <o:p></o:p> >>>>> absolute emphasis on this part: their own money.<o:p></o:p> >>>>><o:p> </o:p> >>>>> From a fairness perspective, RIPE should be granted the necessary <o:p></o:p> >>>>> funds to run the database service, meaning:<o:p></o:p> >>>>><o:p> </o:p> >>>>> - A base fee to keep the database service running, shared equally <o:p></o:p> >>>>> by all members<o:p></o:p> >>>>> - Fees on actions that require manual work from the RIPE NCC (e.g.<o:p></o:p> >>>>> transfers, mergers etc)<o:p></o:p> >>>>><o:p> </o:p> >>>>> Forget about levying higher taxes on larger members - RIPE is not <o:p></o:p> >>>>> a tax collector and doesn't exist to offset differences in wealth. <o:p></o:p> >>>>> It exists to deliver a necessary service, and each member should <o:p></o:p> >>>>> pay according to the burden they place on the organisation.<o:p></o:p> >>>>><o:p> </o:p> >>>>> How much should we pay for a database service? In the ideal world, <o:p></o:p> >>>>> there should be no monopoly on the service and we could let the <o:p></o:p> >>>>> market forces decide what the right price is.<o:p></o:p> >>>>><o:p> </o:p> >>>>> I realize that might not be feasible right now, so we are stuck <o:p></o:p> >>>>> with the next best solution: Letting the community figure out what <o:p></o:p> >>>>> the acceptable price is - I guess most RIPE members run some sort <o:p></o:p> >>>>> of database service of their own and therefore possess a profound <o:p></o:p> >>>>> understanding of the associated costs.<o:p></o:p> >>>>><o:p> </o:p> >>>>> Until we have better data, I suggest we look at the past for<o:p></o:p> >>>>> inspiration: Use the budget for 2014 (€ 22 millions) and adjust <o:p></o:p> >>>>> for inflation - that amounts to approximately € 28 millions.<o:p></o:p> >>>>><o:p> </o:p> >>>>> To get there we can slash External Engagement & Community (€ 9,4 <o:p></o:p> >>>>> millions in the 2024 budget) - RIPE is a monopoly, and the members <o:p></o:p> >>>>> will be there regardless of the activities in that area.<o:p></o:p> >>>>><o:p> </o:p> >>>>> I also suggest that we take a look at the expenses associated with <o:p></o:p> >>>>> the Office of the Managing Director (€ 2,2 millions in the 2024<o:p></o:p> >>>>> budget) - after all, RIPE is an organisation with less than 200 <o:p></o:p> >>>>> employees.<o:p></o:p> >>>>><o:p> </o:p> >>>>> I call for members of the community to contribute: What is the <o:p></o:p> >>>>> right amount of staffing in the RIPE NCC?<o:p></o:p> >>>>><o:p> </o:p> >>>>> Regards,<o:p></o:p> >>>>><o:p> </o:p> >>>>> Yoel Caspersen<o:p></o:p> >>>>> CTO<o:p></o:p> >>>>> Kviknet.dk ApS<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> On Wed, Apr 10, 2024 at 3:12 PM Kaj Niemi <<a href="mailto:kajtzu@basen.net">kajtzu@basen.net</a>> wrote:<o:p></o:p> >>>>> Hi,<o:p></o:p> >>>>><o:p> </o:p> >>>>> Very politely put I do not think any of the three proposed <o:p></o:p> >>>>> charging schemes are in the membership's interest - they certainly aren't in mine.<o:p></o:p> >>>>><o:p> </o:p> >>>>> All three seem to be designed to assure that NCC can continue <o:p></o:p> >>>>> along, business as usual, with its tasks. Thus, we could pretend <o:p></o:p> >>>>> that there isn't a big issue with the membership numbers declining.<o:p></o:p> >>>>> We could also pretend there isn't a real problem with the value <o:p></o:p> >>>>> proposition of the services. Furthermore, we could also pretend <o:p></o:p> >>>>> that we do not care that it all is conveniently funded by the <o:p></o:p> >>>>> membership. I mean, what is<o:p></o:p> >>>>> 1500 or<o:p></o:p> >>>>> 1900 euro to most people? I have heard the last several times in <o:p></o:p> >>>>> the past. After all, why should we care about the expenditure when <o:p></o:p> >>>>> the sums are so small for each LIR? Why should we care when it is <o:p></o:p> >>>>> not our own money? I'll tell you. Not caring about the transaction <o:p></o:p> >>>>> size is bad, if you are willing to let these kinds of sums slide, <o:p></o:p> >>>>> you'll let it slide on bigger amounts. As is treating other <o:p></o:p> >>>>> people's money (OPM) differently than if it were your own. These <o:p></o:p> >>>>> eventually lead to lack of accountability.<o:p></o:p> >>>>><o:p> </o:p> >>>>> What is being proposed is really a significant increase in <o:p></o:p> >>>>> membership fees. In particular, significantly above what it used <o:p></o:p> >>>>> to cost on average to produce services for each member (whether <o:p></o:p> >>>>> they use them or not). Note when I say what it used to cost, as in<o:p></o:p> >>>>> FY2024 the cost per LIR will be higher.<o:p></o:p> >>>>><o:p> </o:p> >>>>> Now, with the membership in further decline the average cost per <o:p></o:p> >>>>> member will once more be higher in FY2025. Next year, I forecast <o:p></o:p> >>>>> that we will have the same "discussion" for<o:p></o:p> >>>>> FY2026 as NCC comes around and asks for more money. Once again. Why?<o:p></o:p> >>>>> Because according to projections the amount of members will <o:p></o:p> >>>>> continue to decrease resulting in higher fees per organization. Once again.<o:p></o:p> >>>>> All in the advantageous name of the articles of association that <o:p></o:p> >>>>> allow pretty much anything.<o:p></o:p> >>>>><o:p> </o:p> >>>>> Following the above rational thought with another is, that what <o:p></o:p> >>>>> one should be doing is choosing what to either invoice separately <o:p></o:p> >>>>> or drop completely. Yes, really. Everyone is happy with free <o:p></o:p> >>>>> services, it is when you apply the money test - request someone to <o:p></o:p> >>>>> pay for something<o:p></o:p> >>>>> - when you see if what you create contains value.<o:p></o:p> >>>>><o:p> </o:p> >>>>> Considering NCC managed to "save" 5% in the FY2024 budget compared <o:p></o:p> >>>>> to FY2023, asking for 8.1% increase (4% annualized) the next year <o:p></o:p> >>>>> is, well, kind of cheeky. It restores the budget pretty much to <o:p></o:p> >>>>> what it would have been with two annual increases. As an exercise <o:p></o:p> >>>>> in budgetary engineering I do approve. As a paying member I do not.<o:p></o:p> >>>>><o:p> </o:p> >>>>> What really would be needed is competition. Competition would make <o:p></o:p> >>>>> the RIR market more efficient. It is rather obvious that the RIR <o:p></o:p> >>>>> markets aren't anywhere near the efficiency they could be at.<o:p></o:p> >>>>> Competition would mean that people wanting to pay<o:p></o:p> >>>>> 1900 - or even more in the future - could choose to do so and <o:p></o:p> >>>>> those who don't want could potentially pay less. Reduced to the <o:p></o:p> >>>>> very basics one is paying for bits in a database.<o:p></o:p> >>>>> In that sense this is rather similar to the certificate market <o:p></o:p> >>>>> where at one time the cost per certificate was sky high and there <o:p></o:p> >>>>> were only a few issuers. Today, I am guessing most do not pay <o:p></o:p> >>>>> thousands annually for a few bits in theirs. Neither do most <o:p></o:p> >>>>> people care whether the cert was issued by Verisign, Gandi or someone else.<o:p></o:p> >>>>> Having looked into it out of curiosity, real competition does not <o:p></o:p> >>>>> seem to be possible as the principles in<o:p></o:p> >>>>> ICP-2 pretty much state that there can/should only be one RIR per <o:p></o:p> >>>>> region. Which makes NCC the definition of a monopoly. Monopolies <o:p></o:p> >>>>> with nice and polite people, well intended purpose and mission <o:p></o:p> >>>>> creep are not good, they're bad. For everyone.<o:p></o:p> >>>>><o:p> </o:p> >>>>> Finally, the surplus. The concept itself is interesting and I do <o:p></o:p> >>>>> know where it comes from. But from an financial point of view it <o:p></o:p> >>>>> is really lending money to someone else and then (maybe) getting <o:p></o:p> >>>>> it back, a year later, less inflation if they did not spend it.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> I would kindly request that the EB would add option D or "Option D:<o:p></o:p> >>>>> No Changes from 2023". :)<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Kaj<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Kaj<o:p></o:p> >>>>><o:p> </o:p> >>>>> __________________________________________________________________<o:p></o:p> >>>>> _<o:p></o:p> >>>>> __<o:p></o:p> >>>>> __________________________________________________________________<o:p></o:p> >>>>> _ __ ___________________________________________<o:p></o:p> >>>>><o:p> </o:p> >>>>> From: ncc-announce <<a href="mailto:ncc-announce-bounces@ripe.net">ncc-announce-bounces@ripe.net</a>> on behalf of <o:p></o:p> >>>>> Simon-Jan Haytink <<a href="mailto:simonjh@ripe.net">simonjh@ripe.net</a>><o:p></o:p> >>>>> Sent: Wednesday, April 10, 2024 12:18<o:p></o:p> >>>>> To: <a href="mailto:ncc-announce@ripe.net">ncc-announce@ripe.net</a> <<a href="mailto:ncc-announce@ripe.net">ncc-announce@ripe.net</a>><o:p></o:p> >>>>> Subject: [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2025 <o:p></o:p> >>>>> Proposals You don't often get email from <a href="mailto:simonjh@ripe.net"> simonjh@ripe.net</a>. Learn <o:p></o:p> >>>>> why this is important<o:p></o:p> >>>>><o:p> </o:p> >>>>> Dear RIPE NCC members,<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> We can now share three draft charging scheme models for 2025 that <o:p></o:p> >>>>> the Executive Board approved with the following resolution at its <o:p></o:p> >>>>> meeting on 25 March 2024:<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> The RIPE NCC Executive Board approves the submission of the RIPE <o:p></o:p> >>>>> NCC Charging Scheme 2025 options to the upcoming RIPE NCC General <o:p></o:p> >>>>> Meeting for members to vote on.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> - Option A - Charging Scheme as is with 22.58% price increase <o:p></o:p> >>>>> for the annual contribution per LIR account (EUR 1,900) and a 0% <o:p></o:p> >>>>> price increase for Independent Internet number resource <o:p></o:p> >>>>> assignments* (EUR<o:p></o:p> >>>>> 50)<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Option B - Charging Scheme as is with 20.97% price increase <o:p></o:p> >>>>> for the annual contribution per LIR account (EUR 1,875) and a 50% <o:p></o:p> >>>>> price increase for Independent Internet number resource <o:p></o:p> >>>>> assignments* (EUR<o:p></o:p> >>>>> 75)<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Option C - Charging Scheme as is with 16.13% price increase <o:p></o:p> >>>>> for the annual contribution per LIR account (EUR 1,800), a 50% <o:p></o:p> >>>>> price increase for Independent Internet number resource <o:p></o:p> >>>>> assignments* (EUR<o:p></o:p> >>>>> 75) and a new AS Numbers fee of EUR 50 per assignment<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> *Resources falling under this charge are IPv4 and IPv6 PI <o:p></o:p> >>>>> assignments; Anycast assignments; IPv4 and IPv6 IXP assignments; <o:p></o:p> >>>>> and Legacy IPv4 resource registrations through a sponsoring LIR.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> The full draft charging scheme models are available from the GM <o:p></o:p> >>>>> Documentation page:<o:p></o:p> >>>>> <a href="https://www/">https://www/</a><o:p></o:p> >>>>> .ripe.net%2Fmembership%2Fmeetings%2Fgm%2Fmeetings%2Fmay-2024%2Fdoc<o:p></o:p> >>>>> u<o:p></o:p> >>>>> me<o:p></o:p> >>>>> ntation-and-archives%2Fsupporting-documents%2F&data=05%7C02%7CEvge<o:p></o:p> >>>>> n<o:p></o:p> >>>>> iy<o:p></o:p> >>>>> .Brodskiy%40kyivstar.net%7C3dec1d17e9f54232d88c08dc5a18264a%7Cf8f9<o:p></o:p> >>>>> b<o:p></o:p> >>>>> d5<o:p></o:p> >>>>> 73bba4300a6ec3b8e70a30986%7C0%7C0%7C638484307004040536%7CUnknown%7<o:p></o:p> >>>>> C<o:p></o:p> >>>>> TW<o:p></o:p> >>>>> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJX<o:p></o:p> >>>>> V<o:p></o:p> >>>>> CI<o:p></o:p> >>>>> 6Mn0%3D%7C0%7C%7C%7C&sdata=3tUyMKDzZZY69M3vjjDqaKxgBrrQMeI1rnhBImz<o:p></o:p> >>>>> a<o:p></o:p> >>>>> ex<o:p></o:p> >>>>> Q%3D&reserved=0<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Although the proposed models are relatively simple, we provide a <o:p></o:p> >>>>> calculator where you can see exactly what you would pay under each <o:p></o:p> >>>>> of the proposed models:<o:p></o:p> >>>>><o:p> </o:p> >>>>> <a href="https://www/">https://www/</a><o:p></o:p> >>>>> .ripe.net%2Fdocuments%2F3757%2FCS2025_Member_Calculator.xlsx&data=<o:p></o:p> >>>>> 0<o:p></o:p> >>>>> 5%<o:p></o:p> >>>>> 7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C3dec1d17e9f54232d88c08dc5<o:p></o:p> >>>>> a<o:p></o:p> >>>>> 18<o:p></o:p> >>>>> 264a%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C6384843070040515<o:p></o:p> >>>>> 6<o:p></o:p> >>>>> 6%<o:p></o:p> >>>>> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTi<o:p></o:p> >>>>> I<o:p></o:p> >>>>> 6I<o:p></o:p> >>>>> k1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=glTH6W6VCl6MSXrBbsUC8A4K%<o:p></o:p> >>>>> 2<o:p></o:p> >>>>> FK<o:p></o:p> >>>>> TE8%2FavtiBwmmokOEY%3D&reserved=0<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> The main considerations for the Executive Board in proposing these <o:p></o:p> >>>>> three models are:<o:p></o:p> >>>>><o:p> </o:p> >>>>> 1. The consolidation of LIR accounts, which means the burden to <o:p></o:p> >>>>> generate sufficient income must be met by fewer accounts<o:p></o:p> >>>>><o:p> </o:p> >>>>> 2. Increased costs due to inflation that were previously catered <o:p></o:p> >>>>> for by the large number of LIR accounts<o:p></o:p> >>>>><o:p> </o:p> >>>>> 3. Following the discussions last year and again this year, there <o:p></o:p> >>>>> appears to be no clear consensus among members on how a <o:p></o:p> >>>>> category-based model would work and the Board does not wish to put <o:p></o:p> >>>>> another category model forward at the upcoming GM that will be <o:p></o:p> >>>>> rejected by the members. Rather, the Board will propose a simple <o:p></o:p> >>>>> model that guarantees adequate funding for 2025 and 2026 - under <o:p></o:p> >>>>> this proposal, we expect there would be no need for a fee increase <o:p></o:p> >>>>> for 2026. The Board will work with the RIPE NCC on a more in-depth <o:p></o:p> >>>>> consultation with the members aimed at arriving at a sustainable <o:p></o:p> >>>>> solution for 2027 and beyond, possibly involving a new charging <o:p></o:p> >>>>> scheme task force.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> All three proposed models are designed to arrive at the same <o:p></o:p> >>>>> income of EUR 41.1 million for the RIPE NCC in 2025. This will <o:p></o:p> >>>>> cover all current services and activities, a 5% staff cost <o:p></o:p> >>>>> increase, a 2% inflation increase on all non-staff costs, and EUR <o:p></o:p> >>>>> 1 million for additional work relating to registry complexity and <o:p></o:p> >>>>> security projects aimed at ensuring the resilience of the Registry <o:p></o:p> >>>>> and the RIPE NCC more broadly.<o:p></o:p> >>>>> Any such additional work would be discussed with the membership <o:p></o:p> >>>>> during Activity Plan and Budget consultations and then need to be <o:p></o:p> >>>>> approved by the Board. This will also allow some leeway should <o:p></o:p> >>>>> more LIR accounts close than we expect.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> It’s important to note that the RIPE NCC aims for an income budget <o:p></o:p> >>>>> that will provide a surplus, and this means that should we meet <o:p></o:p> >>>>> our budgetary targets, a surplus can be returned to members in <o:p></o:p> >>>>> 2026 should they so wish.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> While the RIPE NCC continues to carry out cost-cutting efforts <o:p></o:p> >>>>> across the organisation, drastically reducing the budget at this <o:p></o:p> >>>>> time is not advisable due to the work that needs to be carried <o:p></o:p> >>>>> out, especially in relation to maintaining high-quality registry <o:p></o:p> >>>>> services and securing the registry and RIPE NCC systems. Cutting <o:p></o:p> >>>>> services or activities is not something the Board is planning to <o:p></o:p> >>>>> do, and such actions would take time and need full consultation <o:p></o:p> >>>>> with the membership. An overview of the activities and services <o:p></o:p> >>>>> that the membership fee covers is provided below this email.<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> I also urge you to see the presentation we delivered at the <o:p></o:p> >>>>> charging scheme open house in March so that the full context of <o:p></o:p> >>>>> the situation and the financial landscape we face is clear to you. <o:p></o:p> >>>>> The slides are available at:<o:p></o:p> >>>>><o:p> </o:p> >>>>> <a href="https://www/">https://www/</a><o:p></o:p> >>>>> .ripe.net%2Fmembership%2Fmeetings%2Fopen-house%2Fripe-ncc-charging<o:p></o:p> >>>>> -<o:p></o:p> >>>>> sc<o:p></o:p> >>>>> heme-2025%2F&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C3dec<o:p></o:p> >>>>> 1<o:p></o:p> >>>>> d1<o:p></o:p> >>>>> 7e9f54232d88c08dc5a18264a%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7<o:p></o:p> >>>>> C<o:p></o:p> >>>>> 0%<o:p></o:p> >>>>> 7C638484307004057320%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL<o:p></o:p> >>>>> C<o:p></o:p> >>>>> JQ<o:p></o:p> >>>>> IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=5GTe<o:p></o:p> >>>>> I<o:p></o:p> >>>>> yn<o:p></o:p> >>>>> nzxx1WLZ%2BDRoFNWAhaRPvTemPafvKwlIaEEk%3D&reserved=0<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Finally, I want to thank all those who have contributed to the <o:p></o:p> >>>>> consultation so far on the RIPE NCC Charging Scheme 2025. The <o:p></o:p> >>>>> models we present here are draft and in two weeks we will announce <o:p></o:p> >>>>> the final proposal that members will vote on at the GM on 22-24 <o:p></o:p> >>>>> May. Please discuss the draft proposal on the <o:p> </o:p> >>>>> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> list - any input received by 19 April can <o:p></o:p> >>>>> be incorporated if possible into the final models we propose. And <o:p></o:p> >>>>> make sure to register for the GM so that you can vote on the <o:p></o:p> >>>>> charging scheme that will apply for you and all members next year:<o:p></o:p> >>>>><o:p> </o:p> >>>>> <a href="https://my/">https://my/</a>.<o:p></o:p> >>>>> ripe.net%2F%23%2Fmeetings%2Factive&data=05%7C02%7CEvgeniy.Brodskiy<o:p></o:p> >>>>> %<o:p></o:p> >>>>> 40<o:p></o:p> >>>>> kyivstar.net%7C3dec1d17e9f54232d88c08dc5a18264a%7Cf8f9bd573bba4300<o:p></o:p> >>>>> a<o:p></o:p> >>>>> 6e<o:p></o:p> >>>>> c3b8e70a30986%7C0%7C0%7C638484307004063238%7CUnknown%7CTWFpbGZsb3d<o:p></o:p> >>>>> 8<o:p></o:p> >>>>> ey<o:p></o:p> >>>>> JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7<o:p></o:p> >>>>> C<o:p></o:p> >>>>> 0%<o:p></o:p> >>>>> 7C%7C%7C&sdata=%2BkYHbjPqA8CwacCNlVg0M%2FVvao%2FK8z1zB8hrEeaLXVg%3<o:p></o:p> >>>>> D<o:p></o:p> >>>>> &r<o:p></o:p> >>>>> eserved=0<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Simon-Jan Haytink<o:p></o:p> >>>>><o:p> </o:p> >>>>> Chief Financial Officer<o:p></o:p> >>>>><o:p> </o:p> >>>>> RIPE NCC<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> Services and Activities Covered by the Member Fee<o:p></o:p> >>>>><o:p> </o:p> >>>>><o:p> </o:p> >>>>> - A trusted, efficient, accurate and resilient registry that <o:p></o:p> >>>>> guarantees uniqueness of resources held by members<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Neutral information services uninfluenced by commercial or <o:p></o:p> >>>>> government interests that allow both the RIPE NCC and the <o:p></o:p> >>>>> community to carry out useful research into the Internet<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Engagement activities, including RIPE and regional meetings, <o:p></o:p> >>>>> that build an active membership and community and that contribute <o:p></o:p> >>>>> to the overall good of the Internet<o:p></o:p> >>>>><o:p> </o:p> >>>>> - A voice and influence for the membership in key decision-making <o:p></o:p> >>>>> fora, including with governments and regulators<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Protection of the Joint Internet Number Registry as developed by <o:p></o:p> >>>>> the Internet community<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Learning and development activities that help to address skills <o:p></o:p> >>>>> shortages and contribute to an educated membership<o:p></o:p> >>>>><o:p> </o:p> >>>>> - Support for the Policy Development Process (PDP)<o:p></o:p> >>>>><o:p> </o:p> >>>>> - An authoritative registry of routing information provided by <o:p></o:p> >>>>> RPKI and the RIPE Database<o:p></o:p> >>>>><o:p> </o:p> >>>>> - K-root and DNS services<o:p></o:p> >>>>><o:p> </o:p> >>>>> - A dedicated staff with considerable expertise contributing to <o:p></o:p> >>>>> all of the above<o:p></o:p> >>>>><o:p> </o:p> >>>>> _______________________________________________<o:p></o:p> >>>>> members-discuss mailing list<o:p></o:p> >>>>> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >>>>> <a href="https://lis/">https://lis/</a><o:p></o:p> >>>>> ts.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7C<o:p></o:p> >>>>> E<o:p></o:p> >>>>> vg<o:p></o:p> >>>>> eniy.Brodskiy%40kyivstar.net%7C3dec1d17e9f54232d88c08dc5a18264a%7C<o:p></o:p> >>>>> f<o:p></o:p> >>>>> 8f<o:p></o:p> >>>>> 9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484307004071908%7CUnkno<o:p></o:p> >>>>> w<o:p></o:p> >>>>> n%<o:p></o:p> >>>>> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwi<o:p></o:p> >>>>> L<o:p></o:p> >>>>> CJ<o:p></o:p> >>>>> XVCI6Mn0%3D%7C0%7C%7C%7C&sdata=TSE6bLTaGjEzZzbwPbLL8ZivguLE4ZUOG1Y<o:p></o:p> >>>>> C<o:p></o:p> >>>>> 6W<o:p></o:p> >>>>> k3HVE%3D&reserved=0<o:p></o:p> >>>>> Unsubscribe:<o:p></o:p> >>>>> <a href="https://lis/">https://lis/</a><o:p></o:p> >>>>> ts.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fyoel%2540kviknet.<o:p></o:p> >>>>> dk&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C3dec1d17e9f542<o:p></o:p> >>>>> 3<o:p></o:p> >>>>> 2d<o:p></o:p> >>>>> 88c08dc5a18264a%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C63848<o:p></o:p> >>>>> 4<o:p></o:p> >>>>> 30<o:p></o:p> >>>>> 7004081513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2l<o:p></o:p> >>>>> u<o:p></o:p> >>>>> Mz<o:p></o:p> >>>>> IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=h8qgUsC1phTJj9<o:p></o:p> >>>>> r<o:p></o:p> >>>>> 9T<o:p></o:p> >>>>> HsO2THM2UZcg6CMMNwff4PP3SA%3D&reserved=0<o:p></o:p> >>>> ___________________________________________________________________<o:p></o:p> >>>> _<o:p></o:p> >>>> __<o:p></o:p> >>>> ___________<o:p></o:p> >>>><o:p> </o:p> >>>> Daniel Stolpe Tel: 08 - 688 11 81<o:p></o:p> >>>> <a href="mailto:stolpe@resilans.se">stolpe@resilans.se</a><o:p></o:p> >>>> Resilans AB Fax: 08 - 55 00 21 63<o:p></o:p> >>>> <a href="http://www.resilans.se/">https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.resilans.se%2F&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7Ca1abc79f92b648a3c3e408dc5a31a7ef%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484416574905618%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=D3czuShPaJb9z19rS%2FhjRLVucx4GtdN5RBrAFT25Pr0%3D&reserved=0</a><o:p></o:p> >>>> Box 45 094 556741-1193<o:p></o:p> >>>> 104 30 Stockholm<o:p></o:p> >>>><o:p> </o:p> >>>> _______________________________________________<o:p></o:p> >>>> members-discuss mailing list<o:p></o:p> >>>> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >>>> <a href="https://list/">https://list/</a><o:p></o:p> >>>> s.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEv<o:p></o:p> >>>> g<o:p></o:p> >>>> en<o:p></o:p> >>>> iy.Brodskiy%40kyivstar.net%7C3dec1d17e9f54232d88c08dc5a18264a%7Cf8f<o:p></o:p> >>>> 9<o:p></o:p> >>>> bd<o:p></o:p> >>>> 573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484307004100103%7CUnknown%7<o:p></o:p> >>>> C<o:p></o:p> >>>> TW<o:p></o:p> >>>> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV<o:p></o:p> >>>> C<o:p></o:p> >>>> I6<o:p></o:p> >>>> Mn0%3D%7C0%7C%7C%7C&sdata=Y5j98PfqxzkN%2B2UYI6E5kDMJLYj1qlHRc64sClc<o:p></o:p> >>>> Z<o:p></o:p> >>>> Fa<o:p></o:p> >>>> U%3D&reserved=0<o:p></o:p> >>>> Unsubscribe:<o:p></o:p> >>>> <a href="https://list/">https://list/</a><o:p></o:p> >>>> s.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fregistry-ripe%25<o:p></o:p> >>>> 4<o:p></o:p> >>>> 0r<o:p></o:p> >>>> esilans.se&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C3dec1d1<o:p></o:p> >>>> 7<o:p></o:p> >>>> e9<o:p></o:p> >>>> f54232d88c08dc5a18264a%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7<o:p></o:p> >>>> C<o:p></o:p> >>>> 63<o:p></o:p> >>>> 8484307004109226%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj<o:p></o:p> >>>> o<o:p></o:p> >>>> iV<o:p></o:p> >>>> 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=%2FLi%2BQE<o:p></o:p> >>>> H<o:p></o:p> >>>> dR<o:p></o:p> >>>> thZtiNdR7ETMPAkPAzVevDnMjvq75F3kf8%3D&reserved=0<o:p></o:p> >>>><o:p> </o:p> >>>><o:p> </o:p> >>>> _______________________________________________<o:p></o:p> >>>> members-discuss mailing list<o:p></o:p> >>>> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >>>> <a href="https://list/">https://list/</a><o:p></o:p> >>>> s.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEv<o:p></o:p> >>>> g<o:p></o:p> >>>> en<o:p></o:p> >>>> iy.Brodskiy%40kyivstar.net%7C3dec1d17e9f54232d88c08dc5a18264a%7Cf8f<o:p></o:p> >>>> 9<o:p></o:p> >>>> bd<o:p></o:p> >>>> 573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484307004115782%7CUnknown%7<o:p></o:p> >>>> C<o:p></o:p> >>>> TW<o:p></o:p> >>>> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV<o:p></o:p> >>>> C<o:p></o:p> >>>> I6<o:p></o:p> >>>> Mn0%3D%7C0%7C%7C%7C&sdata=vY2oba0wvj08c6W4f%2FFaPi6BRvFFLM7AbIf5i84<o:p></o:p> >>>> q<o:p></o:p> >>>> T6<o:p></o:p> >>>> s%3D&reserved=0<o:p></o:p> >>>> Unsubscribe:<o:p></o:p> >>>> <a href="https://list/">https://list/</a><o:p></o:p> >>>> s.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fadmin%2540roskom<o:p></o:p> >>>> n<o:p></o:p> >>>> ad<o:p></o:p> >>>> zor.io&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C3dec1d17e9f<o:p></o:p> >>>> 5<o:p></o:p> >>>> 42<o:p></o:p> >>>> 32d88c08dc5a18264a%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C638<o:p></o:p> >>>> 4<o:p></o:p> >>>> 84<o:p></o:p> >>>> 307004121940%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2<o:p></o:p> >>>> l<o:p></o:p> >>>> uM<o:p></o:p> >>>> zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=NlQ4MnUaG53yS1<o:p></o:p> >>>> e<o:p></o:p> >>>> KO<o:p></o:p> >>>> %2F2nhgAkG8yzbN7B3c4koumTvKw%3D&reserved=0<o:p></o:p> >>>><o:p> </o:p> >>> _______________________________________________<o:p></o:p> >>> members-discuss mailing list<o:p></o:p> >>> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >>> <a href="https://lis/">https://lis/</a><o:p></o:p> >>> ts.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEv<o:p></o:p> >>> g <o:p></o:p> >>> eniy.Brodskiy%40kyivstar.net%7C036de29fd4c449fcd1b208dc5a247e27%7Cf8<o:p></o:p> >>> f <o:p></o:p> >>> 9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484360917598516%7CUnknown<o:p></o:p> >>> % <o:p></o:p> >>> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC<o:p></o:p> >>> J<o:p></o:p> >>> XVCI6Mn0%3D%7C40000%7C%7C%7C&sdata=h8OUQ%2BQLt8n53JXrMFkAiZuFP3cavME<o:p></o:p> >>> 5<o:p></o:p> >>> kM9qBisBW%2BQ%3D&reserved=0<o:p></o:p> >>> Unsubscribe:<o:p></o:p> >>> <a href="https://lis/">https://lis/</a><o:p></o:p> >>> ts.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fevgeniy.brodskiy<o:p></o:p> >>> %<o:p></o:p> >>> 2540kyivstar.net&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C03<o:p></o:p> >>> 6 <o:p></o:p> >>> de29fd4c449fcd1b208dc5a247e27%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0<o:p></o:p> >>> % <o:p></o:p> >>> 7C0%7C638484360917604995%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA<o:p></o:p> >>> i <o:p></o:p> >>> LCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C40000%7C%7C%7C&sdat<o:p></o:p> >>> a<o:p></o:p> >>> =iEicBVrkwWvrsraRO8YcAbgVPRjrwBbKOgs83cbmD4g%3D&reserved=0<o:p></o:p> >> _______________________________________________<o:p></o:p> >> members-discuss mailing list<o:p></o:p> >> <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> >> <a href="https://list/">https://list/</a><o:p></o:p> >> s.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEvge<o:p></o:p> >> n <o:p></o:p> >> iy.Brodskiy%40kyivstar.net%7C036de29fd4c449fcd1b208dc5a247e27%7Cf8f9b<o:p></o:p> >> d <o:p></o:p> >> 573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484360917611662%7CUnknown%7CT<o:p></o:p> >> W<o:p></o:p> >> FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI<o:p></o:p> >> 6<o:p></o:p> >> Mn0%3D%7C40000%7C%7C%7C&sdata=kK98VCUHMtAXysvAhUKfUQ01r9rVB9c7GqCLDF8<o:p></o:p> >> 6<o:p></o:p> >> 7p0%3D&reserved=0<o:p></o:p> >> Unsubscribe:<o:p></o:p> >> <a href="https://list/">https://list/</a><o:p></o:p> >> s.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fmihail%2540fedorov.<o:p></o:p> >> net&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7C036de29fd4c449fc<o:p></o:p> >> d<o:p></o:p> >> 1b208dc5a247e27%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%7C63848436<o:p></o:p> >> 0 <o:p></o:p> >> 917617941%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI<o:p></o:p> >> i <o:p></o:p> >> LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C40000%7C%7C%7C&sdata=mSWgo9qeSONeXCJ<o:p></o:p> >> p<o:p></o:p> >> c%2B9FYeqeMXclGVYzC9oTd5F%2BBb8%3D&reserved=0<o:p></o:p> ><o:p> </o:p> > _______________________________________________<o:p></o:p> > members-discuss mailing list<o:p></o:p> > <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> > <a href="https://list/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist</a><o:p></o:p> > s.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEvgen<o:p></o:p> > iy.Brodskiy%40kyivstar.net%7Ca1abc79f92b648a3c3e408dc5a31a7ef%7Cf8f9bd<o:p></o:p> > 573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484416574916796%7CUnknown%7CTW<o:p></o:p> > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6<o:p></o:p> > Mn0%3D%7C0%7C%7C%7C&sdata=e%2BcMjsT6CPBRzISFcOKZg01iXhNqtLv%2BVe0dVZL5<o:p></o:p> > 6uI%3D&reserved=0<o:p></o:p> > Unsubscribe: <o:p></o:p> > <a href="https://list/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist</a><o:p></o:p> > s.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fevgeniy.brodskiy%25<o:p></o:p> > 40kyivstar.net&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7Ca1abc7<o:p></o:p> > 9f92b648a3c3e408dc5a31a7ef%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0%<o:p></o:p> > 7C638484416574924555%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI<o:p></o:p> > joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=gcSFlj7HP<o:p></o:p> > qYWxjVy8fnMJWbtlE4MaEsW4anvXILtR8M%3D&reserved=0<o:p></o:p> > _______________________________________________<o:p></o:p> > members-discuss mailing list<o:p></o:p> > <a href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a><o:p></o:p> > <a href="https://list/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist</a><o:p></o:p> > s.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7CEvgen<o:p></o:p> > iy.Brodskiy%40kyivstar.net%7Ca1abc79f92b648a3c3e408dc5a31a7ef%7Cf8f9bd<o:p></o:p> > 573bba4300a6ec3b8e70a30986%7C0%7C0%7C638484416574932085%7CUnknown%7CTW<o:p></o:p> > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6<o:p></o:p> > Mn0%3D%7C0%7C%7C%7C&sdata=lE%2F2jb%2B%2BIiVDZRF0PJqJm%2FY2AxshNYyWmw4q<o:p></o:p> > gyxtXHI%3D&reserved=0<o:p></o:p> > Unsubscribe: <o:p></o:p> > <a href="https://list/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist</a><o:p></o:p> > s.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fripe-members%2540se<o:p></o:p> > bastian-graf.at&data=05%7C02%7CEvgeniy.Brodskiy%40kyivstar.net%7Ca1abc<o:p></o:p> > 79f92b648a3c3e408dc5a31a7ef%7Cf8f9bd573bba4300a6ec3b8e70a30986%7C0%7C0<o:p></o:p> > %7C638484416574938524%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ<o:p></o:p> > IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=DymXbTBY<o:p></o:p> > Wceq%2BF69YSjN2OLa%2BKAHVEuaYoUVTnYmT7A%3D&reserved=0<o:p></o:p> </div> </div> </body> </html>