Date: Sun, 21 Jul 2019 11:21:18 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK5STJVJVLUBHA4G7VN3IHPZ5EVBNHHBYDQKAQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2911/513576272@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2911@github.com>
References: <quicwg/base-drafts/issues/2911@github.com>
Subject: Re: [quicwg/base-drafts] Separate HTTP/3 stream errors from
 connection errors. (#2911)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5d34ad1ef0544_780d3f83d0ecd964797470";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/P3vjDF3o6lBYTrHWvv9f070YhsU>


----==_mimepart_5d34ad1ef0544_780d3f83d0ecd964797470
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@kazuho 

> I think we need the freedom of promoting stream-level errors to connection errors. For example, when a server detects a suspicious activity by a client at a stream-level, it would make sense to close the connection.

I agree. This is a real thing that happens today with H2 and should be maintained.

My question would be, does  it makes sense for promotion to maintain the the error code fidelity? I.e. if you are closing connection on a miss-behaving peer, is there benefit from articulating the specific stream error code, or does it work as well to drop this to HTTP_GENERAL_PROTOCOL_ERROR?

-- 
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/issues/2911#issuecomment-513576272
----==_mimepart_5d34ad1ef0544_780d3f83d0ecd964797470
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=41567" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/kazuho">@kazuho</a></p>
<blockquote>
<p>I think we need the freedom of promoting stream-level errors to connection errors. For example, when a server detects a suspicious activity by a client at a stream-level, it would make sense to close the connection.</p>
</blockquote>
<p>I agree. This is a real thing that happens today with H2 and should be maintained.</p>
<p>My question would be, does  it makes sense for promotion to maintain the the error code fidelity? I.e. if you are closing connection on a miss-behaving peer, is there benefit from articulating the specific stream error code, or does it work as well to drop this to HTTP_GENERAL_PROTOCOL_ERROR?</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/issues/2911?email_source=notifications&amp;email_token=AFTOJK4DBS2WFIFJJCT3R23QASSJ5A5CNFSM4IFO2MZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OI2UA#issuecomment-513576272">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK6XOEGPHFSJHL6L3E3QASSJ5ANCNFSM4IFO2MZA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJKYVYDO22CUQG7LD64DQASSJ5A5CNFSM4IFO2MZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OI2UA.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/issues/2911?email_source=notifications\u0026email_token=AFTOJK4DBS2WFIFJJCT3R23QASSJ5A5CNFSM4IFO2MZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OI2UA#issuecomment-513576272",
"url": "https://github.com/quicwg/base-drafts/issues/2911?email_source=notifications\u0026email_token=AFTOJK4DBS2WFIFJJCT3R23QASSJ5A5CNFSM4IFO2MZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OI2UA#issuecomment-513576272",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5d34ad1ef0544_780d3f83d0ecd964797470--