Re: [quicwg/base-drafts] Handling of a lost push signal (#4930)

ianswett <notifications@github.com> Thu, 29 July 2021 15:01 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADF483A2577 for <quic-issues@ietfa.amsl.com>; Thu, 29 Jul 2021 08:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.46
X-Spam-Level:
X-Spam-Status: No, score=-7.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.452, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 pQCAlZeZtWyr for <quic-issues@ietfa.amsl.com>; Thu, 29 Jul 2021 08:01:49 -0700 (PDT)
Received: from smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 644133A2558 for <quic-issues@ietf.org>; Thu, 29 Jul 2021 08:01:49 -0700 (PDT)
Received: from github.com (hubbernetes-node-4c0e459.ash1-iad.github.net [10.56.121.19]) by smtp.github.com (Postfix) with ESMTPA id 70C315E0801 for <quic-issues@ietf.org>; Thu, 29 Jul 2021 08:01:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1627570908; bh=iSbbv/vba0nP41sjpEi1Pdnh160KKgxsi6NLkqrFJTo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=eM7G3DmLEFYZTjNaR5SZ3VY5NVoVTyeqOYdysQ9la3lq7xypTzkozdrMI1cvJvxse w+HM6k0YVwWYy9N564i3gaGbW5GiJPW6BKmQP4kvClLltmNSPE11+h4gdI5x8r/4rO u8zOIoW8RYlOK/3Ai8v0sTiZRa8insJ5pAe5gASc=
Date: Thu, 29 Jul 2021 08:01:48 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4EBBJMH4JX3AI2WBV7B2R5ZEVBNHHDR4HSDQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4930/889220689@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4930@github.com>
References: <quicwg/base-drafts/issues/4930@github.com>
Subject: Re: [quicwg/base-drafts] Handling of a lost push signal (#4930)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_6102c2dc6e56f_49c724151611"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/dMDLHPgj2Y9T0wM2kdholECx21I>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jul 2021 15:01:58 -0000

I also support moving this to a future extension, given the discussion above.

I'll note that we made the decision as a WG to ship 'h3' when the transport drafts shipped.  I think that greatly limits the scope of any changes we can make to the existing push design using the existing SETTING.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4930#issuecomment-889220689