Re: [dhcwg] draft-ietf-dhc-dhcpv6-opt-nisconfig-05.txt

On Mon, Feb 09, 2004 at 02:36:20PM -0500, Ralph Droms wrote:
> The alternative method for configuring SNTP and NIS would be...?

Right, I don't know any good alternatives, except DHCP. So we
really need DHCP to configure host parameters, not just interface
parameters. If it learns host parameters from different inter-
faces (or v4 and v6), we have a problem.

There might be some administrative solutions to this. I think
I'll ignore the multiple interfaces issue, it has been there
forever.

Then regarding v4 and v6. If all hosts are dual-stack, I would
suggest the administrator only runs one version of DHCP, or at
least let only one of them configure host information.

In a network with both v4-only and dual-stack, it gets more
complicated. You want DHCPv4 that can configure all the v4
clients need. Then for dual-stack, you would either repeat
all host information, and configure them to ask DHCPv6 only,
or you repeat no host information and let them query both.

I'm not sure if these solutions are good enough. One particular
issue is when you want to configure a dual-stack host with both
a v4 and a v6 NTP server. I think that is a realistic and
reasonable scenario. Should you query both DHCPv4 and DHCPv6
servers, get v4 address from one and v6 from the other and
use both? Might be right thing in some cases, not in others.
I think it's much cleaner if you can get both v4 and v6
addresses from DHCPv6 NTP option. This could either be done
with mapped addresses (so v4 is embedded into v6), or I suppose
made more explicit by having some type field saying whether the
address is v4, v6 or something else. Perhaps TLV encoding...

NTP is of course just an example here.

Stig

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg