Skip to content

Enable WARP (SPED + SNAP), gated by the server - #1094

Draft
hiroshihorie wants to merge 1 commit into
mainfrom
hiroshi/enable-warp
Draft

Enable WARP (SPED + SNAP), gated by the server#1094
hiroshihorie wants to merge 1 commit into
mainfrom
hiroshi/enable-warp

Conversation

@hiroshihorie

Copy link
Copy Markdown
Member

Enables WARP, negotiated with the SFU. SPED (DTLS-in-STUN) via the WebRTC-IceHandshakeDtls field trial, SNAP (SCTP INIT in SDP) via enableSctpSnap on the default configuration. Nothing engages unless the server enables warp, otherwise plain DTLS/SCTP. Mirrors livekit/rust-sdks#1342.

Blocked on an m150 webrtc-xcframework release including webrtc-sdk/webrtc#283, then both Package manifest pins need bumping.

Note: SPED re-enters the #929 crash surface that #1015 disabled. The m150 teardown path should be validated (or rust field data observed) before this lands. SNAP has no such history.

🤖 Generated with Claude Code

Enables WARP on the client, negotiated with the SFU. SPED
(DTLS-in-STUN) via the WebRTC-IceHandshakeDtls field trial set before
factory creation, and SNAP (SCTP INIT in SDP) via enableSctpSnap on the
default RTCConfiguration. When the server does not enable WARP nothing
is advertised and the connection falls back to plain DTLS/SCTP, so
there is no client side toggle. Mirrors rust-sdks #1342.

Requires an m150 webrtc-xcframework release including
webrtc-sdk/webrtc#283. Both Package.swift and Package@swift-6.2.swift
pins (currently 144.7559.13) must be bumped before this builds.
@github-actions

Copy link
Copy Markdown

⚠️ This PR does not contain any files in the .changes directory.

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