<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi there,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I have just a small objection to say to the guys that recommend /24 allocations, I saw plenty.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Please take a look at the BGP table at this moment[1], it is really fragmented and it did triple it’s size in last 6-7 years. I doubt that there is someone happy about this, and this is only our fault, not RIPE’s or other RIR’s.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">We voted what we wanted, and not what we needed, and nevertheless we didn’t care about the future.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">This IPv4 discussions should be closed, and talking about BIG LIRs vs SMALL LIRs is already deprecated, since we all are equal at this moment.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">My hope is that the next big thing (lets say a new Facebook like app) will be born in Silicon Valley (s/Silicon Valley/any other IOT city/) and it will work on IPv6 only. From that moment IPv4 is dead, long live IPv6.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">[1] <a href="http://bgp.potaroo.net/bgprpts/bgp-active.png">http://bgp.potaroo.net/bgprpts/bgp-active.png</a></div><p class="airmail_on">On 23 September 2016 at 01:17:14, Teotonio Ricardo (<a href="mailto:teotonio.ricardo@webtuga.pt">teotonio.ricardo@webtuga.pt</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div></div><div> <title></title> <div dir="ltr"> <div>Regarding this discussion, here is my suggestions about what i think that can be done:</div> <div><br></div> <div> - Disallow LIRs to profit from IPv4 Transfers. If they aren't using resources, they should return them, not making money of them in a "black market". IPv4 Resources are owned by the community, not by a single LIR. No one should be able to create a market of these. If they're selling, i'm pretty sure they don't need them, because the ones who really need, will not be selling them at any cost.</div> <div><br></div> <div>- Start to allocate a minimum of /24 instead of /22 to new LIRs and allow them to get up to /22 in the first two years if they need. (A /24 each 6 months for example)</div> <div><br></div> <div>- Start charging by size of IPv4 allocation (setting a minimum and a maximum each year);</div> <div><br></div> <div>- Use the excessive money made from Annual Membership Fees to fund IPv6 Workshops, IPv6 implementation in opensource projects and internet protocols, IPv6 Marketing material for ISPs, Datacenters, Webhosting companies, Universities and end-users, etc.</div> <div><br></div> <div>- Reduce the Annual Membership Fee, compensate or even pay something to LIRs (using the excessive money - see above) that return their unused Resource Allocations. I'm pretty sure 99% of LIRs who have big unused resource allocations, will not make any move if they don't win something in return.</div> <div><br></div> <div>We need to give a boost to IPv6, but we all know that most of the big ISPs have previously been gathering more IPv4 allocations than they needed in order to take advantage of the future limitations that would occur, putting IPv6 implementation in second place.</div> <div><br></div> <div>If they start being charged by allocation, they will think about returning resources they aren't using and prioritize implementation of IPv6. In my opinion, as a community member, LIRs should have the allocations they need, not the allocations they want.</div> <div><br></div> <div>(Sorry for any grammatical or syntax error.)</div> <div><br></div> <div>Best regards,</div> <div>TEOTÓNIO RICARDO: Technical Support & Account Manager @ WebTuga, Lda.</div> <div>blog: <a href="http://blog.webtuga.pt">blog.webtuga.pt</a> - web: <a href="http://www.webtuga.pt">www.webtuga.pt</a> - area de clientes: <a href="http://clientes.webtuga.pt">clientes.webtuga.pt</a></div> <div>twitter: @webtugahosting - facebook: <a href="http://fb.me/webtugahostingfb">fb.me/webtugahostingfb</a></div> <div>WebTuga - Soluções de Alojamento Cloud</div> <div class="gmail_extra"><br> <div class="gmail_quote"><br></div></div></div></div></span></blockquote></body></html>