-
Notifications
You must be signed in to change notification settings - Fork 79
"tracked" sessions: record of usage should track session usage, not individual key usage #80
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
Comments
Agreed. We should record the overall start and end times and the ids of the keys that were available. |
Tracking by session rather than individual keys aligns with Microsoft's thinking. We support this recommendation. |
If we have initial agreement here, can one of editors volunteer to prepare a pull request for this issue? |
Yes, I will do that. Also for the others where there is agreement or at least |
PR: #87 |
The text from pull request #54 says "the record of key usage" contains an "entry for block key ID." This means that there is a record of usage for each key in the session. This granularity seems unnecessary and has costs, including:
The spec generally treats sessions as a single entity, including closing, removing, and expiration time, and it's unclear why this should be different. If an author really needs different usage data, he or she can use multiple sessions.
The text was updated successfully, but these errors were encountered: