From 957a750bc54c397cacd65040f07710cd051d596f Mon Sep 17 00:00:00 2001 From: Jana Iyengar Date: Tue, 17 Dec 2019 22:05:24 -0800 Subject: [PATCH] Allow use of token after client address change --- draft-ietf-quic-transport.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/draft-ietf-quic-transport.md b/draft-ietf-quic-transport.md index b43582b0a2..f76304ead7 100644 --- a/draft-ietf-quic-transport.md +++ b/draft-ietf-quic-transport.md @@ -1752,11 +1752,7 @@ connection attempts. A client SHOULD NOT reuse a NEW_TOKEN token for different connection attempts. Reusing a token allows connections to be linked by entities on the network path; -see {{migration-linkability}}. A client MUST NOT reuse a token if it believes -that its point of network attachment has changed since the token was last used; -that is, if there is a change in its local IP address or network interface. A -client needs to start the connection process over if there is any change in its -local address prior to completing the handshake. +see {{migration-linkability}}. Clients might receive multiple tokens on a single connection. Aside from preventing linkability, any token can be used in any connection attempt.