Implement TRR steering platform APIs
Categories
(Core :: Networking: DNS, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: valentin, Assigned: valentin)
References
Details
(Whiteboard: [necko-triaged][trr])
Attachments
(7 files, 1 obsolete file)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
We need the rollout addon to be able to query a DNS name and map the CNAME response to one of the TRR URIs in our list.
That URI should be used for that network, if no user choices are present that say it shouldn't be used.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Depends on D68874
Assignee | ||
Comment 3•4 years ago
|
||
TBD:
- who checks that we don't overwrite a user set trr.uri pref?
Should we do it in the addon or platform? I assume it should be the platform, but it's unclear how we would differentiate trr.uri set by the user, from trr.uri set by the rollout, when we start migrating users to other providers. We need to figure out a way to do that. - who resets the URI on network change?
Again, I assume it would be the platform, and the addon just runs heuristics again, and if needed calls the method again. During this time we'd be using the "default" URI.
Assignee | ||
Comment 4•4 years ago
|
||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Depends on D68889
Assignee | ||
Comment 6•4 years ago
|
||
Depends on D69372
Assignee | ||
Comment 7•4 years ago
|
||
Considering that we want to have multiple default TRR providers that are
chosen by the doh-rollout addon, it becomes too complex for the addon
to keep track of all of the prefs it changes, while at the same time
figuring out if the user has ever touched the same prefs.
As such, we will make the distinction that doh-rollout.uri
is only
set by the rollout addon, and network.trr.uri
is only set by user action.
So, when the any of the uri prefs change, we choose them like this:
- The user provider URI
- The addon chosen URI
- The default pref URI
Depends on D69373
Assignee | ||
Comment 8•4 years ago
|
||
This patch also exposes nsIDNSService.currentTrrURI
to be used by the UI
to display the URI currently in use by the TRR service.
Depends on D71659
Assignee | ||
Comment 9•4 years ago
|
||
Depends on D71660
Assignee | ||
Updated•4 years ago
|
Comment 10•4 years ago
|
||
Comment on attachment 9136919 [details]
Bug 1626057 - [WIP] doh-rollout steering detection r=dragana
Revision D68889 was moved to bug 1631609. Setting attachment 9136919 [details] to obsolete.
Assignee | ||
Updated•4 years ago
|
Comment 11•4 years ago
|
||
Stack landed here:
https://hg.mozilla.org/integration/autoland/rev/6dd561a7356b5ebccf996949fa39d420ef169cc3
https://hg.mozilla.org/integration/autoland/rev/a0a204057df224e513bab2ec9caaa2eb74749930
https://hg.mozilla.org/integration/autoland/rev/fad0c0132989cd59aa5cecccbd3b22f700c88d0a
https://hg.mozilla.org/integration/autoland/rev/7dc18bc57d2da0470400ea20ab1aaa2be4a2bd16
https://hg.mozilla.org/integration/autoland/rev/39f442a65b2b4a260ef300f375c25aa69874f45a
https://hg.mozilla.org/integration/autoland/rev/557d17bfcb062818e4bd88f8339eb4d3defe0678
https://hg.mozilla.org/integration/autoland/rev/f9872d8527bc85fb4746cf376be4bf07b3c63181
Comment 12•4 years ago
|
||
Assignee | ||
Updated•3 years ago
|
Description
•