Re: [quicwg/base-drafts] Refine Discussion of 0-RTT Transport Parameters (#2467)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> -when accepting 0-RTT data.  A server uses the transport parameters in
-determining whether to accept 0-RTT data.
-
-A server MAY accept 0-RTT and subsequently provide different values for
-transport parameters for use in the new connection.  If 0-RTT data is accepted
-by the server, the server MUST NOT reduce any limits or alter any values that
-might be violated by the client with its 0-RTT data.  In particular, a server
-that accepts 0-RTT data MUST NOT set values for the following parameters
-({{transport-parameter-definitions}}) that are smaller
-than the remembered value of those parameters.
+The value of the server's previous original_connection_id, preferred_address,
+stateless_reset_token, and ack_delay_exponent MUST NOT be used when
+establishing a new connection; rather, the client should wait to observe the
+server's new values in the handshake.
+
+The client MAY store the server's original max_ack_delay and max_packet_size

The point of max_packet_size is to limit the size of packets.  I realize that if you are making a new connection, the limit applies only to 1-RTT packets because Initial and Handshake packets are sent without knowing what the limits are (the server could comply with a request to send smaller Handshake packets, and maybe the client could also, but it's not something we can guarantee).  However, when sending 0-RTT, you know what the limit was, so why not respect it?

-- 
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/2467#discussion_r257519311