Re: Consensus call for HTTP/3 server push signal handling

Ian Swett <ianswett@google.com> Wed, 01 September 2021 16:29 UTC

Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674733A0B34 for <quic@ietfa.amsl.com>; Wed, 1 Sep 2021 09:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.098
X-Spam-Level:
X-Spam-Status: No, score=-18.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.499, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrSuu-WHNWIJ for <quic@ietfa.amsl.com>; Wed, 1 Sep 2021 09:29:52 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A636B3A0B37 for <quic@ietf.org>; Wed, 1 Sep 2021 09:29:52 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id a93so6311952ybi.1 for <quic@ietf.org>; Wed, 01 Sep 2021 09:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6H6/B4Xhdeu5th0KASh6ACgYUNBY1tdUGik0pnHilwA=; b=VWYjWVByXT6cPWkGTIojjIwRqfZAepksT7iiNcYAajSwFsbEKQ7aD9x2P3UyC7HIOD agmDsviokGgjeu0pi1/yyMSqBiwGsFxnVxUElWBv1hVz/v8SmZaYgrD8e9dlZmuWe9DZ G90FI/JejHbt1clxil2jms5a/c6PSUNfXGSQtETvMJzT0fzBwnm7Aom/uaEJsyvxczVH g8nnneRXax27MEar5998wZPpy9bwECSGasIuuGHNli1g1iD6E3ow3CDaLNCJrWaUpmdT itjhyclgqDI29eGpv8QlpY0vRUdiOx1X+CLzSflkUGMHyBXPqBhCKSbb53yJ+KH62E28 AAHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6H6/B4Xhdeu5th0KASh6ACgYUNBY1tdUGik0pnHilwA=; b=FvwTR4SbaO2SDkxEztOOn8/J6KUMZkuK9kGfF9e6dPRllS0DmE/8Lbo/hwCm+4Wx3l 9fasybmg7dG1U9ABGI5tOVbH9gs1yh3/uCyTEsZ2DBgh4k0MS+E1K7hqDqBrbShOCyGd 3m4gD4KNx7AswwFJ07p416kzZ2vISdFWNKv7LQhDzsX14mxoPG3/WNzJaI0hMLCyqnas /XKlll+bXe/+Rl7U4g6gLY6Pz6SYI3xVEcdMJbZfmkCTUc8wS1dWam8EDHIpGuR1p9Jp TKuVrdBKmH4mVPQJgfY9o04FEj19HpAiV++FHVy8zdG1BgdxEnAZm1DlxzsXP2MpC/xE iWfQ==
X-Gm-Message-State: AOAM531yFOuk33Bl222Jms4x2YfZYrLJE4jdvqdSNJiewNE6WYHZDVI+ 5yfSrmBqn3LjkXvys4xdvuxemvyYAk63kwdk0vQkrQIlOFwYDQ==
X-Google-Smtp-Source: ABdhPJzpzugZTBgaJWazdBicSFUCNSjLFwLsMG1Jd7f/CLV0Vu9DFeP92uko3Q4eDULePCeG8oY3/lDq8UlHmrBpocM=
X-Received: by 2002:a25:d892:: with SMTP id p140mr459208ybg.406.1630513789515; Wed, 01 Sep 2021 09:29:49 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oYZm5j=33xzpC=v3TJBEtcV3x-JmfuC-EE7vndKr0cDkA@mail.gmail.com>
In-Reply-To: <CALGR9oYZm5j=33xzpC=v3TJBEtcV3x-JmfuC-EE7vndKr0cDkA@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 1 Sep 2021 12:29:38 -0400
Message-ID: <CAKcm_gO+HcViPHZkP7haf=hL=VghBHo9p=JLNzzYp1TA=5K4=w@mail.gmail.com>
Subject: Re: Consensus call for HTTP/3 server push signal handling
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: QUIC WG <quic@ietf.org>, quic-ads@ietf.org, QUIC WG Chairs <quic-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a157e05caf1935e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/i-gR68HkIaLJvvu3l_3vAEYJ9Dg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2021 16:29:56 -0000

As I expressed on the issue, I'd rather remove push, but this seems
acceptable as well.

Ian

On Tue, Aug 31, 2021 at 7:01 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> 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
> https://github.com/quicwg/base-drafts/pull/4931. 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
> https://github.com/quicwg/base-drafts/pull/4931. Absent any pushback,
> we'll work with our AD on the next steps for incorporation.
>
> Best Regards,
> Matt & Lucas
> QUIC WG Chairs
>
>
> [1] - https://github.com/quicwg/base-drafts/issues/4930
>