[Meta] Tracking for ICE TCP user pref to be turned on

NEW
Unassigned

Status

()

defect
P2
normal
Rank:
12
4 years ago
8 months ago

People

(Reporter: drno, Unassigned)

Tracking

(Depends on 7 bugs, {dev-doc-complete, meta})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox41 affected)

Details

Bug 891551 landed ICE TCP with the user pref set to off by default.

This bug is a reminder that we want/need to switch that pref to on at some point in the future.
Points: 1 → ---
Rank: 20
For the reference: the pref is called media.peerconnection.ice.tcp
We probably want at least bug 1176407 to be resolved before considering switching it on by default.
Depends on: 1176407
Depends on: 1176377
backlog: --- → webRTC+
Rank: 20 → 15
Priority: P2 → P1
I know Nils is planning to own and deliver this in Q3 (targeting fx42).
Assignee: nobody → drno
Depends on: 1179345, 950660
Depends on: 1185197
Depends on: 1185198
Depends on: 1186339
Depends on: 1189198
Depends on: 1194010
Depends on: 1194019
Depends on: 1195396
Depends on: 1206981
Depends on: 1206465
Depends on: 1207451
Depends on: 1208276
Depends on: 1208278
Depends on: 1213442
Summary: Switch ICE TCP user pref to on → [Meta] Tracking for ICE TCP user pref to be turned on
Depends on: 1208762
Rank: 15 → 12
Depends on: 1244926
Depends on: 1254891
Depends on: 1264351
Depends on: 1266667
Depends on: 1297158
@mreavy: with bug 1266667 landed I think we have the minimum in place to flip the ICE TCP user pref on, which will only activate active ICE TCP connections on e10s and non-e10s.

To reasons to still hold off on flipping the switch are:
1) since bug 1285318 landed we longer have a STUN filter for ICE TCP under e10s.
2) we don't have any good Telemetry data which tells us how often ICE TCP gets used.
Depends on: 1285330
(In reply to Nils Ohlmeier [:drno] from comment #4)
> 1) since bug 1285318 landed we longer have a STUN filter for ICE TCP under
> e10s.

Further discussion regarding the missing filter should happen in bug 1285330
Depends on: 1335939
I'm told this is preffed on in Firefox 54; I have noted it on Firefox 54 for developers (https://developer.mozilla.org/en-US/Firefox/Releases/54#AudioVideo).

I also added to Experimental features in Firefox (https://developer.mozilla.org/en-US/Firefox/Experimental_features) that this was first implemented in Firefox 41, preffed off.

When I get a link to the blog post I'm told :drno is writing, I'll link to it (unless someone else does first).

That aside, this is now doc complete.
(In reply to Eric Shepherd [:sheppy] from comment #6)
> I'm told this is preffed on in Firefox 54; I have noted it on Firefox 54 for
> developers
> (https://developer.mozilla.org/en-US/Firefox/Releases/54#AudioVideo).
> 
> I also added to Experimental features in Firefox
> (https://developer.mozilla.org/en-US/Firefox/Experimental_features) that
> this was first implemented in Firefox 41, preffed off.
> 
> When I get a link to the blog post I'm told :drno is writing, I'll link to
> it (unless someone else does first).
> 
> That aside, this is now doc complete.

If this is preffed on in Nightly only, I think maybe we should clarify that in the release note? Is that the case here?
Flags: needinfo?(eshepherd)
(In reply to Chris Mills (Mozilla, MDN editor) [:cmills] from comment #7)
> If this is preffed on in Nightly only, I think maybe we should clarify that
> in the release note? Is that the case here?

No. It is preffed on in 54 and the pref change rides the trains to release (at least that is the plan).
Flags: needinfo?(eshepherd)
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
I don't have the capacity any more to work on this any time soon.
Assignee: drno → nobody
You need to log in before you can comment on or make changes to this bug.