Re: [MMUSIC] [rtcweb] Updating JSEP and BUNDLE

Hi,

The initial offer issue has nothing to do with the JSEP/BUNDLE misalignment issue. I don’t think they shall be bundled (no pun intended) together.

Regards,

Christer

From: Justin Uberti <juberti@google.com>
Sent: keskiviikko 27. tammikuuta 2021 3.18
To: Roman Shpount <roman@telurix.com>
Cc: Murray S. Kucherawy <superuser@gmail.com>; Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>; mmusic@ietf.org; Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] [rtcweb] Updating JSEP and BUNDLE

On Tue, Jan 26, 2021 at 3:04 PM Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:
I just like to note that the current implementation is not following either JSEP or BUNDLE. At least one current implementation sends identical ports in the initial offer, which is not compliant with either specification. Switching to BUNDLE might not be backward compatible.

Right, which means that we have more possibilities to consider besides the ones that Christer mentioned.

I think we need to split the problem into three parts:
a) what should JSEP endpoints put into initial offers, when in max-bundle mode?
b) what should JSEP endpoints put into initial offers, when in balanced mode?
c) what should all endpoints do in answers and re-offers (regardless of mode)?

For a), we need to come up with something that doesn't break existing applications that don't expect to get port zero. Since this is not the default mode, I don't think we have to worry as much about the particulars of offer-answer.

For b), given that most apps in this mode won't actually end up offering a zero port, I think we have a lot of flexibility in what solution we choose (i.e., the risk of app breakage may not be the dominant constraint).

c) may actually be the most significant decisioni, since it changes the behavior for just about every existing app (i.e., offerers will now start getting zero ports in their answers, regardless of mode). So I think we really just have to decide if there is a technical reason to prefer the BUNDLE behavior over the JSEP behavior, given the risks of such a change.

On Tue, Jan 26, 2021 at 5:51 PM Murray S. Kucherawy <superuser@gmail.com<mailto:superuser@gmail.com>> wrote:
On Tue, Jan 26, 2021 at 11:02 AM Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:
> I think the revised charter takes this into account.  Please let me know if it needs any other corrections.

It needs to be clear that the charter is about fixing the misalignment between the BUNDLE and JSEP specifications - nothing more, nothing less.

Do you think the current charter text needs to be adjusted?  If so, do you have a suggestion?

-MSK
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic