Skip to content

Add SFrame packetization handling for SFrameTransform #252

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

youennf
Copy link
Collaborator

@youennf youennf commented Apr 30, 2025

Following on last WebRTC WG meeting and this week's chair meeting, here is a draft of how SFrame packetization could be integrated with SFrameTransform and RTCRtpScriptTransform.


Preview | Diff

@youennf
Copy link
Collaborator Author

youennf commented Apr 30, 2025

@jan-ivar, @guidou, @dontcallmedom, here is the PR based on yesterday's meeting.

@youennf
Copy link
Collaborator Author

youennf commented Apr 30, 2025

@alvestrand, this also introduces the type attribute mentioned during last WebRTC WG meeting.

@youennf youennf force-pushed the sframe-packetization-integration branch from f580cb7 to 4f74b13 Compare April 30, 2025 10:42
@youennf youennf force-pushed the sframe-packetization-integration branch from 4f74b13 to 6226b9a Compare May 22, 2025 11:39
Introduce RTCRtpScriptTransformType with "sframe" value.
@youennf youennf force-pushed the sframe-packetization-integration branch from 6226b9a to 17e6cf2 Compare May 22, 2025 11:58
@@ -181,6 +188,7 @@ A RTCRtpTransform has private slots:
* `[[readable]]` of type {{ReadableStream}}.
* `[[writable]]` of type {{WritableStream}}.
* `[[owner]]` of type {{RTCRtpSender}} or {{RTCRtpReceiver}}, initialized to null.
* `[[useSFrame]]` of type boolean. // FIXME: Decide whether augmenting this boolean with either cipher suite support or whether doing frame vs. packet based encryption.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do the FIXME as a note so it shows up in the spec?

[Exposed=Window]
interface RTCRtpScriptTransform {
constructor(Worker worker, optional any options, optional sequence<object> transfer);
constructor(Worker worker, optional any options, optional sequence<object> transfer, optional RTCRtpScriptTransformType type);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd prefer to not add more arguments to the constructor but instead reuse the options object we already overload to send to worker. I'm not super worried about name collisions.

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