-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ICD] Implement Check-In Protocol Key refresh requirement #28235
Comments
yunhanw-google
moved this to In Progress
in [Feature] Intermittently Connected Devices (ICD)
Nov 30, 2023
dup with #28232 |
github-project-automation
bot
moved this from In Progress
to Done
in [1.3] SDK Feature Complete
Nov 30, 2023
github-project-automation
bot
moved this from In Progress
to Done
in [Feature] Intermittently Connected Devices (ICD)
Nov 30, 2023
yunhanw-google
moved this from Done
to Todo
in [Feature] Intermittently Connected Devices (ICD)
Dec 11, 2023
yunhanw-google
moved this from Todo
to In Progress
in [Feature] Intermittently Connected Devices (ICD)
Dec 11, 2023
github-project-automation
bot
moved this from Todo
to In Progress
in [1.3] SDK Feature Complete
Dec 11, 2023
github-project-automation
bot
moved this from In Progress
to Done
in [1.3] SDK Feature Complete
Feb 3, 2024
github-project-automation
bot
moved this from In Progress
to Done
in [Feature] Intermittently Connected Devices (ICD)
Feb 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When a client receives a Check-In message with a Check-In Counter value indicating that 2^31 counter values have been used, the client shall refresh its entry with a new key.
The text was updated successfully, but these errors were encountered: