From 02c351e5d158e0cd8ea7ee1e38b973b576f4e461 Mon Sep 17 00:00:00 2001 From: Marten Seemann Date: Sat, 28 Oct 2023 13:27:00 +0700 Subject: [PATCH] update links to repository after moving it to quic-interop org (#325) --- README.md | 2 +- implementations.json | 2 +- trace.py | 2 +- web/index.html | 6 +++--- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 2b623bbf..ef67ada7 100644 --- a/README.md +++ b/README.md @@ -30,7 +30,7 @@ To enable IPv6 support for the simulator on Linux, the `ip6table_filter` kernel ## Building a QUIC endpoint -To include your QUIC implementation in the Interop Runner, create a Docker image following the instructions for [setting up an endpoint in the quic-network-simulator](https://github.com/marten-seemann/quic-network-simulator), publish it on [Docker Hub](https://hub.docker.com) and add it to [implementations.json](implementations.json). Once your implementation is ready to interop, please send us a PR with this addition. Read on for more instructions on what to do within the Docker image. +To include your QUIC implementation in the Interop Runner, create a Docker image following the instructions for [setting up an endpoint in the quic-network-simulator](https://github.com/quic-interop/quic-network-simulator), publish it on [Docker Hub](https://hub.docker.com) and add it to [implementations.json](implementations.json). Once your implementation is ready to interop, please send us a PR with this addition. Read on for more instructions on what to do within the Docker image. Typically, a test case will require a server to serve files from a directory, and a client to download files. Different test cases will specify the behavior to be tested. For example, the Retry test case expects the server to use a Retry before accepting the connection from the client. All configuration information from the test framework to your implementation is fed into the Docker image using environment variables. The test case is passed into your Docker container using the `TESTCASE` environment variable. If your implementation doesn't support a test case, it MUST exit with status code 127. This will allow us to add new test cases in the future, and correctly report test failures und successes, even if some implementations have not yet implented support for this new test case. diff --git a/implementations.json b/implementations.json index 5330d742..fa5017d0 100644 --- a/implementations.json +++ b/implementations.json @@ -51,7 +51,7 @@ }, "chrome": { "image": "martenseemann/chrome-quic-interop-runner", - "url": "https://github.com/marten-seemann/chrome-quic-interop-runner", + "url": "https://github.com/quic-interop/chrome-quic-interop-runner", "role": "client" }, "xquic": { diff --git a/trace.py b/trace.py index 3bcf45b7..02ae13b6 100644 --- a/trace.py +++ b/trace.py @@ -105,7 +105,7 @@ def _get_packets(self, f: str) -> List: self._filename, display_filter=f, override_prefs=override_prefs, - disable_protocol="http3", # see https://github.com/marten-seemann/quic-interop-runner/pull/179/ + disable_protocol="http3", # see https://github.com/quic-interop/quic-interop-runner/pull/179 decode_as={"udp.port==443": "quic"}, ) packets = [] diff --git a/web/index.html b/web/index.html index 2b9e6cbe..ce617c09 100644 --- a/web/index.html +++ b/web/index.html @@ -10,10 +10,10 @@ - Fork me on GitHub + Fork me on GitHub