Hi,
I think that RADV, which adds the possibility for stateless configuration, is an important difference between IPv4 and IPv6.
Of course, router advertisements and router solicitations will not traverse routers, so a tunnel would be needed...
The user would have to set up a tunnel (either IPv6 in IPv6 or IPv6 in IPv4) with a dedicated host at he.net. For the test, HE would send a router solicitation through the tunnel and wait for a router advertisement (perhaps using the 2001:DB8::/32 prefix). The use of RDNSS might also be required.
What do you think of this idea?
you said it yourself....ra wont be transported across routers..how would it go from HE across their router, across multiple internet routers, across your tunnel router, then route it to your hosts?
Well, that's why I suggest using a dedicated tunnel that connects directly the user's RADV daemon to the client at he.net...
RAs won't be transported across routers, but encapsulated RAs will, won't they?