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

(hi - just visiting)

just to be perfectly clear.....

as an occasional network configurer, I think it seems like a pain in the 
backside to have to configure two separate configuration tools that speak 
two separate configuration protocols in order to get two pieces of config 
info (the ipv4 address and the ipv6 address) to a single application on a 
network client.

and as an applications programmer, I think it's a pain in the posterior to 
have to make two unrelated queries and get two unrelated responses back, 
and having to use local configuration, tea leaves, chicken entrails or 
scientific wild-assed guessing to figure out how to combine them, just 
becaue my client software runs on a dual-stack host.

but that's the WG's choice - you can call that either way, and I'll be 
happy to remove my comment on the documents.
But as long as you don't say one way or the other that I'll have to do that 
or that I don't have to do that, the spec is incomplete - I don't know what 
to implement.
And that's why I've called the question.

                       Harald

--On 4. februar 2004 17:16 -0500 Ralph Droms <rdroms@cisco.com> wrote:

> The IESG has one remaining comment on this draft (see
> https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&b
> allot_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
>