So if the above is correct yes we can connect to native IPv6 sites with native IPv6 users able to connect directly back to us (if the routes processes IPv6) and still use IPv4 LAN but in order for all this to happen we have to be told a lie to where we've going and where its from by IPv4 to/from 22.214.171.124.
For real native IPv6 to work on a LAN your LAN must be IPv6.
Dual stack for us users of both IPv4 & native IPv6 when sites move off IPv4 to IPv6 that free up IPv4 is a needed thing to happen.
I just hope they route a prefix at all. I've seen too many ISPs recently put a /64 (or worse, /56 or /48) on-link and then just not route a prefix on top of that. The /56 and /48 cases in particular suggest that those ISPs don't really understand what they're doing.
rDNS delegation would be kinda nice too, so I don't have to remember all my IPs.
If IPv4 was 1-10 and IPv6 was 1-20 and a site is on 15 an IPv4 LAN can't get to it.
Perhaps better to use 11-20 for your IPv6 example there, since a v6-only node can't connect to v4(-only) nodes.
Theirs just no detailed diagram that shows how 4to6 works so I thought I have a go.
From your reference to 126.96.36.199 I'm guessing you're talking about 6to4. 6to4 is basically just a regular 6in4 tunnel with the endpoint being the anycasted 188.8.131.52, so that you don't have to set up an account with someone to bring the tunnel up.
Note that 6to4 is only usable with a public v4 address to talk from -- if you're behind NAT, you can't use it. (But it gives you a routed /48, so you just route a /64 from that onto your LAN in much the same way you would if you got the /48 natively. Yes, this does mean you're going to end up with v6 on the LAN; that's pretty much always the case if you want machines on it to talk to IPv6 servers.)
Unfortunately, right now the closest 184.108.40.206 to VM (owned by Goscomb?) is having some issues with ICMP rate limiting (namely I think that the rate-limiting may be applying to ICMP packet-too-big errors), so PMTUd doesn't work through it... which is a bit annoying.
Would be nice if VM set up their own 220.127.116.11, but it looks like they aren't even capable of that at the moment either...
Quoting Mark's last post - Whilst we already have enough IPv4 address space for our current network needs, as part of ongoing network upgrades, we have been looking at making our network ready for IPv6 connectivity. There are many factors which need to be worked through to ensure a seamless experience for our customers but we anticipate we will progress with initial stages of IPv6 deployment at some point during 2012.
I work for Virgin Media but my opinions are my Own
It doesn't work like that with IPv6. The network is based on the first 64 bits and the host on the last 64 bits. Therefore if things are done correctly a /64 should be the minimum given. If they are using stateless autoconfiguration then the host section address (last 64 bits) is based on the MAC address.
Also note that there isn't NAT, so therefore a firewall is very important