Re: [quicwg/base-drafts] Merge Crypto timeout and PTO (#2806)

[Jana Iyengar <[e-mail]>]

janaiyengar commented on this pull request.



> +The initial probe timeout for a new connection or new path SHOULD be
+set to twice the initial RTT.  Resumed connections over the same network
+SHOULD use the previous connection's final smoothed RTT value as the resumed
+connection's initial RTT.  If no previous RTT is available, the initial RTT
+SHOULD be set to 500ms, resulting in a 1 second initial timeout as recommended
+in {{?RFC6298}}.
+
+A connection MAY use the delay between sending a PATH_CHALLENGE and receiving
+a PATH_RESPONSE to seed initial_rtt for a new path, but the delay SHOULD NOT
+be considered an RTT sample.
+
+Until the server has validated the client's address on the path, the amount of
+data it can send is limited, as specified in Section 8.1 of {{QUIC-TRANSPORT}}.
+If not all data can be retransmitted, then data at Initial and Handshake
+encryption should be retransmitted before any ApplicationData data. If no data
+can be sent, then the PTO alarm should not be armed until data has been

```suggestion
can be sent, then the PTO alarm MUST NOT be armed until data has been
```

-- 
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/2806#pullrequestreview-259792135