[141750] in North American Network Operators' Group
The Business Wisdom of trying to "fix" DHCPv6
daemon@ATHENA.MIT.EDU (Cutler James R)
Fri Jun 10 22:52:21 2011
From: Cutler James R <james.cutler@consultant.com>
Date: Fri, 10 Jun 2011 22:51:26 -0400
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> James R. Cutler james.cutler at consultant.com=20
> Fri Feb 6 18:00:52 UTC 2009
> =20
> DHCP items are end system considerations, not routing network =20
> considerations.
>=20
> The network operations staff and router configuration engineers do not =
=20
> generally concern themselves with end systems.
>=20
> End systems generally are managed quite independently from the routing =
=20
> network. And, they are more subject to the vagaries of day to day =20
> business variability. Note the "one place" in the quoted message =
below.
>=20
> The only overlap is broadcast forwarding for DHCP initiation.
>=20
> Besides, configuration control is hard enough for router engineers =20
> without adding the burden of changing end system requirements. Adding =
=20
> the forwarding entries is almost too much already! ;)
>=20
> So, for routing network operators to denigrate DHCP is probably due to =
=20
> lack of consideration of the end user system requirements. And those =20=
> who denigrate DHCP and say "just hard code it" make end system =20
> management that much more difficult.
>=20
> I still conclude that DHCP is a useful tool for both IPv4 and IPv6 =20
> systems.
=D0=92 11:10 -0700 =D0=BD=D0=B0 22.10.2009 (=D1=87=D1=82), Owen DeLong =
=D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0:
> OK... Here's the real requirement:
>=20
> Systems administrators who do not control routers need the ability in =
a dynamic host configuration mechanism to assign a number of parameters =
to the hosts they administer through that dynamic configuration =
mechanism. These parameters include, but, are not limited to:
>=20
> 1. Default Router
> 2. DNS Resolver information
> 3. Host can provide name to server so server can supply =
dynamic DNS update
> 4. IP Address(es) (v4, v6, possibly multiple v6 in the case =
of things like Shim6, etc.)
> 5. NTP servers
> 6. Boot server
> 7. Site specific attribute/value pairs (ala DHCPv4 Options)
>=20
> These assignments MUST be controlled by a server and not by the router =
because the router is outside of the administrative control of the =
Systems Administrator responsible for the hosts being configured.
James R. Cutler
james.cutler@consultant.com
