Skip to content

Conversation

@jazzz
Copy link
Contributor

@jazzz jazzz commented Oct 26, 2025

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.


The following mappings connect PRIVATE1 concepts to SDS fields:

- `sender_id`: !TODO: This requires PRIVATE1 to be identity aware
Copy link
Contributor Author

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

@jazzz jazzz marked this pull request as ready for review October 28, 2025 23:44
@jazzz jazzz requested review from jm-clius and plopezlpz October 28, 2025 23:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants