Date: Wed, 13 Feb 2019 13:59:22 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abe448a1d95fe678c490528dfbc79514180a3ed3e992cf00000001187c553a92a169ce1869fe88@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2461/c463392078@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2461@github.com>
References: <quicwg/base-drafts/pull/2461@github.com>
Subject: Re: [quicwg/base-drafts]  0-RTT can't use transport parameters or
 1-RTT frames  (#2461)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5c64933a5dc33_484c3f7ff1ad45c0825f4";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/lNOUAFHYkhvpwXRv5ICL6SDLba8>


----==_mimepart_5c64933a5dc33_484c3f7ff1ad45c0825f4
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

@ianswett 
> I think this is ok, but I think it's going to be difficult to get this correct in practice. I expect most implementations will migrate to 1-RTT keys as soon as possible and try to avoid writing special logic for this case, but I can't come up with a way to force clients to do that.

I think it's possible. I think that's what the PR is trying to suggest is that a server can:
* enforce limits based on TP to streams-related frames sent using 0-RTT packets (see #2461)
* refuse to handle any of the following frames in a 0-RTT packet: ACK, PATH_RESPONSE, RETIRE_CONNECTION_ID (see #2458)


-- 
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/2461#issuecomment-463392078
----==_mimepart_5c64933a5dc33_484c3f7ff1ad45c0825f4
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><a class=3D"user-mention" data-hovercard-type=3D"user" data-hovercard-=
url=3D"/hovercards?user_id=3D20072817" data-octo-click=3D"hovercard-link-=
click" data-octo-dimensions=3D"link_type:self" href=3D"https://github.com=
/ianswett">@ianswett</a></p>
<blockquote>
<p>I think this is ok, but I think it's going to be difficult to get this=
 correct in practice. I expect most implementations will migrate to 1-RTT=
 keys as soon as possible and try to avoid writing special logic for this=
 case, but I can't come up with a way to force clients to do that.</p>
</blockquote>
<p>I think it's possible. I think that's what the PR is trying to suggest=
 is that a server can:</p>
<ul>
<li>enforce limits based on TP to streams-related frames sent using 0-RTT=
 packets (see <a class=3D"issue-link js-issue-link" data-error-text=3D"Fa=
iled to load issue title" data-id=3D"409599624" data-permission-text=3D"I=
ssue title is private" data-url=3D"https://github.com/quicwg/base-drafts/=
issues/2461" data-hovercard-type=3D"pull_request" data-hovercard-url=3D"/=
quicwg/base-drafts/pull/2461/hovercard" href=3D"https://github.com/quicwg=
/base-drafts/pull/2461">#2461</a>)</li>
<li>refuse to handle any of the following frames in a 0-RTT packet: ACK, =
PATH_RESPONSE, RETIRE_CONNECTION_ID (see <a class=3D"issue-link js-issue-=
link" data-error-text=3D"Failed to load issue title" data-id=3D"409561841=
" data-permission-text=3D"Issue title is private" data-url=3D"https://git=
hub.com/quicwg/base-drafts/issues/2458" data-hovercard-type=3D"issue" dat=
a-hovercard-url=3D"/quicwg/base-drafts/issues/2458/hovercard" href=3D"htt=
ps://github.com/quicwg/base-drafts/issues/2458">#2458</a>)</li>
</ul>

<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/pull/2461#issuecomment-463392078">view it on GitHub</a>, o=
r <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq8Lt06=
Ju85HvR-hQquhJzZoUgmRyks5vNIq6gaJpZM4a4fJ9">mute the thread</a>.<img src=3D=
"https://github.com/notifications/beacon/AWbkq4HfP9z9A6St1x5VwfoS7H1Q2_vp=
ks5vNIq6gaJpZM4a4fJ9.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<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://github.githubassets.com/images/email/message_cards/header.png","avata=
r_image_url":"https://github.githubassets.com/images/email/message_cards/=
avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/q=
uicwg/base-drafts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@=
kazuho in #2461: @ianswett \r\n\u003e I think this is ok, but I think it'=
s going to be difficult to get this correct in practice. I expect most im=
plementations will migrate to 1-RTT keys as soon as possible and try to a=
void writing special logic for this case, but I can't come up with a way =
to force clients to do that.\r\n\r\nI think it's possible. I think that's=
 what the PR is trying to suggest is that a server can:\r\n* enforce limi=
ts based on TP to streams-related frames sent using 0-RTT packets (see #2=
461)\r\n* refuse to handle any of the following frames in a 0-RTT packet:=
 ACK, PATH_RESPONSE, RETIRE_CONNECTION_ID (see #2458)\r\n"}],"action":{"n=
ame":"View Pull Request","url":"https://github.com/quicwg/base-drafts/pul=
l/2461#issuecomment-463392078"}}}</script>
<script type=3D"application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/2461#issuecomment-4=
63392078",
"url": "https://github.com/quicwg/base-drafts/pull/2461#issuecomment-4633=
92078",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>=

----==_mimepart_5c64933a5dc33_484c3f7ff1ad45c0825f4--