Re: WGLC for draft-ietf-dhc-addr-notification - Respond by December 11, 2023

The WGLC has been uncomfortably quiet, so we've just submitted -07
(https://www.ietf.org/archive/id/draft-ietf-dhc-addr-notification-07.html)
to address an oscillation problem: if some servers support the
registration and some don't, the client might turn the registration on
and off, depending on the order of arriving Replies.
While it's not the end of the world, I think it's rather undesirable.
The new text says that the client always register if at least one
server returns the OPTION_ADDR_REG_ENABLE option, and say the client
MUST stop
registering if that server stops returning the option.
Basically, as long as at least one server supports the registration,
the client will be sending messages, but it's still possible for the
administrator to turn the registration off.

Comments?

On Mon, Nov 27, 2023 at 9:32 PM Timothy Winters <[email protected]> wrote:
>
> Hi:
>
> The authors believe this document is ready for WGLC. Therefore, the chairs
> are initiating a WGLC on this document.
>
> Please review this document and provide your comments and whether you
> support this document moving forward or not by the end of day on Monday,
> December 11th, 2023.
>
> Please see
> https://datatracker.ietf.org/doc/html/draft-ietf-dhc-addr-notification-06.
>
> This is a Standards Track document.
>
> Thank you!
>   ~ Tim and Bernie
> _______________________________________________
> dhcwg mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dhcwg



--
Cheers, Jen Linkova

_______________________________________________
dhcwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dhcwg