<html><head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> </head> <body> Ladies and Gentlemen, it's time to put on your tinfoil hats. /s "Scheme" (Noun): a secret or underhand plan; a plot. Imagine your government needs to increase it's budget and it does so by increasing the lower tax band rate while leaving the higher tax band rate untouched. The people with the lowest incomes pay the majority of the extra tax - it hurts those feel it, most. That is exactly what charging scheme A is. It is a step in the right direction, but unfair and unjust - to make it an unpopular option to vote for. How else would you deter a vote for pay-per-resource? I mean well done, it's absolute genius. This time next year, it will be again asked my many... "why don't the large ISPs with millions of IPv4 that they don't use, pay the same as me?" and the response will be "we tried to vote for a pay-per-resource, but it failed". If you will be paying more for Scheme A, I really do believe that it is fair - perhaps not this year, but next year we could push the large ISPs to pay a higher share. If we had seen this on the current proposed scheme, it would be a lot more attractive to many. Regardless of if you believe IPv4 will be returned to the pool or not, it's a case of supply and demand. It will work itself out. If you can shave a few thousand in fees per year by selling a couple of /24 blocks, why not. That will drive down the market price naturally. That won't happen much with a cap of ~8k per year in fees, but perhaps eventually the cap for IPv4 will be more and more. Regards, Josh Jameson <div class="moz-cite-prefix">On 5/25/23 21:58, Kaj Niemi wrote: </div> <blockquote type="cite" cite="mid:AM7P194MB0756C617C87ABF31C5C3871ECB469@AM7P194MB0756.EURP194.PROD.OUTLOOK.COM"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <div dir="ltr"> <div style=""> <div> <div dir="ltr"> <div>Not to rehash the issues with charging scheme A since plenty has been written but here are some thoughts about the whole thing</div> <div dir="ltr"> <ul> <li>it certainly favors the large LIRs as there is a cap set on purpose for charges as has been mentioned on this list but also during the GM presentation yesterday</li> <li>it favors the very small LIRs as they would pay significantly less than the average cost it takes to cover the NCC’s services</li> <li>it doesn't favor the LIRs that made RIPE NCC what it is today or pretty much everyone who had an initial allocation larger than /22</li> <li>based on the GM presentations the previous lines will continue also in the near future (yes, yes, the members can vote and all those disclaimers apply)</li> </ul> <div dir="ltr"> Now, regarding the issue with returning addresses</div> <div dir="ltr"> <ul style="text-decoration: none; color: rgb(0, 0, 0);"> <li>While I don’t have quantitative data, I doubt anything will increase address returns in a significant way</li> <li>there is a working second hand market with buyers, sellers and brokers that seems efficient</li> <li>why return when “everyone” gets 4-6 mails per day from various people who want to buy or lease your blocks?</li> <li>the street price for a /24 is 10k+ - if you do the math you offset the exorbitant RIPE NCC fees for several years and cash today is better than a promise of cash in the future ;)</li> <li>On the other hand, if you keep your ipv4 addresses they should be on your balance sheet as intangibles since they have value</li> <li>If you buy addresses, they're a legal business expense enabling you to amortize them over longer periods of time. This is great as it lowers your tax liability by reducing earnings before tax (EBT)</li> </ul> </div> <div dir="ltr">(certainly not financial advise)</div> <div dir="ltr"> </div> <div dir="ltr">:)</div> <div dir="ltr"> </div> <div dir="ltr"> </div> </div> </div> </div> <div id="ms-outlook-mobile-signature"> <div> </div> <div dir="ltr"> <div dir="ltr">Kaj</div> <div dir="ltr"> </div> <div dir="ltr">Sent from my iPad</div> <div dir="ltr"> </div> </div> </div> <div id="mail-editor-reference-message-container" class="ms-outlook-mobile-reference-message"> <hr style="display:inline-block;width:98%" tabindex="-1"/> <div id="divRplyFwdMsg" dir="ltr">From: <a class="moz-txt-link-abbreviated" href="mailto:sdy@a-n-t.ru">sdy@a-n-t.ru</a> <a class="moz-txt-link-rfc2396E" href="mailto:sdy@a-n-t.ru"><sdy@a-n-t.ru></a> Sent: Thursday, May 25, 2023 10:56 PM To: Kaj Niemi <a class="moz-txt-link-rfc2396E" href="mailto:kajtzu@basen.net"><kajtzu@basen.net></a> Cc: Skyline Telecom <a class="moz-txt-link-rfc2396E" href="mailto:skylinetelecom@outlook.com"><skylinetelecom@outlook.com></a>; Josh Jameson <a class="moz-txt-link-rfc2396E" href="mailto:josh@servebyte.com"><josh@servebyte.com></a>; <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:members-discuss@ripe.net"><members-discuss@ripe.net></a> Subject: Re: [members-discuss] Response to Comments on the Charging Scheme Proposals <div> </div> </div> <meta name="Generator" content="Microsoft Exchange Server"/>  <div class="PlainText">The problem is that the scheme with categories transfers the load to those who do not have so many resources and they usually need them. It is very profitable for large address holders. It does not encourage the return of resources, but it will allow them to say - look, we pay more than others. Moreover, the scheme with categories does not contribute to the return of unused addresses. If I have 15,000 addresses, then it makes no sense to return 1000 unnecessary ones! Because I will still pay the same amount. Therefore, a fee should be charged for each subnet /24. This is the only way to encourage the return of unused ones. And the price should rise - this will force you to switch to IPV6. Serbulov Dmitry > Arguably charging scheme A is certainly per resource. The alternatives > given for ASNs and xfer fees ditto. You end up with an a la carte meal > instead of a flat-fee buffet. > > > > Kaj > ________________________________ > From: members-discuss <a class="moz-txt-link-rfc2396E" href="mailto:members-discuss-bounces@ripe.net"><members-discuss-bounces@ripe.net></a> on behalf of > Skyline Telecom <a class="moz-txt-link-rfc2396E" href="mailto:Skylinetelecom@outlook.com"><Skylinetelecom@outlook.com></a> > Sent: Wednesday, May 24, 2023 17:23 > To: Josh Jameson <a class="moz-txt-link-rfc2396E" href="mailto:josh@servebyte.com"><josh@servebyte.com></a>; <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> > <a class="moz-txt-link-rfc2396E" href="mailto:members-discuss@ripe.net"><members-discuss@ripe.net></a> > Subject: Re: [members-discuss] Response to Comments on the Charging Scheme > Proposals > > Hi, > > A per resource charging scheme has been rejected many years ago because > that type of charging would force RIPE to become a for profit organization > - from the dutch government / fiscal point of view. It was a lenghty > discussion and the consensus was that RIPE must remain a not-for-profit > organization. > > Silviu > > ________________________________ > From: members-discuss <a class="moz-txt-link-rfc2396E" href="mailto:members-discuss-bounces@ripe.net"><members-discuss-bounces@ripe.net></a> on behalf of Josh > Jameson <a class="moz-txt-link-rfc2396E" href="mailto:josh@servebyte.com"><josh@servebyte.com></a> > Sent: Wednesday, May 24, 2023 2:08:31 PM > To: <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> <a class="moz-txt-link-rfc2396E" href="mailto:members-discuss@ripe.net"><members-discuss@ripe.net></a> > Subject: Re: [members-discuss] Response to Comments on the Charging Scheme > Proposals > > The deadline for members to propose resolutions was 10th May. > Unfortunately RIPE ignored the elephant in the room that showed the most > activity in members-discuss, which was pay-per-ipv4 - like some other > RIRs currently operate. > > They are so confident that it is not something people will vote for, > that they refused to include it as an option, despite it providing RIPE > with the most funding of any other option. > > If RIPE was not a monopoly in our region, I would go elsewhere. To say I > am disgusted with the behavior is a gross understatement. > > Regards, > Josh Jameson > > On 5/19/23 15:00, <a class="moz-txt-link-abbreviated" href="mailto:sdy@a-n-t.ru">sdy@a-n-t.ru</a> wrote: >> Dear Simon-Jan, >> >> Until the fee for one resource becomes the same for everyone, we will >> look >> for a way to distribute and pay for IPv4 resources indefinitely. >> If we don't have enough resources now, it doesn't matter how someone has >> 1 >> billion addresses for some reason. If they need them, they MUST to pay >> like everyone else! >> >> I do not understand why the NCC do not offer to vote a scheme: 1 IP for >> everyone = one price for everyone !!!??? Are there any reasons? They do >> not want to pay for these addresses? OK! Somebody else will take it and >> will be pay in happy. >> >> Dmitry Serbulov. >> >>> Dear all, >>> >>> I’d like to answer the comments and questions that have been raised >>> since the Board Treasurer announced the final proposed charging scheme >>> options. >>> >>> See Raymond’s mail announcing the options at: >>> <a href="https://www.ripe.net/ripe/mail/archives/ncc-announce/2023-April/001645.html" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fripe%2Fmail%2Farchives%2Fncc-announce%2F2023-April%2F001645.html&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QHQ37GMqcgOBdu9yE75mXvdxWILjVXz4fRxZYZjDQuI%3D&reserved=0</a> >>> >>> Also see my colleague Fergal’s mail explaining the instant run-off >>> voting method and how it will work with the charging scheme vote: >>> <a href="https://www.ripe.net/ripe/mail/archives/ncc-announce/2023-May/001647.html" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fripe%2Fmail%2Farchives%2Fncc-announce%2F2023-May%2F001647.html&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=h9pBZUu%2B14nme%2Ft2A6WYBFQDiKE4GBwd2iNxE2vIfpY%3D&reserved=0</a> >>> >>> Purpose of the Charging Scheme and Budget >>> >>> The charging scheme is the mechanism the RIPE NCC uses to ensure it >>> collects sufficient funds to carry out its promises to the members in >>> future years. As a safeguard, any excess (or shortage) of funds is >>> subject to a redistribution vote by the General Meeting. This >>> redistribution has happened many times in the past. This ensures that >>> the RIPE NCC operates on a cost-recovery basis, or in other words >>> operates as a not-for-profit. >>> >>> The Charging Scheme does not define the cost budget of the RIPE NCC, >>> but >>> of course there is a relation between the two. The projected income >>> does >>> at the very least provide direction regarding discussion on the >>> Activity >>> Plan and Budget. >>> >>> The Activity Plan and Budget defines the planned activities and >>> associated costs for a financial year. And for the longer term, we have >>> developed a five-year strategy. Both of these documents are published >>> for the members to provide input on, and they are then approved by the >>> RIPE NCC Executive Board. >>> >>> The Draft Activity Plan and Budget is published on a yearly basis every >>> autumn, specifically to consult with our membership. Additionally, this >>> year there is the option to provide input and feedback via the RIPE NCC >>> Survey 2023, which will launch next week. The Activity Plan and Budget >>> is effectively the RIPE NCC’s promise to its members in terms of what >>> it >>> will do and how much it will spend in the coming year. >>> >>> The most recently approved Activity Plan and Budget (in this case 2023) >>> forms the basis for projections of the required income for the >>> following >>> financial year, as this is the most recent approved “promise to our >>> members”. All charging scheme projections are made with this promise in >>> mind, to ensure sufficient income to continue that promise. If the >>> Activity Plan and Budget 2024 requires us to cut or add activities or >>> costs, then that is what we will do to fulfill our promise. >>> >>> That being said, efficient and effective use of membership funds is a >>> priority and will remain a priority of the Executive Board and the >>> management of the RIPE NCC. >>> >>> Why Change the Current Model? >>> >>> We need to ensure sufficient and sustainable income to continue our >>> operations in a stable and predictable manner. The high market value of >>> IPv4 resources combined with the possibility of multiple LIR accounts >>> per member has created uncertainty and unpredictability for a >>> significant part of our income. A member-based model rather than an LIR >>> account model will help to reduce this uncertainty by removing the LIR >>> account as the basis for the charging scheme. >>> >>> We are also addressing the stated unfairness in the current model. >>> Although some members have expressed the desire for increased >>> differentiation, we see the proposed change as a significant difference >>> from the current one LIR-one fee model. It allows us to spread the >>> funding burden differently because in the current model, all members >>> with one LIR account pay the same fee (exception is the independent >>> resources). Due to a significant inflow of New LIRs in 2019 and 2021, >>> there is a considerable amount of members who hold more than one LIR >>> account, and these members do pay additional LIR account fees. One of >>> the major benefits of the category model is that it charges per member, >>> and with that it reduces the uncertainty caused by multiple LIRs and >>> the >>> associated consolidation risk. >>> >>> We aim to achieve a clearer distinction between RIPE Policy and the >>> RIPE >>> NCC Charging Scheme by removing the LIR account as the basis of the >>> charging scheme. >>> >>> And we want to ensure that the RIPE NCC together with its members is >>> ready for any change the future might bring, by increasing the >>> possibilities the charging scheme provides to adapt for this change. Of >>> course, this can only happen with formal approval by the GM. >>> >>> The Category Model >>> >>> Under this model, the categories would apply as soon as a member holds >>> IPv4 or IPv6 resources as defined in the charging scheme document. >>> Limits as defined in the charging scheme document are the upper limits >>> of the categories. The lower limit for Category 1 is one resource (one >>> IPv4 address or one IPv6 address). The base category applies to all, >>> including members with no IPv4 or IPv6 resources. >>> We have been asked why there is not a per-IPv4 address model, with >>> comments that the category model favours bigger members. In a way, it >>> does, but less so than in the one-LIR account, one-fee model. We also >>> need to stay true to the fact that we are a membership association, so >>> while we can differentiate between members, this needs to stay within >>> reason. >>> >>> Additionally, we need to ensure the independence of the RIPE NCC by not >>> becoming too dependent on a small subset of our membership for a >>> significant part of our income. Furthermore, protecting the one >>> member-one vote principle could become significantly more difficult if >>> the contribution differences become extreme. So we can facilitate >>> differentiation between members in size of contribution, especially >>> compared to the current model we have, but it is essential that this >>> stays within reason. One clear benefit of the category model is that we >>> can refine it over time, working towards a model that is acceptable for >>> more members. >>> >>> On the pricing and category limits, they have been set with the latest >>> Activity Plan and Budget in mind, to ensure at the very least that we >>> can continue with our promise to members in 2024. If the Activity Plan >>> and Budget 2024 requires the RIPE NCC to reduce or add activities or >>> costs, we will act accordingly. >>> >>> Regarding the options presented for voting, our initial plan was to >>> submit two charging schemes for a vote, to provide a clear choice to >>> the >>> members on a category-based model or the current model. Both of these >>> models would provide income at the level of the 2023 budget if we apply >>> a correction for expected inflation of 5%, resulting in a projected >>> income of EUR 42 million. >>> >>> After feedback from members we wanted to ensure the GM could vote for >>> “NO CHANGE” which is represented in Option D. Additionally to this “NO >>> CHANGE” vote, I personally requested to add a vote to keep the income >>> (before any correction for inflation) at the same level as in 2023, >>> which is the reason Option C has been added. The 2nd or 3rd vote on >>> charging for ASN assignments and/or transfers would (if approved) >>> provide additional income over that provided by the charging scheme >>> voted for by members. >>> >>> The Waiting List >>> >>> The current situation regarding the IPv4 waiting list and costs >>> associated with a /24 IPv4 allocation is in our eyes an undesirable >>> one. >>> With the uncertainty of the waiting period (around 1.5 to 2 years) >>> which >>> can be shorter or longer, plus the two-year “non-transfer” policy, it >>> means unpredictable costs for our members and income that is not >>> transparent for the RIPE NCC. >>> - Two-year waiting period = sign-up fee plus two years LIR service fee >>> = >>> 4,100 EUR >>> - Two-year “non-transfer” policy = two years LIR service fee = 3,100 >>> EUR >>> - Indicative price 7,200 EUR >>> >>> To address this, we propose a one-time join-the-waiting list fee, and a >>> to-be-determined /24 IPv4 allocation fee. This would replace costs that >>> apply to members based on being on the waiting list for a long time >>> without receiving resources, as members would be charged the waiting >>> list fee upon placement on the waiting list, and the allocation fee >>> only >>> just before resources are allocated (with the opportunity to reject the >>> resources). >>> >>> This is, in our opinion, a fairer way to charge for these resources. To >>> define this charge and work out any possible issues with RIPE Policy, >>> we >>> are postponing this vote to allow for consultation with the membership >>> because this to-be-determined fee will have an effect on who applies >>> for >>> the resources. We also need to consider fees already paid by LIR >>> accounts, and whether a discount would be in order for fees already >>> paid >>> in relation to specific IPv4 allocations. And for this, time is needed >>> to consult with membership. >>> >>> Additionally, this fee will also result in additional income for the >>> RIPE NCC, which will be subject to a redistribution vote, assuming this >>> provides excess funds. >>> >>> See the original announcement on the waiting list freeze: >>> <a href="https://www.ripe.net/ripe/mail/archives/ncc-announce/2023-April/001643.html" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fripe%2Fmail%2Farchives%2Fncc-announce%2F2023-April%2F001643.html&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GOuQKQV%2BlIefaClZDayqozCzARGlmqet2zdeJpCdiqc%3D&reserved=0</a> >>> >>> Finally, there are probably more questions and comments than I have >>> answered here. But we are preparing for the General Meeting (GM) next >>> week where there will be several presentations from our side on the >>> charging and budgeting of the RIPE NCC. Our Managing Director will >>> present at both the NCC Services Working Group on the past and future >>> of >>> the RIPE NCC, and he will present a more detailed presentation on >>> budget >>> developments in the GM. I will also present on the Charging Scheme >>> options as well as give an update on our current financial situation. >>> >>> I hope you will register to join and follow these presentations, and >>> you >>> will have the opportunity to further ask questions and discuss the >>> various options to vote on. >>> >>> <a href="https://www.ripe.net/participate/meetings/gm/meetings/may-2023" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fparticipate%2Fmeetings%2Fgm%2Fmeetings%2Fmay-2023&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=XzmuC2hQQOh%2F3ztqkl%2BT%2FtCs0aYvaTDVbmmEkdry7Rw%3D&reserved=0</a> >>> >>> Kind regards, >>> >>> Simon-Jan Haytink >>> Chief Financial Officer >>> RIPE NCC >>> >>> _______________________________________________ >>> members-discuss mailing list >>> <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> >>> <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" style="" moz-do-not-send="true">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tvPBquQqZ1Z8NpD66W0fXIs%2FqQmpXf4SyMTHVxf6Ay8%3D&reserved=0</a> >>> Unsubscribe: >>> <a href="https://lists.ripe.net/mailman/options/members-discuss/sdy%40a-n-t.ru" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fsdy%2540a-n-t.ru&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0zo0yJzjTi1cmwrjeywZaJYLVWWBbCyK26zZICs4sB4%3D&reserved=0</a> >>> >> >> >> >> _______________________________________________ >> members-discuss mailing list >> <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> >> <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" style="" moz-do-not-send="true">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tvPBquQqZ1Z8NpD66W0fXIs%2FqQmpXf4SyMTHVxf6Ay8%3D&reserved=0</a> >> Unsubscribe: >> <a href="https://lists.ripe.net/mailman/options/members-discuss/josh%40servebyte.com" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fjosh%2540servebyte.com&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nnEgU3m67iVYzYv6yY464B9vcIEjLnRiV0L24RkfQvY%3D&reserved=0</a> > > > _______________________________________________ > members-discuss mailing list > <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" style="" moz-do-not-send="true">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tvPBquQqZ1Z8NpD66W0fXIs%2FqQmpXf4SyMTHVxf6Ay8%3D&reserved=0</a> > Unsubscribe: > <a href="https://lists.ripe.net/mailman/options/members-discuss/skylinetelecom%40outlook.com" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fskylinetelecom%2540outlook.com&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=b3mxs5a7IehG8KiwZuNi%2B2sScQKbGcKPMo3qXUylOzc%3D&reserved=0</a> > _______________________________________________ > members-discuss mailing list > <a class="moz-txt-link-abbreviated" href="mailto:members-discuss@ripe.net">members-discuss@ripe.net</a> > <a href="https://lists.ripe.net/mailman/listinfo/members-discuss" style="" moz-do-not-send="true">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=tvPBquQqZ1Z8NpD66W0fXIs%2FqQmpXf4SyMTHVxf6Ay8%3D&reserved=0</a> > Unsubscribe: > <a href="https://lists.ripe.net/mailman/options/members-discuss/sdy%40a-n-t.ru" style="" moz-do-not-send="true"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fsdy%2540a-n-t.ru&data=05%7C01%7C%7C295b298c24814178a8f008db5d5a1d45%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638206413875471569%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0zo0yJzjTi1cmwrjeywZaJYLVWWBbCyK26zZICs4sB4%3D&reserved=0</a> > </div> </div> </div> </div> </blockquote> </body></html>