IETF Logo Mail Archive

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

ianswett <notifications@github.com> Tue, 07 May 2019 20:39 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 8A4061202EB for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 13:39:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.919
X-Spam-Level:
X-Spam-Status: No, score=-6.919 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_16=1.092, 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: 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 n7VJquuZdEVJ for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 13:39:27 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 162D11202D3 for <quic-issues@ietf.org>; Tue, 7 May 2019 13:39:27 -0700 (PDT)
Date: Tue, 07 May 2019 13:39:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557261565; bh=4vxfNhjM0vudHeauZK6kA0zPdEF2YxNPKSJ5ImFg/Iw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=llFeqaKmE7KX5b8H2ffo3aWiX/kFKoIFsJisUPHqDtMA5UJnj8zqD7HERUUUQ8lDI rOmHhYlLMNKM0XooS0m98QhV2dAVCM7RhEQhnoJLJHZfs/gj5bOWUumb2lyOIwgaVt boRCjsWP1p1fpZ3g1g4DBzG/kSvT8jNPcNTwmN3c=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZA333J77SBWCAVCEN234PX3EVBNHHBUN2RIE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2665/c490246487@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2665@github.com>
References: <quicwg/base-drafts/pull/2665@github.com>
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_5cd1ecfda607b_47e43fe50cacd95c353538"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/x3ByxZ1zldg1-qWVvMQwErI1IPk>
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: Tue, 07 May 2019 20:39:32 -0000

Maybe this would be better if section 4 was moved after section 6?  Then the concepts would be explained before going into the framing.

I'd also like to reorder/renumber all the push frame types so they're all adjacent to one another and in a sensible order.  Is there a reason they're numbered as they are?  If not, I'll open an issue to renumber them.

-- 
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/pull/2665#issuecomment-490246487

v2.23.0 | Report a Bug | By Email