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

Remove alarm references from the transport doc. #1590

Merged
merged 1 commit into from Jul 20, 2018
Merged

Remove alarm references from the transport doc. #1590

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2193,11 +2193,11 @@ While multiple paths might be used during connection migration, a single
congestion control context and a single loss recovery context (as described in
{{QUIC-RECOVERY}}) may be adequate. A sender can make exceptions for probe
packets so that their loss detection is independent and does not unduly cause
the congestion controller to reduce its sending rate. An endpoint might arm a
separate alarm when a PATH_CHALLENGE is sent, which is disarmed when the
corresponding PATH_RESPONSE is received. If the alarm fires before the
the congestion controller to reduce its sending rate. An endpoint might set a
separate timer when a PATH_CHALLENGE is sent, which is cancelled when the
corresponding PATH_RESPONSE is received. If the timer fires before the
PATH_RESPONSE is received, the endpoint might send a new PATH_CHALLENGE, and
restart the alarm for a longer period of time.
restart the timer for a longer period of time.


### Privacy Implications of Connection Migration {#migration-linkability}
Expand Down