Date: Tue, 14 Jan 2020 13:20:25 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK46HPZTJHA2HDYUZQ54FNRRTEVBNHHCBO6ZLI@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/c574379204@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_5e1e309952f7a_184f3fe62e6cd960779b5";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/hG283JcoeWor8wQlVaMexWQMHQY>


----==_mimepart_5e1e309952f7a_184f3fe62e6cd960779b5
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Thanks for writing this PR, seeing it written down makes me like it clear that I'm not a fan of this change.

One can certainly implement a proxy that doesn't validate the frames, but for this proxy to receive a single H3 connection on the front and send multiple H3 connections out the back, it's going to have to do more than blindly proxy.  For example, there's only one control stream, and I can't imagine how it's possible to run QPACK anything but hop-by-hop.  It also has to map push Ids, etc.

If there's some practical use case I'm missing, please tell me, but in most cases, blindly proxying these frames wouldn't even work, with the DATA frame being the possible exception?

-- 
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-574379204
----==_mimepart_5e1e309952f7a_184f3fe62e6cd960779b5
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>Thanks for writing this PR, seeing it written down makes me like it clear that I'm not a fan of this change.</p>
<p>One can certainly implement a proxy that doesn't validate the frames, but for this proxy to receive a single H3 connection on the front and send multiple H3 connections out the back, it's going to have to do more than blindly proxy.  For example, there's only one control stream, and I can't imagine how it's possible to run QPACK anything but hop-by-hop.  It also has to map push Ids, etc.</p>
<p>If there's some practical use case I'm missing, please tell me, but in most cases, blindly proxying these frames wouldn't even work, with the DATA frame being the possible exception?</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=AFTOJK3WXE5J2SWQJUQKKZTQ5YUBTA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6FJRA#issuecomment-574379204">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK22PDBS24QUOOJA3WDQ5YUBTANCNFSM4KGI2IDA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK4M2CCGAVTUGJHMJO3Q5YUBTA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6FJRA.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=AFTOJK3WXE5J2SWQJUQKKZTQ5YUBTA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6FJRA#issuecomment-574379204",
"url": "https://github.com/quicwg/base-drafts/pull/3336?email_source=notifications\u0026email_token=AFTOJK3WXE5J2SWQJUQKKZTQ5YUBTA5CNFSM4KGI2IDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI6FJRA#issuecomment-574379204",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e1e309952f7a_184f3fe62e6cd960779b5--