Skip to content
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

Open
rikard-sics opened this issue Mar 1, 2022 · 9 comments
Open

Comments

@rikard-sics
Copy link
Member

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

@rikard-sics
Copy link
Member Author

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

@rikard-sics
Copy link
Member Author

Do we even need to halve q?

@rikard-sics
Copy link
Member Author

Savings is that server does not need to count q for responses without Partial IV? So SSN can be used directly on server.

@rikard-sics
Copy link
Member Author

Also need to look at SSN + replay window (received requests implying responses sent without partial IV)

@rikard-sics
Copy link
Member Author

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

@rikard-sics
Copy link
Member Author

Needs further discussion.

@rikard-sics
Copy link
Member Author

The point is you don't even need a count_q, just use your SSN?

@rikard-sics
Copy link
Member Author

rikard-sics commented Mar 1, 2022

https://hackmd.io/sOliRiyGQT-OmjxbprN9XA
(see Efficient counting of ‘q’ for OSCORE AEAD limits)

@rikard-sics
Copy link
Member Author

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.

@rikard-sics rikard-sics transferred this issue from core-wg/oscore-key-update Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant