-
Notifications
You must be signed in to change notification settings - Fork 204
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Jana Iyengar
committed
Feb 1, 2018
1 parent
5ce6149
commit fd34af6
Showing
1 changed file
with
5 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2708,21 +2708,11 @@ implementation decision, and an implementation should be careful to delay | |
conservatively, since any delay is likely to increase application-visible | ||
latency. | ||
|
||
Regular QUIC packets are "containers" of frames. When an endpoint receives an | ||
ACK frame for one or more transmitted packets, all frames in the acknowledged | ||
packets are considered to have been received and processed by the peer, with one | ||
exception. A PATH_CHALLENGE frame (see {{frame-path-challenge}}) is used to | ||
validate a peer's ownership of its address. An ACK frame received for a | ||
PATH_CHALLENGE frame is not adequate to indicate that the PATH_CHALLENGE was in | ||
fact received. A PATH_CHALLENGE is considered acknowledged only when the | ||
corresponding PATH_RESPONSE (see {{frame-path-response}}) is received for it. | ||
|
||
A packet is never retransmitted whole. How an endpoint handles the loss of a | ||
frame depends on the type of the frame. Some frames are simply retransmitted, | ||
some have their contents moved to new frames, and others are never | ||
retransmitted. | ||
|
||
When a packet is detected as lost, the sender re-sends any frames as necessary: | ||
Regular QUIC packets are "containers" of frames. A packet is never | ||
retransmitted whole. How an endpoint handles the loss of a frame depends on the | ||
type of the frame. Some frames are simply retransmitted, some have their | ||
contents moved to new frames, and others are never retransmitted. When a packet | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
mikkelfj
Contributor
|
||
is detected as lost, the sender re-sends any frames as necessary: | ||
|
||
* All application data sent in STREAM frames MUST be retransmitted, unless the | ||
endpoint has sent a RST_STREAM for that stream. When an endpoint sends a | ||
|
, and some frames are retransmitted with updated content.