[riot-notifications] [RIOT-OS/RIOT] NDP: implement missing functionality (#3052)

tinstructor notifications at github.com
Fri Nov 20 12:55:26 CET 2020


@miri64 @benpicco I was wondering what happens when the ABRO valid lifetime expires since [RFC 6775](https://tools.ietf.org/html/rfc6775) is rather ambiguous (at least to me it is) on this subject. For example, it states on [page 29](https://tools.ietf.org/html/rfc6775#page-29): 

> When the ABRO Valid Lifetime associated with a 6LBR times out, all information related to that 6LBR MUST be removed.
 
But then on [page 36](https://tools.ietf.org/html/rfc6775#page-36) it says:

> The router keeps state for each 6LBR that it sees with an ABRO. This includes the version number, the Valid Lifetime, and the complete set of PIOs and 6COs. The prefixes are timed out based on the Valid Lifetime in the PIO. The Context Prefix is timed out based on the Valid Lifetime in the 6CO.

I've tried digging through the code and I think I understood that RIOT just times out all information stored for a given 6LBR (i.e., including contexts and prefixes) when the ABRO valid lifetime expires, regardless of the fact that prefix and context lifetimes may not have expired yet. Conversely I understood from the code that when prefixes and / or contexts expire before the ABRO does, they are timed-out independently. Is my assumption correct? 


-- 
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/issues/3052#issuecomment-731126325
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201120/acfc0bc4/attachment-0001.htm>


More information about the notifications mailing list