Date: Thu, 24 Oct 2019 15:17:22 -0700
From: Nick Harper <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK3G73X7WU4P34LCYHF3X5RYFEVBNHHB5B4MBE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3150/review/306895344@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3150@github.com>
References: <quicwg/base-drafts/pull/3150@github.com>
Subject: Re: [quicwg/base-drafts] Clarify the state a client stores with a
 token (#3150)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5db222f2efa52_12d3fca20ecd9648889e";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/ZFH2xgvKY1gSj0imWLLCV1UDFJI>


----==_mimepart_5db222f2efa52_12d3fca20ecd9648889e
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

nharper commented on this pull request.



> @@ -1697,7 +1697,8 @@ connections; validating the port is therefore unlikely to be successful.
 If the client has a token received in a NEW_TOKEN frame on a previous connection
 to what it believes to be the same server, it SHOULD include that value in the
 Token field of its Initial packet.  Including a token might allow the server to
-validate the client address without an additional round trip.
+validate the client address without an additional round trip.  A client MAY use
+a token from any previous connection to that server.

3 paragraphs down ("Clients might receive multiple tokens on a single connection") mentions that older tokens might become invalid and that clients should send the most recent unused token. I think that covers your question.

-- 
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/3150#discussion_r338815723
----==_mimepart_5db222f2efa52_12d3fca20ecd9648889e
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p><b>@nharper</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/quicwg/base-drafts/pull/3150#discussion_r338815723">draft-ietf-quic-transport.md</a>:</p>
<pre style='color:#555'>&gt; @@ -1697,7 +1697,8 @@ connections; validating the port is therefore unlikely to be successful.
 If the client has a token received in a NEW_TOKEN frame on a previous connection
 to what it believes to be the same server, it SHOULD include that value in the
 Token field of its Initial packet.  Including a token might allow the server to
-validate the client address without an additional round trip.
+validate the client address without an additional round trip.  A client MAY use
+a token from any previous connection to that server.
</pre>
<p>3 paragraphs down ("Clients might receive multiple tokens on a single connection") mentions that older tokens might become invalid and that clients should send the most recent unused token. I think that covers your question.</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/3150?email_source=notifications&amp;email_token=AFTOJK6HHPP7CV5UWJQSA33QQINHFA5CNFSM4JE37ZY2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCJFNT4A#discussion_r338815723">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK5O4FVCDON7FP45J2DQQINHFANCNFSM4JE37ZYQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AFTOJK5BNTZUE2JS4B7FS6DQQINHFA5CNFSM4JE37ZY2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCJFNT4A.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/3150?email_source=notifications\u0026email_token=AFTOJK6HHPP7CV5UWJQSA33QQINHFA5CNFSM4JE37ZY2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCJFNT4A#discussion_r338815723",
"url": "https://github.com/quicwg/base-drafts/pull/3150?email_source=notifications\u0026email_token=AFTOJK6HHPP7CV5UWJQSA33QQINHFA5CNFSM4JE37ZY2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCJFNT4A#discussion_r338815723",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>
----==_mimepart_5db222f2efa52_12d3fca20ecd9648889e--