Re: [quicwg/base-drafts] Retain use of SETTINGS_ENABLE_PUSH (#718)
Mike Bishop <notifications@github.com> Fri, 01 June 2018 20:35 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 E2DDE12DA19 for <quic-issues@ietfa.amsl.com>; Fri, 1 Jun 2018 13:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 Q6SIZG8HRoMF for <quic-issues@ietfa.amsl.com>; Fri, 1 Jun 2018 13:35:10 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B37B12D9FE for <quic-issues@ietf.org>; Fri, 1 Jun 2018 13:35:10 -0700 (PDT)
Date: Fri, 01 Jun 2018 13:35:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1527885309; bh=7aMhcivhi8P8+GbBh9+QJG6q5s27ozzLKoERPInL2ro=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Zd9UdK0KGT9Nd2IjuOh/4rLq+fwzPTjKHmR82EohsdLok//+e3+XEF9CJgRrnUDmp 6JvUFNI+7F99nr2EHV1tjzpC+jVtfoFrSXKAtcpyVhkUq6F2SEpL4uOcSOXw004ioS zepttDIgkMHLB0GZmVwChD99SEI0ySJIhyyol82o=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6080ba8e6ad29d71b964752700d6474ca1123b6d92cf0000000117296ffd92a169ce0eda8cd0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/718/394001534@github.com>
In-Reply-To: <quicwg/base-drafts/issues/718@github.com>
References: <quicwg/base-drafts/issues/718@github.com>
Subject: Re: [quicwg/base-drafts] Retain use of SETTINGS_ENABLE_PUSH (#718)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b11adfd33c01_30ca3fc095108f841837ae"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/9aA_SqXUhmbpwMAKwHGnDoqdjTo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 01 Jun 2018 20:35:12 -0000
Following the logic in #1359, if we treat push as being an extension which defines a few frames and a stream type, then clients should have an opt-in setting declaring that all the push-specific things are supported. If that PR gets merged, the only "privileged" thing about push in the core protocol is that PRIORITY can prioritize/depend on a push stream. I'm almost tempted, as part of this and removing Flags, to say that requests can't depend on pushes and split out a PUSH_PRIORITY frame so that it's totally disjoint. -- 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/718#issuecomment-394001534
- [quicwg/base-drafts] Retain use of SETTINGS_ENABL… janaiyengar
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Martin Thomson
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… janaiyengar
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Martin Thomson
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Lucas Pardue
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Martin Thomson
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Martin Thomson
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Martin Thomson
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop
- Re: [quicwg/base-drafts] Retain use of SETTINGS_E… Mike Bishop