Closed Bug 2014357 Opened 7 months ago Closed 1 month ago

Enable two byte RTP header extension ids

Categories

(Core :: WebRTC, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
155 Branch
Tracking Status
firefox155 --- fixed

People

(Reporter: ng, Assigned: ng)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file, 2 obsolete files)

This has been available for a while upstream. We should enable it.

This is an experimental revision in which I am trying to use Phabricator to
review a patch created by Claude Code.

See Also: → 1340372
See Also: → 2019469
Assignee: nobody → ngrunbaum
Severity: S4 → S2

note: putting extmap-allow-mixed in the SDP suggesting that mixing one and two byte extension is allowed and then not supporting two byte is a bit weird. Also this should be nominated for interop2026?

note: Chromium is likely to send two-byte header extensions in more cases going forward - we have more than 14 extensions that we may want to use (so far, the set of default enabled extensions is less than 15, but it could flip any day).

Attachment #9545256 - Attachment description: WIP: Bug 2014357 - fully support 2 byte headers → WIP: Bug 2014357 - fully support 2 byte headers;r=bwc
Attachment #9545256 - Attachment description: WIP: Bug 2014357 - fully support 2 byte headers;r=bwc → Bug 2014357 - fully support extmap-allow-mixed;r=bwc
Attachment #9608986 - Attachment is obsolete: true
Attachment #9606851 - Attachment is obsolete: true
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
QA Whiteboard: [qa-triage-done-c156/b155]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: