[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.

[Joakim Jakobsen]

Hi.

How I interpret the first statement:
The Config AppKey will generate an error in normal operation, or phase 2/3. OR in phase 1 when the config appkey update message on a valid AppKeyIndex when the AppKey value is different.

Best regards,
Joakim

[xiaolongba]

Hi Joakim,

thanks for your replies, but i still dont understand, can you explain it more details?

[Joakim Jakobsen]

Could you elaborate what it is you don't understand?

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

If the AppKey value isn't different, there shouldn't be any error generated.

Best regards,
Joakim

[xiaolongba]

Hi Joakim,

Many thanks for your reply. Based on the information you answered, it is clear for me now. But another issue generates; why the spec shows me that New keys are distributed using the Config NetKey Update message and the Config AppKey Update message Even though the AppKey value isn't different, there shouldn't be any errors generated? in my opinion, there is not meaningful. we hope to change the AppKey by using the Config AppKey Update message.

the information above let me more confused is that probably there are some wrong explanations on the spec and the correct content should be as below:

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

the following contents from spec：

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

[Joakim Jakobsen]

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

[xiaolongba]

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.