You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the algorithm for generating subsequent offers in [RTCWEB-JSEP] section 5.2.2, replace "The RTP header extensions MUST only include those that are present in the most recent answer" with "For each RTP header extension listed in [[HeaderExtensionsToOffer]] that is also present in the most recent answer, and where direction is not "stopped", generate an appropriate "a=extmap" line with "direction" set according to the rules of [RFC5285] section 6, considering the direction in [[HeaderExtensionsToOffer]] to indicate the answerer's desired usage". This preserves the property that the set of extensions may not grow with subsequent offers."
But RFC5285, section 6 says:
A session update MAY add or remove extension(s)
Given that extmap-allow-mixed is now turning default as of https://webrtc-review.googlesource.com/c/src/+/197943, there's soon no crisis anymore with the number of header extensions in use. I propose we drop the restriction.
The text was updated successfully, but these errors were encountered:
Here's some of the underlying rationale for the JSEP logic, FWIW. This particular part applies to PT selection but the same may also apply to header extension ID selection. rtcweb-wg/jsep#266 (comment)
But RFC5285, section 6 says:
Given that extmap-allow-mixed is now turning default as of https://webrtc-review.googlesource.com/c/src/+/197943, there's soon no crisis anymore with the number of header extensions in use. I propose we drop the restriction.
The text was updated successfully, but these errors were encountered: