State Management (part II) Different NSLPs have different qualitative state management requirements/semantics. E.g. soft state (explicit or implicit refresh), timeout = deletion or just ‘maybe not kept’, even hard state… Different quantitative aspects E.g. Lifetimes, lifetime precision, refresh criticality What would integration with the NTLP buy you? Putting state management functions in NTLP makes the NTLP API much more complex If NSLP peers aren’t always NTLP peers then even harder to define and analyse |