Re: [quicwg/base-drafts] introduce a max_connection_ids transport parameter (#1998)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> @@ -3981,6 +3979,12 @@ A client MUST NOT include an original connection ID, a stateless reset token, or
 a preferred address.  A server MUST treat receipt of any of these transport
 parameters as a connection error of type TRANSPORT_PARAMETER_ERROR.
 
+max_connection_ids (0x000e):
+
+: The maximum number of connection IDs that the peer is willing to store.
+  This value includes only connection IDs sent in NEW_CONNECTION_ID frames.

The need for reciprocity in most cases that consume a connection ID does tend to lead to the numbers being approximately the same.  But it's not symmetric in the sense that they need to be equal.  The design is therefore asymmetric.  

If you consider a client that is moving between networks of questionable quality, they can burn connection IDs on futile probes, leading to greater consumption of connection IDs.  That suggests that a client might store more spares than a server.

-- 
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/1998#discussion_r256655813