Re: Significant milestone on HAProxy's H3/QUIC

Willy Tarreau <> Thu, 23 September 2021 16:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF1513A1101 for <>; Thu, 23 Sep 2021 09:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KQYy_26ilGqp for <>; Thu, 23 Sep 2021 09:09:36 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id AEA3B3A10BA for <>; Thu, 23 Sep 2021 09:09:35 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 18NG9WOr021039; Thu, 23 Sep 2021 18:09:32 +0200
Date: Thu, 23 Sep 2021 18:09:32 +0200
From: Willy Tarreau <>
To: Lucas Pardue <>
Cc: HTTP Working Group <>, IETF QUIC WG <>
Subject: Re: Significant milestone on HAProxy's H3/QUIC
Message-ID: <>
References: <> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 23 Sep 2021 16:09:50 -0000

Hi Lucas,

On Thu, Sep 23, 2021 at 05:02:43PM +0100, Lucas Pardue wrote:
> Hey Willy,
> Congrats to you and the team.

Thanks for them :-)

> In case you missed it, the QUIC interop runner (
> supports

Oh I completely forgot about it when it was shared a long time ago! Thanks
for the reminder (probably they already know about it and will have a great
laugh at me).

> automated interop of lots of clients and servers. If you're familiar with
> Docker, it isn't
> too much work to set up an image for your implementation that can be used
> to test
> locally or get added to the interop runner itself. Instructions are here
> [1]. You can tailor
> test cases towards the bits you actively support and develop.

That's indeed something we should consider once we have something that
looks more robust. For now it's still limited to being used by haproxy

> P.S. and as always hat-tip to Marten et al who help keep the interop
> runner... running

Definitely! Such interop tests are crucial for any protocol and are very
hard to perform by each individual project's developers.