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

ODCID is a special for validating the server address #4344

Merged
merged 4 commits into from Nov 9, 2020
Merged

ODCID is a special for validating the server address #4344

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b071df7
ODCID is a special for validating the server address
martinthomson Nov 9, 2020
c066481
Magic
martinthomson Nov 9, 2020
9f1c03c
Revert "Magic"
martinthomson Nov 9, 2020
da21152
More words on client validation of the server address
martinthomson Nov 9, 2020
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
12 changes: 8 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1928,10 +1928,14 @@ consider the peer address to have been validated.

Additionally, an endpoint MAY consider the peer address validated if the peer
uses a connection ID chosen by the endpoint and the connection ID contains at
least 64 bits of entropy. A client can consider the server address validated on
successfully processing any packet received from the server, since for
encrypting its Initial packets, the server uses the Destination Connection ID
field from the client's first Initial packet; see Section 5.2 of {{QUIC-TLS}}.
least 64 bits of entropy.

For the client, the value of the Destination Connection ID field in its first
Initial packet allows it to validate the server address as a part of
successfully processing any packet. Initial packets from the server are
protected with keys that are derived from this value (see Section 5.2 of
{{QUIC-TLS}}). Alternatively, the value is echoed by the server in Retry and
Version Negotiation packets.

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