Re: Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-22 Thread prerak jain 
On Friday, 22 September 2017 06:35:48 UTC+5:30, Nils Ohlmeier  wrote:
> Hi Prerak,
> 
> > On Sep 21, 2017, at 02:27, prerak jain  wrote:
> > 
> > Firefox gathers candidates for every track which is added to the 
> > PeerConnection object even when bundle policy is set to max-bundle. As per 
> > the specs, it should only collect candidates for any one of the media track.
> > Is there any way I can stop Firefox to gather candidates for all the tracks?
> 
> No we have not invested the time in such optimizations.
> Plus even if we gather candidates only for one bundled track, we still would 
> need to have separate candidates for RTCP in case the other side does not 
> support rtcp-mux.
> 
> Best regards
>   Nils Ohlmeier

Do you have any plan to implement the ice gathering as per the specs for max 
bundle policy. 
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media

Re: Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-22 Thread Nils Ohlmeier 
Well we have a bug for it https://bugzilla.mozilla.org/show_bug.cgi?id=1339203 
 which is in our regular 
back log.
And it is on our agenda for the rest of the year.

> On Sep 21, 2017, at 22:08, Martin Thomson  wrote:
> 
> Support for RTCP mux is now mandatory.  Nils, do you have any plans
> for trimming down the extra gathering?  I appreciate that it might be
> a low priority item.
> 
> On Fri, Sep 22, 2017 at 11:05 AM, Nils Ohlmeier  wrote:
>> Hi Prerak,
>> 
>>> On Sep 21, 2017, at 02:27, prerak jain  wrote:
>>> 
>>> Firefox gathers candidates for every track which is added to the 
>>> PeerConnection object even when bundle policy is set to max-bundle. As per 
>>> the specs, it should only collect candidates for any one of the media track.
>>> Is there any way I can stop Firefox to gather candidates for all the tracks?
>> 
>> No we have not invested the time in such optimizations.
>> Plus even if we gather candidates only for one bundled track, we still would 
>> need to have separate candidates for RTCP in case the other side does not 
>> support rtcp-mux.
>> 
>> Best regards
>>  Nils Ohlmeier
>> 
>> 
>> ___
>> dev-media mailing list
>> dev-media@lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-media
>> 



signature.asc
Description: Message signed with OpenPGP
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media

Re: Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-21 Thread Martin Thomson 
Support for RTCP mux is now mandatory.  Nils, do you have any plans
for trimming down the extra gathering?  I appreciate that it might be
a low priority item.

On Fri, Sep 22, 2017 at 11:05 AM, Nils Ohlmeier  wrote:
> Hi Prerak,
>
>> On Sep 21, 2017, at 02:27, prerak jain  wrote:
>>
>> Firefox gathers candidates for every track which is added to the 
>> PeerConnection object even when bundle policy is set to max-bundle. As per 
>> the specs, it should only collect candidates for any one of the media track.
>> Is there any way I can stop Firefox to gather candidates for all the tracks?
>
> No we have not invested the time in such optimizations.
> Plus even if we gather candidates only for one bundled track, we still would 
> need to have separate candidates for RTCP in case the other side does not 
> support rtcp-mux.
>
> Best regards
>   Nils Ohlmeier
>
>
> ___
> dev-media mailing list
> dev-media@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-media
>
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media

Re: Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-21 Thread Nils Ohlmeier 
Hi Prerak,

> On Sep 21, 2017, at 02:27, prerak jain  wrote:
> 
> Firefox gathers candidates for every track which is added to the 
> PeerConnection object even when bundle policy is set to max-bundle. As per 
> the specs, it should only collect candidates for any one of the media track.
> Is there any way I can stop Firefox to gather candidates for all the tracks?

No we have not invested the time in such optimizations.
Plus even if we gather candidates only for one bundled track, we still would 
need to have separate candidates for RTCP in case the other side does not 
support rtcp-mux.

Best regards
  Nils Ohlmeier



signature.asc
Description: Message signed with OpenPGP
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media

Firefox gather candidates for every media track even with max-bundle as bundlePolicy

2017-09-21 Thread prerak jain 
Firefox gathers candidates for every track which is added to the PeerConnection 
object even when bundle policy is set to max-bundle. As per the specs, it 
should only collect candidates for any one of the media track.
Is there any way I can stop Firefox to gather candidates for all the tracks?
___
dev-media mailing list
dev-media@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-media