Closed Bug 1801384 Opened 3 years ago Closed 3 years ago

[Experiment] Add-On Experiment: DNSSEC Interference Measurement V4 Fx 105.0 to 110.0 Release

Categories

(Shield :: Shield Study, task, P3)

Product:
Shield
Component:
Shield Study
Type:
task

Tracking

(firefox107+)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox107 + ---

People

(Reporter: experimenter, Assigned: k88hudson)

References

(
URL
)

Details

User Story

Delivery Type: Add-on experiment

    What are the branches of the experiment:

- Control dns-study.com 100%:

This is the version of the add-on which configures requests for dns-study.com (v3.2.0)
        

    What version and channel do you intend to ship to?

1% of Release Firefox 105.0 to 110.0

    Are there specific criteria for participants?


Prefs:

Experiments:

Any additional filters: Please ignore clients that have disabled telemetry.

Countries: all

Locales: all

    What is your intended go live date and how long will the experiment run?

Dec 02, 2022 - Dec 09, 2022 (7 days)

    What is the main effect you are looking for and what data will you use to
    make these decisions?

Concretely, there are two questions we intend to answer: 

1. How frequently do middleboxes between clients and recursive resolvers interfere with/drop DNSSEC record types? In other words, is it viable for Firefox to perform DNSSEC validation?
2. Do other record types (e.g. SMIMEA and an unallocated code point) get interfered with/dropped by middleboxes? In other words, is it viable to introduce new record types in a finite period of time?
3. Do certain populations of clients or ISPs experience higher failure rates?

At a high-level, both questions can be answered for each record type with the following analysis steps:

1. For each client, extract the DNS responses reported in each ping for a given record type
2. For a given record type, compare the bytes for the DNS response reported in each ping to the expected response across sessions
3. For a given record type, compute the percentage of DNS responses that do not match the expected response across sessions
4. For a given record type, compute the percentage of missing DNS responses across sessions

    Who is the owner of the data analysis for this experiment?

None

    Will this experiment require uplift?

False

    QA Status of your code:

QA Status: YELLOW for more information see https://docs.google.com/document/d/1P2GuNLPU6B5c184eNQeQ5GerHsVzYqZ4BYEIBXrg-fQ/edit

    Link to more information about this experiment:

https://experimenter.services.mozilla.com/experiments/dnssec-interference-measurement-with-per-client-measurements-v4/

DNSSEC Interference Measurement V4

We intend to measure rates of interference with DNSSEC record types by network middleboxes compared to other DNS record types.

Experimenter is the source of truth for details and delivery. Changes to Bugzilla are not reflected in Experimenter and will not change delivery configuration.

Data Science Issue: https://mozilla-hub.atlassian.net/browse/DS-12345
More information: https://experimenter.services.mozilla.com/experiments/dnssec-interference-measurement-with-per-client-measurements-v4/

[Tracking Requested - why for this release]:

tracking-firefox107: --- → ?
User Story: (updated)
Summary: [Experiment]: Add-On Experiment: DNSSEC Interference Measurement V4 → [Experiment] Add-On Experiment: DNSSEC Interference Measurement V4 Fx 105.0 to 110.0 Release
Start Date: 2022-12-02 End Date: 2022-12-09
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.