[riot-notifications] [RIOT-OS/RIOT] gnrc_netif: reset IPv6 config on reset and address change (#10544)

Martine Lenders notifications at github.com
Fri Jan 18 19:41:25 CET 2019


> Between the lines, https://tools.ietf.org/html/rfc4941#section-3 avoids them by basically adding session-based IIDs.

We don't have this kind of memory space available to do this. 

> Problems arise from network state - the most obvious being transport sessions that will break with changing IP endpoints.
Other problems arrive with host state in routing tables etc.

But so they will if the network device state changes due to a reset (compare `sudo ip link set dev eth0 down` on Linux).

> Personally, I would not advise to make IID changes automatic. If a user actively plays with L2 addresses, L3 address management should IMO be also explicit.

Since we can't add new addresses indefinitely our only option would be to keep the old, risking that it is not based on the link-layer address anymore. This would break 6Lo-ND, since [RFC 6775, section 5.6](https://tools.ietf.org/html/rfc6775#section-5.6) makes this assumption.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10544#issuecomment-455646490
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190118/6ac0c849/attachment-0001.html>


More information about the notifications mailing list