-
Notifications
You must be signed in to change notification settings - Fork 3
Chat Private #93
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
base: master
Are you sure you want to change the base?
Chat Private #93
Conversation
|
|
||
| The following mappings connect PRIVATE1 concepts to SDS fields: | ||
|
|
||
| - `sender_id`: !TODO: This requires PRIVATE1 to be identity aware |
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.
Unsure exactly what the best course of action is here. Recent changes to SDS requires an sender_id be attached the the SdsMessage.
This then brings in a concept of identity to this specification. Its definitely possible to introduce Identity concepts in order to pass them through to SDS, however it seems like a lot of added complexity
This PR adds a specification which describes a conversation protocol for pairwise communication called PRIVATE1.
It covers payload generation and operation after a key has been agreed upon by both parties.
Notes
This may eventually be simplified and use Reliable Channels but its explicit in how it utilizes SDS + segmentation and the reasons for doing so.