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

[Margaret Wasserman <[e-mail]>]

At 02:40 PM 2/9/2004 -0600, Ted Lemon wrote:
>>Then stop trying to configure SNTP and NIS.
>
>This is a non-problem.   If the protocols are different between v4 and v6, 
>they're different protocols, and shouldn't be represented by the same 
>DHCPv6 option anyway.   So the solution is to treat them that way.

What if the protocols are not different between v4 and v6?  I don't know much
about NIS, but the DNS and SNTP protocols (for example) are not different
between IPv4 and IPv6, nor are most other application protocols.  Most
applications on dual-stack systems will not even be aware of whether they
are running over an IPv6 transport or an IPv4 transport -- they just use
TCP or UDP, and pass a version-independent IP address datastructure (that
may have been filled in using DHCP, a DNS lookup, etc.) as a parameter.

>    Practically speaking, if you have a dual-stack client, you're going to 
> configure it with DHCPv4 and DHCPv6, so you can get your NISv4 address 
> from DHCPv4.   The way to write this in a standard if we decided to would 
> simply be that the IP addresses for equivalent servers provided by DHCPv6 
> supersede those provided by DHCPv4.   NISv4 and NISv6 aren't equivalent, 
> so there's no problem.

I don't know what you mean by "the IP addresses for equivalent servers provided
by DHCPv6 supersede those provided by DHCPv4"?  What is an equivalent server,
and how would an application tell?

Margaret



_______________________________________________
dhcwg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/dhcwg