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.

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

Move and consolidate address validation #1886

Merged
merged 24 commits into from Oct 23, 2018
Merged
Changes from 1 commit
Commits
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
Expand Up @@ -1575,8 +1575,8 @@ NEW_TOKEN frame (see {{validate-future}}).
QUIC uses token-based address validation during connection establishment. Any
time the server wishes to validate a client address, it provides the client with
a token. As long as it is not possible for an attacker to generate a valid
token for its own address (see {{token-integrity}}) and the client is able to return
that token, it proves to the server that it received the token.
token for its own address (see {{token-integrity}}) and the client is able to
return that token, it proves to the server that it received the token.

Upon receiving the client's Initial packet, the server can request address
validation by sending a Retry packet ({{packet-retry}}) containing a token. This
Expand Down