I think we should give Linode the benefit of the doubt on this for now.
Depending on how their instances are isolated from each other, it may be difficult to handle prefix delegation all the way down through the individual hosts into the guests.
Even Google had some hacks when they first started bringing up IPv6 support. For example, GMail would display class E addresses instead of the v6 addresses when you viewed last account activity. It was a temporary hack to shoe-horn v6 addresses into their management system.
As I understand it, they don't yet have any automation for setting up /64 prefix routes yet, so every /64 deployed has to be manually added to the router configs. Anyway, you're free to set up your own routing rules using that /64 to forward subnets of it on to different linodes.
Comments
I think we should give Linode the benefit of the doubt on this for now.
Depending on how their instances are isolated from each other, it may be difficult to handle prefix delegation all the way down through the individual hosts into the guests.
Even Google had some hacks when they first started bringing up IPv6 support. For example, GMail would display class E addresses instead of the v6 addresses when you viewed last account activity. It was a temporary hack to shoe-horn v6 addresses into their management system.
As I understand it, they don't yet have any automation for setting up /64 prefix routes yet, so every /64 deployed has to be manually added to the router configs. Anyway, you're free to set up your own routing rules using that /64 to forward subnets of it on to different linodes.