Re: Perhaps (probably?) mobile users
>>It is really the Corporate users that never bother to setup IPv6 (due to fear, ignorance, etc) in their corporate firewall that prevents greater adoption of IPv6.
You are surely unaware that the IPv6 standard did not include network-level resiliency for end users, unlike IPv4. It was never too difficult for corporations, until lately, to obtain a PI (Provider Independent) block of public IPv4 addresses and "advertise" it to multiple telcos (known as multihoming). It means, telcos could be added, dropped or changed easily without the need to change public IP addresses (re-addressing is painful).
The original IPv6 standard did not explicitly allow Provider Independent IPv6 address blocks and early deployments were effectively locked to a single telco and its IPv6 address space. When corporate network engineers and IT managers realized that, IPv6 became extremely unpopular among corporate networking pros for many years due to a telco lock-in.
It is now possible to obtain a Provider Independent IPv6 address block, and with IPv4 PI space exhausted, corporate networking is slowly moving to IPv6. This is a slow process because many self-hosted resources are being moved to the cloud in parallel and many companies are quite happy with their existing IPv4 PI space.
As for the internal network, RFC1918 "grey" IP addresses are more than sufficient for the internal network addressing in most corporate networks. Separation between the internal network and the Internet is most often desired and mandatory.