Re: Significant milestone on HAProxy's H3/QUIC

Lucas Pardue <> Thu, 23 September 2021 16:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 978F13A104D for <>; Thu, 23 Sep 2021 09:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id sb1r5pA4bI70 for <>; Thu, 23 Sep 2021 09:02:57 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 31D213A0F44 for <>; Thu, 23 Sep 2021 09:02:57 -0700 (PDT)
Received: by with SMTP id hx25so230912ejc.6 for <>; Thu, 23 Sep 2021 09:02:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h3hipC41/gAzkRa8hPXAFJxMQIgvalt9cLmZ/UR/Hqw=; b=oLs4ZDp1gfcLpDv+mZnW3TPezprT6WjEi0U4rVemn2F7p0FnUlW2VugPAXJVHHFmU3 vLifNnabZJsvTPqJ2wn7IRVt5CRQ8v4i/CPUhoqGPt9hUPfPibwrhknfn8tv92H7u3RU iePjrqyrfur8pihGsk8G+AJLnvaXB/VhayJasl+5xtj0DSVfMPQUM/vFQjUxAAKf7s2z HoDPEKEiP8GlzoSiXCMNxzhp976PrzWAPSPMSqEIaIn4J590u69ARPfhl/atme5I/hFU QYaMOoykmaIFFaB7R9RJIPX+6wAhUduF+mgfOfzQyiQskZxHZsLBN7t/PwYfhPxmV3GJ mDmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=h3hipC41/gAzkRa8hPXAFJxMQIgvalt9cLmZ/UR/Hqw=; b=VG0BJimhQ4ZpKXyWx2MP0JGzNha9+eDa8g4KwrqLiipnzRHwqZT/Xl9VAvRS58BRVq 8fx1mlvJAp+O9KWQmFpR0kP2hN7m0TZzk1lvmXdbiS/fchIIuz7L84wzLXltb8k56bEi 471cJnAGhrl659LjCObaF1cvkkJA4KqHzffgUsfd0yojSOPk2nkDY1jbo31R519q4UwY T+9qTMhfEyOBuDgKaUdKTpn4JCNm3cBtEQyQJfyIHBwv1AsP2KQVpPq6+K7qD1elhT0Q YmlzZf0onyCM8BjPqKj5c5JoMnFOsNwAM6dPgkGLPRFIQxUOUzDVw4K0aPc375HJAiwE kq3w==
X-Gm-Message-State: AOAM530C8yyNpiXTgCypAsV5B7hA6gEFEc/MWL/YCFqNI2/4dZYbIwQW nqfwls7oLakP0x+vFFn47DEx3TawmwSzXOhAIIo=
X-Google-Smtp-Source: ABdhPJylg2HMS3wfs4FFYAmEmpDC1/qUmrCwOnQdYE2shLaeSY64DaOYkTSfh8Vh1lkui+bUT5s4+dVNM6cTefcEodc=
X-Received: by 2002:a17:906:6b93:: with SMTP id l19mr5971954ejr.26.1632412974954; Thu, 23 Sep 2021 09:02:54 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Lucas Pardue <>
Date: Thu, 23 Sep 2021 17:02:43 +0100
Message-ID: <>
Subject: Re: Significant milestone on HAProxy's H3/QUIC
To: Willy Tarreau <>
Cc: HTTP Working Group <>, IETF QUIC WG <>
Content-Type: multipart/alternative; boundary="0000000000007fbfe905ccabc3d5"
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:03:03 -0000

Hey Willy,

Congrats to you and the team.

On Thu, Sep 23, 2021 at 4:30 PM Willy Tarreau <> wrote:

> Hi all,
> I'm really glad to say that my coworkers Fred and Amaury are seeing
> their long tireless work on H3+QUIC start to pay off. Today I was
> pleased to see an H3 request from curl pass through HAProxy, being
> forwarded to Apache in H2, and the H2 response being routed and
> translated back to H3 so that curl could print it.
> They would have preferred that I remain discrete about it given the
> extremely fragile state of the current code, but I'm really glad as
> the project's maintainer and I'm also glad from an interoperability
> perspective, because the more implementations we see, the faster we'll
> spot and fix bugs, so I was not going to keep that for me :-)

In case you missed it, the QUIC interop runner (
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.


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

[1] -