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

Targeted attacks in Security Considerations #2635

Merged
merged 3 commits into from
May 7, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions draft-ietf-quic-transport.md
Original file line number Diff line number Diff line change
Expand Up @@ -5385,11 +5385,11 @@ define a mechanism that is robust against version downgrade attacks.
## Targeted Attacks by Routing

Deployments should limit the ability of an attacker to target a new connection
to a particular server instance. This means that client-controlled fields, such as the
initial Destination Connection ID used on Initial and 0-RTT packets SHOULD NOT
be used by themselves to make routing decisions. Ideally, routing decisions are made
independently of client-selected values; a Source Connection ID can be selected
to route later packets to the same server.
to a particular server instance. This means that client-controlled fields, such
as the initial Destination Connection ID used on Initial and 0-RTT packets
SHOULD NOT be used by themselves to make routing decisions. Ideally, routing
decisions are made independently of client-selected values; a Source Connection
ID can be selected to route later packets to the same server.

# IANA Considerations

Expand Down