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.

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

editorial: Remove ACK-only (recovery) #3381

Merged
merged 3 commits into from Jan 22, 2020
Merged
Changes from all commits
Commits
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
16 changes: 6 additions & 10 deletions draft-ietf-quic-recovery.md
Expand Up @@ -111,16 +111,6 @@ when, and only when, they appear in all capitals, as shown here.

Definitions of terms that are used in this document:

ACK-only:

: Any packet containing only one or more ACK frame(s).

In-flight:

: Packets are considered in-flight when they have been sent and
are not ACK-only, and they are not acknowledged, declared lost,
or abandoned along with old keys.

Ack-eliciting Frames:

: All frames other than ACK, PADDING, and CONNECTION_CLOSE are considered
Expand All @@ -131,6 +121,12 @@ Ack-eliciting Packets:
: Packets that contain ack-eliciting frames elicit an ACK from the receiver
within the maximum ack delay and are called ack-eliciting packets.

In-flight:

: Packets are considered in-flight when they are ack-eliciting or contain a
PADDING frame, and they have been sent but are not acknowledged, declared
lost, or abandoned along with old keys.

# Design of the QUIC Transmission Machinery

All transmissions in QUIC are sent with a packet-level header, which indicates
Expand Down