[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

On 26-4-2020 13:55, Paul Thornton wrote:
>
> On 26/04/2020 12:11, Elad Cohen wrote:
>
>> ...you don't need to implement a protocol in order to
>> prove it works, ...
>
> I think you will find that this is *exactly* how new protocols are 
> introduced to the community.  People get a working prototype running 
> and can show (1) that it works and (2) that its perceived benefits 
> outweigh its potential flaws.

I'm having a very hard time envisioning the "easy" software application 
changes that are required to support this.
All ipv4 code depends on the fact an ipv4 address is 4 bytes.
All ipv6 code depends on the fact an ipv6 address is 16 bytes.

Now this requires either 1 extra bit somewhere, or another structure 
describing ipv4+ in sockaddr.

So for this idea to be workable, implementations are the only thing that 
are going to convince application developers to jump on the bandwagon.
And that'll be the same struggle af for IPv6. And as long as the likes 
of github.com don't even do ipv6, I very much doubt that ipv4+ is going 
to go anywhere.  Let alone that it will arrive there faster.
So instead of going after "yet another pot of gold", lets get IPv6 going.

just my 2 cts.
--WjW