[webrtc-extensions] Header extension control: spec text inconsistent with RFC5285 section 6. (#60)

handellm has just created a new issue for https://github.com/w3c/webrtc-extensions:

== Header extension control: spec text inconsistent with RFC5285 section 6. ==
> 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.

Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/60 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 18 December 2020 13:55:04 UTC