Subject: Re: [dhcwg] 答复: Re: What about using a single dhcpv6 server for dual-stack hosts to get ipv6/ipv4 settings?

From: "[email-masked]" <[email-masked]>
Date: Sun, 06 Mar 2011 22:07:01 +0100

Very cool to hear Bernie, I thought we were alone in this approach.

And Ted, I couldn't agree with you more!

- Bud

Sent from my HTC

----- Reply message -----
From: "Bernie Volz (volz)" <[email-masked]>
Date: Sun, Mar 6, 2011 20:02
Subject: [dhcwg]答复: Re: What about using a single dhcpv6 server for dual-stack hosts to get ipv6/ipv4 settings?
To: "Bud Millwood" <[email-masked]>, <[email-masked]>
Cc: <[email-masked]>, "Ted Lemon" <[email-masked]>

No, Bud … Cisco Network Registrar also has ONE server that provides both DHCPv4 and DHCPv6 support and most of our configuration objects are the same (except of course the scope and prefix definitions and also the options (there is a v4 set and a v6 set)).

Huyuxing, I don’t see any value in having the DHCPv6 protocol allow configuration of DHCPv4 (at this late point in time). For one, you’ve got to add new functionality into all of the existing client implementations and why would you bother doing that? These clients already support DHCPv4 and it has worked just fine. Invest your time and energy into getting people to move to v6!

-          Bernie

From: [email-masked] [mailto:[email-masked]] On Behalf Of Bud Millwood
Sent: Wednesday, March 02, 2011 9:23 AM
To: [email-masked]
Cc: [email-masked]; Ted Lemon
Subject: Re: [dhcwg]答复: Re: What about using a single dhcpv6 server for dual-stack hosts to get ipv6/ipv4 settings?

	Using a single DHCPv6 server has its' advantages,and would add lots of complexity,but DHCPv4+DHCPv6 would also bring lots of complexity during the transitional period.

If OSS interfaces are different between the two servers, then yes, it is more complex. But I'm not sure that justifies adding DHCPv4 to the DHCPv6 protocol. It sounds more like the OSS interfaces could be better made.

That said,I think we're the only server manufacturer that went so far as to place both DHCPv4 and DHCPv6 engines inside the same process. By doing so we got a very coherent set of OSS interfaces for both protocols, so it most definitely can be done.

Bud Millwood

Weird Solutions, Inc.

http://www.weird-solutions.com

tel: +46 8 758 3700

fax: +46 8 758 3687