<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> </head> <body> <div dir="ltr"> <div dir="ltr">I think it’s great we are being creative with the ideation of the models but… </div> <div dir="ltr"><br> </div> <div dir="ltr">Fair is a very vague yet complicated concept. Here I agree with Nick ;)</div> <div dir="ltr"><br> </div> <div dir="ltr"><span style="text-decoration: none; display: inline !important; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">Distribution in the past has been needs based (based on existing or projected need). It's done.</span><br> </div> <div dir="ltr"><span style="text-decoration: none; display: inline !important; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"><br> </span></div> <div dir="ltr">Any real implementation of forcing a "fair re-redistribution" of <i> RIR assigned resources</i>, as you suggest, will lead in lawsuits. Whether it would be 1, 10 or 1000 doesn't matter. The association will not have the financial resources and time to handle those. Probably not the best use of LIR fees, either. I doubt anyone in legal would ever ACK this.</div> <div dir="ltr"><br> </div> <div dir="ltr">Any of the companies holding address space that RIPE-639 refers to might not have an interest, or even be aware of the "benefits" of being a RIPE LIR themselves. Yes, they don't know about RPKI either, usually. Legacy reverse DNS might be enough. Many of these are multinationals in non-tech sectors who have gotten addresses before the RIR system existed. <span style="text-decoration: none; display: inline !important; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);"> Some of these got addresses around the time classless routing came along from their vendors who themselves had gotten the addresses from IANA just by asking.<span class="Apple-converted-space"> </span></span>Some of these do not route the addresses on the internet, some others do, etc. etc. Again, ruining someone's day by "reclaiming" - let's call it what it really is, hijacking - address space <i>that hasn't been RIR assigned</i> will certainly lead to costly lawsuits and claims of damages as above.</div> <div dir="ltr"><br> </div> <div dir="ltr">Don't think a "Pigouvian tax" would work either as the alternative is always for the holder to sell or rent the addresses. I think it'll lead to more consolidation of addresses to the cloud providers. Probably again not what was intended originally. Any added cost would eventually be shifted to the customers one way or another. Apropos that, Cogent is raising a 200M note secured by a bunch of IPv4 addresses and rental cash flows. Addresses have a significant value as collateral just as stable cash flows do.<span></span></div> <div dir="ltr"><br> </div> <div dir="ltr"><br> </div> <div dir="ltr">:)</div> <div dir="ltr"><br> </div> <div dir="ltr"><br> </div> <div id="ms-outlook-mobile-signature"> <div><br> </div> <div dir="ltr"> <div dir="ltr">Kaj</div> <div dir="ltr"><br> </div> <div dir="ltr">Sent from my iPad</div> <div dir="ltr"><br> </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"><font face="Calibri, sans-serif"><b>From:</b> members-discuss <members-discuss-bounces@ripe.net> on behalf of ivaylo <ivaylo@bglans.net><br> <b>Sent:</b> Friday, April 26, 2024 9:26 PM<br> <b>To:</b> Massimiliano Stucchi <max@stucchi.ch><br> <b>Cc:</b> members-discuss@ripe.net <members-discuss@ripe.net><br> <b>Subject:</b> Re: [members-discuss] GM topic <div> </div> </font></div> <meta name="Generator" content="Microsoft Exchange Server"> <font size="2"><span style="font-size:11pt;"> <div class="PlainText"><br> Thank you for this example Massimiliano !<br> <br> It is very good example how bad the resources can be used, and how bad is <br> to have flat fee for all members ! That's why RIPE fee _MUST_ include per <br> resource component.<br> <br> I am currious about technical aspects in the logic, Even if you go <br> with EUI-64 standart for your network infrastructure (nobody do this, <br> because the addresses unprediction) a /29 IPV6 will let you have 34 358 <br> 689 800 ( > 34 Bilions segments). With the maximum ttl value of 255 <br> (limited by the one byte in the header, current around the internet is <br> used just 64), You can have 134 739 960 (> 134 millions) router <br> interfaces. With the modern switching asics, you will need and around <br> 144 000 000 000 000 (> 144 trillions) ethernet switches where you can <br> connect up to 18446744073709551616 end hosts per segment. Let me also <br> remind that IPV6 protocol allow to use a single (just one) adress per a <br> system/ruter/host (not per interface as IPV4) implemented in almost all <br> vendors equipment and OS.<br> <br> Yes in theory it is posible to need huge address space, but in theory <br> every one of us (LIRs) have to drawn all ipv6 + ipv4 + ASN from IANA (not <br> from RIPE only) to cover all very unlikely future needs.<br> <br> -----<br> <br> The problems RIPE NCC and we members have, is not the charging scheme is <br> fair or unfair, the root of the problem is _UNFAIR RESROURCES <br> DISTRIBUTION_ during the years. As everything in the real world internet <br> resources are also finite numbers. So how to spread finite resources to <br> group of members which by presumptions are equal (First and most <br> important RIPE obligation - threat all members equally) ? Logically - <br> equal. If we were 5 members maybe we can handshake each other and have an <br> agreement (not sure ether when we talk about concurent companies / <br> personals), but we are 21k that's why we need clear, transparent and <br> strong rules equal to all. We currently have a strong discrimination based <br> on very vague foundations and rules.<br> <br> I will be very happy somebody from RIPE to explain us, why one member can <br> hold /8 just for fun (or testing or whatever), in the same time other <br> member to have single /24 (or to be in a waiting queues) extreamly <br> dificult to operate its bussiness because lack of resources and both of <br> them to be forced to pay same fee. Which rule in the RIPE founding <br> agreement exactly says this is fair and equal ? Also how many from the <br> RIPE NCC staff and you LIRs, with hand on heart will tell the current <br> situation is moral, normal and fair to all ?<br> <br> In all cases after the posible delegated resources to RIPE have limits we <br> also need limits for the resource each of us can hold and operate with. <br> thing more fair can be than to take all resources in each category <br> (IPV4/IPV6/ASN) which are delegated to RIPENCC and divide by the LIR <br> members number.<br> <br> <br> Solution one:<br> Redistribute resources equaly to all. Not imposible as I already wrote, <br> but will that lead to tremors in the work of operators - very likely. But <br> what is that is equal fees, equal rights, equal resources.<br> <br> Solution two:<br> Start to "penalise" the the LIRs which holds and operate resources over <br> the fair share limits. That will not make disruption of the internet work <br> in the region. And will give time to those who want to optimise the <br> resource usage to do it and save expenses. How to do it ? - With money <br> ofcourse. To prevent adding too much initial stress to all, we have to <br> start with small steps and calibrate the "penalisation" fee with time.<br> <br> As I wrote in my previous mail the current fair shair resources for each <br> LIR member based on what I checked (by IANA documents and 21500 LIRs) are:<br> <br> 1 x /18 IPV4 block<br> 1 x /28 IPV6 block<br> 16 x ASN<br> <br> Everything above these numbers should be "penalise" with a small fee per <br> each resource over the limit. Ofcourse these limits must be shifted if <br> we become 40k members or down to 10k, but it is an easy part. Also <br> "penalty" fee by 10 euro per year for /24, /32, ASN looks prety resonable <br> in the light of current free market prices - 15k "buy" / 100 euro month <br> rent.<br> <br> It is not a category based charging scheme ! <br> It is fair share charging scheme !<br> Can be looked at like extension of the scheme C, but guarantee much more <br> RIPE NCC sustainable future and covers all LIR resources (not only PI). <br> Current offered option C is inanity, because one LIR can hold /8 PA and <br> none PI space, the other can hold single /24 PA and 10 x /24 PI, and will <br> pay much more than the first one with /8 PA (fair ?) !<br> <br> <br> Another important theme is RIPE-639. 10 Years after the adoption we still <br> have nearly 34% undiscovered resources. How much more time it needs ? If <br> for 10 years you cant find legacy holders what will be the chance to do <br> it in the next 10 or 100 years ? We need a straight deadline to point <br> 2.6. I think RIPE NCC can safely suspend (not delete) all records for <br> these 34% resources. It is good to put dummy records to point to call or <br> email to RIPE support staff, and these resource to be gobaly announce. If <br> nobody call in few (3) mounths, can be consider free and can be drawn into <br> the pool.<br> <br> <br> <br> Ivaylo Josifov<br> VarnaIX / Varteh LTD<br> +359 52 969393<br> Varna, Bulgaria<br> <br> <br> On Fri, 26 Apr 2024, Massimiliano Stucchi wrote:<br> <br> ><br> > Hi,<br> ><br> > On 26.04.2024 16:40, Thibaud Perret wrote:<br> ><br> >> I have a question for Massimiliano, if he sees it:<br> >> Do you really need that many IPv6 addresses? Couldn't you just go with a <br> >> single<br> >> /40 allocation instead? That would still make a couple of /48 to be <br> >> announced<br> >> separately for you to keep your "lab allocation". If the answer is "yes" to <br> >> that<br> >> question, you could then pay well less in most if not all other RIR <br> >> regions.<br> ><br> > I could do with a much smaller allocation. At present, I'm announcing both <br> > /29s, with the first one being where my infrastructure is (and an address I'm <br> > writing this e-mail from), and the second /29 has been used for some research <br> > such as the one you can find here <br> > (<a href="https://labs.ripe.net/author/stucchimax/a-bgp-side-effect-of-rpki/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flabs.ripe.net%2Fauthor%2Fstucchimax%2Fa-bgp-side-effect-of-rpki%2F&data=05%7C02%7C%7C0b84b59374a24b82c60308dc661e588c%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638497527736209710%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C4000%7C%7C%7C&sdata=y2T5QV8Ea7AuXD4WBPSVxPxiuOcA80pYk7PGy8LHnyQ%3D&reserved=0</a>).<br> ><br> > The point of the article was to compare what a "normal" LIR would pay in the <br> > different RIRs. If I were to compare having a /48 (which would be PI at that <br> > point) I would be comparing two different things.<br> > Additionally, I wanted to showcase how some decision could be hindering <br> > Internet development, such as the one from LACNIC to charge so much for IPv6 <br> > compared to all the other RIRs, and the similar situation at APNIC, although <br> > to a lesser extent.<br> ><br> > To wrap this, could I do with a smaller allocation? Definitely. But I <br> > received a /29 as part of my membership and I can make some use of it. I <br> > could also live without a second /29, but that does not increase my <br> > membership fees. I would return it if the charging scheme were to be like <br> > APNIC or LACNIC.<br> ><br> > Ciao!<br> ><br> > -- <br> > Massimiliano Stucchi<br> > MS16801-RIPE<br> > <a href="https://stucchi.ch/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstucchi.ch%2F&data=05%7C02%7C%7C0b84b59374a24b82c60308dc661e588c%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638497527736218822%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C4000%7C%7C%7C&sdata=CCE0El%2F5B41Uiky2BkscGB%2Fb%2FnkIWS2tKh4KGwPNA%2F4%3D&reserved=0</a><br> ><br> <br> _______________________________________________<br> members-discuss mailing list<br> members-discuss@ripe.net<br> <a href="https://mailman.ripe.net/">https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fmembers-discuss&data=05%7C02%7C%7C0b84b59374a24b82c60308dc661e588c%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638497527736224712%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C4000%7C%7C%7C&sdata=AKpL%2FBU%2BGivvG9mSvj2oFyeYeLXVit3cGEBi0iHep9Y%3D&reserved=0</a><br> Unsubscribe: <a href="https://lists.ripe.net/mailman/options/members-discuss/kajtzu%40basen.net"> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Foptions%2Fmembers-discuss%2Fkajtzu%2540basen.net&data=05%7C02%7C%7C0b84b59374a24b82c60308dc661e588c%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638497527736228202%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C4000%7C%7C%7C&sdata=wGy%2BZKcmJxuRIwj9%2BTXb5a6zDlImgJ%2BgmCg51B4zlw8%3D&reserved=0</a><br> </div> </span></font></div> </div> </body> </html>