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

Mike Bishop <> Tue, 07 May 2019 07:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3AFDF1200A2 for <>; Tue, 7 May 2019 00:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Status: No, score=-6.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_HI=-5, 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 9XT7rAASwYg6 for <>; Tue, 7 May 2019 00:05:31 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3308C120072 for <>; Tue, 7 May 2019 00:05:31 -0700 (PDT)
Date: Tue, 07 May 2019 00:05:29 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1557212729; bh=Uj6PWmXjKDdQNsv++yXaXY5kDn3HFczj28Vu/m1chXo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=b+e3Fe8FnJl2vdLyYJR8JTG5NvCHgMFmaIflfxUDzEd2A0KmlzDy3Bdr/fHwoGEto Ht8B4CikFIlxLrhsz5sogyYZ9ksJ7i6nYhq3rcVBcrC8xmFtq3U5zgSUi6UQEySEM3 f9xVzt5uT6brwn3xClXu3fTcqbAw0ZYlZBEy9wzk=
From: Mike Bishop <>
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_5cd12e39c9aaa_6e143fbbd1acd95c1639f0"; 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
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: Tue, 07 May 2019 07:05:34 -0000

MikeBishop 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.

Understandably -- it's a line we have to walk.  (Note that HTTP/2 defines no verbs and pseudo-no headers.)

My principle has been that I'm trying to weed out assumptions that you've read RFC7540 and understand a given concept already.  I'm happy to save redundant and possibly-conflicting text by pointing to a specific section of RFC7540, however.

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