Plusnet Trial vs 6to4

[#1]

Just wondering what the difference are between using IPv6 via the plusnet trial or via a 6to4 router?
Specifically my router (TP-LINK TD-W8970) can be configured as a 6to4 router - then machines on my LAN get both an IPv4 and IPv6 number - and I can send IPv6 packets.  So this is simple to do, but what of the differences from doing IPv6 on the plusnet trial. Only differences I can think of:
1) Under 6to4, all my IPv6 packets go via my standard IPv4 gateway (in plus.net), they pick up on the 6to4 IPv6 gateway hack (192.88.99.1) and forward those packets onto he.net. So this means any IPv6 packets have to go via both the plusnet IPv4 gateway, and the he.net relay router.
2) Plusnet trial, helps debug the plus.net IPv6 set up.
From an end users perspective though what are the implications of these, seem not more than a nats wisker. All packets have to go via various routers anyway, so adding a he.net route would seem to add little overhead. Debugging the plus.net IPv6 set up, I guess helps plusnet - what though does it give us?
Your thoughts?

[#2]

Just to confirm - you are referring to 6to4, and not 6in4?

[#3]

Yes - my current IP is
          inet6 addr: 2002:5773:6a54:10:e2b9:a5ff:fe7e:f675/64 Scope:Global
          inet6 addr: 2002:5773:6a54:10:ecd5:d071:1b90:696e/64 Scope:Global
So yes 6to4 not 6in4.
6to4 is far more auto configured compared to 6in4; e.g. I didn't have to sign up with anyone to route my IPv6 traffic, the "out of the packet" configuration of 6to4 is enough that I just enable it on the router - and off it goes, no more configuration needed. Of course plus.net needs to be good enough to route 192.88.99.1 - which they do. Also you have to assume that IPv6 routers (in particular those with IPv4 interfaces) are 2002:: aware .....

[#4]

The main drawback is the first that you listed - forced routing via specific gateways. One of the key benefits of a well connected network like the Internet is that packets can take multiple paths to reach their destination. Hence, issues within the network can be 'routed around' automatically in order to maintain connectivity and maximise performance. The less 'state' that has to be held in the network the better hence why native IPv6 connectivity always has an edge over tunneling, translation, etc which are more intended as transition mechanisms than acceptable end goals in their own right.
In order to trial IPv6 however it's better than nothing and whilst it may not aid Plusnet it is at least one way in which you can 'dabble' in IPv6 yourself.

[#5]

Doesn't the plus.net IPv6 trial suggest using he.net DNSv6 servers? So wouldn't all plus.net IPv6 traffic via names, also at least have to make an initial connection to he.net?

[#6]

The connection to HE is only to fetch the IPv6 addresses associated with the DNS names of the services you're trying to reach. The subsequent connections to those IPv6 services would be made direct (i.e. not via HE).

[#7]

Quote from: summers

Doesn't the plus.net IPv6 trial suggest using he.net DNSv6 servers? So wouldn't all plus.net IPv6 traffic via names, also at least have to make an initial connection to he.net?

You don't have to use DNSv6 servers to use IPv6! It just needs the DNS server used to give IPv6 answers. E.g.

C:\Users\John>nslookup thinkbroadband.com 212.159.6.9
Server:  cdns01.plus.net
Address:  212.159.6.9
Non-authoritative answer:
Name:    thinkbroadband.com
Addresses:  2a02:68:1::4
          80.249.99.130