dhc-addr-notification: input required on the client behaviour

Hello,

I'd like to start a separate thread to focus on the last (I believe)
unresolved issue with draft-ietf-dhc-addr-notification: how the client
handles subsequent Reply messages w/o OPTION_ADDR_REG_ENABLE option.

To sum it up:
- the logic proposed in -06 (the client processes the first received
Reply) doesn't work, as it would cause an oscillation (and Michael has
stated a number of times that he doesn't really like it).
- to address that, -07 suggested that the client tracks what servers
sent the OPTION_ADDR_REG_ENABLE option. While that approach fixes the
oscillation issue, it sounds rather complex.
- Bernie suggested the following: "once a client receives confirmation
that the link
supports address registration, it sends them regardless of what future
Reply’s (or Advertises) say. Only when the client believes the link
has changed, does it clear the flag and send something
(Information-Request) with the registration option in the ORO list
when it lands at a (possibly) new location".
That approach is very simple, but it has one drawback: if the
administrator disabled OPTION_ADDR_REG_ENABLE  and wants the clients
to stop sending messages, the clients need to be kicked off the
network.

Would the group be OK if -08 contains Bernie's proposal?

-- 
Cheers, Jen Linkova

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