On 12 Sep 2007, at 14:37, Gert Doering wrote:
Thus: "why run DHCP at all"...
Or conversely, and equally legitimately, why run RA at all? Not that I'm specifically advocating that position. 8-)
[ ... ]Just because *some* current IPv4 deployments favour DHCP doesn't mean thatit's the right approach for *all* future IPv6 deployments.
This "some/all" distinction is the real point.
I have a few reasons for needing DHCP today on our university's net:
simple IPv4 autoconfiguration (of course), DNS discovery, and a few
applications which need more exotic support ('next' and TFTP servers
for Cisco phones; special application options retrieved using
DHCPINFORM).
I don't see the third (exotic) category going away. I don't say
'unfortunately', because it's not worth moaning about life being
always more complicated than it might be. Besides, there's job
continuity ... 8-)
RA-only and DHCP-only houses there will surely be. They may be
a majority; I just don't know. Vendors and implementors will
no doubt be happy to accommodate both of these, as they can offer
a complete solution. There will also be houses where neither of
these quite meets the requirements (technical, layers 8 and above,
or whatever). These houses will need to profile their RA and DHCP
services so that they "play nice" with each other. They will look
to vendors and implementors who will have taken care to allow
different slices of either service to be disabled so that it can be
offered only by the other service.
One size just won't fit all.
Stop me if I haven't noticed that this is all just a "violent
agreement".
Best regards, Niall O'Reilly University College Dublin IT Services PGP key ID: AE995ED9 (see www.pgp.net) Fingerprint: 23DC C6DE 8874 2432 2BE0 3905 7987 E48D AE99 5ED9
Attachment:
PGP.sig
Description: This is a digitally signed message part