I’ve been revisiting Nginx HTTP/3 over QUIC/UDP and was wondering what are k6’s plans for HTTP3/QUIC ? Previously for HTTP/3 load testing I built a HTTP/3 supported version of h2load. But would be nice if k6 had support too 
nginx -V
nginx version: nginx/1.23.2 (011122-105436-centos7-d9e494b-br-6e975bc)
built by gcc 11.2.1 20220127 (Red Hat 11.2.1-9) (GCC)
built with OpenSSL 1.1.1q+quic 5 Jul 2022
curl -Ikv --http3 https://domain1.com/
* Trying 111.222.333.444:443...
* Connect socket 5 over QUIC to 111.222.333.444:443
* Skipped certificate verification
* Connected to domain1.com (111.222.333.444) port 443 (#0)
* h2h3 [:method: HEAD]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: domain1.com]
* h2h3 [user-agent: curl/7.85.0]
* h2h3 [accept: */*]
* Using HTTP/3 Stream ID: 0 (easy handle 0xa80c30)
> HEAD / HTTP/3
> Host: domain1.com
> user-agent: curl/7.85.0
> accept: */*
>
* ngh3_stream_recv returns 0 bytes and EAGAIN
< HTTP/3 200
HTTP/3 200
< date: Tue, 01 Nov 2022 11:27:01 GMT
date: Tue, 01 Nov 2022 11:27:01 GMT
< content-type: text/html; charset=utf-8
content-type: text/html; charset=utf-8
< content-length: 2
content-length: 2
< last-modified: Sun, 16 Oct 2022 02:09:43 GMT
last-modified: Sun, 16 Oct 2022 02:09:43 GMT
< vary: Accept-Encoding
vary: Accept-Encoding
< etag: "634b67e7-2"
etag: "634b67e7-2"
< server: nginx centminmod
server: nginx centminmod
< x-powered-by: centminmod
x-powered-by: centminmod
< x-cache-status: MISS
x-cache-status: MISS
< accept-ranges: bytes
accept-ranges: bytes
<
* Connection #0 to host domain1.com left intact
