Skip to content

feat: reserve ratchet steps in SFrame key IDs - #577

Merged
devopvoid merged 1 commit into
mainfrom
feat/sframe-ratchet-bits
Nov 8, 2026
Merged

devopvoid merged 1 commit into
mainfrom
feat/sframe-ratchet-bits

Conversation

@devopvoid

Copy link
Copy Markdown
Owner

Changes the SFrame key ID layout from #576 before it is released, so that the ratchet of RFC 9605, Section 5.1 can be added later without another format change.

  • Key IDs are now context (16 bits), participant (32), generation (8) and ratchet step (8). Senders send step 0; receivers take any other step for an unknown key. A key provider serves up to 65,536 streams.
  • The format is named webrtc-java-sframe/1 (KeyProvider.FORMAT, FORMAT in the browser module), for applications to agree on by signaling.

Snapshot users of #576 need to update both sides of a call together.

Key IDs are now context (16 bits), participant (32), generation (8) and
ratchet step (8), so that the ratchet of RFC 9605, Section 5.1 can be
added without changing the format again. Senders send step 0, and
receivers take any other step for an unknown key.

The format is named webrtc-java-sframe/1 (KeyProvider.FORMAT and FORMAT
in the browser module), for applications to agree on by signaling.
@devopvoid
devopvoid merged commit 616ebd2 into main Nov 8, 2026
26 checks passed
@devopvoid
devopvoid deleted the feat/sframe-ratchet-bits branch November 8, 2026 23:59
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.

1 participant