IETF Logo Mail Archive

Re: [quicwg/base-drafts] It's annoying that one can't send push in 0.5RTT (#2227)

afrind <notifications@github.com> Fri, 21 December 2018 00:48 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 3CC25130EF9 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 16:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 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_24=1.618, 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 NCQR6RVMGVsG for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 16:48:40 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B4CD130E99 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 16:48:40 -0800 (PST)
Date: Thu, 20 Dec 2018 16:48:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545353319; bh=vZGvNlqufXaAZqIk96G9V964O6IaLSWPuRC7cbGnHeU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=n+/56UsPiS2CXHubcQ+UtxtuF0cHYxmrk3Okvk+N1XcQs1kNQ0iDKBrZ+RnnA9WTL Ac9D7lmi1bdt87q/jaGYBjVP9ecVDYrZIjat3wwE27ePz/fiOfxRY/oz0UbqdpxBUz 44cYrduQA7p01aTqJOk3AeX+G/Yr2WOElNytR2/8=
From: afrind <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab068a45aff2140fa6e289ad96ec5a3fe03d6257c292cf000000011833fa6792a169ce177070bb@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/449191304@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_5c1c38677a6a2_5f713fb2794d45c01559ca"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: afrind
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/-4y-bdA21_aYL0ca3ckyOFNSQbA>
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 00:48:42 -0000

That's not part of the HTTP/2 push design.  I agree that it would be a nice feature, but perhaps it's out of charter/scope for v1?

-- 
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-449191304

v2.23.0 | Report a Bug | By Email