[members-discuss] [SPAM] Re: Technical solution to resolve the IPv4 Exhaustion problem and to add more 4, 294, 967, 296 IPv4 addresses that are needed in the world

New addressing schema of [0-65535].[0-65535] shouldn't be too hard to learn (easier than IPv6 hexa numbers)

I don't believe that we as the internet community should block additional IPv4 addresses when the world needs it so much.

All the big companies (Microsoft, Google, Amazon, etc) are supporting IPv6 too and will support IPv6 too.

I don't believe that we need to put pressure and to decide for internet companies and for internet organizations what is the right moment for them to change to IPv6, yes I do believe it should be done and needs to be done - but only they should decide when will the right moment for them.

The current state is bad for the world, what will happen is that the rate of IPv4 will just go up and up and less people will be able to afford it as the time will go by.

Respectfully,
Elad
________________________________
From: Ed Campbell <campbell at inca.ie>
Sent: Sunday, April 26, 2020 1:33 AM
To: Elad Cohen <elad at netstyle.io>
Cc: members-discuss at ripe.net <members-discuss at ripe.net>
Subject: Re: [members-discuss] [SPAM] Re: Technical solution to resolve the IPv4 Exhaustion problem and to add more 4, 294, 967, 296 IPv4 addresses that are needed in the world

I would disagree with everything you said there.

Microsoft getting a large proportion of IO addressing doesn’t help, it hinders the issue. By that logic Google and Amazon and others would also get a large portion.

Resellers would have to learn a new addressing scheme. They don’t understand IPv4 now other wise their networks would be smaller that /16 and their public IP requirements for them and their customers would also be smaller.

And IPv4 has been more used in the last 5 than the previous 20, it is nonsense to think that it would take another 25 years to exhaust this.

It’ll take more than 25 years to exhaust IPv6.



Sent from my iPhone

On 25 Apr 2020, at 23:27, Elad Cohen <elad at netstyle.io> wrote:


In a round table of operating system vendors such as Microsoft and the five RIRs and routing equipment manufacturers, Microsoft will receive a high number of new IPv4+ addresses, so they will have an incentive to deploy the patch to their networking stack fast (all the round table parties will have incentives to quickly create the patches to their systems).

IT resellers will not need to know to do anything besides firmware upgrades to routers and a manual patch update to an operating system (in case the specific end-user operating system is not set for automatic updating)

It took us approximately 25 years to reach the exhaustion of IPv4, it will take us more 25 years to reach the exhaustion of IPv4+, it will give a lot of time for proper and smooth transition to IPv6.

Respectfully,
Elad
________________________________
From: members-discuss <members-discuss-bounces at ripe.net> on behalf of Ed Campbell <campbell at inca.ie>
Sent: Saturday, April 25, 2020 10:24 PM
To: members-discuss at ripe.net <members-discuss at ripe.net>
Subject: Re: [members-discuss] [SPAM] Re: Technical solution to resolve the IPv4 Exhaustion problem and to add more 4, 294, 967, 296 IPv4 addresses that are needed in the world

IPv4 is just over allocated and mismanaged from its inception. Allocating /8’s to DoD etc was just a bad idea.

While I like your idea, the problem with it would be to get the likes of Microsoft to develop their stack to recognise it. The learning curve for dumb IT resellers would also be huge.

The obvious solution is to force the adoption of IPv6 rather than go through another process that will also end up in exhaustion. It may have taken 20 years or so to exhaust IPv4, but the majority of those years weren’t influenced by 4G and now 5G where the demand is going to be extreme. IPv6 is the clear way.

Cheer,
Ed




Sent from my iPhone

On 25 Apr 2020, at 20:01, Elad Cohen <elad at netstyle.io> wrote:


I never created an RFC and not familiar with the process, but I wanted to discuss IPv4+ with Ripe members as I'm a Ripe LIR.

Respectfully,
Elad


________________________________
From: info at cowmedia.de
Sent: Saturday, April 25, 2020 9:53 PM
To: members-discuss at ripe.net
Cc: 'noc xervers'; Elad Cohen
Subject: AW: [SPAM] 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


Hi,



anyhow this is not the right list to discuss this. You need to create an RfC – but as IPv6 already exist there is no real chance of implementing this I would say.



Michael



Von: members-discuss <members-discuss-bounces at ripe.net> Im Auftrag von noc xervers
Gesendet: Samstag, 25. April 2020 20:49
An: 'Elad Cohen' <elad at netstyle.io>; members-discuss at ripe.net
Betreff: [SPAM] 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



That won't be IPv4 but a complete new protocol, and routers/switches/whatever won't support them.

It's a better and cleaner solution to move to IPv6.



Cheers.



[Das Bild wurde vom Absender entfernt. XERVERS]

NOC xervers | +351 300 404 316
P   Please consider the environment before printing this email

[Das Bild wurde vom Absender entfernt. Visit our website]<https://www.xervers.pt/>  [Das Bild wurde vom Absender entfernt. Facebook] <https://www.facebook.com/xervers/>
[Das Bild wurde vom Absender entfernt. Twitter]<https://twitter.com/xervers>  [Das Bild wurde vom Absender entfernt. TrustPilot] <https://www.trustpilot.com/review/www.xervers.pt>





De: members-discuss <members-discuss-bounces at ripe.net> Em Nome De Elad Cohen
Enviada: sábado, 25 de abril de 2020 20:21
Para: members-discuss at ripe.net
Assunto: [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



Hello Everyone,



I want to share with you my technical solution to the "IPv4 Exhaustion" problem (without to upgrade each and every router that exist in the internet), using the below implementation there will be more 4,294,967,296 IPv4 addresses that the world needs so much:



Currently in an IPv4 packet - the source address and the destination address are being represented each by four bytes, each of these four bytes are being displayed as: [0-255].[0-255].[0-255].[0-255]



But it is up to us to choose how we want to display them, for example: four bytes can also be displayed as [0-65535].[0-65535] (two numbers and one dot, the two numbers are bigger because in total they also being represented as four bytes)



So there can be one set of 4,294,967,296 IPv4 addresses (the one that we know in the display format of [0-255].[0-255].[0-255].[0-255])



and another set of 4,294,967,296 IPv4 addresses (with a new format of [0-65535].[0-65535])



We need to have a mark, a flag, in the ip packet header - in order to know if the source address is of the old formatting (IPv4) or of the new formatting (lets call it IPv4+), for that mark the 'reserved bit' in the ip header can be used, so in case the source address is of IPv4+ or in case that the destination address is of IPv4+ (or in case that both the source and destination addresses are of IPv4+) then the reserved bit in the ip header will be set to 1 , we then also need to know exactly if the source address is of IPv4+ or not (meaning of IPv4) and if the destination address is of IPv4+ or not (meaning of IPv4) - this can be done by marking the DF flag if the source address is of IPv4+ (and not marking the DF flag if the source address is of IPv4) and marking the MF flag if the destination address is of IPv4+ (and not marking the MF flag if the destination address is of IPv4), by using the DF and MF bits which are related to fragmentation (whenever the reserved bit is set to '1') we are losing the ip fragmentation functionality for any traffic with an IPv4+ address (for traffic between two IPv4 addresses, the reserved bit is not set to '1' and hence optional ip fragment functionality is unchanged)



We need to know the MTU before an IPv4+ packet will be sent, because no fragmentation will be able to be done with IPv4+ , the current "Path MTU Discovery" (RFC 1191) is not good for that case because it is using the DF bit which we are using as well (and in IPv4+ traffic a DF flag set to 1 is marking that the source address is of IPv4+), and also ICMP protocol can be blocked by routers in the routing path, the solution is to send multiple udp requests (with fixed known MTU sizes) to the destination address (lets call it IPv4+ handshake) - the destination address may or may not receive them (in case a router in the routing path have multiple upstreams and wasn't upgraded to an upper version that supports IPv4+ then it will not recognize the reserved bit and the DF and MF bits related to it, it will not recognize the new IPv4+ addresses and even if the reserved bit is set to '1' and MF flag is set to '1' in the ip packet - it will route to to the destination address just like it is an IPv4 address and not IPv4+ address, meaning to a completely different destination address) - in case the destination address indeed received the IPv4+ packets - it will send back the udp requests to the source address at the exact same sizes (with the reserved bit flag set to '1' and with the DF and MF flags set accordingly) - when the source address will receive them - the source address will know that the destination address is supporting IPv4+ , that ip packets with new IPv4+ formatting will reach the destination and the source address will know what is the biggest size of the udp request that was received - and it will be the MTU for that specific connection between the source and the destination addresses (The IPv4+ handshake will be done again if there is no response from the destination after the initial udp handshake was already completed successfully).



The udp handshake between a source address and a destination address (that any of them or them both is an IPv4+ address) will use a specific udp port, an availalbe unassigned port between 0 to 1023, an operating system networking stack (that was updated for IPv4+ with the operating system automatic updating system) will know exactly what this udp port is for - and will react accordingly, the upgraded operating system networking stack will also check that the destination address (in the IPv4 or in the IPv4+ format) is set locally in the operating system, before sending the udp requests back to the source address (if not then the ip packet will be dropped by the upgraded operating system networking stack). Any operating system that wasn't upgraded to support IPv4+ - will just drop that kind of udp requests.



IPv4+ is fully backward compatible to IPv4 (and any router that was not upgraded yet to IPv4+ will not cause IPv4 traffic to break), it is also not adding any new fields to ip packets or using new fields, IPv4+ will not cause any performance overload for any supported router.



The reason that the MF and DF bits are being use for IPv4+ and not the ToS / IP-ID / Options in ip header are being used is because we cannot be 100% sure that the ToS / IP-ID / Options in the ip header will not be changed or dropped by any rouer in the routing path that wasn't upgraded to IPv4+ (and we don't want to upgrade any router in the world because it is an impossible mission) - in the ip header ToS is being cleared by some routers - IP-ID can be changed by NAT routers - Options field is dropped by many routers, we can trust that the DF and MF flags will not be modified in the routing path by routers that weren't upgraded to IPv4+.



For the above solution not all the internet devices in the world needs to be patched/upgraded to support IPv4+ which is an impossible mission, end-users operating systems need to be upgraded (but it can be done simply using their automatic updating system), BGP routers (and any router with multiple physical routing paths) will need to have its firmware upgraded to support IPv4+, any NAT router that will want to use an external IPv4+ address will need to have its firmware upgraded (any NAT router that will use an external IPv4 address will not need to have its firmware upgraded, only the internet devices in the LAN of the NAT router will need to have a single operating system update in order for them to access IPv4+ addresses in the internet), any home router (not NAT) or home modem will not need to have a firmware upgrade and IPv4+ functionality will be transparent to them.



The deployment of IPv4+ can be fairly easy and very fast, a round table of one person from each one of the 5 RIRs and from each one of the operating systems vendors and from each one of the router manufacture vendors. Even if IPv4+ will be deployed over time, it will not cause the internet to break (devices that need to be upgraded to IPv4+ and didn't yet will work exactly as they are now with IPv4, they will just not yet support IPv4+).



The above will resolve the "IPv4 Exhaustion" problem and will bring to each one of the 5 RIRs almost 900,000,000 new IPv4+ addresses that will be able to the provided to the LIRs worldwide, if you have any question please let me know.



Respectfully,

Elad

_______________________________________________
members-discuss mailing list
members-discuss at ripe.net
https://mailman.ripe.net/
Unsubscribe: https://lists.ripe.net/mailman/options/members-discuss/campbell%40inca.ie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.ripe.net/ripe/mail/archives/members-discuss/attachments/20200425/2912ac7f/attachment.html>