Re: [quicwg/base-drafts] Reference 8.2 of RFC7540 to explain Server Push (#2665)

Jana Iyengar <> Mon, 06 May 2019 23:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2C13312011A for <>; Mon, 6 May 2019 16:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.464
X-Spam-Status: No, score=-1.464 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2o0Wd4_IkhyL for <>; Mon, 6 May 2019 16:50:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 647821200EA for <>; Mon, 6 May 2019 16:50:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=0ucU+WiAOu6GGlQ7opGupoP8D1Y=; b=Aw0B0usaLx6WtOJI CkjEdI4jrhkHWz4ynI8YJdOW70toffJE1B78pePi/0o2s/keD/7N9S48H2FofvuV /NhefaKGMyEEOGmJkr27ujNamlEaSggTVSKKehbxKxdYY9eYvWIQ+OHMyzk8UdkQ ZV3QtQ9bDtjYZKk5KAO/MoFuzPs=
Received: by with SMTP id filter0964p1las1-18767-5CD0C837-29 2019-05-06 23:50:15.882414422 +0000 UTC m=+958254.651747663
Received: from (unknown []) by (SG) with ESMTP id JNmCAQ_sRY2cyLHmhwzs5Q for <>; Mon, 06 May 2019 23:50:15.820 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id B96BA3E283E for <>; Mon, 6 May 2019 16:50:15 -0700 (PDT)
Date: Mon, 06 May 2019 23:50:15 +0000
From: Jana Iyengar <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2665/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Reference 8.2 of RFC7540 to explain Server Push (#2665)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd0c837b808b_81f3fa83bccd968428a3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3esqb9OkokgIsPtX0iEziCfN6EVitZ+oyF5a XDLISZRqnGV0pqTq11UVblV4c4F1KZJaoAY84VsvZUT4SqGIRLMETRczNDUblvqLfwOJLxeMrmjKaA Lor8UPIFAsO8vqw47ICs3Xj4JUnGgKtzZwAUKNPkcEeVZflF0ButNltqqnK4cS2dO4FO4UbE/JUOJV U=
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 06 May 2019 23:50:19 -0000

janaiyengar commented on this pull request.

> @@ -370,6 +370,10 @@ able to send stream data first after the cryptographic handshake completes.
 ### Push Streams
+Server push is an optional feature introduced in HTTP/2 that allows a server to
+initiate a response before a request has been made.  See section 8.2 of
+{{!RFC7540}} for more details.

That's not quite accurate... since the response has to be associated with a previous request. I don't think that level of detail is necessary though. How about "The Server Push feature of HTTP/2 (see Section 8.2 of {{!RFC7540}}) is facilitated in HTTP/3 via push streams."

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: