<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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)">
----</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<i><font size="2"><span style="font-size:11pt">Do you realise that this means you're requiring changing *every*
<br>
socket-speaking application in the world?</span></font></i></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
----</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Every internet host that will want to speak IPv4+ , will have an update (for example through the operating systems automatic updates mechanisms)<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)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
----</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<i><font size="2"><span style="font-size:11pt">It's taken us decades to get applications to use the new struct to support
<br>
IPv6+IPv4, resetting the timer back to 0 and starting over does not help <br>
deployment. It just kicks it another 20 years down the line.</span></font></i></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
----</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I wrote about the usage of a roundtable in order to implement everything fast (the roundtable will include one representative from each of the operating system vendors, one representative from each of the routing equipment manufacturers and one representative
from each of the 5 RIR's), if I will be elected to RIPE board I will do everything in my power so this roundtable will be formed fast and that the needed updates will be created fast. Each party in the roundtable will receive an amount of free IPv4 addresses
from the new IPv4+ pool, and each ASN will also receive for example a /21 , home-routers and home-modems will not be needed to be updated and they will support 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)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
----</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<i><font size="2"><span style="font-size:11pt">You're just inventing yet another incompatible standard and you have to
<br>
touch everything, DHCP, DNS all applications etc.</span></font></i></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)">
There is an adjustment to IPv4+ that the format of addresses will not be [0-655365].[0-655365]v4 - but it will be [256-511].[0-255].[0-255].[0-255]</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
So IPv4+ addresses will be in the format of IPv4 addresses - it will end-user adoption of IPv4+ easier and also integration in the applicative layer easier (as application developers will only need to set that the first number can be higher instead to support
a new format of [0-655365].[0-655365]v4 )<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)">
<br>
</div>
<div id="appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Mikael Abrahamsson <swmike@swm.pp.se><br>
<b>Sent:</b> Wednesday, May 13, 2020 10:22 PM<br>
<b>To:</b> Elad Cohen <elad@netstyle.io><br>
<b>Cc:</b> Brielle <bruns@2mbit.com>; NANOG list <nanog@nanog.org><br>
<b>Subject:</b> Re: RIPE NCC Executive Board election</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">On Wed, 13 May 2020, Elad Cohen wrote:<br>
<br>
> LOL funny seeing you changing your mind by 180 degrees when someone you <br>
> know in the community writing to you the exact same thing.<br>
<br>
"In addition, the sockets API should be extended to support IPxl with a <br>
new socket domain PF_IPXL which is identical to PF_INET in every respect <br>
save that the IP addresses are 8 bytes long instead of 4."<br>
<br>
Do you realise that this means you're requiring changing *every* <br>
socket-speaking application in the world?<br>
<br>
It's taken us decades to get applications to use the new struct to support <br>
IPv6+IPv4, resetting the timer back to 0 and starting over does not help <br>
deployment. It just kicks it another 20 years down the line.<br>
<br>
You're just inventing yet another incompatible standard and you have to <br>
touch everything, DHCP, DNS all applications etc.<br>
<br>
-- <br>
Mikael Abrahamsson email: swmike@swm.pp.se<br>
</div>
</span></font></div>
</body>
</html>