Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RFC 4086 can be an informative reference #4699

Merged
merged 1 commit into from Jan 11, 2021
Merged

RFC 4086 can be an informative reference #4699

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -3169,8 +3169,8 @@ packets on this connection.
### Calculating a Stateless Reset Token {#reset-token}

The stateless reset token MUST be difficult to guess. In order to create a
Stateless Reset Token, an endpoint could randomly generate ({{!RFC4086}}) a
secret for every connection that it creates. However, this presents a
Stateless Reset Token, an endpoint could randomly generate ({{?RANDOM=RFC4086}})
a secret for every connection that it creates. However, this presents a
coordination problem when there are multiple instances in a cluster or a storage
problem for an endpoint that might lose state. Stateless reset specifically
exists to handle the case where state is lost, so this approach is suboptimal.
Expand Down