Date: Thu, 16 Jan 2020 20:59:20 -0800
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJKZYWZRLPO6TDY4A4M54FZY2REVBNHHCBV7VNU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3352/review/344364210@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3352@github.com>
References: <quicwg/base-drafts/pull/3352@github.com>
Subject: Re: [quicwg/base-drafts] Clarify and split the "malformed" definition
 (#3352)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e213f28a2070_372b3fd8afacd95c941f8";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/_S5Q0HgSDhSaOj8u2G4HrG0dq3Y>


----==_mimepart_5e213f28a2070_372b3fd8afacd95c941f8
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

MikeBishop commented on this pull request.



> @@ -410,10 +417,10 @@ considered invalid.
 
 An HTTP request/response exchange fully consumes a bidirectional QUIC stream.

Good call.  Yes, this covers pushes, too -- it's a response message that follows this format.  (I don't see *why* you'd push with a non-final response in the sequence, but it's totally valid....)

-- 
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/3352#discussion_r367769603
----==_mimepart_5e213f28a2070_372b3fd8afacd95c941f8
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@MikeBishop</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/3352#discussion_r367769603">draft-ietf-quic-http.md</a>:</p>
<pre style='color:#555'>&gt; @@ -410,10 +417,10 @@ considered invalid.
 
 An HTTP request/response exchange fully consumes a bidirectional QUIC stream.
</pre>
<p>Good call.  Yes, this covers pushes, too -- it's a response message that follows this format.  (I don't see <em>why</em> you'd push with a non-final response in the sequence, but it's totally valid....)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/3352?email_source=notifications&amp;email_token=AFTOJK75BVXHGK4O665PTU3Q6E3KRA5CNFSM4KHZZ2A2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCSDJJMQ#discussion_r367769603">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK3WZYYSL275GI2GHT3Q6E3KRANCNFSM4KHZZ2AQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJKZ3H3HGI7KQT7BOZNTQ6E3KRA5CNFSM4KHZZ2A2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCSDJJMQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/3352?email_source=notifications\u0026email_token=AFTOJK75BVXHGK4O665PTU3Q6E3KRA5CNFSM4KHZZ2A2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCSDJJMQ#discussion_r367769603",
"url": "https://github.com/quicwg/base-drafts/pull/3352?email_source=notifications\u0026email_token=AFTOJK75BVXHGK4O665PTU3Q6E3KRA5CNFSM4KHZZ2A2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCSDJJMQ#discussion_r367769603",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e213f28a2070_372b3fd8afacd95c941f8--