-
Notifications
You must be signed in to change notification settings - Fork 0
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
Each client can count q up to half(?) the q limit as an optimization #12
Comments
"Pure" servers do not need to count q, since the client will count for them? Server only needs to count responses with Partial IV? Ask Christian to clarify. |
Do we even need to halve q? |
Savings is that server does not need to count q for responses without Partial IV? So SSN can be used directly on server. |
Also need to look at SSN + replay window (received requests implying responses sent without partial IV) |
Revisit this with Christian Point is that counting up to half q means counting your own messages with PIV and the other parties messages without PIV. So the client and server counts each other's messages without PIV. No messages should be missed in the counting. (Whether they are observations or not.) Cases: Observation Echo procedure |
Needs further discussion. |
The point is you don't even need a count_q, just use your SSN? |
https://hackmd.io/sOliRiyGQT-OmjxbprN9XA |
What is the maximum overestimation for the solution in the HackMD? Feedback from Göran during the CoRE interim on April 28 was 2x (double), which makes sense to me also. |
Summarized and added in new issue about optimizations: #19 |
As suggested during the CoRE interim. This works fine with responses with no partial IV since they will be counted in that senders q counter. Each request can only have max one response without PIV. For Observe notifications they will have a PIV (except maybe the first).
The text was updated successfully, but these errors were encountered: