On Friday 11 September 2015 12:59:33 Thiago Macieira wrote: > Or we figure out a way to announce that the address is changing. This is a > lot harder since now we must monitor the network interfaces for the > address attribute: when a temporary address becomes stale and what the new > address is. That WILL require AF_NETLINK on Linux (bye-bye Android and > Tizen...) and we'll be very, very pressed for the same information on other > OS. > > Not to mention that this is about IPv6. For IPv4, the address change can be > instantaneous, with no warning and no ability to send with the previous > address once it happens.
Thinking a little more about this, I think we should ignore IPv4 problems. If your DHCP server changes your address suddenly, well, tough luck. You had 15 years to upgrade to IPv6... As for IPv6, what we can do is provide a list of addresses a node is also reachable on, in the reply to discovery. That list needs to be refreshed periodically (a property with maxage?). Each client needs to store all addresses of a server, so when it receives a packet with any one of those addresses, it can know which server it was sent from. Note that those addresses can include IPv4 too. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
