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

The IESG has one remaining comment on this draft (see 
https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=896&filename=draft-ietf-dhc-dhcpv6-opt-nisconfig):

   what does a DHCPv6 server do when it wants to indicate that there's a NIS
   server available with an IPv4 address and another NIS server available with
   an IPv6 address?

   The two reasons why this can be a silly question:

   - NIS wouldn't work with such a config, so all the servers' addresses
     obviously have to be one address type
   - You can always encode a v4 address as a v6 address using the 96-zeroes
     convention (or something else), so it's obvious how to do it

   But I think the document should address the issue.

We have a couple of alternatives to addressing the issue:

1. Reserve DHCPv6 for IPv6 NIS servers and DHCPv4 for IPv4 NIS servers
2. Wait until the WG completes its work on DHCPv4/DHCPv6 issues
3. Use an encoding to carry IPv4 addresses in the DHCPv6 option; for
    example, Vijay suggests:

    3. Network Information Service (NIS) Servers Option

       The Network Information Service (NIS) Servers option provides a
       list of one or more IPv6 addresses of NIS servers available to the
       client. If any of the NIS servers is available with an IPv4 address,
       then its address will be represented in "IPv4-mapped IPv6 address" 
[RFC3513]
       format. Clients MUST treat the list of NIS servers as an ordered
       list.  The server MAY list the NIS servers in the order of
       preference.

For the DHCPv6 DNS servers option, the WG opted for alternative 1, which
seems to me to be the right thing to do for the NIS servers option, as well.

- Ralph

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