<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">It just keeps getting dumber by the minute. My home ISP hasn’t even updated firmware to one that supports v6, but yeah, they’re surely going to update to your Frankenstein ipv4 because you’re going to give them a taste of addresses from
the nightmare pool that will reach even less of the internet than v6.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">NANOG <nanog-bounces@nanog.org> on behalf of Elad Cohen <elad@netstyle.io><br>
<b>Date: </b>Wednesday, May 13, 2020 at 3:41 PM<br>
<b>To: </b>Mikael Abrahamsson <swmike@swm.pp.se><br>
<b>Cc: </b>NANOG list <nanog@nanog.org><br>
<b>Subject: </b>Re: RIPE NCC Executive Board election<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="color:black">Do you realise that this means you're requiring changing *every*
<br>
socket-speaking application in the world?</span></i><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Every internet host that will want to speak IPv4+ , will have an update (for example through the operating systems automatic updates mechanisms)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="color:black">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></i><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">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+.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><i><span style="color:black">You're just inventing yet another incompatible standard and you have to
<br>
touch everything, DHCP, DNS all applications etc.</span></i><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">----<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">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]<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">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 )<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> 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</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">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<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>