-
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
[msg] [mrp] MRP_ACTIVE_TIMEOUT seems to never be used #15800
Labels
Comments
turon
changed the title
[msg] [mrp] MRP_IDLE_TIMEOUT seems to never be used
[msg] [mrp] MRP_ACTIVE_TIMEOUT seems to never be used
Mar 30, 2022
turon
added a commit
to turon/connectedhomeip
that referenced
this issue
Mar 30, 2022
turon
added a commit
to turon/connectedhomeip
that referenced
this issue
Mar 30, 2022
turon
added a commit
to turon/connectedhomeip
that referenced
this issue
Apr 1, 2022
turon
added a commit
to turon/connectedhomeip
that referenced
this issue
Apr 4, 2022
turon
added a commit
to turon/connectedhomeip
that referenced
this issue
Apr 4, 2022
andrei-menzopol
pushed a commit
to andrei-menzopol/connectedhomeip
that referenced
this issue
Apr 14, 2022
…ynamic timeout (project-chip#17003) * [mrp] Fix project-chip#15800 - Add start of peer active tracking * [sleepy] Add switching between active / idle based on peer tracking. * [sleepy] Use constexpr for kMinActiveTime. * [sleepy] Fix review comments + restyle.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
The sdk doesn't fully implement MRP retransmission timing calculations.
Per slack discussion: https://app.slack.com/team/U01CPER8YCA
There are tickets like this that show some symptoms of this missing support:
#12680
Proposed Solution
Implement ACTIVE/IDLE behavior with pending spec updates to track peer active state per-session rather than per-exchange.
The text was updated successfully, but these errors were encountered: