Date: Tue, 28 Jan 2020 10:43:09 +0000 (UTC)
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK5YNPZLMTGI2QCPNO54HVBLPEVBNHHCCIN5SE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3396/579185046@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3396@github.com>
References: <quicwg/base-drafts/issues/3396@github.com>
Subject: Re: [quicwg/base-drafts] Server cannot proceed after invalid Retry
 token (#3396)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5e3010376afd7_791a3f823fccd96c991fe";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/6UWY1WH7Va7WOA5QpIdaT0_3bB0>

----==_mimepart_5e3010376afd7_791a3f823fccd96c991fe
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

The problem here is that something that is identifiable as a Retry token as distinct from a NEW_TOKEN token will ultimately not be usable.  There's a bit of hedging necessary though as junk that appears to be a Retry token is still ultimately just junk.

To be concrete, let's say that you generate Retry tokens that start with "RETRY!!!" and NEW_TOKEN tokens start with "~~~NEW_TOKEN" The difference between those two is such that it would be unlikely for corruption to cause one to be mistaken for the other, and you have a way to distinguish the two even when all the subsequent bits can't be interpreted after you lose keys or something like that.

-- 
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/3396#issuecomment-579185046
----==_mimepart_5e3010376afd7_791a3f823fccd96c991fe
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>The problem here is that something that is identifiable as a Retry token as distinct from a NEW_TOKEN token will ultimately not be usable.  There's a bit of hedging necessary though as junk that appears to be a Retry token is still ultimately just junk.</p>
<p>To be concrete, let's say that you generate Retry tokens that start with "RETRY!!!" and NEW_TOKEN tokens start with "~~~NEW_TOKEN" The difference between those two is such that it would be unlikely for corruption to cause one to be mistaken for the other, and you have a way to distinguish the two even when all the subsequent bits can't be interpreted after you lose keys or something like that.</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/3396?email_source=notifications&amp;email_token=AFTOJK5YAE364CS52G7WCC3RAAD3PA5CNFSM4KMIZS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKC2TFQ#issuecomment-579185046">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK7MH7AG3KGTDJFPYATRAAD3PANCNFSM4KMIZS3A">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK6QSBPPG3SEGDA6OGDRAAD3PA5CNFSM4KMIZS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKC2TFQ.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/3396?email_source=notifications\u0026email_token=AFTOJK5YAE364CS52G7WCC3RAAD3PA5CNFSM4KMIZS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKC2TFQ#issuecomment-579185046",
"url": "https://github.com/quicwg/base-drafts/issues/3396?email_source=notifications\u0026email_token=AFTOJK5YAE364CS52G7WCC3RAAD3PA5CNFSM4KMIZS3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKC2TFQ#issuecomment-579185046",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5e3010376afd7_791a3f823fccd96c991fe--