Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)

Lucas Pardue <notifications@github.com> Tue, 05 February 2019 15:50 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 DC2931271FF for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 07:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 bX0lZzdiOJZJ for <quic-issues@ietfa.amsl.com>; Tue, 5 Feb 2019 07:50:43 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD1A012008A for <quic-issues@ietf.org>; Tue, 5 Feb 2019 07:50:43 -0800 (PST)
Date: Tue, 05 Feb 2019 07:50:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549381842; bh=p/6Zt5fwqxjtIsOFwT95bjGyM575VGCAr/5iRD/3SDc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0/91y8VxAxSjrj5l8KBxxElGIF/h+JO9KgHsp5PD3TKuCNRd3a9XFUsj6xMXZqNYR ow3ySvssZNlvazMSTxCq9MnjAhyiPVHfGKlBH7YOWZ0A17N8sAxR0vt8FpxBh1mGss 13YVsk4R0+VcAV3kogycx9A+/lf7pyeaeIOJJnas=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe17eca4741b0872edd43cfdf471a6e69c939d57492cf00000001187172d292a169ce183df2cd@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2418/460689489@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2418@github.com>
References: <quicwg/base-drafts/issues/2418@github.com>
Subject: Re: [quicwg/base-drafts] Consider a new stream type to act like MAX_PUSH_ID (#2418)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c59b0d2cdd35_53933f8b308d45b4347494"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/QKTejv3CpdHgBvxsLJBd32D7pBE>
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: Tue, 05 Feb 2019 15:50:46 -0000

It might also solve the problem that the server cannot tell the client that there will be no server push used in a H3 session. You could do that with this design by resetting the "push control stream" or whatever we want to call it. 

This is a different way to achieve the lack of SETTINGS_(DIS|EN)ABLE_PUSH that we no longer have.

-- 
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/2418#issuecomment-460689489