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

[Christer Holmberg <[e-mail]>]

Hi,

>>>> It would be nice to get input from a few more people - especially from those that don't use libwebrtc in the implementations. 
>>>
>>> First of all, SDP processing is not technically part of libwebrtc. Firefox, Chromium, and Safary have different code for that.
>>
>> Ok, so why have people been talking about libwebrtc? My understanding was that it doesn't support bundle-only etc.
>
> libwebrtc has a reference implementation of  SDP processing. I think it will at least accept bundle-only.

Ok, but then it won't be able to *receive* an initial offer with port zero + bundle-only either, will it? 

>>> Second, our code already works with existing implementations (i.e. identical ports for m= lines). Switching it to port 0 in Firefox caused some breakage but it was fixed as well. So, at this point, we do not care.
>>
>> Ok. And, I assume you are talking about an intermediary entity (proxy, SBC etc), right?
>
> It was in the basic SDP processing library that we use. It would short circuit parsing m= lines with port zero and do not parse any of the attributes. This code was previously added to avoid failing SDP parsing with malformed SDP attributes in disabled m= lines.

Ok. I can see how that could happen. But, then the result would at least be predictable - the m= lines with port zero would be disabled, but you could still get a session with the non-zero m= lines. 

Regards,

Christer