Consensus call for HTTP/3 server push signal handling

Lucas Pardue <> Tue, 31 August 2021 23:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A1C0C3A08C0; Tue, 31 Aug 2021 16:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Status: No, score=-1.848 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] 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 XQb9qv6beDzw; Tue, 31 Aug 2021 16:00:28 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 186FA3A0D35; Tue, 31 Aug 2021 15:59:59 -0700 (PDT)
Received: by with SMTP id u3so2465871ejz.1; Tue, 31 Aug 2021 15:59:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=n0I+7XFEa9wYmqBBh7TZK22sX8CB+J+m4+gdk74QvZo=; b=M+KcDj9cFjr0irh8AZhf1CXOK7cb548jFrh2C5MB/YVO0T/URe/qQ8g1X7j9pnvrGC FYMcqJ2HoAN1XVOQy5ZDqhBKHZViYmy1Wllm239DLz3dqWeoF4UoEquCiOh/Fg3TXjd7 hQd81cG6jzFeolwOki8rwbAvD/PMI4z6tCc4e8ceExBU3EAbLoVqoHo7qbaVdxmf9IcL u5TPxxNQSbgzhvH1lkybZumakAKOCAO1RRi8Ebf0mA49mrmb4YlfHCdnF2mLPU2cCN/B SzI5YDCQqhvxiR+zcsTpuC+NMaoW/vQV6elAqUMrbeNBz8RCsm4t4ZJaqFkXtvzQf0Eb 1s6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=n0I+7XFEa9wYmqBBh7TZK22sX8CB+J+m4+gdk74QvZo=; b=pI9R1NoZyWgCulZNvUKx68g3WcbEgpXU4llrknJmHYZWdvTOkmAqH9kwPWyw6gFOX7 BEwKH0cXzBmLV9IM72fs+xaClaHmbRjbj9q9TCcbprRCs51FXUghYRgBSwx67h2o4VgK NnwFMjNKb8by2GhE2s0Qs0qD+4umLvCpg5cg1nWU4J9dQFMXnN2tGXFwqPLqWVtvMM4E 3cZsMBm6GCnnQvtHLHdr2/0+TMMLdpf2mgW+a25XE6F4yBotAH/4HFtyP18OnBdf5P25 SDK2FfBlf1Ma8JuTJPyHLeDf3d2pNDxiGHd6nXT5tG3z7ARGVq15iMcDnTLoEnE9SAyJ ne7g==
X-Gm-Message-State: AOAM5315lyywD5TmSZv8l6L4XmfJqG07w2fAS53jJgEkPYOlK0WFBwxE /op+8ZYUz5zsZ/y999L1QS3pqPDU8TbMqxqpxtkX7Qg+kOs=
X-Google-Smtp-Source: ABdhPJzkxFkj0YtCkirmKz59OsA7RGxK+wYyGjGp1kpJdRSOOrDpLA2BXyDm5Wp3J657bc7L89Q0c4gH5Fet4NUfggY=
X-Received: by 2002:a17:906:2c14:: with SMTP id e20mr33773731ejh.46.1630450795456; Tue, 31 Aug 2021 15:59:55 -0700 (PDT)
MIME-Version: 1.0
From: Lucas Pardue <>
Date: Tue, 31 Aug 2021 23:59:44 +0100
Message-ID: <>
Subject: Consensus call for HTTP/3 server push signal handling
To: QUIC WG <>
Cc:, QUIC WG Chairs <>
Content-Type: multipart/alternative; boundary="0000000000007cae7c05cae2e8f1"
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: Tue, 31 Aug 2021 23:00:34 -0000

Hello WG,

Back in July there was some discussion about potential edge cases related
to HTTP/3 server push, leading to issue #4930 "Handling of a lost push
signal" [1] being raised. As a reminder, draft-ietf-quic-http is now in the
RFC Editor queue following WGLC, IETF Last Call, and gaining approval from
the IESG.

The proposed resolution to this issue is The editor has been
careful to craft things in such a way to have minimal impact on the HTTP/3
protocol, while addressing the points raised in issue #4930.

Our responsible AD has asked us to run a consensus call to ensure that the
WG is happy with this change, before it is incorporated into the document
as part of AUTH48. This email begins a 1-week consensus call (ending
September 7 2021, anywhere on earth) for the proposed resolution at Absent any pushback, we'll
work with our AD on the next steps for incorporation.

Best Regards,
Matt & Lucas
QUIC WG Chairs

[1] -