Closed Bug 1631822 Opened 5 years ago Closed 5 years ago

Choose fastest TRR as measured by TRRPerformance.jsm as default DoH provider (dry-run)

Categories

(Firefox :: Security, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
Firefox 77
Tracking Status
firefox77 --- fixed

People

(Reporter: nhnt11, Assigned: nhnt11)

References

Details

Attachments

(6 files)

  1. Extend TRRPerformance API to expose the fastest provider.
  2. Store this in a pref and send telemetry
  3. In a future release, commit this chosen value as the selected TRR.
Priority: -- → P1

This patch uses TRRPerformance.jsm to get the fastest TRR and store it in a pref
before running DoH heuristics. The chosen TRR URI is sent in a telemetry event.

Depends on D72789

Attached file Data Collection Review

Data Review for the extra telemetry event.

Attachment #9145053 - Flags: data-review?(tdsmith)
Comment on attachment 9145053 [details] Data Collection Review 1) Is there or will there be **documentation** that describes the schema for the ultimate data set in a public, complete, and accurate way? Yes, documentation will either be linked from https://docs.telemetry.mozilla.org/datasets/dynamic_telemetry.html, or the event definition will be migrated into Events.yaml before landing, and the probe dictionary will provide documentation. 2) Is there a control mechanism that allows the user to turn the data collection on and off? Yes, the Firefox telemetry opt-out. 3) If the request is for permanent data collection, is there someone who will monitor the data over time? n/a 4) Using the **[category system of data types](https://wiki.mozilla.org/Firefox/Data_Collection)** on the Mozilla wiki, what collection type of data do the requested measurements fall under? The collection reports URLs but they are chosen from a list in browser/components/doh/TRRPerformance.jsm and reflect technical measurements and not user activity, so these are Category 1, technical data. 5) Is the data collection request for default-on or default-off? Default-on. 6) Does the instrumentation include the addition of **any *new* identifiers**? No. 7) Is the data collection covered by the existing Firefox privacy notice? Yes. 8) Does there need to be a check-in in the future to determine whether to renew the data? Nihanth is response for renewing the collection as required. 9) Does the data collection use a third-party collection tool? No.
Attachment #9145053 - Flags: data-review?(tdsmith) → data-review+

(In reply to Tim Smith 👨‍🔬 [:tdsmith] from comment #7)

Comment on attachment 9145053 [details]
Data Collection Review
Yes, documentation will either be linked from
https://docs.telemetry.mozilla.org/datasets/dynamic_telemetry.html, or the
event definition will be migrated into Events.yaml before landing, and the
probe dictionary will provide documentation.

This migration into Events.yaml has been made in the relevant patch (see https://phabricator.services.mozilla.com/D72790?vs=271004&id=271042#toc)

Pushed by nhnt11@gmail.com: https://hg.mozilla.org/integration/autoland/rev/550e8058d0ad Move TRR race completion marker out of TRRPerformance.jsm. r=johannh https://hg.mozilla.org/integration/autoland/rev/313386beca32 Implement multiple TRR selection dry-run. r=valentin,johannh https://hg.mozilla.org/integration/autoland/rev/ff87b836486d Use geometric mean for fastest TRR selection. r=tdsmith,dragana https://hg.mozilla.org/integration/autoland/rev/b9652dec05a5 Return a random TRR from getFastestTRR if requested. r=johannh https://hg.mozilla.org/integration/autoland/rev/e689eca5f1a5 Exclude TRRs with more than 30% erroneous results from selection. r=dragana
Depends on: 1642723
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: