Hi, On 08/27, Stotland, Inga wrote: > > adds two additional properties: list of unicast addresses > > claimed by the node and the current sequence number value. > Could you please explain the justification for adding these two new > properties? Sure thing. The address part is useful when application would like to talk to its own node's Config or Health Server. At the moment the address is known when calling Import or CreateNetwork (even though the application would then need to store it somewhere, so we end up with two sources of truth), but after Join() the application won't know the address assigned to it. As for sequence number part, reading is mostly for debugging and verification. A few our users had trouble identifying a problem in their setup when their node was listed in other nodes' RPL. In the end I would like to make it writable (increment-only) to enable address reuse, but as this stage I'm still looking for a way to implement this without causing a race condition, so I left it readonly for now. regards -- Michał Lowas-Rzechonek <michal.lowas-rzechonek@xxxxxxxxxxx> Silvair http://silvair.com Jasnogórska 44, 31-358 Krakow, POLAND
