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

Cite the second reason bytes_in_flight might exceed CWND #4006

Merged
merged 1 commit into from Aug 18, 2020
Merged

Cite the second reason bytes_in_flight might exceed CWND #4006

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
5 changes: 3 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -733,7 +733,8 @@ window in bytes.

An endpoint MUST NOT send a packet if it would cause bytes_in_flight (see
{{vars-of-interest}}) to be larger than the congestion window, unless the packet
is sent on a PTO timer expiration; see {{pto}}.
is sent on a PTO timer expiration (see {{pto}}) or when entering recovery
(see {{recovery-period}}).

## Explicit Congestion Notification {#congestion-ecn}

Expand Down Expand Up @@ -782,7 +783,7 @@ acknowledged. When a loss or ECN-CE marking is detected, NewReno halves
the congestion window, sets the slow start threshold to the new
congestion window, and then enters the recovery period.

## Recovery Period
## Recovery Period {#recovery-period}

A recovery period is entered when loss or ECN-CE marking of a packet is
detected in congestion avoidance after the congestion window and slow start
Expand Down