[quicwg/base-drafts] Allow use of token after client address changes (#3307)

Jana Iyengar <notifications@github.com> Wed, 18 December 2019 06:04 UTC

Date: Tue, 17 Dec 2019 22:04:47 -0800
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4AJVO7YARSDX65EXF4A3Z77EVBNHHCAJ5MJU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3307@github.com>
Subject: [quicwg/base-drafts] Allow use of token after client address changes (#3307)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df9c17fde846_5f513fb2c52cd9601316a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/u-dW5dPE6mMDNZOBZOPH_q2H1KY>

[Section 8.1.3 of the transport draft](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#name-address-validation-for-futu) states:
```
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.
```

This is an unnecessary constraint and there’s value in not having it. A server can, for example, include multiple IP addresses for a client in a token, enabling client validation from multiple attachment points.

-- 
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/3307

[quicwg/base-drafts] Allow use of token after cli… Jana Iyengar
Re: [quicwg/base-drafts] Allow use of token after… Kazuho Oku
Re: [quicwg/base-drafts] Allow use of token after… ianswett
Re: [quicwg/base-drafts] Allow use of token after… ianswett
Re: [quicwg/base-drafts] Allow use of token after… Martin Thomson