Closed Bug 1945261 Opened 1 year ago Closed 1 year ago

Support dependency descriptor RTP extension

Categories

(Core :: WebRTC: Signaling, enhancement, P1)

enhancement

Tracking

()

VERIFIED FIXED
137 Branch
Tracking Status
firefox136 --- verified
firefox137 --- verified

People

(Reporter: ng, Assigned: ng)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

We should add the DD RTP header extension for simulcast / SVC.

Assignee: nobody → ngrunbaum
Status: NEW → ASSIGNED
Attachment #9463251 - Attachment description: Bug 1945261 - add dependency descriptor rtp header extension;r?pehrsons → Bug 1945261 - add dependency descriptor rtp header extension;r?pehrsons,bwc
Pushed by na-g@nostrum.com: https://hg.mozilla.org/integration/autoland/rev/ad7e19656a41 add dependency descriptor rtp header extension;r=pehrsons,bwc
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 137 Branch
Attachment #9464317 - Flags: approval-mozilla-beta?

beta Uplift Approval Request

  • User impact if declined: AV1 simulcast will not work with all media servers, e.g. jitsi which uses AV1 by default
  • Code covered by automated testing: no
  • Fix verified in Nightly: no
  • Needs manual QE test: yes
  • Steps to reproduce for manual QE testing: Go to meet.jit.si and create a room. Add 3 participants, e.g. from one instance each from Firefox Release, Chrome Release and the tested Firefox. The two participants not being on the tested Firefox may also be run on a separate machine. Check that video from the tested Firefox is received by the other participants for a few minutes straight. The network should be good to exclude video problems related to bandwidth limitations or packet loss.
  • Risk associated with taking this patch: Low
  • Explanation of risk level: Adds an RTP header extension. Main risk is in negotiation of the extension and in the libwebrtc implementation. The former has been stable for years, the latter has had plenty of bake time in libwebrtc as part of Chrome and Safari, among others.
  • String changes made/needed: None
  • Is Android affected?: yes
Flags: qe-verify+
Attachment #9464317 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
QA Whiteboard: [qa-triaged]

Verified as fixed with the following:

  1. Meeting Jitsi(~20m):
    Participant 1 MacOS 13.2.1 - Firefox Beta 136.0b3 (treeherder build)
    Participant 2 Win 11 - Chrome release
    Participant 3 Win 10 - Firefox Release
  2. Meeting Jitsi(~30m):
    Participant 1 MacOS 13.2.1 - latest Nightly
    Participant 2 Win 11 - Chrome release
    Participant 3 Win 10 - Firefox Release
  3. Meeting Jitsi(~10m):
    Participant 1 Win 10 - Firefox Beta 136.0b3 (treeherder build)
    Participant 2 MacOS 13.2.1 - Firefox Release
    Participant 2 Win 11 - Chrome release
  4. Meeting Jitsi(~10m):
    Participant 1 Win 10 - latest Nightly
    Participant 2 MacOS 13.2.1 - Firefox Release
    Participant 3 Win 11 - Chrome release
  5. Meeting Jitsi(~10m):
    Participant 1 Ubuntu 24 - Firefox Beta 136.0b3 (treeherder build)
    Participant 2 MacOS 13.2.1 - Firefox Release
    Participant 3 Win 11 - Chrome release
  6. Meeting Jitsi(~10m):
    Participant 1 Ubuntu 24 - latest Nightly
    Participant 2 MacOS 13.2.1 - Firefox Release
    Participant 3 Win 11 - Chrome release

Result: Video, audio and screen share worked as expected without problems related to bandwidth limitations or packet loss.

Blocks: 2001872
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: