It's not "real" 128-bit addressing; for addressing routable networks you have only 64 bits. The rest is for devices inside that network. Additionally, it is quite possible that any single device will have more than one IP (with SLAAC, it can ask for how many it needs. With DHCPv6, it can be limited, and that's exactly why Android doesn't support it. Your cellphone company would be able to prevent you from tethering). There's no NAT, so you can't hide a network behind a single IP.
Comments
It's not "real" 128-bit addressing; for addressing routable networks you have only 64 bits. The rest is for devices inside that network. Additionally, it is quite possible that any single device will have more than one IP (with SLAAC, it can ask for how many it needs. With DHCPv6, it can be limited, and that's exactly why Android doesn't support it. Your cellphone company would be able to prevent you from tethering). There's no NAT, so you can't hide a network behind a single IP.
“There's no NAT...”
Are you saying that NAT is technically impossible with IPv6? Because I have doubts about such a statement.
Not imposible, but brings more problems than it solves. It's better to forget, that it exists.
RFC6296, by Cisco.
NAT66 disagrees with you. It’s been in the Linux kernel since version 3.7.
Whether you should do it is a different question, but saying NAT capabilities don’t exist with IPv6 is incorrect.
Have you ever seen that in the wild? I consider myself happy, that I didn't.