Skip to content

Commit 16fd2ee

Browse files
RFC 216: webtransport_h3_cert_hash_test_server (#216)
* RFC 215: webtransport_h3_cert_hash_test_server * Update rfcs/webtransport_h3_cert_hash_test_server.md --------- Co-authored-by: Ms2ger <[email protected]>
1 parent 720ae56 commit 16fd2ee

File tree

1 file changed

+29
-0
lines changed

1 file changed

+29
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# RFC 216: WebTransport over HTTP/3 Test Server that uses a self-signed certificate for authentication with serverCertificateHashes
2+
3+
## Summary
4+
5+
Start another instance of the [WebTransport over HTTP/3](https://datatracker.ietf.org/doc/html/draft-ietf-webtrans-http3-01) server in [RFC 85](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/webtransport_h3_test_server.md) in wpt, that uses instead of the standard certificate a self-signed certificate. The hash of the certificate is passed to the test defined. The certificate is autogenerated at the startup of the wpt tests within the python code.
6+
7+
## Details
8+
9+
### Implementation
10+
11+
It is a slight modification of the server from [RFC 85](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/webtransport_h3_test_server.md) in the `tools/webtransport` directory.
12+
The implementation uses the `cryptography` lib for certificate generation, that is already used by wpt through the `aioquic` lib.
13+
14+
### Handlers
15+
See [RFC 85](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/webtransport_h3_test_server.md) for details.
16+
17+
### `wptserve` integration
18+
19+
See [RFC 85](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/webtransport_h3_test_server.md) for details.
20+
21+
A server certificate hash is autogenerated within the python code in `environment.py`. It is passed as part of the config (property `cert_hash_info`) to the tests. The tests can access the server certificate hash as `server_certificate_hash` inside the javascript templates.
22+
23+
### Dependencies
24+
25+
As of writing this RFC, the only dependency are `aioquic` as in RFC 85 and `cryptography`, which is already a dependency of `aioquic`.
26+
27+
## Risks
28+
29+
Risks are similar to [RFC #85](https://github.com/web-platform-tests/rfcs/blob/master/rfcs/webtransport_h3_test_server.md#risks), as it is a minimal modification of RFC 85, so that maintenance cost increase is neglible.

0 commit comments

Comments
 (0)