Re: [quicwg/base-drafts] Reference 8.2 of RFC7540 to explain Server Push (#2665)
Mike Bishop <notifications@github.com> Tue, 07 May 2019 20:54 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 7540412013E for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 13:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.918
X-Spam-Level:
X-Spam-Status: No, score=-6.918 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, 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 e5g_lHBIMbpm for <quic-issues@ietfa.amsl.com>; Tue, 7 May 2019 13:54:01 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED156120086 for <quic-issues@ietf.org>; Tue, 7 May 2019 13:54:00 -0700 (PDT)
Date: Tue, 07 May 2019 13:53:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557262439; bh=dXqEQ9qn5slDPZdmpnL4SWB2SOrP9IeYDl3d8dMrYqM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LDBOXYMd6MSOuY7FRSMWw2fdUsbQn8WHzMiS6VBDopmpQqNUEbcukLJok1Rkelmha 18VKFWiNnDuUXvCEtjQgsNI/N5N6JHbLjk6rBQXqjvfiGVjqECLG0LGNYi2U2HNQSr URJKiqbQLQjlgRaWtAqtxJKaeff5HRMFoq5RES50=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3R2IHHC7LTVGVRSFF234ROPEVBNHHBUN2RIE@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/c490251215@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_5cd1f067b9e18_4fff3fa8baecd964300446"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/s4uo1GdsGzITxH07eWWFaMCebGg>
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:54:03 -0000
There's already an issue to reorder some of the sections, so I'm happy to consider this as part of the same discussion. As to the numbering, the primary reason is maintaining the same frame IDs for things that stayed over from HTTP/2 -- PUSH_PROMISE has the same ID, CANCEL_PUSH has the ID that HTTP/2 used for RST_STREAM, and DUPLICATE_PUSH is brand new and so pushes into unallocated space. -- 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-490251215
- [quicwg/base-drafts] Reference 8.2 of RFC7540 to … ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Jana Iyengar
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Lucas Pardue
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… MikkelFJ
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… ianswett
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop
- Re: [quicwg/base-drafts] Reference 8.2 of RFC7540… Mike Bishop