Esko Dijk

> @EskoDijk @arnulfrupp any more comments from Your site? @canisLupus1313 Not for now - maybe I can propose further changes (if needed) in a later PR or issue. It's easier...

Review comment: before we can agree on the code, I think in SPEC-1224 the discussion needs to be resolved about which (mesh-impacting) criteria should be used, for making the final...

For the Linux socket() API there is the option `IPV6_MULTICAST_LOOP` that is by default on and can be changed using `setsockopt`. The default documentation is a bit unclear ("Control whether...

@abtink The issue description mentions that `otIp6Send()` is being used by Zephyr. This internally calls `SendRaw()` with parameter `aAllowLoopBackToHost` set to `true`, so the expectation would be surely that the...

Agree that it needs to be defined in the spec if we want to optimize anything here. From the transmitter's perspective: it only knows that the receiver implements the reassembly...

The PR was closed - difficult because fragments may go via different routes, or be delayed > 2 sec en-route while still meeting the final reassembly deadline. One thing I...

@abtink Thanks, > But I dont think this behavior is supported in the case where frag is dropped at MAC layer (no ack after retx). There's also the possibility that...

For the timeout value setting, should we apply a maximum timeout? Something in the order of 10 minutes? This is to ensure that accidentally a very long timeout is set...

It looks like once the 'dropping' begins, every MLE message to be sent is always dropped (Advertisement and Announce). Which is strange because one would expect the queue to automatically...

@caipiblack You had some questions on how the queue mechanism works also: it is a max queue size of 100 outgoing frames. Each frame stays at most 1 second in...