Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dhcwg] Brokenness of specs w.r.t. client behavior with M&O bits



On Tue, 14 Oct 2008, David W. Hankins wrote:
[RA] fails to suck less than DHCPv4; consequently, anyone who runs
stack today uses DHCPv4 to configure IPv6 (using IPv4 nameservers)!

I wonder where you have gotten the latter misconception. There are LOTS of networks which *at least in significant parts of their network* use manual IPv4 configuration (no DHCP) and 1) manual IPv6 configuration (both address and default route), 2) manual IPv6 configuration (only address, default route via RA), or 3) only RA (both address and route).

For example, we don't use any DHCP in server-only LANs. (In 'office' LANs where laptops, desktops, etc. connect it is used however.) I'm pretty sure this is a very common way to manage servers, though I admit that usign DHCP is likely similarly very common.

You seem to underestimate the usefulness of manual configuration, especially when coupled with other configuration management tools that can help automate it for you.

--
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.