simplequicping: like tlsping but for quic #2091
Assignees
Labels
methodology
issues related to the testing methodology
new nettest
ooni/probe-engine
priority/medium
Normal priority issue
research prototype
Comments
bassosimone
added
priority/medium
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 9, 2022
bassosimone
added a commit
to ooni/spec
that referenced
this issue
May 9, 2022
This was referenced May 9, 2022
bassosimone
added a commit
to ooni/spec
that referenced
this issue
May 9, 2022
See ooni/probe#2091 (issue) and ooni/probe-cli#717 (impl). While there, ensure we remove the `oddity` from the JSON examples, since it's non standard and most likely we're going to remove oddities after community feedback (see ooni/probe#2034).
bassosimone
added a commit
to ooni/probe-cli
that referenced
this issue
May 9, 2022
See ooni/probe#2091 (issue) and ooni/spec#237 (spec).
|
Done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is about writing a generic/simple way of running a QUIC ping like we do for tlsping. This new experiment would be much simpler and higher level than the existing QUIC ping. We would not need to manually perform crypto, rather we just need to sit on top of the existing
lucas-clemente/quic-golibrary. Accordingly, the simple QUIC ping will answer different questions such as whether we could use QUIC to connect to an endpoint. Conversely, the existing QUIC ping answers much more low-level questions that are related to understanding how QUIC is blocked on the wire.The text was updated successfully, but these errors were encountered: