Date: Tue, 06 Dec 2016 06:18:15 -0800
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/58/265160297@github.com>
In-Reply-To: <quicwg/base-drafts/issues/58@github.com>
References: <quicwg/base-drafts/issues/58@github.com>
Subject: Re: [quicwg/base-drafts] Frame type extensions (#58)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5846c8a761520_75eb3fafbdeab134130118d";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/i4-QsPwluuqPKt52N_LtIkvZ8uE>
Reply-To: quicwg/base-drafts
 <reply+0166e4abbfdf53b98b491c2cea4fb163291cdca5586ec64d92cf00000001145e8aa792a169ce0b80d4e5@reply.github.com>


----==_mimepart_5846c8a761520_75eb3fafbdeab134130118d
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

Another approach would be:
1) Negotiate what experimental frame types are to be used in the handshake by the client listing the ones it'd like to use. 
2) If the server doesn't repeat back some or all of the suggested frame types, then the client knows the server doesn't support them.
3) Assign them frame numbers on a per-connection basis in the order the server repeats them back.
4) Experimental frames must always be sent post-SHLO with 1RTT keys.
5) If non-negotiated experimental frames are used, close the connection with an error.

In some cases, such as FEC, the sender really needs to know the receiver supports it.  and if they don't, why send it?

-- 
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/58#issuecomment-265160297
----==_mimepart_5846c8a761520_75eb3fafbdeab134130118d
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Another approach would be:</p>
<ol>
<li>Negotiate what experimental frame types are to be used in the handsha=
ke by the client listing the ones it'd like to use.</li>
<li>If the server doesn't repeat back some or all of the suggested frame =
types, then the client knows the server doesn't support them.</li>
<li>Assign them frame numbers on a per-connection basis in the order the =
server repeats them back.</li>
<li>Experimental frames must always be sent post-SHLO with 1RTT keys.</li=
>
<li>If non-negotiated experimental frames are used, close the connection =
with an error.</li>
</ol>
<p>In some cases, such as FEC, the sender really needs to know the receiv=
er supports it.  and if they don't, why send it?</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/58#issuecomment-265160297">view it on GitHub</a>, o=
r <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq4qsAH=
xw2u4SwnueRQgFo0yotuqFks5rFW6ngaJpZM4LCBR3">mute the thread</a>.<img alt=3D=
"" height=3D"1" src=3D"https://github.com/notifications/beacon/AWbkq1QEq8=
njbyxSnIYrwzZmWbAfuc5hks5rFW6ngaJpZM4LCBR3.gif" width=3D"1" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewActi=
on">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/is=
sues/58#issuecomment-265160297"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></me=
ta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6=
-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubuserconte=
nt.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","=
action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dr=
afts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@ianswett in #=
58: Another approach would be:\r\n1) Negotiate what experimental frame ty=
pes are to be used in the handshake by the client listing the ones it'd l=
ike to use. \r\n2) If the server doesn't repeat back some or all of the s=
uggested frame types, then the client knows the server doesn't support th=
em.\r\n3) Assign them frame numbers on a per-connection basis in the orde=
r the server repeats them back.\r\n4) Experimental frames must always be =
sent post-SHLO with 1RTT keys.\r\n5) If non-negotiated experimental frame=
s are used, close the connection with an error.\r\n\r\nIn some cases, suc=
h as FEC, the sender really needs to know the receiver supports it.  and =
if they don't, why send it?"}],"action":{"name":"View Issue","url":"https=
://github.com/quicwg/base-drafts/issues/58#issuecomment-265160297"}}}</sc=
ript>=

----==_mimepart_5846c8a761520_75eb3fafbdeab134130118d--