This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-CC2652R7: Benefits of authenticate thread device into the thread network.

Part Number: LP-CC2652R7

Hello,

I have one FTD, that has already formed thread network and in that my one of MTD device join(Discovery Req/Resp, Parent Req/Resp and Child ID Req/Resp done) that already existing thread network but not authenticate(DTLS steps not done) into the thread network. Without authenticate my MTD device into thread network still it can able to communicate well with their FTD device and I can able to see that packet into the Wireshark as well.

Can anyone tell what are the benefits of the authenticate device into the thread network?, If we not do that then what thing will not work?

Thanks,

Kaushik Parsana

  • Hi,

    If a Thread device can join a network, then we assume that it is already commissioned (hence authenticated and authorized to be on that network).

    Had this MTD already joined the network before?
    Maybe you are using two CLI examples, which already share the same network credentials? (In this case, we can consider them to already be commissioned).

    For typical flow, please see an example of device being commissioned onto the network in the section "Setting up the Thread Network": https://dev.ti.com/tirex/explore/node?node=AOPIgoreYazSKrW7i6NXcA__BSEc4rl__LATEST

    Can anyone tell what are the benefits of the authenticate device into the thread network?, If we not do that then what thing will not work?

    This guarantees that devices on the network are authorized to be in it.
    For a network, it could be a security risk to allow a non-authenticated device onto the network.

    Thanks,
    Toby