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 AAFC9130DCE
 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 20:07:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level: 
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 6T8aIdcTH_OM for <quic-issues@ietfa.amsl.com>;
 Thu, 20 Dec 2018 20:07:01 -0800 (PST)
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 043C812D7EA
 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 20:07:01 -0800 (PST)
Date: Thu, 20 Dec 2018 20:07:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1545365220;
 bh=GRZARUncOCW36b1OHSHfPK5DKTH73id6gwLl3X6Eaqo=;
 h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
 List-Archive:List-Post:List-Unsubscribe:From;
 b=ZlolM57tYL3FJSw+i/gd+U7H0DWRr6/Qj1GYw6Dc3Uy+O/MMBL/F+zdk7EHq12PmJ
 KPz0YmIZVErzRA3OuHs0R3EoqDWDS5W+uY7g+dx3iNKk+HxZAs3KOV0bKLaWV+tQBu
 GM1Ds9SF3FglcY2fKLWciPHjc7EE7ZTillAKE9rE=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4ab393a11e369ba0a88da96cee251c1d6e2a38b24a192cf00000001183428e492a169ce177070bb@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2227/449238933@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2227@github.com>
References: <quicwg/base-drafts/issues/2227@github.com>
Subject: Re: [quicwg/base-drafts] It's annoying that one can't send push in
 0.5RTT (#2227)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c1c66e441104_18bc3fb0b4ad45b861816f";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/UIjgxKSYXPZmj3nTIBxNlD-334E>
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: Fri, 21 Dec 2018 04:07:02 -0000


----==_mimepart_5c1c66e441104_18bc3fb0b4ad45b861816f
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

We discussed pushes without a request as context in h2, and concluded that they were very difficult.  Using the request as context is what made it possible to support push at all in cases where there are multiple users of the same connection (a common occurrence).

I can see how using 0.5 RTT for pushing some content is appealing, such as origin policy, favicons, or other such common resources.  However, I see that as an entirely new feature.

-- 
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/2227#issuecomment-449238933
----==_mimepart_5c1c66e441104_18bc3fb0b4ad45b861816f
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>We discussed pushes without a request as context in h2, and concluded =
that they were very difficult.  Using the request as context is what made=
 it possible to support push at all in cases where there are multiple use=
rs of the same connection (a common occurrence).</p>
<p>I can see how using 0.5 RTT for pushing some content is appealing, suc=
h as origin policy, favicons, or other such common resources.  However, I=
 see that as an entirely new feature.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/2227#issuecomment-449238933">view it on GitHub</a>,=
 or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq3Mn=
ei7lWaNS6WLOAir4b76qmW8Xks5u7F5kgaJpZM4ZdDxb">mute the thread</a>.<img sr=
c=3D"https://github.com/notifications/beacon/AWbkq9YSaZ03Ur9VWhjpcVrug1u5=
-imJks5u7F5kgaJpZM4ZdDxb.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
martinthomson in #2227: We discussed pushes without a request as context =
in h2, and concluded that they were very difficult.  Using the request as=
 context is what made it possible to support push at all in cases where t=
here are multiple users of the same connection (a common occurrence).\r\n=
\r\nI can see how using 0.5 RTT for pushing some content is appealing, su=
ch as origin policy, favicons, or other such common resources.  However, =
I see that as an entirely new feature."}],"action":{"name":"View Issue","=
url":"https://github.com/quicwg/base-drafts/issues/2227#issuecomment-4492=
38933"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/issues/2227#issuecomment=
-449238933",
"url": "https://github.com/quicwg/base-drafts/issues/2227#issuecomment-44=
9238933",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c1c66e441104_18bc3fb0b4ad45b861816f--

