Simon Duquennoy

Hi! This was my mistake, very sorry about it, re-opening this PR now. What happened is the following: I was switching the base branch for this repository https://github.com/wittra/contiki-ng from develop...

Hi! This was my mistake, very sorry about it, re-opening this PR now. What happened is the following: I was switching the base branch for this repository https://github.com/wittra/contiki-ng from develop...

Hi! This was my mistake, very sorry about it, re-opening this PR now. What happened is the following: I was switching the base branch for this repository https://github.com/wittra/contiki-ng from develop...

Hi! This was my mistake, very sorry about it, re-opening this PR now. What happened is the following: I was switching the base branch for this repository https://github.com/wittra/contiki-ng from develop...

My guess is that it is only of use in research / non-IP setups. I personally use it in testbed, to match the infrastructure's node ID to the internal ID.

I would say no (for sure not in my case)

Well there can be a *mapping*, if that counts as *relationship*

I have a module I use for my testbed runs to auto-map node-ID from radio address (per-testbed hardcoded mapping)

The answer is no indeed. I agree on homogenizing! I could contribute my testbed mapping module. When the module is not there, we could either have `node_id = short_addr` or...

My understanding is that for your use-case @romain-jacob, you don't need the deployment module at all. The point of the module is to provide compile-time well-known mappings between IDs and...