Short answer - it depends.
Quick thoughts:
1) SLAAC can suffice, assuming IPv4 is present to "cheat" off of for
DNS/name resolution.
Or if/when RFC5006 gets more widely supported.
2) Maybe, see next comment :).
3) DHCPv6 client and server support is not exactly 100% available on
all platforms, atleast
not natively (3rd party apps exist, e.g. - Dibbler). Many
routers currently support
stateless DHCPv6 server functionality only ... not stateful.
HTH!
/TJ
>-----Original Message-----
>From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-
>boun...@puck.nether.net] On Behalf Of Renelson Panosky
>Sent: Wednesday, June 03, 2009 9:45 AM
>To: cisco-nsp@puck.nether.net
>Subject: [c-nsp] IPV6 implementation
>
>I am getting ready to start running IPV6 on my core routers, i have a
couple
>questions for the people who already have IPV6 running
>
>1. Should I let computers determine their own IPV6 addresses ?
>
>2. Should I procure IPV6 DHCP Appliance ?
>
>or
>
>3. Should i configure my router to act as the IPV6 DHCP Servers?
>
>
>
>Renelson
>_______________________________________________
>cisco-nsp mailing list cisco-nsp@puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
