From 1dc5a83ad1f6bdd68c177dfa2683b0313e63db51 Mon Sep 17 00:00:00 2001 From: Martin Thomson Date: Wed, 13 May 2020 09:12:10 +1000 Subject: [PATCH] s/alarm/timer/ --- draft-ietf-quic-recovery.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md index 37f2b1058f..58dc82439a 100644 --- a/draft-ietf-quic-recovery.md +++ b/draft-ietf-quic-recovery.md @@ -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. @@ -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