The experimental designation is just wrong. We have to break the current requirement to deploy both RA & DHCP if you want to have a working network. Each model should be able to stand on its own, and 5006 fills a hole on that side. The 'experiment' is simply there to placate those that want a DHCP-only model. Change the status of the RFC & make it a node requirement...
Tony > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Brian Haberman > Sent: Thursday, November 13, 2008 6:06 PM > To: [EMAIL PROTECTED] > Cc: ipv6@ietf.org > Subject: Re: Node Requirement: New issue 5: Support for RFC 5006 > > [EMAIL PROTECTED] wrote: > > I recieved a question: > > > > What about RFC5006 "Router Advertisement Option for DNS > Configuration", > > or is it problem that it is of experimental category? > > > > My feeling is that this is experimental, so it cannot really be a > > requirement. > > > > What does the working group think? > > > > Given that this is an Experimental spec, I would contend that we cannot > include it as a requirement for nodes. I think this holds for any > Experimental specification. > > Regards, > Brian > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
