<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style> </head> <body dir="ltr"> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Christian,</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> I'm sorry to write, but you didn't understand how IPv4+ works. And everything that you wrote regarding IPv4+ is completely incorrect.<br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "<font size="2"><span style="font-size:11pt">There is no connectivity between IPv4 and IPv4+</span></font>" - IPv4+ is IPv4, exact same protocol.</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "<font size="2"><span style="font-size:11pt">you would need routers to support 33 bit routes which is not going to happen</span></font>" - This is completely incorrect, route bits are exactly the same.</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> "<font size="2"><span style="font-size:11pt">To enable a client to connect to both the IPv4 and IPv4+ internet it seems to me that you would need at least another address family in the socket protocols which is also a massive overhead. The formatting of the address as two 16 bit values instead of four 8 bit values does not fix the issue in the clients ipv4 stack.</span></font>" - No another address family is needed, the source address and destination are exactly in the four bytes each as they are now - the only difference is the application layer in the operating system - based if the single reserved bit flag is on or off - the ip address will be displayed with one dot (IPv4+) or with three dots (IPv4).<br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <font size="2"><span style="font-size:11pt">"You cannot route ipv4 and ipv4+ in the same global internet if they are two seprate networks and if the addresses mean different things depending on arbitrary address bits.</span></font>" - It is the same network, IPv4 (I'm calling it IPv4+ to represent the one-dot addressing to higher application layers, but it is the same IPv4 packets, same IPv4 network)</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> I'm not against IPv6, IPv6 and IPv4 will always co-exist in some way, IPv4+ brings more ip addresses to IPv4, it doesn't disturb a bit IPv6.<br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Respectfully,</div> <div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Elad<br> </div> <div id="appendonsend"></div> <hr style="display:inline-block;width:98%" tabindex="-1"> <div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Christian Kratzer <ck@cksoft.de><br> <b>Sent:</b> Sunday, April 26, 2020 11:12 AM<br> <b>To:</b> Elad Cohen <elad@netstyle.io><br> <b>Cc:</b> Tobias Lehner <tl@hartl-edv.de>; 'noc' <noc@xervers.pt>; Ed Campbell <campbell@inca.ie>; members-discuss@ripe.net <members-discuss@ripe.net><br> <b>Subject:</b> Re: [members-discuss] Technical solution to resolve the IPv4 Exhaustion problem and to add more 4, 294, 967, 296 IPv4 addresses that are needed in the world</font> <div> </div> </div> <div class="BodyFragment"><font size="2"><span style="font-size:11pt;"> <div class="PlainText">Hi,<br> <br> On Sun, 26 Apr 2020, Elad Cohen wrote:<br> <br> > You didn't fully read my initial post, the MTU with IPv4+ will not be a fixed MTU of 1500 or of any other fixed value, it will be set in the beginning of the connection through a process called: "IPv4+ UDP Handshake"<br> ><br> > Respectfully,<br> > Elad<br> <snipp/><br> <br> Respectfully your solution does not solve any problem. It just creates new ones.<br> <br> There is no connectivity between IPv4 and IPv4+. So clients needing access to both world need to "dual stack" or even "triple stack" if they also need IPv6.<br> <br> To enable connectivity between IPv4 and IPv4+ you would need routers to support 33 bit routes which is not going to happen.<br> <br> To enable a client to connect to both the IPv4 and IPv4+ internet it seems to me that you would need at least another address family in the socket protocols which is also a massive overhead. The formatting of the address as two 16 bit values instead of four 8 bit values does not fix the issue in the clients ipv4 stack.<br> <br> You cannot route ipv4 and ipv4+ in the same global internet if they are two seprate networks and if the addresses mean different things depending on arbitrary address bits.<br> <br> So I fail to see how in any way your solution would provide more adresses to the existing internet without creating a new isolated cloud.<br> <br> IPv6 can coexist with IPv4 because it has been designed appropriately as a fully separate protocol with clean separation in the the ip stack via a separate address family.<br> <br> Greetings<br> Christian<br> <br> -- <br> Christian Kratzer CK Software GmbH<br> Email: ck@cksoft.de Wildberger Weg 24/2<br> Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden<br> Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart<br> Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer<br> Web: <a href="http://www.cksoft.de/">http://www.cksoft.de/</a><br> </div> </span></font></div> </body> </html>