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

May use 64+bit CIDs as address validation #3924

Merged
merged 5 commits into from Jul 29, 2020
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 @@ -1877,8 +1877,8 @@ endpoints. In particular, receipt of a packet protected with Handshake keys
confirms that the client received the Initial packet from the server. Once the
server has successfully processed a Handshake packet from the client, it can
consider the client address to have been validated. Servers MAY treat the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
consider the client address to have been validated. Servers MAY treat the
consider the client address to have been validated. Servers MAY also treat the

receipt of a packet using a server generated destination connection ID with at least 64 bits
of entropy as address validation.
receipt of a packet using a server generated destination connection ID with
ianswett marked this conversation as resolved.
Show resolved Hide resolved
at least 64 bits of entropy as address validation.

Prior to validating the client address, servers MUST NOT send more than three
times as many bytes as the number of bytes they have received. This limits the
Expand Down