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

ianswett <> Thu, 16 May 2019 19:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7E3F012028C for <>; Thu, 16 May 2019 12:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.393
X-Spam-Status: No, score=-6.393 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, 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 ip0i04WCJzTF for <>; Thu, 16 May 2019 12:32:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EB32A120289 for <>; Thu, 16 May 2019 12:32:13 -0700 (PDT)
Date: Thu, 16 May 2019 12:32:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1558035132; bh=F3js95bqe+f3YU1DilgnazhkR4Hb5Aijasr7qyJJEzY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=02DI1LNKC/bk/Vp2XYsmDjysFOX7rxb/kTNBtIXMfAKYTsTm6u7W4Snu2Znxs7BkM iG6zrf4NftV0c/cXb7R04pk7OKkRMcs8MJc570pwd1Bot0sbylrP65grL2UtLXtlpU a/izn5z25N1sUJ/Q/nyO3vsFYbSN6S6Hvmxz5HO8=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2665/>
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_5cddbabc7699f_35143fe9b68cd964615854"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: Thu, 16 May 2019 19:32:17 -0000

I think the Server Push section still lacks a simple explanation of what the push does.  A sentence like what I added in this PR at the beginning would help that.  Currently the Server Push section goes directly into mechanics.

"HTTP/3 server push is similar to what is described in HTTP/2 {{!HTTP2}}, but uses different mechanisms.

Each server push is identified by a unique Push ID. ..."

I'd add more to the first paragraph in case people don't want to read the H2 draft.

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