Re: [quicwg/base-drafts] In-flight not outstanding (#2120)

[janaiyengar <[e-mail]>]

janaiyengar commented on this pull request.

Using "data in flight" is fine without the hyphenation.

> @@ -400,7 +400,7 @@ On each consecutive expiration of the crypto timer without receiving an
 acknowledgement for a new packet, the sender SHOULD double the crypto
 retransmission timeout and set a timer for this period.
 
-When crypto packets are outstanding, the TLP and RTO timers are not active.
+When crypto packets are in-flight, the TLP and RTO timers are not active.

```suggestion
When crypto packets are in flight, the TLP and RTO timers are not active.
```

> @@ -436,9 +436,9 @@ conditions:
   PTO SHOULD be scheduled for min(RTO, PTO).
 
 QUIC includes MaxAckDelay in all probe timeouts, because it assumes the ack
-delay may come into play, regardless of the number of packets outstanding.
-TCP's TLP assumes if at least 2 packets are outstanding, acks will not be
-delayed.
+delay may come into play, regardless of the number of packets ack-eliciting
+packets in-flight. TCP's TLP assumes if at least 2 ack-eliciting packets are

```suggestion
packets in flight. TCP's TLP assumes if at least 2 ack-eliciting packets are
```

> @@ -436,9 +436,9 @@ conditions:
   PTO SHOULD be scheduled for min(RTO, PTO).
 
 QUIC includes MaxAckDelay in all probe timeouts, because it assumes the ack
-delay may come into play, regardless of the number of packets outstanding.
-TCP's TLP assumes if at least 2 packets are outstanding, acks will not be
-delayed.
+delay may come into play, regardless of the number of packets ack-eliciting

```suggestion
delay may come into play, regardless of the number of ack-eliciting
```

> @@ -436,9 +436,9 @@ conditions:
   PTO SHOULD be scheduled for min(RTO, PTO).
 
 QUIC includes MaxAckDelay in all probe timeouts, because it assumes the ack
-delay may come into play, regardless of the number of packets outstanding.
-TCP's TLP assumes if at least 2 packets are outstanding, acks will not be
-delayed.
+delay may come into play, regardless of the number of packets ack-eliciting
+packets in-flight. TCP's TLP assumes if at least 2 ack-eliciting packets are
+in-flight, acks will not be delayed.

```suggestion
in flight, acks will not be delayed.
```

> @@ -796,7 +796,7 @@ Pseudocode for SetLossDetectionTimer follows:
       loss_detection_timer.cancel()
       return
 
-    if (crypto packets are outstanding):
+    if (crypto packets are in-flight):

```suggestion
    if (crypto packets are in flight):
```

> @@ -837,7 +837,7 @@ Pseudocode for OnLossDetectionTimeout follows:
 
 ~~~
    OnLossDetectionTimeout():
-     if (crypto packets are outstanding):
+     if (crypto packets are in-fight):

```suggestion
     if (crypto packets are in flight):
```

> @@ -1043,7 +1043,7 @@ kMaxDatagramSize:
   windows. The RECOMMENDED value is 1200 bytes.
 
 kInitialWindow:
-: Default limit on the initial amount of outstanding data in bytes.  Taken from
+: Default limit on the initial amount of in-flight data in bytes.  Taken from

```suggestion
: Default limit on the initial amount of data in flight, in bytes.  Taken from
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2120#pullrequestreview-184436678