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

[Margaret Wasserman <[e-mail]>]

Hi Mark,

I think that you have misunderstood the nature of Harald's "discuss"...

At 06:19 PM 2/9/2004 -0500, Mark Stapp wrote:
>as we move towards first a dual-stack and then, eventually, a v6 world, it 
>might be helpful to client implementors if we worked on an 
>application-level api. but I'd sort of want to hear that from the client 
>os and application vendors, so that there'd be some hope that the thing 
>would actually do something useful.
>
>we have specified a consistent way to carry this nis information in a 
>dhcpv6 message. we have not insisted that all nis application clients 
>retrieve the information in the same way, or that all v6 dhcp clients 
>export some sort of api that would make that possible. you can insist that 
>we do so before allowing this particular option to move on, but I don't 
>see much value in that. if the iesg wants us to develop a dhcp client api, 
>that's another matter, and we should talk about that on another email thread.

Harald's two "discuss" positions (on the DHCPv6 configuration options
for NIS and SNTP) do not mention an API, nor do they concern how an
application requests or receives DHCP information within the host.

They do question the fact that the DHCPv6 configuration options for NIS
and SNTP do not mention IPv4, nor do they explain how a dual-stack node
would obtain the IPv4 addresses of NIS or SNTP servers.

Margaret









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