It is curious how many times we have heard that, not only heard in NANOG and other NOGs, but also in IETF, even debated in long thread with several IDs, and for some strange reason, we all missed that or maybe because nobody got the running code to demonstrate his/her point in a realistic way? Instead, IPv6 is working for everyone that invest just a little bit of effort, in the only credible long-term solution. Of course, like in any aspect of our life, always some people will believe that they can keep using legacy tools, I still see some people using abacus instead of the “calc.app”, it is nice, just for fun, but is not smart neither productive. It is matter of what the world needs. Regards, Jordi @jordipalet El 13/5/20 21:58, "NANOG en nombre de Elad Cohen" <nanog-bounces@nanog.org en nombre de elad@netstyle.io> escribió: 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@nanog.org> on behalf of David Hubbard <dhubbard@dino.hostasaurus.com> Sent: Wednesday, May 13, 2020 10:44 PM To: NANOG list <nanog@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@nanog.org> on behalf of Elad Cohen <elad@netstyle.io> Date: Wednesday, May 13, 2020 at 3:41 PM To: Mikael Abrahamsson <swmike@swm.pp.se> Cc: NANOG list <nanog@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@swm.pp.se> Sent: Wednesday, May 13, 2020 10:22 PM To: Elad Cohen <elad@netstyle.io> Cc: Brielle <bruns@2mbit.com>; NANOG list <nanog@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@swm.pp.se ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.