-
Notifications
You must be signed in to change notification settings - Fork 4
Updated 0.3 specification #92
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
Conversation
6dda11a to
a0252a8
Compare
cfm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great for the purposes of #85! I've left comments inline as they came to me, but take 'em or leave 'em as you see fit between here and updating protocol.md.
411514b to
f97145b
Compare
|
Moving this back to "in progress" because I suspect this is going to become the catchment pull request in which we accumulate the v0.3 specification for merge into |
8f6b354 to
99f0e99
Compare
fetch operations.
|
Thanks, @rocodes! Based on our conversation today, here's a possible path to merging this into
What do you think? I think (5) really captures my goal at this point: to be able to consider incremental revisions on this foundation. |
docs: reconcile key setup (including signatures) with schedule
Also flattens (but documents) the ciphertext tuples so that the pseudocode parses more intuitively.
|
As of today:
@rocodes, feel free to tag me next week on anything we need to get this into |
docs: reduce pseudocode to HPKE single-shot APIs
…dme, delete wip md doc
6e362d7 to
13af4dd
Compare
|
I've added a couple of notes from the WIP 0.3 md doc to the protocol readme.md about future discussion areas, and I think everything else is captured in protocol.md, so I have deleted the 0.3-wip doc. I think this is ready for main, pending CI. |
…signature (cherry picked from commit 2fb2cca)
|
(cherry-picked last commit from #112) |
cfm
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huzzah. Thanks for tag-teaming on this, @rocodes!
Update protocol specification to 0.3, to match what is currently being drafted: