Re: [quicwg/base-drafts] What indicates the end of a message? (#2230)

Mike Bishop <> Wed, 06 February 2019 00:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7E426128CF2 for <>; Tue, 5 Feb 2019 16:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.935
X-Spam-Status: No, score=-10.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, 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, SPF_PASS=-0.001] 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 cgLtf-9-B3ik for <>; Tue, 5 Feb 2019 16:52:49 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9761D128CE4 for <>; Tue, 5 Feb 2019 16:52:49 -0800 (PST)
Date: Tue, 05 Feb 2019 16:52:48 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549414368; bh=z61vQlHmH0NDu/Z/D0fSTnSOhAHYMDWhg2A8/F9DSfg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rk5rmZM2ogZSF8bYwPN2IZVBwuOBUanXBoF8peuOhmHX9MpNhJiAeMpdzIuurvcZt tHFvbJ9w9h1XioGFnlKjJD3U5WsNR8CPsu090jqgUo4c53lMBgXv1bK5qTquzOo1yo gOQtBTzqtWHlfq63rCJQob4nuSHaf0AASHX/Lu8s=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2230/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] What indicates the end of a message? (#2230)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5a2fe0c65d2_1f103f876a8d45c41265bb"; 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: Wed, 06 Feb 2019 00:52:52 -0000

Since the guidance about where PUSH_PROMISE should be sent falls in the broader category of "info from 7540 that needs to be restated / referenced in H3," I plan to fix this as part of that change.

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