1310259 - Get TLS connection test pings out of the "OTHER" bucket

Status: RESOLVED FIXED

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P1)

Description

[Eric Rescorla (:ekr)]

I am fine with any string name, but I suggest "tls-connection-test".

Comment 1

[Mark Reid [:mreid]]

Per email discussion, let's name it "tls-13-study". Sound OK ekr?

Rebecca, we'd like to request Data Collection approval for this new Telemetry ping type.

Comment 2

[[e-mail]]

Quick assertions:

1) We want this opt-out for release, or all channels?
2) We want this forever or for a limited amount of time?  If limited, for how long?
3) From an analyst perspective, does ekr (who I believe is principal analyst) require anything beyond a.t.m.o / Spark support?  
4) :ekr, for posterity, can you provide a very brief description of the question you are asking and how this custom ping type will allow you to answer it?

Comment 3

[Eric Rescorla (:ekr)]

1. All channels
2. Forever, I think, because I imagine we are going to want to do a series of such studies.
3. If the question here is: do I need someone to help with the analysis then no.
4. We are attempting to compare various versions/configurations of TLS. The experiment is that we have a set of servers with different configs and we hit each of them with the same Firefox and compare the results. We currently care about error rates (due to middleboxes and the like) but in the future we will probably add a 0-RTT test and so then we will care about performance as well.

Comment 4

[Mark Reid [:mreid]]

Sent a PR to add this:
https://github.com/mozilla-services/puppet-config/pull/2347

Comment 5

[[e-mail]]

signing off for data review

Comment 6

[Wesley Dawson [:whd]]

The PR has been merged and deployed.

Comment 7

[Mark Reid [:mreid]]

Document type "tls-13-study" will now be stored separately from the OTHER bucket.