Comment 1 for bug 1810905

Our experience with midonet with NAT64 is that is hard to scale, FIP addresses work as a 1-1 mapping (IPv4 FIP <--> internal IPv6. ) and because of the huge difference between the IPv6 and IPv4 network address space is not a great solution in the long term. I think that for that scenario will make more sense to implement a lbaas service that allows you to use an IPv4 FIP and use ipv6 hosts as backends.

I really think that for the cloud use base is better to configure a dual stack environment, so you can have VMs using ipv4, ipv6 or both. If is not possible to create an IPv6 uplink in your datacenter you always can create it using a 6in4 tunnel. I think that it could be useful to add a feature to neutron that allows us to create an IPv6 uplink using a 6in4 tunnel against a tunnel broker or other router.