Re: [dhcwg] New Version Notification for draft-wing-dhc-dns-reconfigure-01.txt

[Ted Lemon <[e-mail]>]

On Jul 2, 2013, at 12:22 PM, "Bernie Volz (volz)" <[e-mail]> wrote:
> 1. An option from the relay during client requests (Relay-Forw) to the server as to whether the client is single/dual stacked (as the assumption is the relay monitors this).
> 2. A means for the relay to reconfigure the client (already covered by Reconfigure-Request) when changes in the dual stack-ness for a client is detected, perhaps passing this option to help the server determine what to tell the client about reconfiguring. I'm not sure that option adds significant value and requires complicated processing by the server - but if some implementation wanted to use it, I don't see the harm (it would be a MAY).

Thanks, Bernie—that's helpful.   I guess I can see the motivation for doing this, but it seems like some heavy gymnastics the entire purpose of which is to get around bugs in the client stack.   It's also something that a dual-stack DHCP server could detect on its own, if the relays implement the client link-layer-address relay option.   And it's also pretty experimental.

What's the use case?   Do we have a real-world application for this, or is it just something that is theorized to be useful in the future?