Absolutely spot-on IPv6 security analysis by the Deploy360 section at ISOC, detailing security misconceptions - now full-blown myths - of IPv6 infrastructure. Along with the clarification efforts regarding IPv6 and the ramifications for what security componentry has been baked-in to the network protocol, comes the highly enhanced and approximate 3.4×10 to the 38th power addresses as compared to the measly 4.3 billion capability IPv4 address space.

Leaving the gargantuan IPv6 address space benefits for another discussion, the issue of security flaws resident within the protocols' structure must be managed effectively on such an old addressing specification. After all, the original Internet Engineering Task Force [RFC 2460], the “Internet Protocol, Version 6 (IPv6) Specification” possesses a date of December 1998...

"In order to make IPv6 as simple and interoperable as possible, it uses a minimalist standard packet header. In order to make IPv6 as extensible as possible, it allows “extension headers,” additional chunks of meta-data that can be strung behind the IP header to provide additional features and functionality. IPsec leverages the extension header mechanism to carry necessary authentication and encryption data, for one example. Unfortunately, having extension headers designed into the protocol for extensibility also means having security flaws designed in along with them." - via the ISOC Deploy360 Myth#2 Post