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.

Sign up for GitHub

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

Jump to bottom

ACK / NACK #92

Closed
bifurcation opened this issue Jan 13, 2019 · 2 comments
Closed

ACK / NACK #92

bifurcation opened this issue Jan 13, 2019 · 2 comments
Labels
enhancement

Comments

@bifurcation
Copy link
Collaborator

In early discussions around MLS, people expressed interest in specifying how to do ACKs / NACKs on messages. Questions to address:

  • How are ACKs / NACKs encoded?
  • How are they cryptographically protected? (signed, encrypted, MAC'ed, etc.)
  • When should they be sent?
  • Do they apply to handshake messages? application messages? both?
@beurdouche
Copy link
Member

We should discuss that today

@beurdouche beurdouche self-assigned this Oct 1, 2019
@beurdouche beurdouche removed their assignment Dec 20, 2019
@bifurcation
Copy link
Collaborator Author

This was discussed at the January 2020 interim. The conclusion there was that error recovery is a sufficiently complex topic that it merits a separate specification, which may extend the protocol, e.g., to add an Ack message or a Resync proposal.

This was referenced Jan 31, 2020
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bifurcation @beurdouche