4 ms·
Well performance really isn't something I would point to at all. While I believe it can become problematic with great scale (e.g. those expensive CGNAT boxes),
by jcgl 1mo ago
Well performance really isn't something I would point to at all. While I believe it can become problematic with great scale (e.g. those expensive CGNAT boxes), it's more the architectural and connectivity aspects that are problems:
Architecturally, dealing with two different address spaces is a complication. A flat address space is easier to reason about and more flexible. This is amplified by the fact that IPv4's RFC1918 address space is very small. Have you ever had to merge IPv4 networks from different companies? It's rarely the case that they don't have overlapping ranges.
Connectivity-wise, stateful IPv6 firewalling is very different from NAPT in IPv4 because the applications cannot reason about the ports being used (without rendezvous servers).
- iso1631 1mo ago> Architecturally, dealing with two different address spaces is a complication I completely agree, which is why dual stack is terrible. > Have you ever had to merge IPv4 networks from different companies? It's rarely the case that they don't have overlapping ranges. Dual stack doesn't solve that > stateful IPv6 firewalling is very different from NAPT in IPv4 because the applications cannot reason about the ports being used The source port is ephemeral for almost all applications, and I can't think of a good reason it wouldn't be, just legacy crap I'd love to have an ipv6 only network with NAT66 at the boundary, at home and at work, but while it still requires ipv4 I don't see the point.
- jcgl 1mo agoI'm not advocating dual stack either. Like I said in my other reply to you, I am suggesting IPv4-as-a-service using standard translation technologies and architectures.