Open Bug 1806185 Opened 1 year ago

Should we handle m-sections with weird types?

Categories

(Core :: WebRTC: Signaling, defect, P4)

Product:
Core
Component:
WebRTC: Signaling
Type:
defect

Tracking

()

People

(Reporter: bwc, Unassigned)

Details

We have this wpt right now:

https://searchfox.org/mozilla-central/rev/9b8ebf06145feeccf34dc126cf45b07e86556392/testing/web-platform/tests/webrtc/protocol/unknown-mediatypes.html#22

While this is a corner case that we're unlikely to ever see in the wild, it could be argued that this test is correct, and that the correct response is to just reject the m-section with port 0, instead of failing the parse altogether.

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