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

[xiaolongba]

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.

[xiaolongba]

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

thanks in advance.

[Joakim Jakobsen]

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

[xiaolongba]

thanks bro. i can wait.

[thiy71]

Excuse me, i also have a question.

"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"

In my explanation, it means config app key message could not bring different appkey value in Phase 1?

Is it wrong? When to update the new key??  

thanks for reply

[xiaolongba]

In my opinion, the Config AppKey and Network key are all can be sent in phase 1. The reasons are as follows:

• updation means you would like to update the key, including network key and app key. so Config Appkey & NetKey update message has to send in phase 1, otherwise, this updation is not meaningful.
• Base on the description of Config Appkey update section, as below:

             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. 

so " Config AppKey Update message can be sent in phase 1 no matter the AppKey value if it is different or not"

• if Config Appkey update message exists, the configuration server can receive the appkey and netkey and then it goes to phase 1 at this moment. while configuration client will wait for the feedback from these configuration servers, all feedback can be received and then the client will consider phase 1 is over and prepare for the next phase.

So I still keep my point of veiw," Config AppKey Update message can be sent in phase 1 no matter the AppKey value if it is different or not"

anyway, I am waiting for the feedback from jackim.