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

Alternative for simple routing section #3615

Merged
merged 2 commits into from May 1, 2020
Merged

Alternative for simple routing section #3615

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bcda6c2
Alternative for simple routing section
martinthomson Apr 29, 2020
bca51a9
a/that
martinthomson May 1, 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
11 changes: 5 additions & 6 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1203,13 +1203,12 @@ deployment could use one of the following methods for connection continuity
when a client's address changes.

* Servers could use an out-of-band mechanism to forward packets to the correct
server based on Connection ID.
server based on Connection ID.

* If servers can use other dedicated server IP addresses or ports than
the one that the client initially connects to, they could use the
preferred_address transport parameter to request that clients move
connections to these dedicated addresses. Note that clients could
choose not to use the preferred address.
* If servers can use a dedicated server IP address or port, other than the one
that the client initially connects to, they could use the preferred_address
transport parameter to request that clients move connections to that dedicated
address. Note that clients could choose not to use the preferred address.

A server in a deployment that does not implement a solution to
maintain connection continuity during connection migration
Expand Down