Date: Tue, 14 Jan 2020 15:47:33 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK56AMVFBCXOG2XYIAF4FOCZLEVBNHHCBO6ZLI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3336/c574427942@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3336@github.com>
References: <quicwg/base-drafts/pull/3336@github.com>
Subject: Re: [quicwg/base-drafts] Limit fallout of on-stream badness (#3336)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e1e5315b8ca_cae3ffdc0ecd96867467";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/YYa0vIautB37g2bDmo-9bPunuyo>


----==_mimepart_5e1e5315b8ca_cae3ffdc0ecd96867467
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@MikeBishop 
> Malformed headers are already stream errors, so the "trim back" would be to close the PRs entirely.

If our principle is to require H3 endpoints to do their own framing, I think we should go one step further than just closing this PR.

We should stop stating that existence of extraneous frames is considered a malformed request / response (see https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-4.1.3), and that it's a connection error.

I am perfectly fine with having more rigid rules for frames, as it is a hop-by-hop concept. That's very different from header fields which are end-to-end and also might convey information that cannot be understood by an H3 endpoint sitting at the middle.

-- 
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/3336#issuecomment-574427942
----==_mimepart_5e1e5315b8ca_cae3ffdc0ecd96867467
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/MikeBishop/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/MikeBishop">@MikeBishop</a></p>
<blockquote>
<p>Malformed headers are already stream errors, so the "trim back" would be to close the PRs entirely.</p>
</blockquote>
<p>If our principle is to require H3 endpoints to do their own framing, I think we should go one step further than just closing this PR.</p>
<p>We should stop stating that existence of extraneous frames is considered a malformed request / response (see <a href="https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-4.1.3" rel="nofollow">https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-4.1.3</a>), and that it's a connection error.</p>
<p>I am perfectly fine with having more rigid rules for frames, as it is a hop-by-hop concept. That's very different from header fields which are end-to-end and also might convey information that cannot be understood by an H3 endpoint sitting at the middle.</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/3336?email_source=notifications&amp;email_token=AFTOJK76N77ZHHJGZC7DKGLQ5ZFJLA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6RGJQ#issuecomment-574427942">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK36T3BQG7Y4FHHWZR3Q5ZFJLANCNFSM4KGI2IDA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJKYVTODZCKCB4UQKMD3Q5ZFJLA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6RGJQ.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/3336?email_source=notifications\u0026email_token=AFTOJK76N77ZHHJGZC7DKGLQ5ZFJLA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6RGJQ#issuecomment-574427942",
"url": "https://github.com/quicwg/base-drafts/pull/3336?email_source=notifications\u0026email_token=AFTOJK76N77ZHHJGZC7DKGLQ5ZFJLA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6RGJQ#issuecomment-574427942",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e1e5315b8ca_cae3ffdc0ecd96867467--