JoinNonce (or AppNonce ) - Preventing Join-accept replays

Hi all,

Do I understand correctly that chirpstack-application-server implements
the Technical Recommendations for Preventing State Synchronization Issues
3 around LoRaWAN™ 1.0.x Join Procedure

Specifically page 8 on " Remedy #1: Preventing Join-accept replays"

Source implementation in

Could somebody help me to verify this?

Thank you for your help

Yes, this implements a counter returned to the device as the AppNonce, now known as JoinNonce in latest spec.

Previous specifications called for random values, guarding for replays required saving all used nonce values. Counter implementation saves only last values at network and end-device.