Reclaiming IPv4 Class E's 240.0.0.0/4

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by ynik on Monday May 27, 2024 @01:04PM (#40492606)

> If anything is trying to route to only 4 octlets, routers add a 1. in front of it. Bam, legacy solved.

Only for unidirectional UDP.

How do you think the other side would be able to respond if it's unaware of the 5th octlet? Basically every protocol in existence requires two-way communication and there's no backward compatible way of providing that.

[ Parent | on HN ]

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bbarnett on Monday May 27, 2024 @02:25PM (#40493264)

I covered that. Edge routers transition 1.x.x.x.x to x.x.x.x as a default, and x.x.x.x to 1.x.x.x.x. This is an interim change, so that ipv4 can communicate to ipv4 forever. Legacy systems can be supported on ipv4 only, relegating them (just as they are now!) to not having access to that new address space.

[ Parent | on HN ]

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by growse on Monday May 27, 2024 @05:32PM (#40494948)

You realise that this idea of "embedding a smaller, old address space inside a newer bigger one" has existed in IPv6 for a pretty long time now?

[ Parent | on HN ]

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by bbarnett on Monday May 27, 2024 @06:02PM (#40495178)

A car and a motorcycle both travel on roads, but they are still not the same. - Henry Perkins

[ Parent | on HN ]

Re:Reclaiming IPv4 Class E's 240.0.0.0/4 by tiberious726 on Wednesday May 29, 2024 @03:14AM (#40509333)

You mean this? https://en.m.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addres...

[ Parent | on HN ]