Not to diminish the importance or need of such defenses (I have posted in the last week an IPV6 port scanner, etc) but if I was a bad guy, IPV6 doesn't strike me as a very straightforward, easily & widely exploitable attack vector.
We're 2 years past "IPV6 day" and IPV6 is still kind of a work in progress and far, far from being the transport layer the internet and our home networks rely upon. The users of this site are bound to be an unusually ahead of the curve/early adopter/high tech savvy end user - but in the bigger picture I'm probably the only person among my friends & family that has IPV6 native ISP, w/ IPV6 DNS, a cable modem & head end w/ IPV6 enabled, an IPV6 dual stack router, and almost entirely IPV6 dual stack enabled client devices.
So yes it's important, of course, but if you're geeky enough to have a similar setup chances are you didn't fall backwards blindly into it and not know what to do about it.
If I'm a bad guy, I'm spending my time on the old standbys like Java and Adobe exploits instead of attempting proof of concept IPV6 end user attacks.

. In no way trying to encourage complacency, just saying that, if anything, the IPV6 adopting demographic is probably more security aware than the average user who turns on AiCloud remote management features blindly and doesn't question the security risks but also thinks switching their router login to HTTPS brings them some sort of added security.