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

s/alarm/timer/ #3650

Merged
merged 1 commit into from May 12, 2020
Merged

s/alarm/timer/ #3650

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
4 changes: 2 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -567,7 +567,7 @@ have been set for a now discarded packet number space.
Until the server has validated the client's address on the path, the amount of
data it can send is limited to three times the amount of data received,
as specified in Section 8.1 of {{QUIC-TRANSPORT}}. If no additional data can be
sent, the server's PTO alarm MUST NOT be armed until datagrams have been
sent, the server's PTO timer MUST NOT be armed until datagrams have been
received from the client, because packets sent on PTO count against the
anti-amplification limit. Note that the server could fail to validate the
client's address even if 0-RTT is accepted.
Expand Down Expand Up @@ -1251,7 +1251,7 @@ SetLossDetectionTimer():
return

if (server is at anti-amplification limit):
// The server's alarm is not set if nothing can be sent.
// The server's timer is not set if nothing can be sent.
loss_detection_timer.cancel()
return

Expand Down