RIPE NCC Executive Board election

Elad Cohen elad at netstyle.io
Wed May 13 19:53:44 UTC 2020


Your home ISP will support IPv4+ packets exactly as it is now, because IPv4+ is based on the exact current IPv4 packet format. With the needed roundtable - IPv4+ will be deployed in the whole internet and fast.
________________________________
From: NANOG <nanog-bounces at nanog.org> on behalf of David Hubbard <dhubbard at dino.hostasaurus.com>
Sent: Wednesday, May 13, 2020 10:44 PM
To: NANOG list <nanog at nanog.org>
Subject: Re: RIPE NCC Executive Board election


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.



From: NANOG <nanog-bounces at nanog.org> on behalf of Elad Cohen <elad at netstyle.io>
Date: Wednesday, May 13, 2020 at 3:41 PM
To: Mikael Abrahamsson <swmike at swm.pp.se>
Cc: NANOG list <nanog at nanog.org>
Subject: Re: RIPE NCC Executive Board election



----

Do you realise that this means you're requiring changing *every*
socket-speaking application in the world?

----

Every internet host that will want to speak IPv4+ , will have an update (for example through the operating systems automatic updates mechanisms)





----

It's taken us decades to get applications to use the new struct to support
IPv6+IPv4, resetting the timer back to 0 and starting over does not help
deployment. It just kicks it another 20 years down the line.

----

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+.





----

You're just inventing yet another incompatible standard and you have to
touch everything, DHCP, DNS all applications etc.

----

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]

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 )





________________________________

From: Mikael Abrahamsson <swmike at swm.pp.se>
Sent: Wednesday, May 13, 2020 10:22 PM
To: Elad Cohen <elad at netstyle.io>
Cc: Brielle <bruns at 2mbit.com>; NANOG list <nanog at nanog.org>
Subject: Re: RIPE NCC Executive Board election



On Wed, 13 May 2020, Elad Cohen wrote:

> LOL funny seeing you changing your mind by 180 degrees when someone you
> know in the community writing to you the exact same thing.

"In addition, the sockets API should be extended to support IPxl with a
new socket domain PF_IPXL which is identical to PF_INET in every respect
save that the IP addresses are 8 bytes long instead of 4."

Do you realise that this means you're requiring changing *every*
socket-speaking application in the world?

It's taken us decades to get applications to use the new struct to support
IPv6+IPv4, resetting the timer back to 0 and starting over does not help
deployment. It just kicks it another 20 years down the line.

You're just inventing yet another incompatible standard and you have to
touch everything, DHCP, DNS all applications etc.

--
Mikael Abrahamsson    email: swmike at swm.pp.se
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20200513/45b7890d/attachment.html>


More information about the NANOG mailing list