Re: Good for Huawei
I'm not sure I understand what your suggestion is, and I'm not sure your suggestion would work at all, and I'm not sure your suggestion would be a good idea even if it did work.
"Huawei has 18 regions ? Each region could use the full IPv4 range and, with NAT translation between regions, business is done."
The article says they have 39 regions, but I doubt it matters, so let's ignore that. So if I'm understanding your plan correctly, and there's a possibility that I'm really not, we're going to let all those regions use all 2^32 IPV4 addresses, minus some outward facing NAT endpoints. Just using the 10.0.0.0/8 block isn't going to be large enough. In that case, what happens when a customer is assigned the internal IP 104.18.4.22. How do they identify whether they're trying to access themselves or The Register (that's one of their IPV4 addresses)? For that matter, how do they identify if they're going for that address in a different cloud region? I understand how you can encode that into something the routers will interpret and redirect properly, but I don't understand how you identify it in the first place. Every server and application would need to know that there are at least three things any IPV4 address could mean: this region, the internet, or a different region which needs to be identified. Huawei-written software can be given a special address struct to do that, possibly just an 8-bit integer identifying the region or the internet attached to the normal four-byte address, but that won't work as well for user-written software. Software people buy in is going to have an even harder time of it.
Even if you did that, what would happen for all the machines accepting traffic that hasn't already been set up? NAT works well enough if you only open out, but a lot of those devices are the ones that people are opening out to, meaning they need to have somewhere to accept connections. A single IP can only host 65536 services before running out of ports. It's likely that any server will have more than one of those, as even a basic HTTP server generally has three (HTTPS, HTTP, and management, usually SSH). Lots of things use more ports than that, including internal devices making up the network. Is this really better than IPV6, and if so, why?