<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Personally, I would suggest to increase the 2-years-period if the resulting merged LIR contains prefixes from 2 merged LIRs or more</div><div class="">Example:</div><div class="">A (has a /24) and B (has one historical /22 and another /22 from a previous merger) wants to merge: they would need to wait 3 years.</div><div class="">Next time, It would be 4 years, etc…</div><div class=""><br class=""></div><div class="">Also, if several mergers with the same LIR are requested, I honestly don’t recall if this is allowed, but it should not: one merge per LIR per year.</div><div class=""><br class=""></div><div class="">That should block serial-mergers, but not regular small LIRs with a real network activity.</div><div class=""><br class=""></div>There are probably loop-holes in my idea, or it’s perhaps too complex to implement.<div class=""><br class=""><div class=""> <div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;"><div class="" style="orphans: 2; widows: 2;"><span class="Apple-style-span" style="color: rgb(0, 34, 243); font-family: "Helvetica Neue";"><font class="Apple-style-span" color="#1C00FF">David Ponzone<font class="Apple-style-span" face="Arial" size="2"> </font></font></span><span class="Apple-style-span" style="color: rgb(0, 34, 243); font-family: "Helvetica Neue";"><font class="Apple-style-span" color="#000000">Direction Technique</font></span></div><div class="" style="orphans: 2; widows: 2;"><div class="" style="font-family: Arial; font-size: 10px;"><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">email: <a href="mailto:david.ponzone@ipeva.fr" class="">david.ponzone@ipeva.fr</a></span></font></font></div><div class="" style="font-family: Arial; font-size: 10px;"><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">tel: 01 74 03 18 97</span></font></font></div><div class="" style="font-family: Arial; font-size: 10px;"><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">gsm: 06 66 98 76 34</span></font></font></div><div class="" style="color: rgb(0, 34, 243); font-family: Arial; font-size: 10px;"><font class="Apple-style-span" face="'Helvetica Neue'"><br class=""></font></div><div class="" style="color: rgb(0, 34, 243);"><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'">Service Client </font><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" color="#FF0000">IP</font></font><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'">eva</font></div><div class="" style="color: rgb(0, 34, 243); font-family: Arial; font-size: 10px;"><font class="Apple-style-span" color="#1C00FF" face="'Helvetica Neue'"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica;"><div class=""><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">tel: 0811 46 26 26</span></font></font></div><div class=""><font class="Apple-style-span" face="'Helvetica Neue'" size="3"><span class="Apple-style-span" style="font-size: 13px;"><div class="" style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Arial; color: rgb(0, 34, 243);"><span class="" style="text-decoration: underline;"><a href="blocked::http://www.ipeva.fr/" class="">www.ipeva.fr</a></span><span class="" style="color: rgb(101, 104, 149);"> - <span class="" style="color: rgb(0, 34, 243); text-decoration: underline;"><a href="blocked::http://www.ipeva-studio.com/" class="">www.ipeva-studio.com</a></span></span></div><div class="" style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Arial; color: rgb(0, 34, 243);"><span class="Apple-style-span" style="text-decoration: underline;"><br class=""></span></div><div class="" style="margin: 0px; font-stretch: normal; font-size: 10px; line-height: normal; font-family: Arial; color: rgb(0, 34, 243);"><div class="" style="margin: 0px; text-align: justify; font-stretch: normal; line-height: normal; color: rgb(192, 192, 192);"><i class="">Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. </i><b class=""><i class="">IPeva</i></b><i class=""> décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.</i></div></div></span></font></div></span></font></div></div></div> </div> <div><br class=""><blockquote type="cite" class=""><div class="">Le 8 déc. 2021 à 08:03, Arash Naderpour <<a href="mailto:arash_mpc@parsun.com" class="">arash_mpc@parsun.com</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">>My suggestion would be along the lines what was proposed on the APWG<br class="">>meeting already - earmark these /24s as non-transferrable, ever.<br class=""></div><div dir="ltr" class=""><br class=""></div><div class="">I don't think it is a good idea to split the IPv4 addresses into different types, transferable and non-transferrable. it puts those newcomers in a disadvantageous position compared to the older members, it is not fair and doesn't fix anything in long term.</div><div class=""><br class=""></div><div class="">Regards,</div><div class=""><br class=""></div><div class="">Arash </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 8, 2021 at 1:56 AM Gert Doering <<a href="mailto:gert@space.net" class="">gert@space.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br class=""> <br class=""> On Tue, Dec 07, 2021 at 02:29:15PM +0000, Erik Bais wrote:<br class=""> > As WG chairs we would like to see the position of the WG on the topic and what could be seen as a possible solution. <br class=""> <br class=""> As a member of the WG, I do share the sentiment that the intent of the<br class=""> "IPv4 runout" policies have been "ensure that late comers to the game<br class=""> can have a bit of IPv4 space, to number their IPv6 translators", and<br class=""> not "grab some space for free, and sell it for more money elsewhere".<br class=""> <br class=""> I do not think this can be fixed on the AGM level ("one legal entity<br class=""> can only have one LIR account") - we've been there, in the rush to /22s,<br class=""> and all it does it "make people hide behind shell companies", so in<br class=""> the end, the address space goes out anyway, but registry quality suffers.<br class=""> <br class=""> Trying to make the NCC require even more paperwork isn't going to stop<br class=""> those that want to game the system, but will impact everyone else by<br class=""> making the NCC more annoying to deal with.<br class=""> <br class=""> <br class=""> My suggestion would be along the lines what was proposed on the APWG<br class=""> meeting already - earmark these /24s as non-transferrable, ever.<br class=""> <br class=""> <br class=""> Consequences:<br class=""> <br class=""> - there is no more financial incentive to "get one cheap, sell it expensive"<br class=""> <br class=""> - if you need space to run your business, this is exactly what it is<br class=""> there for - you can still sell your business (with the /24), you<br class=""> just need to keep the LIR account. But that's as with other <br class=""> business assets.<br class=""> <br class=""> - if you want to merge multiple LIR accounts, all having their own<br class=""> /24 - then you need to keep around these accounts, or return some<br class=""> of the /24s.<br class=""> - corrolary: if you use these /24s to number your IPv6 translators,<br class=""> then renumbering this translator into "your other /24" is actually<br class=""> not very hard. <br class=""> - corrolary2: If you use the /24s to directly number your customers,<br class=""> you missed the boat already (wearing my RIPE unicorn t-shirt today).<br class=""> <br class=""> Gert Doering<br class=""> -- NetMaster<br class=""> -- <br class=""> have you enabled IPv6 on something today...?<br class=""> <br class=""> SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer<br class=""> Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann<br class=""> D-80807 Muenchen HRB: 136055 (AG Muenchen)<br class=""> Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279<br class=""> -- <br class=""> <br class=""> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" rel="noreferrer" target="_blank" class="">https://mailman.ripe.net/</a><br class=""> </blockquote></div></div> -- <br class=""><br class="">To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/" class="">https://mailman.ripe.net/</a><br class=""></div></blockquote></div><br class=""></div></body></html>