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

WIP: Begin lightly abstracting over the use of UDP as the underlying transport #4043

Closed
wants to merge 5 commits into from
Closed

WIP: Begin lightly abstracting over the use of UDP as the underlying transport #4043

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ca022d8
WIP: Begin lightly abstracting over the use of UDP as the underlying …
Ericson2314 Aug 21, 2020
1a5c504
Apply suggestions from code review
Ericson2314 Aug 28, 2020
c1151bc
Merge remote-tracking branch 'upstream/master' into transport-udp-unh…
Ericson2314 Aug 28, 2020
56d0b98
Don't abstract over UDP for this specific bit of empiracal evidence
Ericson2314 Aug 28, 2020
367347b
Don't imply UDP without "real migrations" means constant IP.
Ericson2314 Aug 28, 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
19 changes: 10 additions & 9 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2554,15 +2554,16 @@ those paths to be linked by entities other than the peer.

A client might wish to reduce linkability by employing a new connection ID and
source address when sending traffic after a period of inactivity. (In
conventional situations using UDP, the client cannot freely vary the IP address,
but can much more readily change the UDP port. Since an address for QUIC when
using UDP is the tuple of the IP address and UDP port, changing the source port
along constitutes changing the QUIC address.) So changing the address from which
it sends packets at the same time might cause the packet to appear as a
connection migration. This ensures that the mechanisms that support migration
are exercised even for clients that do not experience NAT rebindings or genuine
migrations. Changing port number can cause a peer to reset its congestion state
(see {{migration-cc}}), so the port SHOULD only be changed infrequently.
conventional situations using UDP, the client may not always be able to freely
vary the IP address, but can much more readily change the UDP port. Since an
address for QUIC when using UDP is the tuple of the IP address and UDP port,
changing the source port along constitutes changing the QUIC address.) So
changing the address from which it sends packets at the same time might cause
the packet to appear as a connection migration. This ensures that the
mechanisms that support migration are exercised even for clients that do not
experience NAT rebindings or genuine migrations. Changing port number can cause
a peer to reset its congestion state (see {{migration-cc}}), so the port SHOULD
only be changed infrequently.

An endpoint that exhausts available connection IDs cannot probe new paths or
initiate migration, nor can it respond to probes or attempts by its peer to
Expand Down