It is subtle issues like this that make me wonder if it is worth just statically routing the /48 and having done with it. But I can work with this either way; others maybe not so well.
Based on feedback I'm looking at allowing for static routing alongside TR187. However it is likely that CPE will be built to conform with TR187 I want to ensure this works correctly in the first instance. If any of the trialists wish to test the addition of static routing, then I'm happy to attempt it with them.
In theory if the CPE supports it TR187 is the easiest method, the end user almost has no configuration to carry out. On an Asus AC68U , we simply turn on ipv6 native and enable DHCP-PD, all the rest of the configuration is then automatic using the default settings. (well apart from IPv6 firewall which has to be turned on manually).
If we did not use DHCP-PD the user user would have to be aware of their /48 prefix, and know how to subnet this into a /64 for their LAN and configure it into their LAN settings. For technical users this is straight forward. For untechnical home users we assume that they just want to plug and play. NAT in IPv4 actually made this easy for them, a huge number of home users have never considered that they could change their internal subnet away from the default setting.
Edited by hazey_flakes (Wed 19-Aug-15 13:54:00)