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

[Mike Bishop <[e-mail]>]

MikeBishop 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.

Hm, that's true.  But the reverse creates an odd situation where the server can issue 7 CIDs when the client has said they only want 5, but the client can't (or shouldn't) reduce its value by 2 and constrain itself for the lifetime of the connection because of a start-only overflow.

Perhaps the server SHOULD NOT issue more total CIDs than this, but MUST NOT issue more CIDs via NCID?

-- 
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_r243078086