Skip to content

Commit

Permalink
Reference coalesced packets in transport
Browse files Browse the repository at this point in the history
  • Loading branch information
ianswett committed Sep 10, 2020
1 parent 3f64dfa commit 554e892
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions draft-ietf-quic-recovery.md
Expand Up @@ -661,8 +661,9 @@ To speed up handshake completion under these conditions, an endpoint MAY send
a packet containing unacknowledged CRYPTO data earlier than the PTO expiry,
subject to the address validation limits in Section 8.1 of {{QUIC-TRANSPORT}}.

Endpoints can also use coalesced packets to ensure that each datagram elicits at
least one acknowledgement. For example, a client can coalesce an Initial packet
Endpoints can also use coalesced packets (see Section 12.2 of
{{QUIC-TRANSPORT}}) to ensure that each datagram elicits at least one
acknowledgement. For example, a client can coalesce an Initial packet
containing PING and PADDING frames with a 0-RTT data packet and a server can
coalesce an Initial packet containing a PING frame with one or more packets in
its first flight.
Expand Down

0 comments on commit 554e892

Please sign in to comment.