No, on the contrary. What I'm saying is that IPv6 doesn't have enough traction, there's a finite number of developers and there are features that will be used by more people that should take more priority.
To put it another way, a native IPv6 client isn't necessarily as innovative as some of the other pending features. Not having DHCPv6 native isn't the end of the world and is a minor annoyance for a few. Putting a team on implementing DHCPv6 for a small subset of users takes people away from things like bugfixes. DHCPv6 is not trivial.
If Apple found a feature that relied upon IPv6 then I imagine a DHCPv6 client would be a priority. As it is, in the meantime you'll have to settle for things like http://klub.com.pl/dhcpv6/ - which at least works on leopard but you'll have to compile it yourself and it's not complete.
To put it another way, a native IPv6 client isn't necessarily as innovative as some of the other pending features. Not having DHCPv6 native isn't the end of the world and is a minor annoyance for a few. Putting a team on implementing DHCPv6 for a small subset of users takes people away from things like bugfixes. DHCPv6 is not trivial.
If Apple found a feature that relied upon IPv6 then I imagine a DHCPv6 client would be a priority. As it is, in the meantime you'll have to settle for things like http://klub.com.pl/dhcpv6/ - which at least works on leopard but you'll have to compile it yourself and it's not complete.
For some info on what is already possible with IPv6 on OSX take a look here: http://ipv6int.net/systems/mac_os_x-ipv6.html