On 2/27/11 3:08 PM, Owen DeLong wrote: > Look, can we stop arguing about whether someone needs DHCP or not, > whether they need SLAAC or not. Let's just get both solutions to a mature > and useful state where a network administrator can pick the one that works > best for their environment and move on. > > Devices, routers, OSs, etc. should support both. The IETF should stop letting > the two working groups focus on damaging the other protocol and we should > stop treating this as a competition or a battle and start treating it as > options > to accomplish a task.
The documents are done at least for sufficient pieces to make it work. it's in the hands of vendors and has been for a while. The simple fact is that if you want to do it a particular way and you have an installed base that doesn't support doing it that way, then you're not doing it that way. > Owen > > On Feb 27, 2011, at 1:25 PM, Franck Martin wrote: > >> Yes I don't understand why we need DHCPv6, true RD did not have DNS >> information to pass, but that is fixed, no? >> >> ----- Original Message ----- >> From: "Matthew Palmer" <mpal...@hezmatt.org> >> To: nanog@nanog.org >> Sent: Sunday, 27 February, 2011 4:06:29 PM >> Subject: Re: Mac OS X 10.7, still no DHCPv6 >> >> On Sun, Feb 27, 2011 at 08:56:33AM -0500, Ray Soucy wrote: >>> Mac OS X 10.7 does support RDNSS (RFC 5001) so it is able to get DNS >>> server information in an IPv6-only environment. Of course nobody else >>> has implemented that yet, making Apple a "special case" host once >>> again (I don't even think Cisco supports the option in their T series >>> yet). >> >> radvd and rdnssd work together on Linux nicely to provide RDNSS support. >> Works a treat. >> >> - Matt >> > > >
