This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

[Key Refrresh] [Config AppKey Upate] Can Config AppKey Update be called in the key refresh procedure?

Apparently, Config AppKey Update message can be transmitted in the key refresh procedure. However, one point let me very confused, I looked into the Mesh Spec v1.0.1 (page 127)and it shows me as following below:

The Config AppKey Update message shall generate an error when node is in normal operation, Phase 2, or Phase 3 or in Phase 1
when the Config AppKey Update message on a valid AppKeyIndex when the AppKey value is different. 

Based on the information above, it seems that it shall generate an error when node is in normal operation,phase 1/2/3. But the section 3.10.4.1 Phase 1 –distribution of the new keys shows me as shown as below:

The Configuration Client shall send the new keys to each node that is not blacklisted. 
New keys are distributed using the Config NetKey Update message and the Config AppKey Update message

so these two information make me more confused,  if this is the typoes on the specification?

thanks in advance.

  • Thanks, but I don't understand what it is that you are asking here.

    Maybe you could elaborate a little bit on what it is that you don't understand?

    Best,
    Joakim

  • Hi Joakim,

    OK, sorry to make you so confused. Let me explain it more clearly.

    At first, I dont understand the content mentioned on the spec, but I am a little clear after your explanation. However, what you said is different from the specification shows:

    The Config AppKey Update message shall generate an error when the node is in normal operation, Phase 2 or Phase 3.
    It shall also generate an error in Phase 1 when the Config App key Update message on a valid AppKeyIndex when the AppKey value is different

    VS

    The Status field shall identify the Status Code for the last operation on the AppKey List.
    The allowed values for Status codes and their meanings are documented in Section 4.3.5.
    The Status-Code shall be Success if the received request was redundant (add of an identical existing key, update of an identical updated key, or delete of a non-existent key), with no further action taken

    ----as you can see above, the update of an identical updated key, the status code shall be success, while what you said is It shall also generate an error in Phase 1 when the Config App key Update message on a valid AppKeyIndex when the AppKey value is different.

    so my confusion is that if there are typos for this description. in my opinion, Config AppKey Update message can be sent in phase 1 no matter the AppKey value if it is different or not. In other words,

    1. your explanation if it is wrong as it is different from the spec shows.

    2. my understanding if it is correct, if not. can you explain more?

    thanks in advance.

  • any news about it? i can explain it more clearly if it is not clear.

    thanks in advance.

  • Sorry about the delay.

    Just to be sure that I'm not giving you wrong information, I'll talk to some colleagues about this.

    I'll get back to you as soon as possible.

    Best regards,
    Joakim

Related